Extract

Can be one of the following values:

Select the extraction mode to determine how existing data is handled:

• Normal: Overwrites all existing extracted data with new results.
• Additive: Only extracts data for new or empty fields, preserving existing values. Useful when adding new fields to a Data Model.
• Recalculate: Recalculates all calculated fields and re-validates data, ensuring all values are current.

> Tip: Use 'Additive' mode to avoid overwriting user-entered or previously extracted values.

Assigns a Content Type to folders that do not already have one before extraction begins.

• Ensures extraction can proceed even if classification has not been performed or failed.
• Set this property to guarantee all folders are processed with a specific Content Type, or as a fallback.
• If not set and a folder is unclassified, extraction will throw an exception.

> Example:
> Set 'Default Content Type' to "Invoice" to ensure all unclassified folders are extracted as invoices.

Restricts extraction to only the specified Content Types and their descendants.

• When empty, extraction is performed for all assigned Content Types.
• When set, only documents of (or inheriting from) the specified types are processed.

> Example:
> Add "Invoice" and "Purchase Order" to extract data only from those document types.

Restricts extraction to only the specified Data Elements.

• When empty, all data elements are extracted and existing values are overwritten.
• When set, only the listed Data Elements are extracted; all others retain their previous values.

> Example:
> Use this to extract only "Invoice Number" and "Total Amount" fields, leaving all other data unchanged.

Specifies a set of Data Rules to be executed after extraction.

• Use Data Rules for post-processing tasks such as normalization, transformation, or additional validation.
• Only rules that apply to the current Content Type are executed, in the order specified.
• Enables enforcement of custom business logic, data cleanup, and quality checks before saving or exporting results.

> Tip: Use Data Rules to standardize phone numbers, validate totals, or perform other business-specific logic.

Enable this option to automatically flag folders when extracted data fails validation.

• Useful for identifying documents that require review or correction.
• Flags are visible in the batch tree and can be used to route items for further processing.

> Example:
> Enable to flag invoices missing required fields or containing invalid values.

Removes all alternate value candidates for each field, retaining only the selected value.

• Use this to reduce file size and simplify data for export or downstream processing.
• Alternate candidates are typically generated by extractors that return multiple possible values.

> Tip: Enable when only the final, selected value is needed for export or reporting.

Removes all fields that are empty (blank and without a location) from the extracted data before saving.

• Use this to reduce clutter and file size, especially when exporting or archiving data.
• Only fields with no value and no location are removed; fields with extracted values are retained.

> Example:
> Enable to keep only populated fields in the exported data for each document.

Can be one of the following values:

Controls the level of extraction statistics recorded for each document.

• None: No statistics are logged.

• Normal: Summary statistics (such as fields extracted, fields with value, and errors) are logged.

• Use statistics for monitoring, reporting, or troubleshooting extraction results.

> Tip: Enable statistics logging to track extraction quality and identify problem areas in your data.

A combination of the following flags:

The Error Disposition property determines the system's response to errors that occur while executing the activity.

• Flag: The affected Batch Folder or Batch Page will be flagged for review.
• Log: The error will be written to the Grooper event log.
• Stop: Processing will halt, the Batch will be set to an error state, and all pending tasks will be deleted.

You can combine multiple options using the IssueDisposition flags.
Adjust this property to match your organization's error handling and escalation policies.

If the number of consecutive errors reaches this value, a critical stop will occur and the Activity Processing service will halt further processing.

• Use this property to prevent runaway failures and to ensure that persistent errors are escalated for review.
• Set to a higher value to allow more retries before stopping, or to a lower value for stricter error control.

Can be one of the following values:

The Concurrency Mode property determines whether the activity can be executed in parallel across multiple Batch Objects, or if it must run sequentially.

• This setting affects which Processing Queue the activity is submitted to and how tasks are distributed.
• Choose the appropriate mode based on the activity's thread safety and resource requirements.