--- title: "Validations" slug: "validations-2-1" updated: 2026-11-05T01:32:27Z published: 2026-11-05T01:32:27Z canonical: "kb.easysend.io/validations-2-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.easysend.io/llms.txt > Use this file to discover all available pages before exploring further. # Validations ## Article Overview The following article describes how to add validations with examples. ## What Are Validations? (See **Figure 1**) Validations are used to ensure the integrity of the information entered by end-users while interacting with a digital process. ## Adding Validations (See **Figure 1**) Validations are applied to Webflow components. When clicking a component, the Behavior tab appears on the right section. The Behavior tab includes a checkbox to apply a required validation (1) and an option to add other EasySend built-in validations (2). ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1738767090654.png) **Figure 1: Behavior Tab** ### The Required Validation (See **Figure 2** and **Figure 3**) A required validation makes sure that a field is not left blank. It forces the end-user to provide a value before navigating, ensuring that all necessary information is collected. To turn a field into a required field, click a component, display its Behavior tab (1), and check the Required checkbox (2). ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1746110836099.png) **Figure 2: Required Checkbox** In a digital process, a required field appears with an asterisk (3). When trying to leave a page with an empty required field, an error message appears (4). ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1738769932024.png) **Figure 3: Required Validation** ## Adding Validations (See **Figure 4** to **Figure 7**) To add a validation, click a component, display its Behavior tab (1), and click the + Add Validation option (2). ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1746110870119.png) **Figure 4: + Add Validation** When clicking the + Add Validation option, the Edit Validation window appears. The Edit validation window contains a dropdown (3) with a list of available built-in EasySend validations. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1738771040295.png) **Figure 5: Validations Dropdown** Some selected validations require you to input parameters, for example, adding the Cellphone validation requires you to select a country code (4). ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1738771802634.png) **Figure 6: Validation Parameter** After clicking the **Save** button (5) the list of added validations (6) appears in the Behavior tab. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1742394323142.png) **Figure 7: Added Validations** NOTEWhen applying multiple validations to one field, the sequence in which the validations will be triggered is according to the order in which they were added. ## Pattern (Regex) Validation Regex (regular expression) describes the shape a piece of text must have. Think of it as a stencil. You define the outline, such as “three letters, a dash, then six digits,” and anything the user types either fits the stencil or doesn’t. It doesn’t care what the value means, only that it’s built the right way. Usually, Journeys offers named validations like Email or Date. They cover common formats, but every business has its own: policy numbers, member IDs, internal reference codes. With custom regex, you write the stencil yourself. Table 1 provides a few Regex examples. **Table 1 - Regex Examples** | What you want to accept | Regex | Accepts | Rejects | | --- | --- | --- | --- | | Policy number: “POL-” then 6 digits | `^POL-\d{6}$` | POL-482913 | POL-4829, pol-482913 | | US ZIP code, optionally ZIP+4 | `^\d{5}(-\d{4})?$` | 90210, 90210-1234 | 9021, 90210-12 | | Exactly 9 digits (e.g. an ID number) | `^\d{9}$` | 123456789 | 12345678, 12345678A | | Uppercase letters only | `^[A-Z]+$` | SMITH | Smith, SM1TH | | Vehicle VIN: 17 characters, no I, O or Q | `^[A-HJ-NPR-Z0-9]{17}$` | 1HGCM82633A004352 | anything with an O, or 16 characters | ### Business value - **Self-service -** Journeys users can handle new formats on their own, the same day, instead of opening an R&D request and waiting for a release. - **Less R&D load - o**ne generic capability replaces an endless stream of one-off named validations. That’s the “closes a gap generically” part of the story. - **Cleaner data at the source -** bad formats are caught while the customer is typing, not later by a back-office team or a failed integration downstream. - **Better customer experience -** the customer sees an immediate, clear error (“Policy numbers look like POL-123456”) instead of being contacted later to fix a mistake. - **Faster delivery for customer projects -** professional services and partners aren’t blocked by a missing validation when a client has an unusual format. ### How to Configure (See **Figure 8**) After selecting a Text Field or a Text Area component and opening the Edit Validation window as described in the **Adding Validations** section, locate the Pattern validation and write the Regex. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1793824747555.png) **Figure 8: Pattern (Regex) Validation** ## Date Picker Validations The Date Picker component has three specific validations - Only dates within range allowed - Only future dates allowed - Only past dates allowed ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1793825423952.png) **Figure 9: Date Picker Validations** ### **Business Value** **Enforce business rules at the point of entry** - Policy start dates within the next 30 days, not two years out. - Claim incident dates within the coverage period. - Applicant birth dates within an eligible age range (e.g., 18–75 for a product). - Appointment or delivery dates only within an available booking window. **Prevent impossible or illogical data** - An end date before a start date, or a birth date in the future. - Typos like 1925 instead of 2025 that pass a basic “valid date” check but are obviously wrong. **Reduce rework and back-office effort** - Every out-of-range date submitted has to be caught later, followed up with the customer, and corrected. Catching it in the form removes that loop entirely. **Support compliance and eligibility** - Regulated products often have strict time limits: a cooling-off period, a filing deadline, a minimum age. Building these into the form means the process can’t accept an application that breaks them. **Better customer experience** - The customer finds out immediately, with a clear message (“Start date must be within the next 30 days”), instead of getting a rejection email days later. **Less custom work, again** - Like the regex validation, it replaces one-off custom logic with a configurable, reusable rule that Journeys users can set themselves. ### How to Configure (See **Figure 10**) After selecting a Data Picker component and opening the Edit Validation window as described in the **Adding Validations** section, locate the desired validation and configure it, for example: ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1793825485175.png) **Figure 10: Only dates within range allowed Validation**