Branch Projects

Branching

Aligned Elements projects can be branched from the Project Hierarchy view, in order to create an independent line of the documentation.

When triggering a branch from the Action dropdown menu, a new Aligned Elements Project will be created. The user must select the types of Document Objects that shall be copied from the origin to the branch project. The branch project will then contain the latest revisions of Document Objects of the selected Document Object types.

Note that if a type is not selected for Branching, the ID counter for that type is not reset for the Branch project.

For example, if

1) Four User Needs exist in the Origin project and

2) the Origin project is Branched and

3) the user selects to not include the User Needs in the Branch (resulting in an empty User Need section in the Branched project)

4) the user creates a new User Need in the Branch, it will receive ID 5 (UN 5) and not 1 (UN 1)

This is done in order for the trace integrity between then Branched and Origin project to remain intact.

At branching, Project History events are added to both the origin and the branch projects to record the branch action. The branch project will indicate the name of the origin project in the lower left corner of the application.

Note that the following restrictions apply when branching a project. The branch project will not contain the following elements from the origin project:

• Test Runs

• Signatures

• Snapshots

• Old Revisions of Document Objects