DI Analyze

Select the Azure model used to analyze document pages. The model determines the types of layout, text, and semantic elements extracted. Common choices include prebuilt models for general documents or custom models for specialized layouts. Changing the model may affect the accuracy and detail of extracted results.

Can be one of the following types:

Set the language code for OCR extraction (e.g., en for English, es for Spanish). If left blank, multi-language OCR is enabled. Azure does not auto-detect document language. For best results, run the Detect Language activity after extraction to assign the correct culture code.

A combination of the following flags:

Choose additional Azure features to include in the analysis, such as handwriting recognition, table extraction, or style detection. Enabling more features may increase processing time and result detail.

Can be one of the following values:

Select the content format (e.g., PDF, TIFF, JPEG) used for document analysis. The format affects how pages are merged and processed. For folders with mixed formats, choose the format that best matches your document set.

Enable this option to replace previous analysis results with new output. If disabled, existing results are preserved and the activity will skip processing for pages that already have results.

When enabled, the activity will analyze the folder's attachment (PDF, TIFF, JPEG) if available, rather than merging and analyzing individual child pages. This is useful for documents where the attachment is the preferred source for extraction.

The results of the Azure analysis are saved to each page as a JSON file. The file name is generated based on the selected model, following the pattern AzureDI_{ModelName}.json. This allows you to easily locate and review the output for each page.

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.