The Flows page lists the document flows available in the current company. A flow is a reusable definition; it describes what documents an application may need and how the application should be checked.
Route: /flows/
Example:
https://default-company.localhost/flows/
Header actions¶
- All Runs opens
/flows/runs/and shows application runs from every flow. - New Flow opens the form for creating an empty flow.
Flow cards¶
Flows are ordered by name. Each card shows:
| Item | Meaning |
|---|---|
| Name | The flow's readable name. |
| Description | A short explanation, limited on the card to keep the list compact. |
| Active / Inactive | The flow's configuration marker. Inactive flows remain visible. |
| Steps | The number of document-requirement steps configured in the flow. |
| Cross-checks | The number of cross-document checks configured in the flow. |
| Runs | The number of application runs created from the flow. |
Select anywhere on a card to open its Creating and Editing a Flow page.
Create a flow¶
Select New Flow and enter:
| Field | Meaning |
|---|---|
| Name | Required. The title displayed in the list and on runs. |
| Description | Optional. A plain explanation of the flow's purpose. |
| Active | Selected by default. Marks whether the flow is intended to be in use. |
Select Create. A valid flow is saved and opened immediately in the flow builder. Validation errors appear as notifications and leave you on the list.
Note
In the current implementation, Active is a label rather than an access control: inactive flows still appear in the list and their existing detail URLs can still create runs.
Empty state¶
When no flow exists, the page explains that you can create one. Administrators and developers may also import the supplied Identità flow seed through the management command shown on the page.