- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2025 08:25 AM
Greetings,
We're experiencing unexpected behavior in Dispatcher Workspace. When a Work Order Task (WOT) is dropped onto the calendar, a blue line appears. Based on our observations, the blue line seems to start at the date and time the WOT was created. This behavior only started occurring for WOTs created on or after January 29, 2025, and we haven’t seen this before. Has anyone else encountered this? I haven't found documentation explaining what the blue line represents or how to prevent it from appearing.
Additionally, our dispatchers are manually assigning WOTs for January 30, but the tasks are automatically shifting to February 3. We do not use auto task assignment, skills, or geotracking, and our agents have 24x7 schedules to allow assignment at any time. This issue also began on January 29, 2025.
Any insight would be greatly appreciated. Thank you!
(We are on Vancouver not Tokyo, but Vancouver wasn't a label option for the post)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2025 09:31 AM
it's calculated by a BR
- Navigate to: System Definition > Business Rules, search for "estimated_travel_duration".
- Also, check Script Includes related to FSM scheduling
-
Disable or Modify Business Rules:
- If a Business Rule is updating the field incorrectly, disable or adjust its logic.
also for the best use of time, can you please reach out to support to further look into this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2025 11:03 AM
For anyone who runs into the same issue:
The blue line does, in fact, represent the Estimated Travel Duration. It started appearing because the location record (cmn_location) associated with the Agent's user record (sys_user) had newly populated Longitude and Latitude values.
If you do not want the Estimated Travel Duration to autopopulate, make sure your location records do not have Longitude and Latitude populated.
Thank again SalmatO!