Fast-Track UiPath Developer Module 2: Getting to Know UiPath Studio Machina Automation Fast-Track UiPath Developer Module 2: Getting to Know UiPath Studio

2 – Getting to Know UiPath Studio Overview: This module introduces the UiPath Studio development environment, which is where developers spend the majority of their time building automated workflows. Organization: This module is organized into the following sections: 2.1: Projects, the project.json file, and UiPath Studio Orientation 2.2: Activity Packages 2.3: Libraries 2.4: Variables 2.5: Arguments 2.6: Debugging 2.7: Flow Control 2.8: Recording

2.1 – Projects, project.json, & UiPath Studio Orientation First, some housekeeping: If you haven’t already done so, find your UiPath Studio icon in the Windows Start menu, right click it, expand the “More” menu, and select “Pin to taskbar” Repeat the above process for the UiPath Robot icon Click the blue Ui icon on the taskbar to launch UiPath Studio (do not click the white Ui icon yet...we will discuss it later)

2.1 – Projects, project.json, & UiPath Studio Orientation The initial UiPath Studio screen looks like this...

2.1 – Projects, project.json, & UiPath Studio Orientation At the highest level, an automated process that is being developed in UiPath Studio is referred to as a “Project” The following types of Projects can be created in UiPath Studio: Process: a blank canvas on which you can create your automated workflow Library: a blank canvas on which you can create and publish reusable components that can be shared within your organization Transactional Process: a flowchart template that is pre-configured to provide a starting point for creating automated workflows that process data transactions Agent Process Improvement: a monitor events template that is pre-configured to provide a starting point for creating automated workflows that monitor and handle user click, keystroke, or hotkey events Robotic Enterprise Framework: a state machine template that includes transaction processing, error handling, and logging as a starting point for creating robust enterprise-ready automated workflows

2.1 – Projects, project.json, & UiPath Studio Orientation To open an existing project or a specific .xaml file, click Open, navigate to the location of the project, and select the file name

2.1 – Projects, project.json, & UiPath Studio Orientation Click Team to access the actions for connecting to your source control system (TFS/Azure DevOps or SVN)

2.1 – Projects, project.json, & UiPath Studio Orientation The Tools page contains icons to launch UI Explorer and for installing various extensions

2.1 – Projects, project.json, & UiPath Studio Orientation The Settings page contains options for setting the language and the theme and for resetting UiPath Studio back to the default state

2.1 – Projects, project.json, & UiPath Studio Orientation The Help page contains links to resources and provides details about the UiPath Studio version, licensing, and device ID

2.1 – Projects, project.json, & UiPath Studio Orientation Return to the Start page, click on Process, leave the default Name, and click the Create button to create and open a new project in UiPath Studio

2.1 – Projects, project.json, & UiPath Studio Orientation Congratulations! You have just created your first UiPath project! It doesn’t do anything yet, but it has already done some things behind the scenes

2.1 – Projects, project.json, & UiPath Studio Orientation When new Projects are created, a new folder is created in the Documents\UiPath directory The contents of this new directory are different depending on the type of project created (Process, Library, Transactional Process, Agent Process Improvement, or Robotic Enterprise Framework), but all types of projects contain a default workflow file with a .xaml extension (usually ‘main.xaml’) and a project.json file The project.json file is located at the root level of the UiPath\<PROJECT_NAME> folder...

2.1 – Projects, project.json, & UiPath Studio Orientation The image below shows a sample project.json file. The name, description, main file, dependencies, and other project meta-data are contained in this file. While this file contains some interesting and possibly helpful information about your project, the only item that you should modify, if you choose to, is the description.

2.1 – Projects, project.json, & UiPath Studio Orientation Now let’s have a look around Uipath Studio... Instructor-led walkthrough of UiPath Studio

2.2 – Activity Packages Activities are the building blocks of automated workflows in UiPath There are core UiPath activities included by default when Studio is installed Packages can be installed or uninstalled by using the Package Manager Activities can be added to the workflow by double-clicking or by dragging them into the work area

Complete Exercise 2.1 – Show Me the Message 2.2 – Activity Packages Complete Exercise 2.1 – Show Me the Message

2.3 – Libraries Libraries are published packages that contain multiple reusable components that can be shared within your organization To create a Library, select the Library option from the Start page

2.3 – Libraries Publishing a Library from Studio to Orchestrator makes the package available in the “Libraries” page where others can use it

2.4 – Variables Variables contain data values of many different types The types available in UiPath Studio by default include: Boolean Int32 String Object Array of [T] Additional types are available by clicking Browse for Types... in the variable type dropdown and searching for a .Net type Variables can be created directly in the Variables pane below the work area or by using the [CTRL]K key combination in the output field of an activity Changing the name of a variable in the pane changes it in all instances where it is referenced

2.4 – Variables Instructor walkthrough of Variables Complete Exercise 2.2 – Show Me The User Message

Complete Exercise 2.3 – Generic Value Variables

2.5 – Arguments Arguments are used to pass values into and out of other workflows through the Invoke Workflow File activity (which will be covered later) Arguments are created in the Arguments pane below the workspace and the Direction must be specified as one of the following three available options: In: the value is being passed into this workflow Out: the value is being passed out of this workflow In/Out: a value is being passed into this workflow and out of this workflow Property is a fourth option under the Direction dropdown, but it is not currently in use More on Arguments later when we discuss Invoke Workflow File

2.6 – Debugging UiPath Studio provides debugging capabilities that are located under the Execute tab Breakpoints can be toggled on and off of an activity by selecting the activity and clicking the Breakpoints button Breakpoints only activate when running in Debug mode When a Breakpoint is hit, the Break, Step Into, and Step Over options become available and the Debug button becomes a Continue button

2.6 – Debugging Break pauses the Debugging process Step Into moves the process to the next activity in the workflow on each click Step Over executes containers (sequences, flowcharts, or invoked workflows), but does not drill down into them Slow Step slows down processing speed when the process is run in Debug mode. Clicking on the Slow Step button toggles it between Off, 1x, 2x, 3x, and 4x. Options allow you to enable or disable highlighting, logging, and breaking on exceptions Giving each activity in your workflow a unique name as you go is a good practice that will help with debugging your code Adding Log activities to your workflows is also a good debugging practice

Complete Exercise 2.4 – Create a Log Message 2.6 – Debugging Complete Exercise 2.4 – Create a Log Message

2.7 – Flow Control Flow control is the process of using rules and conditions to determine the path that the automated workflow should follow Flow control activities include: If (Sequences) – evaluate a condition and branch flow to the true (“then”) side or the false (“else”) side Flow Decision (Flowcharts) – Flowchart activity that behaves the same as the If activity While – evaluate a condition and then execute a process while it evaluates to true (condition is evaluated before processing) Do While – execute a process and then evaluate a condition -- if true, then execute the process again (process executes and then condition is evaluated)

2.7 – Flow Control Flow control activities include (continued): For Each – iterate over arrays, lists, or other types of collections and process each member of the collection individually For Each Row – iterate over the rows in a data table and process each row individually Switch – branch flow based on the specific result of an expression or value of a variable Delay – pause processing for the specified number of milliseconds Break – stops the current looping process and continues the workflow with the next activity

Complete Exercise 2.5 – Show Me the User Messages 2.7 – Flow Control Complete Exercise 2.5 – Show Me the User Messages

2.8 – Recording Basic – Suitable for single activities – creates a full selector Desktop – Suitable for all types of desktop apps and multiple actions and is faster than the Basic recorder – creates a partial selector inside an application container Web – Designed for recording in web apps and browsers – use Internet Explorer (11 or higher) for best results – creates a partial selector inside a browser container Image – Used to record virtualized environments (such as VNC, virtual machines, Citrix, and more) or SAP. It permits only image, text and keyboard automation, and requires explicit positioning. Native Citrix - Is the equivalent of the Desktop recorder, but for Citrix environments. Only use this in your Native Citrix automation projects.

2.8 – Recording Instructor walk through Recording options Complete Exercise 2.6 – Show Me the Quote