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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A8072 · Issue 221510

Node name handling smoothed for passivation restore

Resolved in Pega Version 7.2

During database migration, the error 'PRMissingContextError: Cannot restore passivated page.' could occur due to handling issues with PR_SYS_STATUSNODES related to upper and lower case IDs. This has been resolved.

SR-A10683 · Issue 222397

Data transform chaining logic corrected for execution order

Resolved in Pega Version 7.2

In some cases, the execution order for super class data transforms was incorrect, causing them to run in reverse of the expected order of class inheritance. The logic for the chaining order has been updated to perform the expected sequence of executing data transform from directed inheritance and then from pattern inheritance.

SR-A14174 · Issue 227463

Improved cache clearing for AsyncServiceManager

Resolved in Pega Version 7.2

Due to changes made to the cache key pattern, the key generated to remove the ADP entry in AsyncServiceManager during request logout did not match the pattern. In some cases this led to an OOM error. The cache clearing has been updated to resolve this problem.

SR-A12864 · Issue 224900

Base64 accepts input with and without ('=') padding characters

Resolved in Pega Version 7.2

When the input given to Base64Util.decode API did not have the extra padding characters '=', the API ignored the last characters of a string with lead and trail braces ('{' and '}') when encoding and decoding and returned inaccurate results. These extra padding characters are used to complete the block structures and to maintain the correct length for the input, so logic has been added to append the remaining padding characters '=' if the input string is of incorrect length.

SR-A12707 · Issue 229383

Subreport join/filter updated

Resolved in Pega Version 7.2

An invalid subreport join/filter condition error was thrown if a filter with an unoptimized property from a sub report on one side had an optimized or literal property on the other side, even if the prconfig setting "reporting/useStreamInJoinConditions" was set to true. This has been fixed.

SR-A13449 · Issue 226932

Passivation fixed for softphone pages

Resolved in Pega Version 7.2

If a softphone page idled for 4 hours, a requestor level page (ScreenPopControlPort) became empty and prevented the user from logging in again. This was caused by a passivation issue that led to the parent page not being correctly set upon reactivation, and has been fixed.

SR-A13449 · Issue 222715

Passivation fixed for softphone pages

Resolved in Pega Version 7.2

If a softphone page idled for 4 hours, a requestor level page (ScreenPopControlPort) became empty and prevented the user from logging in again. This was caused by a passivation issue that led to the parent page not being correctly set upon reactivation, and has been fixed.

SR-A10527 · Issue 221023

Issue with unwanted additional PageList property row corrected

Resolved in Pega Version 7.2

An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.

SR-A10527 · Issue 221549

Issue with unwanted additional PageList property row corrected

Resolved in Pega Version 7.2

An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.

SR-A5351 · Issue 218740

Optimized Clipboard reference processing

Resolved in Pega Version 7.2

Enhancements have been made to optimize reference properties processing for the ClipboardPageImpl.expandAllIfUnexpandedReferenceProperties method.

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