Document Automation architecture

Document Automation uses features from the Control Room and Automation Co-Pilot for Business Users, as well as some third-party products.

The following architecture graphic demonstrates the flow of data in the intelligent document processing workflow for the two possible deployment scenarios:
  • The Learning instance creator uploads documents to the Document Automation interface, for example to test the extraction capabilities of the learning instance.
  • An Unattended Bot Runner deploys the Scheduler Bot to upload and process the documents.

The graphic also shows the scenarios where data is sent to third-party products, such as for Google Document AI or Standard Forms extraction.

Document Automation integrates into Automation Co-Pilot and the Control Room

Control Room to regions mapping

Document Automation is supported on AWS and Google Cloud Platform.

For customers who configured Document Automation with Google Document AI licenses purchased from Google: Documents uploaded to Document Automation for processing in Google Document AI are sent to the Apigee gateway that you configured when you created the processor in Google Document AI.

For customers who purchased Google Document AI product licenses from Automation Anywhere: Google Document AI uses the Apigee API gateway to manage the document processing APIs. When a document uploaded to Document Automation is sent to Google Document AI, data is sent to the Apigee gateway that corresponds with your AWS or Google Cloud Platform region.

Apigee gateway AWS/Google Cloud Platform regions
US
  • US-East
  • US-Central
  • US-West
  • CAN
  • LATAM
Europe
  • EU-West1
  • EU-West4
  • ME
  • S-Africa
  • AP-Aus
  • AP-Singapore
  • AP-JP
  • India

File storage

The document that you upload in Document Automation is first stored in the Automation Anywhere Control Room Storage Service in an encrypted form. During the extraction phase, documents are pulled from the storage service and then uploaded to external providers for extraction.

After extraction, the files are stored as follows:
  • For AA Pre-trained models: File is deleted immediately post extraction.
  • For Connected Learning Instances: File is deleted immediately post extraction.
  • For Microsoft Azure Form Recognizer and Google Document AI: Since these are third party managed extraction services, the privacy policies vary for each providers and it needs to be checked with the service provider. For more details about privacy policy for these external services, see Document AI Security & Compliance and Microsoft Azure AI Security Policies.
When you have the extraction results from the provider, the results are validated. Based on the validation results,
  • If the document goes to validator, it is available for 90 days and you can perform validations within the 90 days.
  • If the document goes to STP or validated by users, then by default the document gets deleted when the downloaded bot runs.