e-Profiles, Winter 2001-2002: What is Pro/INTRALINK® Branching?

Before implementing any type of branching process, there are Pro/ADMIN settings that make it easier to check objects out and get information. Setting up User Roles, Table Displays and Saved Searches in advance is critical for success.

User Roles. Pro/ADMIN, Roles offers the following options that apply specifically to branches:

Create Branch is a Folder Action that lets you create, in Commonspace, a branch name associated to an object or set of objects.

Set Branch is an Object Action that lets you set the branch in your Workspace after the branch name has been created in Commonspace for the objects to be set to the branch.

Forced check in to a different branch is an Object Action that lets you override check-in conflicts for object(s) being checked in to a branch other than the one currently set for the objects (e.g., an object currently at branch Main being checked in at branch Main/Option1).

Forced check in to the same branch is an Object Action that lets you override conflicts on objects being checked into the database. Note: Turning on this option is not recommended unless users are authorized to override check-in conflicts at any time.

Table Displays. Create a default global display for all users that filters to branch “main” (Fig. 2). Displays should include the column titled “branch.” Adding a filter for branch Main to this global display makes it easier for everyday users to find the proper file(s) to check out of Commonspace. This display needs to be set for the Commonspace Display window as well as the Locate Commonspace Objects window.

Figure 2.

Create a secondary global display that shows all branches for an object by displaying the branch column. This table display should be available to users creating branches and modifying objects that have been set to a branch other than Main.

Saved Searches. Create one saved search entitled “Name Search” for global use that has a wildcard for the file name, latest version and/or revision, and filters to branch Main. This allows all users to find the latest version of a file by its name and only those set to branch Main. Without this saved search, users will see all branch names for a given object—potentially causing confusion.

Figure 3.

Another saved search, called “Branch Search,” has branch as the only search option (Fig. 3). This lets users search for all objects set to a particular branch, making check outs easier. For example, assy1.asm and one of its components, part1.prt, have been set to branch Main/Concept1. If you search for assy1.asm, select it and perform a check out, you will check out the branch Main version of part1.prt. To check out both the assy1.asm and part1.prt objects that were set to branch Main/Concept1, you must do a search for branch Main/Concept1. Both assy1.asm and part1.prt will list in the Locate Commonspace Objects window. You need to select both objects before performing the check out.