Page logic: Overview

Page logic settings are specified in document specifications and tell the program how pages in documents are organized. The selected page logic affects the number of pages on which classifiers and extraction fields can be specified. During production, if a document contains more or fewer pages than specified, an operator must manually inspect the documents.

Documents can consist of these types of pages:

First page (green) and additional pages (gold).

These types of page logic are supported:

• Not defined – not recommended. Provided only for backwards compatibility.

• Fixed number of pages

  Use this type of page logic for documents with only one page or for documents with a definite number of pages. You can specify classifiers and fields on every page. For example, if you set Number of pages to 3, you can specify classifiers and fields on all three pages.

     

  If you only need to extract information from the first page, and not the additional pages, and if you do not need to classify the additional pages, do this:

  1. Set the page logic to Fixed number of pages

  2. Set Number of pages to 1.

  3. Set Min. number of appendices to 1 and Max. number of appendices to 100, for example.
     
     

• First page and additional pages

  Use this type for documents that always have the same information on the first page and at least one additional page to extract information from.

   

  Documents that are scanned or identified using this type of page logic need to contain at least two pages.

  Note: If you only need to extract information from the first page, and not the additional pages, and if you do not need to classify the additional pages, do this instead:

  1. Set the page logic to Fixed number of pages.

  2. Set Number of pages to 1.

  3. Set Min. number of appendices to 1 and Max. number of appendices to 100, for example.
     
     

• First page, additional pages and last page

  Use this type for documents that always have the same information on the first and last pages and that must contain additional pages in between.

       

• First page and additional pages – may overlap

  This is the default page logic for new documents.

  Use this type when a document always has the same information on the first page and additional information which may be on one or more additional pages. If the additional information is also on the first page, the pages (page specifications) overlap.

  Example: The first page of an insurance application always contains the applicant's name. Additional pages contain a list of items to be insured. The length of the application depends on the length of the list. If the application is for only a few items, the document may be only one page long. This means that the applicant's name and the items to be insured are found on the same page. In this case, the page specifications overlap.

  or

• First page, additional pages and last page – may overlap

  Use this type for documents that always have the same information on the first and last pages.

  Example – a typical invoice

  Usually, the first page includes the invoice's header fields, the additional pages contain the line items, and the last page includes the invoice's summary fields. You need to extract all of this information.

     

  If the invoice has very few line items, it is possible for two or even all three of these "pages" to be present on one physical page. This is what "may overlap" means.

  In this case, at least three kinds of pages are available in the document specification, but a one- or two-page invoice that contains only one or a few items would be covered by this page logic, because all of the necessary information is now found on one or two pages.

  or or or

Important: In a document hierarchy, validation rules control the page logic allowed in parent/child relationships. (More information.)

Related topics

Specifying page logic for a document specification