Component locking
When component locking is turned on in your account and one user locks a component, other users cannot edit it unless they have the Administrator role.
Component locking is available to all accounts, but is not turned on by default. Account administrators can enable this option for their accounts by toggling the ON/OFF button and refreshing the page to see the changes.
Scenario example
If you work for a large company or enterprise with many users, you may have encountered the problem where multiple users inadvertently open and edit the same component at the same time. Because each user does not realize that the other is also editing the component, they make their changes independently. As a result, whichever user saves the component last “wins” and retains their changes, but the other user's changes are lost because they are overwritten.
To prevent this situation, you can enable component locking in your account. Every time a user opens any type of component, it opens on the Build page with a yellow banner indicating that it is in read-only mode.
Managing component locking
To ensure that only you can edit the component at any given time, you must click Lock & Edit. If another user attempts to lock and edit the component while you have it locked, one of the following occurs:
-
If the user does not have the Administrator role, a message is displayed, indicating that you have the component locked. You can refer to the component in read-only mode but cannot save changes to it until you save and close the component, which releases the lock.
-
Also, the user can acquire the lock from you to get access to change and save the component or can click Cancel and view the component in read-only mode. An administrator can acquire a locked component from another administrator.
- The component locking feature does not allow you to lock a component permanently.
- If you open a component and lock it for editing, it remains locked until you save and close it or until your session expires (you lose Internet connectivity).
- If you accidentally leaves a component locked, an administrator can acquire the lock on the component so that other users can edit it.
- If you accidentally exit the platform without saving a component that you were editing. In that case, you can log in again and attempt to lock and edit the component by acquiring the lock from your previous session.
Integration warns users if they try to save or lock an outdated revision of a component. The Component Lock Revision Options dialog opens. It displays all revisions of the component and highlights the currently open revision in yellow. Depending on your current situation, different options are available.
Scenario A: You open revision 1 of a component, lock it and start to edit. Meanwhile, an administrator acquires the lock, edits and saves it as revision 2. When you try to save revision 1, the dialog below opens. You have the following options:
-
Overwrite — Your changes are saved as revision 3. Revision 3 does not contain the changes that the administrator saved in revision 2.
-
Discard Changes and Reload Latest — Any changes that you made to revision 1 and did not save are lost. Revision 2 opens. If you edit and save the component, your changes are saved as revision 3. Revision 3 contains the administrator’s changes from revision 2 if you did not intentionally change or delete them.
Scenario B: You open revision 1 of a component. You do not lock it. Meanwhile, another user opens the component, locks, edits and saves it as revision 2. When you try to lock and edit the component, the dialog below opens. Revision 1 is selected. You have the following options:
-
Edit Selected Revision (1) — Revision 1 remains open. It does not contain the changes that the other user saved in revision 2. You can edit revision 1. If you edit and save the component, you see the Overwrite option. If you select Overwrite, your changes are saved as revision 3. Revision 3 does not contain the other user’s changes from revision 2.
-
Discard Changes and Reload Latest — Any changes that you made to revision 1 and did not save are lost. Revision 2 opens, containing the other user’s changes. You can edit revision 2. If you edit and save the component, you see the Overwrite option. If you select Overwrite, your changes are saved as revision 3. Revision 3 contains the other user’s changes from revision 2 if you did not intentionally change or delete them.