If you have the appropriate privilege on an area you can choose which default deployment areas of the target (demote to) stage are populated.
If the deployment area list is empty and no deployment operation has been requested, no deployment areas will be updated on the target stage during demotion.
A demote operation will fail if any of the files are deployed to non-default areas. Under the stage being demoted from you must manually roll back those files before you can run the Demote command again.
If a rollback from any development areas in the source stage fails, the demotion from the source stage does not complete.
Demote automatically rolls back files in any deploy by default areas.
When you select a deployment area it must be at the same stage that you are demoting to. For example, if you are demoting from the QA stage to SIT, any area that you select must be attached to the SIT stage. If you select an area that is not at the same stage, an error message is displayed.
You do not require any privilege to roll back from default deployment areas as this privilege is implicit (permission is given automatically if you have the privilege to roll back from the source stage).
You do not require any privilege to deploy to default deployment areas as this privilege is implicit (permission is given automatically if you have the privilege to deploy to the target stage).
You do require a privilege to deploy to non-default deployment areas as this privilege is explicit. Because the area is not a default area you must be granted the privilege on that area before you can deploy to it.
If a roll back and a demotion succeeds but the deployment then fails, a warning is displayed (only the rollback and demote operations are atomic).
If you by-pass stages during a demotion, all default deployment areas in all by-passed stages are rolled back automatically. For example, there are default deployment areas attached to the DEV and SIT stages. You demote from the QA stage straight to DEV by-passing the SIT stage. Both the QA and the SIT default deployment areas are automatically rolled back. The Demote commands are run one at a time. If an intermediate demotion fails, any preceding successful demotions cannot be recovered. All the Demote with Rollback rules above must apply for this rule to be successful.
A demote will fail if the objects are deployed to a deployment area where deploy by default is not enabled. You must first roll back the objects manually.
When you rollback from a higher stage, deployment to the lower stage that you are demoting to is optional.
TIP If you have configuration files that you deploy to areas and then edit, keep them separate from your source code. For example, if you do a rollback but the rollback fails, area recovery will reinstate the previous version of the area and the configuration files will also be rolled back to their previous state. This may affect the content of the files.