When to choose this
Exact behavior
- Both actual and expected must be non-empty strings.
- Case-insensitive suffix via
mb_strtolower/str_ends_with. - Null, non-string, or empty source → no match.
- Empty suffix in rule → fail-closed.
Which field types
Blank / unanswered answers
Does not match.Configure in Studio
1
Open a rule
Logic → Rules, or Branch / Add condition on a field.
2
Pick text field
Email, filename, account number, etc.
3
Choose Ends with
Text operators only.
4
Enter suffix
e.g.
.pdf, @partner.com, -EU5
Add Then actions
6
Test suffix placement on Fill
Worked examples
Corporate email domain
When Work email ends with@acme.com→ Then Show blocksEmployee ID
[email protected] matches; @acme.com.evil.com does not.
PDF upload name (text field)
When Filename ends withFor actual file blocks, use Is not empty on the file field.PDF disclaimer
Regional SKU
When Product code ends with-EU→ Then Show blocksGDPR notice
Student email
When Email ends with.edu→ Then Show blocksStudent discount
Test on fill
1
Suffix at end
Rule on.
2
Suffix in middle only
Rule off.
3
Case variants
Match regardless of case.
4
Empty
Rule off.
Common mistakes
- Using Contains @acme.com when domain must be true suffix — Ends with is stricter.
- Applying to file upload blocks — use presence empty/not empty; filename may be separate text field.
- Empty suffix in rule.
Troubleshooting
Domain false positives
Domain false positives
Use Ends with not Contains to avoid
@acme.com.attacker.net.Trailing spaces
Trailing spaces
Spaces before suffix break match — test realistic typing on Fill.
International characters
International characters
Multibyte suffixes supported via
mb_strtolower.Negated suffix
Negated suffix
Use Does not end with.