A message or stream of data is received by the source connector.
The batch processor decides whether to split the message into multiple messages. If so, the below steps are repeated for each message returned by the batch processor.
The attachment handler extracts and/or stores all attachment data.
The post-attachment-handler content is stored as raw data.
The content runs through the preprocessor script and is stored as processed raw data.
The content is serialized (converted) to the internal representation of the inbound data type (e.g. XML).
The content runs through the filter, and the message is either accepted or filtered. If the message gets filtered, flow stops here and jumps down to the Final Processing Steps.
The content runs through the transformer, where it may be modified.
The post-transformer content is stored as the transformed data.
The content is deserialized (converted) from the outbound data type's internal representation (e.g. XML) into the actual outbound format (HL7, EDI, etc.).
The content is stored as encoded data.
Note: If no filter or transformer are configured, there will not be any transformed or encoded data. In that case, the content used from here on will only be the raw data (or processed raw data if a preprocessor modified it).
The resulting content is passed on to the first destination connector of each destination chain.
