Till date, we have created many processes to fulfill business requirements. I have created 100+ processes just for my blog posts! Process Builder is a very powerful tool to declaratively implement business requirements. It helps businesses to save time, as well as money, by implementing solutions quickly. The best part is, you do not have to write test classes for your Processes or Flows. So far so good, but these processes may create problems in future if you start creating a new process for each requirement. That not only is not a best practice but, in the long run, it is highly unproductive and unsustainable approach to managing process development.
Prior to Summer’16 release, processes executed actions that were tied to only one criteria node. Previously, when a record met your defined criteria node (1) or (3), the process executed the associated action group and then stopped at (2) or (4). It means, processes are designed to execute only one criteria node either (1) or (3) in one execution.
After Summer’16 release, it is possible to choose what happens after your process executes a specific criteria node. Should the process stop? Should it continue evaluating the next criteria in the process? It depends on you! By using this new feature, you can execute multiple action groups in a single process – making it easy to manage all of your processes, for a given object, like an Account, in one place!
Business Use Case
Pamela Kline is working as System administrator at Universal Containers. She has developed a process for a requirement to update Account custom field, Out of Business, to True if an Opportunity Stage is updated to Closed Lost – refer to (For Lost Opportunities) – (Getting Started with Process Builder – Part 71 (Set Your Productivity on Steroids by Creating Reusable Processes!)