You are here:
Considerations for Packaging Flows
You can include a flow in a managed or unmanaged package. Before you create, update, or deploy a package that contains a flow, understand the limitations and behaviors of packages.
Required Editions
| View supported editions. |
Creating Packages
- If you want to deploy a flow with a change set, the change set must include all components that the flow references.
- When you package a flow, all components and fields that the flow references must be available in the same package or a dependent package.
- If these elements are used in a flow, the packageable components that they reference aren’t
included in the package automatically. To deploy the package successfully, manually add the
referenced components to the package.
- Post to Chatter
- Send Email
- Submit for Approval
- If a flow references a Lightning component that depends on a CSP Trusted Site, the trusted site isn’t included in the package automatically.
- When you upload a package or package version, the active flow version is included. If the flow doesn’t have an active version, the latest version is packaged.
Updating Packages
- To update a managed package with a different flow version, activate that version and upload the package. Or, deactivate all versions of the flow, make sure that the latest flow version is the one to distribute, and then upload the package. If you activate a flow version by mistake and upload the package, that flow version is distributed to everyone.
- If you install a flow from an unlocked package with the same API name, the new flow overrides the existing flow in the target org.
- You can’t include flows in package patches.
Other Considerations
- Flow Builder displays Apex actions from managed packages only if the associated method is marked global.
- Flow Builder displays email alerts from managed packages only if the email alert isn’t protected.
- If you register your namespace after you reference a flow in a Visualforce page or Apex code, add the namespace to the flow name before you install the package.
- If a flow is installed from a managed package, error emails for that flow’s interviews don’t include details about the individual flow elements. The email is sent to either the user who installed the flow or the Apex exception email recipients.
- You can’t package flow triggers.
- In a packaging org, you can’t delete a flow after you upload it
to a released or beta first generation managed package. You can delete a flow version from
a packaging org after you upload it to a released or beta first-generation managed
package, if all these criteria are met:
- Salesforce Customer Support activated the Managed Component Deletion permission.
- The flow version isn’t the most recently packaged version of the flow.
- The flow version isn’t active.
- The flow version is not the only version.
- Images in rich text for screens aren’t supported in packages.
Did this article solve your issue?
Let us know so we can improve!
