Skip to main content
The ABBYY FlexiCapture single-task integration solution for UiPath is typically used in one of three scenarios. They differ in where the documents come from and whether an operator verifies the recognition results.

​
Available scenarios

​
Unattended service scenario

The UiPath process that runs the activity sends the file to ABBYY FlexiCapture and receives the processing results in synchronous mode. Files that ABBYY FlexiCapture 12 receives in this scenario need no verification, so they go straight from recognition to the export stage. The ABBYY FlexiCapture project needs an Unattended workflow in the batch type properties, and an Export to data files (XML) export profile in the Document Definition properties.

​
Attended service scenario

The UiPath process that runs the activity sends the file to ABBYY FlexiCapture and receives only a URL that links to the document verification page. In the UiPath process, you can configure the sending of this link to the verification operator by e-mail. After verification, the document goes to the export stage, where the script export profile applies to it. The export creates a new transaction in the specified UiPath Orchestrator queue, holding the image file and the recognized metadata. A separate UiPath process can then extract all the data from the transaction and handle it as your business scenario requires.

​
FlexiCapture as input scenario

Image files are imported into ABBYY FlexiCapture from a mobile client or from a Scanning Station, and documents are verified if verification is necessary. At the export stage, the document uses the script export profile. The export creates a new transaction in the specified UiPath Orchestrator queue, holding the image file and the extracted metadata. From that point, the transaction is handled the same way as in the attended service scenario.