Toggle (yes/no)
A yes/no choice rendered as a two-button segmented control — deliberately not a checkbox, because it starts with neither option selected. A required toggle therefore forces an explicit choice; a checkbox’s unchecked state would silently pass for “no”.
Once pressed there is no way back to “unset” (like Radio).
Configuration
Section titled “Configuration”| Option | Default | Notes |
|---|---|---|
| “Yes” label | Yes |
Any non-empty text — Agree, Opt in, … |
| “No” label | No |
Labels affect display only, never the stored value |
"typeConfig": { "trueLabel": "Yes", "falseLabel": "No" }Stored answer
Section titled “Stored answer”A boolean:
{ "newsletter": false }The distinction that matters: an untouched toggle stores nothing —
absence of the key — while an explicit “No” stores false. false is a
real answer; a required toggle answered “No” is answered.
Rule operators
Section titled “Rule operators”equals, not equals against true/false (the rule builder shows your
custom labels but stores the booleans). Because unanswered never matches,
equals false fires only on an explicit “No” — an untouched toggle
doesn’t trigger it. Design your logic accordingly: “show when they decline”
means after they decline, not until they accept.