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-A14313 · Issue 227652

Autocomplete displays properly after screen rotation

Resolved in Pega Version 7.2.1

A black gap appeared on the screen of iPad and iPhone devices when tying to use the autocomplete window after the screen was rotated between Portrait and Landscape modes. This was due to the autocomplete popover not accepting a % width setting, and the display method of the popover has been modified to display properly.

SR-A14325 · Issue 228543

Repositioned BusyIndicator to cover Target element

Resolved in Pega Version 7.2.1

If the section with busy indicator was taller than the viewport height, the busy indicator mask did not cover the lower part of the section when scrolling and the section was editable. This has been fixed by repositioning the mask to cover the part of the section editable in the viewport and also show immediately on scroll.

SR-A14386 · Issue 230504

Fixed issue with CSS incorrectly overriding skin rule

Resolved in Pega Version 7.2.1

The skin rule settings "Error Border" and "Error Background" were not having any effect on a text control which contained a validation error. This was an issue with the ErrorShade element being overridden by more specific CSS even though the HTML that used that CSS was never produced at run time. This has been corrected.

SR-A14599 · Issue 229391

Error section close icon positioning fixed

Resolved in Pega Version 7.2.1

The close icon in the error section was not properly positioned. This has been corrected.

SR-A14709 · Issue 237690

ShowBusyIndicator positioning codified

Resolved in Pega Version 7.2.1

The location of the showBusyIndicator function was inconsistent between browsers. The position calculations have been updated to correctly display the indicator in the center of the screen on all browsers.

SR-A14842 · Issue 233614

Screen reader updated to handle autocomplete

Resolved in Pega Version 7.2.1

The list in the dropdown was not read by the accessibility package if the focus was on the Autocomplete present in a modal dialogue. To correct this, the new function "AutoCompleteAG.updateLiveRegion" has been added to pega_autocompleteag.js for generating aria attributes for dropdown list items.

SR-A14890 · Issue 230875

Tab title XSS decoding updated

Resolved in Pega Version 7.2.1

Tab titles were not correctly decoding the "(" and ")" characters in the caseID for display due to the XSS handling. This has been updated.

SR-A14917 · Issue 230745

Improved repeat grid filtering performance for Microsoft Internet Explorer

Resolved in Pega Version 7.2.1

Using Microsoft Internet Explorer, a repeat grid with source as report definition was taking 30 seconds to show filter options, and canceling the column filter results could take over 90 seconds. The functions have been tuned with updated jQuery code to resolve the issue.

SR-A14990 · Issue 230019

pyIsAccessible property defaults to false for AG unless checked

Resolved in Pega Version 7.2.1

The pyIsAccessible property was not being set by default for new access groups. This will now be set to false if the "Enable accessibility add-on" is not checked in pyDefault data transform (Applies to Data-Admin-Operator-AccessGroup).

SR-A15288 · Issue 230371

Correct external portal rendering for "Where am I"

Resolved in Pega Version 7.2.1

The "Where am I" process flow diagram was not displayed using external portals. This issue occurred when the iframe and the parent frame had different origins, which prevented Viewer Data registering correctly. The system will now detect whether the parent frame has the same origin as iframe, then choose correct parent context to register Viewer Data.

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