Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C27585 · Issue 370960

Cassandra startup modified to use absolute path to needed files

Resolved in Pega Version 8.1

DDS was not starting on Windows, reporting that it was unable to find the cassandra.bat file. In this case, Cassandra was started using ".\cassandra.bat" command and the path to cassandra.bat was specified by setting the working directory in ProcessBuilder, but ProcessBuilder doesn't use working directory to find the location of the script. In order to ensure consistent startup behavior, the invocation of Cassandra scripts has been modified to run using an absolute path to Cassandra startup files in the command.

SR-C35969 · Issue 375783

Documentation updated to clarify how to use Tracer on Service Rules

Resolved in Pega Version 8.1

Due to an error in the documentation where the table of contents was pointing to an older version of the file, the information about configuring the Tracer to examine Service Rules was not clear. The document reference has been updated to point to the correct version which reads: Service rule tracing is only enabled in environments where the trace/cluster/ServiceRuleWatchMaxProductionLevel Dynamic System Settings is greater than or equal to the production level. By default, trace/cluster/ServiceRuleWatchMaxProductionLevel is set to 4, which means that the ability to trace service rules would not work in a production level 5 environment until trace/cluster/ServiceRuleWatchMaxProductionLevel is increased to 5.

INC-196079 · Issue 694397

Repaired shortcut key use in Flow Action default buttons

Resolved in Pega Version 8.5.6

After update, the shortcuts configured on flow action buttons stopped working. The previous version displayed the labels "Save" and "Cancel" on the portal and it was possible to use hotkeys to press the button. The updated system displayed "Sa&ve" and "Cance&l" and the shortcut did not work. This was traced to the encoding performed by the CrossScriptingFilter API, and has been resolved by ensuring the correct text value is retained and displayed for use with the hotkeys.

SR-B92421 · Issue 348757

Email Attachments use given mail encoding instead of defaulting to UTF-8.

Resolved in Pega Version 8.1

For email listener use cases, email attachments were always converted to HTML using UTF-8. This caused email characters to be changed when they were sent using any other type, ex ISO-8859-1 (Western European). To resolve this, the encoding used in the incoming email will be used to generate the HTML content before it is attached to the work object.

SR-C32947 · Issue 378777

Application Wizard works on application built using application type as framework

Resolved in Pega Version 8.1

Trying to run the Application Wizard on an application built on a framework was failing. This happened only when the framework being used was also built by the Application Wizard and no changes were made to that application after creation. The root cause of this was 'pyAccessGroupForAdministrator' not being correctly populated on the framework application during its creation. Setting this property during the framework application creation has fixed the issue.

SR-C20061 · Issue 362706

Logic changed to improve pr_assembledclasses use on multi-node systems

Resolved in Pega Version 8.1

Previously, each time an RUF was generated on a multi-node system a pulse event was sent to other nodes to re-generate the library as well. When these nodes would get the message, they would regenerate the library as well as in some cases send out the pulse event. In complex installations, this resulted in ~1.4 million updates per hour to the database table in pr_Assembledclasses. In order to improve performance, the system will no longer generate the library on a generate pulse event if eager population is enabled. The library is simply invalidated.

SR-C31109 · Issue 377026

Handling added to clear dashboard Data pages and thread when switching activity

Resolved in Pega Version 8.1

After publishing a dashboard to an application, everything worked as expected when directly logging into that application. However, if the user had multiple access groups and switched to another access group, the wrong dashboard was displayed and D_pxUserDashboardLoadList was not reloaded. This has been resolved by moving the D_pxUserDashboardLoadList Data page to Thread level and adding the new Data transform PZCLEARDASHBOARDDATAPAGES called from pzClearDataPagesBeforeSwitch. This will clear the dashboard Datapages and the thread when switching the activity.

SR-C43501 · Issue 382265

Handling added to clear dashboard Data pages and thread when switching activity

Resolved in Pega Version 8.1

After publishing a dashboard to an application, everything worked as expected when directly logging into that application. However, if the user had multiple access groups and switched to another access group, the wrong dashboard was displayed and D_pxUserDashboardLoadList was not reloaded. This has been resolved by moving the D_pxUserDashboardLoadList Data page to Thread level and adding the new Data transform PZCLEARDASHBOARDDATAPAGES called from pzClearDataPagesBeforeSwitch. This will clear the dashboard Datapages and the thread when switching the activity.

SR-C43501 · Issue 382522

Handling added to clear dashboard Data pages and thread when switching activity

Resolved in Pega Version 8.1

After publishing a dashboard to an application, everything worked as expected when directly logging into that application. However, if the user had multiple access groups and switched to another access group, the wrong dashboard was displayed and D_pxUserDashboardLoadList was not reloaded. This has been resolved by moving the D_pxUserDashboardLoadList Data page to Thread level and adding the new Data transform PZCLEARDASHBOARDDATAPAGES called from pzClearDataPagesBeforeSwitch. This will clear the dashboard Datapages and the thread when switching the activity.

SR-C47733 · Issue 389568

Handling added to maintain grid size when resize is run in a hidden DOM

Resolved in Pega Version 8.1

Grid layout height was getting set as 2px after opening a work item. This was traced to Grid height being reduced when the grid is in a hidden DOM and the resize handler was fired after a new tab was opened, making the grid content not visible. To correct this, a check has been added for contentHeight to avoid setting zero height when this code is run in hidden DOM.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us