Description

Collect additional data per line, not to be confused with Header level steps

In this example we will use the (planned) Count function.

Standard workflow collector steps

From Bin
To Bin
Expiration Date
Lot No.
Tote ID
Serial No.
Quantity

Planned functions that use the "Standard workflow"

Receive
PutAway
Pick
Ship
Count
Move

This article describes the only way to add steps to the standard workflow using CAL code
You can create a whole new workflow and add it to the Application.cfg file

How to enable

Step 1 - Add/Define the collector step in Reference Data

When a device log in, Reference Data is sent to the device. We need to include the definition of our collector to the Reference data.

We will name our collector step "CountLineExtraInfo".

Add the following two code blocks:

Block 1: Codeunit 6181381 TF Mobile WMS Reference Data

CreateConfigRegCollConf(XMLResponseData,'CountLineExtraInfo');

Block 2: Codeunit 6181381 TF Mobile WMS Reference Data

  'CountLineExtraInfo':
    BEGIN
      MobConfTools.RC_Std_Parms(1,              // ID
                                'CountLine',    // Name
                                'Count Line',   // Header
                                'Extra info:',  // Label
                                'Extra info');  // Help Label

      MobConfTools.RC_Decimal_CData(XMLCDataSection,0,0,0,3,TRUE);
    END;

Step 2 - Include the step in the Count functionality

The function CreateOrderLinesResponse is responsible for the reply to the device, including which values to collect.

We will add the following code block have it include our CountLineExtraInfo.
Add you own conditions to when the step should be included, in example, certain items.

Codeunit 6181376 TF Mobile WMS Count

MobXMLMgt.AddElement(XMLOrderLine,'RegisterExtraInfo','CountLineExtraInfo',BaseDataModelNS,XMLCreatedNode);

Mobile WMS currently supports only one RegisterExtraInfo key per Order Line.

This single key must include all extra steps to be displayed. This can be done by adding steps to the existing RegistrationCollectorConfigurationKey ('CountLineExtraInfo' in the example above) or by creating a new RegistrationCollectorConfigurationKey with its own unique name that includes all steps.

If one or more steps are conditional (should be included or not included based on criteria from the order line) you will need to create new a RegistrationCollectorKey for every combination of steps to be included.

Step 3 - Handle the Posting

The XML Request from the scanner, will look like this.

Note the "ExtraInfo" tag with out "CountLine" tag included, along with the value.

Add the following code block to handle the collected value, stored in a tag called "CountLine" as per above naming.

Codeunit 6181376 TF Mobile WMS Count

IF XMLExtraInfoElementNode.Name = 'CountLine' THEN;

See also:

Page:

Case: Add Header Step to inbound goods documents (Signature Step)
Page:

How-to: Add Line Step (TypeAndQuantity)
Page:

How-to: Add Header Step
Page:

How-to: Add Line Step
Page:

Step Configuration Matrix

Examples

Collect an integer

Show information

A boolean step

An information step

Browser not supported