About Item Type Options

The Item Type Options are a group of settings that determine the behavior of a particular type of item. They are represented as check boxes that you check to enable them. You can set or unset them in the Options tab of the New/Copy/Edit Object Type dialog boxes. The options for item types are:

Option | Description
Allow Parallel Checkout | When set, users can check out different or the same revisions of an item in parallel provided that the project owning the item also has the Parallel Checkout option set. See About Project Type Options.
Require User Comment | When set, users must enter a comment concerning the reason for the item revision update before Dimensions will permit the item revision to be created, updated or checked in. This constraint applies when creating, updating, editing or checking in an item revision, or merging two item revisions.
Auto-generate Item Identifier | When set, an item identifier is generated automatically when an item is created. In this case Dimensions will generate a unique identifier. Note that the identifier will be automatically generated even if the user enters a value.
Enable Item Header Substitution | When set, item header substitution is enabled when users get a copy of an item or browse an item (but not when checking one out). For details on how to specify item header substitution variables, see the Dimensions CM online help.
Don't Force New Revision Number on Checkin | When set, either the originator or all users (determined by the Restrict previous Option to Originator check box) can overwrite an item at its initial lifecycle state without changing the revision. NOTE When a request is specified when checking out items, new revisions are always created.
Restrict previous Option to Originator | When the Don't Force new Revision Number on Checkin check box is selected, this check box can be set or unset to specify, respectively, that either all users or only the originator can perform such overwrites.
Compress Library File | When set, files will be stored in compressed form in the Dimensions item library. For details, see About Library File Compression. NOTE The compress storage option is not available for delta library storage.options:item types;item type:options CAUTION! It is strongly recommended that compression is not used for storing text items.
Check in only changed revisions | If set, when Dimensions receives a check in item request, it checks that the checksum for the item revision in the item library is different from its last value. This ensures that you cannot check in exactly the same item revision that was checked out; it forces you to change checked out item revisions before you check them in. NOTE This setting does not affect the web client. In the web client, this behavior can be achieved for all item types on a per-user basis in the Preferences dialog box by deselecting Check in for the If workfile unchanged option.
Enforce Primary Role Constraint | When set, the user can action an item to a new, non-terminal state only if a primary user exists for that lifecycle state. If primary role function is assigned to a user, then leader role function (described below) cannot be assigned to the same user i.e. primary role and leader role functions are mutually exclusive.
Enforce Leader Role Constraint | When set, the user can action an item to a new, non-terminal state only if at least one leader user exists for that lifecycle state. If leader role function is assigned to a user, then primary role function (described above) cannot be assigned to the same user i.e. leader role and primary role functions are mutually exclusive.
Use standard level numbering scheme for revisioning | Use the standard Dimensions Algorithm for determining the numbering of item revisions when a new branch is created. This means that the first revision of the first new branch of an item will have ".1.0" appended. For example, a new branch created from revision 2.1 would be 2.1.1.0 (if a named branch is not used) and the next revision in this new branch would be 2.1.1.1, etc. If this option is not set, the first revision in a new branch will have ".1" appended. For example, a new branch created from revision 2.1 would be 2.1.1 (if a named branch is not used) and the next revision in this new branch would be 2.1.2, etc.

Related Topics

Options Tab for Item Types

Editing an Object Type