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-A20593 · Issue 238898

Pagination added to Hotfix Manager

Resolved in Pega Version 7.2.1

If there were more than 10 uncommitted hotfixes, the Hotfix Manager was not able to display them all due to a page limit and pagination being disabled by default. The pagination footer has now been made visible to allow viewing of the full list of uncommitted fixes.

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.

SR-A21196 · Issue 233151

RAP data pages made consistent across environments

Resolved in Pega Version 7.2.1

It was found that the Data pages for a RAP (rule-admin-product) deployed from dev1 to dev2 differed from the results of the same RAP deployed to demo if it contained a PageList(P1) inside which there is a PageList(P2) property that refers to Data Page (list type). This was caused by a handling difference between the two environments, and checks have been added to ensure consistent results.

SR-A21266 · Issue 239797

Ensured default display after grid takes effect in tree grid without explicit erase

Resolved in Pega Version 7.2.1

Old configurations were still visible after choosing ?Default (display after grid)? unless the value of the section name was explicitly erased. This was due to the generated java code that still contained the data displaying the values in fields it did not consider empty, and the handling has been corrected to resolve this.

SR-A21298 · Issue 240041

NPE on mobile list open resolved

Resolved in Pega Version 7.2.1

A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.

SR-A21487 · Issue 241066

Corrected GRANT generation for DB2 users

Resolved in Pega Version 7.2.1

When importing a RAP with a view into a DB2 10.1 LUW database, the GRANT statements were failing because of invalid syntax and the view creation was not executed. This was caused by the user name not being properly appended to the grant statement generation for DB2 users, and has been fixed.

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