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-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.

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-A13590 · Issue 239611

Updated handling for Cyrillic usernames

Resolved in Pega Version 7.2.1

On systems where Windows user name was created in Cyrillic (ex C:\Users\?????? ????), generated word documents would be empty due to the characters in the directory name not being properly handled. The system now contains modified Silverlight code that will read the registry keys using RegOpenKeyEx, RegQueryValueEx and RegCloseKey functions of advapi32.dll as opposed to previously used RegRead function of Wscript.shell. These new registry functions are Unicode-aware. The Silverlight Prerequisites installer has also been modified to include the latest certificate.

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