In the Project Policies Setting page you indicate the following:
For example, you can set a policy that requires developers to update their work areas with the project's latest recommended baseline before they deliver their work. This practice reduces the likelihood that developers will need to work through complex merge procedures when they deliver their work.
Be aware that, in addition to these, you can create your own policies by using triggers on UCM operations. A trigger is a monitor that causes one or more procedures or actions to be executed when a certain Rational® ClearCase® operation is performed.
Complete the Project Policies Setting page as follows:
Click the down arrow to reveal other readily available promotion levels: REJECTED, TESTED, BUILT, and RELEASED. Rational ClearCase lets you add your own, and remove any of the default ones. Make sure that INITIAL is selected before continuing the exercise.
The deliver tab. By default, all deliver policies are disabled.
For this exercise, enable the following policies:
The View tab. On this tab you specify which type of view, dynamic or snapshot, will be created by default the first time your developers join the UCM project using the Join Project Wizard.
The Access tab. On this tab you can specify who is allowed to modify the project and its streams.