Validation is used to verify if the candidate's answer is in the correct format, depending on the verification chosen. When the response does not match the validation criteria, an error will be displayed alerting the candidate how to match their response to the necessary format. 

Recommendation: Any form field that can have a validation should have one to prevent the amount of incorrect data collected.

Use cases

• Users who want to improve the data quality and consistency.
• Users who want to have a more streamlined integration with other HR systems.
• Users who want to reduce manual intervention and error correction.
• Users who want to have more accurate reporting and analytics.

Validation options

The following are available validation options. You can test all Regex validations through the form or here.

• Single letter – Only accepts one letter A-Z. Numbers or special characters are not accepted.

• Number – This validation is code based (non-regex). Currently this only accepts numerical digitals or decimals (1 or 1.0).
• Phone number – This validation will accept either 11 digits with/without + or 12 digits with +. If you select Phone Number in the Source Field, the system will add additional validate to check it’s a real phone number by sending the input to Twilio through this API. 

• US Phone number – Accepts 10 or 11 digits, but only with the dialing code +1 regardless of format (XXX-XXX-XXXX, XXXXXXXXXX, (XXX) XXX-XXXX, etc.).

• Email address – A response must contain an @ symbol and a proper domain ending.

• ZIP code – 5 digits

• State - Name and Abbreviation – Would accept “Arizona” and/or “AZ”, for example, depending on the selected validation.

• State - Name – Would only accept “Arizona”.

• State - Abbreviation – Would only accept “AZ”, for example.

• City – Uses regex to validate the characters are valid for a city, but will not validate that “Scotsdale” is invalid when it should be “Scottsdale”.

• Street address – Validates standard formats, accepting numbers, letters, spaces, slashes, periods, and hyphens in a typical street address pattern. It requires at least one number followed by street information, allowing for common address formats like '123 Main St', '456-A Oak Avenue', or '789/2 West Blvd'. International characters are supported for addresses outside the US.

• Country – Ensures only letters and spaces are entered in the Country field. It accepts country names like 'United States', 'New Zealand', or 'Costa Rica', but prevents numbers, special characters, or symbols from being entered.

• SSN – A valid SSN meets the following criteria:
  • It should have 9 digits.
  • Divided into 3 parts by a hyphen (-).
  • The first part should have 3 digits and should not be 000, 666, or between 900 and 999.
  • The second part should have 2 digits and it should be from 01 to 99.
  • The third part should have 4 digits and it should be from 0001 to 9999.

• Date (DD/MM/YYYY) – This validation is code based (non-regex).
• Date (MM/DD/YYYY) – This validation is code based (non-regex).
• Past Date (DD/MM/YYYY) – This validation is code based (non-regex).
• Past Date (MM/DD/YYYY) – This validation is code based (non-regex).
• Future Date (DD/MM/YYYY) – This validation is code based (non-regex).
• Future Date (MM/DD/YYYY) – This validation is code based (non-regex).

• Text – This validation ensures text entries start and end without spaces, while allowing letters, apostrophes, hyphens, and international characters between words.

• Text Trimmed – This validation ensures text entries start and end without spaces, while allowing letters, apostrophes, hyphens, and international characters between words. It prevents entries with leading or trailing spaces, ensuring clean, properly formatted text that appears professional in your forms and documents.

• ABA Routing Number – Inputs are validated using this algorithm.
  • When entering a routing number, the candidate must enter exactly 9 digits of only numbers (no letters or symbols). Spaces or dashes can be used and will be ignored. The computer does quick math check to see if the number is formatted right, but even if it passes this check, it might not be a real bank's number. If a candidate is having trouble, double-check that all 9 digits are typed correctly and that you're using the right number for your bank.
• SIN – Inputs must be 9 digits, validated with this algorithm.
• Province – Two letters, either uppercase or lowercase.

• Municipality – Validated through a string that can contain the alphabet, hyphens, dots, and spaces.

• Postal Number – Follows the formate of <letter><digit><letter>__<digit><letter><digit> and valid codes as mentioned here.

• Custom Validations – Available custom validations, which are listed below, allows you to set the exact input method required for your fields. Click here for more information.
  • Custom Numeric – This allows you to set the exact number of digits required and define the error message displayed when the validation fails for this validation option.
  • Custom Alphanumeric – This allows you to set the character count requirement and define the error message displayed when the validation fails for this validation option.
  • Custom Regex – This can only be configured by your CS Representative.