---
sourceDocument: Brazil Field Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/field-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# System properties

# Dynamic scheduling system properties {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Dynamic scheduling system properties

Dynamic scheduling system properties in ServiceNow allow you to customize and control the behavior of the dynamic scheduling process to fit your organization's specific needs.
These properties influence task assignment frequency, automatic dispatching, travel time calculations, and optimization iterations.
Proper adjustment of these properties enhances task assignment efficiency, scheduling accuracy, and overall workforce optimization.
Show full answer Show less  

## Key Features

* **Manual Double-Booking:** Enables dispatchers to manually double-book agents even when dynamic scheduling is active.
* **Travel Time Considerations:** Options to ignore travel time during scheduling, optimize travel time ratings based on different travel inclusion methods (to task, after task, all travel, or no travel), and configure travel calculation methods using Google Maps API, Beans.AI, or straight-line estimates.
* **Agent Recommendation Logs:** Option to display advanced logs showing recommended eligible agents to dispatchers for better decision-making.
* **Dynamic Bundling:** Ensures tasks in Pending Dispatch state are bundled before dynamic scheduling runs, improving task grouping efficiency.
* **Travel Time Threshold Assignment:** Allows assigning tasks to the nearest agent within a configurable travel time threshold, regardless of availability.
* **Work Schedule Enforcement:** Enables dynamic scheduling to strictly use default work schedules or workforce optimization schedules when assigning tasks.
* **Window Start and End Dates Handling:** Dynamic scheduling uses Window start and end dates on work order tasks to determine scheduling windows. There are detailed rules on how these dates are set or defaulted based on SLA, appointments, transfer orders, and manual overrides.

## Practical Use and Configuration

Navigate to **All \> Field Service \> Dynamic Scheduling Administration \> Properties** or directly access the **sysproperties** table to configure these system properties. Key property settings include enabling or disabling double booking, selecting travel time calculation methods, adjusting travel time thresholds for task assignments, and configuring how travel time affects route optimization.

Understanding and correctly configuring Window start and end dates on work order tasks is critical for accurate scheduling. These dates influence when tasks are considered within the scheduling window and can be automatically or manually set based on SLAs, appointments, or transfer orders.

## Why It Matters

By tailoring these dynamic scheduling properties, ServiceNow customers can:

* Improve task assignment efficiency by optimizing agent workloads and travel routes.
* Ensure scheduling aligns with business priorities such as on-time arrivals and route efficiency.
* Enable dispatchers with enhanced control and visibility through features like double booking and advanced recommendation logs.
* Customize scheduling windows to reflect operational realities and SLA commitments.

## Expected Results

Configuring dynamic scheduling system properties allows your organization to achieve optimized task dispatching that respects travel times, agent availability, and scheduling constraints. This leads to improved technician utilization, reduced travel costs, and better adherence to service commitments.  
Set up properties to customize the behavior and functionality of the dynamic scheduling process according to your organization's needs.
The following properties allow you to control aspects such as the frequency of scheduling, automatic assignment, travel time calculations, and optimization iterations. Adjusting these properties helps optimize task assignments,
improve efficiency, and align the dynamic scheduling process with your specific requirements.

Navigate to AllField ServiceDynamic Scheduling AdministrationProperties, or go to `sys_properties` table if you can't find the property in Dynamic Scheduling Administration.  
{#dynamic-sched-system-properties__table_fyv_dtr_bs__entry__3}

| Property label | Property name | Description |
|-|-|-|
| Allow dispatchers to manually double-book agents | work.management.allow. doublebooking.dynamicscheduling | Allows dispatchers to double-book agents manually even when dynamic scheduling is enabled. * Type: true/false * Default value: false {#dynamic-sched-system-properties__ul_jzn_t5b_dzb} |
| Property to ignore calculation of travel time for agents to task location based on schedule | com.snc.dynamic.scheduling. ignoreAgentTravelTimeDuringScheduling | Assigns work order tasks automatically without considering travel time for agents. The Ignore Travel option appears in the work order task form, allowing dynamic scheduling to assign tasks to the highest ranked agents regardless of travel time. Set up the following parameters related to dynamic scheduling when Ignore Travel is enabled: Note: * Double booking must be enabled for the system to assign tasks to the agent automatically. * If access hours are defined in a work order task, the system ignores the defined access hours limit when auto-assigning that task to agents. Access hours are activated using Field Service Access Hours Management (com.snc.fsm_access_hours) plugin. {#dynamic-sched-system-properties__ul_lpj_xms_bzb} * Type: true/false * Default value: false {#dynamic-sched-system-properties__ul_c4t_dvb_dzb} |
| Optimize work block travel time rating | com.snc.dynamic.scheduling.optimize_travel_time_rating | Optimize work block travel time rating. * Type: choice list * Default value: Include all travel {#dynamic-sched-system-properties__ul_jmg_pvb_dzb} The following is more details on the property options: * Include travel to task - Ideal when on-time arrival is a key business metric. Only the time it takes to travel to the task is considered in the rating. Any travel after the task is ignored for scoring. * Include travel after task - Ideal when the order of tasks matters and incorrect sequencing could increase overall route time. This is best if you want to factor in the impact a task has on travel time to the next task. This method ignores how far the agent has to go to the task, but includes the impact that traveling to the task has on the rest of the route. * Include all travel - This is ideal for route efficiency if you want to minimize the total travel time across a technician's day. This method considers both the travel to a task, and the travel after a task. * Include no travel - Ideal for remote tasks, virtual support, or dispatch scenarios where the technician is static since travel is not a factor in work block rating. {#dynamic-sched-system-properties__ul_rxg_hmj_qfc} |
| Travel calculation method | work.management.travel.calculation. dynamic_scheduling | Uses Google Maps API, Beans.AI, or straight line estimates to calculate estimated agent travel time and distance to task locations when agents are assigned tasks using dynamic scheduling. |
| Distance calculation method | work.management.distance.calculation.dynamic_scheduling | Calculates agent's estimated travel time and distance to the task location based on either Google Maps API, Beans.AI, or straight-line. If the Use Google Maps API for travel time estimates geolocation property is enabled, then you can select Google Maps API or straight-line estimates in the properties for calculating estimated travel time and distance. If the Use Google Maps API for travel time estimates is not enabled, then the system uses the value in the Estimated Travel Duration field in the work order task to determine task assignment for the agent. * Type: choice list * Default value: Use straight line estimate. {#dynamic-sched-system-properties__ul_am1_4xb_dzb} |
| Show advanced agent recommendation logs to user | com.snc.dynamic.scheduling.showlogs | Displays recommended eligible agents to the dispatchers while scheduling the tasks using dynamic scheduling. Type: true/false Default value: false |
| Dynamic Bundling before Dynamic Scheduling | com.snc.dynamic.scheduling.bundle_before_scheduling | Ensures dynamic bundling runs before dynamic scheduling. Tasks in the Pending Dispatch state are bundled before running dynamic scheduling. * Type: true/false * Default value: false {#dynamic-sched-system-properties__ul_wsg_s5b_dzb} |
| Enable the feature of assigning task to agent with travel time within threshold | work.management.enable.optimizing.travel | Enables dynamic scheduling to assign work order tasks to the nearest agent regardless of availability. * Type: true/false * Default value: false {#dynamic-sched-system-properties__ul_jtw_1jh_dzb} |
| Assign task to agent with travel time within the threshold in minutes | work.management.travel.time.threshold.minutes | Sets the travel time (in minutes) that assigns a work order task to the nearest agent if they are within the travel distance. * Type: integer * Default value: 5 {#dynamic-sched-system-properties__ul_axr_cjh_dzb} |
| Allow Dynamic Scheduling to only use work schedule/WFO | com.snc.dynamic.scheduling.useWorkScheduleOnly | Enables the default work schedule to be used when scheduling agents with dynamic scheduling and workforce optimization. * Type: string * Default value: true {#dynamic-sched-system-properties__ul_d4r_rpw_2bc} |
[Table 1. System properties for Dynamic scheduling]

{#dynamic-sched-system-properties__table_fyv_dtr_bs}

## Work Order Task Start and End Dates {#dynamic-sched-system-properties__section_xhc_vtb_dzb}

Dynamic scheduling uses Window start date and Window end date field values in the work order task to schedule tasks. Additionally, the system properties, business rules, and client scripts are considered during set up and configuration.

* If both the Window start and Window end dates are present in the work order tasks, dynamic scheduling uses these dates.
* If the task has a Window start date but the date has passed, dynamic scheduling uses the current date and time for this value.
* If the task has a Window start date but no Window end date, dynamic scheduling uses the com.snc.wm.wo.task_window_day property to determine this value.
* If the task has no Window start date but has a Window end date, dynamic scheduling uses the current time for this value.
* If the task has neither a Window start nor a Window end date, dynamic scheduling uses the current time and date for the Window start and the com.snc.wm.wo.task_window_day property for the Window end.
* If a task is created, the Window end date gets automatically populated based on the latest SLA breach date from its parent work order. The business rules Populate Window End Based On SLA for both Task SLA \[task_sla\] and Work Order Task \[wm_task\] tables, and the client script Calculate Window End has to be set to true.
* If a task is created and Fixed window is enabled, the business rules and client scripts doesn't execute and Window end time is not updated. If a work order is created based on an appointment and there is an SLA associated with the work order, the Window end time is populated based on the appointment and not on the SLA.
{#dynamic-sched-system-properties__ul_by1_xtb_dzb}  
The Window start date field gets updated based on the delivery date of the transfer order only for the work orders that are not assigned. The business rule Sync up Delivery Time with WOT has to be set to True. For multiple transfer orders containing mandatory part requirements, the Window start date is set to the latest delivery time of the transfer order(s). Window start date is updated based on transfer orders only when the part requirement associated with the transfer order is mandatory. However, you can manually edit the window start time and override the existing date that is populated based on the transfer order.  
Note:  
The Window start date is not updated if the work order task is one or more of the following:

* Associated with an appointment
* Fixed Window
* Window end is populated and is before the delivery by date.
{#dynamic-sched-system-properties__ul_zs3_2kh_dzb}
**Related tasks**   

* [Configure dynamic scheduling](https://www.servicenow.com/docs/lZCJ4DiL41zYBfGZzfYaxw#create-dynamic-scheduling-config "Dynamic Scheduling enables automatic task assignment to field agents based on predefined rules and configurations. This feature helps streamline task distribution by verifying the correct tasks are assigned to the most suitable agents, optimizing travel time, skill matching, and task priority.")  
**Related reference**   

* [Example - Dynamic Scheduling](https://www.servicenow.com/docs/A0em21BWpLXVv6QEZiEIUQ "Explore how Dynamic Scheduling prioritizes the best agent for a task, focusing on key matching criteria.")

*[\>]: and then