NowGo Driver Apps is built off Thunder Configuration and is highly customisable to accommodate different businesses operations. It can accomodate compliance checks, barcode scanning and capture information based on different driver actions.
Overview
This workflow engine is a foundation for consignment-based workflows. When the user enters the workflow, they’re prompted to scan articles.
The user has two options: success and failure. Each directs the user down a customised flow to collect additional information.
Scan prompt | Scan workflow |
User enters workflow
 | After a single article has been scanned.
 |
Customising the main screen
Structure
Scan prompt | Scan workflow |
Before any articles are scanned
| After a article is scanned |
Handling success
When the user has scanned some articles and hits the Success Button, we can do one of two things:
Immediately create a workflow completion and exit the workflow. This doesn’t prompt for any further information.
Enter a Prompt Flow. This is a series of interactions that prompts the user for more information.
At the end of a Prompt Flow we can then create a workflow completion containing any information captured.
Handling failure
When the user presses the failure button (“Can’t deliver”, in the screenshots above) they’re presented with the Failure Screen. They’re required to indicate which articles they can’t deliver, and then can enter a flow where they can provide more information.
Similar to the success case, when a confirms the failed articles we can do one of two things:
Immediately create a workflow completion and exit the workflow. This doesn’t prompt for any further information.
Enter a Prompt Flow. This is a series of interactions that prompts the user for more information.
Unlike the Success Button, the failure flow doesn’t always exit the workflow. If the workflow was launched from a Stop, and not all the target articles of the stop have been failed, the workflow will return to the main screen.
Failure prompt | Failure Labels |
The Failure Screen, showing a single article
| Components of the Failure Screen
|
Customising the Stop Information Panel
The Stop Information panel is shown if the workflow was entered via a stop. At the moment, this happens in one of two ways:
The driver selects a stop from the Stops List.
The driver free-scans an article and selects an Action, and a matching Action exists on a planned stop for the article.
The Stop Information Panel can show data from the Stop and Job. If the Stop has a Causal Consignment, you can also show information from there.
Structure
Each row has text, and an optional heading and an optional icon.
Multiple rows.
A normal view, and an expanded view.
Behaviour
If the stop has a known location, we’ll show a map at the bottom of the panel. You can disable this behaviour.
If the stop has driver notes associated with it, we’ll always show them at the top of the Stop Information Panel.