I understand it is best practice to only have one flow for each object, what is the best way to bring multiple flows together when you have inherited an org with multiple flows for one object? #SalesforceLive
The answer is it depends.
Unlike processes and apex triggers, Salesforce is not recommending one flow per object. Instead, it depends on your business and situation. If you are a small company, maybe it makes sense to have one before save, after save and delete record triggered flows per object, like a process. If you work in a large org, that may result in very massive flows that are not easy to maintain and would require regression testing with each change. Perhaps you have multiple business units in one org and they want to control their own destiny. You can also use the trigger order to specify the order of execution for your record triggered flows and avoid big flows with subflows. Choose the design pattern that best suits your org's needs.
