Salesforce’s Visual Workflow and Process Builder are incredibly powerful tools but can be very difficult to troubleshoot. I struggled to make these tools effective until I was able to get a glimpse of what was happening inside. Salesforce has some suggestions for how to troubleshoot failing flows but often these tools provide incomplete answers. Particularly for auto launched flows, these techniques are often insufficient.
If you work on the clicks side of the force and you haven’t heard of Custom Settings and the cool things you can do with them using declarative functionality then this is the blog post for you! There are also many other great blog posts for you out there and a few Dreamforce sessions as well. Why should you keep reading this particular blog post and not crawl off down the internet rabbit hole I just dug for you? Because I’m going to explain what Custom Settings are and then document three examples of how you can use them with clicks not code, but more importantly, my examples are kind of funny… I hope.
What are Custom Settings?
Custom Settings, like Custom Objects., have custom fields that allow you to create records that contain data. However, unlike Custom Objects, Custom Settings can be accessed in any formula, workflow rule, and process builder organization-wide. Custom Settings are indeed settings for your org or application!
You’ve probably heard of “lean management” or “lean manufacturing.” It feels like “lean” is ubiquitous in many industries, but I haven’t encountered the buzz word up here in the cloud. We have a self-improvement book club at my employer, Optimum Energy, and last week we discussed 2 Second Lean by Paul Akers.
“Lean” is the involvement of the entire company in continuous small improvements to remove waste and improve efficiency, as practiced by fanatic Paul Akers.
Good Salesforce administration is one of the most “lean” things you could do for your company.
Every day each of Paul Akers’ employees comes up with one process improvement that cuts out two seconds. 2 Second Lean claims you can revolutionize your company in these tiny increments. And I believe it, because that’s exactly what I do all day in SFDC.
At Optimum Energy, for every energy optimization project, a series of emails used to go back and forth between members of three teams until pricing was agreed upon. Now a user clicks a button, launching a flow which asks them a series of questions and starts an approval process. No information is misplaced in an email folder. All the right people are looped in. That’s efficiency!
Continue reading Salesforce Admin: The Leanest Job Ever
Have you ever wanted to report on something only to realize you’ll likely have to write three processes and a few formulas to get there? Have you already written those processes and formulas? Is your org in danger of maxing out all its cross-object relationship reference limits? Are you about to write some more right now? STOP! Custom Report Types can solve many of your cross-object reporting problems with just a few clicks! Continue reading Custom Report Types: Why do I love thee? Let me count the ways…
Here’s an example of a “simple” flow that uses a Decision element. You don’t need to use flow to achieve the results – you could entirely stick to Process Builder. This flow is for educational purposes only.
Here’s the sitch: I want an automatic email to my customer when we quote a specific product. For example, “Dear Darnell McCustomer, for a limited time only, you can purchase the EDGE widget for $150!”
Caveat: I want this to be in an HTML template, not a Visualforce email, based on the Quote object. I can’t reach the price on the Quote Line Item from Quote in this format.
Flow took me from a “hmm…let me Google that” Salesforce admin to a confident “no record is too far out of reach” admin-eloper (admin/developer). Leadership changed at my company and I had to quickly differentiate myself from my new boss, a Salesforce administrator with way more experience than me. In our initial conversations, he made it clear he would prefer to have a developer working for him. Okay…. one developer, coming up!
You can’t do a user lookup inside a screen element in Flow, so create dynamic record choices instead! No need to hardcode the names of employees who might leave.
- Dynamic Record Choice – don’t need to hard code the values if they may change!
- Default Picklist Value
- Screen element in the flow.