Use this event to
| Excerpt |
|---|
Add steps to be displayed at the mobile device when collecting values for each individual document line. |
...
- ..merged with existing workflow steps
- ..declared as part of a collectorConfiguration-Key in Reference Data.
- ..added by calling the Create_StepsByReferenceDataKey-function (Currently only once)
- ..sorted by Id. Sorting can be changed using the
<orderLineConfiguration><extraInformationConfiguration stepSorting="ById"/><orderLineConfiguration/>in mobile configuration.
| Using _Steps-parameter | Using ConfigurationKey from ReferenceData |
|---|---|
| Minimum requirements are Mobile WMS 5.39 and Android App 1.8 | Minimum requirements are Mobile WMS 5.11 |
| 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 order line |
Currently Mobile WMS supports only one (custom) referenced key per Order Line, meaning only one customization may subscribe to this event at any time. This single one subscriber must set a Key that includes all steps for all other intended subscribers as well. This can only be done by knowing other customizations are in place and manually create a new RegistrationCollectorConfigurationKey that includes all steps (this will improve in a future version).
Template
[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
were
Example: Using ConfigurationKey from ReferenceData
Currently Mobile WMS supports only one (custom) referenced key per Order Line, meaning only one customization may subscribe to this event at any time. This single one subscriber must set a Key that includes all steps for all other intended subscribers as well. This can only be done by knowing other customizations are in place and manually create a new RegistrationCollectorConfigurationKey that includes all steps.
// [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;
| Filter by label (Content by label) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...