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-A20346 · Issue 242973

Cell height/width rounded in "," decimal locales

Resolved in Pega Version 7.2.1

Localization for areas that use "," as the decimal separator led to errors indicating the height/width of a merged cell of Free Form layout was a non-integer value. To avoid this, the design time JS will round the measurement for cellWidth and cellHeight.

SR-A20352 · Issue 242962

Scroll handling updated for autocomplete results popover

Resolved in Pega Version 7.2.1

Issues were found with the scrolling handling of an autocomplete popover opened inside a modal window. The pzpega_ui_popover.js has been modified to attach a scroll handler for modal dialog scroll, and code has been added in the clickaway handler to reposition the popover during scroll.

SR-A20391 · Issue 240293

Set enter key use for Google Chrome pagination

Resolved in Pega Version 7.2.1

In Google Chrome, the enter key was not working on the pagination gadget if the report was opened in a new window, but tab would fire the page change. Functionality has been added to the GridActivePage control to create the expected behavior.

SR-A20444 · Issue 238240

BusyIndicator masking fixed for Microsoft Internet Explorer and Firefox

Resolved in Pega Version 7.2.1

BusyIndicator masking was not working properly in Microsoft Internet Explorer and Firefox due to using the scrollTop property which does not work for body elements in these browsers. This has been fixed by adding a browser check and calculating scrollTop from documentElement.

SR-A20569 · Issue 238382

Mandatory date and amount fields validation performed before reset

Resolved in Pega Version 7.2.1

Date and amount fields changed to incorrect format if any mandatory field was empty and screen was saved. This was traced to a handling error where the reset of read-only formatting happened before the validation check, and has been fixed.

SR-A20790 · Issue 239549

Refresh section works after spellcheck

Resolved in Pega Version 7.2.1

When using a radio button with section refresh and conditional layouts and an additional spell check icon, clicking on the spell check icon and then changing the radio button value did not refresh the section. Instead, the busy indicator symbol appeared and caused the system to hang. This was traced to a permission denied JS error occurring on the refresh section after spellcheck when the getListeners API tried to access an orphaned RTE body. This has been fixed.

SR-A20861 · Issue 240914

Value populating made consistent for cascading dropdowns

Resolved in Pega Version 7.2.1

Cascading drop downs sourced from large data pages were not consistent about populating the values. The issue was caused by variable synching, and has been fixed.

SR-A20974 · Issue 241074

Validation will not set errors for hidden fields

Resolved in Pega Version 7.2.1

Autocomplete was generating a hidden input for a property referred to in the Search results configuration and displaying it first when the validation checked the property entry handle, causing an error. Required validation has now been modified to not set errors on hidden fields.

SR-A21040 · Issue 243518

Filter icon display corrected for Microsoft Internet Explorer11

Resolved in Pega Version 7.2.1

The filter icons were not properly vertically aligned when using Microsoft Internet Explorer 11. This was due to the parent of the filter icon element not having a height attribute read by this browser, and has been fixed.

SR-A21043 · Issue 241137

Refresh list action retains focus on work area

Resolved in Pega Version 7.2.1

When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.

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