Validations on a data component specify specific data characteristics that must be true before data can be stored.

 

A document can have multiple validations. Each is executed in the sequence they were specified.

 

Validations are composed of Execution Conditions and Actions.

 

Execution Conditions

If the specified conditions evaluates to 'TRUE', then the specified actions are executed. 
An execution condition can be of three types:

• Match All - If all of the specified conditions are true, the specified actions are taken.
• Match Any - If any of the specified conditions are true, the specified actions are taken.
• Expression- If the specified expression is true, the specified actions are taken.

Actions

• Display Error - A message is delivered to the user, and the record is blocked.
  • Click the magnifier icon to add template variables that supply data from the stream record.
  • Such variables have the form $DataComponent.FieldName.
• Display Warning - A warning is delivered to the user, requiring them to click through, in order to proceed.
  • Click the magnifier icon to add template variables that supply data from the stream record.
  • Such variables have the form $DataComponent.FieldName.
• Execute Rule - Invoke a rule that has been defined in the system, and execute the actions defined in it.

Examples

​

Example: Match All

In this example, all the conditions specified have to be evaluated to true to pass the evaluation. An example of this is if 

        Incident.Country  equals US

        Incident.Zip equals {leave it blank}

 

In this scenario, the validation action is taken only if the country is US and the Zip field is empty.

 

Example: Expressions

Some validations are too complex to be handled through simple specifications like those above. For those validations, Custom expressions can be created. Here, fields from the SiteAssessment data component are referenced to make the expression.

 

In this example, an error is triggered if it is indicated in an assessment that followup is needed, but a followup date has not been specified.

   

The validation below will trigger if Follow Up date is not a future date