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-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-A16337 · Issue 232778

OCXinstaller install.bat script for Windows explicitly sets .cab file path

Resolved in Pega Version 7.2.1

The OCXinstaller install.bat script for Windows failed if it was run from the command line in a directory other than the one the script was stored in. The root cause was the batch file not finding the actual .cab files, as the batch file assumes the cab files are in the current path. The install.bat file has been updated to always uses the path of the batch file as the current path.

SR-A16398 · Issue 232765

UI-Kit updated to use Open Work by Handle in pyFavorites

Resolved in Pega Version 7.2.1

In the Manager portal, clicking on a parent case in the "Following" section opened the subcase instead of the parent case that was being followed. The issue occurred when utilizing the pyFavorites section in a UI-Kit that was configured with the Open Work Item action. To correct this, the UI-Kit for this release has been changed to use the Open Work by Handle option.

SR-A16401 · Issue 232956

Design-time email account accepts Data Page for port number

Resolved in Pega Version 7.2.1

When creating an Email Account rule (Integration-Resources), at design-time, the developer was prevented from using a Data Page reference as the Port number for the Sender or Receiver even though the run-time behavior of using a Data Page reference as a port worked. This has been resolved by removing the UI validation when the input starts with 'equal to', allowing Email Account save and connectivity testing to work with non-parameterized Data Page references for the port number in both Sender and Receiver configurations.

SR-A16406 · Issue 237367

Validation handling added for complex criteria values

Resolved in Pega Version 7.2.1

Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.

SR-A16406 · Issue 231876

Validation handling added for complex criteria values

Resolved in Pega Version 7.2.1

Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.

SR-A16432 · Issue 232172

Repaired Parse-Byte-Pos in File Listener

Resolved in Pega Version 7.2.1

Due to missing encoding for the type, files in byte format caused a NPE in file listener. This has been fixed.

SR-A16449 · Issue 234627

Java Mail API updated

Resolved in Pega Version 7.2.1

A bug in the Java Mail API 1.5.2 jar caused intermittent failures in receiving email. The API has been updated to the 1.5.3 jar.

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