The validation and output formatting features enable you to standardize the development and maintenance cycles for each BIC implementation. However, standard validation has not replaced scripted validation. BIC still supports validation scripts. For a brief introduction to script validation, see About Validation Scripts. For more information, see the Brainware Intelligent Capture Scripting Help.
Validation is a quality assurance task that involves confirming whether a field extraction is correct or incorrect. Validation is configured in Designer’s Validation editor, but the actual work is done in Runtime Server, Verifier, and Advanced Verifier.
Runtime Server loads the project at runtime and executes validation after extraction, but before exporting the project. Documents that fail validation in Runtime Server are forwarded to Verifier for quality assurance. Verifier loads the settings and uses property sheets to display the validation settings.
Validation uses BIC’s hierarchical organization of relationships between parent and child elements.
While Runtime Server processes a batch or list of batches, each containing several documents, it first tries to classify the processed document. After classification, the extraction is performed for each field defined for this document class. The validation rules for a field can either be defined for this document class but can also be inherited from the parent class.
A document is valid when all fields on the document are valid. If one field is invalid according to standard validation or script validation rules, the whole document is invalid. The script validation for a field only performs when the standard validation is valid. If one document of a batch is invalid, the system passes the whole batch to Verifier. If a field’s standard validation is set to invalid, the corresponding script events will not execute.