Manage flow versions

Occasionally, when you're working with complex cloud flows, you might not be able to complete the edition of the flow but might want to store it as it is. Other situations might also require you to modify an existing flow but not interfere with the live version of the flow that might be running. You can address these challenges by saving a draft version of a solution-aware cloud flow.

The solution designer has three actions that you can use to manage flow versions:

• Flow history (1) - Review the different versions of the flow.

• Save draft (2) - Keep a copy of the current flow without publishing it.

• Publish (3) - Release the current copy of the flow as the live one.

  

When a draft version of a flow is ready to release, you can publish it. The publishing process creates a new live version of the flow that the system adds to the version history. You can also bring back an older published version of a solution-aware cloud flow with the Restore capability that's available from the version history when you select that older version of the flow.

You can view the version history in the solution designer, which groups versions by date, from the most recent version to older versions. Each version is tagged based on its status:

• Latest version - Current version that's visible in the editor by default.
• Published - Current version that's available for other users and considered the live version of the flow.
• Past published - Previously published versions.

Other versions with no tags represent flow versions that are saved as drafts.

When you export a solution, the system includes the last published version. Any draft version remains in the original environment’s solution. If you choose to publish all changes while exporting the solution, the system publishes the draft versions of cloud flows as live versions.

Next steps

Now you've learned how to manage flow versions. Next, you apply your learned knowledge to create and test a solution-aware cloud flow.