Review the fixes and limitations in Document Automation for the v.35 release.

Fixes

The timestamps on the Automation Co-Pilot validation page for Document Automation requests are now displayed in the United States time zone for US regions.

Previously, the timestamps were displayed in India Standard Time (IST) is such a scenario.

Service Cloud Case ID: 02163222, 02169928
You can now create Standard Forms models using the Create model option.

Previously, an error was displayed in such a scenario.

Service Cloud Case ID: 02183308, 02183117, 02183140, 02183600, 02183599, 02181980, 02184271, 02185356, 02185132, 02185698, 02187380, 02186484, 02185805, 02186522
You will be able to access the AI > Document Automation (previously, Manage > Learning Instances ) menu to access learning instances when you have the appropriate Document Automation license.

Service Cloud Case ID: 02154136
The number of documents queued for validation is now correctly displayed in the Validate documents option on the Learning Instances page.

Previously, incorrect numbers were displayed in certain scenarios.

Service Cloud Case ID: 02105956, 02110441, 02144450, 02159638, 02143898, 02147184
We have enhanced the data extraction process when accessing storage services by retrying file download when it failed due to storage issues.

Previously, a storage-related error was displayed in certain scenarios.

Service Cloud Case ID: 02141163, 02132605
When you create a parser configuration, a default version is automatically selected when you upload a package.

Previously, you had to manually select the package version in such a scenario.
You can move a learning instance only once to Document Automation using the IQ Bot - DA Bridge package. You will see an error that includes the user ID of the user who has already moved the learning instance to Document Automation if you try to move the same learning instance to Document Automation again.

Previously, multiple users were able to move a learning instance to Document Automation.
When you add an effect to the Enhance image action of the IQ Bot Pre-processor package, the name of the effect type is displayed correctly.

Previously, the effect type was displayed as ENHANCEMENT TYPE.
You can now copy and import learning instances that are using document rules containing multiple group conditions.

Previously, such learning instances failed to copy.

Service Cloud Case ID: 02147445, 02164264

Limitations

When you configure bring your own key (BYOK) that is to be used in the Extract data action, some titles used in the Additional settings option are displayed in English and might not be translated in the languages selected in your Control Room.
You will not be able to edit document rules in a learning instance if the number of document rules used in the learning instance exceeds 19 and if a field rule contains check box field.

Service Cloud Case ID: 02173183, 02180260, 02184419
After creating a Standard Forms model and uploading PDF documents to train the model, PDF documents are not loaded to define tags.
When you update from a previous release to the v.35 release, the name of the effect type in the Enhance image action of the IQ Bot Pre-processor package is displayed as a dash ( - ).

Workaround: Edit the effect and select the effect again to display the effect type correctly.
Limitations from previous releases
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 user processes a document on 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 the 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 set all the table fields in a learning instance to optional and if any documents processed using this learning instance are sent for validation, the validator will not display an option to add a row for the table fields.

Workaround: Set at least one of the table fields to required or delete the empty row from the table to see the Add row button.
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.
Note: No error message is displayed for the private process.
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

Connect Learning Instances from IQ Bot option deprecated

The Connect Learning Instances from IQ Bot option will no longer be available in Document Automation as of January 2025. We recommend that such customers use the IQ Bot - Document Automation Bridge package to use the IQ Bot learning instances in Document Automation.

Completed feature deprecations
CyberArk vault integration in IQ Bot On-Premises deprecated

CyberArk vault will no longer be supported in IQ Bot On-Premises deployment as of December 2024. We recommend that customers who need to continue to use CyberArk vault integration to switch to Document Automation On-Premises deployment.

Completed feature deprecations