Overview
Configure form field validations to ensure data accuracy, and integrate these validations into your workflows to enforce data integrity.
Form User Experience
When the form user hits a validation in the inbox, the configured message will appear in red below the field.
When are Validations Triggered in the Inbox?
There are two things that affect when form field validations are triggered in the inbox:
Workflow: Validations are triggered when the user attempts to run a transition/transaction. See the last section of this article for more details.
Field Enablement: Validations will trigger based on the workflow as long as the field is enabled. This means that if a field is hidden using the visible property but it is enabled, then the user will still run into the validation although they cannot see the field.
Where to Set Up Form Field Validations
Start by selecting the form element you want to validate in the form builder.
Then, navigate to the Validations tab in the right panel (checkmark icon).
By default, fields have no validation.
Default Validation Options
Based on the field type selected, you'll have different default validation options.
For example:
For Integer fields, you can set maximum and minimum values.
For Time fields, you can set start and end times.
For Date/DateTime fields, you can restrict input to past or future dates.
Singe Message vs. Multi-Message Validations
Single Message
Select Validation (Single Message) if you want one message to show when a field input is invalid. You can add one or more validations (required, min/max characters, etc.) but only have a single message displayed to the form user if what they input is invalid.
You can create a custom message to show the user in case they don't meet the validation(s), such as "Fill this out."
Multi-Message Validations
Select Validation (Multi-Message) if you want a different message to be displayed for each validation. Only one of the messages will be shown to the form user based on which of the 2 or more validations are violated.
Validation messages are shown in the order that they appear on the validation tab. If more than one validation is violated, only the message for the validation that appears first in the list on the validation tab will be shown.
Regular Expression / Calculation Validations
When Multi-Message is selected, you have the option to add Regular Expression or Calculation validations.
For Calculation Validations, you can select either "must be true" or "must be false" - any validation can be set up with either method; it's just a matter of which way the logic is easier to work with in the calculation. A common use case for making the calculation to make the validation conditional based on other fields on the form.
For Calculation Validations, the validation works like this (we'll use "must be true" selection as an example): In order for the field to be valid, the calculation must result in true (must be true).
Calculation validations do not enforce that the field is required, unless you build that into your calculation using the has-value calculation.
Activating a Validation in the Workflow (Important!)
Connect form validations to your workflow to enforce them during workflow transitions/transactions. Without this step, the user won't ever run into your validations when they use the form in the inbox.
Select the transition/transaction this validation is required in order to complete.
Add the field(s) with validations to the active validations list in the Validations tab
You can activate a group or an array field and then any validations on any fields within it will all be required for the selected transition/transaction.
Form field validations can be activated on as many