Last updated: 2024-08-01
Applies from: Opter 2024.06.00, Opter Driver for iOS and Opter Driver Labs for Android 2.4.15, Opter Driver (classic) for Android 0.1
Customise the deviation view in Opter Driver
The driver can register anomalies in Opter Driver at the time of POD registration, scanning, or directly when they are detected by selecting Deviations from the detail view menu. You can set which fields are displayed and which fields are mandatory to fill in when the driver records a deviation. You can also rename the fields and set up Opter Driver not to record anomalies at all.
Instructions for drivers are available at Register proof of delivery (POD) in Opter Driver for iOS, Scan freight bills and package labels with Opter Driver for iOS and Pages, tabs and menus in Opter Driver for iOS.
Setting whether drivers are allowed to record deviations or not
With the mobile data settings DamagesPermission and AddNewDamagePermission you set whether drivers should be able to:
see existing anomalies or not.
register new anomalies or not.
Proceed as follows:
Click on Settings > Mobile data > Settings mobile data.
Click on an empty row in the Name column and then on the down arrow in the row being added.
Select DamagesPermission from the list.
Enter “true” or “false” in the Value column.
”True” (default): The option Deviations appears on the menu in the detail view of Opter Driver, if there are discrepancies on the mission. In addition, if AddNewDamagePermission is set to "True", the menu item Deviations is always displayed on all missions, so that drivers can add new deviations.
Choose whether drivers should only be able to see existing deviations or whether they should also be able to register new deviations by setting AddNewDamagePermission as below.
“False”: the Deviations menu option is not displayed. Drivers cannot view existing anomalies or register new anomalies.
If you set DamagesPermission to "true", you can also choose whether they should be able to register new anomalies or not with AddNewDamagePermission.
”True” (default): The driver can register new deviations in Opter Driver.
“False”: the driver cannot add new deviations.
By clicking on Deviations in the detail view, drivers can see existing deviations, but cannot register new deviations. The Deviations menu option is only displayed if there are deviations on the shipment.
Click on Save.
If you don't make any setting at all, both settings are counted as "true". That is, drivers can both view existing and record new anomalies.
Note:
By default, changes made in Opter Driver need to be manually approved in the dispatch centre for the change to be saved, but you can set it so that no changes need to be approved at all, or that only certain changes need to be approved.
For more information, see Setting how changes in Opter Driver are authorised.
Customising the Deviations view
If DamagesPermission is set to "true", you can set which fields are displayed in the deviation view. The fields can also be renamed.
When a driver selects Deviations from the Opter Driver menu, one of the following happens:
If there are deviations registered on the assignment, and if AddNewDamagePermission is set to "true", a view opens where drivers can see existing deviations and register new ones. It is also possible to search for deviations related to the shipment.
Clicking on New deviation or on an existing deviation under Review deviation opens the deviation view.
If there are no discrepancies on the assignment, and if AddNewDamagePermission is set to "true", the discrepancy view opens directly. There the driver can create a new deviation. The drop-down lists Event and Reason are displayed if the selected deviation type has deviation events and deviation causes associated with it. Drivers can also add new deviations from the POD view.
In Opter Driver for Android, the deviation view looks like this:
You can choose which fields to display in the deviation view, and also rename them. The deviation view is managed with the settings starting with "DAM_" in the mobile data settings. There are two types of DAM_settings:
“DAM_XyzPermission”, for example DAM_CommentPermission: Controls whether or not the field is displayed in the view.
“DAM_XyzName”, for example DAM_CommentName: Replace the default name of the field with a custom name.
For more information on the DAM_ settings, see Mobile data settings (window).
If you do not make a setting for any of the mobile data settings starting with DAM_, all fields in the anomaly view will be displayed, except for the Event and Reason drop-down lists, which are displayed if the selected anomaly type has anomaly events and anomaly causes associated with it.
To set which fields should be displayed, proceed as follows:
Click on Settings > Mobile data > Settings mobile data.
- Click on an empty row in the Name column and then on the down arrow in the row being added. Select the DAM_XyzPermission setting for the field to be displayed/hidden, for example DAM_CommentPermission (which controls whether or not the Comment field is displayed). For more information on which settings correspond to which fields, see Mobile data settings (window).
Enter one of the following in the Value column:
“True”: if the field should be displayed.
“False”: if the field should not be displayed.
- Repeat steps 2 and 3 for all other fields whose settings are to be configured.
Click on Save. When you have finished configuring the settings, you can close the window.
To rename the fields, proceed as follows:
Click on Settings > Mobile data > Settings mobile data.
- Click on an empty row in the Name column and then on the down arrow in the row being added. Select the DAM_XyzName setting for the field to be renamed, for example DAM_CommentName (which is the Comment field). For more information on which settings correspond to which fields, see Mobile data settings (window).
Enter the new name of the field in the Value column, for example “Deviation comment”.
Repeat steps 2 and 3 for all fields to be renamed.
Click on Save. When you have finished configuring the settings, you can close the window.
Setting the types, events and reasons that should be selectable
How to set the types, events and reasons that should be available for selection in Opter Driver:
In Opter, in the Deviation types window, set the deviation types that should be available for selection in Opter Driver by selecting the Available in mobile device checkbox. For more information, see Deviation types, window.
In Opter, in the Deviation events window, set the deviation events that should be available for selection in Opter Driver by selecting the Available in mobile device checkbox. For more information, see Deviation event, window.
In Opter, in the Deviation reasons window, set the reasons for deviations that should be available for selection in Opter Driver by selecting the Available in mobile device checkbox. For more information, see Deviation reasons, window.
Setting which fields are mandatory
It is always mandatory to enter a deviation type (field Type) in Opter Driver.
If it is mandatory to enter a deviation event, select Force deviation event in the window Deviation types.
If you want to make it mandatory to enter a reason for deviation, tick Force deviation reason in the window Deviation events.