An approval workflow orchestrates a decision: who approves what, in which order, with which deadlines. Well-designed it speeds up operations; poorly designed it blocks them. Illizeo offers a visual editor to model any flow.
Step-by-step #
-
Pick the business object #
Leave, expense, contract, raise, hire, purchase. Each object has its property set available.
-
Define the trigger #
Manual (user submits) or automatic (on threshold crossed, on event).
-
Build the steps #
Drag & drop: step 1 direct manager, step 2 HR if > X days, step 3 leadership if > €Y.
-
Configure rules #
Auto-approval, escalation, notifications, parallel vs sequential.
-
Test #
The simulator plays 3 cases (standard, edge, exceptional) and lists triggered notifications.
Common workflow patterns #
| Pattern | Usage |
|---|---|
| Linear | Manager → HR → Leadership |
| Parallel | HR + Legal simultaneously |
| Conditional | Leadership if > €5,000, else manager only |
| Auto-approval | If policy met and seniority OK |
| Time cascade | Manager (24h) → N+2 if no response |
FAQ #
How many steps?
Ideal: 1-3 steps. Beyond, lead time explodes and so does frustration.
What if an approver rejects?
Workflow stops, requester notified with reason. Can resubmit.
Workflow versioned?
Yes, each change creates a new version. Running flows keep the previous one to stay valid.
Can I trigger an API action?
Yes, webhook step: creates a Jira ticket, sends Slack, updates a CRM.
