Red Argyle Logo

Patterns
The Salesforce Blog with Tailored Goodness

3 Reasons I Love Process Builder Updates in Salesforce Summer ‘15

There is not much I don’t like about the Salesforce Lightning Process Builder. I’ve already mentioned how I love the flow layout and the abundance of actions. But with the release of Summer ‘15 and the latest Process Builder updates, I find that this tool keeps impressing me while also making my job easier.

 

The first thing I have to talk about when referring to the latest Process Builder updates is the fact that I don’t need to wait 12 hours before deleting a deactivated process. This was something that really bugged me in the past. I don’t like clutter in my home life or my work life. Once I clone, update, and perfect a process, I want to delete the mess I made along the way–and now I can. Thank you, Salesforce, for helping me stay tidy.

 

Next up–we can now define certain conditions before updating a record. HALLELUJAH! This is fantastic. I find myself using this option a lot these days and don’t know how I would function without it. Here’s a great example: I recently built a process on a custom object that needed to do many things. First, it had to check the Industry field on the Opportunity, and depending on what was selected, it would stamp selected users into defined fields on the custom object. I had about 8 different options for Industry and 3 different fields to populate on the custom object. This could be easily done by saying, “If Industry = A, then stamp field 1 with Person 1, stamp field 2 with Person 2, and stamp 3 with Person 3,” etcetera, through all my different Industries (see the screenshot below for a visual on this).

 

Process builder updates let us define criteria before updating a record.

Initial criteria and actions.

 

Making things a bit more complicated, however, was the fact that the client had one additional requirement. He wanted to be able to manually override the automation. Without the ability to define criteria on a record update, manually overriding this process would not have been possible. So, within each record update, I set the criteria to have the process fire only if the field on the custom object was null. With this criteria set, the ability to edit automatic stamping is simple. For example, if Industry = A, then my process will stamp field 1 with Person 1; but, my client can manually override if and when the need arises.

 

Manually overriding automatic stamping

In my example, criteria are set for automatic stamping only if the field “Industry VP Approver” on the custom object is null.

 

While Summer ‘15 has many, many great Process Builder updates, the last one I’d like to mention is that field updates now have so many more options. My mind was blown when I first saw how much power I was now given. My ultimate favorite is “Reference,” which allows me to choose a field on the record, but, more importantly, on a related record. So easy and tidy. Done and done. But we also have access to Global Constants. I can set a value to null ($GlobalConstant.Null) or check to see if a field is equal to $GlobalConstant.Null in a flash. Bravo, Salesforce.

 

While I’d already enjoyed building processes with Lightning Process Builder, with the latest round of Process Builder updates, Salesforce has now made my building faster and more efficient and has given me power that previously only our developers had. So my only question now is, “What CAN’T I do?”