‘Manage Contact Data’ - Main screen flow that launches various disconnected processes:.Complex processes/subprocesses: If your flow involves multiple processes and branching logic, make use of a main flow that launches other secondary flows.The development world calls these ‘Helper’ classes. Re-use: If you’re doing the same thing in your flow multiple times, or doing the same thing you did with another flow, call a subflow to do it for you.Here are some classic use cases for when you should consider a subflow. Take this flow as an example of when you should start asking yourself, “Should I use a subflow?” Utilize subflows for cleaner, reusable, scalable ways to manage flows There’s a great repository out there for Flow-invoked actions called the Automation Component Library - check it out! 3. Find yourself creating loops upon loops and then more nested loops, or hitting element execution limits? It’s time for reusable Apex to do some heavy lifting for you.
#MINDLY ELEMENT LIMIT CODE#
Generic code used in invocable actions will amplify your Flow capabilities across the board - use one action for as many flows as you want!įlow is fantastic but has its limitations, especially around queries, large data volumes, and working with collections. Those days are gone, with Flow now supporting generic inputs and outputs. In the old days, you could invoke Apex from Flow, but you pretty much had to use it for that object or datatype. Harness the power of invoked actionsĬlean up inefficient flows with invoked actions - don’t be scared of using some reusable code to make nice, clean, presentable flows. This is especially critical when you’re using a workaround to address a Flow limitation, performing a more advanced function, or calling an Apex invocable.
This will ensure any member of the team can pick up the work if needed. Make sure you write short blurbs in each step and talk through what each Flow element is and its purpose. Check out this nifty Wiki article from the Salesforce Exchange Discord Server on suggestions for flow naming. One popular naming convention is called CamelCase. There’s no right or wrong way to do this just keep it consistent within the flow. A little bit of work upfront will go a long way for future ‘you’ or somebody else that inherits the flow. Include in the variable description what you’re capturing. Stick to naming conventions when creating variables and elements in Flow. Have a JIRA or Story ID to link it to a Story? Stick it in the description! Ensure consistent naming across elements and variables
Even better if you can mention where this flow hooks into the business process and which groups it touches, so the next person can go to them with questions.
Outline the flow’s purposeįill in that description field! Which problem is your flow solving? Be sure to include what your flow does, the objects your flow touches, and where it’s invoked from (such as which page layout to use if it’s a screen flow, which Process Builder process to use if it’s an autolaunched flow, etc.). Flow designers don’t create solutions out of thin air - we need a business case to solve hard problems, and having those breadcrumbs is critical for maintaining the automation long term. Document your flows!ĭocumenting your flow allows the next person, or the forgetful future version of yourself, to understand the overall flow’s objective. In this blog, we’ll discuss best practices, ‘gotchas,’ and design tips to make sure your flows scale with your organization. We’re starting to see a unique collaboration between admins and developers, with both sides learning a little something about Development and Administration. Flow is not just an ‘admin tool’ - it’s the holy grail of declarative development that unites developers AND admins by allowing the use of Lightning Web Components (LWC) and Apex, and letting the admin orchestrate all of it in one place. There’s no way around it: Salesforce Flow is the automation tool of the future. Editor’s note: This post was updated on February 14, 2023, with the latest information and resources.
0 kommentar(er)
