Form Type

Purpose

The 'Page Count' property indicates how many Page Types are defined for this Form Type, corresponding to the number of pages in the original training sample.

• Used by the classification engine to match documents of the same length and structure.
• Reflects the structure of the trained example, including any cover sheets, inserts, or appendices.

Usage Notes

• This property is read-only and determined by the number of child Page Types.
• If you need to support documents with a different number of pages, provide additional training samples.

Can be one of the following types:

The 'Language' property determines the under which this Form Type was trained.

• This value is set automatically during training, based on the language of the sample document.
• The selected language affects text recognition, extraction logic, and classification accuracy, especially for multilingual or region-specific documents.
• If not explicitly set, the property defaults to the current system culture.
• Use the language editor to select from available cultures and locales.

Purpose

The 'Page Scope - Data Extraction' property limits the number of pages loaded and processed during data extraction and data review. This is especially useful for large documents where only the first few pages are relevant for extraction.

Usage

• Set to a positive integer to restrict extraction to the specified number of pages.
• A value of 0 means all pages are included (unlimited).
• Adjust this setting to optimize performance and focus extraction on the most relevant content.

Related Concepts

• Data Model: Defines the data elements to extract.
• Extract activity: Uses this property to determine which pages to process.

Purpose

The 'Behaviors' property allows you to attach reusable logic, rules, or settings to a Content Type. Behaviors are inherited by descendant types, promoting consistency and reducing duplication.

Usage

• Add or configure Behaviors to control processing, validation, or appearance for documents of this type.
• Only one instance of each behavior type is allowed per Content Type.
• Behaviors can be overridden in descendant types for specialized scenarios.

Related Concepts

• Behavior: Encapsulates logic or settings for processing and UI.
• Inheritance: Behaviors are inherited from parent Content Types.

Purpose

The 'Child Of' property can be used to indicate a hierarchical relationship where Content Type is expected to appear as a child of the selected parent type in batch structures. This relationship allows expressions used for field validation, calculated values, export mappings, and other purposes to access data elements from the parent or ancestor objects directly.

Parent Data Exposure in Expressions

When a Content Type is configured with a 'Child Of' parent, the data elements of the parent Content Type are automatically exposed to the expression environment of the child. This means that expressions used for field validation, calculated values, export mappings, and other scenarios within the child can directly reference data values stored on the parent or ancestor objects.

For example, in a multi-level batch structure such as:

• Personnel File (Parent Content Type)
  • Employee_ID (Data Element on Personnel File)
  • Employee_Name (Data Element on Personnel File)
• Benefits Change Form (Child Content Type)
  • Request_Date (Data Element on Benefits Change Form)
  • Change_Reason (Data Element on Benefits Change Form)

The 'Benefits Change Form' can access data elements from its parent 'Personnel File' in its own field expressions. This give code expressions used on 'Benefits Change Form' access to field like Employee_ID and Employee_Name, and enables scenarios such as:

• Validating a field on the child against a value stored on the parent (e.g., ensuring an employee ID matches).
• Including parent data such as 'Employee ID' in export file names or data mappings.
• Referencing parent fields in calculated expressions for child data elements.

The expression environment exposes parent data elements using a property named after the parent Content Type. For example, if the parent is "Personnel File", its data elements are accessible via Personnel_File.Employee_ID in expressions on the child.

Usage

• Use for multi-level batch structures where parent-child relationships are required (e.g., Personnel File <-- Benefits Change Form).
• Enables export and processing logic to include data from parent elements.
• The selected parent cannot be a descendant or ancestor of this type.

Overview

Setting the 'Sibling Of' property makes the data elements of the sibling Content Types directly accessible in the expression environment of this type. This means you can reference fields, sections, or tables from sibling types in calculated values, validation rules, or export mappings. For example, if "Type A" is a sibling of "Type B", expressions in "Type A" can reference data from "Type B" using the syntax Type_B.FieldName.

Usage Guidance

• Use 'Sibling Of' when a document or folder must be treated as multiple types for extraction, validation, or export.
• Sibling relationships are not hierarchical; all types listed are considered peers for the purposes of data access and processing.
• Avoid circular or redundant sibling assignments, as this can complicate configuration and data access logic.
• Sibling types are assigned as secondary types, and their data is available for use in expressions and export scenarios.

Related Concepts

• Batch Folder: The container to which content types are assigned.
• 'Secondary Content Types': The property on Batch Folder objects which allows assignment of multiple types to a document.
• Content Type: The document or folder type being configured.
• Expressions: Sibling data elements are available for use in calculated values, validation, and export logic.

Can be one of the following values:

Purpose

The 'Caption' property allows you to define a dynamic naming expression for documents, which is recalculated whenever document data changes.

How It Works

Each time index data is saved on a Batch Folder, the Caption expression is evaluated and the folder is renamed to match the result. This ensures that folder names remain synchronized with the underlying data values, and reflect any changes made to extracted or user-entered data.

The Caption expression can reference any data element available in the expression environment, including fields from the current Content Type and, if applicable, data elements from parent types (see the 'Child Of' property for details).

For example, you might use an expression like to generate a name that includes both the 'Invoice No' and 'Invoice Date' fields.:

$"{Invoice_No}_{Invoice_Date:yyyyMMdd}"

Usage

• Useful for making document names more meaningful and easier to identify in the UI.
• When merging multiple documents in a PDF file with bookmarks, the Caption is used as the bookmark name.

Related Concepts

• Batch Folder: The folder whose name is affected by this property.
• Document Instance: The runtime data object used in the expression.
• 'Child Of': Enables access to parent data elements in the expression environment.

Can be one of the following types:

Purpose

The 'Hide Numeric Suffix' property determines if a numeric suffix (e.g., "Document (2)") is shown for documents of this type.

Usage

• Set to true to hide the numeric suffix for a cleaner display.
• Set to false or leave unset to allow numeric suffixes when needed for uniqueness.
• Inherited from parent Content Types if not set locally.

Related Concepts

• Batch Folder: The folder or document whose display name is affected.
• 'Caption': May also influence the displayed name.