You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

 On this page:


Project branching enables multiple users to work on the same model at the same time. To do this, you need to create a project branch which is a copy of the project. You can modify the branch as required, independently of other branches. Branches can be merged back together when required. Conflicts between the branches are resolved during the merge process.

Understanding project branching

To understand how project branching works, you should be familiar with the following terms:

  • Iteration - the smallest possible milestone of the project development. In other words, it is a project version you can open and review created after committing the project to the 3DEXPERIENCE platform. Iterations are labeled by numbers in ascending order starting from 0 (zero).
  • Revision -  a larger project development milestone consisting of one or several iterations. Revisions are labeled by letters from A to Z. Note that iterations of different revisions within a branch are numbered independently as shown below.
  • Branch - a copy of a project made at a certain point of the project development. Branches are labeled by numbers in ascending order starting from 1 (branch 1 is the root project). Each project branch can be developed independently and later merged with another branch. Every project branch consists of one or several revisions. Revisions of different project branches are labeled independently as shown below.
Since iterations of different project branches are not unique, a combination of a branch, revision, and iteration is used to define a certain iteration. A unique project iteration is labeled in the following format: [branch] revision.iteration. For example iteration 4 of revision B of branch 3 would be labeled as [3] B.4. You can see the iteration of an open project in the header of the modeling tool window next to the project name.


Project branching in the 3DEXPERIENCE platform.

Creating revisions and branches

You can create new branches and revisions from any revision of any branch of a project. There is no limit to the number of branches and revisions you can create.


To create a project branch or revision

  1. In the main menu, select Collaborate > Projects. The Manage Projects dialog opens.
  2. Do one of the following:
    1. Select the project you want to branch and click  in the dialog toolbar.
    2. Click  next to the project you want to branch.
  3. In the Select Revision dialog, click the Edit Branches button.

  4. Expand project branches in the open dialog and select the revision from which you want to create another revision or branch.

    Revisions and branches can be created only from the latest iteration of the selected revision. The revision and branch creation buttons will be inactive if you select any other iteration of a revision.

  5. Do one of the following:
    1. Click the Create Revision button to create a revision from the selected revision.
    2. Click the Create Branch button to create a branch from the selected revision.


      If a specific iteration was merged, the Iteration column of the Edit Branches dialog shows the source iteration from which it was merged, e.g., (merged from 2.A (2)).


After completing the above steps, a revision or branch is created and displayed in the Edit Branches dialog. New revisions and branches are named automatically following the rules described in Understanding project branching. In addition, a created revision or the first revision of a created branch holds information about the iteration it was created from. This information is displayed between brackets next to the name of a new revision.