Process Builder is one of the most powerful tools provided by Salesforce to implement business requirements declaratively. Till date, we have created many processes to fulfill business requirements. I have created 100+ processes just for my blog posts!
Process Builder helps businesses to save time, as well as money, by implementing solutions quickly. Implementation of Process Builder is straightforward – you create a Process; tests it; and then, use Change Set to deploy it to Production. The best part is, you do not have to write test classes for your Processes or Flows.
But there are few limitations of Process Builder vis-a-vis Workflow! Yup! You read that right! Workflow has an upper hand when defining Rule Criteria!
Let me unravel this mystery by offering an example: As a System Administrator, you receive a requirement to auto-create a Quote record whenever Opportunity Stage is Proposal/Price Quote or Negotiation/Review.
To achieve the above business requirement, through a Workflow Rule, you may do something similar to as shown in the following screenshot:
But to achieve the same requirement through Process Builder, you may do something similar to as shown in the following screenshot:
If you created processes using Process Builder before then, you know how I set two values for Stage picklist. But, for those, who are relatively new to Process Builder, let me walk you through the process step-by-step. Workflow Rule allows you to select multiple values for a picklist. If you look at the Workflow Rule screenshot, I have chosen (defined) both the picklist value in a single line using commas (,).
But if you try to achieve the same thing using the Process Builder, it will not work. Unlike Workflow rules, one cannot develop a rule criteria to select multiple picklist values, in a single stroke, using Process Builder! For detailed explanation, please refer to the following article published by Salesforce – CONTAINS with multiple comma separated values does not trigger a Process Builder or a Flow.
The solution suggested by Salesforce (is the same as I have used in Process Builder screenshot) is good for the simple business use case. But what about a complicated requirement where you need to take other things into consideration (like Amount > $1000 and Close Date > Today) while defining process criteria? Read the rest of this entry!