Deploy Process Builder

The faster and easier way

Process builder is one of the most powerful way to automate processes within your Salesforce organizations. However, deploying process builders is often not as straightforward as other metadata components.

In this blog post, we discuss typical ways of deploying process builders, known issues and resolutions to make your deployments as smooth as possible.

Deploy process builder using Salesforce Change Sets

In Change Sets, process builder is listed under “Flow Definition”. While each process could have multiple versions, Change Sets only shows top level process names without breaking down into versions.

For example, in the example below, CSAT process has 3 versions CSAT-1, CSAT-2 and CSAT-3 but only CSAT is being shown.

This design means that you cannot deploy a specific version of a process. You simply select the name of the process and Change Set will decide which version to deploy. So how does it select versions exactly ?

• If there is an active version in the source org, the active version will be selected.
• If there is no active version in the source org, the latest inactive version will be used.

Keep in mind that an active flow in a change set is deployed to its destination as inactive. Make sure you activate the flow manually after deployment.

Deploy process builder using ClickDeploy.io

ClickDeploy.io allows you to deploy process builders in a more flexible way. Unlike Change Sets, we break down each process into its available versions so you can select exactly the version you wish to deploy.

In the example above, all 3 versions of CSAT flow are listed. ClickDeploy also shows you that version 1 and version 2 are the same. Version 3 is a new version (represented by the green diff icon).

When deploying sensitive changes like process builders, it is important to compare and review the changes before proceeding with the deployments. With ClickDeploy.io, you can easily compare and view detailed differences between the source org and the target org simply by clicking on the diff icons.

Similar to Change Sets, active flow is deployed to its destination as inactive. Make sure you activate the flow version after deployment.

Common known deployment errors

One of the most common known issues with deploying process builder is : “The version of the flow you’re updating is active and can’t be overwritten.”

This applies to both Change Sets and ClickDeploy.io. If you run into this error, take a look at our support article for resolution.

Are you still using change sets ? Try clickdeploy.io today and deploy Salesforce 10x faster.