Conditional Field Visibility
Conditional field visibility lets you show or hide fields in a section based on the current value of another field in the same section. Use it to keep forms uncluttered — only ask contributors to fill in fields that are relevant given their earlier answers.
How it works
Each field in a section can have one or more visibility rules. A visibility rule says:
"Show this field only when [condition field] [operator] [value]."
If the condition is not met, the field is hidden in form mode and grid mode. Hidden fields are not required (even if marked required) — contributors cannot fill them in because they are not shown.
Common patterns
| Pattern | Example |
|---|---|
| Sub-question shown on Yes | "Is there a delay?" → Yes → show "Delay cause" and "Delay days" fields. |
| Detail fields shown on RAG | RAG = Red → show "Corrective action" rich text field. |
| Conditional date field | "Has the milestone been achieved?" → Yes → show "Achievement date" field. |
| Type-specific fields | "Risk category" = Commercial → show "Contract clause" field. |
| Escalation detail | "Escalation required?" = True → show "Escalation approver" and "Escalation date". |
Configuring visibility rules
- Open the blueprint in the Blueprint Designer.
- Open the section containing the fields.
- Click a field to open its properties.
- Scroll to Visibility (below the field type settings).
- Click + Add visibility rule.
- Choose:
- Condition field — any other field in the same section.
- Operator — see table below.
- Value — the trigger value.
- Set Default visibility — whether the field is shown or hidden when no condition is met.
- Save the blueprint.
Operators
| Operator | Available for |
|---|---|
| equals | Text, Select, Toggle, RAG, Number, Rating |
| not equals | Text, Select, Toggle, RAG, Number, Rating |
| contains | Text, Multi-select |
| does not contain | Text, Multi-select |
| is empty | All field types |
| is not empty | All field types |
| greater than | Number, Currency, Percent, Rating |
| less than | Number, Currency, Percent, Rating |
| is before | Date, Datetime |
| is after | Date, Datetime |
Multiple rules
When a field has multiple visibility rules, choose the combining logic:
| Logic | Behaviour |
|---|---|
| Any (OR) | Show the field if any rule condition is met. |
| All (AND) | Show the field only when all rule conditions are met simultaneously. |
Visibility in grid mode
In grid mode, conditional visibility works at the cell level — a cell in a column is editable only for rows where the visibility condition is met. Rows where the condition is not met show the cell as grey and read-only.
The column is always visible as a column header in grid mode — only the specific cells are locked where the condition is not met. This keeps the grid aligned and consistent.
Visibility vs required
If a field is required AND has a visibility rule:
- When hidden (condition not met) → the field is not required. The section can be marked complete without it.
- When visible (condition met) → the field is required and the section cannot be marked complete without it.
This means you can confidently make "Delay cause" required without it blocking completion for editions that have no delay.
Visibility in outputs
Hidden fields (condition not met) are excluded from output bindings. If you bind a report component to a field that is conditionally hidden, the cell will appear blank in the output for rows where the condition was not met.
Use Hide when empty on output components to collapse cells where the conditional field has no value.
Limitations
- Visibility rules can only reference fields in the same section — cross-section conditionals are not supported.
- Computed and lookup fields cannot be used as condition fields.
- Visibility rules do not affect export CSV/Excel of edition data — all fields (including hidden ones) are exported as columns.