Workflow

The Workflow object defines a configurable business process, a sequence of steps, approvals, notifications and provisioning actions, that IdentityIQ executes automatically. Workflows orchestrate the multi-step processes behind access requests, lifecycle events and custom automation.

• Steps: units of work, which can call rules, set variables, or invoke provisioning.
• Approvals: steps that generate work items and wait for a human decision.
• Transitions: conditional paths between steps, allowing branching logic.
• Variables: data carried through the process.

Workflows are launched by events, an access request, a lifecycle event, or a custom trigger, and run to completion, pausing at approvals and resuming when they are answered. IdentityIQ ships standard workflows (for example LCM provisioning) that you customise rather than building from scratch.

Steps can invoke BeanShell rules for custom logic, computing an approver, transforming data, deciding a branch. This is where much customisation lives, so the same discipline applies: keep the logic small, tested and documented.

Favour clarity over cleverness. Deeply branched, heavily-scripted workflows become impossible to reason about and debug. Use standard patterns, keep custom logic in well-named rules, and always test in a lower environment before production, a stuck or looping workflow can hold up real access.

• Over-complex workflows that no one can safely change.
• Untested changes deployed straight to production.
• No escalation on approval steps, so processes stall on inaction.