Document Type

When enabled, this Document Type can be included in training operations if the parent Content Model uses a training-based classification method.

• Training allows Grooper to learn from sample documents, improving classification accuracy for complex or variable layouts.
• If disabled, this type will be excluded from training and cannot be selected as a target for training commands such as Train As or Train From.

Enable this property if you want users or automated processes to provide training samples for this Document Type.

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.

Can be one of the following types:

If the extractor provided here successfully extracts one or more values from a document, the document will be classified as this Document Type with no further processing.

• Use this property to define a rule or pattern that uniquely identifies documents of this type.
• This is typically used for highly distinctive features, such as a specific title, logo, or keyword.
• If set, this extractor takes precedence over other classification logic for this type.

Assign a Value Extractor that reliably matches only the intended documents.

Can be one of the following types:

If the extractor provided here successfully extracts one or more values from a document, this Document Type will be excluded from consideration during classification.

• Use this property to define patterns or features that disqualify a document from being this type.
• This is useful for filtering out false positives or documents with ambiguous features.

Assign a Value Extractor that matches only when a document should not be classified as this type.

During classification, any document with fewer pages than this value will be excluded from consideration as this Document Type.

• Set to zero to disable the minimum page limit.
• Use this property to prevent short documents from being misclassified as types that require more content.

Adjust this value to match the expected minimum length of documents for this type.

During classification, any document with more pages than this value will be excluded from consideration as this Document Type.

• Set to zero to disable the maximum page limit.
• Use this property to prevent unusually long documents from being misclassified as this type.

Adjust this value to match the expected maximum length of documents for this type.

The 'Scoring Limit' property can be used to ensure that this Document Type does not outscore other types in ambiguous cases.

• If a document matches multiple types, the scoring limit can be used to prioritize one type over another.
• The output confidence for this type will never exceed the specified value, regardless of the underlying classifier or rule results.
• Applies to both classifier results and classification rules.

Set this property to fine-tune classification priority and resolve conflicts between similar types.

Can be one of the following values:

The 'Pagination Type' determines how Grooper identifies the start and end of documents for this Document Type during batch separation.

• Select the value that best matches the structure and consistency of your documents.
• The choice of pagination affects the behavior of related properties such as 'Page Count', 'Prioritize EPI', and 'Repeating Last Page'.

See the remarks for each value for detailed guidance.

• If enabled, Grooper will start a new document whenever any page classifies confidently as this Document Type, not just the first page.
• If disabled, only confident Page 1 results will trigger separation.

Use this property to support document types where any page can indicate the start of a new document, such as forms that may begin on any page.

The document will always consume exactly this number of pages, unless the start of a new document is encountered.

• Set this property to the expected length of documents for this type.
• If the number of pages does not match, the document will not be classified as this type.

Use for highly consistent, fixed-length documents such as standardized forms.

• Use this property to merge adjacent documents of the same type into one, reducing fragmentation in the batch.
• This is useful for scenarios where documents may be split during separation but should be treated as a single logical document.

Enable when you expect multiple consecutive documents of this type to be part of a single entity.

• When enabled, the EPI sequence is considered immutable, and cannot be broken even if a page classifies confidently as the start of another document.
• When disabled, a confident Page 1 classification can break the EPI sequence, starting a new document.
• Only available when 'Pagination' is set to 'Unstructured'.

Use this property to ensure that documents with reliable EPI are not split incorrectly due to classification results.

Can be one of the following values:

The 'Training Scope' determines which pages are included as training samples for classification of unstructured Document Types.

• Adjusting the scope can improve classification accuracy and performance by focusing on the most distinctive pages.
• Use a narrower scope (such as 'FirstOnly' or 'FirstLast') for documents where only certain pages contain identifying features.
• Use 'FML' to train separate models for first, middle, and last pages, supporting advanced classification scenarios.

See the remarks for each value for detailed guidance.

Can be one of the following types:

• Pages on which this extractor produces a match will be classified as a middle page of this Document Type.
• During separation, these "middle page" classifications are used to extend unstructured documents downward.

Assign a Value Extractor that reliably identifies continuation pages for variable-length documents.

• Enable this property for structured documents where the last page (such as a signature page) may appear multiple times to accommodate additional signers or parties.
• The separation engine will extend the document to include all repeated last pages.

Use for structured forms with variable-length signature or summary sections at the end.

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.

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.

The 'Relative Of' property defines a set of related Content Types whose data elements are exposed in the expression environment of this type. Unlike 'Child Of' (which establishes a strict parent-child relationship) or 'Sibling Of' (which exposes data from peer types on the same Batch Folder), 'Relative Of' is used for scenarios where related types may appear as siblings, ancestors, or in varying positions within the batch structure, but their data should always be available for reference in expressions, validation, or export logic.

Usage Guidance

• Use 'Relative Of' when you need to reference data from other Content Types that are not guaranteed to be direct siblings or parents, but are always present somewhere in the batch or folder hierarchy.
• This is especially useful for flexible or variable batch structures, where the relationship between types may change, but cross-type data access is still required.
• Data elements from the listed types are made available in the expression environment, using the code name of each related type as a property.
• The relationship is non-hierarchical and does not affect batch organization or processing order.

Example Scenarios

• Cross-Document Validation:
  Suppose you have a "Case File" Content Type and several document types (e.g., "Intake Form", "Evidence Report") that may appear at different levels or folders within a batch. By adding "Case File" to the 'Relative Of' property of the other types, you can reference case-level data in expressions for validation, calculated values, or export, regardless of the batch structure.

• Flexible Batch Layouts:
  In solutions where documents may be grouped differently (sometimes as siblings, sometimes as children), 'Relative Of' ensures that key data elements are always accessible for business rules, even if the batch hierarchy changes.

Example Expression

To reference a field from a related type named "Case File" in an expression:

Case_File.Case_Number

Impact

• The types listed in 'Relative Of' do not affect the batch structure or document organization.
• They simply expose their data elements for use in expressions, enabling advanced cross-type logic and validation.
• Avoid redundant or circular references, as this can complicate configuration and data access logic.

Related Concepts

• 'Child Of': Exposes parent data elements in the expression environment.
• 'Sibling Of': Exposes data from peer types on the same Batch Folder.
• Data Model Compiler: Handles the exposure of related data elements in the expression environment.
• Expressions: Use related data elements for validation, calculation, 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.