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-127042 · Issue 190334

Localization added for Operator profile values

Resolved in Pega Version 7.1.8

Localization has been added for the Operator profile full display custom labels.

SR-127121 · Issue 193264

Gauge Dial display in Case Manager updated for Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.8

After clearing the browser cache in Microsoft Internet Explorer 8 and logging into the case manager portal, the gauge dials disappeared. On relogin they appeared properly. This issue was due to the style attribute positioning being incorrectly represented in Microsoft Internet Explorer 8, and has been adjusted.

SR-127130 · Issue 192558

Localization added for filter values accessed from a new locale

Resolved in Pega Version 7.1.8

After building a Report Definition that used a custom section to display filter values, localization for the filter values was not working if a user logged in with a different locale. Code has been added to handle localizing filter value and label in this situation.

SR-127156 · Issue 191611

Corrected lost lock workflow error

Resolved in Pega Version 7.1.8

In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.

SR-127156 · Issue 193608

Corrected lost lock workflow error

Resolved in Pega Version 7.1.8

In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.

SR-127156 · Issue 194906

Corrected lost lock workflow error

Resolved in Pega Version 7.1.8

In a scenario where "Launch -> Local action" is used on a button without a grid component in the page, opening a modal window with Ok and Cancel buttons in it and then clicking the cancel and Next button on the main screen caused a Lock Lost error. This has been fixed.

SR-126907 · Issue 193779

Work objects in dynamic container corrected for the AES Manager portal.

Resolved in Pega Version 7.1.8

If a dynamic container is embedded in a section, the work objects opened through AES portal are opened in a dynamic container. When using the AES Manager portal with the Microsoft Internet Explorer 11 browser, work objects would open but then immediately the UI would scroll closed. This was a browser issue where harness tabs with IFRAME in production were not triggering the re-flow for DC tabs as they were for static tabs, and the system has been updated to perform this action correctly.

SR-127161 · Issue 199350

Localization fixed for buttons with shortcut key options

Resolved in Pega Version 7.1.8

Localization was missing for labels on buttons with shortcut key options. This has been fixed.

SR-127231 · Issue 192212

Validation resolved for Class as property reference in Activity Name

Resolved in Pega Version 7.1.8

If the Class was given as the property reference, attempting to enter the Activity Name generated the validation error "Attempting to access the rule in Bad class name: .HARNESSCLASSNAME" and the rule could not be saved. This was traced to the Property reference not being supported for Activity Name, and that has been added.

SR-127306 · Issue 193879

Added special character handling for Tooltips labels and icons

Resolved in Pega Version 7.1.8

Tooltips on labels and error icon were displaying the corresponding escape characters instead of the special characters intended. HTML screens did display these characters correctly. There was a workaround overriding the function in UserWorkForm, but this has been resolved by ensuring the value is html encoded and tooltip is using this value.

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