Flow Building 101: Calling Flows from Apex | Danny Gelfenbaum ☁️ posted on the topic | LinkedIn (2024)

Flow Building 101🏄♂️ - SummaryI hope you enjoyed this Flow Building 101 series. There are many more topics to be covered, and I'll cover some in the future, but for now, this series is done 👌For those who may have missed any of the posts, or would like to revisit them, I've compiled the links below:Post 1 - Planning https://lnkd.in/dzRBbztWPost 2 - Types of Flowshttps://lnkd.in/dNdxbHCAPost 3 - Naming Conventionshttps://lnkd.in/dS_eny6UPost 4 - Optimizationhttps://lnkd.in/dw2RccHXPost 5 - Documentationhttps://lnkd.in/devp7gNrPost 6 - User Experience (First 5 principles)https://lnkd.in/d3UNrbYdPost 7 - User Experience (Last 5 principles)https://lnkd.in/dnfgWqGrPost 8 - Debugging and Testinghttps://lnkd.in/dMV3JiN3Post 9 - Advanced Techniqueshttps://lnkd.in/dUydMbQfLet me know if you want me to cover anything specific in the next posts!

8

2 Comments

What happens when standard Screen Flows components are just not enough? Well, you can either develop your own custom LWC or use a 3rd party app.In this video, I review Avonni's Screen Flow components and how they offer enhanced capabilities without the headache of building everything from scratch.Checkout the Avonni Screen Flow components package! https://bit.ly/3x2ChsI#Salesforce #ScreenFlow #Ad

17

7 Comments

Flow Building 101 🏄♂️ - Part 8"Oh, this is such a simple process... I'll just deploy it straight away..." We've all had this thought... Should you do that? NO!!! (See attached GIF)If I had a dollar for every unexpected issue, I'd have a lifetime supply of premium coffee.Why "wasting" time testing?Ensures Functionality➡️Thorough testing confirms your Flow works as intended, meeting requirements and business objectives.Prevents Unintended Consequences: ➡️Testing uncovers that god-forsaken validation rule someone created back in 2016. ➡️Helps identify unintended consequences like incorrect data updates, accidental deletions, or unauthorized access.Enhances User Experience: ➡️Testing reveals "Ah ha!" moments, uncovering forgotten scenarios or improving process paths.➡️Testing as different users can identify potential bottlenecks, confusing steps, or error-prone areas.Saves Time and Resources: ➡️ Testing saves time and resources in the long run. ➡️ Catching and fixing errors early is easier and less costly than in a live environment. ➡️Who knows how many records will get corrupted or how many integrations were falsely triggered before you fix it?How to test? ➡️Positive TestingThe "happy path". It involves testing scenarios where everything goes according to plan. It verifies your Flow's intended functionality with valid inputs.➡️Negative TestingAnticipating the Unexpected. Tests invalid inputs or unexpected conditions to ensure your Flow handles errors like a boss. The goal is to avoid any negative consequences as much as possible.Tools to test➡️Debug Mode: Did you ever encounter Version 142 of a Flow? Don't be that guy. Salesforce's built-in Debug mode lets you step through your Flow, inspect variables, and pinpoint issues before activation.➡️Flow Test Framework: Create automated tests for your Flows by defining inputs and expected outcomes to verify behavior under different scenarios. Not my favorite due to the hassle, but it's an option.➡️Manual Testing: After Debug mode, activate the Flow and test it on a record to catch edge cases or unexpected behaviors, as debug-mode is very limited scope testing (similar to unit testing).A Debugger Mindset 🐞 Debugging isn't just about technical skills; even seasoned veterans can find themselves stumped for hours. Few tips to keep you on track:👉Stay calm: Don't panic about an error. Take a breath, approach the problem systematically. Take a walk if you've hit a wall. 👉Be methodical: Follow a logical process of elimination to narrow possible causes. Don't assume anything! 👉Ask for help: Reach out to colleagues or communities for help. The Ohana is full of amazing and helpful people!Happy debugging!Remember, testing and debugging are essential in the Flow building process.Embrace these practices, and reliable, robust, and ready your Flows shall be. (*Read this with Yoda voice*)Share your most epic debugging stories in the comments.

20

7 Comments

Flow Building 101 🏄♂️ - Part 7User Experience (2nd half)In the previous post, I covered the first 5 principles of UX design. Let's review the next 5 that will make your Flows even more awesome.Recognition Rather than Recall: ➡Don't force users to remember information from previous screens. ➡Display relevant details when needed, and use defaults to pre-fill fields whenever possible.➡Provide guidance on every screen, rather than lay out the whole process at the beginning of itFlexibility and Efficiency of Use: ➡Allow experienced and inexperienced users to navigate through your Flow based on their experience level.➡Consider offering different paths or options based on user needs (e.g., "Review" button, "Select All").➡Keyboard shortcuts are a good example of this principle but unfortunately, this isn't a developed enough feature in Salesforce Flows yet. By the way, try using Ctrl + / to see Salesforce keyboard shortcuts.Aesthetic and Minimalist Design: ➡ Keep your screens clean, uncluttered, and visually appealing.➡Use sections columns width, whitespace, and/or empty sections effectively if needed to organize the data displayed.➡Prioritize the most important information - Highlight it, use a bigger font, or color it.➡Show only the relevant components - Use reactive formulas to display choices based on previous selections! Help Users Recognize, Diagnose, and Recover from Errors: ➡Everyone makes mistakes. When errors occur, provide clear and specific error messages. ➡Offer suggestions for fixing the issue, and make it easy for users to get back on track. ➡Error can be a system error (Validation Rule that fails a record creation), or a business process error (End Date must be at least 2 weeks from Start Date).➡Give a clear and specific message about what is required - instead of “There was an error”. ➡A common example is replacing the generic "An unhandled fault has occurred" with the actual fault message received ({$Flow.FaultMessage}).I’ll take advantage here to elaborate on Error paths:Once the Fault Path is activated, you can take specific actions to handle the error. This could include: →Displaying a user-friendly error message →Logging the error for later analysis →Retrying the failed action (Useful when the record was locked) →Redirecting the user to a different screen →Sending a notification to an admin.Help and Documentation: ➡When all else fails, have a safety net. ➡Provide context-sensitive help and documentation within your Flow. ➡This could include tooltips, links to relevant resources, or even a "Contact Support" button for more complex issues.By implementing these UX principles, you'll be creating Screen Flows that not only function flawlessly but also delight users with their intuitive design and helpful guidance.Feel free to add some principles/examples to create awesome Flow experiences! Share your tips and tricks in the comments! 👇

15

3 Comments

Flow Building 101 🏄♂️ - Part 6User ExperienceEver had to apply for a visa? Maybe fill out some other governmental form that feels like a labyrinth? complete a 10-page long survey? Oftentimes, those have confusing instructions, endless fields, and zero feedback. It's enough to make you want to throw your laptop out the window.Now imagine the opposite: a smooth, intuitive experience that feels like a breeze. You know exactly where to click, and what needs to be filled, and you only see what is actually relevant. That's the power of good user experience (UX) design, and it's essential for creating Screen Flows that people actually want to use.Let's take a look at some UX tips to make your Flows a joy to interact with, drawing inspiration from the 10 general principles for interaction design, written by Jakob Nielsen (Thanks to Alexander Lapa for introducing me to this). Each one of those can be extensively elaborated, so there will be 2 posts dedicated to this subject 😁 Stay tuned!Visibility of System Status: Keep users informed about what's happening at every step of the Flow. ➡Use progress bars, loading indicators, and clear messages to show them where they are in the process. ➡Add a text explaining what is expected of them! (For example - "Select Opportunities to Close Win", before displaying a data table)Match Between the System and the Real World: ➡Speak your users' language. Use familiar terms, avoid nasty unfamiliar jargon, and structure your Flow in a way that makes sense intuitively. If your business treats and calls Opportunity a "Deal", use "Deal" in the Flow. ➡Use custom labels for screen buttons! For opportunity creation, call it "Generate Deal" instead of the standard "Next".User Control and Freedom:➡ Allow users to easily navigate back and forth between screens (if applicable), make changes, and exit the Flow if needed.Consistency and Standards: ➡Use consistent layouts, colors, and terminology throughout your Flow, and possibly all Flows in the org.➡Follow Salesforce's design guidelines to ensure a cohesive experience.Error Prevention: ➡Be proactive, not reactive (except when it comes to reactive screen components). ➡Anticipate potential errors and guide users away from them. ➡Use clear input validation, provide helpful hints, and offer suggestions to prevent mistakes.➡Anticipate possible scenarios and use Decision Elements and/or visibility filters to display only relevant data/choicesBy mastering these principles, you'll be well on your way to creating Screen Flows that users not only tolerate but make them your"raving fan", as Jodi Hrbek puts it. Stay tuned for Part 7, where we'll explore the other 5 UX principles to make your Flows shine!

46

6 Comments

Flow Building 101 🏄♂️ - Part 5The unsung heroes...Knowing your system from start to finish can be quite challenging for someone who just got hired, a partner, or even for experienced admins in a complicated org. Imagine being asked to fix a critical bug in Production when you have no idea how to reproduce the issue, where it lies, and the purpose of each element in the process once you find it. It can be a little overwhelming, right?Let's shine a spotlight on these unsung heroes and discover how they can save your Flows (and your sanity). Yes, I'm talking about *documentation*.Here's why documentation matters:➡️Clarity: Documented processes are easier to understand, troubleshoot, and maintain. No spent hours deciphering what someone built years ago. ➡️Collaboration: In a team, documentation ensures everyone is on the same page. No "What does this element do again?" questions. ➡️Knowledge Transfer: Makes the transition seamless if you ever need to hand off your Flow to someone else.How to document? An external system like Confluence library or Google Docs is good for big processes or general business documentation, but as SaaS (Salesforce org) changes so frequently, documenting everything is just too much of a hassle.Use the system itself to document the system! Salesforce provides some handy tools to do that:➡️Description Fields: Focus on WHY, not WHAT, as that's self-explanatory from the element action. For example, "checks Invoice type (what) to decide if a refund or a charge needs to be triggered (why). This applies to Fields as well.➡️Version Control: The time machine. A lot can be said about that, and for the hard-core CICD pros here, follow Pablo Gonzalez to dive into this. I'm going light here and talking about Flow versions. It allows you to track changes, and revert to previous versions if needed. To use this properly, the Flow version description must have the essence of the version change. **Here's a quick tip on the description in Flows - The Flow description doesn't have to be the version description! It is by default and changes every new version, but if you go to "View Details" > Edit, you can set the Flow description differently than the version's. Put the PURPOSE of the Flow there, and each version the essence of the version change!➡️Custom objects - If you haven't put ticketing in your org yet, stop everything and go do that. Just Google "Salesforce ticketing system" and you'll find plenty of examples. Use the tickets to document changes and even consider putting those tickets as referrals on description fields for more context.➡️Making documentation a habit - The best time to document your Flow is while you're building it. Take a few extra minutes to add descriptions to each element, and use version control to keep track of your progress. Trust me, your future self (and your colleagues) will thank you!What are your tips for documenting?Share your best practices in the comments below! 👇

12

6 Comments

Flow Building 101 🏄♂️ - Part 4Need for Speed: Optimizing Salesforce Flows Picture this: You're invited to a party at a friend's house. At first, just a couple of friends arrive, and the party is going well. As the night progresses, more and more people join the small cramped space. At some point, you have to walk on your side like a crab among the people to get a beer, the table lamps are all broken, and you're losing your voice just to speak with the person in front of you.Salesforce Flows can be a bit like that party. When your org is small, it runs smoothly. But as your business grows and your data volume increases, those Flows can hit a wall – AKA Salesforce's governor limits. Contrary to your friend who did not enforce any limits on his party, Salesforce governor limits do - they prevent your org from using too many shared resources and impacting everyone else's performance.If your Flows aren't optimized, they can hit these limits quickly, leading to errors, timeouts, and a whole lot of frustrated users.What to do then? Bulk up your Flow 💪Bulkification is taking a pile of things you need to do and doing them at once instead of one at a time. For example, try to send someone $1000. If you would send $1 at a time, it would take a thousand transactions, a ton of fees, and probably a very confused recipient! Bulkification is like sending that whole amount in one go – it's faster and more efficient, and the money is well received!In practice: ➡️DML Optimization - treat DML operations (insert, update, delete) as an expensive resource. You want to make them count! ➡️Use entry conditions - Don't run a process that doesn't need to run! ➡️If at some point the process is no longer relevant (due to some condition), terminate it as early as possible and prevent it from executing all of the rest of the logic. ➡️Choose the right trigger type - Use the "Fast Field Updates" option for record-triggered flows when your primary goal is updating fields on the triggering record. This significantly improves speed and does not consume a DML! ➡️Avoid unnecessary updates: Only update records that have actually changed! There's no need to re-save a record if nothing has been modified. Use a decision element to check that. ➡️Selective filters: Use filters to narrow the queries (GET elements) and retrieve only the needed records. ➡️Batch the updates: Instead of updating each record individually, collect them in a list and perform a single update operation. ➡️Schedule it (if applicable): If a Flow doesn't need to run in real-time, consider moving the logic to a scheduled Flow or Asynchronous path.By implementing these optimization techniques, you can significantly improve the performance of your Flows, even when dealing with large volumes of data. This will allow scalability and smooth growth of the org!Any tips for optimizing Salesforce Flows you'd like to add? Share your knowledge in the comments below! 👇

45

12 Comments

Flow Building 101 🏄♂️ - Part 3 Why naming conventions matterEver tried reading a book where all the characters had names like Bob, Bobette, and Bobby? It would get pretty confusing, right? The same goes for building Flows in Salesforce. Without a consistent naming system, your beautiful automation can quickly become a mess of elements, variables, and resources.Let's talk about why naming conventions matter and how to make your Flows as easy to read as your favorite novel.👨⚖️ The Case for ConsistencyNaming conventions are the grammar of your Flow. They create a structure and predictability that make your Flow easier to understand for both yourself and anyone else who might need to work on it in the future.Here's what you gain: ➡Readability - Imagine trying to debug a Flow where everything is named "Action1," "Decision1," and "VariableA.". There is no need to image really, just open a Process Builder as a Flow - not for the faint of heart. It can make me smack my keyboard like a "German Kid Keyboard Smasher" (Search it on YouTube). With descriptive names, you can quickly grasp the purpose of each element. ➡Maintainability: As your Flows grow and evolve, consistent naming makes it much easier to update and modify them without breaking anything. ➡Collaboration: When you're working with a team, clear naming conventions ensure everyone is on the same page, preventing miscommunication and errors.Naming convention principles: ➡Be descriptive and meaningful - Choose names that accurately reflect the purpose(!) or content (e.g f_CalcDaysBetweenDates) ➡Be consistent - Same Styling for elements. For example, use camelCase for variables (e.g., firstName) and snake_case for constants (e.g., MAX_VALUE). ➡Prioritize readability - Favor clarity over saving characters. While short names might seem convenient, they can become cryptic (especially over time) if they don't convey meaning. Use full words or abbreviations that are easily understood by other developers. (For example - OppToBeCreated and not var_o) ➡Prefixes and Suffixes - little labels you can add to your Flow elements to give them extra context (var_NewAccount for variable, f_CalculateExpirationDate for formula, etc)You can even create your own system of prefixes and suffixes as long as it's consistent throughout your Flow.⭐ Bonus Tip:Don't forget about the Description field for the resource! Use it to add even more detail about what each element, variable, or resource does, and more importantly - WHY (so you won't scratch your head to understand the purpose behind it 6 months later).There's no one-size-fits-all naming convention. The most important thing is to choose a system that works for you and your team and stick to it. By implementing a few simple guidelines, the future you will thank you.I’ll put in the first comment a great resource to dive deep into naming conventions!

21

9 Comments

Flow Building 101 - Part 2All right, so you've got your plan in hand – now it's time to pick the right tool for the job! Salesforce offers different types of Flows, each with its own unique strengths and ideal use cases.⚠️ Just an important point on this matter - Sometimes, Flow will NOT be the right tool at all... There are many standard salesforce features (Assignment rules, roll-up fields, approval processes, Lightning record pages, and so on) that will make the Flow building unnecessary. And when it's too complicated, a custom Apex/LWC development may be the best route to go.This is going to be boring to advanced admins but important nonetheless. Let's dive into the Flow types:Screen Flows ➡️Think of Screen Flows as your interactive tour guides. ➡️This would be the right choice when human interaction is needed.Autolaunched Flows ➡️Call it whenever you need it. It's basically a plug-in Flow, called by some other process. ➡️This is truly an amazing tool when you need the same or similar process invoked from different sources. ➡️For example, You can create an "Invoice" record when a user produces an invoice manually, or when a scheduled process runs. Both can use the same logic in the auto launched Flow! I think this is one of the most underrated flow types!Scheduled Flows ➡️Automate a task at a specific time or interval. ➡️A common use case can be an email reminder - nudge users with reminders for upcoming deadlines or events. ➡️Use Formula fields to calculate when to run the Flow! Record-Triggered Flows ➡️Those are by far the most common. ➡️Always on the lookout for specific record changes (and they damn better be specific - DO NOT use "No Entry". More on that in the next posts). ➡️This one has the most optimization considerations needed as it shares the Governor Limits with ALL other processes in the same transaction (i.e, the same record change lifecycle), including other Flows, Apex, Workflows and Process Builders (god forbid).Platform Event-Triggered Flows ➡️The more advanced type. ➡️Those Flows listen for events happening in Salesforce or external systems and react in real-time. It's a bit more complicated and requires a Platform Event object. ➡️The great benefit of this type is the scalability - each Flow run is a completely new transaction, separated from what triggered it!The variety of types of Flows keeps getting bigger, but those are the essential ones.The right Flow type depends on your specific use case and automation goals. By understanding the different types of Flows and their triggers, you'll be well-equipped to choose the right tool for the job and build automation that achieves your business process goal and empowers your users.Attached is Salesforce Ben's amazing infographic of Flow Types and when to use them.What is your favorite Flow type? Have you built any awesome Flows lately? Share your favorite use cases in the comments! 👇#Salesforce #FlowBuilder #Automation

211

13 Comments