UI Path

Introduction to Ui Path

The Ui Path Platform offers you the components you need to design and develop automation projects, execute the instructions automatically and manage your robot workforce.

The components of the Ui Path Platform are

➤ Ui Path Studio (the workflow designer),

➤ Ui Path Orchestrator (the robot management platform) and

➤ The Robot (the agent executing the instructions).

Ui Path Studio

➽ Helps you design automation workflows visually, quickly and with only basic programming knowledge.

➽ Studio is where the automated processes are built in a visual way, using the built-in recorder, drag & drop activities and
best practice templates.

Ui Path Orchestrator

➽ Lets you control, manage and monitor the robots. It is also the place where libraries, reusable components,
assets and processes used by the robots are stored. Orchestrator is a server application accessed via browser,
through which the robotic workforce is controlled, managed and monitored:

• The connections with the robots are created and maintained, and the robots are grouped (control).

• The automated processes are distributed as tasks to the robots (management).

• The execution of tasks is logged and kept track of (monitoring).

The Robot

➽ Executes the workflows and instructions sent locally or via Orchestrator. There are two types of robots:

• Attended – is triggered by user events, and operates alongside a human, on the same workstation.

• Unattended - run unattended in virtual environments and can automate any number of processes.

Ui Path Architecture

As you can probably remember, the UiPath solution consists of Studio, Robot and Orchestrator, each of them having a specific function.

• Studio is where the magic happens through the design of automation workflows.

• Robot executes the activity or process designed in Studio while

• Orchestrator controls the robots in the production environment and the execution of tasks.



➤ Studio and the robots function within the client’s infrastructure, with Studio installed on the developers’ stations,

and the robots on a Windows Server or Windows Desktop machines, both real and virtual, depending on the automation scenarios.




➤ Orchestrator is hosted on a web application server, so the clients can access it through a web browser, with designated credentials.

➤ Orchestrator comprises several layers: the presentation layer, or the interface that we access using the browser, the service layer(allowing for API calls) and

Persistence layer, where relevant information and events are stored and logged. The persistence layer is generally built using SQL Server and Elasticsearch.

The client may choose only one of them, or even different solutions altogether. We’ll provide more details about this topic in the next sections.


Studio---where the automations are built, using drag & drop widgets, the built-in recorder, and reusable components.Knowledge of a programming language is not required to build simple projects, as the design is made visually on a canvas, using building blocks.

Robots are the digital workers that carry out the automations, based on the instructions received from UiPath Orchestrator

Orchestrator is the web-based application used to deploy, assign tasks to and monitor the robotic workforce. It is mandatory in large and complex automations, but not in simple cases like the one above


Note:- I will be updating this blog frequently.✍

Thank you for visiting this blog☕️

“In the end, only three things matter: How much you loved, how gently you lived, and how gracefully you let go of things not meant for you”

Six Stages of an RPA Implementation

Ⅰ. Prepare RPA

➽ The processes are defined, assessed, prioritized and the implementation is planned.

Ⅱ. Solution Design

➽ Each process to be automated is documented ("as is" and "to be"), the architecture is created and reviewed,
the test scenarios and environments are prepared and the solution design is created and documented for each process.

Ⅲ. Build RPA

➽ The processes are automated, the workflow is tested and validated and the UAT prepared.

Ⅳ. Test RPA

➽ The UAT is performed, the workflow is debugged and the process is signed off.

Ⅴ. Stabilize RPA

➽ The Go-Live is prepared, the process is moved to production, monitored, measured and the lessons learned are documented.

Ⅵ. Constant Improvement

➽ The process automation performance is assessed, the benefits tracked and the changes managed.




Following are some of the roles encountered in RPA implementations that drive the change

Ⅰ. Solution Architect

➽ Is in charge of defining the Architecture of the RPA solution.
The Solution Architect translates the requirements captured by the functional analysts, creating the architecture and design artifacts.
They lead, advises, and is responsible for the developers' team delivery.

Ⅱ. Business Analyst

➽ Is responsible for mapping of the AS IS and proposed TO BE processes.
Business Analysts hold knowledge of the business process that gets automated, general business process theory and RPA capabilities.
They are responsible with listing the process requirements for automation, clarifying the inputs and expected outputs,
creating RPA documentation (Process Design Documents, Process maps.

Ⅲ. Implementation Manager or Project Manager

➽ Forms and manages the RPA team, does resource planning and teams availability, in order to hit automation goals.
Most of the times the PM is the Single Point of Contact (SPOC) for questions, RPA initiatives, or parallel RPA product projects.

Ⅳ. Infrastructure & IT Security admin

➽ With good technical and security skills, they are responsible for setting up and maintaining hardware &
software resources for UiPath product installations. They set up accounts for all the devs, end users and robots.

Ⅴ. Process Owner

➽ Is the key stakeholder and beneficiaries of the RPA solution.
Usually Senior Management level, with some 10-15+ years of experience, possibly split across domains.
Multiple people can have this role, based on department (Finance, IT, HR, etc).

Ⅵ. RPA Support

➽ Manage the robots after the processes have been moved to production,
with support from the original RPA devs who have performed the automation.
May have multiple levels of support: L1- Client, L2- client/ partner, (L0 – Super users; L3 – UiPath)

Note:- I will be updating this blog frequently.✍

Thank you for visiting this blog☕️

“Learn this from water: loud splashes the brook but the oceans depth are calm”