Full Acknowledgement
This requires both acknowledgement flags in the handling specification extension to be set to “true”. This is the most rigorous response framework supported by ITK3. The sender will receive up to two responses and will response to the business level response when two responses are received. There are 3 possible information flows which are defined below.
Note: The diagrams assume that all response messages are valid and can be processed by receiving system.
Issue is Detected at Technical Level
The diagram below shows the response flows when an issue is detected at the technical level.
| Sender | Flow | Receiver |
|---|---|---|
| START | ||
| 1..1 | Send Payload |  |
 |
Infrastructure Level Response | 1..1 |
| END |
The diagram below shows the response flows and MESH response flows when an issue is detected at the technical level.
Issue is Detected at Business Level
The diagram below shows the response flows when an issue is detected at the business level.
| Sender | Flow | Receiver |
|---|---|---|
| START | ||
| 1..1 | Send Payload | |
|
Infrastructure Level Response | 1..1 |
|
Business Level Response | 1..1 |
| 1..1 | Infrastructure Level Response | |
| END |
The diagram below shows the response flows and MESH response flows when an issue is detected at the business level.
No Issues Detected
The diagram below shows the response flows when no issues are detected.
| Sender | Flow | Receiver |
|---|---|---|
| START | ||
| 1..1 | Send Payload | |
|
Infrastructure Level Response | 1..1 |
|
Business Level Response | 1..1 |
| 1..1 | Infrastructure Level Response | |
| END |
The diagram below shows the response flows and MESH response flows when no issues are detected.
