Database Reference
In-Depth Information
Then, it sends an approval that creates the level 1 approval, which is an application called
AppForApprovalsLevel1
. After the
Approve
or
Deny
button is selected, it creates a
new message that is sent back to the saga, and the saga handles the messages. Depending
on the return message, it will either call the
IHandleMessages<Ap-
proveRequestCommand>
or
IHandleMessages<DenyRequestCommand>
handler. The saga will be pulled up by the bus, as we had the mapping code in this ex-
ample to map the messages to
RequestID
.
We can pull up the saga that matches the message and routes it based on some logic—in
this case, the cost—or returns it to the originating client. The saga may contain a huge part
of the original message, so all of it doesn't need to be propagated through messages.
