When to choose this
Exact behavior
- Choice multi-select fields.
- Normalizes to sorted unique string sets.
- Requires non-blank actual answer.
- Matches when normalized sets differ (extra option, missing option, or completely different).
- Non-empty expected set required.
Which field types
Blank / unanswered answers
Never matches.Configure in Studio
1
Open a rule
Logic → Rules, or Branch / Add condition on a field.
2
Pick multi-select field
3
Choose Not equals set
4
Define the excluded exact set
Chips for the combination that should not trigger this branch’s “different from” logic.
5
Add Then actions
6
Test exact excluded set vs others on Fill
Worked examples
Not the free-only bundle
When Features not equals setSelecting only Community support does not match this rule (they’re exactly that set); any other answered combo matches.Community support→ Then Show blocksPaid onboarding
Avoid risky pair
When Permissions not equals set Delete, Admin → Then standard approval flow
Exact dangerous pair excluded from match; blank still fails.
Upsell when not bare minimum
When Add-ons not equals setIf “None” is a stored option representing empty bundle semantics, test carefully on Fill.None→ Then Show blocksImplementation offer
Campaign mismatch
When Tags not equals set Staff, Internal → Then external thank-you page
Test on fill
1
Select exactly the excluded set
Rule off.
2
Any other non-empty selection
Rule on.
3
Blank
Rule off.
Common mistakes
- Expecting “not exactly ” to fire on blank — it will not.
- Using when you mean “does not include A” — use Does not contain.
- Confusing with Is none of — different list semantics.
Troubleshooting
Rule never fires
Rule never fires
Source may be blank or accidentally always the excluded set.
Rule always fires
Rule always fires
Any answered combo differs from set — may be too broad; narrow with Equals set on positive path instead.
Single option set
Single option set
Works as one-element exact set comparison.
Need blank path
Need blank path
Add Is empty sibling rule with Any match.