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
Describe 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
Screen Flow versus Autolaunched Flow (No Trigger)
Learn this conceptRecord-triggered Flow versus user-launched flows
Learn this conceptFast Field Updates versus Actions and Related Records
Learn this conceptSchedule-triggered Flow versus scheduled paths
Learn this conceptMaintain, 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.
Record-triggered flows start themselves when a Salesforce record is created, updated, or deleted, then finish in the background with no screens and no person driving the run. User-launched flows start only when someone (or a process they choose) invokes them: a screen flow walks a person through pages of questions and information, while an Autolaunched flow with no trigger runs silently after a button, Apex, API, orchestration, or another flow starts it. Pick the type by whether the business event is a record change that must always fire, or a person or caller who must decide when to start.