Skip to main content

Conditional logic

Conditional logic makes the document smart: fields show up, become required or exclude each other depending on what the signer enters. The canonical example is the W-9-style tax form, where the chosen classification drives which fields must be filled.

It is edited visually (if / then rules) in the template editor, on each form field.

Available rules​

Conditional display​

A field appears or hides based on another field's value.

If the "LLC" radio button is selected → show the "LLC type" text field.

Conditional requirement​

A field becomes required when a condition is true.

If the "VAT exemption" checkbox is checked → the "Exemption reason" field becomes required.

Selection exclusivity​

In a radio button group, only one value can be selected. Changing the selection automatically hides the conditional fields tied to the previous value.

Mutually exclusive fields​

Two fields (or groups) exclude each other: filling one disables the other.

Fill in the SSN or the Tax ID/FEIN — never both.

AND / OR combinations​

Conditions combine:

If radio = "LLC" AND the "Foreign" checkbox is checked → show the "W-8" field.

Good practices​

  • Test every branch of the form in draft mode before activating the template — including going back (changing a radio selection must clear fields that became irrelevant).
  • Combine with type validation: a required conditional field should also validate its format.
  • Values entered in conditional fields can be written back to Salesforce via TrueSign Connect — remember to map both branches.