Pattern-Based Separation

Can be one of the following types:

• A new document is created at each page where the Value Extractor finds one or more matches.
• The extractor can be configured to detect barcodes, keywords, regular expressions, or any other supported pattern.
• The separation logic is triggered solely by the presence of a match; pages without matches are appended to the current document.

Usage Example:
Assign a barcode extractor to create a new document at each page containing a barcode, or use a regex extractor to split at pages with a specific header.

Best Practices:

• Ensure the extractor is specific enough to avoid false positives.
• Test with sample data to confirm that only intended pages trigger separation.

Can be one of the following types:

• If this Value Extractor produces any results on a page, that page will be excluded from consideration as a separator, even if it would otherwise qualify.
• Use this property to prevent false positives or to filter out pages that match certain patterns (e.g., cover sheets, summary pages).
• Commonly used in conjunction with the main 'Value Extractor' to refine separation logic and improve accuracy.

Usage Example:
Assign a barcode extractor to 'Value Extractor' to separate on barcode pages, and use 'Exclusion Extractor' to skip pages containing a "Do Not Separate" marker.

Best Practices:

• Configure 'Exclusion Extractor' to match only those pages that should never act as separators.
• Test exclusion logic to ensure it does not inadvertently suppress valid separation points.

• When set, all folders created by this provider during separation will be assigned the specified Content Type.
• Use this property to ensure that separated documents are classified correctly for downstream processing and extraction.
• If left unset, folders will not be assigned a specific content type by this provider.

Usage Example:
Assign a "Statement" Content Type to all folders created by a statement separator, ensuring they are processed as statements in later activities.

Best Practices:

• Set 'Content Type' when all separated documents should be classified the same way.
• For dynamic classification, use a provider that supports content type assignment based on extracted values.

Overview

The Bind Only property allows a Separation Provider to execute its page analysis logic and identify potential document boundaries, but without making any changes to the Batch Folder or its Batch Pages. No pages are moved, deleted, or classified, and no new folders are created. Instead, the separation points are recorded for later review and action.

Purpose and Role

• Separation Preview:
  Enables users to preview how the current separation logic will affect a batch, without risk of data loss or unwanted changes.
• Review and QA Workflows:
  Supports workflows where separation points are reviewed and confirmed by a user before being applied, typically using the Separation View in Grooper Review.
• Safe Testing:
  Allows designers to test and validate new or updated separation rules on real data, ensuring accuracy before committing changes.

Usage Scenarios

• Batch Import:
  Run separation in BindOnly mode during import to mark suggested document breaks, then allow operators to review and finalize separation.
• Quality Assurance:
  Use BindOnly to audit how separation logic would perform on production batches, identifying potential issues before they impact downstream processes.
• Iterative Design:
  Experiment with different separation strategies, reviewing the results in the Separation View before applying them.

Best Practices

• Always use BindOnly when developing or tuning separation logic to avoid unintended changes to batch data.
• Combine with the Separation View to provide operators with a visual interface for reviewing and confirming separation points.
• Once separation logic is validated and approved, disable BindOnly to apply the changes to the batch.

Related Features

• Separation View: The user interface for reviewing and confirming separation points identified in BindOnly mode.
• Batch Folder, Batch Page: The objects affected by separation when BindOnly is disabled.
• Separation Provider: The base class for all separation logic in Grooper.