Optimistic locking behaves incorrectly
A case type is configured with Optimistic locking. However, the conflict message displays incorrectly whenever it is updated by a background process.
Steps to Reproduce
- Enable the Optimistic locking for a case type
- Create a case of the same case type and keep the assignment open
- Make a few changes to the case through a background process (not manually, but through an activity using the Queue Processor)
- Submit the case on Pega once the background process is complete. No error occurs though 'The update was performed by a Queue Processor' message displays on the History tab
An issue in the client application code or rules. The pxUpdateDateTime property is not set in the Queue Processor activity. This property is checked by the pzShowConflicts activity.
Perform the following local-change:
Set the pxUpdateDateTime property in the Queue Processor activity.
0% found this useful