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-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-A91802 · Issue 260001

Apache Struts JARS updated to improve security

Resolved in Pega Version 7.2.2

The Apache Struts JARs have been updated to resolve the following potential security vulnerabilities: The REST plugin in Apache Struts 2 2.3.20 through 2.3.28.1 allows remote attackers to execute arbitrary code via a crafted expression. Apache Struts 2 2.3.20 through 2.3.28.1 mishandles token validation, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via unspecified vectors. The URLValidator class in Apache Struts 2 2.3.20 through 2.3.28.1 and 2.5.x before 2.5.1 allows remote attackers to cause a denial of service via a null value for a URL field.

SR-A97544 · Issue 267587

Calendar Gadget has correct start date after Daily to Weekly switch

Resolved in Pega Version 7.2.2

The Calendar Gadget was not working as expected in Weekly Mode. This was traced to the selected day in Daily mode being considered the first day of the week when the gadget was switched to Weekly mode, leading to open tasks being displayed against wrong dates in Weekly mode. This has been fixed by adding logic to calculate the first day of week when the gadget is switched to Weekly mode.

SR-A97544 · Issue 268332

Calendar Gadget has correct start date after Daily to Weekly switch

Resolved in Pega Version 7.2.2

The Calendar Gadget was not working as expected in Weekly Mode. This was traced to the selected day in Daily mode being considered the first day of the week when the gadget was switched to Weekly mode, leading to open tasks being displayed against wrong dates in Weekly mode. This has been fixed by adding logic to calculate the first day of week when the gadget is switched to Weekly mode.

SR-A99330 · Issue 267808

Calendar Gadget has correct start date after Daily to Weekly switch

Resolved in Pega Version 7.2.2

The Calendar Gadget was not working as expected in Weekly Mode. This was traced to the selected day in Daily mode being considered the first day of the week when the gadget was switched to Weekly mode, leading to open tasks being displayed against wrong dates in Weekly mode. This has been fixed by adding logic to calculate the first day of week when the gadget is switched to Weekly mode.

SR-A98702 · Issue 270066

Minor update to help doc for property optimization run time

Resolved in Pega Version 7.2.2

The help file for Property optimization using the Property Optimization tool has been updated with non-critical corrections to the phrasing regarding the length of time that might be required to perform background processing.

SR-A75956 · Issue 250547

D_OfflineWorkIDs DP performance improvements

Resolved in Pega Version 7.2.2

The logic of D_OfflineWorkIDs DP has been updated to improve performance for the SA PROD App.

SR-A94190 · Issue 264787

Paging on History-Work.pzGetMessageKeysForFlowDependencies list view disabled

Resolved in Pega Version 7.2.2

This list view History-Work.pzGetMessageKeysForFlowDependencies had paging enabled, but the activity Work.pzGetAllStatusforDepClass was not implemented to support paging and therefore would iterate only through the first page of a large listview. This has been resolved by disabling paging on the History-Work.pzGetMessageKeysForFlowDependencies list view to ensure all results are available for iteration.

SR-A96030 · Issue 264560

Read only dynamic select updates property value correctly

Resolved in Pega Version 7.2.2

When a dynamic select was in read only mode, it would show the incorrect property value if the source list of the dynamic select had changed since the value was set. This was due to Dynamic select is defaulting to the first value from the drop down in Read-only mode, and has been fixed by changing the out-of-the-box dynamic select to use pxDropDown so that the first value is not defaulted in Read-Only mode in the pzAssignmentTabInner section.

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