Join me for a Salesforce.org webinar Intro to Flow on Thursday, Apr 9, 2020 9:00 AM – 10:00 AM PDT. Register here.
Remember back when there were community events and conferences? I had the honor to speak at Cactusforce in Phoenix in January — highly recommend this small event! So many MVPs, so many recognizable experts in one small event. And the weather was great.
Session Description: Flow Loops unlock incredible power previously held only by devs. Without using any code, Admins can create an automated process to loop through all related records and take actions based on what is found there!
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.
Answering why this failed doesn’t have to be a rabbit hole.
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!