#Forms
A form is what a person sees when they start a process or work on a user task, and what they enter becomes data the process can use.
#Where a form is used
flowchart LR F[Form] --> S["Start event<br/>start form"] F --> U["User task<br/>task form"] C["Process data so far"] -- "Form data input" --> U U -- "entered values" --> N["Next steps"] S -- "entered values" --> N
- A start form is shown when somebody starts the process from a catalog.
- A task form is shown when somebody opens a user task in their task list.
Forms belong to one process and are listed on its Forms tab, together with the user tasks that use them. Only executable processes have forms. A running task shows the form as it was when its process was deployed.
#Build a form
Forms are built in a drag-and-drop form builder: text fields and areas, numbers, dates and file uploads; checkboxes, radio groups, selects and tag lists; groups and dynamic lists; and display elements such as text, images, HTML, document previews, tables and spacers. See Build a form and Form field types.
#Fill a form with process data
A task form can show what the process already knows — the customer a previous step fetched, the amount a person entered at the start. The user task's Form data input decides which value goes into which field, using expressions. See Fill a form with process data.
#Show, hide and lock fields
Per field, a user task can set:
- a Display control condition — the field is hidden while the condition is
false; - an Input control condition — the field is shown but cannot be changed while the condition is true;
- Option data for a selection, taken from the process data instead of a fixed list.