Week 2 — Salesforce Flow & Automation

Short, point-wise study notes for Salesforce Admin / Developer preparation

1. Business Process Automation

• Automation = Salesforce performs repetitive tasks automatically.

• Benefits: saves time, reduces manual work, improves data accuracy, and ensures processes are followed.

• Interactive: Screen Flow, Autolaunched Flow, Approval Process.

• Behind the scenes: Record-Triggered Flow, Schedule-Triggered Flow, Platform Event-Triggered Flow, Apex.

2. Salesforce Flow
• Salesforce Flow = overall Salesforce automation technology.

• Flow = saved automation that performs a business process.

• Flow Builder = tool used to create and manage flows.

• Flownatic = someone who enjoys creating flows.

3. Flow Builder
• Three building blocks: Elements, Connectors, Resources.

• Toolbox = elements and resources.

• Canvas = area where the flow is built.

• Button Bar = Save, Run, Debug, Activate, Undo, etc.

4. Flow Elements
• Interaction: Screen (user input/output), Action (email, approval, Chatter, etc.), Subflow (calls another flow).

• Data: Get Records, Create Records, Update Records, Delete Records.

• Logic: Assignment, Decision, Loop, Collection Sort, Collection Filter.

5. Flow Resources
• Variable = stores a changeable value.

• Constant = stores a value that cannot change.

• Formula = calculates a value.

• Text Template = stores reusable text.

• Record Variable = stores fields of one record.

• Record Collection Variable = stores multiple records.

6. Variables
• Variable = a temporary container for information used by a flow.

• Types: Text, Number, Currency, Boolean, Date, Date/Time, Record.

• Boolean = True/False.

• Record variable can store all field values for one Salesforce record.

• Each flow run starts variables with their default values.

7. Get Records
• Get Records retrieves data from Salesforce.

• Typical configuration: choose Object → set Filter Conditions → choose how many records to store.
• Example: find a Contact whose Email matches the email entered by a user.

8. Decision Element
• Decision creates different paths based on conditions.

• Example: Contact found? → Yes: update; No: create.

• Common operators: Equals, Greater Than, Less Than, Is Blank, Contains.

9. Assignment Element
• Assignment changes or stores values in variables.

• Example: [Link] ID = Find a [Link] ID.

10. Create Records

• Create Records creates new Salesforce records.

• Example: if no duplicate Contact is found, create a new Contact from a record variable.

11. Update Records

• Update Records changes an existing Salesforce record.

• Example: set the existing Contact ID, then update the Contact using the record variable.

12. Screen Flow Project

• Collect Contact information → Find matching Contact → Decision → ask whether to update → Update existing OR Create new →
show confirmation/link.

• Basic path: Start → Contact Info → Find a Match → Match Found? → Update/Create.

13. Approval Process

• Approval Process automates record approval/rejection.

• It defines entry criteria, approvers, approval steps, and actions.

• Initial Submission Actions: happen when submitted; can lock record, update field, send email, etc.

• Final Approval Actions: happen after all required approvals; can update status, send email, unlock record.

• Final Rejection Actions: happen when request is finally rejected; can update status, clear fields, send email.

14. Validation Rules

• Validation Rule prevents users from saving invalid data.

• Example: Has Support Plan = True AND expiration date is blank → prevent save.

• Example: Stage = Closed Lost AND Close Reason is blank → prevent save.

• Validation rules can affect existing records when those records are edited/saved.

15. Flow Builder vs Process Builder

• Flow Builder is more powerful and feature-rich and is the preferred modern automation tool.

• Process Builder is an older automation tool with fewer capabilities.

• Use Flow for new automation where appropriate.

16. Run vs Debug

• Run executes the latest saved version and can change real Salesforce data.

• Debug executes with extra information to help understand and troubleshoot the flow.

• Memory: Run = Execute; Debug = Execute + Investigate.

17. Flow Interview
• Flow Interview = one running instance/execution of a flow.

18. Scheduled Path

• Scheduled Path runs part of a flow at a specified time.

• Example: Opportunity closes → wait 7 days → send follow-up.

19. Flow Loop

• Loop processes records in a collection one by one.

• Useful when the same logic must be applied to multiple records.

20. Flow Troubleshooting

• Common causes: faulty logic, blank/null values, permissions, incorrect configuration, invalid data, or code problems.

• Steps: check errors/warnings → Debug → inspect variables → check Get Records → check Decision conditions → verify
permissions → fix → test again.
Quick Revision — Most Important
Topic Remember

Automation Performs tasks automatically

Flow Automation process

Flow Builder Tool to build flows

Element Performs a step

Connector Controls the flow path

Resource Stores/calculates information

Variable Stores a changeable value

Get Records Retrieves data

Create Records Creates records

Update Records Updates records

Assignment Changes a variable value

Decision Creates conditional paths

Loop Processes multiple records

Screen Gets/displays user information

Approval Process Automates approval/rejection

Validation Rule Prevents invalid data

Run Executes the flow

Debug Executes + helps troubleshoot

Flow Interview One flow execution

Scheduled Path Runs at a scheduled time

Exam focus: Flow → Flow Builder → Elements → Get Records → Decision → Assignment → Create/Update Records → Variables → Screen
Flow → Record-Triggered Flow → Approval Process → Validation Rules → Debug.