Use actioning to deploy objects

In Dimensions CM you can map lifecycle states to stages in the GSL. If this mapping is set up, when you action an object to a lifecycle state that is mapped to a stage, it is automatically promoted to, or demoted from, that stage.

If the Deploy by Default option is selected for the deployment areas attached to the stage, the object is also automatically deployed to, or rolled back from, the areas.

In this example some of the states in the request lifecycle are mapped to stages in a GSL:


For example:

  • When a request is actioned up, the request lifecycle from the Under Work state to In Test it is automatically promoted from DEV to SIT.

  • When a request is actioned down, the request lifecycle from the Ready for QA state to In Test it is automatically demoted from QA to SIT.

Guidelines and behaviors:

  • You can use action-driven deployment with items, requests, and baselines.

  • For action-driven deployment to work, you need the privileges to action and promote to stages and areas.

  • Actioning an object to an off-normal state removes item revisions from the associated stage.

  • You map lifecycle states to the GSL in the Lifecycles section of the Dimensions CM Administration Console.

  • When you use action-driven deployment to promote or demote an item revision to another stage, the operation is applied globally to the same item revision across all projects in the current product.

    If you select the Use local stages option in a project/stream, the stage of the item revision in that project is not affected when the same item revision is promoted/demoted in any other project/stream. This way, the same item revision can be at different stages in each project/stream.

    After you have selected the Use local stages option for a project/stream, you cannot change it.

Back to top

See also: