Conflict message does not display on updating case
A screenflow is present in a case type in the user's application. The Conflict message does not display on simultaneously updating the same case from another session in the screen flow. A transfer functionality is present. However, the transfer action is performed by the other user. In the transfer function, updatedatetime and pxupdatecounter are updated. In the other session where the screenflow is present, the message does not display on clicking the Submit button. However, the case is configured in the Optimistic locking.
Steps to Reproduce
- Create a case type with a screenflow
- Open Session1 as User1 and navigate to the last screen of the screenflow
- Update the case (pxupdatedatetime and pxupdatecounter) as User2 in Session2 by running an activity
- Submit the last screen as User1. Error message (conflict message) does not display
A defect in Pegasystems’ code or rules. The Optimistic Locking is not built for the screen flows in the initial iteration. It is scheduled to be enhanced in a future Pega release. RecalculateAndSave is added by FlowMethodBody first use assembly (FUA). The FUA checks for NeedToSaveWorkObject or not. This must be False in this case but it is True.
Perform the following local-change:
Perform a Save on each step of the flow instead of performing on the last step by unchecking the Save on last step checkbox.
0% found this useful