Unit 1: Introduction To Cloud Studio: Week 2: First Automations

Week 2: First Automations
Unit 1: Introduction to Cloud Studio

Introduction to Cloud Studio
Overview
1
2
3
4
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Artifacts
Artifacts Assemble Automation

Application ✓
Automation ✓
Data Type ✓ ✓
Process ✓
User Task ✓ ✓
Desktop Package ✓
File ✓ ✓
Project Pane ✓
SDKs ✓

Automation editor

Automation editor
1
1. Navigation Tab
2. Toolbar
2
3. Canvas
4. Automation Information
3 4
Application capture – Screen selection
1
1. Navigation Tab
2. Detected Applications
3. Screen Preview
4. Screen Information
2 3 4

Application capture – Captured application
3. Application Screens
4. UI Elements 3 6
5. Canvas
6. Screen Information
4 5

Application capture – Captured UI element
3. UI Elements
a) Toolbar 6
b) List c
6. Element Information
c) Main information
d) Criteria d
e) Captured Data 3
a
b e

Application capture – UI element – Captured data
Captured Data displays a list of potential

criteria that will be used for declaring a
UI element.
Criteria are required for the recognition
algorithms to pilot the declared
application screen later.

Data type

Data type
1
1. Navigation Tab
2. Toolbar
2
3. Fields List
4. Data Type Information
3 4
Data type – Field properties
3. Fields List
a) Selected Field
4. Field Properties
3 4
First “Hello World”
We will simply:
Create a new project
Add a simple activity
Launch it

Second example
We will simply:
Capture a simple application
Use it within an automation
Test it

Third example
We will simply:
Capture a simple application
Use it within an automation
Add some logic to it
Test it

Overview

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2020 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 platforms, 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/copyright for additional trademark information and notices.
Unit 2: Automations in Cloud Studio
Automations in Cloud Studio
What is an automation?
A sequence of steps to pilot and automate multiple

interactions on different applications that are
available on a specific computer.
The equivalent of a scenario in the Desktop Studio.
When packaged, automations can be

independently executed either in attended or
unattended mode.
We design automation in what we call the

automation editor.

Automation editor
The Toolbar
The Right Side

The Graph Flow Panel
The Console
What does an automation contain?
In an automation, you will be able to interact with:

▪ Other automations to enable reusability
▪ Application screens to call activities
▪ Built-in activities that come with the SDK packages
▪ Data type and variable manipulations
▪ Controls that allow you to orchestrate the other steps
▪ Custom JavaScript code

Create your first automation: SDK packages and activities
When creating your first automation in a project,

two SDK package dependencies will be
automatically added:
▪ Core
▪ Excel
Those packages contain the basic activities to build

an automation and to manipulate Excel files.
You can also choose to import other SDK packages

▪ Word, PDF, Outlook,…

Create your first automation: agent version
Also, when creating your first automation in a

project, you will be asked to choose your agent
version:
▪ If your agent is already connected to the tenant it will
be filled with your current agent version.
▪ Otherwise, you have to manually input the minimum
agent version that will run the automation.
Choosing the agent version for your project filters

the list of activities you can use.

Build an automation
The automation steps will be executed in

descending order.
To add new steps, drag and drop them from

the right side panel to one of the lines in the
graph flow.

Step inputs and outputs
Each step in an automation can take input and

produce output.
The input expects a value for a specific data type.
The output produces a value for a specific data type.
An input can take either a static value or an output of a

previous step.

Demo – Create an automation

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Data Types and Input/Output in Automations
and Activities
Data Types and Input/Output in Automations and Activities
What is a data type?
By default, three basic types of data are available in

the Cloud Studio: string, number, and Boolean.
For more complex data, you need to use data types.
A data type is a way to structure the data you can

pass between steps of your automations.
You can create a new data type manually, but some

are also automatically available with the SDK.
To allow more flexibility, an “any” type has been

created.

Creating a data type
A data type is composed of a set of fields.
Each field has a name and an associated type that can be either one
of the simple three types or a reference to another complex data type.

Demo – Create a data type

Creating automation inputs and outputs
In the right side panel of the automation editor

you can define the input and output parameters
of your automation.
For each input or output, you have to choose:

▪ A name: it must not contain spaces or any special
characters
▪ A type: it can be either one of the simple three types
or a complex one
▪ Whether or not it is a list: An input or output can be
just a simple object or a list of objects

Filling the input of a step
You have multiple ways to proceed:

▪ Use the suggested input field. This will propose the
best option depending on the type of your input
– Use an existing variable
– Type a static value
▪ Use the expression editor if you need to pass a
value that is the result of a calculation or text
manipulation
▪ Use the data editor to create a static object

Demo – Create automations that use data types

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Additional Patterns and Activities:
Loops, Logic, and Controls
Additional Patterns and Activities: Loops, Logic, and Controls
Logics and controls
When creating your automation you can use

different controls to orchestrate it:
▪ Conditions
▪ Loops
− For each
− Forever
− Repeat
▪ Custom scripting

Conditions
This control allows you to have multiple outcomes

defined by a Boolean expression that determines
the following step.
You can choose to add multiple branches for one

condition step.
You can also define outputs for your condition. The

output will take a different value depending on the
branch that will be executed.
In the different branches you can add an Exit

Automation step if you want to end your automation
in certain conditions.

Demo – Create a condition

Loops: For each
This control allows you to go through each element

in a list one by one.
When inside the For each loop, you have access

to two parameters:
▪ index: a number that starts at 0 that corresponds to
the index of the current element in the list
▪ currentMember: the current element in the list

Loops: Repeat
This control allows you to repeat some steps for a

defined number of times.
You have to provide a starting and an ending

number value.
The loop will be repeated an amount of times

equal to (Ending Value – Starting Value + 1)
When inside the Repeat loop, you have access to

one parameter:
▪ index: a number that starts at your starting value and
is incremented by 1 each loop, until it reaches the
ending value.

Loops: Forever
This control allows you to repeat some steps until

a certain condition is met.
When inserting a Forever loop, it automatically

adds a condition to it.
You have to provide a Boolean expression for this

condition to describe when the loop should end.
When inside the Forever loop, you have access to

one parameter:
▪ index: a number that starts at 0 and is incremented by
1 until the loop ends

Demo – Create loops

Custom script
This activity allows you to define a custom

behavior using JavaScript code.
You can manipulate data coming from previous

steps if you set them as inputs of your script.
You can also create new outputs from this step

and return them in the JavaScript code.
In the custom script you have access to all the

activities and screens available in your project.

Demo – Create a script

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 5: Debugger: Step by Step
Debugger: Step by Step
Testing/debugging an automation
The tester/debugger helps you test and

troubleshoot the execution of your automation on
your Desktop Agent.
Prerequisites:
▪ You should have connected your Desktop Agent
▪ You should have created an environment in the Cloud
Factory where your Desktop Agent is registered

Breakpoints
When testing an automation, you may want to:

▪ Just execute the automation to test it
▪ Execute the automation step by step to troubleshoot it
– For that you need to add breakpoints
To add a breakpoint, you need to selected a step

and click on the orange circle on the left.
When testing your automation, it will automatically

stop at the steps where you added breakpoints.

Testing procedure
First, click the test button at the Select the environment on which Wait for the test package to be
upper right of the automation your Desktop Agent is registered. downloaded by your Desktop
editor. Agent.

Automation editor in debug
Toolbar
Timeline
Inputs/Outputs
Breakpoints
Console
Debug toolbar
Stop the debug session Execute one step Step out to upper automation
Resume the execution Step into a sub-automation

Tester demo

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 6: Store: Bots Brought to You by SAP
Store: Bots Brought to You by SAP
Overview
Within Cloud Factory Without Cloud Factory

Type of content
Pre-built content SDKs

Content details
Overall information
Detailed description
Package details
Get it!

Pre-built content

Browse – Acquire – Customize pre-built content
Browse Acquire Customize

Demo

Regular deliveries covering multiple lines of business
150+ examples of pre-built

content
Multiple lines of business
Ready to use…
… to customize
Created by LoB experts

SDKs

SDKs overview
SDK modular architecture

▪ Simple dependencies management
▪ ‘Plug & play’
▪ Online documentation
Outlook Excel Word PDF SAP GUI SAPUI5 ...
Core SDK
SDKs lifecycle
Cloud Project SDK Dependencies

▪ Project settings
▪ Always available
Dependency Section
▪ Add or delete package
▪ Version choice
Project Automation
▪ New SDK functionality is ready to use
▪ New activities

Demo

Summary
Pre-built content SDKs

Thank you.
open@sap.com
Follow all of SAP

warranty.

Unit 1: Introduction To Cloud Studio: Week 2: First Automations

Uploaded by

Copyright:

Available Formats

You might also like

Unit 1: Introduction To Cloud Studio: Week 2: First Automations

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit 1: Introduction To Cloud Studio: Week 2: First Automations

Uploaded by

Copyright:

Available Formats

Week 2: First Automations

Unit 1: Introduction to Cloud Studio

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Artifacts Assemble Automation

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Captured Data displays a list of potential

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Create a new project

Add a simple activity

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Capture a simple application

Use it within an automation

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Capture a simple application

Use it within an automation

Add some logic to it

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

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

A sequence of steps to pilot and automate multiple

The equivalent of a scenario in the Desktop Studio.

When packaged, automations can be

We design automation in what we call the

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

The Right Side

In an automation, you will be able to interact with:

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

When creating your first automation in a project,

Those packages contain the basic activities to build

You can also choose to import other SDK packages

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Also, when creating your first automation in a

Choosing the agent version for your project filters

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

The automation steps will be executed in

To add new steps, drag and drop them from

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Each step in an automation can take input and

The input expects a value for a specific data type.

The output produces a value for a specific data type.

An input can take either a static value or an output of a

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

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

By default, three basic types of data are available in

For more complex data, you need to use data types.

A data type is a way to structure the data you can

You can create a new data type manually, but some

To allow more flexibility, an “any” type has been

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

A data type is composed of a set of fields.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4