When Server processes a batch, all single field validation rules for simple fields are processed. This includes those rules inherited by a parent class. Once all simple field validation rules are processed, single field validation rules for table fields are processed row by row. Finally, any multi-field validation rules are processed.

A validation rule is ignored if a dependent field formatter or a previously processed rule fails.

Validation rules can be inherited from parent classes or passed to child classes. An inherited validation rule can be changed in the child classes.

Multi-field validation rules create dependencies among fields or table fields. If you map fields in a multi-field validation rule that are not shown on the same validation form or are defined as read-only, a warning is displayed. You can also check warnings by selecting Validate Project from the Configuration group on the Project tab of the Ribbon. For read-only and invisible fields, validation rules are not processed, but if necessary, can be forced valid.

Multi-field validation rules create dependencies among fields or table fields. Mapping a multi-field validation rule to fields that do not appear on the same validation form or that are defined as read-only generates a warning. To check warnings, select Validate Project from the Configuration group on the Project tab of the Ribbon. For read-only and invisible fields, validation rules are not processed, but if necessary, can be forced valid.