Summary UiPath RPA Certification Study
Guide Complete
automation first three-pronged approach
-A robot for every person
-Open and free collaboration
-Robots learn skills
UIPath Studio
Helps you design automation workflows visually, quickly and with only basic programming knowledge.
Where the automated processes are built in a visual way, using the built-in recorder, drag & drop
activities and best practice templates.
UIPath 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. A server application accessed via
browser, through which the robotic workforce is controlled, managed and monitored
UiPath supported automotation types
-Attended
-Hybrid
-Unattended
Attended robot
Triggered by user events, and operates alongside a human, on the same workstation. Started from
robot tray or command prompt
Unattended robot
Run unattended in virtual environments and can automate any number of processes
Project Panel
Displays the contents of the automation project, enabling the project organization through creation of
subfolders and management of dependencies. Also allows importing workflows and opening file
locations
Output panel
Displays valuable information about the execution of the automated process: messages logged,
errors, and warnings
Variables panel
Enables creating variables and changing their attributes
Arguments panel
Enables creating variables and changing attributes of arguments that store data which are passed
between projects
Imports panel
,Allows viewing the imported namespaces, and also adding new ones
Namespace
Classes of activities or variables that can be used in a project
Properties panel
Allows viewing and changing the properties of a selected activity. The information shown is
contextual, as different activities can have different properties
Outline panel
Displays the project hierarchy, all available variables and nodes. You can go to a specific activity by
selecting it
Process
A set of interrelated or interacting activites that transform inputs into outputs.
Components of a process
-Inputs
-Process Flows
-Source applications
-Outputs
Inputs
The data that goes in the process
Process flows
The sequences of sub-processes or activities used to perform the sub-processes or activities of the
process
Outputs
The result generated by the process
What a procedure explains
-Who is responsible for each part of the process
-When each part of the process needs to occur
-How to handle exceptions
-The specifications applicable to each part of the process
Factors driving automation potential
-Rule based (Decisions are made based on business rules and pre-defined logic)
-Process type
-Standard input (Content is positioned in the same place even if the input types are different)
-Process expected to change (Are processes or applications used to process a case going to change
within 3-6 months?)
,-Unknown exceptions % (Percentage of the total volume received which cannot be processed without
an external factor)
Process types
-Manual and repetitive (Process performed by users and most of the process steps are the same for
all cases or transactions)
-Semi-manual and repetitive (Process which is performed by users and also involves an automation
mechanism like Macro, Outlook plug-ins, etc.)
-Automated (Process which is already automated)
-Manual but Not Repetitive (Process which is performed by users. The process steps for each case will
be different)
Process fitness
-Rule-based
-Automatable and/or repetitive process
-Standard input
-Stable
Automation complexity
-Number of screens
-Types of applications
-Variations / scenarios
-Types and number of inputs
Low: Easily created and requires small customizations. Desktop and web apps, scraping. 1-2 weeks
Medium: Possibly requires the transfer of data between apps. 3-4 weeks
High: Requires programming skills (string manipulations, working with arrays, data tables, collections,
data formatting, exception handling, terminal emulators). 4-6 weeks.
4 categories of processes
-No RPA
-Semi-automation
-High-cost RPA
-Zero-touch animation
No RPA
Processes where change is frequent, the system environment is volatile, and multiple manual (even
non-digital) actions are required
Semi-automation
Processes that can be broken down into steps that can be clearly automated, and steps that need to
stay manual (such as validations or usage of physical security tokens)
High-cost rpa
, Processes that are rather digital and can be automated, but use some technologies that are complex
(such as OCR) or require advanced programming skills
Zero-touch automation
Processes that are digital and involve a highly static system and process environment, so that they can
be easily broken into instructions and simple triggers can be defined
Six stages of RPA implementations
1) Prepare RPA
2) Solution design
3) Build RPA
4) Test RPA
5) Stabilize RPA
6) Constant improvement
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
Solution Architect
Is in charge of defining the Architecture of the RPA solution. Translates the requirements captured by
the functional analysts, creating the architecture and design artifacts. They lead, advises, and are
responsible for the developers' team delivery.
Business Analyst
Is responsible for mapping of the AS IS and proposed TO BE processes. 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/Project Manager
Forms and manages the RPA team, does resource planning and teams availability, in order to hit
automation goals. Most of the times is the Single Point of Contact (SPOC) for questions, RPA
initiatives, or parallel RPA product projects.
RPA Developers
On complex projects, several will collaborate to automate all processes
Infrastructure and 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).
Guide Complete
automation first three-pronged approach
-A robot for every person
-Open and free collaboration
-Robots learn skills
UIPath Studio
Helps you design automation workflows visually, quickly and with only basic programming knowledge.
Where the automated processes are built in a visual way, using the built-in recorder, drag & drop
activities and best practice templates.
UIPath 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. A server application accessed via
browser, through which the robotic workforce is controlled, managed and monitored
UiPath supported automotation types
-Attended
-Hybrid
-Unattended
Attended robot
Triggered by user events, and operates alongside a human, on the same workstation. Started from
robot tray or command prompt
Unattended robot
Run unattended in virtual environments and can automate any number of processes
Project Panel
Displays the contents of the automation project, enabling the project organization through creation of
subfolders and management of dependencies. Also allows importing workflows and opening file
locations
Output panel
Displays valuable information about the execution of the automated process: messages logged,
errors, and warnings
Variables panel
Enables creating variables and changing their attributes
Arguments panel
Enables creating variables and changing attributes of arguments that store data which are passed
between projects
Imports panel
,Allows viewing the imported namespaces, and also adding new ones
Namespace
Classes of activities or variables that can be used in a project
Properties panel
Allows viewing and changing the properties of a selected activity. The information shown is
contextual, as different activities can have different properties
Outline panel
Displays the project hierarchy, all available variables and nodes. You can go to a specific activity by
selecting it
Process
A set of interrelated or interacting activites that transform inputs into outputs.
Components of a process
-Inputs
-Process Flows
-Source applications
-Outputs
Inputs
The data that goes in the process
Process flows
The sequences of sub-processes or activities used to perform the sub-processes or activities of the
process
Outputs
The result generated by the process
What a procedure explains
-Who is responsible for each part of the process
-When each part of the process needs to occur
-How to handle exceptions
-The specifications applicable to each part of the process
Factors driving automation potential
-Rule based (Decisions are made based on business rules and pre-defined logic)
-Process type
-Standard input (Content is positioned in the same place even if the input types are different)
-Process expected to change (Are processes or applications used to process a case going to change
within 3-6 months?)
,-Unknown exceptions % (Percentage of the total volume received which cannot be processed without
an external factor)
Process types
-Manual and repetitive (Process performed by users and most of the process steps are the same for
all cases or transactions)
-Semi-manual and repetitive (Process which is performed by users and also involves an automation
mechanism like Macro, Outlook plug-ins, etc.)
-Automated (Process which is already automated)
-Manual but Not Repetitive (Process which is performed by users. The process steps for each case will
be different)
Process fitness
-Rule-based
-Automatable and/or repetitive process
-Standard input
-Stable
Automation complexity
-Number of screens
-Types of applications
-Variations / scenarios
-Types and number of inputs
Low: Easily created and requires small customizations. Desktop and web apps, scraping. 1-2 weeks
Medium: Possibly requires the transfer of data between apps. 3-4 weeks
High: Requires programming skills (string manipulations, working with arrays, data tables, collections,
data formatting, exception handling, terminal emulators). 4-6 weeks.
4 categories of processes
-No RPA
-Semi-automation
-High-cost RPA
-Zero-touch animation
No RPA
Processes where change is frequent, the system environment is volatile, and multiple manual (even
non-digital) actions are required
Semi-automation
Processes that can be broken down into steps that can be clearly automated, and steps that need to
stay manual (such as validations or usage of physical security tokens)
High-cost rpa
, Processes that are rather digital and can be automated, but use some technologies that are complex
(such as OCR) or require advanced programming skills
Zero-touch automation
Processes that are digital and involve a highly static system and process environment, so that they can
be easily broken into instructions and simple triggers can be defined
Six stages of RPA implementations
1) Prepare RPA
2) Solution design
3) Build RPA
4) Test RPA
5) Stabilize RPA
6) Constant improvement
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
Solution Architect
Is in charge of defining the Architecture of the RPA solution. Translates the requirements captured by
the functional analysts, creating the architecture and design artifacts. They lead, advises, and are
responsible for the developers' team delivery.
Business Analyst
Is responsible for mapping of the AS IS and proposed TO BE processes. 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/Project Manager
Forms and manages the RPA team, does resource planning and teams availability, in order to hit
automation goals. Most of the times is the Single Point of Contact (SPOC) for questions, RPA
initiatives, or parallel RPA product projects.
RPA Developers
On complex projects, several will collaborate to automate all processes
Infrastructure and 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).
