You can only deploy files to, or roll back files from, a deployment area if the files are at the stage that owns the area or at any stage above it. For example, to deploy foo.c to a deployment area assigned to the SIT stage, foo.c must be at SIT or above. During failure recovery Dimensions may override this rule.
The Rollback command removes an item revision from an area and automatically redeploys the item revision that was there previously. For example, if you have revision 1.0 in an area, deploy revision 3.0, and then roll back revision 3.0, Dimensions CM redeploys revision 1.0 not revision 2.0. If no previous revision of the rolled back item was deployed to an area, the item revision is deleted. For example, if you deploy the first revision of an item and then roll it back, the revision is deleted from the area and not replaced with another revision.
You can only roll back a complete deployment operation. An operation is all items, request and baselines that were part of the original deployment to an area. To perform a rollback you must roll back all the objects that were part of the operation. You cannot break up a group and roll back individual objects.
If you have a privilege on a deployment area you can select or deselect it before you run the Deploy or Rollback commands.
If a Deploy command fails it backs out everything from the failed area and stops any further deployments.
If you deploy to multiple areas in parallel, not in sequence, and the deployment to one of these areas fails, the other deployments are not affected.
If a Rollback command fails it puts back into the area everything that it had tried to roll back.
If you share a deployment area with another project or stream, deploy a request (R1) to the area, and the other project then deploys a different request (R2), you cannot roll back the first request (R1) until the second request (R2) has been rolled back by the other project.
You can only roll back in the reverse deployment order. For example, you deploy requests in the following order: R1, R2, and R3. To roll back R1 you must first roll back R3, followed by R2, and then R1.
Item revisions, requests, and baselines in an off normal lifecycle state cannot be deployed or rolled back.
Note: Move on deploy is not supported in Dimensions CM 12.x and later.
All of the items in a deployment operation belong to a deployment change set. A deployment change set is then applied to a deployment area to create a new area version. An area version is therefore a delta of an area.