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-A99757 · Issue 265774

UpdateCalculationLabel modified to get embedded property label

Resolved in Pega Version 7.2.2

In Case Default rule -> open calculation tab, the calculated property field has a maximum value of 64 characters. In order to allow the setting of an embedded property as a target value (which would exceed the 64 character limit), pyUpdateCalculationLabel has been modified to get the label of the embedded property.

SR-A96555 · Issue 264154

RequiredSkills Declare Index fixed for Federated Case Manager

Resolved in Pega Version 7.2.2

In Federated Case Manager, skill-based routing of assignments to a workbasket generated a pyCommitError indicating "Cannot save instance of class Index-AssignmentSkills-Federated". This was due to missing index table properties needed by the Index-AssignmentSkills-Federated.RequiredSkills declare index, and has been fixed.

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

SR-A86522 · Issue 266946

ResumeFlow updated to handle SLA update in batch mode

Resolved in Pega Version 7.2.2

When any assignment configured with SLA was resumed by any agent in batch mode, the associated record in the pr_sys_queue_sla table was not getting deleted. To resolve this, the deletion method used in CompleteAssignment has been updated.

SR-A97665 · Issue 265978

ResumeFlow updated to handle SLA update in batch mode

Resolved in Pega Version 7.2.2

When any assignment configured with SLA was resumed by any agent in batch mode, the associated record in the pr_sys_queue_sla table was not getting deleted. To resolve this, the deletion method used in CompleteAssignment has been updated.

SR-A94083 · Issue 266677

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

SR-A97281 · Issue 263948

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

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