Deduplicate

Can be one of the following values:

The 'Compare By' property determines how documents are evaluated for similarity. Choose between text-based comparison, which considers the textual content of documents, and data-based comparison, which requires exact matches of extracted data values.

• When set to Text, documents are considered duplicates if their text content is sufficiently similar, as determined by the 'Minimum Similarity' property.
• When set to Data, documents are considered duplicates only if all extracted data values match exactly.

Select the mode that best matches your document processing scenario. For example, use Text for unstructured documents and Data for structured forms.

This property sets the threshold for text-based duplicate detection. The value should be between 0 and 1, where 1 requires documents to be identical and lower values allow for more variation. For example, a value of 0.95 means documents must be at least 95% similar to be considered duplicates.

This property is only used when 'Compare By' is set to Text. Adjust this value to control the strictness of duplicate detection. Lowering the threshold may result in more documents being grouped as duplicates, while raising it will require closer matches.

Can be one of the following values:

The 'Disposition' property controls what happens to each group of detected duplicates. Options include moving duplicates to a new folder, deleting them, flagging them for review, stacking them together, or appending their children to the first copy.

Choose the disposition that best fits your workflow. For example, use Move to organize duplicates into a separate folder, Delete to remove them, or Flag to mark them for manual review.

When 'Disposition' is set to Move, this property determines the Content Type assigned to the new folder that will contain the duplicate documents. Select a content type that is appropriate for the group of duplicates being created.

This property is only relevant when using the Move disposition. If not set, the default content type will be used.

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.