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-A16148 · Issue 231915

Support for value list and value group editing/deletion added

Resolved in Pega Version 7.2.1

Trying to update a valuelist using the clipboard generated an error during the processing after clicking on save due to the processing of finding the page value coupled to the valuelist within the activity UpdatePageFromCLipboardInMultiThreadedContext (step1). Support has been added for value list and value group editing/deletion to correct this.

SR-A16256 · Issue 231874

Exception recovery added to PegaAESRemote

Resolved in Pega Version 7.2.1

The presence of a bad or missing data-admin-db-table was causing an exception and exit when the PegaAESRemote agent sent data to PDC or AES to support analysis. The code has now been updated to handle the exception and continue to build the XML and send it across to PDC/AES.

SR-A16333 · Issue 232083

Added missing quotes for changetrack_updatefield values

Resolved in Pega Version 7.2.1

The From and To entries coupled to the field value changetrack_update were missing the necessary quotes for the Change events. This omission has been fixed.

SR-A16904 · Issue 234334

Wrapper added to expression builder for the jump transition on a step

Resolved in Pega Version 7.2.1

While using expression builder, selecting the option for "Enable conditions after this action" in an activity and submitting the expression did not show the expected result in the When input box. Attempting to use the expression builder again and submitting it then resulted in the screen freezing and requiring a refresh. To resolve this, a "pyStepsTransSection" wrapper section was been added for the "pyStepsTransParamsWhen" when condition.

SR-A16942 · Issue 239819

IAC updated to parse all gateway header paths

Resolved in Pega Version 7.2.1

While parsing the PegaRUles-SetGateWayContextURI, a problem was found with the system only considering the last two parts in the base URL multiple context/servlet paths. The system has been updated to parse all paths in gateway header while constructing servlet name.

SR-A16960 · Issue 233587

Predictive Analytics rulesets excluded from RSA

Resolved in Pega Version 7.2.1

The Pega-provided Predictive Analytics rulesets were being incorrectly being checked and flagged by the Rule Security Analyzer. The PAD rulesets have now been properly excluded from the RSA check, and further analysis was done to find and fix other RSA flags that should have been excluded.

SR-A17065 · Issue 233138

Support added for custom XSS headers

Resolved in Pega Version 7.2.1

After upgrade, problems were found with setting XSS headers. To resolve this, the new Dynamic System Setting "http/responseHeaders" has been added to support custom HttpResponseHeaders.

SR-A17338 · Issue 233583

Upgrade error resolved for localized rulesets in custom access group

Resolved in Pega Version 7.2.1

Due to an error in the MostFrequentlyUsedMap code, upgrading was failing if a particular environment had Requestor Type records referencing a custom Access Group that had localized rulesets. This has been fixed.

SR-A17425 · Issue 233173

Memory leak fixed in Field Value Conclusion Cache

Resolved in Pega Version 7.2.1

A memory leak was found with Field Value Conclusion caching not being correctly cleared of the dummy conclusion values for null objects. This as been resolved.

SR-A17758 · Issue 234057

Check added to avoid duplicate encryption

Resolved in Pega Version 7.2.1

When a property of type TextEncrypted was edited from the clipboard viewer, the encrypted value was being encrypted again. This was caused by the server side trimming the string values of parameters sent in a post body, removing '\t' from the encrypted value '\t{ps}XXXXX' and triggering encryption of an already encrypted value. To prevent this, the system has a check for strings starting with '\t{ps}' at the time of parsing URL Parameters or post body.

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