Customise the scan list in Opter Driver for iOS

The scan list is the view displayed when a driver has scanned packages with Opter Driver. You can set which fields are displayed in the scan list and what information is displayed for each package on the order.

Instructions for drivers can be found in Scan freight bills and package labels with Opter Driver for iOS.

Step 1 (optional): Setting which fields are to be displayed

You set the fields to be displayed in the scan list using the Design field for mobile window or the XML file App.OpterDriver.Design (or App.Design). For more information, see Customising the layout and features of Opter Driver. The fields are described in ( Design field for mobile (window).

For example, you may want to display the following fields:

Package ID number [PACKAGE.PACKAGEID]
Status (package) [PACKAGE.STATUS]
Scan time (package) [PACKAGE.SCANTIME]
Terminal name (package) [PACKAGE.HUBNAME]
Resource (package) [PACKAGE.RESOURCE]
Comment (scanning) [PACKAGE.SCANCOMMENT]
Dimensions (package - scanning) [DIMENSIONSSTRING]

More information such as the Dimensions (package - scanning) [DIMENSIONSSTRING] field can be found in Step 2: Set the package information to be displayed below.

Step 2 (optional): Setting the package information to be displayed

In the scan list, package information such as weight, volume, pallet location, package type and freight type can be displayed. The parcel information is displayed for each parcel on the order.

If package information is to be displayed in the scan list, proceed as follows:

Use the mobile data setting PackageDimensionsString to set the text and information to be displayed about the parcels in the scan list, for example "Pallet position: 17”. For more information, see Detailed instructions for PackageDimensionString below and in ( Mobile data settings (window).
To display the settings in PackageDimensionsString, do one of the following:
- If you use the window Design field for mobile:
  
  The Design field for mobile window can be found by clicking on Settings > Mobile data > Design field for mobile.
  
  Click on the tab Scanning view and search for the field Dimensions (package - scanning) [DIMENSIONSSTRING]. If it is in the list Excluded, drag and drop Dimensions (package - scanning) [DIMENSIONSSTRING] to the list Included. It is also possible to double-click on a field to move it to the other list. Click on Save at the bottom.
- If you use the XML file App.OpterDriver.Design (or App.Design):
  
  What is between the <scanrows> </scanrows> tag pair in App.OpterDriver.Design is displayed in the scan list.
  
  Add PACKAGE.DIMENSION STRING between the <scanrows> </scanrows> tag pair , where you want it.
  
  For complete examples of what the XML file App.OpterDriver.Design might look like and for more information, see App.OpterDriver.Design. Save your changes when you are done.

Detailed instructions for PackageDimensionsString

Add the mobile data setting PackageDimensionsString and enter “| Package type: {14} | Weight {1:0.##} kg | Volume: {2:0.##}" in the Value column. The variables ({0}-{15}) take their values from the package rows.

PackageDimensionsString is a free text field. This means that any text required can be written around the variables, for example:

“Package type: {0}, total weight {1:0.##} kg, volume: {2:0.##}.”
“The package is of type {14}, has a volume of {2:0.##} and weighs {1:0.##} kg.”

Information on which other dimensions you can display is available in ( Mobile data settings (window)).

Variables that return numbers

For variables that return numbers, it is possible to specify how many decimal places to display in the scan list, and whether to exclude unnecessary trailing zeros at the end of the number. In our example (“Weight: {1:0.##} kg”), we have limited the number of decimals for the weight to a maximum of two, but if the weight is “8.00” on the package row, only “Weight: 8 kg” is displayed in the scan list. If the weight in the package row is “8.10”, “Weight: 8.1 kg” is displayed in the scan list. The unnecessary trailing zeros after the decimal point are deleted.

The syntax works in the same way as in text and HTML reports. The number of decimal places is limited by the number of zeros after the decimal point (0.00). To exclude unnecessary trailing zeros, enter # signs instead of zeros. The dot is converted to a comma in the app.

Obs!

Numbers are stored with six decimal places in the Opter database. If a limit is not defined, all numbers are always displayed to six decimal places. For example, if “Width: {5} m” is entered in PackageDimensionsString, “Width 2.000000 m” will be displayed in the scan list.

Copy code

Variables in PackageDimensionsString that return numbers

Weight: {1:0.00}
Volume: {2:0.##}
Load metres: {3:0.00#} 
Pallet space: {4:0}
Width: {5:0.00}
Height: {6:0.00}
Depth: {7:0.00}

Returns

Weight: 8.00

Volume: 8.12, or 8.1 (if the number on the package row is 8.10), or 8 (if the number on the package row is 8.00)

Load metres: 8.123, or 8.12 (if the number on the package row is 8.120), or 8.10 (if the number on the package row is 8.100)

Pallet space: 8

Width: 8.00

Height: 8.00

Depth: 8.00

Step 3 (optional): Block or warn about another resource when scanning

You can set it up so that the scan is blocked or the driver receives a warning if they try to depart and/or pick up a mission that is not scheduled on that resource. You set the status from which departure and/or pick-up scans are blocked or the driver receives a warning. For instructions, see Block or warn about another resource when scanning in Opter Driver for iOS.

Restriction in scan list settings

For Opter Driver (classic) for Android, you can set whether collision scans are displayed in a block or as separate scans in the scan list using the mobile data setting OneScanRowPermission. For Opter Driver for iOS and Opter Driver Labs for Android, collision scans are always displayed in blocks, regardless of the setting you have made for OneScanRowPermission. More information is available in ( Mobile data settings (window).

Troubleshooting

If you are using Design field for mobile and your changes Design field for mobile are not visible in the app, see Configuring which fields are displayed in Opter Driver for iOS.