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.

About this task

The page and field status settings for AIndex are the same as those settings for VeriFine (see Configuring the VeriFine client).

  • Ignored field statuses
    The Ignored Field Statuses field determines which fields to hide, meaning AIndex does not display any field that has one of the specified status values.
  • Done field statuses
    The Done Field Statuses field determines which fields to hide when the Problem fields only check box is selected. Because you are hiding all of the fields, it does not really matter which value you enter. However, you can enter 0 (the standard setting) for the Done Field Statuses field.
  • Done page statuses
    The Done Page Statuses field is used to determine when a batch is complete. When all of the pages in a batch have one of the specified values, you can complete the batch. Otherwise, you can put the batch on hold only.
  • Validation statuses
    The Validation Statuses field specifies three page status values.
  • Editing the ManualPageID settings
    The ManualPageID settings control how AIndex manages pages and fields with the specified status values.
Parent topic: TravelDocs: Using AIndex for manual page identification and registration