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