The email request is held
Handle send email before using the approval
- outcome
- PERMIT_WITH_APPROVAL
- dispatch
- false
- executed
- false
- reason
- approval_required
- effect
- send_email
- actor id
- operator
- resource
- mailbox
- request id
- approve-1
Record an approval, send it back through CRUSHIA, and keep a locked effect denied.
Recommended first: Product training. You can still study this lesson.
An approval is a recorded fact. It names the request and the person. It does not mint authority, it does not dispatch, and it is not a permit. The next send-email request is decided again by CRUSHIA. The outcome is still PERMIT_WITH_APPROVAL. The fact re-entered the decision. It did not replace the decision. A production.deploy request marked approved stays DENY, reason locked deny. Locked DENY stays DENY.
These fields were returned by the teaching workstation for this lesson. They are not a production permit.
Handle send email before using the approval
Record the duty officer's approval of that request
Handle a new send-email request after the fact is recorded
Ask for production.deploy and mark the request approved
Say where the approval goes. It goes back into the decision. It does not go to Rain.
This lesson is not complete yet.
A passed check is saved in this browser so you can resume. It is not a certificate, not an accreditation, and not authority to run an effect.