• Branch. When creating the first new revision of an existing item in a project, Dimensions CM adds a period before the revision number.

  For example, if the revision number of an existing item is 2, the first new revision in this project is 2.1, and the next one is 2.2.

  For a new item created in a project, the first revision number is 1, the next one is 2, and the one after next is 3.

• Do not Branch. When creating the first new revision of an existing item in a project, Dimensions CM 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 is 3, and the next one is 4. If the revision number of an existing item is 2.1, the first new revision is 2.2.

  We recommend that you use the Do not Branch option and have a single assigned branch.

• Forced . Does not allow to override the revision strings calculated automatically by Dimensions CM when you create a new item revision.

• Allow users to override default revision number. Allows you to override the default revision strings generated by Dimensions CM when 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: Users with the Workset Manager/Project Manager role can deliver items to a stream even when this option is set.

You cannot modify a locked project/stream, which means:

• No items or item revisions can be created in the workset.

• Items included in the project/stream cannot be deleted from the physical library or removed from the workset.

• Project/stream items cannot be actioned or suspended.

• You cannot alter the content of item revisions in the project/stream. But you can create a new revision, provided that the project/stream which will include the new revision is not locked.

Note: Users with the Override Process Checks privilege, or by default the special role PRODUCT-MANAGER, can 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 are 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 the 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: After you select this option, you cannot clear it. If your project is using Deployment Automation, this option is always selected.

• Use item type settings. Items in this project will obey the Change Management (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.

For details about the Change Management rules, see the Administration Console online help.

Selecting this option will require users to provide a request ID when they make 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.