Convert Data

This property determines which documents are eligible for conversion by matching their Content Type.

• Only Batch Folders with this type will be processed.
• The associated Data Model defines the data elements available for extraction and mapping.

Tip:
Set this to the Content Type that matches the structure of your incoming documents.

This property defines the target structure for the converted data.

• The Data Model of this type determines the fields and layout of the output.
• Data is mapped and transformed from the source to this target type using the 'Actions' collection.

Tip:
Use a Content Type that matches your export or downstream requirements.

This collection defines the logic for how data is transferred and transformed during conversion.

• Each Data Action can copy, calculate, or manipulate data fields.
• Actions are executed in order and can be nested for complex scenarios.

Tip:
Use Set Field Value actions for calculations, and Copy Base for hierarchical or grouped operations.

• If set to true, the Extract activity is run before conversion to ensure the latest data is available.
• If set to false, it is assumed that extraction has already been performed and saved.

Scenario:
Enable this if documents may not have up-to-date extraction results.

Use preprocessing rules to clean, validate, or normalize data before it is mapped to the target type.

• Rules can perform calculations, enforce business logic, or prepare data for conversion.
• Applied after extraction (if enabled) and before the main conversion actions.

Tip:
Use this to ensure data quality or to apply corrections before conversion.

• If set to true, any modifications made by preprocessing rules are persisted to the source document.
• If set to false, changes are only used for the current conversion and are not saved.

Scenario:
Enable this if you want to retain data corrections or normalizations for future processing steps.

Use postprocessing rules to finalize, validate, or further transform data after it has been mapped to the target type.

• Rules can enforce business requirements, perform calculations, or clean up data.
• Applied after all conversion actions and before the document is saved.

Tip:
Use this to ensure the output meets export or reporting standards.

Can be one of the following values:

The SaveDisposition enum controls how the result of the conversion is stored:

• : The converted data becomes the primary Content Type for the document. The previous primary type is demoted to secondary.
• : The converted data is added as a secondary Content Type, preserving the original as primary.
• : The converted data is saved as a new child Batch Folder under the original document.
• : The source Content Type is replaced with the target type, removing the original assignment.

Usage Scenarios:

• Use Primary when the converted data should be the main representation for downstream processing or export.
• Use Secondary to support multi-type documents or for audit trails.
• Use Child to create document branches or to preserve both original and converted versions in a parent-child relationship.
• Use Replacement for full migration to a new type, discarding the original type assignment.

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.