Share this page

# New Object Type dialog box

In the New Object Type dialog box, create a new type of item, request, design part, baseline, or project. For items, requests, and projects, you can set additional options that define the rules and behavior of the object type.

In this topic:

## New Object Type: General tab

On the General tab of the New Object Type dialog box, provide the following object type details:

Field | Description
--- | ---
Product | (Display only) Specifies the product to which this object type belongs. By default, the current product is selected.
Class | (Display only) Specifies the object for which you are creating the new type.
Name | Enter a unique name for the object type. Use up to 10 characters for item types and up to 25 characters for other object types.
Lifecycle | (Optional) Select a lifecycle to associate with the object type. For design parts, the lifecycle is set to LC_PART and cannot be changed.
Description | Enter a description for the object type, up to 240 characters long.
What is the closest functional match for this type? | Items and requests only: Define the purpose for which you intend to use the item or request type. Based on your selection, Dimensions CM sets the defaults on the Options tab.

Back to top

## New Object Type: Options tab for items

For item types, set additional options on the Options tab of the New Object Type dialog box. The default selection is based on the Closest Functional Match option you defined on the General tab.

For an overview of these options, see Item type options.

Option | Description
--- | ---
Allow Parallel Checkout | Allows to check out different revisions of an item in parallel.
Require User Comment | Makes a user comment required when items are created and checked in.
Auto-generate Item Identifier | When creating a new item, automatically generates an item identifier.
Enable Item Header Substitution | When getting or browsing items, enables the Dimensions CM item header substitution facility.
Don't Force New Revision Number on Check-in | Allows to update the content of the item that is at the initial lifecycle state without changing the revision. If a request is specified when checking out items, Dimensions CM always creates new revisions.
Restrict previous Option to Originator | If the update at the initial lifecycle state is enabled, restricts the permission to update. Only the user who created the item can update it.
Compress Library File | Compresses files when storing them in the Dimensions CM item library.
Check in only changed revisions | Doesn't allow the same item revision that was checked out to be checked back 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 | To action an item to a non-terminal state, requires a user with the Primary role to exist.
Enforce Leader Role Constraint | To action an item to a non-terminal state, requires a user with the Leader role to exist.
Use standard level numbering scheme for revisioning | Enables the use of the standard Dimensions Algorithm for determining the numbering of item revisions when a new branch is created.

Back to top

## New Object Type: Options tab for requests

For request types, set additional options on the Options tab of the New Object Type dialog box. The default selection is based on the Closest Functional Match option you defined on the General tab.

For an overview of these options, see Request type options.

Option | Description
--- | ---
Create Requires Role | Ensures that only users with the Create Request privilege can create requests. By default, this means that they require a role on the product to have this privilege. Note: Users can be granted the Create privilege for requests under general grant rules, Grant to all users.
Save History | Saves request attribute and action description history when actioning to a new state.
Notify Originator on Close | Sends an email notification to the originator when the request is closed.
Enforce Primary Role Constraint | To action a request to a non-terminal state, requires a user with the Primary role to exist.
Enforce Leader Role Constraint | To action a request to a non-terminal state, requires a user with the Leader role to exist.
Take roles from all affected design parts | Determines roles on a request of this type by including the role assignments on all the design parts to which it is related. When this option is cleared, role assignments are taken only from the common ancestor design part for all the related design parts.
Disabled request type | Restricts the creation of any new requests of this type.

Back to top

## New Object Type: Options tab for projects

For project types, set additional options on the Options tab of the New Object Type dialog box.

For an overview of these options, see Project type options.

Note: These are the default settings for a new project type. You can change the defaults. For streams (projects of type STREAM) some options are dimmed and cannot be changed.

Field | Description
--- | ---
Project is trunk | Treats the project as a trunk. Clear this option to treat the project as a branch. For streams, this option is cleared and cannot be changed.
Automatic revision generation | Generates revision strings automatically. Clear this option to enforce that the user supplies a revision ID. For streams, this option is selected and cannot be changed.
Parallel check out | Allows an item revision to be checked out by multiple users at a time. For streams, this option is cleared and cannot be changed.
Use local stages | Determines whether the stage of item revisions is "local" to this project/stream or can be affected by changes in other projects/streams. (The same item revision could be at a different stage in different projects/streams.) By default, an item revision's stage in this project/stream is not affected when the same item revision is promoted/demoted to another stage as a result of activities in another project/stream. Clear this option to update the stage of an item revision in a project/stream when that item revision in the project/stream is promoted/demoted to another stage. Note: The stage of an item revision can also be changed when it is actioned if its lifecycle states have been mapped to stages in the GSL.
Always disable CM Rules | Select this option if you want the CM rules option for items in this type of project to be set to Always disabled by default when the project is created (but you can override this). When this option is set for a specific project, item operations in that project act as if CM Rules were not enabled for any item types or request types.
Always enable CM Rules | Select this option if you want the CM rules option for items in this type of project to be set to Always enabled by default when the project is created (but you can override this). When this option is set for a specific project, item operations in that project act as if CM Rules were enabled for all item types and request types. For details, see Object Types content area.
Require change control when refactoring | When set, a project of this type has the option Request required to refactor set by default when it is created. When this option is set, the user is required to provide a request ID when making any refactoring changes to the project, such as moving or renaming items or project folders.

Back to top

See also:

- Object type definitions

https://admhelp.microfocus.com Dimensions CM 8942
Tips to improve your search results... Dimensions CM Help Center CM Help 14.7 All View Local Help Center View Online Help Center Version: