Skip to content
ImplementedFor eCRF designers, data managers, validation staff

Forms reference

Last updated Oct 21, 2026

What this is, and who it is for

Everything the form builder can put on a form, and what each setting does downstream, used to be one long page here. It is now a section of its own, The form builder, with a page for each part, so that every option is described where it is used. This page tells you where each thing from the old reference now lives.

Where to find it

You are looking forPage
Field types: text, number, date, choice, table and the rest, and what each storesField types
Layout fields: section, heading, description, instruction, separatorSections, headings and layout
Table columns, rows, kinds, N/ATables and repeating groups
Validation: required, limits, patterns, dates, and what happens when one failsValidation, edit checks and their severities
Normal range and unitsUnits and normal ranges
Conditional visibility, value assignment, auto-populateConditional logic
Formula and calculated fieldsFormulas and calculations
Clinical settings: queries, source verification, CDISC annotationField properties (the CDMS tab)
The form's own settings: code, domain tag, category, event formVersions, reopening and publishing and Binding a form to visits
Deprecating a fieldVersions, reopening and publishing
Where each piece of logic runs (browser or server)Formulas and calculations, Conditional logic
Cross-form rulesRules reference

What you can do

Read the page for the part you are working on. For a first form, follow Build a form: a walkthrough.

Every option

Every option is on the linked pages. The two corrections to what this page used to say, because people rely on them:

  • A value outside a hard limit is not simply "not stored". What a failing check does is the field's choice: Query (saved and a query opened, the default), Block (the save is refused) or Warn (a message only). See Validation, edit checks and their severities.
  • The "Site can resolve", "Monitor can resolve" and "Reason codes" settings do not exist in the builder, and the "Auto-query" switches on the CDMS tab are fixed on. The CDISC domain is a grouping label; only EX and CM also make a form a dispensing form for the Pharmacy role, and AE, AE (serious) and CM make it an event form.

What the system records

See each linked page. In short, every save of a form is a revision of the version's draft design and an audit entry, and a field's deprecation records a reason.

What you cannot do, and why

See Overview and Versions, reopening and publishing.

Compliance Q&A

No Q&A applies on an index. The pages above carry them.

Rules reference · Design forms · Not built yet