A project has various options that determine the default behavior in relation to its item revisions and files.
The project options are:
Project type:
Branch: When creating the first new revision in this project for an existing item, Dimensions adds a period before the new revision number. For example, if the revision number of an existing item is 2, the first new revision in this project will be 2.1, and the next, 2.2 etc. (The first revision number of a new item created in this project however, will be 1, and the next, 2 etc.)
Do not Branch: When creating the first new revision in this project for an existing item, Dimensions increments the last number by 1. For example, if the revision number of an existing item is 2, the first new revision in this project will be 3, and the next, 4, etc. If the revision number of an existing item is 2.1 the first new revision in this project will be 2.2, etc.
It is recommended that you use this option, and that you use a single assigned branch.
Forced: does not allow you to override the revision strings calculated automatically by Dimensions CM when you create a new item revision.
Optional (Allow users to override default revision number): allows you to override the default revision strings generated by Dimensions CMwhen you create a new item revision.
Locked: Prevents user changes to items in a project while this option is set.
Unlocked: Permits operations on items in a project.
By default the Workset Manager or Project Manager is able to lock or unlock a project or stream. Locking a project/stream is particularly useful when creating a baseline as this will prevent the ordinary user from updating the project/stream when baselining is in progress.
NOTE It will still be possible for a user with the Workset Manager/Project Manager role to deliver items to a stream even when this option is set.
A locked project/stream is not editable, meaning:
No new item or item revisions can be created in the workset.
None of the items included in the project/stream can be deleted from the physical library or removed from the workset.
None of the items in the project/stream can be actioned or suspended.
No user is allowed to alter the content of an item revision in the project/stream. The user, however, is allowed to create a new revision provided that the project/stream which is to include the new revision is not locked.
Note that users with the Override Process Checks privilege, or by default the special role PRODUCT-MANAGER, will be allowed to bypass the above restrictions.
This deployment-related option determines whether the stage of item revisions is "local" to this project/stream or can be affected by changes in other projects/streams. If its lifecycle states have been mapped to stages in the GSL, then the stage of an item revision will be changed when it is actioned to those states. Setting Use local stages for a project/stream preserves the stages of item revisions in that project/stream from changes as a result of actioning. (Note that this means that the same item revision could be at different stages in different projects/streams.)
If you select this option, the stage of an item revision in this project/stream is not affected as a result of actioning even when stages in the GSL are associated with states in its lifecycle. The stage in this project/stream can only be changed as a result of promoting and demoting.
If you do not select this option, then when the state of an item revision is changed as a result of actioning, its stage in this project/stream will also be changed.
NOTE Once you have selected this option for a project or stream, you cannot subsequently deselect it.
Use item type settings: Items in this project will obey the CM rules as defined for their item types.
Always enabled: Items in this project will behave as if the CM rules defined for their item types are all enabled regardless of whether they are enabled in the Administration Console.
Always disabled: Items in this project will behave as if the CM rules defined for their item types are all disabled, regardless of whether they are enabled in the Administration Console.
CM Rules are described in About Change Management Rules in the Process Configuration Guide.
Request required to refactor: If this option is selected, the user will be required to provide a request ID when making any refactoring changes to the project, such as moving or renaming items or project folders.
NOTE You cannot relate refactoring changes in response to a request if the request is above the initial stage in the Global Stage Lifecycle.
Assigned Branches: The list of valid branches that can be assigned to new item revisions in the project. Streams can only have one assigned branch.
Default branch: The branch that is used as the default for new item revisions in the project.
These options can be set when you first create a new project, and you can change them when editing the project properties.
Related Topics