Final Up to date on July 4, 2022 by Rakesh Gupta
My identify is Pablo Gonzalez. I’m the creator of HappySoup.io and have been a Salesforce developer for 11 years.
Except you’ve been dwelling below a rock the previous couple of months (and I received’t decide when you’ve got!), you’ll have heard that Salesforce has plans to retire Workflow Guidelines and Course of Builders in favor of Flows.
The official announcement solutions a lot of the questions you can have about this, so I extremely advocate studying it, and I’ll strive to not repeat an excessive amount of about it right here. Nevertheless, the essential bit is that this:
We wish to make Move your one-stop store for low-code automation. And we wish to be certain that we are able to throw the complete pressure of our builders into constructing superior, new options and dealing on scaling up what we do have, which implies we’re stopping lively growth on Course of Builder and Workflow Guidelines.
One of the simplest ways so that you can keep and future-proof your group is to maneuver your automation to Move. That may be a big, daunting job for these of you who’ve turn into Course of Builder rockstars or are an enormous pile of Workflow Guidelines that no person has touched in three years. We all know it will take time.
Okay, so someday, you will be unable to create new Workflows, and Salesforce is encouraging us emigrate our present Workflows over to Flows. So, how can we try this?
On this article, I’ll present you use HappySoup’s new Workflow migration instrument, and Salto’s free product to assist with the duty at hand.
Don’t migrate, consolidate as a substitute
Salesforce has launched its official workflow migration tool, which creates a 1:1 mapping of a Workflow to a Move.
So when you’ve got a Workflow that has a discipline replace, the instrument will create a Move that updates a discipline on the file that triggered the Move.
It is a good begin, however it’s not scalable. For instance, when you’ve got 20 Workflows on the Account object, utilizing the instrument would depart you with 20 Flows. That’s not any higher; you simply moved your mess from one room to a different.
Ideally, we should always have a look at these 20 Workflows and work out how we are able to consolidate them into fewer Flows. For instance, you can consolidate all discipline replace Workflows right into a single Move known as “Account updates,” the place you utilize determination parts to determine which fields are up to date.
This might make it simpler to cause about your Flows. For instance, you’d have one Move for account updates, one other one for electronic mail alerts, and so on.
That’s only one instance. You might additionally group Workflows primarily based on widespread fields or widespread enterprise processes and transfer them over to a single Move.
Okay, that every one sounds very good, however how do I try this once more?
HappySoup.io and Salto.io to the rescue
The thought of 20 or extra Workflows and determining how they’re comparable sounds nice, however in apply, it’s actually arduous to do. You should one way or the other export all the information about your Workflows and have the ability to type them by the fields they’re utilizing within the standards, which fields are being up to date, and so on.
In the case of Course of Builders, you want a approach to shortly perceive what they’re doing and the way they examine to present Flows within the org.
HappySoup.io Workflow Export Software
HappySoup.io is a 100% free and open-source software for Salesforce influence evaluation. I lately added a brand new characteristic that means that you can export all of your Workflows in a flattened format. This lets you put them in an excel doc and filter, type, and manage them in no matter means you think about.
As regular, a picture (video on this case) speaks a thousand phrases, so please watch this video the place I clarify how this characteristic works.
Happy Soup’s Workflow Migration Info
Salto’s Free Product Move and Course of Builder Visualization
Salto.io has a 100% free tier with influence evaluation capabilities, much like HappySoup.io (and sometimes higher!).
The free product additionally means that you can visualize Course of Builders and Flows in a model new format. This makes it tremendous straightforward to grasp what the Course of Builder is doing, which variables are getting used, the actions/circumstances, and so on.
Once more, a picture speaks a thousand phrases, so right here’s a video exhibiting the way it’s achieved:
With these two free instruments, you now have a approach to perceive the whole lot about what your workflows are doing and a approach to visualize complicated flows and course of builders.
What’s left is to spend a while going by them and making a doc or a course of diagram that maps out how all these automations will play properly with one another.
Be sure to do an intensive regression testing (primarily based on what you documented) to make sure you didn’t break any enterprise processes alongside the best way.
Do you will have any concepts or insights on making this migration simpler? Let me know within the feedback!
I wish to hear from you!
What’s one factor you realized from this submit? How do you envision making use of this new information in the actual world? Be at liberty to share within the feedback beneath.