Content Type - Submit Job

Can be one of the following types:

Select the Code Activity that will be executed for each document included in the submitted Processing Job. The chosen activity defines the automated processing logic—such as extraction, validation, or transformation—applied to each item.

Only activities compatible with the selected 'ProcessingScope' are available for selection.
Changing the activity may update the allowed processing scopes automatically.

Example:
Assign an 'Extract' activity to perform data extraction on all documents of this Content Type.

Can be one of the following values:

Determines the batch object level at which Processing Tasks are created for the job.

• Folder: Tasks are submitted for each folder (typically representing a document).
• Page: Tasks are submitted for each page within the selected documents.
• None: No tasks are submitted (used when no valid scope is available).

The available options are filtered based on the selected 'Activity' and its allowed scopes.

Considerations:
Choose a scope that matches the granularity of processing required by the Code Activity. For example, use 'Page' for page-level OCR or 'Folder' for document-level extraction.

Controls the depth in the batch hierarchy where Processing Tasks are created:

• 0: Tasks are submitted for the documents in the result set.
• 1: Tasks are submitted for the immediate children of those documents.
• -1: Tasks are submitted for the parent folders (ancestors) of the result set items.

Use positive values to target child levels, or negative values to target ancestor folders.
This property enables flexible targeting of documents or folders for processing, supporting advanced workflows such as processing parent folders or sub-documents.

Example:
To process all pages within each document, set 'ProcessingScope' to Page and 'Level' to 1.

Sets the processing priority for all tasks in the submitted job.
Lower values are processed first, allowing you to expedite urgent work or delay less critical tasks.

Usage Guidance:

• Use a lower value (e.g., 1) for high-priority jobs.
• Use a higher value for background or non-urgent processing.

Adjusting priority helps manage workload and ensures that critical documents are processed promptly.

Select the Processing Queue (also known as ThreadPool) that will execute the submitted tasks. The queue determines which servers or services process the tasks, as well as concurrency and throughput limits.

Configuration Tips:

• Assign a queue optimized for the type of activity (e.g., a dedicated OCR queue for recognition tasks).
• Use different queues to balance load or restrict processing to specific machines.

If no queue is specified, the default Processing Queue is used.

Specifies how many Processing Tasks are grouped together in each submitted Processing Job.

• Use a smaller value to create more, smaller jobs (useful for load balancing or rapid feedback).
• Use a larger value to reduce overhead and submit fewer, larger jobs.

Default: 5000 tasks per job.

Example:
If there are 12,000 documents to process and 'JobSize' is set to 5,000, three jobs will be created: two with 5,000 tasks and one with 2,000 tasks.