A process represents the association between a package and an environment. Each time a package is linked to an environment, it is automatically distributed to all the Robot machines that belong to that environment.
The Processes page enables you to deploy an uploaded package to Robot environments, manage previously created associations and keep all your processes up to date. This helps you distribute packages on the Robot machines and execute processes faster from the Jobs page.
Note that creating a process requires your user to have View and Create permissions on Processes, as well as View permissions on Packages and Environments. Read more About Roles.
Each time a package is linked to an environment, it is automatically distributed to all the Robot machines that belong to that environment, in the
%ALLUSERSPROFILE%\UiPath\Projects folder. When you update or rollback a process, it is also automatically updated in the aforementioned directory.
If a new version of a package is available in Orchestrator (you published a new version from Studio), it is indicated with the following icon next to the process it is part of. For more information, see Managing Process Versions.
If a package version associated with an environment is no longer available in the configured NuGet repository, it is indicated with the following icon .
If you are using the latest available version of a package in a specific process, the following icon is displayed next to the process.
If you have multiple Robots on the same machine, it is recommended that you group them in the same environment. Otherwise, some errors might occur when deploying different versions of the same process.
Activities used in Studio packages are stored in a NuGet feed that Orchestrator has access to. As a result, each time you deploy a package to an environment, the activities are also sent to the Robot machines that are part of that environment. This enables you to execute processes using those Robots, even when your connection to Orchestrator is down.