UIPath TAM Learning P

Additional Knowledge

10/11/2023

Santiago Giraldo Osorio

Technical Account manager - ACCELIRATE
Contents
Citizen Developers.............................................................................................................................5
Citizen Developers and the fully automated enterprise.................................................................5
What is the RobotPath?.................................................................................................................6
What is the HumanPath?...............................................................................................................6
Studio Web.........................................................................................................................................6
Who is it for?..................................................................................................................................7
Why should I use it?.......................................................................................................................7
Templates.......................................................................................................................................7
What are templates?..................................................................................................................7
Connections...................................................................................................................................7
What are connections?...............................................................................................................7
UIPAth Insights...................................................................................................................................8
What can you measure?.................................................................................................................8
What is UiPath Insights?...............................................................................................................11
What are the key features of UiPath Insights?.............................................................................11
Who is it for?................................................................................................................................11
How can you access it?.................................................................................................................12
How does Insights fit into the larger picture of the UiPath Platform?..........................................12
Types of permissions....................................................................................................................13
Viewer..........................................................................................................................................13
Designer.......................................................................................................................................13
Admin...........................................................................................................................................13
ROI Viewer and ROI Editor............................................................................................................13
UIPath Apps......................................................................................................................................14
What makes UiPath Apps different?.............................................................................................14
The Components of UiPath Apps..................................................................................................14
Apps.........................................................................................................................................14
App Studio................................................................................................................................15
Get Started With App Studio........................................................................................................16
Input Controls:..........................................................................................................................16
Display Controls:.......................................................................................................................16
Container Controls:..................................................................................................................16

1|Page
 Setting control properties.............................................................................................................16
General:....................................................................................................................................16
Events:......................................................................................................................................16
Style:.........................................................................................................................................16
Data binding.................................................................................................................................16
What are Events and Rules in Apps Studio?.................................................................................16
Events.......................................................................................................................................16
Rules.........................................................................................................................................17
Expressions...................................................................................................................................17
How do expressions work?.......................................................................................................17
Functions..................................................................................................................................18
Named operators.....................................................................................................................18
Working with Files and Persistent Data........................................................................................18
Working with files stored in Orchestrator.................................................................................18
Working with UiPath Data Service entities...............................................................................19
Functions..................................................................................................................................19
Rules.........................................................................................................................................20
Action Center...................................................................................................................................20
Overview......................................................................................................................................20
Unassigned action status..........................................................................................................20
Completed action status...........................................................................................................20
Pending action status...............................................................................................................21
Action types.................................................................................................................................21
Form tasks................................................................................................................................21
Document Understanding tasks...............................................................................................21
External tasks...............................................................................................................................21
Automation Ops...............................................................................................................................22
What is UiPath Automation Ops?.................................................................................................22
Why you need it?.........................................................................................................................22
Creating Policies...........................................................................................................................23
Deploying Policies........................................................................................................................23
How are policies applied based on the options set at tenant, group and user level?...................24
Uploading Policies........................................................................................................................24

2|Page
Data Service.....................................................................................................................................25
What is Data Service?...................................................................................................................25
What are the key components of Data Service?...........................................................................25
How do you use Data Service?.....................................................................................................26
What are the benefits of using data service?...............................................................................26
Creating Entities in Data Service...................................................................................................27
Using Entities in Studio Projects...................................................................................................27
Storing Values in Data Service......................................................................................................27
License Allocation and Management............................................................................................28
License Level Details.................................................................................................................28
Community License..................................................................................................................28
Provisioning Data Service Tenants............................................................................................29
License Workflow.....................................................................................................................29
Process Mining.................................................................................................................................30
Process Discovery.........................................................................................................................30
How can we build a healthy transformation pipeline?.................................................................30
What is Continuous Discovery?....................................................................................................32
What are the stages of Continuous Discovery?........................................................................32
How Discovery products work together?.................................................................................32
Test Suite..........................................................................................................................................33
Types of testing............................................................................................................................33
Phases of the testing....................................................................................................................34
Test Levels....................................................................................................................................34
Test Suite......................................................................................................................................34
Components.............................................................................................................................34
Software development and testing process cycle.....................................................................35
UiPath Test Manager....................................................................................................................35
Main functional areas...............................................................................................................35
Relationship Between The Different Types Of Assets...................................................................36
SAP Automation...............................................................................................................................36
What is an endorsed application?................................................................................................36
What does this certification mean for UiPath?.............................................................................36
What does this certification mean for UiPath and SAP clients and partners?..............................36

3|Page
Processes Examples......................................................................................................................37
SAP WinGUI automation with UiPath...........................................................................................37
SAP WebGUI and SAP Web Dynpro automation with UiPath...................................................38
SAP Fiori automation with UiPath............................................................................................39
SAP automation across all SAP non-visual interfaces - SAP BAPI..............................................40
Benefits of automating SAP non-visual interfaces....................................................................41

4|Page
Citizen Developers
are non-technical users who create simple automations for themselves or their departments.

In other words, Citizen Developers automate tasks, whereas RPA Developers automate processes.
Automation users enjoy the outcome of both worlds.

Tasks vs processes

A task can be described as a series of steps that are performed by a single operator, be it a human
or a machine. For example, merging data from two different Excel files and saving the final file in a
local folder.

We define a step as an action which is required to accomplish a specific, clearly defined purpose.
For example, downloading an Excel file attachment from an email.

A process is a set of interrelated or interacting tasks that aim to deliver a larger objective. It can
group together both humans and machines. Take for example an order-to-cash process which
needs to work with multiple systems and requires human validation of the output.

Citizen Developers and the fully automated enterprise.

Now let's see how you, as a Citizen Developer, can have a positive impact on your organization:

 1 - Increasing the speed of automation development at the departmental and individual

levels
While your RPA developers work on big, organization-wide automations, as a Citizen
Developer you can find day-to-day uses for automation tools in your own work.

 2 - Reducing the load on the IT department

The IT department cannot focus on bigger strategic targets if they are distracted by simple
automation requests. As a Citizen Developer, you can design and build your own personal
automations, which will provide another layer of automation support and creation for your
organization.

 3 - Offering ground-level process expertise

The people who use the tasks and processes know them best. As a Citizen Developer you
can save yourself and your teammates from tedious work by automating away the most
mundane tasks.

Having the right mindset helps one take a complex problem, analyze it, and come up with possible
solutions. We can then present these solutions in a way that a robot, a human, or both, can
understand.

We call this mindset Computational Thinking and here are the four key techniques we’ll explore in
this lesson.

5|Page
1 - The first technique is called Decomposition. When facing a complex problem, the first step is to
break it down into smaller, more manageable pieces.

2 - The second technique describes the process of Pattern Recognition, which involves finding
similarities between and within problems.

3 - The third technique, Abstraction, helps you filter out all the irrelevant details.

4 - Using the fourth technique, you Design Algorithms, meaning you develop a step-by-step or a set
of rules for solving the problem.

What is the RobotPath?

The Robot Path is a detailed overview of your task's steps. The objective is to have a click-by-click
process flow. Imagine you give the Robot Path to a new hire instead of training.
Let's look at the Robot Path of the Unicorn Name task automation.

What is the HumanPath?

The HumanPath is just a high-level overview of the task's steps.
Let's take a look at the HumanPath of this task automation.

Studio Web
Studio Web is a web-based product within the Studio family, focusing on collaboration as a key
ingredient for delivering exceptional business outcomes. The main goal of Studio Web is to offer a
simple, online platform that allows you to create and manage automation processes easily.

Designed to complement the citizen developer program, Studio Web also offers new
troubleshooting capabilities, which we will discover in this course. By providing compatibility
across platforms, centralized storage, and CI/CD pipelines, it creates a comprehensive platform for

6|Page
a diverse range of users, including business users, citizen developers, RPA developers, IT Admins,
and Orchestrator Admins.

Who is it for?
Studio Web is designed, well, for everyone looking to automate a task. It's perfect for both
beginners who are starting their automation journey but also for experienced users who need a
convenient tool for designing and sharing automation projects.

Why should I use it?

Studio Web enables the effective automation of digital tasks and various online processes. It's
designed to run on Windows, macOS, and Linux operating systems, thereby offering a versatile
solution for automating tasks across different platforms. It's ideal for IT automation and enables IT
departments to automate cloud and ITSM tasks directly from their browser without needing
additional desktop software tools.

One of the standout features of Studio Web, particularly for UI Automation, is live streaming. It
allows users to visually follow the progress of their automation as it unfolds within the cloud robot.
This enhances the user experience and provides valuable real-time insights.

Additionally, Studio Web leverages the power of the Integration Service to deliver activities and
triggers that users can leverage for automating online services.

Studio Web also boasts a range of pre-built Document Understanding activities such as Digitize
Document, Classify Document Scope and Data Extraction for a Field that aid in processing and
analyzing documents more efficiently.

Templates
There are two ways of creating a new project in StudioWeb:

1. Starting with a template;

2. Alternatively, you can build a project from scratch (we'll discuss this option in the next
lesson, Building a Project).

What are templates?

A template is a preconfigured project that automates common scenarios. Templates can be used
as-is or as a starting point for new projects. There are templates that don't require configuration,
and others that require a few changes to match your data.

Connections
Automations must connect to the online applications you use in your projects. When you design
automations, you can create and manage connections securely straight from your projects.

What are connections?

Connectors are available in Integration Service(opens in a new tab) for a wide range of
applications, and you can automate your accounts using connections.

7|Page
You can add or use an existing connection from your Personal Workspace or from other folders
you're assigned to in the current tenant. When you add a new connection from Studio Web, the
connection is created in your Personal Workspace.

When sharing a project, each user must configure the connections with their own specific data.

UIPAth Insights
To measure automation, you need to establish concrete goals that you can use to check your
progress towards reaching those goals.

Here's an easy, three-step approach to achieving this:

 Start with tracking and measuring your operational metrics (errors, utilization, success
rate, and so on).

 Then tie these operational results to business outcomes (ROI, process outcomes) - more on
the difference between operational and business KPIs below.

 Finally, measure each performance metric every month, and then total them for every year
so you can get a comprehensive understanding of pace and scale.

Remember that every metric you track should answer a question you have, whether it’s an
operational ask or a business ask.

What can you measure?

Automation analytics spans across two types of metrics: operational KPIs and business KPIs.

 1 - Operational KPIs contain information that relates to the execution of automation itself,
but they don’t include things like time saved and money saved.

 Errors

Why?

Let’s face it, Robots don’t need coffee, but they can’t perform perfectly if blocked by
obstacles beyond their control. For instance, Robots may be unable to finish a process if an
application fails or is under maintenance.

How?

For unexpected roadblocks like this, it’s important to track any errors and the reasons
behind them. When you look back at the trends over time, you’ll be able to see patterns
and take action to remedy them.

 Robot utilization

Why?

Keeping track of how long your Robots have worked each day is important for capacity
planning. Robot utilization shows if your Robots could work harder or if you’re asking too
much of them.

8|Page
 How?

You’ll want to look at utilization in terms of hours per day, with 24 hours being your max
for Unattended Robots and the number of hours a human is working per day with
Attended Robots. It’s a good idea to have a few checkpoints for utilization:

 Average hours worked per day (for all Robots)

 Hours worked per day over a certain amount of time

 Hours worked per day for specific Robots you think are over- or under-utilized

A low daily utilization rate means you could give your Robots more work to do, while a high
daily rate might indicate an automation backlog. In the case of a high utilization rate, it’s
most likely time to add more Robots to distribute the workload.

 Success rate

Why?

This goes without saying, but an automation that fails isn’t all that useful. That’s why
tracking the success rate is so important!

How?

You’ll want to aim for a success rate of around 90%. It’s surprising and seems
counterintuitive, but a success rate around 100% could mean that some failures aren’t
being correctly tracked.

 Duration

Why?

Similar to the success rate, there are often misconceptions about process duration. It’s
exciting to see that a process ran super quickly, but short runtimes might mean that an
automation failed.

2 - Business KPIs tie what happens in your RPA deployment (operational) to how it benefits your
company (business). These are the metrics that you can use to actually grow and scale RPA in your
organization.

 ROI

Why?

You’ll want to think of automation ROI in terms of at least two perspectives: hours
saved and money saved.

Let's say your business is dependent on a lot of time-intensive processes, like manual data
entry from PDFs.

9|Page
The speed with which employees can process and enter information is limited, even if
they're master typists. So, we'll assume it takes 15 minutes to process each PDF. With RPA,
this kind of manual data entry can be sped up to a matter of seconds.

Not only will this increase the number of PDFs processed per day, but you'll also free up a
lot of employee time for activities that can't be automated.

The hours spent by an employee have a cost, usually one much higher than that of a
software robot. Periods of high demand can be especially expensive to compensate
employees for. You're either paying extra for overtime work or finding, hiring and training
temporary employees you can't keep once demand returns to normal.

Robots, however, are scalable. When those labor-intensive periods come up, you can
automate the manual labor and utilize those savings in other areas.

How?

Robots can accomplish grueling manual tasks in minutes or even seconds. It’s important to
note how long a process would take a human to manually complete so that you can
compare this baseline to how long a Robot took to do the same thing. From here, it’s easy
to calculate the time saved by automation.

You can do the same thing to find financial savings by attaching a dollar value to an
employee's time.

Keeping the time in hours is the easiest calculation since most jobs have an hourly pay
rate.

 Process outcomes

Why?

RPA is used to get rid of mundane human tasks, so knowing what Robots have
accomplished for the business is paramount. Every automation is supposed to achieve
something, so knowing and defining that end goal is important.

Building on our previous example of manual data entry from PDFs, let's look at one of the
most common process outcomes: invoice processing.

You would most likely want to offer more competitive SLAs and, to this end, aim to reduce
the amount of time it takes for an invoice to be processed from the moment it is received
to when the amount is paid to a vendor.

With RPA, you can easily track how long this takes.

How?

This is where you want to look at the same metrics you were tracking before you used RPA
and apply your RPA results.

10 | P a g e
 In our invoice example, you'll need to compare the amount of time it took to process an
invoice pre-RPA and post-RPA.

What is UiPath Insights?

Insights is the analytics component of the UiPath Platform. It provides analytics capabilities by
using any combination of available business and operational metrics.

It allows you to build customizable views specific to your needs and priorities. It also comes with
several dashboard templates (Robots, Processes, Queues, and Business ROI) that are intended to
address immediate automation measurement needs from a business and operational perspective.

UiPath Insights was created to help you:

What are the key features of UiPath Insights?

Here's what makes UiPath Insights an end-to-end analytics solution:

11 | P a g e
Who is it for?
Insights is an end-to-end analytics solution for users across an entire organization. From business
users (Analysts, Process and Business owners, Executive leadership) that need to define, track,
measure and share process KPIs and business outcomes, to users across the Automation Center of
Excellence (COE Leads, RPA Developers, Solution Architects, Business Analysts, Project Managers,
RPA Operations Managers) with an interest in a holistic view of their RPA deployment.

Different stakeholders have different objectives with regards to tracking and measuring
RPA...Thus, when building Insights, we took into account the goals, needs, and tools required by
each strategic persona throughout the automation journey:

How can you access it?

UiPath Insights is available as a first-party cloud service in Automation Cloud, as a first-party service
available on-premises through Automation Suite, as well as a standalone on-premises product.

You can access it by signing up for our 90-day Enterprise Trial plan.

12 | P a g e
How does Insights fit into the larger picture of the UiPath Platform?
The UiPath Platform, the most advanced vehicle for scaling up your automation program, now
includes powerful analytics that measure, report and align automation operations with strategic
business outcomes.

The UiPath Platform covers all the stages of an RPA implementation and the deployment can be
done either on-premises, in cloud or using a hybrid approach:

 Discovering through Automation Hub, Process Mining, Task Mining and Task Capture tool.

 Building through the UiPath Studio family, Document Understanding, Integration Service
and pre-built automation components.

 Managing the automation ecosystem via Automation Cloud, Orchestrator, AI Center, Test
Suite, Data Service and—of course—Insights.

 Running it using the different types of UiPath Robots.

 Engaging the automation with human users via Assistant, Action Center, Apps and
Chatbots.

Automation analytics, provided to our customers through the Insights solution (either on-premises
or cloud) connects our platform's loop by enabling the ability to manage the automation, by
measuring it.

By measuring the performance of automation and the impact that it brings to their business,
customers will be able to advance towards the fully automated enterprise™.

Types of permissions
There are 5 types of permissions you can gain access to in Cloud Insights.

Viewer
This grants view-only permissions in Cloud Insights. Viewers will only be able to view the template
dashboards and dashboards shared by users with enhanced permissions and will not be able to
create their own.

They can not only see the dashboards, but also download them or have them sent as PDFs.

13 | P a g e
Designer
Users with this permission have edit/create/delete rights in Cloud Insights. Designers may edit
dashboards, create new ones, make copies of the templates to their “My Dashboards” section, or
delete dashboards.

Designers can also share with other users in the tenant.

Admin
An admin is a user who can configure Cloud Insights. Admins have access to User Management.
They are the only users with the ability to enter values for the Tenant ROI dataset. And they have
the same dashboard permissions as Viewers.

Admins are by default assigned to users in the Admin group in Automation Cloud. If admins are
expected to edit dashboards, they can be granted the Designer permission on top of Admin.

ROI Viewer and ROI Editor

ROI Viewer and ROI Editor are both auxiliary permissions. They must be added on to one of the
two main permissions: Viewer or Designer. Both these permissions are specifically created to
control who can see or make copies of the Business ROI dashboard template and who has access
to the ROI dataset.

Users assigned to ROI Viewer will have view-only access to the Business ROI template dashboard.
They will be able to interact with the dashboard, but they will not be able to copy it to their own
dashboard space (even if they have designer permission).

Users assigned to ROI Editor will have the ability to copy the Business ROI dashboard template into
their “My Dashboards” section. They will have access to the ROI baseline data, which will enable
them to build new widgets containing the numbers entered by the Admin for the ROI dataset. To
be assigned to ROI Editor, users must have the Designer permission granted first.

UIPath Apps

Simply put, low-code development means building software applications in a visual way. Instead of
writing lines of code, the development is based on drag-and-drop actions, pre-built components
and connectors.

This can have a huge impact on the speed of building and deploying applications. Low-code
development is expected to heavily influence digital transformation programs through the
democratization of business application development.

What makes UiPath Apps different?

Typically, low-code solutions facilitate the development of applications which only connect with
application programming interfaces (APIs). These are the standard ways through which
applications communicate and exchange data.

14 | P a g e
UiPath Apps takes it one step further by harnessing the power of RPA. Instead of connecting to
APIs directly, applications built with UiPath Apps interact with ready-made automations. The
automations have the full power of the UiPath Platform behind them and work across the widest
possible set of applications and data sources to get work done.

The Components of UiPath Apps

There are two components of UiPath Apps: the first is Apps and is the service used to execute
apps. The second one is App Studio and is the tool used to design the apps.

Let's take them one by one.

Apps
This is accessible from the left sidebar of UiPath Automation Cloud or UiPath Automation Suite (if
UiPath Apps is enabled on the tenant). When accessing Apps, you will see the list of all the
available applications. Depending on your permissions defined at app level, you can only run an
app or run, edit, export and delete it.

All the apps are enterprise-grade applications with modern user interfaces, mobile-friendly and
available cross-platform. They automatically scale and adjust to any form factor and can be
embedded onto existing software.

Moreover, UiPath Apps are Progressive Web Apps 10 (PWAs), which means they can be “pinned”
to your device’s homescreen and can be launched stand-alone. Thus, they give you a near native
experience without actually having to download or install anything.

App Studio
App Studio opens automatically when you create a new app or when you edit an existing app. App
Studio is a cloud-based web interface that requires no installation, being available from your local
browser. This enables anyone to build a functional presentation layer through drag-and-drop
actions and by linking the application components with automated processes published to
Orchestrator and with their parameters.

The design is done using building blocks, which are added, configured and customized in a "what
you see is what you get" (WYSIWYG), ready-to-deploy application.

15 | P a g e
With App Studio leveraging some of the capabilities of the UiPath automation platform, you can
develop the entire range of applications, from a simple visualization layer for a single automated
process to a complex application with multiple processes being triggered in a given logic and
complex data models.

Get Started With App Studio

All the development capabilities in App Studio are built around controls. These are the building
blocks of apps: you add them to the canvas, resize and customize them, then connect them to
the automations.

There are three types of controls:

Input Controls:
Allow human users to provide an input to the application. This can be a button to start a process or
a text field to enter the email address of a customer as an input parameter for the process.

Display Controls:
Display the outputs of an event run (the ticket number) or provide context for a human user to be
able to interact correctly with the app (for example, a label).

Container Controls:
Used to group several controls and/or to separate different parts of an user interface, for example
4 text fields displaying customer data.

Setting control properties

General:
This property category configures how the control is displayed, its function, the parameter with
which it is bound, and its state. Each control has its own particular properties.

Events:
This category allows the configuration of events and rules involving the control, such as triggering
a process, showing a message, opening an URL, and so on.

16 | P a g e
Style:
This property configures the look and feel of the controls such as border, font, margin and size.

Data binding
Once the presentation layer of the application is done by adding and configuring controls, you can
connect the controls to input and output parameters of the automated processes imported from
Orchestrator. This is called data binding.

What are Events and Rules in Apps Studio?

Events and Rules enable you to create increasingly complex apps. Events are recorded when a user
interacts with an app or control. Rules allow your app to take a predefined action when a certain
event occurs. This provides an efficient way to configure the behavior of your application on user
interactions, such as clicking on a button.

Events
As we have seen in the video demos, events are triggers that get activated when a user interacts
with an app or a control. Each control supports a single event, for example:

Event Controls

Clicked On Button, Header, Label, Icon, Image

Value Changed Checkbox, Date picker, Dropdown, Slider, Switch, Text Area, Textbox, List

Loaded Page, Table

Rules
Rules allow apps to take an action when a certain event occurs.
Let's recall a few rule examples that we have seen in the video demos:

Rule Description

Opens a page of the app as a pop-over or as the contents of a

Open a Page
page container.

Close Pop-Over/Bottom Sheet Closes the current Pop-Over.

Show Message Show a message as a toast notification.

Show/Hide Spinner Show or hide a spinner overlay to show the app as busy.

Start Process Starts an Automation Process.

Expressions
Expressions are made up of logical operations allowing you to transform, modify, and compute
the data within an app, returning a result used in the same app.

Let's look at several scenarios where they can be used:

17 | P a g e
  Process data stored in variables, outputs, and other control values from the Resources
panel.

 Concatenate pieces of text (strings).

 Perform comparative operations.

 Accommodate simple scenarios using the If function.

 Perform arithmetic operations.

 Control hidden, disabled, font/background color properties.

 Reference a selected record or field from another control.

How do expressions work?

Expressions rely on functions and named operators to perform operations. Expressions can be
used both in controls and rules in UiPath Apps.

Below you can find the out-of-the-box set of functions in the App Studio designer:

Functions
And / Or / Not

 Concat
 Contains
 EndsWith
 If
 IsBlank
 Length
 StartsWith

Named operators
Category Operator

Addition and subtraction +, -

Comparison <, <=, >, >=

Concatenation &

Equality ==, !=

Exponentiation ^

Logical &&, and, AND, | |, or, OR, !, not, NOT

Multiplication and division *, /, %

18 | P a g e
Working with Files and Persistent Data
Working with files stored in Orchestrator
Orchestrator storage buckets provide a per-folder storage solution for automation projects and
apps, thus removing the need for external storage.

By designing apps using this feature, you can upload new files at runtime or download files from
storage buckets.

How is this done in UiPath Apps?

The connection with the storage bucket is done through a specific type of control: the File Picker. If
the file referenced is an image, it will be shown as such inside the app.

Storage buckets are folder entities in Orchestrator, so access has to be configured at user level.

Working with UiPath Data Service entities

UiPath Data Service is the component of the UiPath Platform used for persistent data storage. The
integration between UiPath Apps and UiPath Data Service enables the development of apps which
use data stored as entities in UiPath Data Service.

There are different UiPath Apps functions and rules to interact with Data Service entities:

Functions
Filter

The function returns all records that result in true. These expressions can reference fields/columns
by name.

Example:

Sort

Sorts the rows of a given array or range by the values in one or more columns.

Example:

Lookup

Returns the first entity record that matches the condition.

Example:

19 | P a g e
New

Creates a new in-memory entity.

Example:

Rules
The Create/Update Entity Record can be configured when using any control within Apps. To
configure this rule, expressions need to be used.

This rule can accept the following inputs:

 A reference to the entity itself

 A specific entity to update

The Delete Entity Record can be configured in the case of any control.
To configure this rule you must use the Lookup function.

Action Center
Depending on the access type provided, users can either View or Manage activities as required.
Users will be configured in such a way that the right Human will enter the loop within the
automated process at the right moment, in the right place. In this way, all users can concentrate on
the task at hand without disruptions.

The login screen looks different depending on the connection made to the Action Center platform
via On-Premises or Cloud services. Nevertheless, the functionality of the Platform will be the
same.

Overview
As we might know by now, whenever a Human is required to perform an action within the long-
running business process a task will be created in Action Center. Once the input has been received
the Robot will continue to the next process steps.

Let's learn about the different stages of a task as it enters Action Center:

Unassigned action status

Once an action is generated for a Human user, it will be displayed in the Actions page with
the Unassigned status. This means that no user has been allocated to it.

For example: you might be involved in a long-running business process that at some point will
require Human intervention. At that moment the process is suspended, and the Robot asks for

20 | P a g e
intervention. This happens through the new task that is created and added in the "Unassigned"
task list. At that moment, you can assign the tasks to yourself or to a colleague.

Completed action status

The Actions page displays Completed status once our Human user completes an action.

Using the same example, after you either assigned the task to your self (or to a colleague) and it
has been completed, the activity will receive the "Completed" status.

This will allow the Robot to resume the automated business process.

Pending action status

The Action page displays Pending status when an action is assigned to a Human user.

Continuing the example, once the task has been created and you or a colleague has assigned the
task it will appear with the Pending actions list waiting to be picked up and resolved.

Most likely a queue of such items will form and will be completed in order depending on their
priority.

Action types
There are multiple ways of giving our Robot the data it needs to start or continue working on the
business process. Depending on the task, there are specific ways in which data can be added as
input. Let's look at a few methods of adding our responses in tasks.

Form tasks
Sometimes Robots will require data that only Human users posses. This data can be added
through the use of Input Forms. The form templates are created beforehand by RPA Developers
and the fields will be tailored to specific activities.

Tasks cannot be modified once they are completed. In our example, the data that is added into
the fields won't be editable after the "Submit" button is selected.

Document Understanding tasks

These types of actions will present the Human with information the Robot has been able to
identify in documents, after processing them automatically. There are two types of Document
Understanding Tasks:

 Document Classification Tasks where Humans validate the automatic classification

performed by the Robot.

 Document Validation Tasks where Humans review specific pieces of information that are
automatically identified by the Robot, and assigned to fields of interest for the use case.

21 | P a g e
External tasks
In more complex automation scenarios, RPA Developers can configure the way tasks are created in
Action Center by tying in the automated process external tools such as CRMS, reporting, or
management tools.

Actions and events performed in the aforementioned external applications can trigger task
creation or completion inside Action Center. Such tasks can be automatically populated with data
from external systems such as Jira or Salesforce or create completely new tasks once external
systems receive a specific status.

An example would be an automated business process where the Robot starts or resumes process
execution only after a Human adds a specific input to Jira for example. Once the required data has
been added or a system-specific Jira entry has been created (such a Jira Ticket), a trigger will signal
a task creation or completion in Action Center which will put in motion or resume the automated
business process.

Automation Ops
What is UiPath Automation Ops?
UiPath Automation Ops is a centralized, web-based development operations tool that enables the
configuration and deployment of governance policies for UiPath Studio family products and for
UiPath Assistant.

Automation Ops is an admin feature available in UiPath Automation Cloud, allowing admins to
enforce policies to the organization's employees.

Why you need it?

As companies scale automation development through Centers of Excellence and citizen
development programs, governance becomes more and more important. And the need for
governance may come in different shapes:

 What applications and websites users may or may not automate.

 What feeds users may install package from.

 What activities and packages may be used.

 Secure password practices in automation projects.

 What are the organization-wide development best practices and standards or tailored
department standards.

What is the scope of governance through Automation Ops?

Automation Ops grants you easy control over product use aspects like:

 Settings (e.g. Workflow Analyzer rules, sending feedback)

 Permitted package feeds

 Allowed activities and activity packages

22 | P a g e
  Applications and URLs that can be subject to automation

The possibility to reference Workflow Analyzer rules greatly increases the governance scope.

Once a policy is being defined and deployed, it guarantees its enforcement over the use of the
products selected (Studio Pro, Studio, StudioX, Assistant) by the organization's users. Moreover,
the possibility of enforcing policies per tenant, group, user and product offers a lot of flexibility for
larger companies with many groups of users with different needs and permissions.

Automation Ops is a natural step towards enterprise-scale governance capabilities, built on top
of the already existing file-based governance feature, made available in 2020.

Creating Policies
1. Access UiPath Automation Ops from the Admin page of UiPath Automation Cloud.

2. Under the Policies tab, click 'Add product policy'. Give it a name and choose the product
for which it will apply.

3. Once the policy is created, you can change the name, the availability and the priority from
the upper tab. The availability dictates for how long a cached policy will apply if the
product fails to connect to Automation Ops.

4. Policies can be configured from the five tabs:

o Design: to enforce the policy, set both “Enforce Analyzer before Publish” and
“Enforce Analyzer before Run” to “yes”.

o Features: configure general behaviors that cannot be configured by the users, like
“Allow users to send feedback” or the “Getting started” screen.

o Manage Sources: control the feeds that appear and the rights of the users e.g., to
add others, to enable or disable the existing ones.

o Workflow Analyzer: customize any Workflow Analyzer rule by enabling it, choosing
the default action and configuring its parameters.

o Location: control the locations where automation projects are stored locally.

Deploying Policies
With Automation Ops, you can deploy policies at tenant, group, and user level, for each product.
Policies deployed at tenant level are applied to all the users in that tenant. For more granularity,
you can apply different policies to specific groups or specific users. Deployments defined at user
level override deployments at group level, which in turn override those at tenant level.

23 | P a g e
When no policies are selected at these levels, there are default options in place. The default option
at tenant level is No Policy, while at group and user level it's Inherit (from the higher level - user
inherits from group and group inherits from tenant).

Steps to deploy a policy from Automation Ops

1. From Automation Ops, access the Deployment tab, consisting of three second-level tabs -
Tenants, Groups and Users.

2. In the Tenants tab, you can select a different policy applying for each type of license (for
example, RPA Developer) and each product the license type grants access to (for example,
StudioX). The default option is 'No policy'.

3. In the Groups tab, you can configure policy enforcement at Automation Cloud group level,
again per product. You can add existing groups and edit the ones that were previously
added. This time, the default option is 'Inherit (Tenant)'.

4. In the Users tab, you can deploy policies to individual Automation Cloud users, per
product.

How are policies applied based on the options set at tenant, group
and user level?

 When a policy is deployed at user level, the policy is applied to the user.
o If a policy created in Automation Ops is selected, the policy overrides any policy
deployed at group or tenant level.
o If the No Policy option is selected, the product is not governed by Automation Ops
for the user, overriding any policy deployed at group or tenant level.
o If the Inherit option is selected, the policy defined at group level is applied. If one
does not exist, the tenant-level policy is applied.

 When Inherit is defined at the user level:

o If the user is part of a group and a policy is deployed at group level, the group
policy is applied to the user.
o If a policy created in Automation Ops is selected, the policy overrides any policy
deployed at tenant level.
o If the No Policy option is selected, the product is not governed by Automation Ops
for the user, overriding any policy deployed at tenant level.
o If the Inherit option is selected, the policy defined at tenant level is applied.
o If the user is part of multiple groups where a policy is deployed, the group policy
with the highest priority is applied to the user (the lower the priority value, the
higher the priority of the group policy).

 When no policy deployment is defined at user or group level, the policy deployed at tenant
level for the product is applied to the user.

24 | P a g e
 o If the No Policy option is selected, the product is not governed by Automation Ops
for the user.

Uploading Policies

1. From UiPath Studio, go to the Help tab in the backstage view and select Generate
Governance File. This comes with two options: Classic Policy and Modern Policy.

2. The main difference between the two comes from the fact that the Classic Policy is a single
file, while Modern Policy comes as three different files, one for each profile - StudioX
(Business), Studio (Development) and Studio Pro.

3. To upload a governance file, simply go to the Policies tab of Automation Ops and click
Upload. Once it is uploaded, you can edit it the same way a policy created in Automation
Ops is edited.

4. Uploaded policies are deployed the same way as the policies created in Automation Ops.

Only modern policies can be uploaded in Automation Ops.

Data Service

What is Data Service?

The UiPath Data Service is a persistent data storage service bringing powerful no-code data
modeling and storage capabilities to your RPA projects. In other words, it offers the capability to
define relational business objects and store records on the Automation Cloud.

What are the key components of Data Service?

Let's take a moment to get familiar with the key components of the Data Service :

 Entities

 Fields

 Relationships

 Records

Below you can see a schema created in Data Service. Click the markers below to learn more about
each component.

25 | P a g e
How do you use Data Service?
So you've decided you want to use the data modeling and storage capabilities of Data Service. Here
is a brief overview of the steps you would need to take.

In UiPath Data Service

 1 - Access Data Service on the UiPath Automation Cloud. If needed, enable Data Service.

 2 - Create your Entities.

 3 - Create your Fields for each Entity and set field types and relationships.

In UiPath Studio

 4 - Import your Entities into a dedicated namespaces in UiPath Studio. You can do this by
using the Resources panel or the Manage Entities ribbon option.

 5 - Create variables and arguments using your entities as variable types. Use them to store
and pass business data in your project.

 6 - Install the Data Service Activities Pack.

 7 - Use the new activities to create, query, modify or delete records upon process
execution.

In UiPath Data Service

 8 - If needed, edit your Entities, Fields or Records in Data Service.

What are the benefits of using data service?

 Secured, persisted, and accessible storage that enables you to keep all your data in a
dedicated place.

26 | P a g e
  Reduce the number of variables in your processes and work with rich consistent entities,
customized for your business needs.

 Seamlessly access your entities, records, and documents.

 Store completely new and also existing data.

 Define, modify, and extend business entities and store records for those entities.

 Define rich metadata like relationships, rules, attributes for your entities, and store
documents associated with the defined entities.

Creating Entities in Data Service

Note that Entities are created from Data Service, which is accessed from the Automation Cloud.

The following requirements need to be met in order to use Entities in Data Service and Studio:

 You first need an Automation Cloud account.

 UiPath Studio 2020.8 or higher Enterprise or Community edition;

 UiPath Assistant or Robot connected to a Modern folder in your cloud account;

 Data Service enabled for your tenant.

Using Entities in Studio Projects

 We've imported our entities to the project using the Resources panel and the Manage
Entities option.

 We've replaced the out arguments in the Get Olympics Information workflow with the
argument based on the imported entity Olympics Edition.

 Note that Entities must be initialized using the New Operator, read from the Data Service
or passed through an input argument in a workflow before usage, otherwise assigning or
reading their values can cause errors.

 To address a field of a variable of Entity type in an Assign activity, we've used the
expression: [Link].

 We've replaced the arguments in the Get Medals and Show Medals workflows using the
new arguments based on the Olympics Edition and Nations Results entities.

 We've ran the process to see it in action.

27 | P a g e
Storing Values in Data Service
 We've installed the UiPath Data Service Activities package.

 We've used the Create Entity record activity to store records in Data Service from our
process.

 We've used Query Entity records to identify potential duplicate entries and add only
unique records.

 We've updated an entity in Data Service and re-imported it in our project.

28 | P a g e
License Allocation and Management
UiPath Data Service usage is included in all Robot or Studio-enabled licenses and includes two
levels of service:

 Community—free of charge

 Enterprise—paid

The amount of data storage available, the instances size requirements and the allowed number of
Data Service API calls vary depending on the type of license you acquire.

License Level Details

Allowed Data Service usage is expressed in Data Service Units (DSU). Each Data Service Unit grants
a certain amount of data storage, attachment storage, and a maximum number of API calls per day.

Community License
A Community license has a fixed Data Service Unit assigned which can only be enabled for a single
tenant.

Below is an overview of what is included

Data Storage Attachment Storage Maximum API calls per day

100 MB 500 MB 1,000

Enterprise (including Enterprise Trial)

Your Automation Cloud account is granted one Data Service Unit for each of the following licenses:

 Action Center

 Attended

 Automation Developer

 Citizen Developer

 RPA Developer

 RPA Developer Pro

 Process Mining Developer

 Test Robot

 Unattended Robot

Below is an overview of what is included in a single Data Service Unit

29 | P a g e
 Data Storage Attachment Storage Maximum API calls per day

1 GB 5 GB 10,000

After you enable Data Service, you can allocate up to the maximum amount of Data Service
available units. You can change the number of assigned units later on.

Provisioning Data Service Tenants

IMPORTANT: The license type for a Data Service tenant is the license type of the account at the
time of the tenant creation.

When upgrading a Community account to an Enterprise (or Enterprise Trial) account, your existing
Data Service tenant is restricted to the community storage and API call limits.

To leverage the storage and API calls available to your Enterprise (or Enterprise Trial) account, you
need to create a new Data Service tenant.

License Workflow
This is how the license structure works:

 Your Automation Cloud account has different licensing quantity parameters for each
service that can be attached to the platform.

o This means that, based on those quantity parameters, you can add one or multiple
services to your Automation Cloud account.

 When enabling the Data Service for a tenant, you must assign one or more DSUs to it.

The details of the total and allocated Data Service Units can always be reviewed. Depending on
your role,

 Users can access Automation Cloud > Home page > License Allocation;

 Organization Administrators can access Automation Cloud > Admin Page > License
Allocation > Other Services.

Check the License usage page for details.

The license is freed up if:

 the tenant is disabled;

 the tenant is deleted;

 Data Service is removed from an existing tenant.

30 | P a g e
Process Mining
Process Discovery
Process discovery is a set of tools and techniques that help us understand how business processes
are executed. Ultimately, using process discovery solutions like UiPath Process Mining, we want to
transform sub-optimal processes into more efficient ones.

How can we build a healthy transformation pipeline?

In the process of transitioning from a legacy to a digital-first company, the scope of change may
include people, systems, processes, and even attitudes and beliefs. And at every level of change, a
healthy transformation pipeline is needed.

For processes, a healthy transformation pipeline always starts by having a transparent view of how
processes look like today. Using process discovery, we can get insights on our as-is processes and
use these insights to define and implement the to-be.

Process mining for big and general processes and task mining / task capture for specific tasks inside
the processes

31 | P a g e
32 | P a g e
What is Continuous Discovery?
Continuous Discovery is a value-based approach that enables you to innovate in order to meet
your targeted process and business key performance indicators (KPIs) by combining discovery and
automation technologies.

What are the stages of Continuous Discovery?

How Discovery products work together?

Here are the products with which UiPath enables Continuous Discovery.

 UiPath Process Mining - Compiles and analyzes data from business systems and systems of
record to identify the end-to-end process as it's currently executed.

 UiPath Task Mining – Analyzes the work the people do on their desktops while executing
their processes.

 UiPath Communications Mining – Enhances the data models with insights from business
interactions like email or customer requests.

 UiPath Automation Hub - Epicenter of the automation program where ideas for process
and task automation are published and managed through their automation lifecycle. It
accelerates the time to automation, effectively documents the automation program, and
helps optimize processes based on the KPI impact and the ROI.

33 | P a g e
Test Suite
Types of testing

34 | P a g e
Phases of the testing

Test Levels

Test Suite
Components

35 | P a g e
Software development and testing process cycle

UiPath Test Manager

It's the component of the UiPath Test Suite used for managing test projects and test requirements,
referencing test cases and handling the execution of manual testing. Another important function is
managing test results for supporting the decision process.

UiPath Test Manager consists of the web application and the hub or server. The server integrates
directly with UiPath StudioPro and UiPath Orchestrator and can be integrated with third party
Application Lifecycle Management (ALM) tools, such as Jira.

Main functional areas

 Creating test projects.
 Creating or importing test requirements.
 Managing test cases and assigning them to test requirements.
 Assigning automation from UiPath StudioPro to test cases.
 Creating and documenting manual test cases. The manual steps can be recorded in real-
time with UiPath Task Capture.
 Creating and executing manual test sets.
 Displaying test results in dashboards and reports.
 Creating defects from test results.

36 | P a g e
Relationship Between The Different Types Of Assets

SAP Automation
What is an endorsed application?
SAP Endorsed Apps are a category of solutions from SAP's partner ecosystem to help customers
become best-run, intelligent enterprises. Endorsed apps complement and
extend SAP products and are meant to deliver value with desired outcomes – quickly,
easily, and with support from SAP. To know more about it, visit the SAP blog(opens in a new tab).

What does this certification mean for UiPath?

This certification showcases the strong relationship between UiPath and SAP and ensures that
customers can trust the quality and performance of UiPath solutions when used with SAP systems.

 It ensures that our integration with SAP is reliable and trustworthy.

 Certified solutions adhere to SAP standards for technical implementation, which means
our solutions are aligned with industry best practices and technical requirements.

 SAP certification serves as proof of the quality of our product, demonstrating that UiPath
solutions are thoroughly tested and validated for SAP integration.

What does this certification mean for UiPath and SAP clients and
partners?
 Accelerate Migration to the Cloud
 Automate Across All Your Enterprise Systems
 Discover a Fast and Proven Path to Value

37 | P a g e
Processes Examples

SAP WinGUI automation with UiPath

View of SAP WinGUI ALV Table.

Best practices when automating SAP WinGUI

38 | P a g e
  Use the [Link] package version 23.4 or above (latest version
recommended) for optimal compatibility and support.

 Utilize wildcards and regular expressions within selectors generated for SAP WinGUI
elements, providing flexibility when identifying UI elements within SAP applications. This
approach ensures that your automation remains functional even as elements evolve over
time.

 SAP WinGUI selectors can employ technical IDs, Text, Tooltip, and Type of SAP control
attributes for identification purposes, granting more precise control when working with UI
elements.

 To navigate the SAP toolbar button menu, leverage the "Click Toolbar Button" activity. This
activity grants you access to manipulate all buttons and their sub-menus within the SAP
toolbar. Seamlessly interact with different menu options to navigate through SAP's
functionalities.

 The "Select Dates in Calendar" activity allows you to efficiently choose individual days, day
ranges, or specific weeks within the SAP calendar. After indicating the SAP calendar, you
can use this activity to interactively and accurately select the desired date ranges.

 Simplify tab selection within SAP using the "Select Item" activity. When working with tabs,
the "Select Item" activity directly presents all individual tab options as selectable choices.
This eliminates the need for complex selector configurations and enhances the ease of
automating tab navigation.

 Enhance data extraction precision by customizing column names during extraction using
the XAML editor within the Data Scraping activity. You can indicate the desired column
name, whether it's the longest, shortest, or the displayed name at the time of extraction.
This feature streamlines data extraction and organization.

SAP WebGUI and SAP Web Dynpro automation with UiPath

39 | P a g e
SAP WebGUI, also known as SAP GUI for HTML, allows users to access SAP functionalities and run
SAP transactions directly from a web browser, without installing any SAP front-end software.

SAP WebDynpro interface.

SAP Web Dynpro is a UI development framework provided by SAP for creating web-based
applications within the SAP NetWeaver ABAP environment. It provides users a rich user interface
featuring drag-and-drop blocks to create custom UI screens.

Web Dynpro provides seamless integration with SAP backend services, allowing developers to
easily access and manipulate data from SAP systems.

SAP Fiori automation with UiPath

SAP Fiori is a web interface design system which provides users with a consistent experience for
SAP technologies across platforms and devices, being at the core of SAP's product experience.

40 | P a g e
Automation projects for SAP Fiori can be created out-of-the-box using UiPath, eliminating the need
for dedicated SAP extensions or activities.

UiPath supports SAP Fiori versions 1.52 and above, which are currently maintained by SAP.

SAP automation across all SAP non-visual interfaces - SAP BAPI

The SAP BAPI Activities pack offers a powerful set of tools that allow RPA developers to seamlessly
invoke SAP Business Application Programming Interfaces (BAPIs).

The package comes with a scope activity, SAP Application Scope, that enables the user to connect
to a SAP system and use a Invoke SAP BAPI activity to invoke a specified BAPI.

41 | P a g e
Benefits of automating SAP non-visual interfaces
 Up to 50x Speed: Direct API access enables faster automation execution compared to
traditional UI-based automation.

 Low Maintenance: Stable API interfaces require less maintenance, ensuring lasting
efficiency in your SAP automation projects.

 Super Robust: By skipping the full UI tech-stack, automation projects become more robust
and less prone to potential disruptions caused by user interface updates.

 Scalable: Direct API access allows automation to run in containers without UIs, making it
easier to scale the solution in line with business requirements.

 Performance: Eliminating the need for resource-heavy UI components leads to improved

overall performance in SAP automation projects.

 Unattended: API-based automation does not block the PC while executing, enabling
unattended automation without interfering with user activities.

 Easier Rollout: Robots do not need UI technology installed, simplifying the deployment of
SAP automation projects.

42 | P a g e