Skip to main content
The installation path depends on whether the package serves an existing UiPath process or a new one.

Install the package for an existing UiPath process

All UiPath processes consist of various activities. When a Robot launches a process, or when UiPath Studio opens one, it searches the available activity feeds for the relevant activities and downloads them. To open the sample ABBYY FlexiCapture 12 Processor process, place the Abbyy.FlexiCapture.WebApi.Client.nupkg and Abbyy.Activities.UiPath.FlexiCaptureActivities.nupkg packages in an activity feed that the Robot can reach.

Place the packages in the Robot’s local feed

Copy both packages into the folder that matches your UiPath edition:
  • UiPath Community Edition%LocalAppData%\UiPath\app-xx.x.x\Packages, where xx.x.x is the UiPath version number
  • UiPath Enterprise EditionC:\Program Files (x86)\UiPath\Studio\Packages
To find the path to the Robot’s local feed, open UiPath Studio and open the Settings tab. Then select Local in Manage Sources.
Screenshot of the UiPath Studio Settings tab showing the Manage Sources panel, where the Local default package source points to the Robot's local activity feed folder under the UiPath app Packages directory.

Place the packages in the Orchestrator activity feed

Packages in the Orchestrator activity feed are available to every Robot connected to Orchestrator, which cuts the time needed to update a package for all of them. Use the method for your UiPath edition:
  • UiPath Community Edition – Go to the cloud Orchestrator and select Processes → Packages. Then click Upload and upload the Abbyy.FlexiCapture.WebApi.Client.nupkg and Abbyy.Activities.UiPath.FlexiCaptureActivities.nupkg packages one after another.
    Screenshot of the Packages page in UiPath Orchestrator, where the Upload button is highlighted and the uploaded Abbyy.Activities.UiPath.FlexiCaptureActivities, Abbyy.FlexiCapture.WebApi.Client, and Abbyy.UiPath.FlexiCapture.MultiTaskActivities packages are listed.
  • UiPath Enterprise Edition – Copy the packages to the Orchestrator activity feed. By default it is located in C:\Program Files (x86)\UiPath\Orchestrator\NuGetPackages\Activities on a machine that has Orchestrator installed. You can also download the packages on the Libraries tab in the Orchestrator web application.
For more information about activity feeds, see the UiPath documentation.

Add the package to a new UiPath process

To use the Capture Data activity in a new process, or to add it to an existing one, include the Abbyy.Activities.UiPath.FlexiCaptureActivities.nupkg activity package in the dependencies of the process.
1

Open Manage Packages

Open an existing process in UiPath Studio and click Manage Packages.
Screenshot of UiPath Studio with a blank process open and the Manage Packages button highlighted on the Design ribbon.
2

Find the local package source

Select Settings and find the local Source in the Default package sources list.
Screenshot of the Manage Packages dialog in UiPath Studio on the Settings tab, where the Local source under Default package sources points to the UiPath app Packages folder.
3

Copy the packages to that source

Copy the Abbyy.FlexiCapture.WebApi.Client.nupkg and Abbyy.Activities.UiPath.FlexiCaptureActivities.nupkg packages to the folder specified in Default local package source.You can also place these packages in any other available source from the list.
4

Install the activity package

  1. Go to Manage Packages and navigate to All packages → Local.
  2. Select Abbyy.Activities.UiPath.FlexiCaptureActivities in the activity list.
  3. Click Install, and then click Save.
Screenshot of the Manage Packages dialog in UiPath Studio with the Local source selected and the Abbyy.Activities.UiPath.FlexiCaptureActivities package chosen, showing its details and the highlighted Install and Save buttons.
The Capture Data activity then appears in the available activities list.
Screenshot of the UiPath Studio Activities panel showing the Capture Data activity available under the ABBYY FlexiCapture Single-Task Package node.