Intro and a some history
With Business Central Fall Release 2019 (version 15) C/SIDE development has reached the end of the road. AL is now the only way of doing customization's.
Starting with MOB 4.33 (released December 2018) we have had an App Source (Cloud) 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 still allows in-code customization.
These first .al versions was an AL porting of our existing C/SIDE application and introduced only few new features to better support Mobile WMS customization via Extension.
With MOB 5.00 we take the next step, the API:
Introducing Integration Events that allows Mobile WMS to be easily extended by YOU, without modifying the Main extension!
(We like to refer to this as "the API")
Request new features / Integration Events
This first version of our Integration Events API (.al) supports a subset of the most common customization's. These include modifying the XML Response documents, creating new Reference Data and creating/posting your own new AdHoc and Lookup documents.
Additional features has been planned for 2020. When our API is fully implemented, we expect to support almost any customization to Mobile WMS via Extensions.
Should you require a feature or Event that is not listed in our released or planned features (below),
Then submit your usage scenario to us via the service desk here
Features included in MOB 5.00
Please find the integration events in the API Documentation.
Each integration event includes
- A Code template
- A working code example
to copy to your own VS Code project!
A common denominator for the integration events is the introduction of new patterns for working with the Mobile Response without having to handle XML data.
This eliminates the need for any deep knowledge of the underlying Request/Response structure and ensures correct formatting and encoding of data.
Some select high-level descriptions of 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.
Features planned for 2020
These additional events support has been planned:
- Additional filtering possibilities for "GetOrders" and "GetOrderLines"
- Add or modify RegistrationCollectorSteps at any level ("Header"-level, "Line"-level and to be displayed during posting)
- New "Steps Library" to easily reuse all types of steps currently used by the Mobile WMS base app as well as selected commonly customized steps (i.e. "Signature")
- More knowledge base documentation How-to's, Cases and Tuturials.
- Flag Response if it was was created/modified by extension (customization), to better trace errors during Help Desk requests.
Dec 2019