Inriver integration framework

Integrating PIM with standard adapters can make it easy to connect PIM to target systems, but it can also limit the PIM model.
The Inriver Integration framework decouples standard adapters to better focus on integrating to the target system, and focus less on the Inriver part of the integration.
To specify how channels are exported the framework sets up the entity type ExportTarget. This entity contains information specific to a channel being exposed throughthe framework.
The PIM model is mapped using the integration_model of the integration framework.
This is a JSON document that maps the model to the outbound model.This outbound model is generic and defined by the integration framework.
Keeping this model generic makes sense as it enables higher quality standard adapters.
There are still model limitations, and as the integration framework runs as extensions in Inriver SaaS it has limitations in memory and relies on the ChannelStructure being in sync.