IDHub Workflow Overview
Identity Solutions must provide consistent security accuracy, while being agile and flexible to change when your business changes.
IDHub workflows are node-based, and use a combination of State Nodes, which request triggering actions throughout the workflow lifecycle.
Users can configure IDHub to perform simple, or sophisticated actions, while moving from one state to another, using the various Operation Nodes in the workflow designer tool.
IDHub provides a diverse range of pre-defined nodes with API capabilities, and the option to create/import custom-made nodes.
IDHub Workflow Elements
State Nodes
A State Node stops the workflow, and either terminates the workflow or awaits the next action to start.
Action Nodes
Action Nodes define any desired manual or automated, process or action, which needs to happen between two different states.
Operation Nodes
Operation Nodes are actions performed by IDHub, automatically following an Action Node, or a modifying Condition Node.
Condition Nodes
Condition Nodes process Action Nodes with multiple possible outcomes, leading to separate branches within the workflow. Condition Nodes use preexisting or custom javascript, to identify the proper result from the previous Action Node logic.
Errors
Identified errors will be labeled, to assist in debugging the configuration, ensuring proper logic and consistent operation within the workflow.
Workflow Communication
Custom Emails
IDHub comes with many out-of-the-box emails. However, customized emails sent to a set of individuals depending on approval, rejection, or any other action, can be accomplished by configuring a custom email to the workflow.
Custom Email Templates
Email templates can be created and stored separately from workflows, and used at any point within IDHub.
While creating a workflow, you can instruct the system to send notifications using an Operation Node, choosing a specific email template, and providing the target to receive the email.
Designating Target Recipients
IDHub includes a “Send Notification” Operation Node, which requests the appropriate template, and the individuals or groups that will receive the notification.
Workflow Forms
Applications frequently require proprietary or unique information as part of the application onboarding process like:
- RSA Tokens
- Device Type: Android or iOS Device
- Date Requests
- Unique IDs
- Personal Information
- Clearance Levels
- Social Media Usernames
Custom Forms are created and stored separately from workflows, and can be added to the request, as part of the approval process.
While configuring a Task Node, you can require that the approver fills out the form before completing any action.
Learn more..
IDHub Workflow Extras
