No more ONE Process Builder per Object BS. It doesn’t translate to Flows… so what do we do now?
In a nutshell, here's my rules... Build Flows carefully and with consideration. Don't use Process Builders until the last resort (there are still a few last resorts out there). Similarly for Workflows but they are less evil that Process Builder, and I still use Workflows for Emails. Make liberal use of the new Asynchronous Flow Trigger type coming in Winter '22. Create separate Flows when an After Update is needed on a field that doesn't get updated very often. Create one Flow for Before Save for most Objects and start with doing anything in there, until you can't, or it needs to be split out into Subflows or move to an After Save Context (After Save Subflows in Winter '22 will be great).
For the real advice use the Record-Triggered Automation guidehttps://architect.salesforce.com/design/decision-guides/trigger-automation/
Here’s my advice as I go through moving all my Process Builders to Flows and think about it a bit more.
| Status | ||||
|---|---|---|---|---|
|
Bottom Line
For every flow action, if it can’t be in a Before-Update Flow then think about when this action is required to be run. IF you can set criteria that action does NOT have to be run on every single update, then stick it in a separate Flow with criteria so the Flow is not even run until it needs to. Remember Process Builder ran through almost every node almost every time… that was such a waste of recourses and slowed everything down considerably. If you don’t need to run a Flow, don’t.
...