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.
SR-B54277 · Issue 336406
Trimmed unneeded properties from doUIAction call
Resolved in Pega Version 7.4
Null pointer exceptions were generated when relaunching the manager portal after saving a work-object, and the error "Request-URL Too Large. The requested URL's length exceeds the capacity limit for this server" appeared. This was traced to the number of properties included in the doUIAction call; unnecessary parameters have been removed to resolve this issue.
SR-B66164 · Issue 325166
Handling improved for pzActiondropdown's Action label value
Resolved in Pega Version 7.4
When an alternate flow action was picked from LocalAction's list and then submitted, the presence of any page-set messages would cause the submission to fail and the flow remained on the same flow action. This was an issue with handling the changed value of the FlowAction label, and the pzActionDropdown control has been modified to get the correct pyDefaultActionIndex parameter value.
SR-B70422 · Issue 326897
Removed unnecessary add/delete history entries related to empty page properties
Resolved in Pega Version 7.4
The field level auditing configured for page group or list property types was creating multiple add and delete entries in the history of the case even though the pagelist/pagegroup had not been modified. This was traced to method used by the pagelist change audit process to compare current pages to the previous value of the pagelist pages: during pagetostring conversion, sometimes the empty properties in page are present in the String and sometimes they are not, resulting in a difference that generated the non-essential audit entries. This has been fixed by changing the getProperty references in getPageAsString function to use getIfPresent instead. Null checks have also been added.