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-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-A13184 · Issue 230179

Corrected count mismatch in compared XML outputs

Resolved in Pega Version 7.2.1

A count mismatch between the XML output file and the manifest file for XML output format for embedded page list properties has been resolved to ensure accurate reporting.

SR-A13184 · Issue 229061

Corrected count mismatch in compared XML outputs

Resolved in Pega Version 7.2.1

A count mismatch between the XML output file and the manifest file for XML output format for embedded page list properties has been resolved to ensure accurate reporting.

SR-A13187 · Issue 226047

JSON mapping performance enhanced

Resolved in Pega Version 7.2.1

JSON mapping performance has been enhanced with the addition of a native JSON property cache along with the introduction of a DSS to skip all unnecessary intensive checks if the JSON node name is found to be valid. This will be handled through a DSS JSON/useNativeAPI which when set uses adoptJSONObject/adoptJSONArray() as the API for inbound JSON parsing. Please note that if the DSS is set, homogeneous arrays are only supported with valuelist configuration in connectors. Heterogeneous arrays are not supported when DSS is set.

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