Event-Based

• Each event in the list specifies a condition (such as barcode detected, blank page, patch code, etc.) that can trigger the creation of a new document or folder.
• Events are evaluated in order; the first event to return a disposition determines the separation action for the page.
• Use the collection editor to add, remove, or reorder events to match your workflow requirements.

Usage Example:
Add a 'Barcode Detected' event to separate at barcode pages, followed by a 'Blank Page Detected' event to separate at blank pages.

Best Practices:

• Order events from most specific to most general to ensure correct prioritization.
• Include only the event types relevant to your batch structure.

• When enabled, Control Sheets are detected and processed in addition to other configured events.
• Control sheets can encode separation instructions, folder levels, and content type assignments.
• If disabled, only the events in the 'Events' list are considered for separation.

• When enabled, every detected Control Sheet is removed from the batch after separation, even if the control sheet itself is configured to be retained.
• Use this property to enforce a clean batch with only document pages remaining after separation, which can simplify downstream processing and review.
• If disabled, the deletion behavior for each control sheet is determined by its own embedded settings.

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.