Use this event to
| Excerpt |
|---|
Add steps to be displayed at the mobile device when collecting values for each individual document line. |
...
- Are executed when values for each line is collected
- Is merged with existing worlflow workflow steps
- New steps is always declared as collectorConfiguration-Key in Reference Data.
- These new steps is added by calling the Create_StepsByReferenceDataKey-function (Currently only once*)
- For Android App the sort Sort order for new steps will usually be by Id but can be modified using the
<orderLineConfiguration><extraInformationConfiguration stepSorting="ById"/><orderLineConfiguration/>tag in the configuttion mobile configuration file. - For Windows Mobile the sort order for new steps is determined by the App and cannot be modified.
*) 
Currently the Windows Mobile App and Android Mobile App 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
// [Template]
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Put Away", 'OnGetPutAwayOrderLines_OnAddStepsToWarehouseActivityLine', '', true, true)]
procedure OnGetPutAwayOrderLines_OnAddStepsToWarehouseActivityLine(var _BaseOrderLineElement: Record "MOB NS BaseDataModel Element"; _WhseActivityLine: Record "Warehouse Activity Line")
begin
end;
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...