Supported Since: 17.01
A simple integration flow normally ends either
at a one-directional egress connector or
at the same bi-directional ingress connector that started the integration flow
But in a situation where none of the above two scenarios are possible, this processing element can be used to end an integration flow marking it as successfully completed.
Since this processing element belongs to the set of basic processing elements, this will be available for every project by default.
The message context will be sent to this outport if any exception occurred while processing
In the following use case, the requirement is to read a message from a SFTP server, perform some custom processing and then send it to a HTTP endpoint. When the response from the HTTP endpoint is received, a custom validation is performed on it and the flow should be marked as successful if the validation is successful.
To achieve the above requirement, the response path of the HTTP egress connector is connected to the custom processing element that performs the validation on the response. Then the "On Success" outport of the processing element (which will receive the message context if the validation is successful) is connected to a Successful Flow End processing element that will mark the flow as successfully ended.