Rule checks whether the field is empty or nonempty according to the rule settings.

The rule can be found in Basic rules.

	Rule usage example
	Field address has to contain any nonempty value.

Rule checks whether at least n of m selected fields are empty or nonempty according to the rule settings.

The rule can be found in Basic rules.

	Rule usage example
	At least 2 of the fields phone, email, and address has to have nonempty value.

Rule compares the incoming field value with constant set up in rule parameters.

The rule can be found in Basic rules.

	Rule usage example.
	Rule usage example: Age in years has to be greater or equal to 21.

Rule checks whether the incoming field value is in the specified interval.

The rule can be found in Basic rules.

	Rule usage example
	Rule usage example: Weight in kilograms has to be greater than 480 and lower or equal than 520.

Evaluates a CTL expression and rejects validated record when the result is false.

The rule can be found in Basic rules.

	Rule usage example
	Start time is lower than end time. Records where start time is greater than end time will be rejected.

	Note
	Filter expression editor helps editing the CTL expression.

Checks if value is present or missing in lookup table.

The rule can be found in Basic rules.

	Rule usage example
	Product code is a valid product code from the table. Consider all record not having corresponding product code in the lookup table as invalid.

	Note
	Data field and corresponding field from lookup table need to have same data type.

The rule accepts any field.

The rule can be found in Basic rules.

The rule rejects any record.

The rule can be found in Basic rules.

Rule Is Date checks string field to be in desired date and time format. See Date and Time Format

The rule can be found in String rules.

	Rule usage example
	Check start date to be in format yyyy-MM-dd.

	Note
	Functionality of date validation depends on correct locale and timezone settings. See Locale and Time Zone.

	Important
	If you have date in yyyyMMdd format (e.g. 20150111) and you need to have exactly 8 characters, use Strict validation from Locale and format settings to check date correctly. Otherwise you 2011011 would be considered as valid date corresponding to the mask. The date would be interpreted as 2011-01-01.

Rule Is Number validates field to have a desired numeric format.

The rule can be found in String rules.

	Rule usage example
	Weight must be an integer.

Rule String Length checks the length of the string.

The rule can be found in String rules.

	Rule usage example
	Login name has to be have at least 3 letters. The maximal allowed length is 20 characters.

Rule Pattern Match checks whether the field corresponds to a regular expression.

The rule can be found in String rules.

	Rule usage example
	Check name to begin with letter A and to be formed by at least 3 letters.

Rule Enum Match checks field to contain one of values from predefined set of values.

The rule can be found in String rules.

	Rule usage example
	Field must have value of "A" or "B".

Rule E-mail Address checks a field to be valid email address. Valid email address means an email address in correct format. It does not mean existing email address.

The rule can be found in String rules.

	Rule usage example
	Check that field senderEmail contains valid email address.

Rule Phone Number checks field for phone number in correct format.

The rule can be found in String rules.

Furthermore the rule can convert validated phone number to specified format.

1) (201) 555-5555 is a valid US number, but so is +420 777 777 777 - it is a valid international phone number that you can dial from the US.

2) Usage: D substitutes any digit. You can also specify allowed repetition count with {min,max} pattern.

3) The following output formats of phone numbers are available:

	Rule usage example
	Phone number has to be valid US number with leading international prefix.

Copy copies value of input field to another output field.

The rule can be found in Assignment rules.

	Rule usage example
	Copy content of field startDate to field startDateStr.

Transform can be used to produce custom output values.

The rule can be found in Assignment rules.

	Rule usage example
	Copy a group of input fields to different group of output fields based on which branch of validation tree (group of rules) was successful.

Copy all fields by name copies all input fields onto output fields having the same name and type.

The rule is added as a first rule in tree of active validation rules by default. The rule should not be put after any rule assigning values to output fields as it would overwrite all the output values produced by rules above it.

The rule can be found in Assignment rules.