Work order task start and end dates

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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 document outlines how dynamic scheduling utilizes the Window start and Window end dates for scheduling work order tasks in ServiceNow. Understanding these configurations ensures effective task management and scheduling within the system.

    Show full answer Show less

    Key Features

    • Dynamic Scheduling: Uses Window start and end dates to determine task scheduling.
    • Current Date Usage: If the Window start date has passed or is missing, the system defaults to the current date/time.
    • SLA Integration: The Window end date is auto-populated based on the latest SLA breach date from the parent work order unless Fixed Window is enabled.
    • Transfer Orders: Updates to the Window start date are based on delivery dates of mandatory part transfer orders, with options for manual overrides.

    Key Outcomes

    By configuring the Window start and end dates accurately, ServiceNow customers can ensure that work order tasks are scheduled effectively, reducing the risk of SLA breaches and improving operational efficiency. Proper setup enables timely updates and better alignment with delivery timelines, enhancing overall task management within the platform.

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