Skip to main content

Submit Image

Submits an additional image to an existing ABBYY Cloud processing task.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.

Inputs​

  • Image Path - Path to the image file to submit to the existing task.
  • Task ID - ID of the existing ABBYY task to add the image to.

Options​

  • PDF Password - Password for encrypted PDF files if applicable.

Outputs​

  • Task - Updated ABBYY task object with the new image added.

How It Works​

The Submit Image node adds additional images to an existing ABBYY processing task. When executed, the node:

  1. Reads the image file from the specified path
  2. Retrieves the existing task using the task ID
  3. Uploads the new image to the task
  4. Updates the task with the additional image
  5. Returns the updated task object

Requirements​

  • Valid ABBYY Cloud credentials
  • Valid existing task ID from a previous Process Image call
  • Valid image file at the specified path

Error Handling​

The node will return specific errors in the following cases:

  • Robomotion.ABBYYCloud.ErrImagePath - Image path is invalid or file not found
  • Robomotion.ABBYYCloud.ErrImageData - Cannot read image file data
  • Robomotion.ABBYYCloud.ErrTaskID - Task ID is invalid or empty
  • Robomotion.ABBYYCloud.ErrPDFPassword - Invalid or incorrect PDF password

Usage Example​

Scenario: Process a multi-page document

1. Process Image node (first page):
   - Image Path: "C:/docs/page_001.jpg"
   - Language: English
   - Export Format: pdfSearchable
   - Output: {{ $.task }}

2. Submit Image node (page 2):
   - Image Path: "C:/docs/page_002.jpg"
   - Task ID: {{ $.task.id }}

3. Submit Image node (page 3):
   - Image Path: "C:/docs/page_003.jpg"
   - Task ID: {{ $.task.id }}

4. Process Document node:
   - Task ID: {{ $.task.id }}
   - (Configure processing options)

5. Wait Task node:
   - Task: {{ $.task }}
   - Timeout: 120 seconds

Common Use Cases​

  • Multi-Page Documents - Combine multiple page images into one document
  • Document Assembly - Build documents from separate image files
  • Batch Scanning - Add sequentially scanned pages to a task
  • Front-Back Processing - Combine front and back sides of documents
  • Book Digitization - Process book pages into a single document
  • Mixed Document Sources - Combine pages from different sources

Tips and Best Practices​

  • Page Order:
    • Submit pages in the correct sequential order
    • First page comes from Process Image node
    • Additional pages via Submit Image nodes
    • Final page count affects Processing Document timing
  • Task Management:
    • Store task ID from initial Process Image
    • Reuse same task ID for all pages
    • Don't process until all pages are submitted
    • Use Process Document after all submissions
  • Image Consistency:
    • Use same resolution for all pages
    • Maintain consistent orientation
    • Match color depth and format
    • Similar image quality across pages
  • Error Handling:
    • Enable Continue On Error for robust batch processing
    • Track which pages were submitted successfully
    • Retry failed submissions before final processing
    • Validate page count before processing
  • Performance:
    • Submit pages sequentially (one after another)
    • Don't wait between submissions
    • All uploads should complete before Process Document
    • Larger page counts increase processing time
  • PDF Handling:
    • Can submit encrypted PDFs with password
    • Multi-page PDFs are split automatically
    • Consider PDF page count in timeout settings
  • Memory Management:
    • Don't keep too many tasks open simultaneously
    • Delete completed tasks to free resources
    • Monitor task quota on ABBYY Cloud account
  • Workflow Patterns:
    • Loop pattern: Submit Image in a loop for multiple files
    • Sequential: Individual Submit Image nodes for known page count
    • Dynamic: Adjust workflow based on actual page count
  • Validation:
    • Verify task ID is valid before submission
    • Check file exists before submitting
    • Confirm upload success before next page
    • Count submitted pages matches expected