Comparison between lightning process builder vs workflows. Features and limitations.

1. Lightning Process Builder vs
Workflows
-Prasanna Deshpande

2. Lightning Process Builder
• Lightning Process Builder lets you automate business processes using
a visual interface.
• Processes allow you to execute actions when certain conditions are
met.
• You can add multiple groups of criteria and associate actions with
each criterion.
• You can create immediate and scheduled actions.
• You can use versioning to easily track and maintain processes.

3. Advantages of Process Builder
• You can write multiple steps in one Process. It means task which
would have required multiple workflows can be combined into single
Process.
for example, you decide to add two layers of criteria (criteria 1 and 2), the process builder will check criteria 1 first. If the record complies with this criteria, it
will execute the action associated with it and stop.
However, if the record doesn’t meet criteria 1 it will check criteria 2. If the record fulfils the requirements of criteria 2, then it will execute the action associated
with it. And so on for criteria 3, 4, etc.
In effect, what this means is that processes that you could only have done with multiple workflow rules in the past, can now be achieved with only one process.
• More Number of tasks can be performed than workflows.
• Other than actions available in workflows you can doo additional actions as below. – Trigger an apex class;
• – Create a record;
• – Launch a flow (you can’t do this with a workflow anymore, remember?)
• – Post to chatter;
• – Submit for approval;

4. Advantages of Process Builder
• More flexibility with in criteria stages than
workflows and visual aspect
• Higher limits on number of processes and
the number of nodes Organization has.
• For example you can refer:
https://developer.salesforce.com/blogs/developer-
relations/2015/03/process-builder-taking-point-click-
development-new-level.html

5. Limits on Workflows
• The default limit is 50, but you may request 300 as a maximum of Active
Workflow Rules. You can add additional inactive rules for a total of 500 Workflow
rules, and this limit is hard-coded.
There is, however, a 2,000 Rules per org maximum. The org limit applies to any
combination of workflow (including Processes created via Process Builder),
assignment, auto-response, and escalation rules, both active and inactive. This is
a hard coded limit that cannot be raised.
• Large number of Workflows makes system slow and impact on overall
performance.

6. Limits of Process builder
Description Per-Organization Limit
Total active rules and active processes. Rules include workflow rules, escalation rules,
assignment rules, and auto-assignment rules.
50 per object
Total flows and processes 1000
Active flows and processes 500
Total number of criteria nodes that are evaluated and actions that are executed at runtime 2000
Total number of flow interviews that are resumed or groups of scheduled actions that are
executed per hour
1000
Total number of flow interviews or groups of scheduled actions that are waiting to be
processed
30,000
Total number of relative time alarms defined in flow versions or schedules based on a field
value in processes
20,000

7. Approach for overcoming number of
workflow limits
• Segregate the current workflows and develop them as a part of
various Process Builder process. After that corresponding WFR can be
deactivated
• One Process Builder process would perform multiple WFR jobs
• Process Builder is the latest feature from Salesforce which would
come up with more options in future and Salesforce recommends
that Process builder should be used.