You are here:
Considerations for Flows Installed from Packages
Keep these considerations in mind when you distribute, upgrade, or remove a flow that you installed from a package.
Required Editions
| View supported editions. |
- Flow Builder can’t open a flow that is installed from a managed package, unless the flow is a template or overridable.
- If you install a managed package that contains multiple flow versions in a fresh destination org, only the latest flow version is deployed.
- If you install a non-template flow from a managed package, error emails for that flow’s interviews don’t include any details about the individual flow elements. The email is sent to either the user who installed the flow or the Apex exception email recipients.
- If you install a flow from an unmanaged package that has the same name but a different version number as a flow in your org, the newly installed flow becomes the latest version of the existing flow. However, if the packaged flow has the same name and version number as a flow already in your org, the package install fails. You can’t overwrite a flow.
- If you install a flow from an unlocked package that has the same name as a flow in your org, the newly installed flow overrides the existing flow.
Status
An active flow in a package is active after it’s installed. The previous active version of the flow in the destination org is deactivated in favor of the newly installed version. Any in-progress flows based on the now-deactivated version continue to run without interruption but reflect the previous version of the flow.
Distributing Installed Flows
- When you create a custom button, link, or web tab for a flow that’s installed from a managed package, include the namespace in the URL. The URL format is /flow/namespace/flowuniquename.
- When you embed a flow that’s installed from a managed package in a Visualforce
page, set the name attribute to this format:
namespace.flowuniquename.
Upgrading Installed Flows
Upgrading a managed package in your org installs a new flow version only if there’s a newer flow version from the developer. After several upgrades, you can end up with multiple flow versions.
Removing Installed Flows
- You can’t delete a flow from an installed package. To remove a packaged flow from your org, deactivate it and then uninstall the package.
- 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.
- If you have multiple versions of a flow installed from multiple unmanaged packages, you can’t remove only one version by uninstalling its package. Uninstalling a package—managed or unmanaged—that contains a single version of the flow removes the entire flow, including all versions.
- Delete flows from an unlocked package manually—you can’t delete them by removing them from the unlocked package.
Translating Installed Flows
You can translate flow definition names only on the Translate page.
