Business Processes
End-to-end workflows your organisation depends on
What are Business Processes?
Business processes represent the high-level workflows that deliver value to your organisation — things like "Order Fulfilment", "Customer Onboarding", "Payroll Processing", or "Incident Response". Each process documents what the workflow does, which departments own it, what infrastructure supports it, and how much it is worth financially.
Financial Value
Each business process can have a financial value representing the monetary worth of the process. This figure is central to the risk report: when an issue is linked to a control that protects a business process, the process's financial value is used to calculate risk exposure.
Setting accurate financial values is important for meaningful risk quantification. The value should reflect the revenue, cost of disruption, or strategic importance of the process.
Connections to Other Areas
- Entities — a process can be linked to multiple entities, representing which departments or teams own or participate in the process.
- Configuration items — linked to the assets that support the process, mapping workflows to infrastructure.
- Applications — linked to the applications that enable the process.
- Controls — controls can be linked to business processes, connecting compliance measures to the workflows they protect.
- Tickets — tickets can reference affected business processes.
Process Modeler
Each business process has a built-in visual workflow designer called the Process Modeler. The modeler lets you define the process as a series of steps with dependencies:
- Steps — each step has a name and can be linked to specific configuration items.
- Dependencies — steps can declare which other steps must complete before they begin (step A before step B), creating a directed workflow graph.
Version Management
The Process Modeler supports version control for your workflow definitions:
- Draft — when you edit steps in the modeler, changes are saved as a draft version. Only one draft can exist at a time.
- Published — publishing a draft makes it the active version. The previously published version is automatically archived.
- Archived — past published versions are preserved as read-only snapshots.
- Restore — you can restore any archived version, which creates a new draft from that version's snapshot. This lets you roll back to a previous workflow design.
Each version stores a complete snapshot of all steps and their dependencies, so restoring a version faithfully recreates the workflow as it was at that point in time.