End-to-end workflow for moving learning instances from IQ Bot to Document Automation
- Updated: 2024/12/03
End-to-end workflow for moving learning instances from IQ Bot to Document Automation
Follow the end-to-end workflow provided in this document to move learning instances from IQ Bot to Document Automation successfully.
The following image shows the workflow of how the learning instances are moved from IQ Bot to Document Automation:
- Stage 1
- Synchronize (sync) the learning instance that you want to move from IQ Bot to Document Automation with the IQ Bot environments so that the learning instance is on the same
version on all environments. You can sync the learning instance from production
(Prod) to test (UAT) environment and then from UAT to development (Dev)
environment.
To sync a learning instance, export the IQBA file from one environment and import the file into the destination IQ Bot environment. See Transferring learning instances between IQ Bot environments.
- Stage 2
-
- After the learning instances are in sync, process a few documents in each of the environments to check if the results are the same in each environment.
- Using the IQ Bot - DA Bridge package,
export the learning instance from the IQ Bot development
environment and import it to the Document Automation
development environment.
After the learning instance is imported, it is available in private mode in Document Automation and is visible only to the user importing the learning instance.
We recommend that you publish the learning instances to public repository as soon as the learning instances are imported to Document Automation so that other users can access the learning instances. The .la file extension is used when learning instances are exported and imported using the IQ Bot – DA Bridge package.
- After moving the learning instance to the Document Automation
development environment, test it by processing a few documents to verify
that the results match those in the IQ Bot environments.
If the results are different, you must troubleshoot the learning instance. Repeat the troubleshooting process until you get the desired results for the learning instance in the Document Automation development environment.
Note:- After moving the learning instance to the Document Automation development environment, you
can enable validation feedback and train the learning
instance by processing new documents.
You might need to process a few documents before you can see improvements based on the validation feedback. See Feedback-based validation for bridged learning instances.
- You will not be able to export or import validation feedback
for bridged learning instances to Document Automation environments.
We recommend that you use validation feedback in specific scenarios. The results of the validation feedback-based improvement can assist in managing new layouts or documents.
When the validation feedback is enabled, the system will continuously learn from the validation feedback provided by users. See Applicable scenarios to use the Bridge package.
- After moving the learning instance to the Document Automation development environment, you
can enable validation feedback and train the learning
instance by processing new documents.
- After you get the desired results in the Document Automation
development environment, move the learning instance to the public mode
so that users can access it to process documents.
Ensure that you move the learning instance to public mode as soon as it is ready for other users to use. Doing so helps avoid any issues: for example, users cannot move the learning instance or view the learning instance in Document Automation. See Publish the learning instance to production.
- Set up permissions for users in Document Automation to use the learning instance. See Document Automation users.
- Build a bot to upload documents to Document Automation and schedule the bot. See Build a bot to upload documents to Document Automation and Schedule a bot.
- Stage 3
- Perform an end-to-end testing of the learning instance to validate the workflow before you proceed with moving the learning instance to the next environment.
- Stage 4
- Repeat the steps provided in Stage 2 to move the learning instance from IQ Bot testing and production environments to Document Automation testing and production environments, respectively.
- Stage 5
- Disable the bot that was used to upload documents in IQ Bot after moving the learning instance.