In this document we discuss, “Fulfillment Workflow”, which is one of the out-of-the-box workflows provided by IDHub.

Fulfillment Workflow Description

In this section we explain the steps and flows, taken by IDHub, to execute the “Fulfillment Approval Workflow”.

  • The first step is a “State Node”. A state is one of the several states/statuses in IDHub. This 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, by default, the state is “Request Submitted”. The first step in this workflow is “Request Submitted” state node.

  • In the next step, we have the “Action Node”. The Action Node denotes a task action, or a workflow action. It is present immediately after the state node, and it is used to trigger a flow. In our case, the action node would be “Start”.

  • Thirdly, we have the “Operation Node”. This node is used to perform small atomic operations, required to complete a transition. Operation Nodes are custom developed nodes, used to perform a particular function.

    • Fulfillment Task operation node, means the state of the request is Waiting for Fulfillment.

At this point, the fulfiller would make the decision to Reject or Accept the request. Depending on the decision, IDHub would process the flow accordingly. Below are the steps for both scenarios.

*Flow steps are below, if the request has been REJECTED by the Fulfiller.

  • In this case, we have the Fulfillment Reject action node, which denotes that the task has been rejected by the Fulfiller.

  • The request is now deemed complete, and we have the state node “Request Completed”.

*Flow steps are below, if the request has been ACCEPTED by the Fulfiller

  • In this case we have the Fulfillment Approve action node, which denotes that the task has been approved by the Fulfiller.

  • The request is now deemed complete, and we have the state node “Request Completed”.