Installation of Ui path Studio(Community Edition)

➤ We’ll start off by accessing the Ui Path website. We’ll simply select “Start Trial”, and then click the “Choose Community” button.

➤ Firstly, we must pick a Sign in method and complete all the necessary steps. Note that you can choose to Sign up with an Email that’s different from the options displayed.

➤ Secondly, we need to create an account on the UiPath platform. We’ll provide all the details, such as First Name, Last Name, Country and Company Name, if known. When done, we can hit Signup.

➤ That’s it! In a few moments, we will be redirected to the UiPath Platform. Let’s navigate to the Resource Center tab available on the left-hand side menu. We’ll proceed by selecting the “Download” button under Community Edition.

The UiPath Studio Installer will now start downloading.

➤ After the download process is successfully finalized, we’ll simply open the installer file to begin the installation process itself. At the end, we’ll see a pop-up screen that prompts us to choose a License type.

➤ As we do not need a license key for the Community Edition, we’ll proceed by selecting “Activate Community Edition”.

Success! UiPath Studio is now installed, so we are ready to start our very first RPA project. Happy automation!

Navigation in Ui Path Studio

We will talk about the UiPath Studio interface and functionalities. We will see how it provides the means to create automation workflows from scratch or edit previous projects to ensure that they are tailored to suit your needs. Let’s begin!

➤ We’ve just opened UiPath Studio. As you can see, we can create a new project or open one that we’ve edited recently.

➤ Let’s create a new one to delve into the basics of UiPath Studio. We need to give it a name, such as Studio_Demo, select the location where we want to save it - let’s stick with the default one at the moment - and, finally, provide a description that makes the project easy to identify later on.

➤ Okay, now that we’ve opened a new process, let’s first take a look at the Projects panel.

➤ In here, we can find the project dependencies and the xaml file we are currently working on.

➤ Dependencies comprise the activity packages we are using to automate processes.

➤ Each activity corresponds to an action that is usually performed by a human user.

➤ In other words, activities are what enable us to build automation projects.As you can see, there is a dedicated tab next to this one, but we’ll talk about it later on.

➤ Now, let’s say we want to automate a Word file. To do that, first we need to install the package that contains Word activities and add the dependency here on this list.

Let’s click Manage Packages

These are the dependencies that have already been installed. If an update is available, this clickable blue arrow is displayed.

➤ But what we need now is the Word activity package, so let’s click the All Packages section and type Word in the search field.
Here it is! Select it, click install, then hit save, and we’re done! We can see a new dependency here on this list.

➤ Now let’s move on! The xaml file contains this specific project. We can easily add a new project here by clicking this button and browsing for the xaml file that contains it.

Look, it is now displayed here

In most automation projects, we will use Variables to store data

➤ There is a section in UiPath Studio where you can see all of them and set or edit their name, type, and scope. The section is called the Variables panel and can be viewed by clicking here.

➤ You’re probably familiar with the way in which variables work, but let’s recap the basics before moving on.

When setting the type of a variable, we need to think about the kind of data we want to store.

• If it’s a number, we need to set the type to Integer.

• Is it’s text, the type is String.

• If we’re dealing with a yes or no a.k.a (true or false) scenario, a Boolean variable is suitable.

• If there are multiple values of the same variable type, we can store them together in an Array variable.

• There is also a variable type which is specific to UiPath and can store any kind of data. The name of this type of variable is self-explanatory - Generic value.

Now let’s talk about the scope of a variable

➤ In the most simple terms, scope corresponds to where the variable will be available in the workflow.

➤ If we need to use a specific variable throughout this entire workflow, its scope will be its biggest container, or the Flowchart in this example. That means we can use the variable in any activity, regardless of any smaller containers the activity is placed in.

➤ But not all the variables in this workflow have this scope. Let’s click this container.

➤ As you can see, the Variables panel has changed - there are more items in it.

➤ These variables are only used in this particular section of the process, so we don’t need to expand their scope.

➤ If we go to a different section of the workflow and attempt to use one of the variables that have a limited scope, we can see that Studio cannot find it.

➤ So, as you can see, we can navigate through the different sections of our process using the navigation bar above the Designer panel.

➤ However, there is a simpler way to view the entire structure of the project and open the different containers in it.

➤ Let’s take a look at the right side of the screen. As you can see, there is a tab called Outline. Let’s open it!

➤ This is the structure of the entire project. If we click on different activities, our selection is displayed on the Designer panel. Long story short - the Outline panel eases the navigation throughout the workflows and provides a comprehensive view of the project layout.

➤ Last, but not least, there is a Universal Search feature at the top right of UiPath Studio.

➤ You can enter in a variable name, an activity name, or anything else and it will return where within the workflow that search result lies.

➤ Now let’s run the workflow! We can do that by opening the Execute tab and clicking Run.

➤ Now, to see the actions that have been performed, we can open the Output panel to see the details of the execution. If any errors occur, they are displayed in here.