Validation Principle
tikento uses two-level validation:
- Client-side (blur) — validation when leaving the field. Instant feedback for the attendee.
- Server-side (backend) — repeated validation when the form is submitted. Guarantees data correctness.
The backend is the single source of truth. Even if client-side validation is bypassed, the server will reject incorrect data.
Built-in Rules by Field Type
Standard rules are provided for each of the 14 field types:
| Field Type | Built-in Validation |
|---|---|
| Email format (RFC 5322), regex check | |
| Phone | Phone format, international regex |
| Text | Minimum/maximum length |
| Number | Minimum/maximum value |
| Date | Valid date, range boundaries |
| URL | URL format |
| Dropdown | Value from allowed options |
| Radio | Value from allowed options |
| Checkbox | Required check (for consents) |
| File | File type and size |
Configuring Validation
Required Field
The "Required field" toggle in the field settings. When enabled, the attendee cannot submit the form without filling in this field.
Regex Pattern
For text fields, you can set a regular expression to validate the input format:
- Open the field settings in the form builder.
- Find the "Validation" section.
- In the "Regex pattern" field, enter the regular expression.
- In the "Error message" field, enter the text the attendee will see if the input doesn't match.
Examples:
- Tax ID (12 digits):
^\d{12}$ - Passport series and number:
^\d{4}\s?\d{6}$ - Letters only:
^[a-zA-Z\s-]+$
Minimum and Maximum
For number fields, set boundaries:
- min — minimum allowed value
- max — maximum allowed value
For text fields:
- minLength — minimum text length
- maxLength — maximum text length
Blur Validation
Validation triggers when the attendee leaves a field (loses focus). This provides instant feedback:
- The field is highlighted in red
- An error message appears below the field
- The attendee can immediately correct the input
When returning to the field and correcting the error, the highlighting and message disappear.
Localized Messages
All standard error messages are translated into supported languages (ru, en, es, ar, it, de, fr). The attendee sees the message in the form's language.
For custom messages, you can provide a translation for each language:
- In the field settings, open the "Validation" section.
- Click the translation icon next to the "Error message" field.
- Fill in the texts for the desired languages.
If no translation is provided, the fallback chain is used: requested language, Russian, English, error key.
Validation During Step Navigation
In multi-step forms, validation is performed before moving to the next step. The attendee cannot proceed until all required fields on the current step are filled in correctly.