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

Certification Workflow Description

In this section we explain the steps and flows, taken by IDHub, to execute the “Certification 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”. In this section we explain the steps and flows, taken by IDHub, to execute the “Certification Workflow”.


At this point, the workflow would decide whether an Approver is Required or Not Required. Below are the steps for both scenarios.

*Flow steps are below, when an Approver is NOT REQUIRED.

  • In this case, the request workflow would directly go to the Create Certification Task (discussed below).

*Flow steps are below, when an Approver is REQUIRED.

  • In this case, we have the Certification Approval Task operation node, which means the request has been sent to the user who will approve the certification.

  • The request now has a state node of “Waiting for Approval”, which means the status of the request is “Waiting for Approval”.


At this point, the Certification Approver User, would make the decision to Reject or Approve the task. Depending on the decision, IDHub would process the flow accordingly. Below are the steps for both scenarios.

*Flow steps are below, if the task has been REJECTED by the Certification Approver User.

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

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

*Flow steps are below, if the task has been APPROVED by the Certification Approver User.

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

  • Now, it moves to Create Certification Task operation node (discussed below).


Create Certification Task Operation Node

  • Create Certification Task operation node is a JSON object, which creates the Certification Task Request, and converts the statues of the request to “Waiting for Certification”.

  • Next, we have the Complete Certification action node, which denotes that the Certification Task has been completed by the certifier.

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