Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.





 




 

Table of Contents
maxLevel3
minLevel0
indent1



Intro and some history

With Business Central Fall Release 2019 (version 15) C/SIDE development has reached the end of the road. AL  
AL is now the only way of doing customization's. Starting with MOB version 4.33 (Since December 2018 ) we have had an AppSource offer for Business Central.


But if you needed to do any major customization work you had to take ownership of our (Per-Tenant) extension, which allows in-code customization.

The These first AL versions introduced very limited support for extending Mobile WMS. 

With MOB 5.00 we took have taken the next step to fully embrace the AL platform: The Extension API.

Introducing The API introduces Integration Events and code patterns that allows Mobile WMS to be easily extended, without modifying the Main extension.


Benefits include:

  • Simplified functions, so you can focus on the customers requirement and not the system.
  • New patterns for working with the data without handling XML response data manually, eliminating need for knowledge of the underlying Request/Response structures.
  • "Documentation Driven Development" where every Mobile WMS event can easily access via the API Documentation area.
Find
  •  
    • Including working code examples to copy to your own VS Code project

Explore the new integration events in the API Documentation

The For all events the documentation includes:

  • Code templatestemplate
  • Working code examples to copy to your own VS Code project

Benefits include:

  •  All events are new patterns for working with the data without handling XML response data manually.
This eliminates the need for any deep knowledge of the underlying Request/Response structure and ensures correct formatting and encoding of data


How-to articles and Tutorials will get you started:


Descriptions of some integration events:

Create your own new ReferenceData (headerConfigurations, registrationCollectorConfigurations and ListData.
This includes a new pattern to create headerConfigurations without writing directly to the Xml.  The API documentation for new ReferenceData is here.

Set custom Xml Response content from all major document handler codeunits.  
This includes a new pattern for modifying Xml Content without writing to directly to the Xml (via new "OnAfterSetFrom[...]-events) l. An introduction can be found here  Whitepaper: Custom XML Response Extensions . A sample use is i.e. OnGetReceiveOrders_OnAfterSetFromWarehouseReceiptHeader

Sorting Xml Response content from all major document handler codeunits
Data returned from 'Get' Document Handlers can be be sorted by any pre-existing tag or custom tag in the Xml Response documents (via new 'OnAfterSetCurrentKey[...]-events). A sample use is i.e. OnGetReceiveOrders_OnAfterSetCurrentKey

Create your own new custom document handlers and write your our own code to be executed during adhoc posting.
If pre-existing events at other document handler classes for some reason do not meet your needs, a custom new Adhoc Registr. can be written to support basically any thinkable customization via new document handlers.


Request new features / Integration Events

This Extension API supports most Most common customization's .are supported

Including:

  • Creating/posting your own custom AdHoc and Lookup documents.
  • Modifying existing Planned functions with DisplayLines, Filtering, Ordering, Adding Steps or hooking onto posting events.

  • Should you require a feature or Event, please submit your usage scenario to us here.