...
...
...
...
Use this event to
...
Excerpt |
---|
TODO Run additional code after a PostAdhocRegistration request has been executed. Implement custom document locking scheme or display messages at Mobile Device. TODO |
Description
TODO
Using this event you may implement a custom planned document locking scheme. These are the locks that are set for documents at the Mobile Device that will prevent other users from handling same documents at the same time.
Since this event is consistently called before planned documents are displayed at the Mobile Device, you may also use the event to display confirmation messages at the device when such documents are opened.
TODO
|
---|
Add/Replace steps or Manipulate Header Field Values before standard steps are generated |
Description
- Add custom steps
- Replace standard steps with custom logic
- Manipulate Header Field Values before standard steps are generated
This event is triggered before existing unplanned functions generates their steps, allowing you to manipulate how they are created.
You can also add your own steps or replace standard logic entirely using "IsHandled".
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Adhoc Registr.", 'OnGetRegistrationConfiguration_OnBeforeAddSteps', '', true, true)]
localprocedure OnGetRegistrationConfiguration_OnBeforeAddSteps(_RegistrationType: Text; var _HeaderFieldValues: Record"MOB NS Request Element"; var _Steps: Record"MOB Steps Element"; var _RegistrationTypeTracking: Text; var _IsHandled: Boolean)
begin
end;
Parameters
Expand |
---|
title | Click here for parameters... |
---|
|
- _RegistrationType: The registration type you want to manipulate. "UnplannedMove", "UnplannedCount", "AdjustQuantity" etc.
- _Steps: The resulting Steps to display
- _IsHandled: Handling the registration type will replace the standard logic entirely
- _HeaderFieldValues: Values from Header
- _RegistrationTypeTracking: Optional tracking information for Mobile Document Queue List
|
Example
Add a new step to Unplanned Move, collecting a "Reason Code" for the movement.
// Example 1: Add Reason Code step to Unplanned Move
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Adhoc Registr.", 'OnGetRegistrationConfiguration_OnBeforeAddSteps', '', true, true)]
localprocedure OnGetRegistrationConfiguration_OnBeforeAddSteps(_RegistrationType: Text; var _HeaderFieldValues: Record"MOB NS Request Element"; var _Steps: Record"MOB Steps Element"; var _RegistrationTypeTracking: Text; var _IsHandled: Boolean)
var
MobWmsToolbox: Codeunit"MOB WMS Toolbox";
Location: Text;
begin
if _RegistrationType <> MobWmsToolbox."CONST::UnplannedMove"() then
exit;
// Create step for Reason Code. Id 95 is not used by standard steps.
_Steps.Create_ListStep_ReasonCode(95, _HeaderFieldValues.Get_ItemNumber());
end;
...
;
// Read the Reason Code from request and apply to Whse. Journal Line [EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Adhoc Registr.", 'OnPostAdhocRegistrationOnUnplannedMove_OnAfterCreateWhseJnlLine', '', true, true)]
localprocedure MyOnPostAdhocRegistrationOnUnplannedMove_OnAfterCreateWhseJnlLine(var _RequestValues: Record"MOB NS Request Element"; var _WhseJnlLine: Record"Warehouse Journal Line")
begin
_WhseJnlLine.Validate("Reason Code", _RequestValues.GetValue('ReasonCode'));
end;
Filter by label (Content by label) |
---|
showLabels | false |
---|
showSpace | false |
---|
sort | title |
---|
title | More examples |
---|
excerptType | simple |
---|
cql | label = "bc" and label = "example" and label = "adhoc" and label = "onafterpostonbeforeaddsteps" |
---|
|
Version History
Version | Changes |
---|
MOB5.48 | Introduced |
...