Description
Relative Date Validation allows form creators to set dynamic, rule-based boundaries for Date fields. Instead of restricting users to static calendar dates, you can automatically calculate minimum (Start date) and maximum (End date) allowable dates based on a dynamic reference point.
This ensures data accuracy by preventing users from submitting illogical timelines. If a recipient selects a date outside your configured range, an error occurs, and they are blocked from completing the document until the date is corrected.
How to set up
Select the Date field you want to restrict. In the right-hand settings panel, locate the Start date and End date sections.
2. Click the dropdown menu under Start date (to set a minimum limit) or End date (to set a maximum limit) and select Relative date.
3. Choose what the date should be relative to in the Reference date dropdown:
User's system date: Validates based on "Today" — the day the recipient fills out the form.
Another Date: Validates based on the value entered in a different Date field (for example, referencing a "Start Date" field to validate an "End Date" field). Fields with an incompatible date format are shown as unavailable in the dropdown.
4. Configure the Offset to determine the actual boundary:
Direction: Select Add (+) to shift the boundary into the future or Subtract (−) to shift it into the past.
Value and Unit: Enter a number and choose between Days, Weeks, Months, or Years.
Example: To require a one-month lead time, set Add (+) | 1 | Months.
Once configured, the system automatically generates a helper text below the field (for example, "Enter a date between Today + 14 days"). This guides the recipient and helps reduce errors before they happen.
To keep in mind:
If you link two Date columns within a table (e.g., Row 1 Start Date and Row 1 End Date), the validation logic automatically applies strictly to the sibling fields within that exact row.
If you attempt to delete or change the format of a Date field that is currently acting as a "Reference" for another field's validation, the Editor will display a warning. This prevents you from accidentally breaking your document's logic.
Use Cases
Use Case 1: Notice of compensation plan change (Minimum notice period)
The Scenario: Company policy dictates that any change in a salary plan must have at least a 14-day notice period.
The Setup: You place a single "Effective Date" field on your form. In its settings, you configure a Start date restriction.
The Logic: Reference date = User's system date | Offset = Add (+) 14 Days.
The Result: When a manager fills out the form, the system automatically calculates the boundary based on their current day. The calendar will gray out and block any dates within the next 13 days. The user cannot click the "Complete" button until a date at least 14 days in the future is selected.
Use Case 2: Project timeline (Dependent dates)
The Scenario: In a project form with a "Start Date" and an "End Date", the end date logically cannot occur before the start date.
The Setup: On the "End Date" field, you configure a Start date restriction using the other field as the anchor.
The Logic: Reference date = Start Date (Field) | Offset = Add (+) 0 Days.
The Result: As soon as the user picks a Start Date, the End Date's validation updates instantly. If they pick May 10th to start, the system restricts the End Date calendar so they physically cannot pick May 9th or earlier.