Validation messages

A form rejects bad input before saving. The rules come from the table field's type, required flag, and any custom rules — you don't configure them on the form.

But you do control how clear the error feels.

Where errors come from

Three sources, in order:

1. Type — Email rejects values that aren't email-shaped. Date rejects "next Monday".
2. Required — refuses blank when the field is required.
3. Custom rules — your min/max/pattern/etc. configured on the table.

Each rule has its own message — written when you defined the rule on the table.

Error message tips

• Be specific. "This field is required" is fine; "Pick a leave type before saving" is better.
• Tell the user what to do, not what went wrong.
• Don't repeat the field label. The error appears next to it; the label is right there.

Edit messages on the table field, not on the form. The form just displays them.

Where errors show

Errors appear under the input that caused them, in red. If the user clicks Save with multiple errors, the form scrolls to the first one and focuses it.

Successful save

After a successful save, the form redirects to either:

• The detail (Show) page of the just-saved record (default).
• The list page.
• A custom URL — set on the form's Settings tab.

Choose the destination that matches what the user is most likely to do next.

Where to next

• Common mistakes.