Before you use change sets to deploy a flow, understand the limits and behaviors that are
related to component dependencies, deployment, and flow triggers.
If you want to deploy a flow with a change set, the change set must include any component
the flow references.
When you view the dependent components for the change set, the Component Dependencies page
lists the dependencies for all versions of the flow. Add all interdependent components
for the relevant flow version to the outbound change set.
If a flow element references these components, the Component Dependencies page doesn’t
display that component. To deploy the flow successfully, manually add those referenced
components to the change set.
Post to Chatter
Send Email
Submit for Approval
For example, if you deploy a flow that includes a Submit for Approval element, manually
add the referenced approval process.
If a flow references a Lightning component that depends on a CSP Trusted Site, the trusted
site isn’t included in the package or change set.
Deploying Change Sets
You can include only one version of a flow in a change set.
An active flow in a change set is deployed to its destination as inactive. Manually activate
the flow after deployment.
If the flow has no active version when you upload the outbound change set, the latest
inactive version is used.
Deploying or redeploying a flow with a change set creates a version of the flow in the
destination Salesforce org.
In production orgs, you can enable the setting to deploy a new active version of a process
or flow using change sets or Metadata API. The setting doesn’t appear in non-production orgs
(such as scratch, sandbox, and developer orgs), because you can always deploy a new active
version.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
