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

What's new

What's new
Introducing Google Gemini models on AWS and GCP for data extraction in Document Automation

You can use the Google Gemini generative AI models that are available via Amazon Web Services (AWS) and Google Cloud Platform (GCP) for data extraction in Document Automation. This offering provides you the flexibility to select the generative AI model depending on the Cloud provider your company has certified.

Google Gemini provides the following advantages:

  • Efficient processing of large, unstructured documents
  • Handle documents in both English and other languages
  • Handle complex document layouts
  • Faster processing of documents with better data extraction accuracy

Create a learning instance in Document Automation

What's changed

What's new
Enhancements to version history in test mode

The following enhancements are made to the version history in test mode:

  • When you make changes to a learning instance and the version selected in the version history is the latest, you will be allowed to save the changes made to the learning instance.
  • When you make changes to a learning instance and the version selected in the version history is not the latest, you will see an error when you try to save the changes made to the learning instance. Click Go to latest version, make changes to the learning instance again, and then save the changes.
  • The version history drop-down will display all the available versions.

View version history of a learning instance

Fixes

You can now use a custom table name in Japanese, Korean, or Chinese when creating a custom table.

Previously, you were not able to use a custom table name Japanese, Korean, or Chinese.
When you restore a learning instance to any previous version from version history and reprocess a document, the document upload count is not increased.

Previously, the document upload count increased in such a scenario.
You can now add fields to existing Standard Forms projects, create new models, and train the models without any errors.

Previously, an error was displayed in such a scenario.
The Automation Co-Pilot validator now correctly displays a validation error when a required signature field is not found in Standard Forms documents.

Previously, no error was displayed in such a scenario.
When you create a model in Standard Forms, any leading or trailing spaces in table names will automatically be removed.

Previously, an error was displayed when training the model in such a scenario.
Limitations from previous releases
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.
If you copy a learning instance that is using a third-party parser configured in Document Automation and process documents using the copied learning instance, data extraction will fail.
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.

IQ Bot

The IQ Bot On-Premises installer now displays the correct release version in the installation directory.

Previously, the release version displayed in the installation directory was incorrect.