Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Optimistic locking behaves incorrectly

KCP-331

Summary

A case type is configured with Optimistic locking. However, the conflict message displays incorrectly whenever it is updated by a background process.

 

Error Messages

Not Applicable

 

Steps to Reproduce

  1. Enable the Optimistic locking for a case type
  2. Create a case of the same case type and keep the assignment open
  3. Make a few changes to the case through a background process (not manually, but through an activity using the Queue Processor)
  4. 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 

 

Root Cause

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.

 

Resolution

Perform the following local-change:
Set the pxUpdateDateTime property in the Queue Processor activity.

Suggest Edit

Published December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us