Use this event to
| Excerpt |
|---|
Add steps to be displayed at the mobile device when collecting values for each individual document line. |
Description
Steps defined at line level (collected for each individual line) requires a collectorConfiguration-Key to be declared in Reference Data.
This is unlike steps at header level, that allows steps to be declared directly in the OnGetReceiveOrderLines_OnAddStepsToAnyHeader event.
- So you must use this event in conjunction with OnGetReferenceData_OnAddRegistrationCollectorConfiguration
Line-level step are :
...
merged with steps from your existing workflow
...
in application.cfg
You may add custom steps using either a the _Steps-parameter or a ConfigurationKey to be declared in Reference Data.
...
The _Steps-parameter is the easiest and most flexible to use, but you may consider using a ConfigurationKey when performance or backwards compatibility with older Android Apps is more important to you.
| Using _Steps-parameter | Using ConfigurationKey from ReferenceData |
|---|---|
| Easier syntax (Steps defined on-the-fly) | More difficult to use (requires ConfigurationKey in ReferenceData) |
| Multiple subscribers to same OnAddSteps event is possible | Only a single subscriber must exist to same OnAddSteps event |
| Performance cost is 5%-10% per step added to order lines | No performance cost per additional step |
| Minimum requirements are Mobile WMS 5.39 and Android App 1.8 | Minimum requirement is Mobile WMS 5.11 |
...
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnGetReceiveOrderLines_OnAddStepsToAnyLine', '', true, true)]
local procedure OnGetReceiveOrderLines_OnAddStepsToAnyLine(_RecRef: RecordRef; var _BaseOrderLineElement: Record "MOB Ns BaseDataModel Element")
begin
end;
Example: Using _Steps-parameter
...
// [Example]: Add steps referenced by new RegistrationCollectorConfiguration-Key to line steps collectors
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnGetReceiveOrderLines_OnAddStepsToAnyLine', '', true, true)]
local procedure MyOnGetReceiveOrderLines_OnAddStepsToAnyLine(_RecRef: RecordRef; var _BaseOrderLineElement: Record "MOB NS BaseDataModel Element")
begin
_BaseOrderLineElement.Create_StepsByReferenceDataKey('CustomReceiveSteps');
end;
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Reference Data", 'OnGetReferenceData_OnAddRegistrationCollectorConfigurations', '', true, true)]
local procedure MyOnGetReferenceData_OnAddRegistrationCollectorConfigurations(var _Steps: Record "MOB Steps Element")
begin
_Steps.InitConfigurationKey('CustomReceiveSteps');
_Steps.Create_DecimalStep(10000, 'CustomNetWeightGrams');
_Steps.Set_header('Net Weight (Grams)');
_Steps.Set_label('Net Weight (Grams):');
_Steps.Set_helpLabel('Net Weight in Grams per Base Unit of Measure');
_Steps.Set_minValue(0);
_Steps.Set_maxValue(100000);
_Steps.Set_performCalculation(true);
end;
Sorting Steps for order lines
Steps are generally sorted by Id. This can be changed using the <orderLineConfiguration><extraInformationConfiguration stepSorting="ById"/><orderLineConfiguration/> in application.cfg
| Filter by label (Content by label) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...