Salesforce Workflow Vs Process Builder in Salesforce

Workflow Rule

By using Workflows we can:

1) Update a field

2) Send an email

3) Create a Task

4) Send an outbound message

Don’t forget to check out: Automation Hero | Salesforce Process Builder a step ahead Workflow

All of these can be initiated when a record is created, condition meet.

Process Builder

Using Process Builder we can:-

We can create a record can Update related records can Launch a Quick Action. We can Post to Chatter We can Launch a FlowWe can Call Apex code We can Submit for approval can Invoke another process

In Process Builder, We can update any type of field on any related record but Workflow only updates some type of field on a parent record of a Master-Detail relationship.

Procedure Builder has the capacity to design different on the off chance that state in one Process as opposed to separate Workflow rules.

On the off chance that you need your procedure to accomplish more than what procedure activities permit, don't stress we can likewise call Apex or a stream from a procedure.

Apex

With Apex you could do the following:

Delete records
Update unrelated records
Share records with more complex criteria than Sharing Rules permits
Add/remove users in Chatter Groups and Public Groups
Create email templates that pull info from multiple records and Objects
And more

Apex is a very powerful tool, but do your best to minimize its use and don’t be afraid to employ it, but make sure you think it through thoroughly to determine & if there is a way you can accomplish what you need declaratively. Utilizing Apex means that you will require to write test coverage. besides the more Apex you have, the more it will make arrangements from Sandboxes in light of the fact that the progressions should be validated against the entirety of the code

Workflow Limits

Per-Org limit value all out guidelines across objects

(Applies to any mix of work process, task, automated message, and acceleration rules, dynamic and inert.) 2,000All out guidelines per object
(Applies to any blend of work process, task, pre-programmed message, and heightening standards, dynamic and inert.) 500Dynamic standards per object
(Applies to any mix of the dynamic work process, task, pre-programmed message, and acceleration rules, just as record change forms.)

50 Time triggers per work process rule110Quick activities per work process rule1 40 Time-subordinate activities per time trigger 40 Work process messages every day 1,000 for every standard Salesforce permit (15 in Developer Edition); 2,000,000 for every organization work process time triggers every hour 1,000Flow trigger workflow actions: flow variable assignment 225 (N/A in Professional Edition)Consolidated aggregate of these robotizations that start or resume dependent on a record's field esteem. Resume occasions that are characterized in dynamic streams Gatherings of planned activities that are characterized in dynamic procedures time triggers that are characterized in dynamic work process rule the latest stream meets that are continued 20,000.

1. The immediate actions and each time trigger can have 10 emails alert 10 tasks10 field updates 10 outbound messages 10 flow trigger.

2. The experimental run program for stream trigger work process activities is finished. On the off chance that you've so far empowered the pilot in your organization, you can resume to make and modify stream trigger work process activities. On the off chance that you didn't empower the pilot in your organization, utilize the Flows activity in Process Builder rather

Process LimitsWhen building processes keep split limits and Apex governor limits in mind. In addition, a process’s API name must be special across all processes and flows in your org.

REQUIRED EDITIONS

Available in: Salesforce Classic and Lightning Experience

Available in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions Limits Shared with Other FeaturesProcesses share some limits with rules and flows.

PER-ORG LIMITESSENTIALS OR PROFESSIONAL EDITIONENTERPRISE, UNLIMITED, PERFORMANCE, OR DEVELOPER EDITION

Rules include workflow rules, escalation rules, assignment rules, and auto-assignment rules. 5050 Total processes 5 per process type 4,000 per process type active processes 5 per process type 2,000 per process type criteria nodes that are evaluated and actions that are executed at runtime per process 2,0002,000 Groups of scheduled actions that are executed or flow interviews that are resumed per hour 1,0001,000 Combined total of this automation that start or resume based on a record’s field value.

Resume events that are defined in active flow groups of scheduled actions that are defined in active processes time triggers that are defined in active workflow rules Inactive flow interviews that are resumed 20,00020,000 As far as possible for messages sent from email alarms are 1,000 for each standard Salesforce permit per organization, with the exception of Developer Edition organizations. For a Developer Edition organization, the regular work process email limit is 15 for each standard Salesforce permit. The general organization limit is 2,000,000, which is shared over all highlights that utilization work process email alarms: work process rules, endorsement procedures, streams, and procedures. Active record change processes and rules per object

Apex Governors and Limits for Processessalesforce carefully implement points of confinement to guarantee that runaway procedure don't hoard shared assets in the multitenant condition. forms are represented by the per-exchange limit that is authorized by Apex. On the off chance that the procedure makes the exchange surpass representative confines, the framework moves back the whole exchange. For insights concerning the tasks that are remembered for the exchange, see "Triggers and Order of Execution" in the Apex Developer Guide.

DESCRIPTION PER-TRANSACTION LIMIT

Total number of SOQL queries issued100Total number of records retrieved by SOQL queries 50,000 Total number of DML statements issued 150 Total number of records processed as a result of DML statements10,000Each Create a Record activity utilizes one DML articulation. Every Quick Action activity can utilize one DML articulation. Each Update Records activity utilizes one SOQL inquiry and one DML articulation. Every stream activity can utilize various SOQL questions and DML articulations, contingent upon the components that the stream executes. For subtleties, see Per-Transaction Flow Limits. Each Create a Record activity utilizes one DML articulation. Every Quick Action activity can utilize one DML articulation. Each Update Records activity utilizes one SOQL inquiry and one DML articulation. Every stream activity can utilize various SOQL questions and DML articulations, contingent upon the components that the stream executes. For subtleties, see Per-Transaction Flow Limits. Each Create a Record activity utilizes one DML articulation. Every Quick Action activity can utilize one DML articulation. Each Update Records activity utilizes one SOQL inquiry and one DML articulation. Every stream activity can utilize various SOQL questions and DML articulations, contingent upon the components that the stream executes. For subtleties, see Per-Transaction Flow Limits.

Limits for Creating and Managing ProcessesConsider these limits when creating and managing processes.

PER-PROCESS LIMIT VALUE: Total characters in a process name255Total characters in a process’s API name79Total versions of a process50Total criteria nodes in a process 200.