Note: These steps are repeated for each destination connector that a message flows through.
The encoded content from the source connector is used by each destination connector as its 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 for the current destination here. If there are additional destinations in the current chain, these steps are repeated for the next destination. Otherwise, assuming all other destination chains have finished, flow 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 is 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.
The destination connector builds a message from all available previous content, stores it as sent data, and sends it to the outbound system.
A response is received by the destination connector and stored as the response data.
If a response transformer is configured, the response content is serialized (converted) to the internal representation of the responseinbound data type (e.g. XML).
The response content runs through the response transformer, where it may be modified.
The post-response-transformer content is stored as the responsetransformed data.
The response content is deserialized (converted) from the response outbound data type's internal representation (e.g. XML) into the actual outbound format (HL7, EDI, etc.).
The response content is stored as processed response data.
