Share this page

# Open projects and set defaults

In the web client, you can set a default project and define its preferences, such as the work area, design part, or branch. Set project options to determine versioning and deployment behavior, CM rules, and named branches.

In this topic:

## Set default project/stream

When you log in to the web client, the last project/stream you used opens automatically. You can open any Dimensions CM project/stream and set it as default.

To set project/stream as default:

1. In the My Current Project/Stream view, click Set Current Project/Stream on the toolbar. The Set Current Project/Stream dialog box opens.

2. To set a default project, verify that the project option is selected.

   To set a default stream, select the stream option.

3. (Optional) To limit the list of projects/streams, enter a keyword in the Filter field. For example, enter dev to match any project/stream that contains dev in its name.

4. Select a project/stream from the list.

5. Click OK.

Back to top

## Define project/stream default settings

You can set the defaults for each project or stream you open in the web client.

Dimensions CM can store the following preferences for previously opened projects/streams:

Work area | The location for items you update, modify, and deliver back to the repository.
Request | The request related as In Response To new item revisions created in the project/stream. For details about object relationships, see Link version and change management.
Design part | The design part that owns any new items created in the project/stream.
Branch | Projects only: The branch where new item revisions are created.
Library cache area | The area used to improve performance over wide area networks.

To define project/stream defaults:

1. In the status area at the bottom of the web client's window, click the settings icon next to the project name.

2. In the Set Project Default Settings dialog box, set the following options:

   Option | Description
   --- | ---
   Work area | To change the assigned work area, enter the path to the work area folder: If the folder is on your local machine, enter a full path, for example, c:\payroll. Note: Avoid setting the work area to the root folder of the drive on your machine, for example, C:\. If the folder is on a remote node, begin the path with the node name, followed by two colons (::), for example, HOST1::/payroll. To browse for a work area folder, click the browse button.
   Default request | Enter a request ID, or click the browse button to select a request. If you are using requests from multiple providers, specify the external request's ID in the following format: <requestProviderID>:<requestID> Example: Suppose you have an ALM Octane request provider with the ID OCTANE01. To set its user story US12345 as the default request, enter the following specification: OCTANE01:US12345 For details on how to find requests, see Select requests from different providers.
   Default design part | Enter the design part ID, or click the browse button to find one.
   Default branch | Enter a branch name, or select a branch from the list. Leave empty if you don't want to set a default branch.
   Optional library cache area | Select a library cache area from the list. This option is available only if at least one library cache area is defined for the project in the Administration Console.

3. Click OK.

Back to top

## Set default work area

When you set your current project/stream, you can define its default work area.

Note: You cannot set a web folder as a project work area.

To select a project work area:

1. In the status area at the bottom of the web client's window, click the Work Area name link.

2. In the Set Project Work Area dialog box, enter a path to the work area folder:

   If the folder is on your local machine | Enter a full path, for example, c:\payroll. Note: Avoid setting the work area to the root folder of the drive on your machine, for example, C:\.
   If the folder is on a remote node | Begin the path with the node name, followed by two colons (::). For example, to use the payroll folder on the HOST1 UNIX node, enter HOST1::/payroll.

   You can also click the browse button and navigate to the folder.

3. Click OK.

Back to top

## Set project options

Project options determine the default behavior of item revisions and files in a project.

Open a project to set its options. When you open a project, you can also view its details, such as the status, creation and last update date, or the user who last updated the project.

To set project options:

1. To set the options for your current project, open the My Current Project view, and click Open on the toolbar.

   To set the options for another project, open the Projects view, expand the appropriate node in the navigation pane, and click a project in the content pane.

   The Open Project dialog box opens, displaying general information about the project. The details are display only, except the stream ID that you can edit.

2. Select the Options tab.

3. Set version management options:

   Field | Description
   --- | ---
   Branch | Select this option to increment version numbers by adding a period before the new number. For example, if an item's revision number is 2, the item's first new revision in this project is 2.1, and the next one is 2.2. But for new items, the first revision number is 1, and the next one is 2.
   Do not branch | Select this option to increment version numbers by adding 1 to the previous revision number. For example, if an item's revision number is 2, the item's first new revision in this project is 3, and the next one is 4. If an item's revision number is 2.1, the first new revision is 2.2. Note: We recommend that you use this option and assign a single branch.
   Allow user to override default revision number | Select this option to allow users to change the automatically generated revision number when they create new item revisions.
   Lock project | Select this option to prevent users from making changes to items. Locking a project is particularly useful when creating a baseline, as it restricts users from updating the project while baselining is in progress. To lock or unlock a project, you need the Workset Manager or Project Manager role. Note: Workset Managers or Project Managers can deliver items to a project even if the project is locked. You cannot modify a locked project: No items or item revisions can be created. Project items cannot be deleted from the physical library or removed from the workset. Project items cannot be actioned or suspended. You cannot change the content of item revisions. But you can create a new revision to be included in another project, provided that the target project is not locked. Note: You can bypass these restrictions if you have the Override Process Checks privilege or the PRODUCT-MANAGER role.

4. Define the options for Change Management rules:

   Field | Description
   --- | ---
   Use item type settings | Select this option to make items follow the CM rules, as defined for their item type in the Administration Console.
   Always enabled | Select this option to make items behave as if the CM rules defined for their item types are enabled, regardless of whether they are enabled in the Administration Console.
   Always disabled | Select this option to make items behave as if the CM rules defined for their item types are disabled.
   Request required to refactor | Select this option to require users to specify a request ID when they make refactoring changes, such as moving or renaming items or project folders. Note: You cannot relate refactoring changes as In Response To a request if the request is above the initial stage in the Global Stage Lifecycle (GSL).

5. To specify how to handle item deployment, set the Promotion option:

   Field | Description
   --- | ---
   Use local stages | This deployment-related option determines whether the stage of item revisions in this project is affected by changes in other projects/streams. This option enables the following behavior: If Use local stages is selected, this preserves the stages of item revisions from changes caused by actioning. The stage of an item revision in this project remains unchanged when the same item revision in another project/stream is promoted/demoted to another stage. As a result, the same item revision can be at a different stage in different projects/streams. If Use local stages is cleared, then promoting/demoting an item revision in another project/stream to another stage changes the stage of the same item revision in this project. If an item's lifecycle states are mapped to stages in the Global Stage Lifecycle (GSL), then the stage of an item revision can also be changed when the item revision is actioned to those states. Note: After you select this option, you cannot clear it. If your project is using Deployment Automation, this option is always selected.

6. Specify branches assigned to this project:

   Field | Description
   --- | ---
   Named branches (checkboxes) | Select one or more valid branches to which future revisions in this project may be assigned.
   Default branch (radio buttons) | Select the default branch for item revisions in the project.

7. Click OK.

See also:

- About projects

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: