Project/Version filter

When defining a View based on a Project/Version filter, you are presented with a list of all Projects in the current repository and all Version Labels that have been assigned to these projects. Defining the filter is simply a case of checking the projects to be included and which version of these projects to view:

Note that, with Views based on a Version Label, there is no requirement to select a Version Label. In this case, the filter will default to the tip revision of files in the selected projects.

Making a Project/Version View the current view will force Team Coherence to carry out all actions on that particular version of the files in the selected projects. When viewing files in Version Manager, only files that match the View settings will be displayed, and only revisions up to and including that Version Label will be displayed.

Additionally, all folder working paths are specific to that View. Changing the default working path for a folder while a view is active changes it only for that View. In this way, you can work on different versions of a project simultaneously by keeping the working source for each version in a different location.

When a view is active, check out actions will automatically insert the Version Label that the view is based on in the Check Out dialog box. When checking in modified files, the Version Label will be added to the Check In dialog box, and the Move existing version label to new revision checkbox will be checked to make sure that the new revision is included in the view.

From version 7.1.2.98, Version Labels can be associated with a Branch Base Label to improve automatic branching functionality. If a Version Label with an associated Branch Base Label is used in a View, branching is automatically applied from the point where the Label and its associated Branch Base Label are attached to the same revision. This ensures that changes made to a previous version of the software do not overlap (i.e. where the relevant version of the file is both the version being modified and the current tip revision in the <development> View).

For more information on Views, and working with multiple versions, check out the Scenarios section of this manual.

If a user selects a View based on a Version Label that they do not have Assign access to, the View will be read-only and the user will not be able to check files in or out.