Promoting a release to the next environment

Prerequisites

• You have created a release and added Flows to it. Refer to Adding a Flow to a release.
• You have at least two environments configured in your MCR.

Promote a release to deploy it to the next environment in the development life cycle.

For example:

• Once you have finished building the release in the development environment, you can promote the release to the test environment and test the Flows in the release.
• Once you have tested the release and it is ready to go live, you can promote it to the production environment.

You can only promote a release forward to the next environment. You must roll it back to undo and remove a release from the current environment. For more information, refer to Rolling back a release.

After creating a release, promote it to the test environment by following these steps:

1. Navigate to the Environments page.

2. Locate the release you created that is automatically deployed to the Development environment.

3. Expand the release details and click Promote to Test.

4. System checks for MCR nodes.

   • If the target environment has an MCR node configured, the system notifies that node to download and deploy the release.

   • If you have associated multiple nodes, the system notifies each node in sequence.

   • If you have not configured an MCR node for the environment, the system deploys the release to the cloud runtime by default.

5. The Flow design-time modal waits for a success message from the MCR node.

   • On success, you will view the Promote release successful message.

   • On failure, the screen returns an error notification at the bottom right of the screen.