wm_task_proposed_schedule

[Joshua Chen MTL]

any1one knows what this is used for? how does it get populated?

proposed schedule related list.

[Maik Skoddow · Accepted solution]

Hi @Joshua Chen MTL 

The ServiceNow table wm_task_proposed_schedule is part of the Field Service Management (FSM) module and is used to store proposed scheduling information for work order tasks. It contains data about suggested or recommended start and end times for tasks before they are finalized and assigned, typically as part of the scheduling and optimization process within FSM. This table supports intelligent task scheduling and optimization features by holding potential scheduling options generated by the system or schedulers, which can be reviewed or adjusted before confirming the actual schedule. Essentially, wm_task_proposed_schedule acts as a staging or recommendation layer for scheduling work order tasks, enabling dynamic and optimized planning of field service activities.

Maik

[Maik Skoddow · Accepted solution]

Hi @Joshua Chen MTL 

The ServiceNow table wm_task_proposed_schedule is part of the Field Service Management (FSM) module and is used to store proposed scheduling information for work order tasks. It contains data about suggested or recommended start and end times for tasks before they are finalized and assigned, typically as part of the scheduling and optimization process within FSM. This table supports intelligent task scheduling and optimization features by holding potential scheduling options generated by the system or schedulers, which can be reviewed or adjusted before confirming the actual schedule. Essentially, wm_task_proposed_schedule acts as a staging or recommendation layer for scheduling work order tasks, enabling dynamic and optimized planning of field service activities.

Maik

[Joshua Chen MTL]

do end users interact with this table or it's just to store the data/output of dynamic scheduling and schedule optimization? 

keep that related list hidden on the work order task?

[Maik Skoddow]

Exactly!

[Joshua Chen MTL · Accepted solution]

i previously accepted a reply as a solution, but the correct answer is:

 It is used to store scheduling recommendations generated by the optimization engine that could not be applied to the actual Work Order Task.

This typically occurs when certain conditions prevent the system from updating the task schedule, such as task locking, scheduling conflicts, constraint violations (for example, skills, availability, or time window restrictions), or manual dispatcher overrides. In these situations, the optimization engine still calculates the best possible assignment, but instead of updating the live task record, the recommendation is stored in the `wm_task_proposed_schedule` table for reference.

This allows dispatchers and administrators to understand what the optimizer intended to schedule, why the task may not have been automatically reassigned, and what alternative scheduling options may be available for manual review or action.

Since this table only stores proposed (not applied) schedule recommendations, it may remain empty if the optimization engine is able to successfully apply schedules, or if the environment does not frequently encounter constraint or locking scenarios.