A process is a workflow template made of several process steps that moves a case (and optionally scopes and engagements) from start to completion. Open Case Management Setup → Processes.
Process
|
Field |
Description |
|---|---|
|
No. |
Unique process number. |
|
Description |
Descriptive name, e.g. "Assessment Process", "Mediation Process". |
Process step
|
Field |
Description |
|---|---|
|
Step |
Step number. |
|
Description |
Step label, e.g. "Registration", "Delivery", "Completion". |
|
Previous Step / Next Step |
Previous or next step (0 = none). |
|
Start |
Marks the start step (the initial step of new cases). |
|
End |
Marks a terminal step. |
|
Triggers Codeunit Id |
Optional: codeunit run when the step is entered (extension point for tenant-specific automation). |
|
Milestone Amount |
Amount billed on reaching this step in milestone billing. |
|
Milestone Is Percentage |
The milestone amount is a percentage of the contract amount rather than an absolute value. |
|
Require All Activities Approved |
Gate: the case can only leave this step once all its activities are approved. |
How processes work
-
Step advancement – Users with the "Proceed in Process" capability advance the case to the next step. Before the change, mandatory attributes and – if configured – the approval gate are checked.
-
Integration events – Each step change raises events (before and after), to which tenant-specific extensions can attach (e.g. send email, create activity, validate conditions).
-
Per-step attribute permissions – Attribute visibility, editability, and required status can be set per process step (see Attributes in Ventoo Case Management).
-
Milestone billing – If the current step carries a milestone amount, milestone profiles bill that amount once the step is reached.
Process assignment
The process applied to a case is determined in this order: scope schema → scope → default process from general settings. The process and current step are stored on the case.