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-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.

SR-A5351 · Issue 216605

Optimized Clipboard reference processing

Resolved in Pega Version 7.2

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

SR-A7513 · Issue 218791

Corrected timing of OnMessage firing on restart

Resolved in Pega Version 7.2

MDB Listeners that have been processing incoming messages successfully were becoming problematic when the JVM was restarted. At that time, PRJMSListener's onMessage() started to process JMS messages from the queue even when the PegaRULES engine had not successfully initialized, resulting in large numbers of repeating error messages in the log file. In order to resolve this, the PRJMSListener.java has been updated to check the node initialization in OnMessage() itself instead of invoke() of JMSListenerServant.

SR-A6621 · Issue 221216

Fixed locking on node level declare pages

Resolved in Pega Version 7.2

In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.

SR-A4310 · Issue 212995

Fixed locking on node level declare pages

Resolved in Pega Version 7.2

In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.

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