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-123238 · Issue 183084

Localized constant values in read-only format

Resolved in Pega Version 7.1.8

Constant values in read-only format in the formatted text control were not being picked up in the localization wizard. This was a defect in the GenerateFormat RUF, and has been fixed.

SR-123238 · Issue 178781

Localized constant values in read-only format

Resolved in Pega Version 7.1.8

Constant values in read-only format in the formatted text control were not being picked up in the localization wizard. This was a defect in the GenerateFormat RUF, and has been fixed.

SR-123239 · Issue 183080

Added localization for CategoryActions navigation rule

Resolved in Pega Version 7.1.8

The CategoryActions navigation rule has been made available for localization.

SR-123239 · Issue 180147

Added localization for CategoryActions navigation rule

Resolved in Pega Version 7.1.8

The CategoryActions navigation rule has been made available for localization.

SR-123241 · Issue 183082

Localization added for pyDashboardMiddle

Resolved in Pega Version 7.1.8

The pyDashboardMiddle section has been made available for localization in both the Pega-EndUserUI and UI-Kit-7 rulesets.

SR-123241 · Issue 182735

Localization added for pyDashboardMiddle

Resolved in Pega Version 7.1.8

The pyDashboardMiddle section has been made available for localization in both the Pega-EndUserUI and UI-Kit-7 rulesets.

SR-123242 · Issue 183215

Stage names now incuded in localization wizard

Resolved in Pega Version 7.1.8

Previously, Stage names were not picked up by the localization wizard unless each Case Type was saved in the application. An enhancement has been added to allow them to be localized more efficiently.

SR-123245 · Issue 185467

Resolved frame stack error with Flow GenerateAndProcessRequirements

Resolved in Pega Version 7.1.8

Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.

SR-123245 · Issue 185150

Resolved frame stack error with Flow GenerateAndProcessRequirements

Resolved in Pega Version 7.1.8

Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.

SR-123249 · Issue 184707

Stale stage completion checkmarks cleaned up

Resolved in Pega Version 7.1.8

When using a Split-For-Each shape with "Join" field set to "Iterate" and the Harness set to "TreeNavigation7" on a sub process tabbed screen Flow, the green tick marks which appear after completion of every stage in screen flow were not resetting for new items in the page list. Closing the workobject by clicking on red (X) mark and then reopening the same work object reset it properly. This was caused by missing logic to check whether FlowData should be reused or not, and has been fixed.

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