Overview
This guide describes how Workflows behave across environments, after the migration to organization-level Workflows in early 2023.
Prepare for migration to organization-level Workflows
To learn how to prepare for the migration from environment-level to organization-level Workflows, see Migration to organization-level Workflows.
Am I using organization-level Workflows?
Here is one way to check:
- Open any Workflow in the Workflow Editor.
- Click the “config” icon at the upper right corner of the Editor canvas.
- In the config modal, check whether you see an Environments section under Configurations.
- If you see an Environments section, you are using organization-level Workflows.
- If you do not see an Environments section, you are using environment-level Workflows.
Key concepts
Workflow spans all environments
An organization-level Workflow exists in and can be used in all environments in your Persona organization. For example, if your organization has one Sandbox environment and one Production environment, a single organization-level Workflow can be edited and used in both your Sandbox and Production environments.
In contrast, an environment-level Workflow exists in and can be used in only one environment in your Persona organization. For example, if your organization has one Sandbox environment and one Production environment, a single legacy Workflow could exist either in Sandbox, or in Production, but not both.
An environment is a runtime for Persona. Environments come in two types: Sandbox‚ which is useful for testing; and Production. To learn more about these types, see Sandbox vs. Production Environments.
Publish creates new version across all environments
An organization-level Workflow has one version history across all environments.
Publishing a new version of a Workflow publishes a new version to all environments. It is currently not possible to publish a new version of a Workflow to only some environments.
Set a Workflow state for each environment
An organization-level Workflow can have a different state in each environment. For example, an organization-level Workflow can be active in a Sandbox environment while it is inactive in a Production environment.
To learn more about Workflow states, see Workflows: Manage versions and state.
FAQ
Can I run one Workflow version in one environment, and run a different version of the Workflow in another environment at the same time?
No. Currently, the new version of a Workflow must be published to all environments at the same time.
Note that you can set a different state for each environment when you publish a new version. For example, you can have Sandbox set to active—so that the new version begins to run in Sandbox, and Production set to inactive—so that the Workflow does not run at all in Production.
How does staging a roll-out work for an organization-level Workflow?
Staging a roll-out will deploy the new version to all environments at your chosen percentage.
For example, if you have a Sandbox environment and a Production environment, and you stage a roll-out of a new version at 50%, then the new Workflow will be rolled out to 50% in your Sandbox environment and 50% in your Production environment.
Note that you can set a different state for each environment during a rollout. For example, you can have Sandbox set to active—so that the new version begins to run alongside the previous version in Sandbox, and Production set to inactive—so that the Workflow does not run at all in Production.