Page Comparison

Description

Example 1: Planned function posting

Using this event OnPostReceiveOrder_OnBeforePostAnyOrder

[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostAnyOrder', '', true, true)]
    local procedure OnPostReceiveOrder_OnBeforePostAnyOrder(var _OrderValues: Record "MOB Common Element"; var _RecRef: RecordRef);
    var
        MobToolbox: Codeunit "MOB Toolbox";
    begin
        MobToolbox.ErrorIfNotConfirm('You are stopped for some condition... Do you want to continue?', _OrderValues);
    end;

Example 2: LockOrder (Planned function, when an Order is selected)

Using this event OnLockOrder_OnBeforeLockOrder

    [EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Order Locking", 'OnLockOrder_OnBeforeLockOrder', '', true, true)]
    local procedure ShowConfirmBox_OnBeforeLockOrder(_MobDocumentQueue: Record "MOB Document Queue"; var _RequestValues: Record "MOB NS Request Element"; var _IsHandled: Boolean)
    var
        MobToolbox: Codeunit "MOB Toolbox";
    begin
        if _RequestValues.GetValue('Type') = 'Pick' then
            MobToolbox.ErrorIfNotConfirm(_RequestValues, 'You are stopped for some condition... Do you want to continue?');
    end;

Example 3: Custom Unplanned function 

Using this event OnPostAdhocRegistrationOnCustomRegistrationType

        [EventSubscriber(ObjectType::Codeunit,  Codeunit::"MOB WMS Adhoc RegistrMOB WMS Adhoc Registr.",  'OnPostAdhocRegistrationOnCustomRegistrationTypeAsXmlOnPostAdhocRegistrationOnCustomRegistrationType',  '',  truetrue,  truetrue)]
        local procedure My01OnPostAdhocRegistrationOnCustomRegistrationTypeAsXml My01OnPostAdhocRegistrationOnCustomRegistrationType(var _XMLRequestDocRegistrationType:  XmlDocumentText;  var  _XMLResponseDoc: XmlDocument; _RegistrationType: Text; var RequestValues: Record "MOB NS Request Element"; var _SuccessMessage: Text; var _RegistrationTypeTracking:  Text[200];  var  _IsHandled:  Boolean)
        var
        MobToolbox        MobToolbox:  Codeunit  "MOB ToolboxMOB Toolbox";
        begin
                if  _RegistrationType <> RegistrationType <> 'MyNewUnplannedName' then
                        exit;

        if  _IsHandled IsHandled then
                        exit;
        MobToolbox
        MobToolbox.ErrorIfNotConfirm('You are stopped for some condition_RequestValues, 'You are stopped for some condition...  Do you want to continueDo you want to continue?', _XMLRequestDoc);
        MOBToolbox.CreateSimpleResponse(_XMLResponseDoc, '');
        _IsHandled := true;
    end;
);

        _SuccessMessage := 'My custom success message';
        _RegistrationTypeTracking := 'My custom description for the document queue (column RegistationType)';
        _IsHandled := true;
    end; 

Example 4: Custom Unplanned function (legacy XML version)

Using this event OnPostAdhocRegistrationOnCustomRegistrationTypeAsXml

    [EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Adhoc Registr.", 'OnPostAdhocRegistrationOnCustomRegistrationTypeAsXml', '', true, true)]
    local procedure My02OnPostAdhocRegistrationOnCustomRegistrationTypeAsXml(var _XMLRequestDoc: XmlDocument; var _XMLResponseDoc: XmlDocument; _RegistrationType: Text; var _RegistrationTypeTracking: Text[200]; var _IsHandled: Boolean)
    var
        MobToolbox: Codeunit "MOB Toolbox";
    begin
        if _RegistrationType <> 'MyUnplanned' then
            exit;

        if _IsHandled then
            exit;

        MobToolbox.ErrorIfNotConfirm('You are stopped for some condition... Do you want to continue?', _XMLRequestDoc);

        MOBToolbox.CreateSimpleResponse(_XMLResponseDoc, '');
        _IsHandled := true;
    end;

How it works behind the scenes 

The key ”ForceWarning:” is prefixed to a regular ERROR() command.

Error('ForceWarning:%1', MyConfirmMessage);

1. This way front-end App knows to a display a Confirm dialog
   
   
   1. Choosing "Cancel" will return the user to the previous screen
   2. Choosing "Confirm" will automatically repeat the request with a “Force” tag included
      
      
2. The Force tag tells the backend that the Process can now be completed and NOT halted by the ERROR command.