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-A14464 · Issue 228529

Enhancements to SystemCleaner and SystemPulse

Resolved in Pega Version 7.2.1

Insufficient allocated space for passivation data in a shared filesystem can lead to passivated requestors not being properly cleaned up and possible OOM issues. In order to provide better support, SystemCleaner has been enhanced to better diagnose issues related to insufficient allocation, and any resulting information can be found in deleteExpiredDir in com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage . In addition, when the system pulse is disabled via pxSystemNodeStatus set to Unknown, it would silently run in SMA and no log messages were generated. Since critical agents should provide a more visible indication that the processes are not running as expected, both System Pulse and SystemCleaner have been modified to stop the server startup and report when the server status is unknown.

SR-A14493 · Issue 227902

Clipboard viewing on SMA fixed

Resolved in Pega Version 7.2.1

Any user having Manager as the default portal was having difficulty viewing the clipboard pages. This was due to the XML being generated incorrectly for the clipboard of requestors with more than one thread open in them. This has been fixed.

SR-A14562 · Issue 231191

Enhanced logging to debug Composite Portal Menu rendering errors

Resolved in Pega Version 7.2.1

In order to better diagnose exceptions generated when trying to render a Section from Composite Portal Menu, more debug logs have been added when DatabaseImpl.open is called on any particular instance. The debug logs will print the authorization related information - the ruleset list, the current thread, current access group etc.

SR-A14584 · Issue 230941

Timing changed on rapid row deletion to resolve value shifts

Resolved in Pega Version 7.2.1

When editing a decision table, rapidly deleting rows and then clicking to the first row sometimes resulted in the first row's value being altered to the value of a different row. This was due to overlapping calls. To avoid this, the "DELETEROW-BUTTON" will be disabled after click until the deletion of the current row is complete.

SR-A14599 · Issue 229391

Error section close icon positioning fixed

Resolved in Pega Version 7.2.1

The close icon in the error section was not properly positioned. This has been corrected.

SR-A14619 · Issue 229625

Alignment resolved for repeating grid headers

Resolved in Pega Version 7.2.1

Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.

SR-A14709 · Issue 237690

ShowBusyIndicator positioning codified

Resolved in Pega Version 7.2.1

The location of the showBusyIndicator function was inconsistent between browsers. The position calculations have been updated to correctly display the indicator in the center of the screen on all browsers.

SR-A14740 · Issue 232865

Edit button page retrieval updated for better accuracy

Resolved in Pega Version 7.2.1

Due to the Edit button configuration for Data types passing the identical name "Data Type" to the Landing Page action configuration, the pages being retrieved for editing were inconsistent when moving between the Dashboard and the Manage Change screen. The system has now been updated to pass the unique pyInsHandle key for every data type to ensure expected results.

SR-A14740 · Issue 232864

Edit button page retrieval updated for better accuracy

Resolved in Pega Version 7.2.1

Due to the Edit button configuration for Data types passing the identical name "Data Type" to the Landing Page action configuration, the pages being retrieved for editing were inconsistent when moving between the Dashboard and the Manage Change screen. The system has now been updated to pass the unique pyInsHandle key for every data type to ensure expected results.

SR-A14774 · Issue 233421

Number formatting made consistent for Propositions

Resolved in Pega Version 7.2.1

In Proposition landing, a decimal property was rounded to three digits when shown in read-only mode but clicking on the edit option for the Proposition displayed the entire number with all the digits after the decimal. This was not a desired difference, and the presentation setting for Double type property has been modified to show all numbers after the decimal.

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