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-A99076 · Issue 265225

Localization added to pzManageRecords section

Resolved in Pega Version 7.2.2

Localization has been added to pzDataTypeOverview Section, pzDataTypeOverview harness, and pzManageRecords.

SR-A87643 · Issue 256839

Attachment section in case audit localized

Resolved in Pega Version 7.2.2

Localization has been added to the attachment section in case audit.

SR-A88035 · Issue 257024

Localization added for 'Close All' functions for multiple tab views

Resolved in Pega Version 7.2.2

Localization has been added to the 'Close All' menu item and tooltip that appear when multiple tabs are present, using the new field value pyMessageLabel.

SR-A96924 · Issue 270078

Enable browser cookies message appears as expected

Resolved in Pega Version 7.2.2

Mashup code while running on a browser with cookies disabled was not working as expected. The logic to find the whether the cookie is enabled or disabled has been improved, and if the cookie is disabled mashup will correctly prompt the message to enable it.

SR-A93026 · Issue 263587

Browser check added to avoid Microsoft Internet Explorer 8 busy indicator error

Resolved in Pega Version 7.2.2

Microsoft Internet Explorer 8 does not correctly support the UMicrosoft Internet Explorer vent that handles the busy indicator; a browser check has been added to prevent compatibility issues.

SR-A85972 · Issue 260745

Cancel button fixed for custom portal in Microsoft Internet Explorer 11

Resolved in Pega Version 7.2.2

On clicking the cancel button in a custom portal, an exception occurred when using Microsoft Internet Explorer 11. The exception says "There has been an issue, please consult your system administrator". This was due to the different browser handling of the div used for the target element, and a check and additional handling has been added to resolve this.

SR-A75557 · Issue 254432

Clipboard placeholder text issue resolved

Resolved in Pega Version 7.2.2

Placeholder text was being submitted to the server for text-area control while refreshing the current harness. This was due to the use of the old Action area which results in the form name 'ActionForm' while the system no longer had the code to support that name. The code to removePlaceholder Values on submit for ActionForm form case has now been added.

SR-A89260 · Issue 263428

Performance improvements for Proposition rule editing in Google Chrome

Resolved in Pega Version 7.2.2

Proposition' rule editing in Google Chrome was substantially slower than in other browsers due to the display handling for a text area present inside a Table structure with a heavy DOM. Performance has been improved by updating the code to avoid span generation for a minimum height setting in pixels and by optimizing the heightUpdate API.

SR-A97603 · Issue 264562

JAWS reads "Showing all reports"

Resolved in Pega Version 7.2.2

The Accessibility related property for dynamic layout of section pzRBShortcutsTitle7 has been updated to allow JAWS to read out the "Showing all reports" title.

SR-B426 · Issue 271503

Error label highlighting corrected for inside grid

Resolved in Pega Version 7.2.2

The correct label associated with the UI element in which the client side error was thrown was not highlighted when inside a grid. To fix this, the function findLabelFor has been updated to handle the case specific to the grid, as the error elements ID and the label's 'for' attribute were never equal due to the 'for' attribute changing value when used on repeating elements within a grid.

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