UI Path ********

Which of the following actions have to be taken in order to run a job on an attended robot connected to the cloud Orchestrator? An automation process was published in Orchestrator, in a folder to which the user has access to The user was added in automation Cloud The user is signed in to Orchestrator The user has a Studio Pro license

An automation process was published in Orchestrator, in a folder to which the user has access to The user was added in automation Cloud The user is signed in to Orchestrator

The interface between the human user and the attended robot. It allows the human to trigger jobs, but also to organize processes, add reminders and so on.

Assistant

A type of robot working on the same machines as the humans, during the same hours. They are triggered directly by humans (usually through UiPath Assistant) or by an event related to what the human user does.

Attended Robot

The cloud platform of UiPath, the single place for managing users and services, such as cloud Orchestrator, cloud AI Fabric, cloud Data Service, and so on.

Automation Cloud

A business process or task automated with Studio family. Depending on the complexity and development approach, an automation project may consist of one or several workflows. A workflow is a set of actions following a given logic set by the developer, having an input and an output. Workflows are typically linked in the same automation project through input and output arguments.

Automation Project

Studio (simple)

Building automation projects

Assistant (simple)

Commands the attended robot

(True/False) Attended users can run automation jobs using UIPath Assistant

False

(True/False) Unattended robots are typically deployed on separate machines

False

How can you add activities to your Studio project?

From the Activities panel

A single execution of an automation process by an attended or unattended robot. If the robots are connected to Orchestrator, both attended and unattended jobs appear there.

Job

Automation Cloud (simple)

Manages the users and cloud services

Orchestrator (simple)

Managing automation processes and jobs

The component of the UiPath RPA Platform in charge of the management of automations, users and robots, as well as the management of the assets used in development or in running automations.

Orchestrator

The sign-in feature connects Studio to...

Orchestrator

An automation project published as a NuGet package from the Studio family to Orchestrator or locally.

Package

A package in Orchestrator linked to an Orchestrator folder where human users or robots have access. If stored locally, packages can be used as processes when they are run by attended robots.

Process

What actions can be easily performed by Studio users that are signed in to Orchestrator?

Publish a package to Orchestrator Run jobs using published processes

UiPath's execution agent installed on a machine and enabling you to run automation jobs based on processes developed in Studio.

Robot

Robots (simple)

Run automation jobs

The component of the UiPath RPA Platform for developing Robotic Process Automation projects

Studio

the RPA Developer profile

Studio

the Advanced Developer profile, with access to testing capabilities, as well as C# support

Studio Pro

the Citizen Developer profile

StudioX

The Studio family consists of three profiles available in the same application. While no additional installation is needed, accessing the profiles depends on the license:

StudioX Studio Studio Pro

(True/False) Attended robots cannot run automation processes published to orchestrator

True

(True/False) In order to receive an attended user license from cloud Orchestrator, users need to be first added in Automation Cloud.

True

(True/False) You can run jobs from Orchestrator both on attended and unattended robots

True

A robot typically deployed on a separate machine than any human user. Their jobs are triggered exclusively from Orchestrator. Since robots do not exist as separate entities in Orchestrator, a more technical definition would position unattended robots as execution slots - a user logged in on a machine, executing an automation job, as instructed by Orchestrator.

Unattended Robot