If the learning
instance uses a Google Document AI model and you did not purchase
Google Document AI licenses through Automation Anywhere, you
must provide your Google Document AI credentials to the Extraction
bot. See Configure key for Google Document AI
If the learning instance uses an Automation Anywhere model, ensure that each file
is 50 MB or less.
If the learning instance uses a Google
Document AI model, ensure that each file is 20 MB or less, with a maximum of
5 pages.
Ensure that the sample documents are in one of the following supported document
types:
Perform the following steps to upload sample invoices to the learning instance to
test the data extraction capabilities of the learning instance.
Procedure
Upload documents to test the learning instance:
See these steps in a video:
Click Process documents.
In the Process Documents window, click
Browse to select the files to upload.
Note: Documents with file names exceeding 149 characters
will display an error during processing. Ensure that the file names remain
below the 150-character limit.
In the Download data to field, enter the file
path that will hold extracted data.
When the process runs, it creates the following three folders in the
provided file path:
Success: Contains the extracted data in the
specified format (CSV or JSON).
Invalid: Holds documents marked invalid.
Failed: Holds documents that could not be
processed.
You can provide an output folder path based on one of the
following options:
Option 1: The local device path if you have set
up document processing and validation on the same device.
This option is typically used when you are testing the
learning instance.
Option 2: The shared folder path if you have
set up distributed validation on separate devices.
This
option is typically used for published learning instances.
For example,
\\10.239.192.60\Sharepath\Output.
Click Process documents.
The Bot Runner window appears. The window
disappears when the documents are done processing. Refresh the
Learning instances table to see the updated
metrics.
If there is a value next to the Validate documents
link, you must manually validate the document fields. Otherwise, proceed to step
3.
To skip a document without correcting errors, click
Skip to proceed to the next document
in the validation queue.
To remove a document that cannot be processed, click
Mark as Invalid.
After you make the necessary corrections, click
Submit so that the document can finish
processing.
The next document in queue appears. When all the documents are
corrected, the system displays a message stating that no more tasks are
available.
Close the tab to return to the Learning Instances
page.
Verify the output results:
Open the file in the Success folder that contains the
extracted data and review the results to ensure that it matches your use
case.
The Microsoft forms return
extracted values (OCR data) in the JSON format, such as
GUID_0-MSFormTableResult.json. Along with the extracted
document data in <<GUID>>_FileName CSV file,
the Success folder also shows the extracted table data
separately in another CSV files. Based on the number of tables in the document,
you can find different CSV files for each table. For example,
<<GUID_PAGE_NUMBER-Table_FILENAME_PAGENUMBER_TABLENUMBER.
With
separate table data, you can compare extracted data with Microsoft engine
data in the GUID_0-MSFormTableResult.json file.
Optional: Review the Learning Instance dashboard.
The dashboard displays the total number of uploaded documents and the
number of documents pending validation.
If the learning instance repeatedly cannot find a field or if
characters are not correctly recognized (such as the letter "l" extracted as the number
"1"), you can try changing the OCR to Google Vision OCR.
What to do next
Build a bot that uploads documents from a source folder to the
learning instance. Then, publish the learning instance assets (process, form, and
bots) to the public repository so that the learning instance can
be used in public mode to extract data from real documents, and validators can
manually validate documents: Publish learning instance to production