Field security

This topic guides you when you are setting up field validations for form definitions.

Use the Security slider in the Field dialog to adjust how sure Interpret must be about each character. Base your decision on the validation possibilities and the importance of accuracy for the field.

The higher the security, the less Interpret guesses and the more sure the result is.

Examples

If a field has a checksum control, a higher interpretation level than the default can be selected, because the result of FORMS' interpretation is checked and, if the check digit is incorrect, the field is brought to your attention during verification.

If there can only be one value in a field, for example a specific digit in a character field if a mark field next to it is checked, you can set both To and From to reflect this specific digit. Then, to make it easier for FORMS to interpret the value as that digit, you can increase the interpretation level to maximum. Security is still high because of the strict field validation.

If, on the other hand, there is no suitable validation routine and an incorrectly interpreted value could therefore pass unnoticed, the security level should be increased.
 

Warning
  • This setting can have unexpected results. The effect can be very different for different fields. Results can vary greatly depending on the quality of the form and the form image. Test the effect of your changes on many forms.

  • High or maximum interpretation can result in undetected errors. Wrong characters can be shown for a field with Complete status. Use only for fields that are validated against valid values, or fields whose values do not have to be correct.

Options for field definitions

Advanced options and validation routines

Demand fields