Examples of applications in which multiple users might concurrently access records include the Work Order Tracking application, the Problems application, the Incidents application, the Changes application, and the Activities and Tasks application.
When edit mode is enabled for an application but a record is not in edit mode, actions that update the underlying record are not available to the user. When the user places the record in edit mode, the actions become visible. An action that has a prerequisite of SAVE in Application Designer indicates that it might update the underlying record.
When a user selects records on an application's List tab and selects an action, the action does not run on records that are currently being edited by other users if the action causes an error. If the action will not cause an error, then the action takes place on the records in edit mode. For example, a user places a record in edit mode in the Item Master application. Another user selects that record on the application's List tab and selects the Add to Item Storeroom action while the first user is making changes on the Item tab. The action is allowed on the record as it does not cause an error for the first user.
The following actions release a record from edit mode:
If a user closes the browser without logging out, the record remains in edit mode until session times out. Starting a child application does not take the record out of edit mode, nor does saving the record.