Skip to main content
The ABBYY FlexiCapture single-task integration solution for UiPath can typically be used in the following three scenarios:
  1. FlexiCapture as an unattended service (UiPath - FlexiCapture - UiPath); no verification is required.
The UiPath process in which the activity is running sends the file to the FlexiCapture and receives the processing results in synchronous mode.The FlexiCapture project requires unattended workflow in batch type properties and Export to data files (XML) export profile in the document definition properties. In this scenario, files received by ABBYY FlexiCapture 12 do not require verification, so once the recognition is completed, they go directly to the export stage.
  1. FlexiCapture as an attended service (UiPath - FlexiCapture - Verification - UiPath).
The UiPath process in which the activity is running sends the file to the FlexiCapture and receives only a URL linking to the document verification page. In the UiPath process, for example, you can configure the sending of this link to the verification operator by email. When the verification is complete, the document goes to the export stage, where the script export profile applies to it. As a result of the export, a new transaction is created in the specified queue of UiPath Orchestrator. Transaction contains image file and recognized metadata. All data from the transaction can be extracted in a separate UiPath process in which the user can configure their further processing as it’s required in his business scenario.
  1. FlexiCapture as input (FlexiCapture Mobile/Scanning Station - FlexiCapture - Verification (if required) - UiPath).
Image files are imported to FlexiCapture using a mobile client or from a Scanning Station. Documents are verified if it’s necessary. At the export stage the document uses the script export profile. As a result of the export, a new transaction is created in the specified queue of UiPath Orchestrator. The transaction contains an image file and extracted metadata. The further process of working with the transaction is similar to “FlexiCapture as an attended service” scenario.