Workflow Rules vs. Process Builder

Automating business processes for your users can take your applications from “nice” to legitimately useful. A savvy admin can save users time and clicks while creating consistency of processes and increasing data integrity, so mastering the tools available on the Salesforce platform can be very valuable to any organization.

Workflow Rule

Workflow has been an admin’s friend for a long time. Workflows can:

– Update a field

– Send an email

– Create a Task

– Send an outbound message (communication with another system)

These can be initiated when a record is created, whenever it meets a certain condition, or whenever it is first set to meet a certain condition. The actions can be performed in any combination and can even have a time delay, rather than be performed immediately.


Process Builder

Process Builder is a newer tool for admins which is even more powerful. In addition to everything a workflow can do (except for sending outbound messages), you can:

– Create a record (not just Tasks!)

– Update related records

– Launch a Quick Action

– Post to Chatter

– Launch a Flow

– Call Apex code

– Submit for approval

– Invoke another process

Process Builder also extends upon the things that workflow does. For updating related records, Process Builder can update any field on any related record, where Workflow can only update some fields on a parent record of a Master-Detail relationship. Process Builder can also update multiple related records in a situation when all of a record’s child records need the same update.

Also, Process Builder finally gives admins the ability to set the exact order of operations, whereas with Workflow we had no control. No more complex workarounds to be able to ensure things happen in a certain order!

Since Process Builder also has the ability to configure multiple if-then conditions in one Process rather than separate Workflow rules, it helps new admins and admins who inherit orgs visualize the business processes with its sleek visual interface.

Process Builder has versions, so you can retain deactivated Processes. This can be very helpful if you realize something isn’t working and want to look back to what was happening before.

Lastly, one of the biggest reasons to use Process Builder, might just be because it’s the future.



This conversation is vital for future innovations in our industry.

Like
Reply

To view or add a comment, sign in

More articles by Archith Shriram Ramesh

  • Best Practices using Salesforce Workflow

    Salesforce Workflow evaluates records as they are created and updated and determines if an automated action needs to…

  • Trigger Context Variables:

    All the trigger context variables prefixed with “Trigger.” (Ex: Trigger.

  • 10 Reasons Why We Love the Salesforce AppExchange

    Drives Positive Business Impact: The AppExchange is the largest app marketplace for cloud-based business software…

  • 5 ADVANTAGES OF SALESFORCE CRM

    1) Ease of Use – It stands to reason that one of the single most important elements of any service is its ease of use…

  • Salesforce Chatter

    5 Reasons You Should Be Using Salesforce Chatter We all know Salesforce likes to talk about the social enterprise, and…

  • Salesforce.com Wave Analytics Cloud: Pros

    Salesforce.com Wave is a big bet that's already generating demand, but will it live up to the billing? Will Salesforce.

  • Advantages of Lightning in Salesforce

    Why Use the Lightning Component Framework? The benefits include an out-of-the-box set of components, event-driven…

    2 Comments

Others also viewed

Explore content categories