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-A12342 · Issue 226223

Standard System Usage Summary report updated with Daily Usage Table

Resolved in Pega Version 7.2.1

When the Standard System Usage Summary report was run, no users were shown even though users were able to access the system. The Hourly and Daily Usage Reports show data collection, but this was not propagated to the Summary report. This was an issue caused by the Summary Report not accepting values from the Daily Usage table, and schema updates have been made to fix this.

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

SR-A13729 · Issue 231588

Embedded Valuelist/valuegroup count included in manifest file

Resolved in Pega Version 7.2.1

The pxTotalInsertsCount for Embedded ValueList /ValueGroup Property was missing in the Manifest file while the pxTotalInsertsCount for Toplevel ValueList /ValueGroup Property was present. The Embedded Valuelist/valuegroup property count will now be included as expected.

SR-A14014 · Issue 227004

HTTP Connector API will dynamically set TLS protocol

Resolved in Pega Version 7.2.1

The HTTP Connector was failing to connect using TLS v1.2 protocol due to the SSL Protocol being hardcoded to TLS while setting SSLContext. To fix this, the system will not pass the protocol while instantiating SSLContext, but will leave it to the API to set to highest protocol from JRE.

SR-A14108 · Issue 242466

Better handling for rules considered duplicates

Resolved in Pega Version 7.2.1

A legacy API was not properly resolving rules present in an earlier ruleset version, leading to the creation of additional rules. The system will now consider rules already present in the earlier ruleset version and present the Other duplicate screen asking to skip, overwrite, or rename the rule.

SR-A14283 · Issue 232771

Service request retry works in async mode

Resolved in Pega Version 7.2.1

The Retry mechanism has been modified to correctly pass the child requestor's status when service is configured in async mode.

SR-A14781 · Issue 246050

Timeout value honored for ConnectSOAP using JMS Transport

Resolved in Pega Version 7.2.1

ConnectSOAP has a response timeout function, but this setting was not being honored when JMS transport was used. This has been corrected.

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