Learning Salesforce Flows

Learning Salesforce Flows for Propertybase Admins

Getting Started

• If you are migrating to Flows from Process Builder and you are just getting started with Learning Flows, we would recommend to learn basic Record-Triggered Flows first
• Although you can use the migration tools, it is a good idea to practice building a Record-Triggered Flow from scratch, so that you can familiarise yourself with the flow builder interface
• Practice creating a basic Record-Triggered Flow to perform basic actions such as send an email, update a field and update related records
• Flow errors:?review any flow errors in Set up > Process Automation > All Failed Flow Interviews. The Propertybase Admin will also receive an email with the details.
• Understand the following A-Z Flow terminology

A-Z

Action Elements 
  Is a step that instructs the flow to perform 
  specific tasks or operations to automate processes within Salesforce.
Drag Selection
  Allows you to highlight multiple elements at 
  once by clicking and dragging your cursor over them, simplifying
  the process of connecting and configuring elements in the flow.
Elements
  Are building blocks that represent individual tasks or actions
  Flow Builder, Flow Debug Tool, Flow Element : Update Records
Flow Loop Variables
Flow Orchestrator
Flow Types
Resources
  Are reusable pieces of data or information, such as variables 
  and record-related data, that can be used throughout the flow to
 store, manipulate, or access information as needed.
Variables 
  Are like containers that hold and store data temporarily 
  during the flow's execution, allowing you to use and manipulate 
  the information as the flow progresses.        

10 Best Practices & Tips for Record-Triggered Flows

1. Include an entry criteria - this will limit the number of records that will trigger the flow. And then this?reduces the number of times a Flow is called, which help to improve performance during the Flow execution.
2. Labels & Descriptions - use proper labels and descriptions when creating elements or resources in your flow, as this will help for readability when you or others edit/add to your flow.
3. Updating related records - you no longer need to use the loop element to update related records, which simplifies this type of flow. Now you can simply directly update all of the related records in an update action.
4. Created & Edited Flow, Check for New Records for a "Before Save" Record Triggered Flow - Use the criteria "ID" is null = TRUE which denotes the create scenario since the Id gets created only after record is created.
5. Created & Edited Flow, Check for New Records for a "After Save" Record Triggered Flow - Use the criteria "CreatedDate" ischanged = TRUE to detect the created scenario.
6. Formula entry criteria - you can now use a formula to check ISCHANGED, ISNEW fields etc in the entry criteria.
7. Debug & Test Before you are activating a flow, ensure you have tested your new flow.
8. Test your?record-triggered flow:?Whenever you are creating any record-triggered flow, make sure you are testing it with 5 to 10 records. This is to ensure the functionality works with multiple records with different scenarios as well.
9. Document your Flows - outlining the purpose of the flow and ensure consistent naming and across elements & variables.
10. Don't hardcode Record IDs - instead of hardcoding record IDs it is best to use a formula for your entry conditions and this will allow you to reference a Record Type's DeveloperName OR you can use the get records element.

For more information on Flows and how-to-guide check out RoundRock's page on Flows here .