The Anchor Command

The Anchor command makes the selected files active An element is said to be active in a workspace or stream if a new version of the element has been created there, and that version has not been either (1) promoted to the parent stream or (2) purged from the workspace or stream. See default group, backed, passive. An issue record is said to be active in a workspace or stream if the head version of one or more of its change package entries is in the stream's default group. in the workspace (places them in the workspace’s default group The set of elements that are currently active in a particular workspace or stream.), without modifying them. 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.)

Must-anchor situations: You must anchor a file before editing it if

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.

Invoking the Anchor Command

In the Details pane of the File Browser, select one or more file elements whose current status is (backed). Then, invoke the command in any of these ways:

In either of the must-anchor situations described above, if any element to be anchored is currently active in any sibling Two or more workspaces or streams that have the same parent stream. Pass-through streams 'don't count' -- that is, all workspaces that promote versions to the same stream are considered siblings, even if some of them are direct children of the stream, while others are children of an intervening pass-through stream. workspace, the Anchor dialog box appears, to help you complete the command.

Using the Anchor Dialog