TravelDocs: Using AIndex for manual page identification and registration

You must be running Datacap 8.0.1 Fix Pack 1 or later to complete this section.

Making a copy of the application
When you finish reviewing AIndex, you need to roll back the changes to the application. You can use the Datacap Studio Application Wizard to make a copy of the application and then work on the copy.
Updating the application
You configured the PageID ruleset to use multiple page identification techniques that are implemented in a cascade fashion. To demonstrate manual page identification by using AIndex, you are going to remove the text matching and pattern matching functions and send any batch with unidentified pages to AIndex.
Updating ManualPageID
You must configure the ManualPageID task to use aindex.aspx. You also must add the required page and field status settings and set the template path to point to the fingerprint folder of the application. Additionally, you must create a rule that runs if a user changes an existing page status.
Creating the ManualIDValidate rule
AIndex assigns the failed (DOF) page status if you change an existing page type. You cannot complete the batch if any page has a failed status, so you need a rule to change the status to done.
Running a batch through the workflow
Because Rulerunner is not configured to run the TravelDocs2 application, you need to use Datacap Web Client to run the batch through the background tasks.
Testing the ManualIDValidate rule
Run another batch through the workflow but this time change the page status on one of the pages to start the ManualIDValidate profile.

Parent topic: Learning from sample applications

Related concepts

Manually identifying and registering pages (AIndex)
Verifying by using AIndex