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.
SR-A99040 · Issue 268520
Cleared email field in FieldMarketer campaign remains blank
Resolved in Pega Version 7.2.2
If the Email field of a FieldMarketer campaign was cleared and saved, closing and then reopening the session filled the email field with the Operator ID, which is not a valid email address. This was traced to Operator Email always defaulting to OperatorID if empty, and the activity has now been modified to not set the email field if empty.
INC-121435 · Issue 563875
Handling added for null requiredskillcount on assignment
Resolved in Pega Version 8.2.7
If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.
INC-122149 · Issue 562783
Corrected approval step task message
Resolved in Pega Version 8.2.7
When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.
INC-127077 · Issue 564107
Busy indicator appears when uploading via Select
Resolved in Pega Version 8.2.7
After update, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and has been resolved.