Creating and Configuring Views
This topic describes procedures for creating and configuring various types of Views.
Creating a New View
To create a new view based upon an existing view, do the following:
- Display the project view upon which the new view will be based.
-
Choose View > New.
The New View Wizard opens.
-
Select one of the available options from the View Type list:
Branch All Will be based on a configuration of the currently open view. All items in the new view will be set to branch when they are modified. This branch behavior can be changed later for individual items in the new view so that changed items do not branch. Reference Allows users to read from and write to a subset of the parent view's current configuration. Any changes appear in both the reference view and its parent. Lightweight Activity View will be based on the current configuration of the currently open view. All file and folder items in the new view will be shared down on demand and set to branch when they are modified. Project should have "Create workspace change package" option enforced to be able to create lightweight activity views. Skip steps 5 to 9.
Read-only Reference Allows users to read from a subset of the parent view. Unlike a read-write reference view, the contents of a read-only reference view may be current (floating) or configured to a point in the parent view's past by specifying a label, promotion state, or time. - Type a Name and a Description for the view in the appropriate fields and click Next.
- Select the
Root Folder for the new view and click
Next.
Note: The New View Wizard skips this step for a Non-Derived view.
-
Type or browse for the name of an appropriate Default Working Folder.
Caution: For a Branch All or a Non-Derived view, always use a working folder that is different from the one used by the parent view. Using the same working folder for the parent and child views can cause changes in one view to be overwritten when files are checked out from the other view. It can also result in incorrect or, at least, misleading file status indicators. For a Reference or Read-Only Reference view, you can use the same working folder as the parent view.
- Click Next to display the Select Types page.
- Select the item types to include in the new view. The new view will include items of the selected types from the parent view, unless the
Override default types option has been selected in the
View Access Rights dialog box.
Tip: To create a view with no shared items, use the Branch All view type and clear all the check boxes on the Select Types page.
-
Click Next to display the Configuration page.
If you are creating a Non-derived or Reference view, click Finish.
Note: It is not necessary to display the Configuration page for a Non-Derived view because no items from the parent view are included. It is also not necessary to display the Configuration page for a Reference view because the items have the same configuration as those in the parent view.
- Select one of the available configuration options on the Configuration page.
- Click Finish.
View Configuration Options
The following table describes the view configuration options available in the New View Wizard.
Floating Configuration | Not recommended. All the items in the new view will be identical to the corresponding items in the current parent view. Changes to an item in the parent view will be made to the corresponding item in the new view until that item branches, while changes to an item in the new view will be reflected in the parent until the item in the new view branches. (In many cases, the first change to that item will result in branching). New items in the parent view will appear in a branching view. However, new items added to a branching view will appear in the parent view only if the new view is the
Branch none type.
|
Labeled Configuration | All the items in the new view will have had the specified label in the parent view. In all cases, the revision of the item to which the label was attached is the tip revision in the new view. This option is disabled if the parent view has no view labels. Changes to the parent view do not affect the new view, including changes to the label upon which the view is based. Unless an item is set to
Branch on change in the new view, it will be read-only and you cannot change it.
|
Promotion State Configuration | All the items in the new view will have been part of the specified promotion state in the parent view. In all cases, the revision of the item that was part of the promotion state is the tip revision in the new view. This option is disabled if the parent view has no promotion states defined for it. Changes to the parent view will not affect the new view, including changes to the promotion state or its assigned label. Unless a specific item is set to
Branch on change in the new reference view, it will be read-only and you cannot change it.
|
Configuration As Of | The new view will contain only the items that existed at the date and time you specify. In all cases, the tip revision of each item in the new view is the revision closest to, but before, the specified time. Changes to the parent view will not affect the new view. Unless a specific item is set to
Branch on change in the new view, it will be read-only and you cannot change it.
|
View Type Options and Settings
The following table below lists the settings that must be selected in the New View Wizard to create the different views.
Desired Characteristics for New View | Options to Set | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Branching: Branch All (Not Floating)
|
|
||||||||||||||
Read-only Reference View (Frozen)
|
These views can be rolled back. |
||||||||||||||
Non-derived View (also called Blank Branching View)
|
|
||||||||||||||
Reference View (Also called Read/Write Reference View)
Note: Labels created and objects deleted in the child view appear and disappear in the parent view; this is not true for other types of child views. |
|
||||||||||||||
Lightweight Activity View
|
|
||||||||||||||
Branching: Branch None (Not Floating). Not recommended.
No change to a child item that can branch results in branching until the Branch on Change check box is selected. After branching, the box is disabled. |
Note: Addressed In Build field when the child view is created,
|
||||||||||||||
Branching: Branch None (Floating). Not recommended. Use only when a different set of view labels is needed for the same data.
No change to a child item that can branch results in branching until the Branch on Change check box is selected. After branching, the check box is disabled. |
See the note below. |
||||||||||||||
Branching: Branch All (Floating). Not recommended.
Any change to a child item that can branch results in the branching of that item, unless its Branch on Change check box has been cleared. After branching, the box is disabled. |
See the note below. |
||||||||||||||
Branching: Branch All (Floating)
Any change to a child item that can branch results in the branching of that item, unless its Branch on Change check box has been cleared. After branching, the box is disabled. |
See the note below. |
Note: If users are likely to perform many move and share operations, using branching, floating views can result in multiple unwanted references to the same folders or items, causing confusion. Also, if a change request has
Next Build
in the