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-B3591 · Issue 278006

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

SR-B35931 · Issue 293471

prpcUtils readme updated for importing to Oracle

Resolved in Pega Version 7.3

The readme regarding importing to an Oracle database has been updated to reflect the current state of prpcUtils.

SR-B35963 · Issue 292315

pyID displayed in Show relevant Records

Resolved in Pega Version 7.3

Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.

SR-B35963 · Issue 292466

pyID displayed in Show relevant Records

Resolved in Pega Version 7.3

Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.

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 294119

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.

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