Managing Scheduling and Optimization28% of the exam
Global, in-day and resource schedule optimization
Choose between global optimization, in-day optimization, Resource Schedule Optimization and scheduling recipes from the scope, the time pressure and the trigger, including in-day run times by engine and the settings a dispatcher picks for one resource.
Given a scenario, decide the appropriate type of optimization service to use.
~7 min read · 6 practice questions ·
What the exam expects
- Choose global, in-day or Resource Schedule Optimization (RSO) from the scope (territories or one resource), the horizon and how fast the result is needed.
- Configure a policy for in-day optimization and state its run time with and without Enhanced Scheduling and Optimization.
- Name the settings a dispatcher chooses when launching RSO, and tell them apart from scheduled job settings.
- Recommend scheduling recipes for hands-off responses to schedule events, and say what replaces them on the enhanced engine.
Key terms:
- Global optimization: optimizes one or more territories across a range of days; the most thorough option.
- In-day optimization: a fast run for one or more territories on the day of service, set by the In-Day Optimization field on a policy.
- Resource Schedule Optimization (RSO): optimizes one service resource's schedule after last-minute changes.
- Scheduling recipe: an automated optimization response to an event such as a cancellation, time change or overlap.
- Optimization horizon: the range of days considered available for scheduling in a request.
Key facts
Global optimization
- Detail
- Most thorough; can take several hours
Global run cadence
- Detail
- Regularly, for example every night, or manually
In-day run time
- Detail
- Up to 5 minutes enhanced; up to 10 minutes without
In-day best span
- Detail
- Current day or at most 2 days
In-day switch
- Detail
- In-Day Optimization field on the scheduling policy
Who runs in-day
- Detail
- FSL Admin Permissions or FSL Dispatcher Permissions
RSO launch
- Detail
- Resource's name on the Gantt, three dots, Resource Schedule Optimization
RSO options
- Detail
- Time horizon, policy, candidates, keep scheduled, only assigned appointments
Recipes on the enhanced engine
- Detail
- Fix Schedule Overlaps flow (Beta) replaces them for late-finish overlaps
Legacy 24-hour limit
- Detail
- 50,000 appointments; only global, in-day and RSO requests count
Sources for this section (5)
- In-Day Optimizationhelp.salesforce.com (opens in a new tab)
- Optimize Your Schedulehelp.salesforce.com (opens in a new tab)
- Handle In-Day Changestrailhead.salesforce.com (opens in a new tab)
- Scheduling and Optimization Serviceshelp.salesforce.com (opens in a new tab)
- Enhanced Limitshelp.salesforce.com (opens in a new tab)
- When is in-day optimization unavailable on a legacy-engine territory?
- Why can a dispatcher with only FSL Dispatcher Permissions run in-day optimization but not configure its policy?
- Which setting keeps statuses unchanged during in-day runs?
- Why can't a dispatcher set territory groups when launching RSO?
- When does the Fix Schedule Overlaps flow replace scheduling recipes?
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 (6 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