openSAP

Enter Next-Level Bot Building with SAP Intelligent

RPA 2.0
Week 1 Unit 1

00:00:05 Hello and welcome to our openSAP course How To Build Bots with SAP Intelligent RPA 2.0.
00:00:13 My name is Alexandre Fortin and I am a product manager at SAP Intelligent RPA. The goal of
this course is to provide you
00:00:21 a detailed solution overview and step by step tutorials on how to create a bot, from capturing
application to automation design and deployment.
00:00:31 So with that, let's see how the course is structured. The course will cover five weeks and an
additional week for the final exam.
00:00:40 During the weekly assignment after each course week and the final exam at the end of the
course,
00:00:46 you can collect points in order to obtain a record of achievement. You must score half of the
available points through the course.
00:00:55 Let's have a look at how the course content is going to be provided. We are a group of experts,

00:01:01 we will present the course units to you. In week one, we will give you an overview of the
different components
00:01:07 of SAP Intelligent Robotic Process Automation and getting started with them. In week two, we
will discover how to build bots with the cloud studio
00:01:17 by using automation, data input and output, and by reusing the store content. In week three,
we'll go deeply by capturing screens and new elements of your applications.
00:01:29 We will also talk about the modular aspect of automations, custom code, and how to use APIs
in your project.
00:01:37 In week four we will talk about how to leverage Excel, Word, Outlook, or PDF within your
projects.
00:01:44 In week five, we will close the course by giving you an overview of the different connectors that
can access SAP GUI, SAPUI5,
00:01:53 or simply access all desktop-based applications. And we will conclude with a summary.
00:02:00 And then week six will be your final exam with questions, and it covers the complete course
content.
00:02:09 The course will also provide the possibility to redo all the steps shown to you in your own
systems.
00:02:17 These exercises are an optional element of this course and are not part of any assignments.
After this short introduction.
00:02:26 Let's get started with week one. Let's define what Robotic Process Automation is.
00:02:34 Robotic Process Automation accelerates the digital transformation of business processes.
RPA will automatically replicate all tedious actions
00:02:44 to free up human workers for more high-value tasks. RPA is usually delivered in two ways.
00:02:51 The unattended mode, in which the bots are working autonomously with only human
supervision.
00:02:58 And in attended mode, bots will work with humans to assist them, to help them. Now, let's talk
about how SAP Intelligent RPA aims to deliver business value.
00:03:16 We generate business value by improving operations, by gathering resources for more high
value tasks at lower cost.
00:03:25 We increase the service quality typically by reducing the processing times, such as revenue-
generating transactions like purchase orders.
00:03:34 Our solution is compliant with your infrastructure. We leverage existing applications and
existing landscapes.
00:03:41 Another important aspect is about increasing the compliance, reducing human errors that can
often happen with unpredictable activity peaks for so many reasons.
00:03:53 And last but not least, we can provide a quick return on investment as our solution can be
implemented in just a few weeks.
00:04:04 What are the typical use cases and the return from our customers? Some examples.
00:04:11 Reducing 75% of the workload. Going 50 times faster for the processing speed.
00:04:18 Making the financial closing at a global scale with more than 100 subsidiaries, which leverage
automation every month between two and four times faster
00:04:29 during the closing tasks. Improve the user experience by combining SAP Intelligent RPA with
00:04:36 SAP Conversational AI and Service Ticket Intelligence. And these are just a few examples.
00:04:44 Extracting data from various connectors, downloading various reports, and many other
activities can be achieved with SAP Intelligent RPA.
00:04:56 We often think about the kind of task that is complicated, complex, which takes a significant
amount of time.
00:05:05 Yes, RPA can take care of this task, of this process. But what about all the tasks that are not
so complex, not so complicated?
00:05:18 Users tend to forget all the simple tasks, hidden and repetitive. You can focus on the tedious
process.
00:05:26 On the other hand, you could consider working on the short tasks, which last five minutes, but
40 times.
00:05:34 Well, five minutes by 40 times, it's more than three hours in a day for just one person.
00:05:41 And at the end of the day you've got something, because small steps can make big changes.
00:05:49 Here, a use case without a robot. Someone needs a new laptop, a software license or any
type of equipment.
00:05:57 Until now, he has been used to sending an e- mail to the support team describing the request.
On the support side, an asset management application is used to manage requests.
00:06:10 And, you know, the kind of powerful application overcomplicating handling a simple request. In
the end, the request takes ages.
00:06:21 The internal customer is just waiting. The IT department would like to improve this.
00:06:27 They created a simplified form, hosted in a simple Web app. The user would need to fill out the
form and that's it.
00:06:35 However, the problem is still the same. There is no link between the Web app and the asset
management system.
00:06:42 The user needs to copy and paste all the information between the two systems and for all
incoming requests.
00:06:52 And there is here the robot in the picture. On one side, the Web app.
00:06:58 On the other side, the asset management system. Every morning the robot alone creates more
than 100 requests in the system
00:07:07 and it gives a report on what has been done. The support team can focus on high-value tasks.

00:07:14 That's it. To finish with this example, the asset management system is still here,
00:07:22 with its relevant screens. Web services or API are a pretty good idea, but need a long time to
develop

2
00:07:31 because of all the mandatory checks to be taken into account. The migration is no longer
identified for the moment.
00:07:39 We found this case because the time and the budget were both lacking. Time and budget are
often key points to promote robots.
00:07:50 Another good example is the purchase order creation. The purchase department receives a
purchase order through e-mail on a daily basis.
00:08:00 The first filter is needed for various reasons. Once filtered, the team needs to identify
00:08:08 the products, quantity, the customer, and so on. If you have only one product to sell, it's fine.
00:08:17 The list is somehow defined, you can enter in your system, you launched the corresponding
transaction, navigating the screen,
00:08:25 looking for all the mandatory fields, and so on. Done?
00:08:31 Perhaps. But the team would need to do it again and again and again.
00:08:40 And here is how the automation could handle this process, this task. You have a robot that will
first read the spreadsheet row after row.
00:08:52 All the files will be translated to the corresponding transaction in your favorite ERP system.
00:08:59 Once put in place, it will continue to work to help the team. For the last slide, we can
summarize the use case criteria.
00:09:13 The first is related to manual and repetitive actions. When you find there are many actions
often done by many employees,
00:09:23 automation should be considered. The second is volume,
00:09:28 taking into account hundreds or thousands of files in a day or even by many people should
lead to thinking in terms of assigning this task to a robot.
00:09:41 It's easy for a user to switch from one application to another. Imagine where there is there are
10 or 15 applications to drive,
00:09:50 collecting and entering data. If you can hide this complexity
00:09:54 by automatically coding the required applications, this will help the user's life.
00:10:01 And last but not least is the ability to help an application that is a bit boring to use from time to
time.
00:10:09 It's a legacy application and nobody wants to update it, to replace it. Too many useless
screens containing useless data.
00:10:19 But never mind. Robots have here to clean up this place,
00:10:24 only picking up the mandatory data, and let the user do his job with more accuracy. This is the
end of our unit.
00:10:34 Thank you for watching. In the next unit, we will present an overview of the solution and the
tools.
00:10:41 Thank you.

3
Week 1 Unit 2

00:00:06 Hello again. In this unit, we'll present an overview of the situation and the tools.
00:00:14 Some key concepts of Intelligent RPA. It comes often with the unattended bot/the digital
walker.
00:00:22 From a technical standpoint, it is deployed on server. It will be executed through a schedule or
trigger.
00:00:29 And from a functional standpoint, it aims to lower manual processes - often repetitive with
lower added value.
00:00:36 When well identified and designed, it could cover a whole process. For example, automate
purchase order.
00:00:45 On the other hand, we often talk about attended bot/digital assistant. From a technical
standpoint,
00:00:51 it is deployed on the user workstation triggered by your user. The goal from the functional
standpoint is
00:00:59 to ease manual processes, simplify them, increase the user performance. Some areas of the
process can be automated, but at the end the user is in control.
00:01:13 And what is Intelligent RPA without orchestration, without control? We provide a solution that
is accessible with simply an Internet browser,
00:01:22 a cloud-based solution for managing all process automation resources. And have you
identified an end-to-end process, maybe simple
00:01:31 with few decisions to take, or even complex? It needs to be design.
00:01:37 Process automation requires a design phase. All authoring tasks related to process
automation
00:01:43 are performed during this phase. It starts with capturing application, build workflow, and much
more.
00:01:52 In your company landscape, you have servers, business applications that were purchased,
customized, or developed.
00:02:00 Your company has in the meantime started to use cloud services with different flavors like
Performance as a Service, Software as a Service, Infrastructure as a Service.
00:02:10 Some of these applications are interconnected. Some are not.
00:02:15 And maybe you will ask, "Who is making the glue between applications not connected?" Who
is going to enter again and again duplicate information?
00:02:24 The user. SAP Intelligent Robotic Process Automation comes with two main components.
00:02:32 The first is responsible for orchestration, monitoring, and authoring. It's a cloud-based solution
powered by SAP Cloud Platform,
00:02:40 with no deployment required, with simply a Web browser. The second is responsible for
executing the process automation,
00:02:49 a line of business can run as attended mode. If some processes can run in a way that direct
human interaction is not required,
00:02:57 we are talking about unattended mode, digital walker mode. Both components will be linked
with the cloud securely.
00:03:08 SAP Intelligent Robotic Process Automation is a robust and scalable solution.
00:03:14 Its functional coverage is able to solve both attended and unattended new use cases.
00:03:18 Using JavaScript language, it makes it even easier, from a development standpoint, to jump to
a project.
00:03:26 The framework is fully extensible. One key element of the open mindset is two third parties -
00:03:32 native Windows applications and legacy applications are already working out of the box.
Virtualization protocols are also working,

4
00:03:40 making communication between application and bot very efficient. It works for simple projects
or even complex projects
00:03:48 involving a large number of screens, application types. Today, you start with the project, but it
could require changes over time.
00:03:58 Thanks to its robust scripting language, modification can be tracked. UI elements are clearly
identified thanks to a powerful graphical design,
00:04:07 and debugging can be done locally or even remotely. Once your project is ready,
00:04:13 deployment to workstation does not require significant memory consumption. Also, compared
to other solutions in the market,
00:04:20 fast response time is a key differentiator. Desktop agent is able to work with a wide range of
applications and technologies.
00:04:31 SAP applications such as SAP GUI, S/4HANA, SAPUI5, Web applications, custom
applications we built with native Windows APIs,
00:04:40 Java-based applications, terminal applications, and so on. And access to dedicated
applications, such as Microsoft Office.
00:04:47 Web Services protocol can be used to talk with on-premise or cloud-based solutions. To do so,
the agent is using a powerful and extensible script language
00:04:59 based on JavaScript. For each technology,
00:05:02 drivers, connectors have been developed to work as closely as possible with them. The agent
will simply leverage the user profile, the Windows credentials.
00:05:13 Once installed, administrator privileges will never be required. Also agent is available within
SAP Cloud Platform
00:05:27 in the different data centers around the world, all the time. With more than seven languages,
00:05:33 we have a lot of resources to share with you. And here are the main cloud components,
00:05:41 cloud factory, cloud studio, and the store. Cloud factory is a main piece for orchestration and
monitoring,
00:05:51 updated on a regular basis. With each release, new features and capabilities are added or
even improved.
00:06:00 Today, the factory is responsible for managing agent groups, managing all logins, managing
environments, development, test, production,
00:06:09 import or deploy packages from the studio, and monitor job execution. Cloud studio aims to
assemble existing desktop packages
00:06:20 and use behind the scenes an SAP workflow. You can use your tasks and workflow inbox to
get user feedback or validation
00:06:28 without running an agent. An assembling scenario uses low-code or no-code paradigms.
00:06:36 Cloud studio brings a Web-based authoring client for creating desktop automations.
Application can be captured
00:06:43 using behind-the-scenes Windows-based agent and a browser extension. A graphical designer
is available without plugin.
00:06:51 Complex authoring is doable using the low-code, no-code paradigms. However, coding is still
doable if needed for advanced users.
00:07:00 Test and validation are also doable using an online tester. The store is the channel for all
prebuilt content.
00:07:11 You can search, browse, or filter content. You can take a look at the content before
downloading,
00:07:17 and once downloaded, it will be available directly within your tenant, making use and
deployment very easy.
00:07:27 Here are the on-premise components - desktop agent, the browser extension, and the desktop
studio.

5
00:07:36 Desktop agent is a key component responsible for executing the automation within a
workstation or a server.
00:07:44 Bots can be delivered in attended or in unattended mode. Connection is established from the
agent to the cloud using SSL and WebSocket protocol.
00:07:56 Once the session is established, distribution of jobs or projects is transparent and automated
from the factory.
00:08:08 The desktop studio is a suite of tools with an integrated development environment,
00:08:13 focusing on process automation development. It covers, from the specification and
development perspective,
00:08:20 an application capture, a code editor, a workflow designer, and many more. Through its built-in
debugger, local or remote tests are doable.
00:08:30 But the desktop studio covers both application capture and workflow design. And for more
details about it,
00:08:36 I would recommend to watch our previous course: open.sap.com/courses/rpa2 SAP Intelligent
Robotic Process Automation aims to accelerate digital transformation
00:08:51 by automatically replicating actions that have lower added value. It provides a suite of tools,
cloud and on- premise.
00:08:59 and a growing ecosystem, which can work for both attended and unattended usage. It works
with a wide range of applications and technologies.
00:09:09 It is powered by SAP Cloud Platform, machine learning, and AI. And that's all for the solution
and tools overview.
00:09:16 In the next unit, we will do an end-to-end demo.

6
Week 1 Unit 3

00:00:05 Welcome to unit three, Onboarding and Tenant Administration. My name is Simardeep Singh,
and I work as a software developer
00:00:14 in the SAP Intelligent Robotic Process Automation team in Walldorf. This unit will present
different steps you will need to follow in order to set up
00:00:25 a running environment for all your RPA projects. So let's start.
00:00:33 From the moment you decide to use the SAP Intelligent RPA solution to the moment you
create your bots, you will have to execute some actions
00:00:43 so that you can use our tool in SAP Cloud Platform. It will start with the creation of trial account
and then the service subscription.
00:00:53 After having subscribed to the service, you will create a service key and manage the access
rights.
00:01:00 So let's have a look into the first step. The trial account for the Cloud Platform can be created
by following the link shown in the slide.
00:01:12 Fill the form to create the account. Once the registration is complete, a trial account will be
created.
00:01:19 Remember to add a phone number that can be used to receive a passcode for a login. To start
using the trial account, you will have to verify your e-mail.
00:01:36 Your SAP user ID will be generated on successful verification of the e-mail. Now you can click
the "Click here to start your trial!" button.
00:01:52 On the verification that the trial account was created successfully, a subaccount will be created
containing organization and space.
00:02:01 But at this point, one might ask, "What is a subaccount?" So, a subaccount, it lets you
structure a global account
00:02:11 according to your organization and project requirements. But with regard to members,
authorizations, regions, and quotas.
00:02:22 Each subaccount is independent from other subaccounts. So next step, after getting the trial
account,
00:02:32 is to subscribe to the SAP Intelligent Robotic Process Automation service. To do that, select
the subaccount and open the subscription step.
00:02:45 Once the subscription step is open, just click on Subscribe
00:02:49 and you will be subscribed to SAP Intelligent Robotic Process Automation. To access the SAP
Intelligent Robotic Process Automation public APIs,
00:03:02 you need a service key from the service instance in SAP Cloud Platform cockpit. Create an
instance of the Intelligent Robotic Process Automation service
00:03:13 from SAP Service Marketplace. On the successful creation of the service, create a service as
shown in the figure.
00:03:33 In order to manage the exercise, we need to detail how it works. First, a user can access a
subaccount only if there is a dedicated trust relationship
00:03:46 between the subaccount and the identity provider. An identity provider could be an SAP ID
service or any SAML 2.0 provider.
00:03:57 The access rights in the applications are based on roles. In our case, the roles are defined by
SAP Intelligent RPA,
00:04:05 and a user is not allowed to modify them. So you think like, what's the point?
00:04:13 So now the point is each role can be put inside the role collections. So that means you can
create a role collection,
00:04:20 a user-defined custom role collection, where you can put in all the roles required, and then you
can assign that role collection to any user.

7
00:04:32 So a user can be assigned one or more roles, so these roles can be put inside the role
collection
00:04:39 and the role collection can be assigned to a user. So if you see here the IRPA Officer,
00:04:46 it has the complete capabilities, or you can say it has access to all the capabilities to manage
and run the SAP Intelligent RPA software.
00:04:58 So if a user is assigned a role collection containing the IRPA Officer role, that means that user
will have all the access to control the SAP Intelligent RPA.
00:05:13 So to create a role collection, you need to specify your name and a description,
00:05:18 and then you link a role to the role collection. To link a role to the role collection,
00:05:26 you must select the application identifier. An application identifier can be easily identified
00:05:33 by just seeing a substring, which is uaa-ipa. So that means when you link a role to the
collection
00:05:41 and then you select the application identifier, look for the keyword uaa-ipa in the URL,
00:05:47 and then save the role collection after the assignment. Access to the different functionalities is
granted
00:05:56 using the Trust Configuration option, which is present inside the security for the subaccount.
00:06:11 So, to select, you just select the identity provider by clicking on the name,
00:06:17 use e-mail address to show assignment. If the user is not added to the identity service, it will
prompt to add the user.
00:06:26 Once the user is added, you can assign the role collection, which we created in the previous
steps.
00:06:35 And with this, you have successfully created an environment to use the SAP Intelligent RPA
solution.
00:06:43 Let's see a quick demo to see how we set up the environment, and it will go through all the
steps we already discussed.
00:06:53 Click on Enter Your Trial Account. Here you can see a trial subaccount already created.
00:07:01 Click on the trial subaccount to subscribe to the SAP Intelligent Robotic Process Automation
service.
00:07:09 On the left-hand side, you can see the Subscriptions tab. Click on the Subscriptions button.
00:07:16 Inside Subscriptions, you can view all the subscriptions provided by Cloud Foundry.
00:07:22 Let's search for "robotic process automation". Click on the tile
00:07:27 and then click on the Subscribe button to subscribe to SAP Intelligent Robotic Process
Automation.
00:07:40 So now we are subscribed, the next part is to get the service instance so that we can access
the public APIs
00:07:48 provided by SAP Intelligent Robotic Process Automation. To do that, let's go inside Spaces.
00:07:57 Here you can see a dev space already created. Click on the dev space,
00:08:02 and on the left-hand side, go inside the Service Marketplace Here, search for SAP Intelligent
Robotic Process Automation service.
00:08:28 So this service enables access to the public APIs. So let's create an instance of this service.
00:08:42 By default, the service plan is "standard". Choose a specific instance name,
00:08:47 let's name it "demo-instance", and do "Next", "Next", and then we do "Create Instance".
00:08:59 So once the instance is created, we require the client ID, secret, and auth URL.
00:09:04 To obtain all those credentials, we have to create a service key. So inside the demo instance,
00:09:11 click on Create Service Key and provide a service key name. Let's name it "skey".
00:09:20 And then click on the Create button. So now our service key is automatically created,
00:09:28 you can view this service key to see the client ID, secret, and authorization URL. So these
parameters are required when you want to access

8
00:09:38 the Intelligent Robotic Process Automation from an external system. So now we have already
created the service.
00:09:46 The next part is to manage the authorization and roles. So let's create a role collection first.
00:09:53 To do that, click on Role Collections on the left- hand side. Let's create a new role collection
and name it "irpa_officer".
00:10:17 So a role collection can have one or more roles. So the highest role which you can provide
00:10:23 in Intelligent Robotic Process Automation is IRPA Officer. So let's search for the role IRPA
Officer and put it inside the role collection.
00:10:42 So once you click on Add, a role is added to this specific role collection. So you can also add
users that can be assigned to this specific role collection
00:10:52 here under the Users panel. Or else click on Save.
00:11:02 Users can be assigned the role collections using the trust configurations. To do that, we have
to go back,
00:11:09 and under the Security tab we click on the Trust Configuration. Here you provide the e-mail
address of the user
00:11:25 to whom you want to assign the specific role collection. If the user is not added to Cloud
Platform, it will ask you to add the specific user
00:11:34 for this specific identity provider. Let's add this user
00:11:38 and then we click on Assign Role Collection. Search for irpa_officer and assign role collection.

00:11:46 So now you have successfully added the role collections and assigned the roles to the user.

9
Week 1 Unit 4

00:00:05 Hello, welcome back. In this unit, we will talk about projects, packages, and personas.
00:00:14 Let's have a look on the two tabs in the factory. We have Projects tab and Packages tab.
00:00:23 We can manage projects and manage packages. In desktop studio, our on-premise tool, you
can design projects.
00:00:31 From this local project and you can then generate a local package. This local package can be
then imported
00:00:38 in cloud factory in order to be deployed in the desktop agent. In cloud studio, our cloud tool,
you can design projects too.
00:00:49 However, you just need to generate a package that is already inside the cloud factory. Within
the Projects tab,
00:00:59 you have access to all projects created or imported in cloud factory. Depending on the kind of
process you want to automate,
00:01:08 you can either reuse desktop packages within a project or you can create directly a brand-new
cloud project without desktop packages.
00:01:20 From the project tile, you can share, rename or delete a project. Let's do a quick demo.
00:01:32 Let's start with the projects, so the project is available here on the Projects tab, so we see that
we have two projects.
00:01:39 So let's have a look at the type of option that we've got, so we have the share, the rename,
and the delete.
00:01:45 So let's rename the project that we have here and say it as a Hello World and give some
description.
00:02:01 Maybe we would need to share it, so we go on the Share, and we add a new type of user,
00:02:08 which is anyone, for instance, and it does the ability to read. And if we don't need it,
00:02:17 we can simply delete this project. And that's it.
00:02:26 We can open the remaining project. And we see the different type of content inside.
00:02:43 And that's it for the project. Now back to the Packages tab.
00:02:50 In this tab, you have access to all packages within your tenant. Packages can be imported
from desktop studio,
00:03:00 generated from cloud studio, or acquired from the store. Maybe you will ask what a package is.

00:03:08 A package is simply an immutable version of content that is ready to be deployed in an

environment.
00:03:16 Packages are versioned and have a built-in lifecycle management. Packages can have
different states, preview or released, for instance.
00:03:29 In preview, the package can be deployed for a dev or test environment. Only a released
package should be deployed to production environment.
00:03:40 We have other states, such as a deprecated or decommissioned. Such packages will be
replaced by newer versions.
00:03:50 As mentioned before, a project and then its packages can have many versions. For instance,
deprecation can be decided now or with a delay.
00:04:03 Decommissioned should be the last state or step before deletion. When you import a package
from desktop studio,
00:04:13 behind the scenes, we generate a cloud project. Quickly after, we generate a cloud package,
00:04:19 and from this cloud package, you should be able to deploy in an environment. When you work
directly with a cloud project, you simply generate a cloud package.
00:04:31 Versioning is also specified, whether it's only patches, minor changes, or even significant
changes, you decide.

10
00:04:42 Let's do a quick demo. The packages contain all the projects that have been generated as a
bundle.
00:04:53 So typically, if we go under Packages, you will find all the packages coming from the project,
for instance, or coming from the store, as we can see here.
00:05:05 So, this package has been created from the Hello World 2 from cloud studio. And we can see
that we have different versions.
00:05:13 So with a preview, which SDK has been used, and the target agent version. So if we click
here, we see the different versions that have been defined.
00:05:23 So we have the version 1.0.0, 1.0.1, 1.1.0, and so on and so forth. So we can go here and we
see that this version was released with a preview
00:05:33 and this version is known as deprecated. So if we don't need this version anymore,
00:05:40 so we can go here, we click, and we say it's going to be deprecated. Or we can decide
whether this version is going to be decommissioned.
00:05:49 So we click on Decommission. This version will soon disappear.
00:05:56 We click on Decommission. If we make a mistake, we can very quickly go back with "Rollback
to Released".
00:06:07 But if we really don't need it, it can go on the decommission. And after a couple of seconds or
minutes,
00:06:16 the version will disappear, this one was released, and this one was also as a preview.
00:06:23 So we can see that we can go directly to decommission or we can decide to release. And
that's it.
00:06:33 So we have the different versions. And we can see that this one is deprecated, so we can
decide to "Rollback to Released",
00:06:41 or we can decide that this version is going to be in decommissioned mode. And if we have a
look, so, we have a different vision
00:06:54 and this is the active version that we see here on the preview. So we can decide that, if we
want to open it, for instance,
00:07:02 we send information that we have to the bot or we can go on Open and we see the read-only
version of this package.
00:07:11 So we see the different files, the project pane, and the automation. And, if needed, the
dependencies.
00:07:21 We can decide to add a trigger and we have also some information like the sharing. So the
sharing concept is still the same, so we can decide to share with any one group or user.
00:07:35 So if we go back under Packages, we see the different versions, and we can see that the
packages that we declared as a decommissioned have now disappeared.
00:07:48 And that's it for the packages. This will end our unit.
00:07:57 We would like to remind you about the persona that you defined with SAP Cloud Platform. The
role of IRPA project member can perform tasks such as
00:08:10 import desktop packages, create cloud packages, and many more. And that's all for now.
00:08:16 In the next unit, we will talk about agents, environments, and monitoring. Thank you.

11
Week 1 Unit 5

00:00:05 Welcome back. In this unit, we will talk about agents, environments, and monitoring.
00:00:12 Let's have a look at the tabs in the factory. We have the Agents tab, Environments tab, and the
Monitoring tab.
00:00:20 We can manage agents and environment and perform monitoring. Agents are simply the on-
premise software.
00:00:29 Let's start with the agent list. In this tab, we'll report all known agents.
00:00:34 You can filter or search, and for a given agent, you can delete from the list or share. In the
agent groups, you can define the structure of your landscape.
00:00:47 You can use a csv file for defining the agent hierarchy, or you can simply define, one by one,
which agent allocation.
00:00:55 Agent group can be defined by machine or login. Within an agent group, you can customize by
adding a node or an agent.
00:01:06 Cut and paste is also available. We have added, in the Agent tab, an alert framework.
00:01:13 For instance, you can be notified whether agents are deleted or the connection is lost.
Distribution can be also defined.
00:01:22 Distribution is the process between the deployment of a package to the target agents in
attended or unattended mode.
00:01:30 An alert can be sent by mail to one or many recipients. You decide how long such notifications
should happen for.
00:01:38 Let's do a quick demo on agents. So let's have a look at the Agent.
00:01:45 So, on the Agents we have here, click on Agents, and we see the list of the different agents
connected.
00:01:52 In our case, we have only one agent. We go on Agent Groups where nothing has been defined
and nothing also defined on the Alerts.
00:02:02 So let's go back to the Agents. So on Agents we see all the agents connected and we have the
mode.
00:02:09 So in our case, the agent is written in attended mode. So we can see here on the agent that it
is starting in attended mode.
00:02:22 We can see the sharing status, and we can even share the agent, so we can decide whether
this agent
00:02:31 can be shared with any one group, user, or for a given environment. We can decide also to
remove the agent,
00:02:40 so in this case, the agent will be notified. We see that the connection has been lost.
00:02:50 And after a couple of seconds, because we have already stored the information, the agent will
store the connection and will be back to normal.
00:03:02 The agent is now back to connected. We can define agent groups, so the agent groups can be
defined in two ways.
00:03:11 So either we can import a csv file, so that, so we specified a csv.
00:03:23 We decide what type of csv, whether it's a machine or login. Create, and boom, we have a
different structure.
00:03:32 And if we need, we can even customize or create a new group, for instance, so we can add a
new group.
00:03:46 So whether it's going to be a prediction. And we could add a new machine.
00:04:07 So we can define the group here. So if we want to include the production here, we just need to
copy and paste.
00:04:19 And in this case, the production will now be within the test environment. So we save, and we
find the same area.

12
00:04:31 So we can import again, share, or we can rename or delete the agent group. We can define
alerts.
00:04:43 So the alert can be defined here. We go on New Alert.
00:04:48 We can define agent deleted. So this is a category, so we have two categories, agent or
distribution.
00:05:01 So we can decide which is agent deleted, connection is lost, or the connection is closed by the
agent.
00:05:08 We send the alert, we can decide on the recipient, [email protected]. And you could add
several different recipients.
00:05:23 You can send your letter until a certain amount of time, and we can limit the number of sent e-
mails.
00:05:32 And that's all for the agents. Now, let's talk about the Environment tab.
00:05:42 You can define the functional environment within your tenant. An environment can be dev,
test, or prod.
00:05:48 You decide which this environment should be shared with. And inside an environment, you will
deploy the packages and define the triggers.
00:05:57 Within an environment, you will associate the agents or the agent group. And here on the left,
an example on how to add an agent or an agent group
00:06:09 and here on the right to add an environment variable. Now let's see what the deploy packages
looks like on the left,
00:06:19 and what the create triggers looks like to the right. To guide you in the process of package
deployment, we've added a wizard.
00:06:31 You choose a package to deploy, you choose a trigger type, and fill the form. And that's it.
00:06:38 You can leverage advanced parameters such as time zone, job expiration, and so on. Enough
talks, let's do a quick demo.
00:06:50 So, let's have a look at Environments, so we have no new environment. So we click here to
create a new environment like Alex Test Environment.
00:07:07 You can decide the type of environment that you want. Click on Create.
00:07:18 The environment is now created, so we see that we have no packages, no triggers, no agents,
and no variables, so we can now register our agent in our system.
00:07:29 So we select this agent And then if we want to add a content, we go directly to the package,
00:07:42 or we can even skip the package and go directly to the trigger. So let's have a look at adding a
package.
00:07:50 So we can decide that we want to use this version. Now this package is being checked,
00:08:01 and whether there are some environment variables on it. Okay, so the package is being
added, this package,
00:08:15 but there is no trigger, so we can go directly to Add Trigger. So we see that the package has
been already deployed, so we can select this one.
00:08:28 We click on Next and we can decide what type of trigger we want, so like this one for attended,
for instance.
00:08:36 We click on Next. And we decide for the whole week.
00:08:49 So now the package has been added in a preview state, and we see the trigger is needed so
we can add directly another version of the package.
00:09:01 So, for instance, like this one, version 2.0.2. So we see that this step is not mandatory.
00:09:19 Or, if we want, we can add a trigger. And we want to use your version 2.0.3.
00:09:29 So in this case, the system has detected, there is a trigger that already exists so we can
decide to update a package or deploy another copy.
00:09:40 So if we view this one, we click on next. Still are putting on the attended.
00:10:00 And that's it. So we see under Triggers.

13
00:10:13 That this is the version that we published. And so we can go and get it and with a different type
of trigger
00:10:25 that has been defined, so we can modify it, and the same for the package. So, the later version
that we put here is vision 2.0.3, contains one trigger.
00:10:38 And we see which trigger is been used and we can see that we have to triggers to decide what
type of API,
00:10:48 what type of trigger can be defined and the same for the packages, with a different type of
filtering, and so on and so forth.
00:10:58 And that's it for the environment. While the Agents and Environment tabs are here to manage
resources,
00:11:08 the Monitoring tab serves another purpose. Dashboards give you an overview of your
intelligent RPA landscape.
00:11:16 You get the status of your jobs, your agents. You can quickly have a look at the executed jobs.

00:11:24 Within the Jobs tab, you have access to jobs information with many details. You can filter and
search with different criteria,
00:11:32 cancel job, or even get detailed information on job. The Logs tab is here to collect unexpected
events that could happen within your landscape.
00:11:45 Again, you can filter and search with different criteria and download the whole content in csv.
Finally, we display the monthly usage of your intelligent RPA landscape.
00:12:00 You can also download historical data in csv. Let's do a quick demo on the monitoring.
00:12:09 For the demo for the monitoring, we have a dedicated environment, a tenant in which more
information and more content has been pushed.
00:12:20 So we see that under Monitoring. So we go here on Monitoring,
00:12:24 so we see the different statuses with the different environment with distributions,
00:12:28 the ongoing jobs and the agents, and the different jobs that have been exhibited today. So we
see that today.
00:12:35 So we can switch to the seven days or even to the last 30 days. So we see the different values
that we have in this packet of time.
00:12:47 So we have the Jobs here and then we see that we can define the range that we need. Then
with a time period, so we can decide which automation we want, the status,
00:13:01 the type of package, the environment, or even the machine, and the type of trigger. So if we go
under Logs, we see the different types of action that were happening.
00:13:15 And the same for the consumption, so we see the different values that have happened for the
past month.
00:13:23 And if we go now to the data so we can know the different types of information, whether it is
historical job data, alert logs, distribution,
00:13:33 and in our case we have no BAM activity. And then let's go back to the dashboard.
00:13:38 So you can see that we can go directly here and we see a date range that has been already
selected with a different automation,
00:13:47 and so we can have also a look directly in this automation with a different type of information
like this status history.
00:13:57 It was it was successful, different type of environment, and so on and so forth. So we can go
back to Jobs.
00:14:09 And go back for the Logs. So same idea for the logs, we can download the logs if we need to.

00:14:19 And that's all for the dashboard. We hope you are now familiar with the three important topics
of cloud factory.
00:14:33 In the next unit, we have a look at deployments on desktop agent. Thank you.

14
Week 1 Unit 6

00:00:06 Hello, welcome back. In this unit, we will see the deployments on desktop agent.
00:00:14 Before the different demos, we will talk quickly about the desktop agent. And then we will
download and install the desktop agent,
00:00:22 connect the desktop agent to a tenant, we will simply execute this project in attended mode,
and we will end by executing a project in unattended mode.
00:00:34 So, what is the desktop agent? It's an on-premise component available on support.sap.com.
00:00:41 Its mission is to execute process automation in attended or unattended mode. The
connections start from the agent to the cloud factory
00:00:50 using secured communication channels. You decide how the agent will start.
00:01:00 So, let's download and install the agent. Let's download and install the on-premise component.
00:01:08 So we go here, on the Help Portal, go on the On-premise Components Setup.
00:01:19 You will find the link for downloading the software. We just need to go on this link,
00:01:31 this one, and this one, and we just need to take the latest patch level.
00:01:42 We just need to wait a couple of seconds for the software to be downloaded. That's it.
00:02:07 Okay, so we click on Next, we just need to install the desktop studio, in case we need it. We
click on Next, Next, and we go to install.
00:02:28 This will take a couple of minutes to install. Okay, the software is now installed.
00:02:55 Let's connect the agent with cloud factory. Okay, so we will need to connect to the agent that
we just installed.
00:03:05 So we launch the agent. So we just need to fill a name, OpenSAP Tenant.
00:03:21 Include the domain, the URL, save it.
00:03:27 The system is requesting the login, and that's it. Okay, so our agent looks like it's been
connected,
00:03:35 so we can check now whether this agent has been connected, and we see that this agent is
connected with the idle state, login, and the machine.
00:03:46 And that's it. And so we can see here in the about that we are in idle mode.
00:03:52 Good. So, ready for the next demo.
00:04:00 Now, let's execute a project in attended mode. Okay, so let's start with a quick demo.
00:04:10 So we see the agent that we set up, so we have now no projects associated with this agent.
00:04:18 So we have already set up an environment. So we have to go in the environment.
00:04:25 We will need to add a trigger directly, so we select this project, click on Next. Our project is
going to be attended, so we click on Next.
00:04:43 And we select for the whole week. And that's it.
00:04:49 Okay, so now a project has been added within this environment and we'll see in a couple of
seconds that
00:04:58 the project will appear directly in the list of the projects. So we can see that the project is now
happening here.
00:05:06 So we can now start the project. The agent will start.
00:05:14 So we can go under Agents to see what's happening, so we see the agent is now refreshed.
00:05:25 So it's in the IDLE phase. It will take a couple of seconds to start.
00:05:43 Okay, so now the agent has been completely restarted. And it's ready for using this package.
00:06:01 So we can see now on this we have Start Hello World. So if we click on it, what is my name?
00:06:08 My name is Alex. And that's it.
00:06:15 So we see now under Monitoring, under Jobs, that this job has been successful. So we can
even repeat again.
00:06:35 And we see this job has been successful. So that's it for a quick attended task.

15
00:06:48 Let's do our last demo by executing a project in unattended mode. For our last demo,
00:06:57 we are going to make an unattended job execution. So, first of all, we would need to make
00:07:05 sure that the agent is working in the background mode. And then we go on the overview and
we see that we have our package and so forth.
00:07:20 So what we need to do is to import a project or package. So we select this one.
00:07:39 And we need to select Scheduled. So as we can see, this project doesn't have in here any
menu
00:07:46 for being launched directly from the agents. So we go on to Scheduled,
00:07:51 we click on Next. We are going to name it, so we will start the project every five minutes.
00:08:04 We can even decide that the job will expire after five minutes, and to avoid creating new jobs,
00:08:12 we just need to deselect new job, so the job won't be created if the one is not finished.
00:08:20 And we would need to select the period of time that we want to do. We can remove the end
date if we want it to apply to until the end of the time.
00:08:32 And that's it, so we can define the execution. So we see there is one automation, and the
priority for now is low.
00:08:41 Okay, so we just need to click on Create and see what's happening. Okay, so if we go on
Triggers, we see that this attended job is here,
00:09:00 and here's the scheduled job that we just created and we see that the next execution is
planned in one minute.
00:09:06 So we can go directly on the monitor and see on the jobs what's happening. So the list of jobs
that have been successful, failed, or expired are shown here.
00:09:22 And we would need to have to wait a couple of seconds until the job would be a triggered for
execution.
00:09:31 What we can do if we want is to see what's happening. So the job here is going to create
00:09:39 some files in this folder once this capability is launched. So we'll see what's happening.
00:09:49 And if we want to, we can even trigger. But let's have a look.
00:09:54 It looks like the job is going to start right away. Okay, the job is being executed, and that's it.
00:10:07 So we see that the job has successfully created four elements. One folder, a start document, a
document that was a download from the Web site,
00:10:19 and it created an end document, so we can have a look how it works, what it looks like. Also
using the download from the Web site about the What's New.
00:10:34 Okay, so the document is being created so we can even go to click here, run again the same
execution, and see what's happening.
00:10:44 So the job will start and everything is going to be done again very quickly. And again, the job
will start after a couple of seconds.
00:11:05 And that's it. Okay, so one thing important for the job,
00:11:10 so we can see that the job has been successfully launched several times. So what we can do
now is to stop the agent and to see what's happening.
00:11:27 So we go back to the environment. We see the schedule planned for in the next few minutes,
00:11:36 so we can start so to run now and see what's happening in the monitoring. So we go back on
Jobs.
00:11:44 And we see that this job cannot be ready because the job cannot be distributed. So if for some
reason the agent is not connected, nothing will be started.
00:11:58 So we just need to start the agent. And see the behavior that will happen.
00:12:12 So automatically we are in the in the middle
in the middle of the five minutes of exploration. So quickly, the job will be ready, goes running,
00:12:29 and is going to be successful, and we see that the job as ended properly. So that's it.
00:12:36 So with the unattended work you can define a schedule and if the agent is no longer working,
so even after being restarted, the job is kept in the pipe.

16
00:12:50 I hope you enjoyed the different demos, this will end our week together. See you next week.
00:12:57 Thank you.

17
www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.