Document Automation v.42 release - Review what's changed, and the fixes and limitations in Document Automation for the v.42 release.

Automation 360

Review what's changed, and the fixes and limitations in Document Automation for the v.42 release.

What's changed

Automatically correct image orientation in IQ Bot Pre-processor

When you use the Orient image action in the IQ Bot Pre-processor package, you now have the option to automatically correct the image orientation using the Auto option in the Rotate setting. When you select this option, the Angle field is hidden because the model calculates rotation automatically. This option corrects orientation only at 0°, 90°, 180°, and 270°.

Using Orient Image action

Fixes

You can now select a custom model that you created before updating to this release when you configure a learning instance.

Previously, you were unable to select such custom models in such a scenario.

Service Cloud Case ID: 02332382, 02331481
The CSV files generated by a learning instance that was moved from IQ Bot to Document Automation use correct character encoding.

Previously, the CSV files used a different character encoding in such a scenario.

Service Cloud Case ID: 02223005
Document Automation now displays the correct error message when the External connections option is disabled.

Previously, an incorrect message was displayed in such a scenario.

Standard Forms now works correctly for existing bring-your-own-key (BYOK) configurations.

Previously, license validation failed in such a scenario.
You can now successfully process a document when automation uses Document Classifier and IQ Bot Pre-processor actions along with the Document Extraction Extract Data action.

Previously, document processing failed in such a scenario.

You can now successfully delete a parser created in Document Automation.

Previously, users were not able to delete parsers.

You can now create Standard Forms models when your license includes Document Automation Credits only.
When documents are processed using Cloud Extraction Service, the default validator now correctly displays the user-defined Adaptive Search Queries when user-defined queries are used for actual extraction.

Previously, the default validator displayed default queries in such a scenario.
The following fixes are included when you download accuracy data in document evaluations:
  • When you download accuracy report data for a version of the document that does not contain extraction results, the download will no longer fail.
  • When you download accuracy report data for multiple documents and if extraction results are not available for one or more documents, the output will no longer contain incomplete data.
  • When you download accuracy report data for multiple documents, the output report will no longer include an incorrect accuracy report header.
If a learning instance was using Pandas, oracledb, or Pillow Python scripts for data extraction in IQ Bot and you moved the learning instance to Document Automation using the IQ Bot - DA Bridge package, the Python scripts are now considered for data extraction when you process documents in Document Automation.

Previously, the Python scripts were not considered for data extraction in such a scenario.
When you use actions in the IQ Bot - DA Bridge package, the icons for the actions are now displayed correctly in the Task Bot editor.

Limitations

When you use the Classify Document action with a classification model that was trained using a legacy version of the Train Classifier action, and you have updated to the Document Classifier package version 42.0.3 or later, the action fails with an ABBYY engine exception.
Workaround:
  • Use the Document Classifier package version 3.37.4 or earlier with the existing classification model.
  • Use the Train Classifier action in the Document Classifier package version 42.0.3 or later to train the model and then use the model in the Classify Document action.
When the form field accuracy for a document is unavailable and shown as NA or --, the overall form field accuracy score is still calculated and displayed as a percentage instead of showing as --.
When a document does not contain any form fields, document evaluation calculates and displays the accuracy for such form fields as 0 percent instead of marking it unavailable. This value is also included in the overall document accuracy calculation, which produces an incorrect score for the document.
When you process a Dutch invoice or document using the Google Document AI provider, the extracted price value includes only the numeric value and does not include the Euro (€) currency symbol.
When you use the Orient image action in the IQ Bot Pre-processor package to rotate a JPEG image at a non-standard angle (for example, 30°, 45°, 60°, 120° instead of the standard 0°, 90°, 180°, or 270°), the output image is visually distorted. The content in the image appears stretched, dragged, or skewed, and the original aspect ratio and image layout are not preserved.
Limitations from previous releases
When you download accuracy report data for multiple documents, and if extraction results are not available for one or more documents, the output might contain incomplete data.

Workaround: Download ground truth documents only for the learning instance version that contains extraction results for the selected documents.
Data extraction might fail with the following error while using the Cloud Extraction Service: INVALID_ARGUMENT: Invalid UUID string.

Workaround: Use an input form instead of process-level input variables to pass the required inputs to the learning instance process.
The following limitations are applicable to Model connections:
  • Model connections using the Automation Anywhere vendor is not supported.

    Workaround: Use the built-in generative AI providers when creating learning instances.

  • In Model connections, the Fine-tuned and Grounded model types are not yet supported.

    Workaround: Use the Standard model type.
When you try to check in a process without having the required permissions, the audit log entry for this event will include Source as Control Room instead of Document Workspace and Item name as Unknown instead of <learning-instance-name>.
When you use a regular expression for a table field without defining an alias, the regular expression might not be considered for extracting the data.

Workaround: Define an alias for the table field before using a regular expression.
When you process documents containing multiple tables in Standard Forms, the order of the tables extracted is reversed.
Document extraction will fail with the error “500: Internal Failure , Failed to initialize ABBYY’ when you change the default path (C:/ProgramData/AutomationAnywhere/GlobalCache) of Global Cache Location for your devices.
When you process documents with file names greater than or equal to 75 characters in test mode, you might not see improvements in the reprocessing time for such documents.
If you have disabled the OCR provider in the administrator settings and if you are using a language other than English for your Control Room, you will see an error to enable the OCR provider settings in English in the following scenarios:
  • When you create a learning instance that is using an OCR provider
  • When you change the OCR provider for an existing learning instance
When you use the Document Classifier actions (Classify, Classify documents, and Train Classifier) and Extract Data action in the Document Extraction package together in a bot, the bot will fail to execute.

Workaround: Ensure that you create separate bots when using any of the actions from the Document Classifier package and the Extract Data action of the Document Extraction package. If you need to execute these bots in a sequence, include these bots in an Automation Co-Pilot process.
When a user processes a document on a custom process learning instance, the validate document count is not updated post extraction. Also, if the user submits the document, the validate document count is updated with a negative value.
A user with the Automation Co-Pilot administrator permissions is unable to view the Document Automation tasks that are assigned or requested and are in pending or complete status.
When you are using the IQ Bot Pre-processor package actions and if the Output folder path contains Japanese characters, you will see an error when processing documents.

Workaround: Create an output folder in a folder path that does not contain any Japanese characters and provide the path in the output folder path field.