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-A12980 · Issue 227344

Added dropdown to select applications for new requirements

Resolved in Pega Version 7.2.1

A dropdown has been added to the Requirements screen to display the existing applications for the current user when creating new requirements.

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.

SR-A13187 · Issue 229142

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.

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-A13464 · Issue 227723

Tracer updated to handle encrypted URLs

Resolved in Pega Version 7.2.1

Tracer was not working properly when encrypting URLs. To resolve this, the URL will be obtained from the clipboard property instead of depending on the URL when encryption is present.

SR-A13472 · Issue 231026

History tables updated for deletion and importing.

Resolved in Pega Version 7.2.1

The history table was not properly updated for actions on Data tables when deleting or importing new records using the pzDeleteRecord activity. There were no problems for adding or updating. Previously, pzDeleteRecord activity did not modify the history table, and that tracking has been added so that activity can be used in this manner.

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