The rules you will reach for most
Most validation comes down to a handful of checks. Forms365 Workspace covers these visually, so you set them without writing code:
| What you want | How | Example |
|---|---|---|
| A real email address | A pattern (regex) on the field | name@example.com passes, "n/a" does not |
| A phone of the right length | A length or pattern rule | Reject a mistyped six-digit number |
| A quantity within range | Min and max on a number | Between 1 and 500 |
| A sensible date | Min and max on a date | Not before today for a booking |
| End date after start date | Cross-field validation | Block a return that is before the departure |
Say why, not just no
A rule that only turns a field red is frustrating. You can set a custom message on each rule so the person is told what is wrong and what good looks like, for example asking for a mobile number in the format you expect rather than a blank rejection. Clear messages are the difference between a form people finish and one they abandon.
Checks across more than one field
Some rules only make sense when two fields are read together. An end date should not fall before a start date. A total should not exceed a stated budget. Cross-field validation compares the fields and blocks the submission when they contradict, which is the same shared rules engine behind conditional logic and calculations.
When you need something unusual
For the rare check the visual rules do not cover, there is a scripting layer. Workspace has a code editor with a JavaScript API for reading and writing the form, so an unusual requirement does not force you back to a spreadsheet. Most forms never need it.
Keep bad data out of your list.
14-day free trial. No credit card.