Skip to main content
Feedback

Releases

Releases are how you build and deploy flows to an environment.

Releases allow you to easily build and deploy a collection of flows to your environments, and move them through the development life cycle.

  • Instead of publishing a Flow on the Flow canvas, build a Flow and choose which release to add it to. The release is automatically deployed to the development environment.

  • Once you have finished building and adding flows to a release in development, you can promote it to the test environment.

  • You can promote releases from development to testing, and from testing to production. Promoting a release into the production environment finalises the release, making it live and available to your users. You cannot remove flows from a production release.

  • Manage a release by navigating to the Environments section and selecting the specific environment.

    • Flow execution in an environment is always based on the latest deployment. When running a Flow in an environment, you always run the latest deployed Flow to that environment.

    • You must be signed into Flow to run a Flow in the development or test environments. Any user can run a Flow in the production environment.

    • You can remove flows from the release, promote it to the next environment, roll the release back, or delete the release completely.

Creating a release

Get started by creating and automatically deploying a release to the development environment.

Adding flows to a release

Build and add additional flows to a release.

Promoting a release

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

Rolling back a release

Rolling back a release redeploys the previous snapshot versions of any flows in the release to the environment, while simultaneously removing the current snapshot version of any flows in the release, rolling them back to the previous environment.

The Flow Run URL

The format of the Flow Run URL changes when using environments.

https://us.flow-prod.boomi.com/[Tenant ID]/play/[Player]/?flow-id=[Flow ID]&environment-id=[Environment ID]

  • The [Tenant ID] is the ID of the tenant that the Flow belongs to.

  • The [Player] is the name of the player that is used to render the Flow. This value can change, depending on which player is chosen when running the Flow.

  • The [Flow ID] is the ID of the Flow.

  • The [Environment ID] is the ID of the environment that the Flow is being run in. This is assigned automatically for each environment. This value can change, depending on which environment the Flow is being run in.

    If a Flow is launched without an Environment ID in the Run URL, the default environment is used. The production environment is set as the default, but you can make any environment the default. Refer to Environment settings.

On this Page