Grooper Help - Version 25.0
25.0.0017 2,127
  • Overview
  • Help Status

Route Definition

Embedded Object Grooper.Activities

Defines a routing rule that links a Content Type to a Batch Process.

Remarks

A Route Definition enables flexible, criteria-based routing of documents into distinct workflows within Grooper.

Overview

A Route Definition determines how documents of a specific Content Type (or unclassified documents) are dispatched into a downstream Batch Process.
Each route can be configured with conditions, data transformation logic, and options for how documents are moved or cloned.

How Routing Works

  • Routes are evaluated in order. Only the first matching route is applied to each document during the Route activity.
  • Each route can target a specific Content Type or apply to documents without a classification.
  • The route specifies the destination Batch Process and can assign a new Content Type to the routed document.
  • Optional conditions can be set using a boolean 'Trigger' expression, allowing for advanced, rule-based routing.
  • Documents can be either moved or cloned into the target batch. Cloning retains the original document for audit or parallel processing.
  • Routed batches can be started in a paused state for review or configuration before processing begins.

Data Transformation

  • When converting between Content Types, a set of Data Actions can be defined to map, copy, or transform data fields as part of the routing process.
  • This supports scenarios where the source and target Content Types have different data models or require normalization.

Example Scenarios

  • Exception Handling: Route unclassified or exception documents to a dedicated Batch Process for manual review.
  • Workflow Segmentation: Send invoices and contracts to different Batch Processes based on their Content Type.
  • Data Normalization: Assign a new Content Type and apply Data Actions to standardize data before export or further processing.

Configuration Tips

  • Place more specific routes before general ones to ensure correct matching.
  • Use the 'Clone' option to retain originals when parallel workflows or audit trails are required.
  • Use the 'StartPaused' option to allow for human review or additional configuration before processing.

Properties

NameTypeDescription
General
Options

See Also

Used By

Notification