Process Builder is a like a double-edge sword – on the one hand, it is one of the most powerful tools provided by Salesforce to implement business automation declaratively; on the other hand, if one implements process builder sloppily then, it may turn into a nightmare by flashing errors like SOQL 101 error, CPU timeout, etc.
Let us first understand the role Process Builder plays in streamlining businesses processes and procedures. First and foremost, Process Builder helps businesses save time, as well as money, by enabling users to implement solutions quickly. Implementation of Process Builder is straightforward – you create a Process; test it; and then, use Change Set, to deploy it to Production. The best part is, you do not have to write test classes for your Processes or Flows.
We all desire to be on the right side of the sword! The question is, how? How can one learn to adhere to best practices to implement process automation declaratively?
Well, look no further! For, 100+ blogs, on Process Builder, are on Automation Champion alone.
To get you started, this article summarizes best practices and strategies to implement Process Builder processes.
#1 Always! Plan before you build
The key to successful project implementation is – design first and then implement. Process Builder is no different – the same logic applies here too. I have seen many cases where people start creating process(es) as soon as they get requirements. As a result, more often than not, users end-up getting some weird error messages.
I am a seasoned trainer. Time and again, I have to remind my trainees not to rush into implementing the process as soon as I give them requirements! Furthermore, I get number of requests from the community to help them identify errors in their process builder. My first question to them is, please show me your design. Almost always, their response is – Design? Huh? What? I can show you my process, why do you need to see a design? So, please, save time and sanity – Design first!
Reference – Getting Started with Process Builder – Part 79 (Auto Remove Managed Package License from a Deactivated User!)
Here are my suggestions – once you get the requirements do the following: Read the rest of this entry!
