Dependencies Between Response Routes
Response Routes can be dependent on one another as shown in the following figure.
(1) A Response Route, with format and transmission method. There may be any number of these Response Routes in a profile.
(2) State of the Response Route. In this case, Error.
(3) State of the Response Route. In this case, Success.
(4) A dependency of a Response Route from the status of a previous Response Route. In this case, the dependency on error. Thus, Response Route B is executed only if Response Route A has the status Error.
(5) Response Route without dependency on previous Response Routes.
(6) A dependency of a Response Route from the status of a previous Response Route. In this case, the dependency on success. Thus, Response Route D is executed only if Response Route B has the status Success.
Example
Response Route D depends on Response Route B. Response Route B is not executed due to its own (unfulfilled) dependencies. In this case, Response Route B gets status Skipped. As a result, Response Route D is not executed and also gets status Skipped because it depends on Response Route B. Generally, Response Routes dependent on skipped Response Routes are not executed.
GUI: The configuration of this phase is described in section Phase 6 (GUI). See especially section Dependencies.