Managing Scheduling and Optimization28% of the exam
Complex work dependencies and scheduling limits
Model multistage jobs with scheduling dependencies: set up complex work, pick Same Start, Start After Finish, Start After Finish and Same Day or Immediately Follow, and apply the engine-specific limits on chain size, all-or-none scheduling, territories, capacity-based resources and multiday work.
Given a scenario, determine the appropriate option to execute Complex Work in Agentforce Field Service and Operations.
~6 min read · 7 practice questions ·
What the exam expects
- Set up complex work, including the work order parent requirement and the per-territory switch for the legacy engine.
- Choose Same Start, Start After Finish, Start After Finish and Same Day or Immediately Follow from a job's sequencing requirement.
- Apply engine-specific limits: chain size (five versus two for Immediately Follow), all-or-none scheduling and how many appointments are enforced at once.
- Troubleshoot unscheduled chains: territories missing from the optimization request, pinned but unscheduled links, capacity-based resources and multiday appointments.
Key terms:
- Complex work (scheduling dependency, multistage work): relationships between service appointments that scheduling must respect.
- Dependency type: the logic relating two appointments, such as Same Start.
- Dependency group (chain): the set of related appointments in a service appointment's Scheduling Dependencies section.
- All-or-none scheduling: every appointment in the chain is scheduled, or none is.
- Consecutive work: appointments linked with Immediately Follow.
Key facts
Parent record
- Detail
- Each dependent appointment's parent must be a work order
Setup
- Detail
- Update layouts, activate dependency types, enable for non-enhanced territories
Immediately Follow
- Detail
- Same day, back to back, same resource
Enhanced dependency group
- Detail
- Up to 5 appointments scheduled automatically
Legacy Immediately Follow
- Detail
- 2 appointments; error on a third
Enhanced all-or-none
- Detail
- Always applied to the chain
Legacy enforcement
- Detail
- Two appointments at a time, even with all-or-none selected
Multi-territory chain
- Detail
- Select all its territories in the optimization request
Capacity-based resources
- Detail
- Not assigned by scheduling or optimization in a dependency group
Multiday plus complex work
- Detail
- Not supported; scheduled end isn't calculated
Emergency action
- Detail
- Doesn't support appointments with a scheduling dependency
- Why can't the Time Dependency and Same Resource fields control a chain in an enhanced-engine territory?
- When does a pinned appointment stop an enhanced-engine chain from being scheduled?
- Why is the Emergency action a poor fit for an appointment with a scheduling dependency?
- Which resources can't scheduling or optimization assign to a dependency group?
- When does legacy-engine optimization treat the appointments of a dependency group as pinned?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Agentforce Field Service and Operations Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 38 lessons of the Agentforce Field Service and Operations Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both