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-A86964 · Issue 256956

Corrected date value created by ShowConflicts

Resolved in Pega Version 7.2.2

An invalid format date value was being created by the "pzShowConflicts" activity, causing problems when trying to submit an assignment updated by another agent. This has been fixed by setting the value with the PRDateFormat.DEFAULT_DATETIME_MEDIUM format instead of DD-MM-YYYY.

SR-A101006 · Issue 272734

JDBC password handling corrected

Resolved in Pega Version 7.2.2

After upgrade, a JDBC database connection on WebSphere 8.5/Oracle 11G indicated success on test connection, but a username/password "connection could not be obtained" error was thrown when attempting to save the connection. This was due to the handling of the encrypted password, and has been fixed.

SR-A98390 · Issue 264755

Scheduled report cleanup error resolved

Resolved in Pega Version 7.2.2

Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.

SR-A91839 · Issue 259235

Resolved ConcurrentModificationException in mContent iteration

Resolved in Pega Version 7.2.2

When adding or removing the items from a repeat grid and submitting the modal dialog, an intermittent ConcurrentModificationException was coming from the API ClipboardPageImpl.clearMessages(). This was traced to the function iterating over mContent and has been fixed by making a copy of mContent and iterating over that.

SR-A94737 · Issue 265585

Correspondence updated with party role change from dropdown

Resolved in Pega Version 7.2.2

On changing the party role from the drop down, the value was not updated in the correspondence. This was due to CreateSelectedCorr activity only being called when the correspondence was changed in the drop down, and has been resolved by regenerating the correspondence view any time an edit is selected and submitted.

SR-A94737 · Issue 265371

Correspondence updated with party role change from dropdown

Resolved in Pega Version 7.2.2

On changing the party role from the drop down, the value was not updated in the correspondence. This was due to CreateSelectedCorr activity only being called when the correspondence was changed in the drop down, and has been resolved by regenerating the correspondence view any time an edit is selected and submitted.

SR-A69740 · Issue 250228

Scheduled Reporting Review harness refresh updated

Resolved in Pega Version 7.2.2

When saving a scheduled report task, sometimes the changes were not applied correctly in the landing page. This has been resolved by updating the Pega-ScheduledTask-Reporting.Review harness so a save action will refresh a section rather than refreshing the harness twice.

SR-A100106 · Issue 266744

Include from clipboard validation corrected

Resolved in Pega Version 7.2.2

An error was generated when attempting to save a section included via clipboard page due to the wrong page class being sent for the clipboard section. This has been fixed by setting the GetPageClass RUF to pick the proper page name while sending it for validation.

SR-A20694 · Issue 256036

Added overlay modal dialog check in service intent

Resolved in Pega Version 7.2.2

The enter key press was not working as expected when searching for a new service intent. While another service intent was currently open, 'enter' jumped back to the open service intent. This has been corrected by adding a target check for an overlay modal dialog.

SR-A98390 · Issue 252437

Scheduled report cleanup error resolved

Resolved in Pega Version 7.2.2

Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.

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