Avoid concurrent updates from Related action

Question

Hi, 
 Please suggest different and effective ways through which I can avoid multiple users accessing same related action to update records . 
 Thanks 
 Namrata

paragk998 · Accepted Answer

Hi Namrata, you can use @Version (case sensitive) to achieve this. just need to add @Version in column jpa annotation eg. @Id @GeneratedValue @Version

Mike Schmitt · Answer

The one technique I've seen used successfully is to include a database column, i.e. "isLocked" (boolean), which gets set to TRUE as soon as a user initiates a particular related action, and the same gets set back to FALSE when the related action is concluded or timed out. And if any user attempts to start the related action while the "locked" value is true, they're diverted away, perhaps to a task telling them that this record is locked.

jims419 · Answer

You can also accomplish something similar to what Mike is suggesting by using process analytics. If you have your related actions start a process instead of using a start form, you can use queryprocessananalytics to see if there are any active processes with whatever metadata you track for your record. This may or may not perform better depending on the rest of the structure of your app, but can help avoid database calls to write the locks.