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-A7611 · Issue 217142

Ampersand not rendered properly for DropDown

Resolved in Pega Version 7.2

In case of dropdowns with defer load, options having "&" were being double-encoded and displayed as '&'. The API has been updated to correctly handle the special character.

SR-A1440 · Issue 213844

Added catch for unspecified layout format

Resolved in Pega Version 7.2

Layouts saved without a format name were not rendering correctly; the container format was changed to 'other', which generated an exception due to the 'other' format not being available in the XML. To prevent this error, the layout format assignment is now wrapped in the JS with a try-catch.

SR-A3540 · Issue 210203

Added check for duplicate Date Control validation error

Resolved in Pega Version 7.2

In a screen flow, it is possible to move forward despite validation errors on the Date control. However, returning to the control caused the validation error message to be displayed twice. This was caused by both the server side and the client side generating the error. To correct this, logic has been added to check if the clipboard already has the messages defined in pClientErrors and avoid adding them to the clipboard if so.

SR-A6010 · Issue 215099

Added handling for special characters in RUF labels API

Resolved in Pega Version 7.2

A change in the handling of special characters such as quotation marks was causing compiler errors after upgrade. This was traced to the StringUtils.escapeIntoJavaString api for label generation in generateCellContent RUF and has been corrected.

SR-A6636 · Issue 215085

Added missing hover text for closing work object

Resolved in Pega Version 7.2

Hovering the mouse over the "X" (Close) icon in a work object was displaying the same message given when hovering over the tab. This was due to a missing "Title" attribute in the dynamic container, and has been fixed.

SR-A6636 · Issue 215085

Added missing hover text for closing work object

Resolved in Pega Version 7.2

Hovering the mouse over the "X" (Close) icon in a work object was displaying the same message given when hovering over the tab. This was due to a missing "Title" attribute in the dynamic container, and has been fixed.

SR-A3384 · Issue 212375

Added negation(!) handling for 'when' functions in icon control

Resolved in Pega Version 7.2

After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.

SR-A3384 · Issue 211149

Added negation(!) handling for 'when' functions in icon control

Resolved in Pega Version 7.2

After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.

SR-A2971 · Issue 215035

API updated for Tab Group error handling with Accordion layouts

Resolved in Pega Version 7.2

When there is error field on a section which has many Accordion layouts using Tab Groups configured with deferred load with/without pre-load, attempting to submit/refresh the section was generating an error and not rendering properly. This was an issue with the markSectionTabErrors API, and has been resolved.

SR-A2971 · Issue 213000

API updated for Tab Group error handling with Accordion layouts

Resolved in Pega Version 7.2

When there is error field on a section which has many Accordion layouts using Tab Groups configured with deferred load with/without pre-load, attempting to submit/refresh the section was generating an error and not rendering properly. This was an issue with the markSectionTabErrors API, and has been resolved.

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