How can I prevent multiple users from accessing the same related action?

The problem with the Data Locking Strategies is it is not user friendly. If the collision occurs at the updating of the data step, each of the 2 users trying to trigger the related action will spend X number of minutes editing the data, but only one users' update will go through. Instead, the locking should occur immediately at the beginning of the related action, and the user that cannot make the changes should be informed immediately before they take unnecessary action on the record. Process reports were how we were planning on designing the solution, but because of the random variations in the time it takes to pull the report, it is not a correct solution in that both related actions (2 triggered at the same time) could pull either 0 active processes, 1 active processes, or 2 active processes. What we need is a true locking solution to solve this. Does anyone have experience in building a dynamic mutex solution in Java for an Appian plug-in?

The problem with the Data Locking Strategies is it is not user friendly. If the collision occurs at the updating of the data step, each of the 2 users trying to trigger the related action will spend X number of minutes editing the data, but only one users' update will go through. Instead, the locking should occur immediately at the beginning of the related action, and the user that cannot make the changes should be informed immediately before they take unnecessary action on the record. Process reports were how we were planning on designing the solution, but because of the random variations in the time it takes to pull the report, it is not a correct solution in that both related actions (2 triggered at the same time) could pull either 0 active processes, 1 active processes, or 2 active processes. What we need is a true locking solution to solve this. Does anyone have experience in building a dynamic mutex solution in Java for an Appian plug-in?