Image Processing

Specifies the IP Profile that defines the sequence of image processing commands (such as deskew, despeckle, or orientation correction) to be executed on each image.

• The selected profile determines the cleanup and transformation steps applied to each Batch Page or Batch Folder.
• Choose a profile that matches your document quality and processing requirements.

Tip:
Use a profile with only the necessary commands to optimize performance.

• When set to true, a copy of the original image is saved before any processing is applied.
• This allows users to revert changes to the image.
• Undo images increase storage requirements but provide a safety net for permanent operations.

Scenario:
Enable this if you want to allow users to undo image cleanup or if you are testing new IP Profiles.

Can be one of the following types:

• Determines how processed images are compressed and stored.
• If not specified, the default compression settings from the root node are used.
• Choose a compression type (e.g., JPEG, PNG) that balances image quality and file size for your workflow.

Tip:
Use lossless compression for archival or high-accuracy OCR scenarios.

Can be one of the following types:

• When enabled, images are extracted directly from image-based PDF pages and processed as images.
• If changes are made, the PDF page is overwritten with the updated image.
• If disabled, all PDF pages are processed using rendering. If both are disabled, PDF pages are ignored.
• This setting has no effect on non-PDF input pages.

Scenario:
Enable this to preserve original image quality when processing scanned PDFs.

Can be one of the following types:

• When enabled, non-image PDF pages (such as text or vector pages) are rendered to images and processed.
• Only orientation changes are applied to non-image PDF pages; the original content is never overwritten.
• If 'Rendering' is disabled and 'Bursting' is enabled, only image-based PDF pages are processed.
• If both are disabled, PDF pages are ignored.
• This setting has no effect on non-PDF input pages.

Tip:
Enable this if you need to normalize orientation for electronic PDFs or to ensure all pages are processed uniformly.

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.