Document Automation v.40 release

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.

Copiez une instance d\'apprentissage dans 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.

Copier des projets dans des Standard Forms | Delete projects in Standard Forms

What's changed

Import and export learning instances using Model connections

When you import or export a learning instance, the Model connection configuration is 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.

Exportation et importation d\'instances d\'apprentissage

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.

Validation des documents via le validateur Automation Co-Pilot

Fixes

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 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
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 vers Document Automation : Plan de transition.

Obsolescences de fonctionnalités terminées