---
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


---

# WOT start and end dates

# Work order task start and end dates {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Work Order Task Start and End Dates

This functionality in ServiceNow's Brazil Release manages scheduling of work order tasks by usingWindow startandWindow enddates.
Dynamic scheduling relies on these dates to effectively plan task execution within specified time frames.
Show full answer Show less  

## Key Features

* If both Window start and Window end dates exist, dynamic scheduling uses them directly.
* If the Window start date has passed, scheduling uses the current date and time instead.
* If only the Window start date exists, the Window end date is calculated using the `com.snc.wm.wo.taskwindowday` property.
* If only the Window end date exists, the current time is used as the Window start.
* If neither date exists, scheduling defaults to the current date/time as Window start and uses the `com.snc.wm.wo.taskwindowday` property for Window end.
* Upon task creation, the Window end date is automatically populated based on the latest SLA breach date from the parent work order, provided specific business rules and client script are enabled.
* If Fixed window is enabled, the automatic update of Window end date is disabled.
* For work orders created from appointments with an SLA, the Window end is set from the appointment time rather than the SLA.
* The Window start date for work order tasks updates based on the delivery date of associated transfer orders only if the work order is unassigned and the part requirement is mandatory.
* Multiple transfer orders with mandatory parts set the Window start to the latest delivery time among them.
* Users can manually override the Window start date populated from transfer orders.

## Important Considerations

* The Window start date is not updated if the work order task is linked to an appointment, has a Fixed Window, or if the Window end is set before the delivery-by date.
* Business rules such as **Populate Window End Based On SLA** and **Sync up Delivery Time with WOT** must be enabled (set to True) to ensure automatic date population functionality.

## Practical Impact for ServiceNow Customers

Understanding how Window start and end dates are set and managed allows customers to ensure accurate task scheduling aligned with SLAs, appointments, and delivery timelines. This promotes better task coordination, timely completion, and compliance with service commitments. Customers can also exercise manual control where necessary to address exceptions or special cases.  
Dynamic scheduling uses work order task Window start and
Window end dates to schedule tasks.
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.  
Window start date gets updated for the work order tasks based on the delivery date of the transfer order only for work orders that are not assigned. The business rule Sync up Delivery Time with WOT [business rule](https://www.servicenow.com/docs/wdx4qKrpTVr~V6DIZdXnFw "Several types of components are installed with Field Service Management.") has to be set to True. Multiple transfer orders that has mandatory part requirements, the Window start is set to the latest delivery time of the transfer order. Window start date is only 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:

* Associated with an appointment
* Fixed Window
* Window end is populated and is before the delivery by date
{#dynamic-sched-task-window-dates__ul_g1h_4lb_zlb}