Multi Separator

• Each provider in the list is evaluated in sequence for every page in the batch.
• The first provider to assign a separation action to a page determines the separation for that page; subsequent providers are only consulted if no action is assigned.
• Use the collection editor to add, remove, or reorder providers to match your workflow requirements.

Usage Example:
Add a Control Sheet Separation as the first provider, followed by a Pattern-Based Separation to handle pages not separated by control sheets.

Best Practices:

• Place the most restrictive or specific providers first to ensure they take precedence.
• Use a general-purpose provider (such as Pattern-Based Separation) last as a fallback.

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.