- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Restarting Robot Components
- Troubleshooting
- About Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
Robot User Guide
Custom Package Folders and Network Paths
A Package combines all parts used in an automation and it can include: Activities, Workflows, Files, Data Sources, and other components needed for running the automation. A project created in Studio is published as a Package to a location/feed from where it is later downloaded by the Robot introduction and used to run an automation.
The following locations/feeds are configured by default in Studio:
- Orchestrator Tenant and Orchestrator Host
- Local
- Official
- Marketplace
Custom feeds can be used as well, but before setting up a custom location to publish a Package, make sure that Robots have access to it.
For more information on how feeds work and how to change them, see the Managing Activities Packages document which goes in more details on this subject.
PACKAGES_FOLDER
parameter or by editing the uipath.config file. This enables you to change the download location of your workflows and their dependencies for Studio and/or Robot.
%userProfile%\.nuget\packages
.
%USERNAME%
or %USERPROFILE%
but needs to be escaped as follows:
-
When the setup is invoked from Command Prompt - use -
UiPathStudio.msi PACKAGES_FOLDER=C:\Some\Path\^%USERNAME^%
. -
Batch scripts - use
%
-UiPathStudio.msi PACKAGES_FOLDER=C:\Some\Path\^%USERNAME^%
. -
PowerShell console or scripts - no escaping is needed.
-
When using Active Directory domain accounts, it is recommended to specify the domain name in the folder structure too, such as
C:\packages\^%UserDomain^%.^%Username^%
.
- No restrictions when a local path is used by multiple service mode robots on the same machine.
- When the robot is deployed in service mode and Secure XAML is used, network paths are not supported.
- Service mode robots installed on separate machines cannot connect to the same folder on a network. Each machine must have its own folder.
- Only non-mapped paths are supported, e.g.
\\server\Packages
. Mapped network paths such asZ:\Packages
is not supported. The reasoning consists in how the mappings are being resolved per user. In this situation, the owner of the installed files is the computer account and thus, it will not have access to the per-user network mappings.
- When local paths are used, the path must contain the username.
- If the same local path is used by multiple user mode robots on the same machine, installing or running an automation can fail if two or more robots try to use the files in the folder at the same time. If two or more robots try to install the same process at the same time, the installation can fail.
-
When network paths are used, the path must include the machine name and username.
Note:If the same process has to be executed by multiple robots simultaneously, make sure that the workflow does not write or modify any files in the workflow installation folder. The working directory of the automation is the installation folder, thus you should avoid using relative paths in the workflow except for reading files packaged in the automation.
To avoid this, use absolute paths that resolve to each specific user. For example%userprofile%\Desktop
or%temp%
.