Grooper Help - Version 25.0
25.0.0023 2,165
  • Overview
  • Help Status

Batch Process

Node Grooper.Core

Defines a configurable workflow for processing batches of documents in Grooper.

Remarks

A Batch Process orchestrates a sequence of activities—both automated and human-attended—applied to a Batch as it moves through Grooper's workflow. Each process consists of ordered steps, called Batch Process Steps, which specify the Activity to perform at each stage. Activities may include system-driven tasks (such as image processing, recognition, classification, extraction, and export) or human-driven review tasks.

Workflow Definition

  • A Batch Process is composed of one or more Batch Process Steps, each representing a discrete Activity.
  • Steps are executed in order, but flow control can be customized using expressions or scripts.
  • Activities can be fully automated or require human intervention via Review steps.

Example Processes

The steps included in a process can vary widely depending on the inputs and processing objective. Below are two sample workflows:

Example 1: Scanning Paper Invoices and Exporting to a Database

  • Step 1 – The Review activity configured with a Scan View, to allow scanning.
  • Step 2 – The Image Processing activity, to remove skew and scanner artifacts.
  • Step 3 – The Recognize activity, to perform OCR.
  • Step 4 – The Separate activity, to create documents from pages.
  • Step 5 – The Classify activity, to assign document types.
  • Step 6 – The Extract activity, to extract data elements.
  • Step 7 – The Apply Rules activity, to normalize extracted data.
  • Step 8 – The Review activity configured with a Data View, for human review of documents with missing or invalid data.
  • Step 9 – The Export activity, to export data to a database table.

Example 2: Processing Pre-Separated PDFs and Exporting to a Document Management System

  • Step 1 – The Split Pages activity, to split the PDF documents into pages.
  • Step 2 – The Image Processing activity, to perform image processing on image-based PDF pages.
  • Step 3 – The Recognize activity, to read PDF text and OCR image-based pages.
  • Step 4 – The Classify activity, to assign document types.
  • Step 5 – The Extract activity, to extract data elements.
  • Step 6 – The Merge activity, to create a PDF document with extracted data embedded in metadata.
  • Step 7 – The Export activity, to export the document to a document management system.

Publishing and Versioning

  • Batch Processes must be published before they are available for production use. Use the Batch Process - Publish command to publish.
  • Publishing creates a read-only version in the 'Processes' folder, which is used for all new Batches.
  • Changes to a Batch Process require republishing to take effect for new Batches; existing Batches are not affected until updated.
  • To update an existing Batch to the latest process version, pause the batch and use the Batch - Update Process command.
  • Unpublishing a process removes it from production use but does not delete its configuration.

Flow Control and Customization

  • Steps execute sequentially by default, but execution order can be customized:
    • Use the 'Next Step Expression' and 'Should Execute Expression' on each Batch Process Step for simple, formula-like logic.
    • For advanced scenarios, attach scripts to the Batch Process to handle events such as batch completion and redirect flow as needed.
  • Scripts are event-driven and can intercept or modify workflow behavior at runtime.

Integration with Batches and Folders

  • Batch Processes are applied to Batches at creation or manually by operators.
  • Each Batch contains a hierarchy of Batch Folders and Batch Pages, which are processed according to the defined steps.
  • The 'Content Type' property determines the data model for batch-level indexing and validation.

Error Handling and Review

  • Human review steps can be configured to handle exceptions, missing data, or validation errors.
  • Review queues and priorities can be set globally or per step to control task assignment and processing order.

Best Practices

  • Design Batch Processes to match business objectives and document lifecycles.
  • Use publishing and versioning to manage changes safely in production environments.
  • Leverage expressions and scripting for flexible, maintainable flow control.
  • Regularly review and test process steps to ensure accuracy and efficiency.

For more information, see the documentation for Batch, Batch Folder, Batch Process Step, and Activity.

Properties

NameTypeDescription
General
Publishing

Design Tabs

General View, edit, and manage the properties and publication status of a Batch Process.
Reports View reports for a node.
Batches Manage and review all batches associated with the selected Batch Process.
Scripting Create, debug, modify, and compile scripts for scriptable nodes.
Advanced View or edit advanced details about a node.

Context Menu Commands

Command Shortcut Description
edit_calendar Add Activity Adds a new Batch Process Step to the Batch Process, configured with a specific Activity.
package_2 Create Project Moves the Batch Process and its exclusively referenced nodes to a new Project.
publish Publish Publishes the working version of a Batch Process, making it available for production use.
disabled_visible Unpublish Unpublishes a Batch Process, making it unavailable for production use in the local Grooper repository.

Child Types

See Also

Used By

Recommended Content

Notification