Paths and Route Tasks

Route tasks can be added only to input paths.

Route tasks send each incoming message to a single destination based on which route case evaluates to true, or to a single destination designated as otherwise if none of the cases evaluate to true.

Paths on the input flow to a target operation correspond to paths on the output and fault flow from that target operation. Paths ending in Throw Fault have a corresponding mediation fault path on the Fault flow. Paths ending in a Generate Reply task have a single, common Handle Reply path on the Output flow.

Note: You can only introduce the route in the input path, and the response (output or fault) always returns to the original requester—the requester that invoked the mediation operation.
Output path for a route


Mediation tasks can be added to sub-paths after a route activity. Typically, you use a Transform task when the input, output, or fault message schema does not match the mediation operation message schema.
Fault path for a route