FSM - "Work in Progress" WOT is not showing in Dispatcher Workspace.

[Community Alums]

In the Dispatcher Workspace I could see the Advanced Filter Conditions are correctly mentioned to filter the Work in Progress WOT. There is no changes made to the OOB Script include "DispatcherWorkspaceCalendarUtilSNC". Still Once the WOT is moved from Accepted to WIP, Its Disappearing from the Dispatcher Workspace. Its not showing under All Active Tasks as well. What can be the possible issue here.

[Community Alums]

I could see the data is showing correctly in the Left side Panel Based on the Filter selected. I am confused regarding the WOTs showing inside the calendar. 

Script Include :DispatcherWorkspaceCalendarUtilSNC
Function: getCalendarTaskQuery - This OOB Function describes the state values which should show in the Workspace Calendar, which includes WIP state as well. Still WOT in WIP state is not showing in the calendar. 

[Joshua Chen MTL]

is your state inactive in 

Navigate to Field Service > Dispatcher Workspace Configuration > Task State Colors.

else open a hi support ticket, WIP should show ootb if you have not done any customization

[MatthewBilly]

Because the calendar is choosing what information about the task to use to set the travel start, expected start/actual start, and estimated end, it is important to ensure that actual travel and actual work start times are being set which ALIGN with the state of the task. For example: for a task in the state Work in Progress, the system is expecting to have: Actual value for travel start [actual_travel_start] to anchor left side of travel bar, actual value for [work_start] to anchor the work section, and then it will leverage the estimated duration [estimated_work_duration] to set the length of the work bar. This is true for completed tasks also needing actuals to properly display

We've seen this behaviour OOTB with the dispatcher workspace buttons for start work not setting an actual travel start or actual work start time. Depending on your interpretation, this is either an opportunity or a bug.

For Example:
The reason the dispatcher is clicking the start button is that the technician is unable, or has already started work. In this case, the system doesn't even know that travel has started and doesn't have the ability to estimate when that was: this allows the dispatcher to gather the information from the technician and put it in the actuals section of the WOT. Take the time to configure this per your client expectations using scripts to autopopulate or perform validation before the user is allowed to state transition.

@Joshua Chen MTL is also correct, that the colour value of the task state must be configured correctly in app_cmn_state_color_config otherwise the object will not be displayed