Hi,
I attended a recent webinar on TrailheaDX on flow best practices. In the webinar it was recommended that we create one flow per object (I'll continue referring to this as the 'master' flow) then create multiple sub-flows that are then called via that 'master' flow.
That being said, this doesn't appear to be possible with record triggered flows since they cannot call sub-flows. I really like this tip and would like to implement it for my org in order to keep us from hitting governor/apex cpu limits, however, if the 'master' flow is not a record triggered flow, I do not know how to call it whenever a record is created or updated. Does anyone have any recommendations on how to achieve this?
Thanks in advance!
#Flow #Flow Builder #Best Practices #Salesforce's Governor Limit #CPU Limit #Data Management #AwesomeAdmins #TDX21 #Automation
Hi Kristan, That's Great that you got to learn best practices. For sure FLOWs is a very powerful automation tool on the force.com platform. But we have to be sure that there are still many use cases that we cannot achieve through Flows. There are some drawbacks and a lot of scope of improvments and I am sure Salesforce will come up with new features. I personally have seen a lot of changes on FLOWs.
To answer your question: Before having a Trigger's feature in FLOWs we use it to invoke FLOWs through Process Builder. This way you can still invoke multiple Flows on one object. But it will always be On-Creation or On-Edit of a record.
