Skip to main content

Prerequisites

  • The Automation Anywhere user has a Bot Creator license, which is required to configure input parameters.
  • The ABBYY FlexiCapture user has the Scanning Operator and Verification Operator roles, or the Administrator role.

Send documents to ABBYY FlexiCapture

This procedure applies to both the attended and the unattended service scenario.
1

Open the sample task for editing

  1. Open the Automation Anywhere Enterprise Client.
  2. In the list of available tasks, select ExportToFlexiCaptureExample and click Edit.
2

Specify the server address

Double-click the Variable Operation action of $ServerURL$ and type the ABBYY FlexiCapture server address in the dialog box that opens.
3

Specify the other required parameters

If you are using tenants, $Company$ is also required. To enable it, right-click the Variable Operation action, click Enable for the $Company$ parameter, and then specify the name of your tenant.
4

Run the task

Click Save in the Task Editor, and then click Run.
The image file is sent to ABBYY FlexiCapture. You get back either a link to the verification page, in an attended scenario, or the processing results, in an unattended scenario. If an error occurs while the task is running, the error is recorded in the following log file:

Get processing results in the attended service scenario

1

Send the documents first

2

Open the sample task for editing

  1. Open the Automation Anywhere Enterprise Client.
  2. In the list of available tasks, select ImportFromFlexiCaptureExample and click Edit.
3

Specify the required parameters

In the Task Editor dialog box, specify the following:If you are using tenants, $Company$ is also required.
4

Run the task

Click Save in the Task Editor, and then click Run.
The ABBYY FlexiCapture server receives a request to check the output folder for suitable processing results. Because the document you sent has not been verified yet, a message reports that there are no suitable processing results. To verify the document, see Verify documents in the attended service scenario. If an error occurs while the task is running, the error is recorded in the following log file: