Configuring printout scanning in Opter Terminal

The automatic printing of labels immediately after a package has been scanned with Opter Terminal can be enabled. This function is configured in the mobile data settings. Printing from the app is done based on the settings in the Terminal printing window. The function is configured as follows:

Step 1: Open the Opter Terminal layout settings

Click on Settings > Mobile data > Settings mobile data.
Click on Edit, next to Terminal.Settings.

If Terminal.Settings does not appear in the list, click on an empty line in the Name column and select Terminal.Settings from the list.

Note:

If you have configured specific Opter Terminal settings for the terminal whose setting you want to adjust, the following setting must be applied for that terminal in the terminal registry, rather than in Terminal.Settings. For more information, see Separate Opter Terminal settings for individual terminals.

Step 2: Activate the function

Add the following line within the <terminal> tag. The Print option is added to the main menu in Opter Terminal.

Copy code

Enable printout scanning

<printing enabled="true"/><!-- enable/disable print true or false -->

The next time users log into Opter Terminal, they can scan and print labels immediately by selecting Print in the main menu.

Step 3: Configure the options

Add the following section to the XML file in order to change how printout scanning works. The options are configured using true/false values. If you do not add the section and make active selections, the following default settings are used.

Copy code

Default settings for printout scanning

<print>
  <shipment visible="true" />
  <package visible="true" />
  <orderdate visible="false"/>
  <route visible="false"/>
  <nextroute visible="false"/>
  <nextresource visible="false"/>
  <nextorder visible="false"/>
</print>

shipment: Control whether or not freight bills can be scanned.
package: Control whether or not packages can be scanned.
orderdate: Show/hide the order date in the scanning list.
route: Show/hide the last shipment’s route in the scanning list.
nextroute: Show/hide the next route in the scanning list.
nextresource: Show/hide the resource that will carry out the next shipment in the scanning list.
nextorder: Show/hide the route sequence in the scanning list.

Example

The following example shows the structure. Other sections of the XML file have been removed in the example. Your XML file contains more information.

Copy code

Opter Terminal print functions

<?xml version="1.0" encoding="utf-8" ?>
<fleet101>
  <k2>
    <windowsce>
      <terminal>
        <print>
          <shipment visible="true" />
          <package visible="true" />
          <orderdate visible="false"/>
          <route visible="false"/>
          <nextroute visible="false"/>
          <nextresource visible="false"/>
          <nextorder visible="false"/>
        </print>
        <arrivalscanning enabled="true"/> <!-- enable/disable arrivalscanning true or false -->
        <departurescanning enabled="true"/><!-- enable/disble departurescanning true or false -->
        <floorcheckscanning enabled="true" /><!-- enable/disable floorcheckscanning true or false -->
        <loadcarrierscanning enabled="false"/><!-- enable/disable load carrier scanning true or false -->
        <damages enabled="true"/><!-- enable/disable damagescanning true or false -->
        <terminalpod enabled="true" /><!-- enable/disable POD-scanning true or false -->
        <printing enabled="true"/><!-- enable/disable print true or false -->
        <picture maxsize="799" selectfromgallery="true"/><!-- max width on the widest side of the image  -->        
      </terminal>
   </windowsce>
  </k2>
</fleet101>