Checklist progress
0/282Learned
Platform Administrator
Study Checklist
Checklist progress
0/282Learned
Given a scenario, identify the appropriate automation solution based on the capabilities of the tool
0/5
Describe capabilities, use cases, and configuration for Flow
0/14
Screen versus record-triggered versus autolaunched flows
Learn this conceptGet, Create, Update, and Delete records in Flow
Learn this conceptScreen elements and input components in Flow
Learn this conceptScreen flow launch and distribution options
Learn this conceptRecord-triggered flow object and entry configuration
Learn this conceptEntry conditions versus Decision elements
Learn this conceptBefore-save versus after-save record-triggered flows
Learn this conceptScheduled paths on record-triggered flows
Learn this conceptAutolaunched subflows for reusable logic
Learn this conceptSchedule-triggered autolaunched flows
Learn this conceptRecord-triggered flows in the save order of execution
Learn this conceptFlow activation and version management
Learn this conceptManage Flows versus Run Flows permissions
Learn this conceptDescribe capabilities, use cases, and configuration for the approval process
0/12
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Administrator studiers. 593 members and growing.
A scheduled path is a delayed branch on a record-triggered flow: the record change still starts the work, but some actions wait until a time you pick. That time comes from the create or update event itself or from a date field on the record, then shifts by an offset such as five days after Close Date or one month before a warranty date. Use a scheduled path when one record change should cause a later follow-up; use a schedule-triggered flow when you want a clock-based job that can repeat daily or weekly without depending on that change.