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-A12357 · Issue 230904

Corrected error handling logic when using KeepMessages

Resolved in Pega Version 7.2.1

Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.

SR-A12357 · Issue 231872

Corrected error handling logic when using KeepMessages

Resolved in Pega Version 7.2.1

Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.

SR-A12544 · Issue 230235

Error Header and Button Footer scrolling fixed

Resolved in Pega Version 7.2.1

Error Header and Button Footer scrolling was corrupted due to an absolute positioning error in the harness. This has been corrected.

SR-A12708 · Issue 228601

Resolved JS exception after editing data-bound grids

Resolved in Pega Version 7.2.1

On expand of row, a 'Rule not found' exception was thrown when a data-bound grid had a row added in the middle and then deleted. This was caused by the improper updating of the ID handles making the grid object look stale, and has been fixed.

SR-A12708 · Issue 231848

Resolved JS exception after editing data-bound grids

Resolved in Pega Version 7.2.1

On expand of row, a 'Rule not found' exception was thrown when a data-bound grid had a row added in the middle and then deleted. This was caused by the improper updating of the ID handles making the grid object look stale, and has been fixed.

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.

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