Forms
AvailableCollect structured human input on a User Task.
Forms let a workflow collect structured human input for use cases like approvals, employee onboarding, customer verification, order review, incident resolution and general data collection.
Example: a manager approval form
Order ID [ O1001 ]
Customer [ John Smith ]
Amount [ 125,000 ]
Decision [ Approve ▼ ]
Comments [ ]
[ Submit ]Form workflow
User Task
Linked Form
User enters data
Validation
Task completion
Process variables updated
Forms should be connected to process variables so the data a user enters becomes part of the workflow context that downstream tasks and gateways can read.
The form designer
| Capability | Detail |
|---|---|
| Components | 22 component types on a 12-column grid, including groups and repeating lists |
| Validation | Required, length, range, pattern, email / phone / URL and custom FEEL rules |
| Conditional fields | Hide a field or make it read-only or disabled with a FEEL expression |
| Lifecycle | Draft → Validated → Published → Deployed → Retired |
| Versions | Change history, component diff and restore as a new draft |
| Translations | Labels per language, with fallback to the original label |
| Playground | Run a form against sample data before publishing |
A running task keeps the form version it first opened with. The table component and file upload cannot yet be submitted when completing a task.