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.
Scheduled paths and schedule-triggered flows both wait for a clock, but they start for different reasons. A scheduled path is a delayed branch on a record-triggered flow: a record is created, updated, or deleted, then part of that same flow runs later, or before or after a date on that record, once per trigger. A schedule-triggered flow is a separate autolaunched flow that starts at a date and time you set, can repeat daily or weekly, and can process a batch of records that match filters without anyone changing a record.