When you create or select one of these supported fields, the Diagram Content Menu (DCM) opens on the right-hand side. A Rules tab will appear next to Properties.
The Rules tab allows you to configure optional validation rules for Currency, Date, Number, Text, and Text Area fields only. These rules are optional, configured individually and apply only to the selected field.
Why Configure Field Rules?
Field rules stop invalid input at the point of entry. Every rule is a mistake the user cannot make and a correction nobody has to do later:
Cleaner data — values arrive in the shape your reports expect (no "$1,200" typed as "1.2k").
Fewer follow-ups — a date rule that blocks past dates prevents "please resubmit with a valid date" conversations.
Guardrails for real-world limits — cap an expense field at policy limits, restrict bookings to future dates, force a valid email format.
Currency
Minimum - sets minimum value that can be entered. (E.g. claim amounts must be at least $1.)
Maximum - sets maximum value that can be entered. (E.g. cap a per-item expense claim at the policy limit of $500.)
Integer only toggle:
If on, only whole numbers are allowed. If a decimal is entered, the field will be rounded up to the nearest whole number when submitting.
If off, decimals are allowed. When more than 2 decimals are entered, the field will be rounded up to 2 decimals when submitting.
Date
Minimum date with dropdown options:
None.
Absolute date. When selected, a second date field appears titled: 'Minimum absolute date'. Contains a calendar, allowing user to choose date. (E.g. an incident report can reference events from 1 January onward.)
Relative to today. When selected, a second number field appears titled: 'Minimum offset (days)'. (E.g. set 0 to stop users entering dates in the past for an expiry or booking field.)
Maximum date with dropdown options:
None.
Absolute date. When selected, a second date field appears titled: 'Maximum absolute date'. Contains a calendar, allowing user to choose date.
Relative to today. When selected, a second number field appears titled: 'Maximum offset (days)'. (E.g. set 30 to require bookings to be made within the next month.)
When date rules are set, only the allowed dates are enabled, indicating to users which dates are allowed.
Number
Minimum - sets minimum value that can be entered. (E.g. quantity must be at least 1.)
Maximum - sets maximum value that can be entered.
Integer only toggle:
If on, only whole numbers are allowed. If a decimal is entered, the field will be rounded up when submitting. (E.g. head counts are whole people.)
If off, decimals are allowed in accordance with the number set in the next field. When more than the allowed decimals are entered, the field will be rounded up to the allowed number of decimals when submitting.
Decimal precision (description: Number of digits after the decimal. Applied on blur.).
This field disables when Integer only toggle is on.
Enables when toggle is off. (E.g. set 2 for currency-style values like 123.45.)
Text
Minimum length - sets minimum characters that can be entered. (E.g. require at least 5 characters so "n/a" is not accepted as a description.)
Maximum length - sets maximum characters that can be entered. (E.g. match the length of a reference code field.)
Pattern matching
None
Email address - needs to be in a typical email address format.
Phone number - can add any amount and combination of numbers and dashes (-).
Website - a website URL must be entered.
Numeric - Any combination and length of numbers are allowed.
Alphanumeric - Any combination and length of numbers and letters only.
Whitelist specific characters (Note: only these characters are allowed) - type characters next to each other without any dividers, case sensitive.
Blacklist specific characters (Note: these characters are not allowed.) - type characters next to each other without any dividers, case sensitive.
Use pattern matching when a field has a known format — it validates the shape of the input at entry, so downstream reports and exports receive well-formed values.
Further Information
For conditional show/hide logic and default values, see Adding Business Rules to Dynamic Forms. For field details and properties, see Dynamic Forms: Form Field Details, Properties, Rules. For testing validation behaviour, see Previewing and Testing a Dynamic Form.