Routing and processing
The message is passed to the service input queue of the MSIF service. It is deleted from the MER database.
The message flow DNQ_K_MX1 implements all business routing logic for the MX scenario 1. Each combination of source queue and condition corresponds to one filter pattern in the Route node of the flow. The combinations of source queue and condition are evaluated in the order shown in the table. The target queue is determined by the first combination of source queue and condition that matches the values within the message.
| PT | Source queue | Condition(s) | Target queue | Queue type | NPT |
|---|---|---|---|---|---|
| B | MX1Input | The message was received from SWIFTNet. | MX1Application | A | |
| B | MX1Input | The message could be transformed if necessary and validated successfully. | MX1AuthorizeFirst | M | A |
| B | MX1Input | None | MX1Edit | M | A |
| B | MX1Edit | None | MX1Authorize | M | A |
| B | MX1Create | None | MX1Authorize | M | A |
| B | MX1AuthorizeFirst | The message was rejected by the authorizer (UserAction= REJECT). | MX1Edit | M | A |
| B | MX1AuthorizeFirst | None | MX1AuthorizeSecond | M | A |
| B | MX1AuthorizeSecond | The message was rejected by the authorizer (UserAction= REJECT). | MX1AuthorizeFirst | M | A |
| B | MX1AuthorizeSecond | None | MX1RtS | M | B |
Legend:
- PT
- Processing type:
- B
- BUSINESS
- U
- USERACTION
- Queue type
- The type of the next MER queue:
- M
- MAIN
- D
- DRAFT
- B
- BACKOUT
- R
- REDIRECT
- T
- TEMPLATE
- NPT
- Next processing type:
- A
- APPLICATION
- B
- BUSINESS
- U
- USERACTION