Policy Workflow Step 20
An āapprove_pageā needs a document source to approve a document. Therefore, we are adding a document source below the āapprove_pageā by clicking on the āDocumentsā button in the top navigation bar.
The āapprove_documents_gridā has the permission for the Standard Registry, must be active by default is of data type āapprove.ā
In contrast to the installer case where we create documents and send them for approval, we have no dependencies on the incoming documents. We take account of this by adding the āsave_new_approve_documentsā dependency.
Next, we add the required custom UI fields on the approval UI form. Note that since this is a general approval form we do not have to specify a schema or an entity type for the UI.

Below are the screenshots of the field inputs





Programmatically this workflow step looks like this:
Last updated
Was this helpful?