When to choose this
Exact behavior
- Text only; non-blank source required.
- Non-empty expected suffix required.
- Case-insensitive suffix negation.
- Blank source → never matches.
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
Select text field
3
Choose Does not end with
4
Enter excluded suffix
e.g.
.tmp, @gmail.com5
Add Then actions
6
Test on Fill
Answered non-match vs blank vs matching suffix.
Worked examples
Require work email (not consumer)
When Email does not end withAdd separate validation if blank should fail — Does not end with ignores blank.@gmail.com→ Then Show blocksCompany verification
Block temporary extension
When Filename does not end with .tmp → Then allow submit path
Non-EU product codes
When SKU does not end with-EU→ Then Hide blocksEU compliance
Partner exclusion
When Referral code does not end with -INTERNAL → Then public rewards flow
Test on fill
1
Matching suffix
Rule off.
2
Other suffix or none
Rule on when answered.
3
Blank
Rule off.
Common mistakes
- Using for “not a gmail OR blank” without Is empty clause.
- Suffix typos (
.PDFvs.pdf) — case-insensitive but extension must match characters.
Troubleshooting
Consumer email still passes
Consumer email still passes
Subdomain emails may not end with
@gmail.com — add Contains clauses or validation message.Blank skips rule
Blank skips rule
Add Is empty → Hide or Require as needed.
Multiple banned suffixes
Multiple banned suffixes
Any group with multiple clauses or custom validation copy on canvas.