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

What's new

Update extraction models in Standard Forms learning instances

You can now change the extraction model for an existing learning instance by copying the learning instance and changing it to the required extraction model. To use a different extraction model, you no longer need to create a new learning instance and manually recreate configurations such as field mappings and validation rules.

Copy a learning instance in Standard Forms
Copy or delete projects in Standard Forms
You can now copy or delete projects when using Standard Forms.
  • Copy a project when you want to preserve the configuration of an existing project. You can use the copied project to update and test the project without affecting the original project.
  • Delete redundant or unused projects.

Copy projects in Standard Forms | Delete projects in Standard Forms
Support for Japanese and Korean languages

You can now process documents in Japanese and Korean languages using the User-defined document type with ABBYY and Google Vision OCR engines.

Note: As these languages use generative AI for data extraction, validation feedback will not be used.

Languages supported in Document Automation

What's changed

Adaptive Search Queries available with and without test mode

You can now use Adaptive Search Queries in learning instances that have the test mode option disabled. Previously, you were only able to use Adaptive Search Queries in learning instances where the test mode option was enabled.

The Adaptive search query option will be available for the processed documents in the following scenarios:

  • With the test mode option enabled for a learning instance, open the learning instance, and use the Process option to process documents.
  • With the test mode option disabled for a learning instance, use the Process action on the Learning Instances page to process documents.

Adaptive Search Queries
Import and export learning instances using Model connections

When you import or export a learning instance, references to the Model connection such as the Model connection name, vendor, and model names will be included in the learning instance. When you import a learning instance that was using a Model connection, the Include the Generative AI Model connection option is introduced on the Import Learning Instances page to review the Model connection option before importing the learning instance.

Export and import learning instances
Enhanced zoom controls when validating documents

Users validating documents can now zoom in on documents up to 500 percent and select specific zoom levels. Users can also continue to use the zoom in and zoom out controls, and the selected zoom level is reflected in the drop-down option.

Validating documents through Automation Co-Pilot validator
Keyboard shortcuts for navigating validation errors

You can now use keyboard shortcuts in the validator to quickly navigate between fields that contain errors or warnings. Select Shift+Enter to move to the next error or warning field and Ctrl+Enter to move to the previous error or warning field. This enhancement helps validators review and correct large documents and table-based data more efficiently without manually locating validation issues. The shortcuts automatically expand collapsed sections when the next error field is inside a collapsed table or form section.

Validating documents through Automation Co-Pilot validator
Only Task bot option supported when copying learning instances

When you copy learning instances, only the Task bot option for processing documents will be available.

Copy a learning instance in Document Automation

Fixes

When you import a learning instance that includes bots or processes that already exist in the Control Room, the audit log will not correctly indicate that it was imported.

Previously, the audit log indicated that the learning instance was edited in such a scenario.

Service Cloud Case ID: 02279026
Validation feedback is now correctly applied when field rules with actions such as Set Value, Replace, and Regex Extract are applied.

Previously, validation feedback was not applied in such a scenario.

Service Cloud Case ID: 02274135
Data extraction will no longer fail when you copy a learning instance that is using a third-party parser configured in Document Automation and process documents using the copied learning instance.

Previously, data extraction failed in such a scenario.
In the Advanced training settings option, the table fields that are not selected for validation feedback are no longer displayed in the Primary Column drop-down.

Previously, such table fields were displayed in the Primary Column drop-down in certain scenarios.
You will no longer be able to view Model connections when editing a learning instance in Cloud deployments.

Previously, you were able to set the Model connections in such scenarios.
When you create a document rule in Standard Forms and update the Data type field for a different field, the existing document rules no longer reset.

Previously, existing documents were reset in such a scenario.
The Extract Data action now displays the complete list of learning instances when used in automation.

Previously, the complete list was not displayed in such a scenario.

Service Cloud Case ID: 02281644
You can now enable test mode for learning instances created in v.35 or earlier releases that are in the public workspace.

Previously, you were not able to enable test mode in such a scenario.
The alignment of IF and THEN conditions in field rules is now displayed correctly.

Previously, these conditions were misaligned.
Correct label is displayed for the Confidence option when the Control Room is set to a language other than English.

Previously, the label was incorrectly displayed in certain languages.
In the Advanced training settings option, the table fields that are not selected for validation feedback are no longer displayed in the Primary Column drop-down.

Previously, such table fields were displayed in the Primary Column drop-down in certain scenarios.
Data extraction will no longer fail when you copy a learning instance that is using a third-party parser configured in Document Automation and process documents using the copied learning instance.

Previously, data extraction failed in such a scenario.
When creating or editing a learning instance, field properties are now retained after changing the data type before entering a label for a field.

Previously, changing the data type reset all configured field properties.

Limitations

When you process a document using a learning instance that is using a generative AI provider and the Adaptive Search Queries feature, the validator displays the correct generative AI model. However, when you change the generative AI provider and check the validator without processing any documents, the generative AI provider will display the updated generative AI provider instead of the previous generative AI provider used for processing the document.
When you create and process a document using a learning instance in the private repository, move the associated process to the public repository, and then submit the document from the validator, the Download data automation will fail.
Limitations from previous releases
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.

  • Custom models do not support vision-powered generative AI data extraction even when using OpenAPI schema.

    Workaround: Use the built-in models for vision-powered generative AI data extraction.
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 edit and check in a process linked to a public learning instance that is using Cloud Extraction Service, the extraction bot might not be visible in dependencies, and document processing might fail.
Workaround: Use one of the following options:
  • Update to the v.39 release
  • Use the default process or copy the learning instance to create a new process and then publish the learning instance before processing documents
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.

Completed deprecations

IQ Bot Cloud is deprecated

IQ Bot Cloud is deprecated as of March 2026. We recommend that customers evaluate the transition plan for moving from IQ Bot Cloud to Document Automation. See IQ Bot to Document Automation: Transition plan.

Completed feature deprecations