StatusWork is not getting updated after completion of case
User introduced an activity in dynamic Audit Log updating, which is being called in almost all steps of a case life cycle to update the Audit history dynamically.
Once case gets completed the case status remains in "In Progress" stage only.
Out-of-the-box (OOTB) Audit logging status shows correct status.
2017-10-18 10:35:42,157 [ PegaRULES-Batch-8] [ STANDARD] [ ] [ NGDP2:01.01.01] ( ResumeFlow.Work_.Action) ERROR - Save, Delete or Commit has failed because lock "BG-NGDP2-WORK A-280" is not held
2017-10-18 10:35:42,222 [ PegaRULES-Batch-8] [ STANDARD] [ ] [ NGDP2:01.01.01] ( ResumeFlow.Work_.Action) ERROR - The assignment with handle ASSIGN-WORKBASKET BG-NGDP2-WORK A-280!SETUP_FLOW_0 could not be opened
2017-10-18 10:35:42,305 [ PegaRULES-Batch-8] [ STANDARD] [ ] [ NGDP2:01.01.01] ( ResumeFlow.Work_.Action) ERROR - The assignment with handle ASSIGN-WORKBASKET BG-NGDP2-WORK A-280!SETUP_FLOW_0 could not be opened
Steps to Reproduce
- Run the Case.
- After successful completion of case, click on Audit tab displaying the audit log stating case completed last step; however, case status remains in InProgress instead of Resolved-Completed.
Looking into the custom activity, that is,UpdateCase, as per step-2 lock and release onCommit has been enabled.
Step-4 internally (through commitWithErrorHandling activity) also does Commit(refer step-4 of commitWithErrorHandling activity).
If ReleaseOnCommit is used for opening the work object, and if there exists an extra commit in the application (in the use case via the call to commitWithErrorHandling), that will cause the work object to be unlocked sooner.
Perform the following local-change:
Uncheck ReleaseOnCommit for the Obj-Open step of the custom activity.
0% found this useful