How to handle the multi-screen problem?https://community.appian.com/discussions/f/user-interface/28016/how-to-handle-the-multi-screen-problemAny thoughts on how we can handle this problem?Did anyone else faced similar issue and how did you handled it? Many times recently we have cases that get &quot;stuck&quot; are doing so because someone processes on them twice. There&#39;s three flavors of this: en-USTelligent Community 12RE: How to handle the multi-screen problem?https://community.appian.com/thread/109030?ContentTypeID=1Wed, 08 Mar 2023 16:47:41 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:95c41d8f-cefc-4a41-8b60-3aac6b286d0bjasmithak<p>By Implementing Optimistic lock and pessimistic lock.</p> <p></p> <p>Optimistick lock works for option 1 and 3, Have &quot;version&quot; column in the main table and check for version before writing to DB,&nbsp;if it is in lower version then write to DB else route it back to UI saying data is modified by other.</p> <p>Pessimistic lock for option 2, have column in db &quot;isLocked&quot; if anyone opens a related action to update the case record, set &quot;islocked&quot; flag as true, when other tries to update the same case if &quot;islocked&quot; is set to true dont show the related action or dont allow them to update the case.</p><div style="clear:both;"></div>