As a blueprint developer, you can safely capture a snapshot of a working blueprint before risking further changes.

At deployment time, you can select any of your versions to deploy.

How to capture a blueprint version

From the design page, click Version, and provide a name.

The name must be alphanumeric, with no spaces, and only periods, hyphens, and underscores allowed as special characters.

How to restore an older version

From the design page, click Version History.

On the left, select an older version to inspect it in the canvas and code editor. When you find the version that you want, click Restore. Restoring overwrites the current draft without removing any named versions.

Blueprint version history

How to release a version to users of vRealize Automation Service Broker

From the design page, click Version History.

On the left, select a version and click Release. You cannot release the current draft until you version it.

When more than one version of a blueprint is released, vRealize Automation Service Broker uses the most recent one.

How to compare blueprint versions

When changes and versions accumulate, you might want to identify differences among them.

From the Version History view, select a version, and click Diff. Then, from the Diff against drop-down, select another version to compare to.

Note that you can toggle between reviewing code differences or visual topology differences.

Figure 1. Code Differences
Blueprint version code differences

Figure 2. Visual Topology Differences
Blueprint version visual differences

How to clone a blueprint

Although it's not the same as saving a version, from the design page, Actions > Clone makes a copy of the current blueprint for alternative development.