›Why this process needs a structured workflow
Employees wait 5+ days for standard requests — laptop, access, software — because each one is manually handled by email between IT, HR and procurement. The delay blocks onboarding, frustrates new hires and erodes productivity.
Utilyx models the service catalog as an executable workflow: each catalog item has its own approval chain, provisioning connector and notification path, so a standard request is fulfilled in minutes instead of days.
›The automated catalog workflow
The workflow is structured as a decision tree with 3 branches (Standard, Pre-approved, Custom) and 7 steps end-to-end. Each step is executed by a named actor (Requestor, Routing engine, Approver, call-connector, email service, Fulfillment team, IT Manager) and every action is timestamped.
- Step 1 (Start — Requestor): the employee browses the service catalog portal and selects an item. Mandatory fields: item_id (catalog ref), quantity, business_justification, requested_for (self or colleague), delivery_date. Conditional sections appear based on item category (hardware → shipping_address; software → license_type: single/concurrent; access → target_system, permission_level).
- Step 2 (Routing): three branches split the tree — Branch A (Standard item, cost < threshold): auto-approved, jumps to provisioning; Branch B (Pre-approved by manager delegation): manager email approval via email module, 24h SLA; Branch C (Custom / cost > threshold): two-level approval (manager + IT budget owner), RFC created if infrastructure impact.
- Step 3A (call-connector): for hardware, the call-connector triggers the procurement API (SCIM or vendor endpoint) to create a purchase order; for software, it calls the license manager API to allocate a seat; for access, it calls the IAM API (Okta/Entra) to grant the permission set.
- Step 4A (email): the requestor receives an email confirmation with ETA and a tracking link; the line manager is cc'd for visibility.
- Step 5A (Fulfillment): the IT fulfillment team receives the provisioned item for final QA (asset tag, license key verification) and marks the task complete.
- Step 6A (Closure): the requestor confirms receipt, the asset is registered in the CMDB via sql-query (INSERT into ci_assets), and a satisfaction survey is sent.
›Concrete benefits
Teams that adopt Utilyx report request fulfillment time cut from 5 days to under 4 hours for standard items, 70% of catalog requests auto-provisioned without human touch via call-connector, and zero shadow-IT purchases because the catalog covers every approved item.
The visual catalog designer lets a service owner publish a new item in 15 minutes, the approval delegation removes the manager bottleneck, and the no-code connector framework integrates any IAM, license or procurement API — no developer required.
›The workflow in real time
Every node is executable, every branch is testable. Visualize the actual flow of your data while you design.
Frequently asked questions
Can the catalog auto-provision access and software?
Yes. The call-connector module calls your IAM, license manager or procurement API to provision the approved item automatically — no manual intervention for standard requests.
How are approvals handled for non-standard requests?
The routing engine splits the tree by cost and category: standard items auto-approve, pre-approved items go to a delegated manager, and custom items require two-level approval plus an RFC if infrastructure is impacted.
Ready to automate your processes?
Utilyx lets you design, automate and orchestrate your workflows visually — with an AI copilot, OCR, PDF generation and legal archiving. Start in minutes, not weeks.
