View configuration
Specify various configuration parameters for the view
After you specify options for the view, the view is created and the Edit Configuration dialog is displayed
Controls in the dialog box
Some of the controls in the Edit configuration dialog box are applicable only to certain types of view. Further, some controls are specific to the view's configuration management model (Base ClearCase® or UCM).
Applicability | Control name | Control description |
---|---|---|
All view types | Version Selection Rules (Base ClearCase) | Enables you to edit the rules for selecting element versions. For complete information on version selection rules, refer to the config_spec reference page. |
UCM Custom Rules (UCM) | Displays non-UCM rules that can be included in the UCM config spec if access to VOBs in Base ClearCase mode is required. | |
Copy rules | Enables you to create a view configuration by copying the configuration of another view. | |
Web, automatic, and snapshot views | Load rules | Specifies the directories and files that are
to be copied into the view. Load rules for web and snapshot views Load rules are required for web and snapshot views. Load rules for automatic views Load rules are optional for automatic views because directories and files are loaded when you browse them. However, in an automatic view, load rules are useful for
To add a load rule to an automatic view, the element that
is to be loaded must be selected by a version-selection rule before
you set a new config spec that includes the new load rule. To add
a load rule for an element that is not selected by the view, edit
the config spec as follows:
Config specs for automatic views do not support "nested" load rules:
The first rule loads all subdirectories and files in /vob1/dir1. The second and third "nested" rules are redundant; however, their presence in this context results in an error. Always set the pathname for a load rule to the directory that encompasses all needed files and directories. To expand the scope of a load rule to include the parent of the currently specified pathname, do not add another load rule for the parent directory; instead, replace the current rules with a rule that specifies the parent. For example, in the config spec that is shown above, you would delete these two rules:
such that the config spec would show only this load rule:
|
Web and snapshot views | Update options | Enables you to specify how hijacks are to be handled. |
Automatic views | Mount VOBs | Displays a list of VOBs that can be mounted.
Mount all VOBs that contain element versions that you need to access
from this view. (Note: mounting a VOB in one automatic view does not
make it available to your other automatic views on the same client
machine: every automatic view must specify the VOBs that are to be
mounted.) VOBs are also mounted implicitly
|
Select all project component VOBs (UCM) | Selects the UCM project component VOBs for mounting. | |
Shared cleartext cache location | Specifies local storage for cleartext for files that are accessed from automatic views. Specify the same cache directory for all of your automatic views that reside on the same client machine and that access the same VOB content. The automatic view that is the first to access a file that has not yet been fetched obtains it from the VOB. When another automatic view accesses that file, it obtains it from local shared storage (which is more efficient than fetching the same file from the VOB). Default : user_home_directory\.ccase_automatic_cltxt_stg | |
Snapshot views | Use current time, Preserve version creation time | Version modification time can be set to checkin time (Use current time) or to the time that the version was created (Preserve version creation time). |