Validations

From a Dynamic Evidence perspective, Validations refer to data validity checks to be performed on Case Evidence records before they can be saved or activated. In Non-Dynamic Evidence, such validations are implemented at development time using Java code; for Dynamic Evidence, however, these are specified administratively. Validations are invoked at runtime in three situations:

• Upon saving data on a Case Evidence create page in respect of a Dynamic Evidence Type Version which has such defined Validations
• Upon saving data on a Case Evidence modify page in respect of a Dynamic Evidence Type Version which has such defined Validations
• After a case worker has selected 'Apply Changes' or 'Validate Changes' from the Evidence Workspace page, again for Case Evidence in respect of a Dynamic Evidence Type Version which has such defined Validations

Two administrative means of defining Dynamic Evidence Validations are provided via the Validations Tab in the Evidence Properties Panel, and these can be used either separately or in combination:

• Standard Validations

  A number of Standard Validations, frequently used in Evidence processing, are provided out of the box in the Evidence Editor. These have been defined based on an analysis of Evidence Validations written in Java over a period of many years, and distilled into a set of configurable Standard Validations.

  Standard Validations are defined in the Validations tab of the Evidence Properties Panel, and are described in detail in the following section.

• Additional Validations

  In order to specify a validation which cannot be expressed in terms of a Standard Validation, administrators also have the option of defining a CER Rule Set to perform Validations. If provided, this CER Validation Rule Set will be executed in addition to any Standard Validations which exist for a Dynamic Evidence Type Version.

  Information on defining Validations using CER can by found in the chapter on CER Rule Sets; see Validation Rule Sets for more details.