Skip to main content

Creating Data Validation Rules

Validation rules ensure that data entered into an attribute meets defined criteria.

Validation rules ensure that data entered into an attribute meets defined criteria. Validation is applied when a record is saved from a screen and when a record is written by a process. If validation fails, the record is not saved and an error message is shown or written to a notification.

Validation rules apply to individual attributes. For more complex cross-record or cross-object validation, use a process instead.


How Validation Works

A validation rule consists of one or more basic validations - individual comparison checks that each return True or False - and an optional formula that combines those checks using AND, OR, and NOT logic. If no formula is defined, all basic validations are combined using AND by default.


Step 1 - Create the Validation Rule

  1. Open the Configuration application and navigate to Validation \> Validation.

  2. Click New.

  3. Enter a clear, meaningful Name.

  4. Optionally enter a Message to display if validation fails. If left blank, the platform generates a message automatically.

  5. Leave the Formula blank for now.

  6. Enter an Audit Comment and click Save and Refresh.


Step 2 - Add Basic Validations

  1. Select your validation rule.

  2. In the Basic Validation section, click Edit, then Add.

  3. Enter the number of basic validations required and click Add.

For each basic validation, define:

  • Term - a short identifier for the rule, used in the formula (e.g. GE10, LT100)

  • Function - defines how the attribute value is interpreted before comparison (see table below)

  • Operator - defines the comparison logic (see table below)

  • Value - the value to compare against; if using Regex, enter the regular expression here

Enter an Audit Comment and click Save and Refresh.


Step 3 - Define the Formula (Optional)

If the default AND combination of all basic validations is not sufficient, define a custom formula.

  1. Click Edit on the validation rule.

  2. Enter the Formula using AND, OR, NOT, and brackets.

Example:

(GE10 AND LT50) OR (GE80 AND LT100)

This allows two valid ranges while rejecting values in between.


Step 4 - Apply the Rule to an Attribute

  1. Navigate to Objects \> Objects and select the relevant object.

  2. Edit the required attribute and select the validation rule from the Validation field.

  3. Enter an Audit Comment and click Save and Refresh.

The rule runs whenever the attribute value is saved.


Validation Functions

Function

Description

Suitable For

Value

Uses the attribute value directly

All types

Length

Number of characters

String, Text, HTMLText, Reference

Lower

Converts to lowercase before comparison

String-based types

Upper

Converts to uppercase before comparison

String-based types

Trim

Removes leading and trailing spaces

String-based types

Year

Extracts year (YYYY)

Date, DateTime, Timestamp

Month

Extracts month (MM)

Date, DateTime, Timestamp

Day

Extracts day (DD)

Date, DateTime, Timestamp

Hour

Extracts hour (HH)

Date, DateTime, Timestamp

Minute

Extracts minute (mm)

Date, DateTime, Timestamp

Second

Extracts seconds (ss)

Date, DateTime, Timestamp

Round

Rounds number using ROUND_HALF_EVEN logic

Integer, Number

Floor

Rounds down to nearest whole number

Integer, Number

Ceiling

Rounds up to nearest whole number

Integer, Number


Validation Operators

Operator

Meaning

Equal To

Exact match

Not Equal To

Must differ

Greater Than

Strictly greater

Greater Than or Equal To

\>=

Less Than

Strictly less

Less Than or Equal To

\<=

Contains

Must contain specified characters

Does Not Contain

Must not contain specified characters

Empty

Must be null

Not Empty

Must have a value

Regex

Entire value must match regular expression


Important Notes

  • Validation applies only if the attribute is required or has a value. Blank values on non-required attributes are not validated.

  • String comparisons using greater/less than are based on ASCII values.

  • Keep validation rules simple and use meaningful Term names.

  • Always provide a clear custom message for complex logic so users understand why their input was rejected.

Did this answer your question?