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-A13063 · Issue 227020

Autocomplete handles parameters with special characters

Resolved in Pega Version 7.2.1

Auto-complete was not properly handling filtering values containing apostrophes or other special characters. This has been fixed.

SR-A13115 · Issue 224892

Corrected sizing collapsed grid height to content

Resolved in Pega Version 7.2.1

A Repeating Grid using Progressive pagination and "Size grid height to content" with a configured number of rows to be shown without expansion was not accurately sized down when the content was below the display number. The function to adjust height of progressive grid has been fixed to display the content as expected.

SR-A13211 · Issue 229120

Numeric paging link '...' visible on all pages of large reports

Resolved in Pega Version 7.2.1

Using Numeric paging for Data-.pyGridPaginator, a report with more than ten pages did not correctly display the NextBunch pagination link '...' until the last page. This was an issue with a visibility condition available to pyGridPaginator, which has now been corrected.

SR-A13528 · Issue 229419

Fixed dropdown harness action focus

Resolved in Pega Version 7.2.1

If a pyActionArea section was dropped inside a harness with dropdown mode, the focus was going to the first focusable element in the harness when the dropdown was used to switch among local actions. This has been fixed.

SR-A13589 · Issue 227936

Datapage result usable as value in OpenURL

Resolved in Pega Version 7.2.1

When a Link was configured with an onclick event that called an 'Open URL in Window' action, giving the 'Alternate Domain URL' field a datapage result as a value resulted in an error. This was caused by findClassOfPageReference RUF not having handling for cases where Page.pxResults() was specified in the pages and classes. Support has been added such that if the specified index is not specified already, then check whether it is specified without index in pages and classes.

SR-A13674 · Issue 227843

repeat grid with progressive pagination error fixed

Resolved in Pega Version 7.2.1

A JS error occurred when using repeat grid with progressive pagination due to the system attempting to set the style attribute for a null element. The APIs have been updated for this nested grid scenario and to allow grid initialization to take care of assigning the proper index.

SR-A13779 · Issue 227492

Fixed repeat grid sorting for multiple pages

Resolved in Pega Version 7.2.1

During pagination, the grid was not retaining the sorting state, and sorting was broken from the second page onwards. The SortClipboardData activity for both pagination and sorting action has been updated to correct this.

SR-A13796 · Issue 229066

Error messages scroll while using WAI

Resolved in Pega Version 7.2.1

After moving all controls into dynamic layouts, error messages were not scrolling with the screen when using PegaWAI (accessibility). To correct this, the error msg span position will be set absolute from its parent.

SR-A13815 · Issue 227490

Events working for repeat grid with Top.<ListProperty> source

Resolved in Pega Version 7.2.1

Single click or double click events on a grid record were not working if Top. was used as source pagelist property. This was due to missing support for "Top.[pagelist]" in grids, which has been added.

SR-A13882 · Issue 228926

Date Control in expandable repeating grid shows proper date value

Resolved in Pega Version 7.2.1

The Date control in the repeating grid was showing the case ID number instead of the date value when configured as master-details with expandable rows. This was due to a missed use case of the "display read-only formatting" feature where a read-only condition configured on the control returned the editable control in the response instead of read-only. This 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