1. Integration Guide
  2. Processing Overview

Processing Overview

Once an event triggers the requirement to send a Transmission for one or more objects, the following processing takes place. The exact steps differ depending on the media type of the target message i.e. whether the External System is expecting "application/xml" or "application/json".

  1. Construct internal objects based on SQL Queries. Out XML Profiles are applied during the generation of the objects for XML messages.
  2. Convert the objects into a string representation.
  3. If anything other than the Current Target Namespace is selected then this conversion takes place now.
  4. Apply XSL Transformations if needed (for XML).
  5. Save the resulting output to the I_TRANSMISSION table. If the outbound integration is designated as a Mobile Device message (e.g. generated via the Compose and Send UI action or dispatch actions), then an entry is also stored in the I_MESSAGE table.
  6. Send the resulting output via the indicated notify type (e.g. HTTP POST). The External System record in Transportation and Global Trade Management Cloud indicates whether or not an acknowledgment is required from the external system.
  7. Updates the status of the Transmission.