Solved

Dispatch Console resorting tables too quickly (15.4)

  • 24 April 2023
  • 1 reply
  • 49 views
bskallerud
Rank
Userlevel 6
Badge +11

We do a lot of manual dispatching, and the dispatcher will typically sort the Unallocated orders in the DC by ZIP or ETA (or other criteria). If they find 10 orders with the same ZIP they want to dispatch they drag and drop this on the SAs timeline. If they are not quick enough to select the next order, the DC will resort the Unallocated table, and the dispatchers have to scroll down again from the top (it takes 3-5 seconds before this happens). Any idea if we can change the time it takes before this happens or something?

icon

Best answer by Phil Seifert 24 April 2023, 16:35

View original

1 reply

Phil Seifert
Rank
Userlevel 7
Badge +21

Hi Bjørn,

This is working as designed. 

The situation is that your DC is allowing updates again after the drag/drop action moved the item to the Allocated tab.  If you select another row straight away, you will remain where you were in the list.

If you were doing other activities that do not result in moving the activity out of the unallocated tab (change ETA for example) it will also remain where it is as long as the row is selected.

 

Reply


Terms & ConditionsCookie settings