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-B35965 · Issue 302489

Fixed copy from data page with optional data mapping

Resolved in Pega Version 7.3

When 'Optional data mapping' was used on a pageList property with the 'copy from data page' option enabled, data was not getting populated to the PageList if the filtered result was page type. This was traced to an issue with optional data mapping in a keyed data page, and has been resolved by changing the function to add the indexed page instead of directly using the FilteredClipboardProperty.

SR-B35965 · Issue 302490

Fixed data page copy with optional data mapping

Resolved in Pega Version 7.3

Copying from a data page with optional data mapping was not populating the PageList as expected when the filtered result was page type. This was due to missing clipboard handling when the data page was sourced by VL and the keyed result was a single page. To correct this, the indexed page will be copied instead of the FilteredClipboardProperty directly.

SR-B35965 · Issue 302490

Fixed data page copy with optional data mapping

Resolved in Pega Version 7.3

Copying from a data page with optional data mapping was not populating the PageList as expected when the filtered result was page type. This was due to missing clipboard handling when the data page was sourced by VL and the keyed result was a single page. To correct this, the indexed page will be copied instead of the FilteredClipboardProperty directly.

SR-B35987 · Issue 296514

Improved backwards compatibility for migrated rules with Declare Expressions

Resolved in Pega Version 7.3

The current activity pzUpdateConditionsList did not have backward compatibility for "AND" and "OR" operators in rules created with older version of Pega Platform that allowed the use of "And" and "Or". This has been resolved by adding a check for equalsIgnoreCase when converting "And" to "&&".

SR-B36091 · Issue 292431

Hazelcast logging added with updated jar

Resolved in Pega Version 7.3

Additional Hazelcast logging has been added and and the prcluster-7.1.jar has been rebuilt for better reliability.

SR-B36134 · Issue 294001

Security fix to prevent URL tampering

Resolved in Pega Version 7.3

Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.

SR-B36134 · Issue 294080

Security fix to prevent URL tampering

Resolved in Pega Version 7.3

Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.

SR-B36228 · Issue 292442

Improved RuntimeCacheImpl performance

Resolved in Pega Version 7.3

There was unnecessary contention within the RuntimeCacheImpl when that class was asked to provide information about a blank class name. To correct this and improve performance, a check for the empty class name has been moved out of the synchronized block to the top of this method.

SR-B36307 · Issue 292510

prconfig added to disable tracer checks in census

Resolved in Pega Version 7.3

There was some contention when checking for tracer to log trace events for access denials in a census application. Since tracer is not used in census, a prconfig switch has been added to disable these tracer checks.

SR-B36431 · Issue 293350

SOAP simulations restored

Resolved in Pega Version 7.3

SOAP simulations were not executed as expected due to the hard coded value SOAP being removed and made generic. This has been fixed by updating the service type to SOAP in the parameters passed to the simulations section.

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