Flow of status
Value | Dashboard display | Description |
info_recv |
| New job created in Detrack. |
in_transit |
| Awaiting arrival of goods to warehouse. |
dispatched |
| Job information ready to be sent to Driver App for drivers to perform job. |
completed |
| Job completed by driver. |
completed_partial |
| Job completed by driver, but with at least 1 item rejected in |
failed |
| Job failed. |
on_hold |
| When admin changes the status to on-hold manually through the dashboard. |
return |
| When admin changes the status to return manually though the dashboard. |
Flow of tracking_status
he tracking status is the end result of the various combinations of different fields. (e.g. status, assign_to, date).
Value | Description |
Info Received | New job created in Detrack. |
Out for delivery / | Job being assigned to a vehicle, |
Scheduled | Job being assigned to a vehicle, |
Completed | Job completed by driver. |
Partially Completed | Job completed by driver, but with at least 1 item rejected in |
Failed | Job failed. |
On hold | When admin changes the status to on-hold manually through the dashboard. |
Return | When admin changes the status to return manually though the dashboard. |
COMBINED STATUS AND TRACKING STATUS
|
|
| Description |
info_recv | Info Received |
| Used when the job information reached courier, and goods has yet to arrive. |
in_transit | Info Received |
| Used when goods is being sent to warehouse. |
dispatched | Info Received | null | When the job is ready to be sent out to the Driver App for drivers to perform the job. |
dispatched | Out for delivery / Out for collection | Not null | When the job has been sent out to the Driver App for drivers. |
completed | Completed | Not null | When the job has been completed. |
completed_partial | Partially Completed | Not null | When the job has been completed, but with at least one rejected item in the |
failed | Failed | Not null | When the job has failed. |
on_hold | On Hold |
| When there is some issue with the job, and the admin wishes to delay the job. |
return | Return |
| When there is some issue with the job, and the admin wishes to return the goods. |
MILESTONES
This section is about the milestones
array. This array will serve as a log to record the various events that happened to your job.
Value | Description |
info_recv | New job created in Detrack. |
dispatched | Triggered when |
out_for_delivery |
|
head_to_delivery | Driver triggers “Head to location” from Driver App for Delivery |
head_to_pick_up | Driver triggers “Head to location” from Driver App for Collection |
completed | Job completed by driver. |
completed_partial | Job completed by driver, but with at least 1 item rejected in |
failed | Job failed. |
on_hold | When admin changes the status to |
return | When admin changes the status to |
LOGGING OF INFORMATION IN THE MILESTONES ARRAY
NORMAL MODE
Info Received (info_recv) will be added when job is created.
Heading to delivery (head_to_delivery) / pick up (head_to_pick_up) will be added when driver triggers heading to.
When job status (dispatched/completed/failed ..etc) has changed, milestone will be added.
When driver has changed and “Add vehicle change milestone” is enabled, corresponding entry will be added.
COURIER MODE
Milestone will be added based on the job status when job is created.
Heading to delivery (head_to_delivery) / pick up (head_to_pick_up) will be added when driver triggers heading to.
When job status (dispatched/picked_up/completed/failed ..etc) has changed, milestone will be added.
When driver has changed and “Add vehicle change milestone” is enabled, corresponding entry will be added.