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

Save Button error in Optimistic Lock



Using Optimistic Locking, when the same work object is updated in another session during a screen flow, the Save button displays an error.

Error Messages

The Operation completed successfully but returned no content.

Steps to Reproduce

  1. Create a case type.
  2. Add a screen flow.
  3. Add an input text property.
  4. Execute the case type.
  5. Add a value to the field.
  6. Click Save.
  7. Open the same work object in a new browser session. 
  8. Click Begin..
  9. Modify the field value.
  10. Click Save. 
  11. Return to the first session.
  12. Click Save.
  13. Observe the error message.

Root Cause

A defect in Pegasystems’  code or rules.
The issue was with the actions configured in the Save button of the pyCaseActionAreaButtons section.


Perform the following local-change:

Since the section is available and present in the UI kit, override the section and perform the below configurations:
  1. In dynamic layout 5, open the Configuration of the Save button.
  2. In Actions, retain only the out-of-the-box Save action, and remove the When condition and Run script action.
Suggest Edit

Published August 16, 2019 - Updated October 8, 2020

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