Optimistic Locking

We are trying to follow best schema practices by referring to the document at https://docs.appian.com/suite/help/17.3/Database_Schema_Best_Practices.html.

The main question belongs to the section of "Optimistic Locking" wherein the implementation refers to implementing using @version annotation.

We did prototype and an alert is being raised in a condition when the version is stale. However, the alert being created is not visible to process initiator and

the process is breaking. We would like to see if there is any graceful approach of rolling back the changes in this scenario and also give a meaningful message

to the process initiator.

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data