Document Automation and IQ Bot v.33 release

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

Document Automation

What's new
Introducing Anthropic models on Amazon Web Services and Google Cloud Platform for data extraction in Document Automation

You can now use the Anthropic models available on AWS and 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.

Anthropic provides the following advantages:

  • Processes large unstructured documents well.
  • Processes both English and non-English documents.
  • Processes documents much faster with better data extraction accuracy.
  • Allows you to use your own license using the bring your own license (BYOL) model.
    注: OEM license will be enabled in a future release.

Create a learning instance in Document Automation | [データの抽出] action

Process unstructured documents in more languages

You can now process unstructured documents that include content in the following languages: Afrikaans, Albanian, Catalan, Chinese, Croatian, Czech, Danish, Dutch, Estonian, Finnish, French, German, Hungarian, Icelandic, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Malay, Norwegian, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish, Swedish, Tagalog, Turkish, and Vietnamese.

Language support matrix and OCR engines

Process standard forms in more languages

You can now process standard forms that include content in the following languages: Afrikaans, Albanian, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Estonian, Finnish, Hungarian, Icelandic, Indonesian, Malay, Norwegian, Polish, Portuguese, Romanian, Russian, Slovak, Slovenian, Swedish, Tagalog.

Language support matrix and OCR engines

What's changed
Improved advanced training settings in validator

When you provide validation feedback for the Primary Column and the End of table indicator fields, the validation feedback is now improved to automatically populate these values when you process documents of similar type even when the end of table indicator is at random locations.

You can clear the automatically updated values:

  • Primary column field: Click the drop-down menu and select the empty value from the drop-down menu.
  • End of table indicator field: Click the close button next to the value in the end of table indicator field or click the close button on the selection box of the value on the document.

Improve table data extraction

Fixes
You can now process documents in Document Automation using a migrated classic IQ Bot learning instance when the learning instance was created using check box.

Previously, data extraction failed in such a scenario.

When a user clicks the Language field during parser configuration, the languages are now displayed in the correct order.

Previously, the languages were not displayed in the correct order in such a scenario.

You can now provide a shared network path as the output path for the Advanced Classifier actions and successfully execute bots using these actions.

Previously, an error was displayed in such a scenario.

Service Cloud Case ID: 02085363

When you validate documents, you will no longer see an error when you navigate from the Detail view to the Table view.

Previously, an error was displayed in such a scenario.

When a user processes a document on a custom process learning instance and submits the document, the Validate documents count for the instance is updated correctly.

Previously, the count was not updated when the document was processed, and a negative count was displayed when the document was submitted.

You can now view the Google Document AI provider icon when you use the Receipts and Utility Bill document types.

Previously, the provider icon was not displayed in such a scenario.

You can now process documents that contain decimal numbers (such as .78, .99) for the number data type in the validator.

Previously, an error was displayed in such a scenario.

Limitations
You will see the Document Automation details page and license consumption (pages) for a learning instance when you perform the following actions:
Scenario 1
  1. Connect a learning instance from IQ Bot to Document Automation.
  2. Delete the learning instance.
  3. Migrate the learning instance from IQ Bot to Document Automation using the IQ Bot - DA Bridge package.
  4. Delete the learning instance.
  5. Connect the learning instance to Document Automation.
Scenario 2
  1. Migrate a learning instance from IQ Bot to Document Automation using the IQ Bot - DA Bridge package.
  2. Delete the learning instance.
  3. Connect the learning instance to Document Automation.
Data extraction fails in imported learning instances that are using a generative AI provider and are configured for the output format to be in JSON.

Workaround: Change the output format to CSV.

When you are using the IQ Bot Pre-processor package actions and if the Input file path and Output folder path contains Japanese characters, you will see an error when processing documents.
Workaround:
  • Place the documents to be processed in a folder path that does not contain any Japanese characters and provide the path in the input file path field.
  • 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.
Limitations from previous releases
No error message is displayed to an user when the IQ Bot learning instance has already been bridged by another user.
For a public process, you might encounter an error message in the following scenarios:
  • After validating all the documents in the validation queue.
  • After processing some documents with same learning instance, if you open the first document and click Refresh.
注: No error message is displayed for the private process.

IQ Bot

Fixes
When using IQ Bot for extracting large amounts of data that cannot be stored on your local (browser) storage, you will no longer see the “Something went wrong” error when validating documents.

Previously, you were seeing this error in certain scenarios.

Service Cloud Case ID: 02094667

Updates to the interface

IQ Bot and Document Automation