(3.10) Payload Persistence

On Dell Boomi, there is a lack of standard API to fetch the message payloads from the platform. To log the messages, every client builds a custom message persistence mechanism or archives the wanted messages on Atom’s installation Directory

To save the message payloads in Int4 IFTT, there is the need to send the complete message together with the additional interface details to Int4 IFTT WebService.
Our proposal for this is to use an additional process, called SavePayload, that will read all the obligatory data, map them to the required structure and send all the details to Int4 IFTT.

This process can be added directly to the actual processes tested or on your custom logging mechanism.