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.
SR-A99477 · Issue 266058
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-A96203 · Issue 270094
CreateCase rollback corrected
Resolved in Pega Version 7.2.2
While creating a sub-case and getting an error on any end-step of flow, Pega starts the rollback of the process, but was saving pxCoveredInsKeys in the Clipboard page of Case. This was a missing use case in AddCoveredWork to call RemoveFromCover if an error was thrown while creating a child case along with copying page pages from cover to primary, and has been corrected.
SR-A96203 · Issue 266909
CreateCase rollback corrected
Resolved in Pega Version 7.2.2
While creating a sub-case and getting an error on any end-step of flow, Pega starts the rollback of the process, but was saving pxCoveredInsKeys in the Clipboard page of Case. This was a missing use case in AddCoveredWork to call RemoveFromCover if an error was thrown while creating a child case along with copying page pages from cover to primary, and has been corrected.
SR-A91680 · Issue 259008
Resolved Null Pointer Error for resubmit of a corrected case with optimistic locking
Resolved in Pega Version 7.2.2
Work order case creation was throwing a null pointer exception in logs if optimistic locking was enabled on the case type and the case was resubmitted after correcting a validation error. This has been fixed with the addition of a null check for a clipboard page in use.