Tip sets and validation hints

A tip set attaches small, persistent help to fields on a page. Create one with New content, then Field tips.

Defaults and per-tip settings

A tip set has defaults for the trigger icon, the focus behaviour and the hover behaviour. Each tip overrides them and sets:

Setting	Values
Kind	guidance or validation
Trigger	Icon, hover or focus, as offered by the editor
Icon position	after-label, inside-end, after-field
Anchor	The field, picked on the page

Guidance tips show help text. Validation tips check what the user typed and show a hint when it fails.

Validation rules

Rules: required, regex, length, date-not-future, date-within-days. A tip can carry extra rules combined with all or any.

Behaviour worth knowing:

• An empty value passes every rule except required.
• A broken regex passes everything at run time. The studio refuses to publish it.
• Field values are evaluated in the page and never stored or sent anywhere.

Worked example

Warn when a date of loss is in the future:

1. New content, Field tips. Name it "Loss date checks".
2. Add a tip, pick the Date of loss input.
3. Set kind to validation with the rule date-not-future. Write the message: "The loss date cannot be in the future."
4. Add a second tip on the Policy number with a regex rule ^[A-Z]{2}\d{8}$.
5. Preview on page, type a future date, and confirm the hint appears. Publish.

Gotchas

• Validation tips show a hint. Nothing in the schema makes them block the host form's submit.
• Guidance-only tip sets with validation-style extra rules raise the Checks warning extra-rules-on-guidance. A combine without rules raises combine-without-rules.
• A tip icon beside a full-width field is tucked inside the field's end edge so it stays on screen. If it covers text, use after-label.