Package Inactive Processes and Flows

When a subscriber installs a package that contains an active process or flow, that process or flow remains active. However, sometimes subscribers want to decide whether and when to activate each process or flow. For example, subscribers probably don’t want record-change process templates to be active upon installation. Now you can package inactive processes and flows so that subscribers can activate them at their convenience.

Where: This change applies to Lightning Experience and Salesforce Classic in Professional, Enterprise, Performance, Unlimited, and Developer editions.

Why: Suppose you create a process template that subscribers are likely to clone and customize instead of use as is. We recommend that you keep that template inactive in the package.

How: When you upload a package that contains a process or flow, the active version of the process or flow is distributed to subscribers. If the process or flow has no active version, the latest version is distributed to subscribers.