Page Comparison

...

Description

Use case -

...

Select a Line

The selection can be done on any value defined on the order line, either standard like ItemNumber, or custom elements added the lines on Order Lines GetOrderLines Response

...

If any other value is sent out, the application will go through the automatic searching mechanism where order line registration status is taken into account as well as the position of the selection.

Use case -

...

Set/return Step

...

values

The response can also include values to be set on the line steps as predefined default values.

Use case - Add/return a new line

You can use information from the Request, an ItemNumber, a SerialNumber or a Lotnumber (requirement) to add a line.

Then returning a Response to refresh the lines. The new line will be selected, and ready for registration.

But remember, lineselection currently requires GS1 barcodes  - or a (barcode converter to circumvent this requirement)

How to set it up

In order to enable this functionality a <lineSelection> request needs to be setup in application.cfg inside the service xml element for the specific service type.

...

Once the service is set up, the page can be set up as follows to dictate define in which order, the online request should be made.

...

The <lineSelection .../> element can be setup set up in three ways:

• LocalFirst - Use the scanned barcode to search for an order line locally, and if no match was found, a request is made to the backend
• LocalOnly - Only search locally for an order line match
• OnlineFirst - Send a request to the backend first, and if that did not result in any order line match, search locally
  See Order Lines Mobile Configuration

...

• Refreshing the order lines can be done by returning the following response
• After refreshing the refreshorder lines, the scan triggering the online request will be further used again to potentially either select a newly added lineline, or display an error message that no match was made.

<responseData xmlns="http://schemas.taskletfactory.com/MobileWMS/BaseDataModel">
  <RefreshOnSuccess>true</RefreshOnSuccess>
</responseData>

...

<responseData xmlns="http://schemas.taskletfactory.com/MobileWMS/BaseDataModel">
  <select xmlns="http://schemas.taskletfactory.com/MobileWMS/WarehouseInquiryDataModel" name="LineNumber" value="300000">
    <values>
      <ExpirationDate>26-10-1980</ExpirationDate>
      <LotNumber>Lotty261080</ExpirationDate>LotNumber>
    </values>
  </select>
</responseData>

...

• If values are set on the registration collector through the values element, they can either be automatically accepted using the fastForwardMode on the Workflow Configuration, or just added for the user to accept
• The barcode needs to be Gs1, and contain either an item number or a serial number

...

...