- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Packages and libraries
A package is a bundle comprising all automation elements such as activities, workflows, files, and data sources. When you create a project in Studio, you publish it as a package to a specific location or feed. From here, the Robot can download and use it to run the automation.
Use absolute paths to indicate the location of packages.
The following locations and feeds are configured by default in Studio:
-
Orchestrator Tenant and Orchestrator Host - These activities feeds are added by default if your Robot is connected to Orchestrator and they cannot be disabled. The Orchestrator Tenant option is available only if the tenant libraries feed is enabled in Orchestrator. The feeds have the following source:
https://[Orchestrator_host]/nuget/activities
. -
Local - The feed for the packages installed locally with Studio. The feed has the source:
%ProgramFiles%\UiPath\Studio\Packages
for per-machine installations or%localappdata%\Programs\UiPath\Studio\Package
s for per-user installations.Note:The publish date displayed in the Manage Packages window for packages from the local feed is the date when the Studio installer was built, not the date when the packages were published.
-
Official - The official online UiPath feed, where you can find the activity packages that are officially supported by us. This feed has the following source:
https://pkgs.dev.azure.com/uipath/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json
. -
Marketplace - This public feed contains all the activities published on the UiPath Marketplace. Please note that whether or not packages are built and officially supported by UiPath is specifically stated in the Manage Packages window, Package Information tab. This feed has the following source:
https://gallery.uipath.com/api/v3/index.json
.
In Enterprise installations, a custom activity feed can only be used in workflows started from Studio on that user. Starting a job on the same machine from Orchestrator or the Assistant results in the Robot not being able to retrieve the appropriate package. To avoid such scenarios, add the custom feed
To use custom feeds, make sure the Robot has access to the custom location.
-
For the Strict runtime rule, the Robot looks only for the specified package version. For example, if you select Version 2.5.0 and set the Runtime Rule as Strict, the Robot seeks only version 2.5.0. If not found, it throws an error.
-
Fot the Lowest Applicable Version runtime rule, the Robot looks for the specified package version or higher. For example, if you select Version 2.5.0 and set the Runtime Rule as Lowest Applicable Version, the Robot searches for versions starting with 2.5.0 (2.5.0, 2.5.1, 2.5.2 and so on). If not found, it throws an error.
-
If you choose to install the local feed, the
%ProgramFiles%\UiPath\Studio\Packages
folder is created. It contains the activity packages that are officially supported by UiPath at install time. The feed is enabled by default. -
If you choose not to install the local feed, the
%ProgramFiles%\UiPath\Studio\Packages
folder is created, however it only contains the packs that are added as default dependencies to a new project:-
UiPath.UIAutomation.Activities
-
UiPath.System.Activities
-
UiPath.Excel.Activities
-
UiPath.Mail.Activities
-
When you connect the Robot to Orchestrator, a NuGet feed is provided by Orchestrator. It contains the activity packages that are officially supported by UiPath . This feed is enabled by default and depends on your storage settings.
Robot connected to Orchestrator |
|
---|---|
Robot not connected to Orchestrator | When the Robot is not connected to Orchestrator, or it does not find the required activities in the local feed, it uses the
following feed:
This is the official online UiPath feed, which is the source from where the Package Manager in Studio retrieves its activities. By default, this feed is not active. To enable it, in Studio, go to Settings > Manage Sources, and select the corresponding option. |
A fallback package folder is a backup folder from which the robot can retrieve necessary packages if the primary source fails.
NUGET_FALLBACK_PACKAGES
environment variable on the robot machine. The variable should contain the list of full paths, each separated by a semicolon,
to these backup folders. If the environment variable does not exist, the robot tries to read the NuGet packages fallback folders
from the Nuget.config
file.
You cannot use fallback folders to store and run entire automations or workflows.
Processes deployed in fallback folders are not supported, only dependencies.