Process Hub · Build by process type
Build a Forms process
Create a simple form or survey with pages, validation and a usable submission flow.
On this page
Before you start
- Have Edit solutions access, an approved runtime connection and a small set of sample answers. Decide whether this is a simple form or a survey questionnaire.
Useful first version
Start with customer reference, issue type, description and evidence. Add lifecycle stages only after the basic capture flow is working. A survey can use additional pages and branching, but every path still needs to be tested.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open Builder → New process. Choose Forms, set a clear Name and supported subtype/placement, and create the draft.
- In Process setup configure the process identity, numbering and intended capabilities. Keep the first version focused on one business record.
- Open Fields & questions. Add fields with stable keys, clear labels and suitable types. Organise pages/sections and choose one, two or three columns where available.

Use the outline to select a section, the canvas to arrange questions, and Question settings to configure the selected field. - Set required values, defaults and conditional behaviour. Add attachments only where evidence is needed; use a single-select User field for any field-based assignment.
- Choose record views and optional features. Configure Business lifecycle when the submitted record needs stages and handoffs. If using manual work items assigned to the creator, review when the first draft save starts the task/deadline.
- Preview the whole form, including branches, empty required answers and the narrow stacked layout. Save the draft, validate, publish and deploy.

Save draft keeps unfinished work. Complete required answers before starting final submission. - Grant member access and test Add New → Save draft → reopen → Submit. Then separately configure/release approvals, workflow links or notification policies as required.
Try a complete business example
What you should see
A member can capture, save and submit the intended form and understand what work happens next.
If something goes wrong
Add New created no persisted record yet
The initial form is unsaved. A record is created on successful Save draft or submission.
A self-assigned draft deadline keeps counting while you edit
Where configured, the first draft save starts the manual work item deadline. Saving again does not restart it.
A generated number cannot be required or edited
Process number is display-only generated identity; it is not a normal answer field.