Release Management

Release Management controls when a saved Workflow revision moves from one Site Environment to the next. It lets development continue in Test without automatically changing the revision deployed to a later Environment.

Enable Release Management

Open Settings, select Site settings, and set Release management mode to Enabled. Availability depends on the Tenant's subscription features.

Release Management is disabled by default because it adds lifecycle steps that simple or small integrations may not require. A Site can contain any number of Environments and by default includes a Test and a Production Environment.

When enabled, the first Environment is the editable Test Environment. Later Environments use the revision promoted to them and revisions cannot be saved directly to them.

Promote a Workflow

  1. Save and test the Workflow in Test.
  2. Open Manage releases in the Workflow designer.
  3. Confirm that the source Environment shows Published.
  4. Click Promote between it and the next Environment.
  5. Review the source and target names, then click Confirm.
  6. Repeat through each Environment in order.

Promotion publishes the selected revision to the target Environment.

Invocation behavior

When a Workfloow is invoked over HTTP, the intended Environment is determined by mapping the hostname that was used to the its Environment. Once the Environment is known, the runtime will load the revision of the Workflow that is currently at the head of that Environment (i.e. the Workflow version that was most recenrtly saved or promoted into that Environment).

A Sub-Workflow also runs the revision published in the same Environment as its caller.

The designer controls used to inspect and promote revisions are runtime-specific. Use the documentation for the Workflow's runtime.

See also