Can you share if process builder is the best solution when making many various updates to a record over the course of a life-cycle? This process would need to be able to make record updates, create tasks immediately as well as scheduled actions such as tasks or stage changes. But I am struggling to know the best way to accomplish this by limiting the number of separate processes on that same object.
Can you make any suggestions on process builder best practices for advanced use cases?
How can we control order of operations if you have multiple processes active on the same object?
Should you have more than one per object?
It also seems that scheduled actions are limited base on some settings of the process. Like trigger on create or update, vs checkbox, etc. Is there a good place to identify some advanced use cases and best ways to tap into all this tool has to offer and optimize its available features?
Thanks!
Wow, that's a lot of questions! I'll start by saying that it's best to have ONE Process and no Workflows on one particular object. If you have numerous Workflows and Processes on the same object, we know that Workflows will be executed before Processes BUT it is unpredictable which order the Workflows, and the Processes, will be executed. Since we can have many decision blocks in one Process, that enables us to create an "order of events" inside that Process. So you want to roll everything into one Process.
