Last Updated on October 16, 2021 by Rakesh Gupta
Big Idea or Enduring Question:
How do you deploy Flows or Processes using Workbench?
After reading this blog post, the reader will be able to:
- Understand how to use Workbench retrieve change set
- Understand how to use Workbench to deploy flows
- Understand how to use Workbench to deploy processes
- Deploy components to any org using Workbench
Business Use Case
Pamela Kline is working as a System administrator at Universal Containers. She has developed a Flow (Getting Started with Salesforce Flow – Part 50 (Welcome New Users by Default – Auto Follow them in Chatter!)) in her Trailhead playground and is done with testing. Now, she wants to deploy the flow to her UAT Sandbox.
Automation Champion Approach (I-do):
Once you are done, with Flow or Process development, the next step is to deploy it. There are many ways, through which, you can deploy or distribute, Flow(s) or Process(s), from one org to another:
This blog is a sequel to my previous blog – Distribute Process(es) using the Visual Studio Code. In the previous blog, I discussed how to deploy Flow(s), or Process(es) to another sandbox using the Visual Studio Code.
Today, I am going to discuss how to deploy a Process(s) or Flow(s) using the Workbench. Workbench is a powerful, web-based suite of tools designed for administrators and developers to interact with Salesforce.com organizations via the Force.com APIs. Workbench allows users to describe, query, manipulate, and migrate both data and metadata in Salesforce.com organizations directly in their web browser with a simple and intuitive user interface. Workbench is free to use, but is not an official Salesforce.com product.
Workbench also allows us to deploy the metadata components like Flows and Processes in different environments – such as, Developer Sandbox, Production Org or Trailhead Playground.
Migrate Metadata Components using Workbench
Follow the instructions to create an Package and deploy it to another Salesforce org using Workbench.
- The very first step is to create an Outbound Change Set or Package in the source org, i.e. Trailhead Playground in this scenario. It doesn’t matter which option (Outbound Change Set or Package) have selected to go forward, as long as it contains all metadata components.
- Before proceeding ahead, make sure that the package you created in Trailhead playground looks like the following screenshot:
- The next step is to retrieve the package or change set using workbench.
- Open the Workbench and login with your Trailhead playground username and password.
- Make sure that you’ve selected Production for Environment option.
- Navigate to Migration tab and select Retrieve option.
- Under Retrieve
- Click Next.
- Click Retrieve.
- Click Download Zip File select your Desktop as the place to save the file in so it is easy to find later on.
- At the end, logout from the Workbench.
- The last step is to upload the package to Pamela’s UAT Sandbox.
- Open the Workbench and login with your UAT Sandbox username and password.
- Make sure that you’ve selected Sandbox for Environment option.
- Navigate to Migration tab and select Deploy option.
- Under Deploy
- Click Next.
- Confirm all of the options for deployment by clicking on the Deploy button.
- Wait for process to become completed.
- After successful deployment, you will get the message shown in the following screenshot.
Proof of Concept
At long last, here comes the final step!
I want to hear from you!
What is one thing you learned from this post? How do you envision applying this new knowledge in the real world?
Let me know by Tweeting me at @automationchamp, or find me on LinkedIn.