Define the Commit Mode in the scheduling policy to determine what happens when schedule conflicts occur during global, in-day, or resource schedule optimization.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| The Agentforce Field Service and Operations core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions. |
| User Permissions Needed | |
|---|---|
| To enable optimization overlaps prevention: | Custom permission set: FSL Admin Permissions |
| To run Resource Schedule Optimization (RSO), in-day, or global optimization: |
One of these custom permission sets:
|
This is a Field Service managed package feature.
The Commit Mode field in the scheduling policy determines how the system handles schedule changes made during an optimization run. For example, if a dispatcher reschedules an appointment or schedules a new job, creating discrepancies between the schedule's state at the start and completion of optimization. These changes can cause scheduling conflicts. Make sure the Commit Mode field is added to the Scheduling Policy page layout.
- Create and manage scheduling policies from the Field Service Admin app in the Field Service settings tab. Click Go to Guided Setup under Getting Started, or click New in the Scheduling Policies tab under Scheduling.
-
Select the scheduling policy Commit Mode according to the guidelines.
Note When you aren’t using Enhanced Scheduling and Optimization, global optimization runs in the Always Commit mode regardless of the Commit Mode setting.