I want to design a workflow to make it work like,

If criteria C1 =true; -> Action 1. Field Update

If criteria C1 & C2=true -> Action 1. Field Update 2. Email alert.

In a single workflow I'm not able to implement this one, also I don't want to use process builder(least priority) here. Neither want to go for trigger. Instead want to keep 2 workflows W1 & W2.

W1 : C1= true; -> 1. Field Update

W2 : C1 & C2 =true -> 1. Field Update & 2. Email ALert.

Is this a good design practice? Or should I go by process builder? Please suggest.

1 Answer 1


You should go with Process Builder. The beauty of process builder is one process can handle multiple criteria updates and all of them will be in a single process like the one you have now.

Process Builder is the future! If you see the new Professional Salesforce Editions, they don't have workflows anymore, they only come with Process Builder. Process Builder can do a lot more than what a workflow does. You shouldn't be surprised if Salesforce stops allowing creation of new workflows 2-3 years down the line.

When a single process builder can handle both the scenarios, you should go with it instead of multiple workflows. And process builder can also help you you set the execution order for your 2 criteria unlike the 2 workflow rules here.


In your first criteria in the process builder, if you click on STOP, there is an option to continue evaluating next criteria. So, even if the 2nd criteria falls under the "false" of 1st criteria, the process continues on to the next criteria and evaluates and runs it too, all with in a transaction.

  • 1
    Completely agree with sfdc's comments, Process Builder is being developed to replace Workflow Rules (& then do more than WFRs). The one risk with the PB at the moment is that if you set your criteria to evaluate a field that's empty, this will throw an error whereas a WFR will just evaluate to false.
    – Alex S
    Commented Jun 15, 2016 at 9:09
  • 1
    Using the PB also helps avoid limits - you're limited to 300 rules & processes per object. You can evaluate up to 2,000 criteria nodes (& trigger multiple resulting actions for each) for a process, versus the 300 WFRs.
    – Alex S
    Commented Jun 15, 2016 at 9:15
  • 1
    If limits are a concern, take a look at this guide on writing criteria to avoid wasting resources too.
    – Alex S
    Commented Jun 15, 2016 at 9:15
  • 2
    At the end of the first Condition block (criteria), there will be a STOP Button. Click on stop button and choose "Continue Evaluting Next Criteria too". That should help
    – sfdcFanBoy
    Commented Jun 15, 2016 at 9:42
  • 1
    Yes it is......,
    – sfdcFanBoy
    Commented Jun 17, 2016 at 13:37

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .