Managing single branches

When managing single branches, you can do the following: Control access to branch definitions. You can restricting the ability to create, modify, or delete branch definitions to identified users with access rules and Command Suppression. Access restrictions on branch definitions are honored during revision configuration, for example, unreadable content in branch definitions is not considered for revision configuration. Identify content for branch definitions. Identify item revisions for branch definitions. Available item revisions are listed in a pseudo folder under the branch definition. Duplicate item revisions in the same branch definition are not permitted. Mark branch definitions as active or inactive. By default, branch definitions are active at the time of creation. You can change the state of a branch definition to inactive at any time. If a branch is in an inactive state, no item revisions can be added to or obsoleted from it. Item revisions in a branch definition are considered during revision configuration, regardless of its state; the state of the branch does not affect any action on any of its item revisions. Add an item revision to a branch. You add an item revision to a branch definition by copying it, and then pasting it with a Branch Content relation. After the successful addition of the item revision to the branch, the start date on the Branch Content relation is set to the creation date of the relation. The item revision is effective in the branch definition from this start date onwards or until the end date if one is specified. Obsolete item revisions from a branch definition. To obsolete item revision from a branch definition, set an end date on the Branch Content relation. The item revision is effective in the branch definition from the start date to the specified end date. Delete branch definitions. You can only delete a branch definition if it is not referenced by a revision rule or by another branch definition.