Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Overall requirement validation

Updated on January 18, 2022

In addition to performing guided validation at the individual document level, the application provides a parallel mechanism at the level of the overall requirement. This allows the system to collect data and perform validation across multiple documents or collect data and perform validations that are not related to any document. For example, you can use this capability to ensure that certain data items collected from one document match data items from a different document.


In the Requirement shown above, there is an overall Requirement validation in addition to the document validations. This overall Requirement validation is guided by three entries:

The Overall Verification Section VerifyMortgageID is presented at validation time so that you can enter information about the information being validated.

You must define the section in the same class as the Requirement rule or in an ancestor class.

The Processing Instructions provide guidance to the operator regarding how to process the requirement.

Runtime results

In this example, the operator has already validated the Passport and State ID documents , and has incorrectly entered the Date of Birth on the State ID. When the operator performs the overall Requirement validation, the operator is presented with the validation screen for validating the document. In the case of this guided validation example (as configured above), the screen looks like the one below.

The operator is asked to Ensure ID matches applicant and across several documents, and is presented with the data as entered from the documents.

In the example below, the Date of Birth entries for the two documents do not match. If the operator tries to proceed, the validation rule indicates why the overall Requirement cannot be validated.

The operator revalidates the documents to repair the birth date error. In this example, it is assumed that the mismatch was due to operator error rather than an actual mismatch on the documents. After the error is corrected, the operator can revalidate the overall requirement.

The system determines that the overall Requirement is now valid and the requirement is completed by changing its status to Resolved-Completed.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us