Upon completion, we click back on the โapprove_pageโ field and add an approval action step by clicking on the โActionโ button in the top navigation bar.
Again we add a tag and permission. Note that we choose the action type of โselector.โ This allows us to add Options as fields to the UI for different types of selections โ approval/rejection.
Note that for the approve option we are binding the action to the โupdate_approve_document_statusโ we defined before.
Note that for the reject option we are binding the action to the โinstaller_rejectedโ action we previously defined.
Next, we return to the โapprove_documents_gridโ step and add the โapprove_documents_btnโ action as a binding block to Field 4 since Field 4 captures the approval or rejection of the document. Note, the choice of block for Field 4 makes sense now, because the bound action is a block itself.
Programmatically this workflow step looks like this:
This completes the definition of the approval page.