ESP Auto Separation

• The selected scope determines which Document Types are available for classification and separation.
• The classification method defined on the scope is used to identify the type of each Batch Page.
• Choose a Content Model to include all document types in the set, or a Content Category to restrict to a subset.

Usage Example:
Set 'Scope' to your main Content Model to enable classification and separation for all document types in your solution.

Best Practices:

• Ensure the scope includes all document types you expect to encounter in the batch.
• Use a Content Category to limit separation to a specific group of document types if needed.

• Each rule specifies which attachment types should be merged with which host document types.
• Attachment rules are evaluated during separation to ensure related pages are grouped together as a single document.
• Use the collection editor to add, remove, or configure rules as needed for your workflow.

Usage Example:
Add a rule to merge "Addendum" pages with their corresponding "Contract" documents.

Best Practices:

• Define rules for all known attachment scenarios to ensure complete and accurate document grouping.
• Review and test rules to avoid unintended merges or missed attachments.

• When enabled, separation will not create a document that includes pages from more than one original file.
• This is especially useful when batches are created by splitting multi-page PDFs or TIFFs, as it prevents accidental grouping of pages from different source files.
• This feature depends on the 'Original Page Number' property of each Batch Page, which is set by the Split Pages activity.

Usage Example:
Enable 'Respect Original Page Numbers' to ensure that each separated document remains within the boundaries of its original imported file.

Best Practices:

• Enable this option if your workflow involves splitting multi-page files and you want to maintain logical document integrity.
• Leave disabled if your batches are composed of single-page imports or if cross-file grouping is intentional.

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.