As of Summer ’23 new Salesforce orgs have Enhanced Scheduling and Optimization enabled
for all service territories. Existing orgs can switch to use Enhanced Scheduling and Optimization
for all service territories or per territory. Enhanced Optimization per Territory enables you to
deploy Enhanced Scheduling and Optimization only on selected territories, for example, territories
with simpler scheduling scenarios. This gradual rollout lets you keep the more complex scheduling
scenarios for later releases, when all the service territory features are supported.
Required Editions
| Available in: Available in Lightning Experience and Salesforce Classic in these
editions where Field Service is enabled: Enterprise, Unlimited, and
Developer Editions
|
| User Permissions Needed |
| To enable Enhanced Optimization Per Territory: |
Customize Application |
This is a Field Service managed package feature.
Before you set up enhanced optimization for all or selected territories, make sure that you
meet these requirements.
- Field Service is enabled.
- The latest version of the Salesforce Field Service managed package is installed.
- Enhanced Scheduling and Optimization is enabled.
To enable all service territories to use Enhanced Scheduling and Optimization, in Field
Service Settings, select and then select Use enhanced scheduling and optimization for all
service territories.
Use Enhanced Scheduling and Optimization when service appointments or service resources don't
have an associated service territory. In Field Service Settings, select and then check that Use enhanced scheduling and optimization when
there isn’t an associated service territory is enabled.
If you're using Enhanced Scheduling and Optimization per territory, the operation
you’re performing determines the selected optimization engine.
- For service appointment operations (Drag and Drop, Get Candidates, Schedule, Unschedule, and
Check Rules), the associated territory of the appointment determines the optimization engine.
- For global optimization operations, the selected territory determines the optimization
engine.
- For resource absence operations (Drag and Drop, create new, and delete), the resource’s
associated territory member determines the optimization engine.