new

Enterprise

Collaboration & Security

Record Page: Conditional Required Fields

Whats New page -  Manage Members - Access level overview (1)
The Record Page now supports Conditional Required Fields. Solution admins define per-field rules on the Display Logic tab that make a field mandatory when other field values dictate it, and the rule fires immediately as users edit the record — no save-time surprise. ITSM incident forms requiring a resolution note only when Status equals Resolved, GRC attestation records requiring an evidence link only when Result equals Pass, and PMO project intakes requiring an executive sponsor only when Priority equals Critical all get conditional validation at the right moment.
Key Highlights
  • New Required Fields Section on Display Logic: A dedicated Required Fields area on the Display Logic tab lets solution admins define rules that make a field required when another field's value matches a condition. Same UI pattern as the existing Sections, Tabs, and Fields rule types.
  • Immediate Enforcement, Not Just On Save: Rules become effective as soon as the triggering field value changes on an open record, before the record is saved. Users see the required-state indicator update in real time and can complete the record before submission.
  • Visibility Wins: If a field is hidden by a Display Logic rule (whether directly or because its tab or section is hidden), the conditional-required rule doesn't fire against it. Hidden fields are never treated as required, no matter what the require rule says.
  • One Rule Per Field: Every field can have at most one conditional-required rule. System fields (Record ID, First Created, Followed By, and so on), calculated fields (Formula, Lookup, Rollup, Count, Autogenerated Title), and fields already marked as required in the field settings are excluded from the rule builder.
  • Same Tab-Level Validation UX: When a save action generates multiple required-field errors, the Record Page shows the count of empty required fields per tab, exactly matching the existing required-field validation model. No new failure UI to learn.
How It Works
  • Open a table's field settings and go to the Display Logic tab. The new Required Fields section sits alongside the existing Sections, Tabs, and Fields rule categories.
  • Click Add Rule, pick the field that should become required, define the condition against another field's value (Status equals Resolved, Priority equals Critical, Result equals Pass), and save the rule.
  • The rule-indicator icon appears on the field in the Fields tab so admins can see at a glance which fields have a conditional-required rule attached.
  • On the Record Page, as users edit a record and change the triggering field's value, the conditionally-required field shifts to a required state immediately. If they try to save without providing a value, validation errors surface per tab.
  • Pair conditional-required rules with existing conditional-display rules for the full picture: hide a field until it's relevant, then require it once it is.
Available on Enterprise and Signature plans.