Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
What is it
Collect additional data on line basis. (Not to be confused with Header level)
Description
Collector steps are define in "Reference Data". Making them static to a degree.
However, often you want the step to have a Default Value or other information related to the current Line.
- 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
If needed, you can create a whole new workflow and add it to the App config file Frontend - Configuration files
- make a Collector Step on a Line dynamic by adding the relevant "Item No." as Default value and as a Help Text
Note:
- Please start by following a complete example of adding a Collector Step on Line basis.
- Seek inspiration in Codeunit MOB Conf. Tools
Syntax
'CollectorKey{[key][attribute][value]}'
For example:
RegisterExtraInfo','DemoOrderLineExtraInfo{[StepNameA][PropertyA][ValueA][StepNameB][PropertyB][ValueB]}
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:Image Removed
Code Block | ||
---|---|---|
| ||
CreateConfigRegCollConf(XMLResponseData,'CountLineExtraInfo'); |
Image Removed
Image Added
Code Block | ||
---|---|---|
| ||
... 'CountLineExtraInfo': BEGIN// Example of making a step dynamic MobConfTools.RC_Std_Parms(1,'MyTextStep','Enter my text','','Please confirm my // ID 'CountLine', // Name text'); MobConfTools.RC_Text_CData(XMLCDataSection,'',20); // Default value = blank because it will be injected dynamically from the Line |
Step 2 - Include the step in a Warehouse functionality like Pick
Image Added
Code Block | ||
---|---|---|
| ||
IF WhseActHeader.Type IN [WhseActHeader.Type::Pick,WhseActHeader.Type::"Invt. Pick"] THEN 'Count LineMobXMLMgt.AddElement(XMLOrderLine,'RegisterExtraInfo', // Header STRSUBSTNO('DemoOrderLineExtraInfo{[MyTextStep][defaultValue][%1][MyTextStep][helpLabel][We 'Extra info:'expect "%1"]}',WhseActLinePlace."Item No."), // 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.
Image Removed
Code Block | ||
---|---|---|
| ||
MobXMLMgt.AddElement(XMLOrderLine,'RegisterExtraInfo','CountLineExtraInfo',BaseDataModelNS,XMLCreatedNode); |
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.
Image Removed
Add the following code block to handle the collected value, stored in a tag called "CountLine" as per above naming.
Image Removed
Code Block | ||
---|---|---|
| ||
IF XMLExtraInfoElementNode.Name = 'CountLine' THEN; |
See also:
Examples
Image Removed
Collect an integer
Image Removed
Show information
Image Removed
A boolean step
Image Removed
NS_BASE_DATA_MODEL,XMLCreatedNode); |
See also:
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
See also:
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Example
Image Added
Collect an text - Note the dynamic values