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-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-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-A14862 · Issue 231106

TrimLog performance improved

Resolved in Pega Version 7.2.1

Activity log.trimlog is called several times from the systemCleaner agent to clean up old entries of generally unused Log- classes. In order to improve performance on large logs, the previous partial load and delete method has been updated to a bulk cleanup using the purgeTableContainingClass() API in the Pega Database.

SR-A14879 · Issue 232530

Improved security for JSON stack

Resolved in Pega Version 7.2.1

To increase security, the response to invalid JSON input will display a generic InvalidStream message rather than the full class name and method name. The complete information will be available in the log.

SR-A15093 · Issue 231322

Activity preview includes preconditions, transitions

Resolved in Pega Version 7.2.1

The "Preview" of an activity (Actions dropdown | Preview) did not include preconditions, transitions information. In order to ease reviewing code changes between versions, these will now be included in the preview rule.

SR-A15105 · Issue 230713

Performance improvements for "Check out to Branch"

Resolved in Pega Version 7.2.1

The "Check out to Branch" operation was very slow in installations with very large ruleset lists. Performance has been improved by removing unnecessary calls to the GetAppRulesets activity.

SR-A15325 · Issue 231926

NPE resolved for WorkLock

Resolved in Pega Version 7.2.1

After upgrade, errors occurred in the WorkLock activity when attempting to create new Work Objects in a pre-production environment. This has been fixed.

SR-A15710 · Issue 232090

Additional logging added to diagnose stale thread errors

Resolved in Pega Version 7.2.1

In order to better diagnose issues with stale threads, loggers have been added to the ThreadData class to capture and print any stack trace which is causing the thread to be cleared or destroyed. These loggers will only be printed whenever a stale thread error is thrown in order to maximize log space.

SR-A15922 · Issue 231258

Support added for cleartext passwords in Snapstart

Resolved in Pega Version 7.2.1

When posting credentials from an external source, the code makes the assumption that the Password value is encoded and therefore it is decoded prior to being handed to the authentication activity in Pega. This is not always the case. If the Password value is passed as clear text the result in the activity is garbled. This creates problems when subsequent authentication is attempted to an external source. To support this handling, a new DASS 'authentication/Snapstart/pwddecode' has been added. When the setting is false, the password is not decoded in Snapstart cases and will necessitate a cleartext password.

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