UiPath Glossary

A

account

Refers to a user’s identity within UiPath products, which is used to grant them access to UiPath properties. For example, a user can create an account using their email address and a password to access UiPath resources online (Automation Cloud, UiPath Community Forum)

action

Task to be performed or undertaken by a user when user intervention is required in order to proceed to the next step in a long-running workflow.

action catalog

Action container, where the user can categorize their actions. The catalog in which an action resides is set during workflow design in Studio.

activity

Building block of process automation. UiPath Studio comes with various built-in activities, as well as dedicated activities (PDF, Mail, Excel) you can install through the Package Manager, depending on your needs.

argument

Entity used to pass data from one workflow to another. Can store data dynamically and pass it on. They are configured at design time, in Studio, and can be parameterized in other third-party apps or Orchestrator.

C

component

Pieces of code that help you create a clear and smooth automation process. Within UiPath the following component types are defined: custom activities, snippets, automation frameworks, solutions and connectors, dashboards, machine learning models.

CoE

Abbreviated for Center of Excellence, an internal, self-sustaining group of employees who can embed RPA deeply and effectively into the organization, and redistribute accumulated knowledge and resources across future deployments.

connector

Application Connector is a component that enables UiPath products to connect with other applications.  A Data Connector is a component that enables UiPath products to connect with external data sources.

custom activity

Building block of the process automation. Multiple activities, connected between them create the automation workflow. The complexity of activities varies from simply defining a variable to configuring them by using custom wizards.

E

environment

Grouping of robots in a classic folder which enables the user to execute processes on multiple robots simultaneously.

F

local feed

Local repository of activity packages that is installed by default with Studio and/or Robot at this location - %ProgramFiles(x86)%\UiPath\Studio\Packages. You can choose not to install this feed or disable it later from the Manage Packages window in Studio.

official feed

Official UiPath online repository of supported activity packages - https://www.myget.org/F/workflow/. It can be disabled from the Manage Packages window in Studio.

packages feed

Repository of packages that allows you to store and group packages in order to control their availability and isolation.

floating robot

Orchestrator entity that controls the connection capabilities of UiPath Robot with respect to the host machine on which it's installed. A floating robot enables one user to work on multiple workstations, as the robot is not tied to a specific machine. Recommended for users who work on multiple machines (non-persistent VDIs or shift-based workplaces). All robots in modern folders are floating robots.

Orchestrator folder

Automation management container within a Tenant, for example Finance Department and HR Department. Orchestrator owns the folders hierarchy and the UX for it. All other suite products that need automation-related configuration, management, and deployment must understand and work with Folders. For example, to deploy a test suite to the HR Automation Testing folder, Test Manager must integrate with Orchestrator; or to deploy an application to the Invoice Processing folder, Apps must integrate with the same Orchestrator.

G

governance

Global user policy for restrict permissions on feed management, Workflow Analyzer rules, and more.

H

host license

Type of license that aggregates multiple robot licenses, which can then be allocated to your tenants from a centralized location, at the host level.

J

job

Execution of a process on UiPath Robot.

L

library

.nupkg package consisting of reusable components that can be used as an activity in multiple processes.

local feed

Local repository of activity packages that is installed by default with Studio and/or Robot at this location - %ProgramFiles(x86)%\UiPath\Studio\Packages. You can choose not to install this feed or disable it later from the Manage Packages window in Studio.

M

machine template

Orchestrator entity that works as an API key generator, which authorizes the connection between UiPath Robot and Orchestrator. It enables administrators to connect multiple Robots to Orchestrator using the same key. The generated key works for any machine on which the Robot is installed, with no restrictions in terms of machine name, so this can be used for all types of setups, including those in which the name of the workstation changes every time a user logs on to it.

standard machine

Orchestrator entity that works as an API key generator, which authorizes the connection between UiPath Robot and Orchestrator. It enables administrators to connect the Robot to Orchestrator on one workstation only. The standard machine key is generated for a single workstation with the same name as given to the standard machine. This is recommended if you want to restrict connecting the Robot to Orchestrator on a certain machine only, as it works in scenarios in which the machine name stays the same each time you connect to it.

Multiuser

Type of user license. Allows more than one individual to use UiPath software and helps control entitlements for multiple users on one license. Recommended for users that work in shifts. Each Multiuser license adds up to 3 distinct authenticated users to the maximum number of users that can be granted access. You must obtain a number of Multiuser licenses equal to the number of authenticated users accessing the product or service simultaneously. It is displayed as Concurrent User in the previously released versions of UiPath products (e.g., v2020.10 Orchestrator).

N

Named User

Type of user license. Ties the usage of UiPath software to an individual user. You must obtain a separate license for each uniquely identified user accessing the product or service.

NonProduction

License. Functionally identical to an Unattended license, but as per the license agreement it can only be used for developing/testing (unattended processes).

O

official feed

Official UiPath online repository of supported activity packages - https://www.myget.org/F/workflow/. It can be disabled from the Manage Packages window in Studio.

Orchestrator folder

Automation management container within a Tenant, for example Finance Department and HR Department. Orchestrator owns the folders hierarchy and the UX for it. All other suite products that need automation-related configuration, management, and deployment must understand and work with Folders. For example, to deploy a test suite to the HR Automation Testing folder, Test Manager must integrate with Orchestrator; or to deploy an application to the Invoice Processing folder, Apps must integrate with the same Orchestrator.

organization

Root of a customer organization in UiPath. It is represented by a URL that an enterprise has access to and controls (e.g. ). Services (for example Automation Hub) and data can be scoped at the organization level. In most cases, an organization maps to a legal entity. There is complete isolation between organizations; a user can be part of multiple organizations, but a user must always choose what organization to work in; user actions are scoped to an organization.

P

package

Automation project that has been published.

package feed

Repository of packages that allows you to store and group packages in order to control their availability and isolation.

R

floating robot

Orchestrator entity that controls the connection capabilities of UiPath Robot with respect to the host machine on which it's installed. A floating robot enables one user to work on multiple workstations, as the robot is not tied to a specific machine. Recommended for users who work on multiple machines (non-persistent VDIs or shift-based workplaces). All robots in modern folders are floating robots.

standard robot

Orchestrator entity that controls the connection capabilities of UiPath Robot with respect to the host machine on which it's installed. It enables one user to work on a single workstation, as the robot is tied to a specific machine, namely the one set at robot creation. Recommended for users who always work on the same machine. Standard robots are the predecessors of floating robots, and you can only find them when working with classic folders.

S

service

Instance of a UiPath product within an organization or a tenant. For example, a tenant may have an Orchestrator service, and an AI Fabric service provisioned.

snippet

Component containing ready-made bits of code that can be either invoked or included in workflows.

solution

Component containing an end to end process automation created using UiPath software that solves domain and industry-specific business problems. This consists of UiPath process flow definitions with examples and templates, how-to documentation as well as Binary or Non-Binary Workflow Libraries.

standard robot

Orchestrator entity that controls the connection capabilities of UiPath Robot with respect to the host machine on which it's installed. It enables one user to work on a single workstation, as the robot is tied to a specific machine, namely the one set at robot creation. Recommended for users who always work on the same machine. Standard robots are the predecessors of floating robots, and you can only find them when working with classic folders.

standard machine

Orchestrator entity that works as an API key generator, which authorizes the connection between UiPath Robot and Orchestrator. It enables administrators to connect the Robot to Orchestrator on one workstation only. The standard machine key is generated for a single workstation with the same name as given to the standard machine. This is recommended if you want to restrict connecting the Robot to Orchestrator on a certain machine only, as it works in scenarios in which the machine name stays the same each time you connect to it.

T

transaction

A queue item that has been processed.

trigger

Functionality enabling the user to execute jobs in a preplanned manner, at regular intervals (time triggers), or whenever new items are added to the queues (queue triggers).

U

UiPath account

Also known as a local account. A user-owned account that is registered with UiPath and used to log in to Automation Cloud and other UiPath resources such as the UiPath Forum or UiPath Academy. The account is created by either choosing a username and password, or by federating with Microsoft, Google, or LinkedIn when signing up for Automation Cloud or when accepting an invitation to join an Automation Cloud organization.

W

webhook

HTTP callback triggered by a user-defined event in Orchestrator.

workflow

Project that connects several activities in order to create a robotic process automation.

workflow template

Framework that provides an already established workflow structure, and facilitates best practices such as modularity, reusability, maintainability, and extensibility.