Overview

The following covers the process for adding a created scan button on the load level of workflow to allow drivers to scan both while a load is In Progress and after a load has been Completed. This setup may require multiple workflows in Drive Axle to be updated, depending on how workflows are being used.  


The following sections outline how to add an action to an existing workflow in Drive Axle after creating the action, using “Scan Document” as an example.


The screenshot example below shows the yellow “Scan Document” action on both their current load that is In Progress and on a load that they have Completed in the past. To view historical completed loads in the application, click on “View History” in the loads list.


Current INPROGRESS Load     Historical COMPLETED Load

                                                         

Creating The Form And Action For Scanning

If you do not already have a form and action that you wish to add to the driver’s workflow, you’ll want to begin by creating those first starting with the form and then following with the action. A guide on how to create these can be followed here:


Statuses In Workflow

Within a Workflow individual statuses can be defined. Load statuses, shown in blue under the Loads section of workflow, can be created within Drive Axle but also correlate to how the statuses are defined within the ELEOS.udf_TripStatus function.


When the application is online, the workflow editor is used to correlate a Load (Trip) status with its associated action. It is not required to be sequential or to directly follow what is outlined within the editor. When ELEOS.udf_TripStatus is executed, it returns a “Status” for the respective load record. The status returned should be an identical match to the status defined within the editor. The application will then display whatever actions are defined under that status within the editor. For example, regardless of what the driver’s current status is, if the Eleos.udf_TripStatus function returns “INPROGRESS”, the actions defined under the “INPROGRESS” load status in the workflow editor are shown to the driver in the app. Load statuses differ from Stop statuses, which show in Drive Axle as a different (off-white) color within the Stops section and are instead controlled by Eleos.udf_StopStatus.


When the application is offline, the Workflow Editor in Drive Axle’s App Manager fully defines how the workflow will function and progress as the driver completes workflow actions.  The arrows in the editor dictate which status to transition to after submission. Drive Axle - Drive Axle Walkthrough  has some additional information on what workflow statuses are and how workflows are used in Drive Axle.

 

Determine which Workflow to Add the Button To

Before adding a button to workflow, first determine which workflow the button needs to be added to.   To confirm this, you can log into the application as a driver, look at the driver’s current In Progress load and the buttons that are displayed on that load. Compare the existing actions on the load to the workflows in your company’s Drive Axle environment, to determine which workflow is being used for the order.  The same can be done with a historical order that has been Completed to determine if one workflow is being used for both historical and current loads, or if multiple workflows are being used.


For example, the Completed load #78 has 2 workflow buttons on the load level: Reset Workflow and Test Inline Document Capture:

 

 

Then check Workflows in Drive Axle to see which one contains those actions for the Completed load status. Do this by going to App Manager > App Configuration > Workflows.  




Select any workflow and then select the appropriate load status in that workflow to see what actions are associated with it. In the example below we can determine that the driver is using the DEFAULT workflow by looking at the Completed load status in each workflow and matching it with what is seen in the application for a driver’s Completed load.

 


Please note that this method will not always work since there may be multiple workflows that have the same actions defined for a particular Load status or a Load status that does not yet have any associated actions.  You can also determine which workflow a driver is using by reviewing the ELEOS.udf_TripStatus function.


Most clients use multiple workflows, and in this case, you may see these workflow codes in your Drive Axle as CURRENT for when the load is In Progress, and DEFAULT for the workflow code when the load is Planned, Available, Or Completed. For a default implementation, and for the example used in this document, CURRENT and DEFAULT are the workflow codes used. These are the most common default workflow codes used and are dynamically set depending on how the load or leg statuses are updated within your TMS.  ELEOS.udf_TripStatus is the function that determines which workflow code to use and by default typically contains the SQL scripting logic for setting this workflow code between CURRENT and DEFAULT.  However, please be aware that some companies use different workflow codes to identify each workflow.  It is also possible for a client to instead just use one single workflow for both loads that are active/in progress and loads that are in other statuses like completed, planned, etc.

 

How to Add a Button to a Single Workflow

If just adding an action to the Load level for a singular workflow, it would just need to be added to the appropriate status in the workflow that is being used by drivers, as defined in ELEOS.udf_TripStatus. For example, if only one workflow is being used with the code DEFAULT, then the action would need to be assigned to the appropriate load statuses in that workflow.     

 

Updates To Current Workflow

First, ensure that the action/form that needs to be added to workflow is already created. Then, determine where the button needs to be added and to which workflow. For the following example, if you are looking to add the button to the driver’s active load and find that the driver is using the CURRENT workflow for INPROGRESS loads, then we can make the necessary updates to the CURRENT workflow. The action button can be added to any load status or multiple statuses within the CURRENT workflow, but for this example, we will be adding it to INPROGRESS to show the scan action on loads that are currently being worked on. To make this change, within Drive Axle, you’ll first navigate to the App Dashboard, and then select Workflows under the App Configuration drop down:

 


Once in Workflows, select the CURRENT workflow:

 


Within the workflow editor you’ll then want to focus on the Load section, which contains the blue Load statuses.  Select the INPROGRESS status.  Once it is selected, the panel to the right will show that the INPROGRESS Load status is selected and in parentheses is the INPROGRESS code for the load status. Here you can add an existing Action.

 

 

You’ll then need to select scan action you wish to add from the drop down:


 

If there are multiple actions on a single load status, you can change the order of which the actions appear on the Load in the application by clicking and dragging up or down, using the dots to the left of each action button.  Ensure you select the blue Save button to finalize your changes: 

After saving and finalizing this change to the CURRENT workflow, your selected scan action will show on the current load that is In Progress. To verify this, log into the application as a driver with an active load and see the Scan Documents button showing on the Load level, above the list of stops for that load:


 

If Mulitple Workflows Are Used

If using multiple workflows, like in the example for this document, in order to have the Scan Documents button on both in progress and completed loads then the Scan Documents button needs to be added to each workflow. Following the steps outlined above to add an action to the load level of workflow, the Scan Documents action can be added to additional workflow(s), in the case that multiple workflows are being used. For example, if the DEFAULT workflow is used for Historical loads, then the Scan Documents button can be added to the COMPLETED Load status in the DEFAULT workflow so that it appears in the application on a historical load. That way, drivers can still scan documents for that load when it is in Completed status.


To do this, follow the same steps that were taken to add the action to the CURRENT workflow, except you will want to select the DEFAULT workflow from the list of workflows. After saving and finalizing changes to the DEFAULT workflow, your selected scan action will show in the application to drivers. To verify this, log into the application as a driver with a Completed load under “View History” in the loads list and see the Scan Documents button show on the Load level, along with the other actions that were already on the Completed status.