Field options

Every field you add to a form has a type (what shape of data it captures), an optional parent (for grouping), and a list of optional validators. Some types add their own configuration block on top — signatures, scans, and prompts all have extra editors that appear when you pick those types.

Populating a new field

1. Open Captis Admin → the form you want to edit → Field Definitions.
2. Click + in the left list. A new draft field appears with a generated UID and a Field ID you can rename.
3. Fill in Field ID (human-readable key used in schemas and PDF data binding) and Label (what the user sees).
4. Pick a Type from the dropdown (see the table below).
5. Optionally pick a Parent field (only repeating groups and groups can be parents).
6. Add any Validation rules and tenant-specific flags (Contains PII, Inheritable across forms, etc.).
7. Save. The field is now available to assign in the Wizard and to calibrate on the PDF.

Field types

Each type maps to a JSON-schema shape and a renderer in the form-fill app + PDF generator.

Prompt answer kinds

When you set Type = prompt, an additional configuration block appears. Pick an Answer kind:

Validators

Validators run at form-fill time and on submit. Add as many as you like; they all have to pass. Date format validators check the input shape; date semantic validators check the resulting date.

Date formats

Date semantics

Pair these with a format validator above.

Phone

Height

Numbers & text length

Identity, address, email, regex

Type-specific configuration

Signature fields

• Bound to field — the data field this signature is attached to. Drives whose signature it is.
• Reset on edit — when true (default), edits to watched fields invalidate the signature on the next edit-mode submit.
• Watched fields — explicit list of fields whose edits invalidate this signature. Null = all data fields except other signatures and the paired date.
• Cascades to — other signature ids that get invalidated together with this one.
• Date field — a date field paired with the signature; auto-populated on sign.

Scan fields

• Source — camera, photos, or files.
• Subtype — document (multi-page document scanner), id (single shot), or card (CR80-aspect card).
• Output format — png, jpg, or pdf.
• Scan card type (optional) — references a tenant-defined card type that runs server-side OCR and populates sibling fields from the extracted text.

Prompt fields

• Title + body — header + descriptive paragraph shown when the card is expanded.
• Answer kind — one of the five kinds in the table above.
• Per-choice branching content — each yes/no choice and each pick-one/pick-many option can carry its own title + body that replace the prompt’s parent title/body after selection.
• Per-choice populate targets — each choice can mirror its answer into one or more sibling fields, choosing per-target what to write: the raw answer, a literal constant (bool / num / string, type-inferred from input), or null (clears the target).

Other field flags

• Contains PII — activates screen protection (FLAG_SECURE on Android, blank-on-resign overlay on iOS) when any visible field in the active form has this set.
• Inheritable across forms — on submit, the field’s value is harvested into the linked entity’s attributes and pre-fills on future forms about the same entity.
• Required-field policy override — rare per-field override that’s strict enough to block submit even when the form-level policy allows warn-and-submit.
• Warning text — override label written into the printed missing-fields warning when the field’s label is ambiguous in that context.
• iOS privacy category — override the heuristic Privacy Manifest category for this field.