Workflow Nodes

IDHub provides different nodes which you can leverage to create your custom workflow to cater to your specific organisation scenarios. This document would elaborate on the different nodes provided by IDHub.

Types of Nodes

There are basically there different types of nodes in an IDHub workflow which are as follows:

1. Operation Node
2. State Node
3. Action Node

Let’s go into each one of these nodes in further details

Operation Node

What are Operation Nodes?

Operation nodes are the nodes through which you can do different operations in the workflow.

What are the different operation nodes provided by IDHub?

Following are the Operation Nodes provided by IDHub includding their description, input and required attributes

Name	Description
Create Task	This is used to create a task based on the payload given and assign it to users.
Update Task	This is used to update the status, add other attributes in the task.
Send Notification	The send notification node is used to send the notification based on the parameters
Fetch User	This is used to fetch users for further actions. For Example: To send an email to all the users who are a part of a role, you would need the user objects to retrieve the value of the email id
Update Request	used to update the status of the request or add other metadata to the request object
Fetch Entitlement	This fetches the entitlement in the User Account collection to be added by provisioning engine
Update Request	The Update request node is used to update the payload of the given request
Check For Task Completion	This node is used to check whether the task is completed or not.
Revoke Expired Accounts	If you want to revoke the accounts which are expired then you can use this node.
Fetch Expired Accounts	You can use this node to fetch all the expired user accounts and revoke them using the Revoke Expired Accounts node.
Create Ticket	This node is used to create a Ticket (Zendesk, JIRA). This node is useful in scenarios where you would like to create support desk ticket in your business logic.
Cancel other Tasks	This node is used to cancel any open tasks, if any task is still open.
Create Request	This node is used to create a request in the workflow based on the provided payload.
Reject Fulfillment	This node is used to reject a Fulfillment Task. In scenarios of Disconnected application provisioning, if you want to reject the fulfillment task generated then you can use this node in the workflow.
Complete Request	This node is used to complete a Request generated in the workflow.
Complete Approval	This node is used to complete the approval of onboarding tasks.
Webhook	This node is used to make REST API calls. GET, POST, PUT, DELETE, and PATCH methods are allowed
Javascript	The node is used to execute the self-contained function that was specified in the node. Any parameters for the function can be specified in the javascript code

State Node

What is a state node

State nodes are the one which is used to denote a certain state of the request in the workflow. For example: Request Submitted, Request Completed etc.

What are the required attributes in a State Node

• Name
  • This name is only being used in the workspace area of 'Create workflow'
• State
  • This is the status name either provided by IDHub in the initial stage as 'Request Submitted' or otherwise added by you
• IsResolution
  • If you want to update the resolution of the request status, then you can make this as true
    • Resolution
    • Resolutions can be 'Assigned', 'Expired', 'Completed' etc

Action Nodes

What is a Action Node

Action nodes are the one which is used to perform certain action of the request in the workflow. There are two types of Action Nodes provided by IDHub.

• Condition Node
  • This is used to check certain condition in the workflow. For Example: Approver is Absent or not.
• Action Node
  • This node is used to perform action for the request in the workflow. For Example: Start, Reject, Approve etc.