Process Hub · Fields, validation and calculations
Configure fields, questions and record layout
Choose field types, stable keys, required values and a layout people can complete.
On this page
Before you start
- Create a saved process draft. Have sample answers ready; know which values will drive assignment, lookups, calculations and integrations.
Useful choices
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Choice | Use a controlled list for consistent categories; decide single or multiple selection. |
| Lookup | Store a stable source key while showing a friendly label. Prepare the lookup first. |
| Record reference | Choose an existing related record when the relationship matters. |
| Attachment | Capture files/evidence with the configured attachment capability. |
| Calculation | Derive a value using supported expressions; validate the source fields. |
| Process number | Show the generated record identifier; users do not type or submit an answer for it. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open the draft in Builder. For Forms choose Fields & questions; for other types open the corresponding header, line, register or route field area.
- Add one field for each business value. Give it a clear label and a stable key. Use Text for references that may contain letters or leading zeroes, Number for quantities and Date or DateTime according to the precision required.
- Choose a User field when the value must identify a profile user. For assignment from a field, make it single-select. A typed name in a Text field cannot resolve an assignee.

Use the outline to select a section, the canvas to arrange questions, and Question settings to configure the selected field. - Set Required, defaults and global visibility/read-only behaviour deliberately. Keep generated process numbers display-only. Explain the expected unit or answer in the label/instructions.
- Group related questions into pages or sections. In a repeated section, decide whether people may add, delete, duplicate and reorder rows. Choose the column layout and preview the narrower stacked layout.
- Save and preview a complete record plus an incomplete one. Check keyboard order, labels, empty options and long values. Publish and deploy the structure before using these fields in automation.
Example: a care intake form
Add customer_reference (Text), issue_type (Choice), description (Long text), received_on (Date), reviewer (single-select User) and evidence (Attachment). Require the first three at intake; make resolution evidence a later-stage requirement. Use the same keys in the lifecycle and workflow examples.
What you should see
People see a readable record layout with correctly typed values, predictable validation and stable references for later configuration.
If something goes wrong
A required field cannot be edited
Check global read-only/hidden settings, calculations/provider protection and the current lifecycle policy. A stage cannot make a protected field writable.
A renamed label breaks a formula or mapping
Labels are presentation. Check that the stable field key and source column still exist; update dependencies when changing structure.