High level overview

Integration Layer only consists of generic (helper) functions related to the interface process. All module specific code related to the interface process is part of the specific modules.

1. The packaging entries (only available/known by the Mobile Warehouse app) are packed (serialized to JSON via the Integration Layer helper function) and sent via generic functions available in the Integration Layer app, on the basis of the interface contract. It's possible to serialize to JSON automatically or define the schema (per field (type) + how to handle) yourself.
2. The package is received and unpacked (deserialized) by the Packaging extension, again using generic functions available in the Integration Layer app, on the basis of the interface contract. When fields aren’t present in the defined schema, they will not be parsed i.e. skipped.
3. The App Integration Code triggers the defined procedure in the Packaging extension. In this case, register the Packaging entries on the basis of the received record set in the actual Packaging entries table (only available/known by the Packaging app). When all goes well, Packaging will set Handled to true. When errors occur in this final step, it’s necessary to also backport the messages to the Mobile Warehouse extension. Again, this is possible by using the generic functions available in the Integration Layer app on basis of its specific interface contract.