Project Structure, Annotations, and Logs

Go to the Project panel in the UIPath studio, you can see all the dependencies which are associated with the project. The UiPath is going to take care of all the dependencies and whatever the files are created will be stored on the left side.

Whatever the screenshots captured in the workflow will be stored in the .screenshots folder as shown below.

By default, the created project will be stored in the Document folder in your system which is a default folder. Go to Documents folder under the This PC and under the UiPath Folder you can see all the projects which you have created.

Click on any project and you can see that the JSON file and the .screenshot file

Every project can have only one main.xml file.

If you want to create a new sequence or workflow, go to the New tab on the ribbon and select sequence.

Once you click on Create button the new sequence will be created.

The Sequence will be created by the name sequence.xml as shown below.

Here you can set any of the sequences as main.xml which means, that file will be the starting file of the project.

You can rename any of the activities at any point of time by clicking on it and you can edit the activity name in the property pane in front of Display Name


PDF Automation by Using UiPath Studio

Annotations in UiPath

Annotation is basically used to display a short message to the developer/business for why a particular sequence/workflow is created for.

To create annotations we can right-click on the activity or sequence and click on Add annotations to write the specific message. If we have multiple activities inside the sequence/workflow we can get exactly what we are looking for.

The annotation can be Docked or Undocked or if you want to hide you can hide the annotation as shown below.

The Undocked annotation will look like as shown below

If you hide the annotation, then by clicking on the message symbol whenever you want you can see the annotation.

Basics of Automation in UiPath Studio

Logs in the UiPath

When we are automating any workflow by using the log messages as a key point we can get the exact status of the workflow. So if the workflow is having any runtime error it can be caught in the log file which we can refer for debugging to solve the issue.

Let's create a new sequence in the Basic Automation Process by the name Logs

The Logs.xml file will be created, now go to the activity pane and search for Logs messages and drag and drop this into the log sequence.

Enter the log message inside the message box inside the double quotes and save and then run the sequence by pressing CTRL+F6, Once the sequence starts executing the output will be written to the output pane.

There are four types of output messages that are present in the output pane like Error type, Warning type, Information type, and Trace type output message as shown below.