SR-B13418 · Issue 283237
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.
SR-B13702 · Issue 287232
SLA correctly calculated for migrated rules
Resolved in Pega Version 7.3
After upgrade, using the case designer view to look at a case type created in an earlier version displayed errors in the right panel for the goal-HH:MM:SS and deadline-HH:MM:SS fields if the assignment had the SLA rule "Default". This was an error in backwards compatibility related to whether the "pzIsAutoGenerated" property used to distinguish the SLA was auto generated or not, and has been corrected by setting the Visibility condition .pzAutoGenerated to 'true' in the lower Dynamic layout to avoid a null value in migrated rules.
SR-B13872 · Issue 290520
StartDependencies RUF logging updated from Error to Debug mode
Resolved in Pega Version 7.3
After calling a utility to create a child case through an activity on a parent sub-flow, updating the parent case status with the "UpdateStatus" activity logged an error message that the dependent had not been created successfully. This was an unintended side effect of a logging change made for diagnostic purposes, and has been fixed by changing the logs from Error mode to Debug mode in the pzStartDependencies RUF.
SR-B14774 · Issue 285008
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B14774 · Issue 285027
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B15604 · Issue 286328
Made InputProperty not mandatory for business logic
Resolved in Pega Version 7.3
When business logic is selected, pzToDecisionTreeExpress is selected as the routing activity for the assignment. However, errors occurred due to the mandatory parameter InputProperty property being passed as empty. To address this, the parameter will be marked as not mandatory.
SR-B16331 · Issue 303039
Check added to WorkUnlock to ensure cover page exists
Resolved in Pega Version 7.3
An intermittent error was logged related to workunlock. This was caused by Work-.Close calling workUnlock from the param.coverPage without performing a check first to ensure that the coverPage exists and has a class. To fix this, the WorkUnlock activity has been modified to verify that the coverPage has a class before unlocking the cover object.
SR-B16331 · Issue 294717
Cover page check added to Work-Close
Resolved in Pega Version 7.3
An intermittent stack trace was being generated in Work-Close; this has been resolved by adding a check to ensure that the coverPage exists and has a class.
SR-B16784 · Issue 287160
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.
SR-B17100 · Issue 290607
Optimistic locking fixed for GetNextWork
Resolved in Pega Version 7.3
The optimistic locking feature was is not working as expected when GetNextWork was invoked. This was caused by missing parameter passing, and has been fixed.