Related Posts
Additional Posts in Salesforce Professionals
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

In the last year my largest implementations have been completely flow, with need for very little Apex. (Always use where suited)
Similar to Apex, scheme a flow architecture and use a handler per object for before save and after save and leverage sub flows for reusability and organization.
Also leverage the flow list, view function and naming syntax to create easy to navigate lists when you have a large org with 50 + flows
With the flow explorer, and constant updates per release, flows can be very accessible way for powerful automation without relying on a developer
My rule of thumb- if there is a need for trigger on an object, move all the flow logic to trigger. Salesforce is always recommending flows but they publish no guidelines for what to do when you must have a trigger too on the object.
So create flows unless there is a trigger on the object.