When to choose this
Exact behavior
- Numbers only.
- Blank source or comparison → never matches.
- Float comparison (
<=);"100"vs100works. - Pick another field in Value for dynamic ceilings.
Which field types
Blank / unanswered answers
Never matches. Add Is empty for skipped-field paths.Configure in Studio
1
Open a rule
Logic → Rules, or Branch / Add condition on a field.
2
Select a number field
Currency, integer, rating, calculated total, etc.
3
Choose Less than or equal
Number family only.
4
Enter the cap
e.g.
500, 3.5, or pick Max allowed in Value.5
Add Then actions
Show blocks warnings, Hide submit when over limit (pair with inverse rule).
6
Test on Fill
At cap, above cap, below cap, blank.
Worked examples
Free tier limit
When Team size less than or equalExactly 5 seats qualifies.5→ Then Show blocksFree plan eligible
Fail band
When Score less than or equalScore 49 matches; 50 does not.49→ Then Jump to pageRetake
Within approved budget
When Estimated cost less than or equal (pick) Budget cap → Then enable submit path
Inventory warning
When Requested qty less than or equal 0 → Then Hide submit
Combine with validation messaging on canvas.
Test on fill
1
Above cap
Rule off (for ≤ cap rules).
2
Exactly at cap
Rule on.
3
Below cap
Rule on.
4
Empty field
Rule off.
Common mistakes
- Expecting ≤ on dates — not in Studio for date family.
- Using Less than when boundary should pass — use ≤.
- Single rule for both over-cap and under-cap — split into two rules or use separate Rules rows.
Troubleshooting
Operator missing
Operator missing
Field not numeric — use integer/currency or calculated number.
Cap reference empty
Cap reference empty
Referenced field blank until filled.
Need inclusive date cutoff
Need inclusive date cutoff
Use Before with (deadline + 1 day) or numeric days-until field.
Floating point surprises
Floating point surprises
Currency with many decimals — test realistic inputs on Fill.