Is Your Organization Ready to Retire Workflow Rules and Process Builder?

pexels andrew neel 2312369 scaled compressed - Alternative Solutions Consulting

Is Your Organization Ready to Retire Workflow Rules and Process Builder?

Salesforce Automation Tools

Currently, on the Salesforce Platform there are three tools you can use to create automation. Those three tools are Workflow Rules, Process Builder and Flow. Salesforce is gearing up to retire Workflow Rules and Process Builder. This retirement is focused on creating a more streamlined approach to automation and to keep things as simple as possible with their low-code motto. As this retirement looms, Salesforce will lead you to create any new automations using only Flow. At Alternative Solutions our Salesforce Consultants are evaluating and readying our own instance for this change.

How does this effect your Salesforce Org? One of the benefits of Salesforce is the ability to automate repetitive tasks. If you currently have Salesforce, your org is mostly likely using one of these tools for your current automation processes. It’s now time to begin thinking and strategizing on how you will convert your existing processes to Flow.

Mapping Out the Process

Salesforce has started to map out a process to help you “go with the Flow”. They are giving everyone plenty of time to make these transitions but don’t wait to get started. If you have a Salesforce Admin in house, they will need to ramp up their knowledge of Flow and learn more about the migration tool that Salesforce currently has in Beta testing that will help you convert your existing processes. This is a great time to make sure that your organization is following the best practices of having only one automation process for each object. You want to avoid having overlapping processes on objects. The overlapping of multiple automation triggers on any one object can cause a spider web of a mess and untangling the mess can be overwhelming.

Start Using Flow

For new Admins this might be a bit overwhelming and daunting especially since you cut your teeth on Process Builder or Workflow Rules. Your first action should be to locate all the current automations and inventory those. As you start your inventory, you will need to determine if they are still applicable to your current business process. You will also need to start using Flow in any new automations so that you will not have to revisit or make changes as you move toward updating existing automations.

Salesforce’s Migrate to Flow (Beta) tool currently provides support for converting your existing Workflow Rules into Flows. They plan to add support for Process Builder to Flow migration as well, in the Winter ’23 release. Also on the horizon is the plan to start blocking Admins ability to create new Workflow Rules and Processes, currently slated for the Winter ’23 release.

As always, these dates are subject to change and should be considered a forward-looking statement.

Create Your Roadmap

Here at Alternative Solutions, we are working with our clients to create a Roadmap to ensure that this transition is as seamless as possible and that nothing gets lost as the automation processes are converted. We will be starting, just like you should, by mapping all existing processes and evaluating their necessity. It’s also a perfect time to clean up any automation that isn’t needed and perhaps define any new processes that your Users can benefit from. If you are wanting to get ahead of the game and make updates that can consolidate your current automation processes, Alternative Solutions can help. We offer support packages to ensure that your team stay ahead of the game, and you come out with an even better and cleaner process than before.

Don’t forget Trailhead

As always, Salesforce recommends seeking out Trailhead and going through their trails on Flow. This will help you better understand what this transition will entail and to get the jump on learning a new and powerful tool that can help you better utilize your platform.