Field Array
A Field Array is a repeatable section of a form: a group of fields that the user can add multiple times. Each entry (row) contains the same set of sub-fields. Use it whenever a form needs a list of similar items — for example, expense line items, multiple dependents, previous employers, or several addresses.
How it works
A Field Array holds a set of nested fields. At fill time, the user sees one row of those fields and can add more rows as needed; each row captures its own values.
- The field starts with one blank row to fill in.
- The user can add and remove rows; the last remaining row can't be deleted (so at least one entry is always present).
- Mark the Field Array required if the user must provide at least one entry.
Inner (nested) fields
The fields inside a Field Array are ordinary form components — text inputs, numbers, dropdowns, dates, and so on — each configured with its own label, validation, and other field properties. For example, an "Expenses" Field Array might contain Category (dropdown), Amount (number), and Date nested fields, and the user adds one row per expense.
NestingA Field Array contains regular fields — it's a single level of grouping. You don't place a Field Array inside another Field Array.
Pre-filling
A Field Array can be pre-filled so it opens with rows already populated (for example, seeding line items from earlier data or an integration). The nested values are available in the Data Center as part of the array, so downstream steps can read what was entered in each row.
Where it's configured
- Build it in the Form builder. Open the form, add a Field Array component, then add the nested fields inside it. Configure each nested field's properties just like a top-level field.
- Control visibility/editability per node (App Permissions). Each nested sub-field can be set Editable, Read only, or Hidden per workflow step under App Permissions — see Field Array permissions.
