AIMS Approval Workflow Document
Purpose of the document
In this document we would be discussing the “AIMS Approval” Workflow, which is one of the out of the box workflow provided by IDHub.
AIMS Approval Workflow Description
In this section we would describe the steps and flows which is taken by IDHub in executing the AIMS Approval workflow.
The first step is a “State Node”. A state is one of the several states/statuses that is there in IDHub. So this basically represents a request state in the workflow. This node does not perform any function. A flow is stopped when this node is reached. When a request is submitted, then by default the state is “Request Submitted”. So the first step in this workflow is “Request Submitted” state node.
In the next step, we have the action node. Action note denotes a task action or a workflow action. It is present immediately after the state node and is used to trigger a flow. In our case, the action node would be “Start”.
After the 2nd step, we have the Operation node. This node is used to perform small atomic operation required to complete a transition. Operation nodes are custom developed nodes to perform a particular function.
In our case the 3rd step is Approval Task operation node. This means that the request is submitted to the Access Manager.
Next we have the state node, and the state of the request workflow is Waiting for Approval.
At this point, Access Manager would take a decision, whether he would like to either Reject or Approve the task. Depending on that, system would take the flow accordingly. Below we are describing the flow steps in each case.
Flow Steps in case of Rejection of task by the Access manager.
In this case, we have the Reject action node, which denotes that the task has been rejected by the access manager.
Then the request is deemed completed and we have the state node, with state being ‘request completed’
Flow Steps in case of Approval of task by the Access manager.
In this case we have the Approve action node, which denotes that the task has been approved by the access manager.
After that we have the complete request operation node. So then the request is deemed completed and we have the state node, with state being ‘request completed’