3. The File Browser : Anchor: Preventing Files from Being Overwritten

Anchor: Preventing Files from Being Overwritten
The Anchor command makes the selected files active in the workspace (places them in the workspace’s default group), without modifying them. Anchor creates a new version in the workspace stream. This new version, called a virtual version, simply records the fact that the file is officially active in the workspace. See Real Versions and Virtual Versions for more information.
Typically, you anchor a file in your workspace to prevent it from being overwritten with a newer version by a subsequent Update command. (Update overwrites inactive files only, not active ones.) However, there are some situations in which you must anchor a file before editing it:
The Send to Workspace command is a variant of Anchor. Instead of activating the version that is currently in your workspace, Send to Workspace can activate any version of the element. See Send to Workspace for more information.
Invoking the Anchor Command
In the Details pane of the File Browser, select a file element whose current status is (backed). Then,
right-click and choose Anchor from the context menu.
In either of the must-anchor situations described above, if any element to be anchored is currently active in any sibling workspace, the Anchor dialog box appears, to help you complete the command.
Note: Anchoring an element link or symbolic link operates on the link itself.
Using the Anchor Dialog
When you anchor a set of elements in an anchor-required or exclusive file locking workspace, a dialog appears if one or more of them is active in a sibling workspace. This enables you to select/deselect individual elements to be anchored. Note that the elements that are active in the sibling workspace are initially deselected. This makes it easy to avoid the situation where multiple users are working on the same file(s) concurrently. The exclusive file locking feature guarantees that this situation won't occur

Micro Focus