Checklist progress
0/316Learned
Platform App Builder
Study Checklist
Checklist progress
0/316Learned
Given a scenario, demonstrate the use of formula fields to meet stated business requirements.
0/15
Given a scenario, determine the capabilities, use cases, and implications of roll-up summary fields.
0/9
Given a scenario, demonstrate the use of validation rules to meet stated business requirements.
0/14
Create and configure flows using Flow Builder
0/21
Flow Builder elements, connectors, and resources
Learn this conceptCreate and delete records in Flow Builder
Learn this conceptUpdate Records versus assigning $Record
Learn this conceptDecision outcomes and the default outcome
Learn this conceptLoops and bulk DML in Flow Builder
Learn this conceptCollection Filter, Sort, and Transform
Learn this conceptScreen components and input validation
Learn this conceptChoice resources versus picklist and record choice sets
Learn this conceptEntry conditions and when-to-run on update
Learn this conceptScheduled path time source and offset
Learn this conceptAsynchronous paths on record-triggered flows
Learn this conceptCustom Error on record-triggered paths
Learn this conceptHTTP Callout from Flow Builder
Learn this conceptDescribe the capabilities and use cases for Flow Approval processes
0/13
Given a scenario, determine the appropriate flow type to meet stated business requirements
0/5
Maintain, monitor, and troubleshoot flows
0/11
Describe the capabilities and use cases for using Agentforce to automate business processes
0/9
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.
When a Salesforce flow reads or writes records, it does so either as the person who started it or as the system. That run context decides whether the starter's object, field, and record access apply, or whether the flow can see more (or all) data. Who may start or resume a given flow is a separate access check from that data context.