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-A22615 · Issue 244189

Fixed positioning for Options lightbox

Resolved in Pega Version 7.2.1

The Options lightbox in the calendar was floating with the screen while scrolling due to absolute positioning, and has been fixed.

SR-A22750 · Issue 244061

Case Stages status updated by automated process

Resolved in Pega Version 7.2.1

Case stages that were completed by an automated process and not a person maintained their default "Future" status in the Case Stages data page instead of being marked "Past". The stage completion status is determined by value in "pxCompletedBy", but this field was empty due to the automation. A check has been added to resolve this.

SR-A22816 · Issue 246151

Message clearing CME error fixed

Resolved in Pega Version 7.2.1

A Concurrent Modification Exception error as thrown in logs when navigating to from one row to another row in tree grid due to a data page being loaded while trying to clear messages in a page. This has been resolved by disabling auto populate while in the process of clearing messages in a page.

SR-A22933 · Issue 241566

Check added to resolve Google Chrome-based value localization error

Resolved in Pega Version 7.2.1

A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.

SR-A22958 · Issue 247141

Mobile Client passivation fixed

Resolved in Pega Version 7.2.1

Data pages were not being properly passivated in the mobile client. This was traced to an exception generated by the isFromDictionaryFlag() function when navigating to or from PRE assignment to any other assignment in the flow after hitting unknown list and unknown group settings. As the isFromDictionary function is not necessary here, it has been removed.

SR-A22982 · Issue 249598

Resolved memory leak in ActionRequestRegistrarContainer cleanup

Resolved in Pega Version 7.2.1

A memory leak was traced to ActionRequestRegistrarContainer objects not being garbage collected. In the Tampering protection feature, an ActionRequest Registrar per HarnessID is still created in ALLOW mode, however it will not be removed as done in the cases of WARN and DENY modes. To resolve this, the system has been updated to not create containers in ''ALLOW" mode.

SR-A23012 · Issue 242327

pega.u.d.onViewUpdatecorrectly triggered from Master-Detail

Resolved in Pega Version 7.2.1

The "pega.u.d.onViewUpdate" function invocation was not being triggered as expected when the details screen was opened from a master list while offline. To fix this, the "actionInfo" pzInskey has been updated to obtain the Page Context on which the RDL is configured.

SR-A23178 · Issue 248200

Checkout to branch ruleset handling improved

Resolved in Pega Version 7.2.1

The Checkout to branch option was not able to find a list of branches in Pega Marketing after a minor ruleset migration. To resolve this, the system will make use of a non versioned ruleset name for showing branches if an application is referring a ruleset whose major or minor version is different from the Ruleset of the Rule that is being checked out.

SR-A23222 · Issue 244490

"Deadline date" corrected for German locale

Resolved in Pega Version 7.2.1

When a case was opened, the deadline shown in the top was in the wrong format for a German locale. This was caused by the standard translation method being used, and has been corrected by replacing the non-auto-generated pyCaseDeadline control with pxDateTime control to fix the issue.

SR-A23282 · Issue 245229

Checkout to branch ruleset handling improved

Resolved in Pega Version 7.2.1

The Checkout to branch option was not able to find a list of branches in Pega Marketing after a minor ruleset migration. To resolve this, the system will make use of a non versioned ruleset name for showing branches if an application is referring a ruleset whose major or minor version is different from the Ruleset of the Rule that is being checked out.

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