About the Automation Co-Pilot process in Document Automation

Document Automation uses Automation Co-Pilot for Business Users technology to manage the end-to-end document extraction process. When you create a learning instance in Document Automation, the system also creates an Automation Co-Pilot process. Review the following guide to understand the logic.

When a learning instance is in production, each incoming document creates a new request, which triggers the extraction process. If a document requires manual validation, Automation Co-Pilot creates a validation task and assigns it to a validation team.

After the documents are processed, the Download bot downloads the extracted data to a file in the Success folder.

The AARI process manages the bots associated with a learning instance

Start: The Automation Co-Pilot form that defines the inputs, such as the learning instance name, uploaded documents, and output folder.
Bot Task ExtractionBot: Executes the RPA bot that processes incoming documents to extract data from them.
Document Validator Task: Opens the Validation user interface where the user can manually validate the fields in the document.
Documents require validation: The ExtractionBot tried to process the documents then sent the documents for validation, the documents were successfully validated, and the DownloadBot downloaded the extracted data to the Success subfolder.
Request status = VALIDATION_SUCCESS
Invalid documents: The previous process was interrupted at validation, where a user marked certain documents as invalid. These documents were downloaded to the Invalid subfolder.
Request status = VALIDATION_INVALID
Reprocessed documents: The previous process was interrupted at validation because the user clicked Reprocess. Documents were sent back to the ExtractionBot for reprocessing.
Request status = VALIDATION_REPROCESSING
Documents are successfully processed: The ExtractionBot successfully processed the documents, no documents required validation, and the DownloadBot downloaded the exacted data.
Request status = success and STP
Processing failed: The ExtractionBot failed to process the documents (for example: invalid format or could not read the file) and the file is saved to the Failed subfolder
Request status = FAILED
Deployment failed: The Control Room failed to deploy the ExtractionBot (for example: lost server connection). The Control Room makes three attempts.

Important: We do not recommend deleting the process. If you unintentionally delete a process associated with a learning instance, do the following steps to recover the process:

Navigate to Manage > Learning Instances and mouse over the actions menu to the right of the learning instance.
Click Export.
Mouse over the actions menu to the right of the learning instance and click Delete.
Click Import at the top of the page.
Click Browse and select the .dw file you exported.
When prompted, click Overwrite to generate a new process for the learning instance.

Automation 360

About the Automation Co-Pilot process in Document Automation