Training UIPATH – 12/4/2024: Vibhu

1. Difference between A360 vs Mulesoft?

Control over platform for API, Most of the times it is expensive

Deploy on cloud hub mulesoft code executed and deployed. Vcose processor visualization platform.

UI PATH 0 – Orchestrator like Control room on A360

Bot agent – robot

UIPATH studio –

Development env is a desktop application in uipath, a360 is online.

Create GitHub Account using Xalta id create repo for UiPath, and repo is private.
https://github.com/tanvim101/UIPath-Xalta
SAP SOLUTON MANAGER?

SAP Solution Manager is a central platform used by organizations to manage and monitor their SAP
systems and applications throughout their lifecycle. It provides functionalities for various tasks such as
system monitoring, incident management, change control, and more.

In the context of UiPath extension installation, the SAP Solution Manager integration allows UiPath users
to streamline their automation processes within SAP environments. By leveraging the UiPath extension
for SAP Solution Manager, users can automate repetitive tasks, enhance productivity, and improve the
efficiency of SAP-related processes.

This integration typically involves the installation of the UiPath extension for SAP Solution Manager,
which enables communication between UiPath robots and SAP Solution Manager. With this extension
installed, UiPath robots can interact with SAP Solution Manager Functionalities, such as creating and
managing incidents, executing SAP transactions, extracting data from SAP systems, and more, thereby
enhancing the automation capabilities within SAP environments.

Create a github acc using Xalta id, create a repository ui path training, connect UI path with github rep,
rep is private

Is the underlying technology is JAVA in automation industry?

Java has been a popular technology in the automation industry, particularly in the realm of test
automation. Tools like Selenium, Appium, and TestNG, which are widely used for automating web and
mobile applications, are written in Java. Additionally, Java's platform independence and robustness
make it a preferred choice for building automation frameworks and handling various automation tasks.

However, it's worth noting that the automation industry is diverse, and different technologies are used
for various purposes. While Java is prevalent, other technologies such as Python, JavaScript, and C# are
also commonly used, depending on the specific requirements and preferences of the project or
organization. Ultimately, the choice of technology in the automation industry depends on factors such
as the nature of the application, the skill set of the team, and the goals of the automation effort.

Table extraction

Search for smart phones in amazon and get the data of first 5 pages using table extraction option

Cross platform compatibility?

Cross-platform compatibility in UiPath Studio refers to the ability of UiPath automation projects to run
seamlessly across different operating systems such as Windows, macOS, and Linux. UiPath Studio, as a
leading Robotic Process Automation (RPA) tool, provides support for building automation workflows
that can be deployed on various platforms without requiring extensive modifications.

This cross-platform compatibility ensures that UiPath automation solutions can cater to diverse
environments, allowing businesses to leverage automation capabilities regardless of their underlying
infrastructure. It also enables flexibility in deployment, as organizations can choose the operating
system that best suits their needs without worrying about compatibility issues.

What is Object Repository in UiPath?

In UiPath, an Object Repository is a centralized location where you can store and manage the properties
and attributes of UI elements (also known as "objects" or "controls") that your automation interacts
with. These UI elements can include buttons, text fields, dropdown lists, checkboxes, and any other
elements present in the applications you are automating.

The Object Repository serves several purposes:

Centralization: It provides a single location to store all the UI element definitions used across your
automation projects, promoting consistency and reusability.

Easy Maintenance: By storing UI element properties and attributes in a central repository, you can easily
update them if they change in the application being automated. This reduces the effort required to
maintain your automation workflows.

Enhanced Collaboration: Object Repositories can be shared among team members, facilitating
collaboration and ensuring that everyone uses the same definitions for UI elements.

Parameterization: You can define variables or arguments within the Object Repository to make your
automation more dynamic and configurable.

Enhanced Readability: Using descriptive names and grouping related elements together in the Object
Repository can improve the readability and maintainability of your automation projects.

UiPath provides various types of Object Repositories, including:

Global Object Repository: A project-level repository that can be accessed by all workflows within the
project.
Local Object Repository: A workflow-level repository that is specific to a particular workflow.

UI Explorer Repository: A repository automatically generated by the UI Explorer tool, which captures the
properties and attributes of UI elements as you interact with them during recording or design time.

Overall, the Object Repository in UiPath is a powerful tool for organizing and managing UI element
definitions, making your automation projects more efficient and maintainable.

What is RE framework?

The REFramework (Robotic Enterprise Framework) in UiPath is a template or a foundation for building
robust and scalable automation solutions, particularly suited for long-running processes and attended or
unattended automation scenarios. It provides a structured approach to developing automation projects,
focusing on key aspects such as exception handling, transactional processing, logging, and reusable
components.

Here are some key components and features of the REFramework:

Modularity: The REFramework encourages breaking down automation processes into reusable
components or workflows, enhancing maintainability and scalability.

Transaction Handling: It includes mechanisms for managing transactions, allowing processes to handle
interruptions or failures gracefully and resume from the last known state.

Exception Handling: The framework provides a structured way to handle exceptions and errors, enabling
developers to define how the system should react to different types of failures.

Logging and Monitoring: Built-in logging capabilities allow for tracking the execution of processes and
identifying issues quickly. The framework logs details such as transaction status, error messages, and
execution times.

Configurability: The REFramework supports configuration files where parameters and settings can be
defined, making it easier to adapt automation solutions to different environments or scenarios.

State Machine: It uses a state machine design pattern to manage the flow of execution, with states
representing different stages of the automation process.

Framework Components: The framework includes predefined components such as Main.xaml (the entry
point for the automation), InitAllApplications.xaml (for initializing applications), Process.xaml (the main
processing workflow), EndProcess.xaml (for finalizing the automation), and more.

By leveraging the REFramework, developers can streamline the development and maintenance of
automation projects, ensuring consistency, reliability, and scalability. It provides a standardized
approach to building automation solutions that align with best practices and industry standards.
Additionally, UiPath provides documentation, training materials, and community support to help
developers understand and effectively utilize the REFramework in their projects.
UIPATH training from academy

Studio, Orchestrator and Robots are what we call the core RPA components of the UiPath

Platform.

We call them the core components because RPA can't work without developing automations,

running them, and managing the entire ecosystem.

DAY 2, 15/4/2024 MONDAY

Create a project and use all excel activities

LIB USED FOR EXECEPTIONs

Selector in studio

Selectors in UiPath Studio are XML fragments and enable the identification of specific user interface

elements.

A selector in UiPath Studio is a feature that enables the identification of a specific User Interface element
through its address and attributes. These selectors are stored as XML fragments.
The element identification is performed to execute specific activities in an automation project.
Selectors are generated when UI elements are indicated for activities which require target element(s).

Lesson summary

1. Selectors in UiPath Studio are XML fragments and enable the identification of specific
user interface elements.
2. Selectors consist of nodes, each of which is composed of tags and attributes.
3. Selectors use these tags to specify which elements they want to target and apply styles or
perform actions on.
4. Attribute provides specific information about the element, such as its name, ID, class,
title, or type. These attributes are used to find and perform actions on the desired
elements during automation.
Full selectors contain all the information required to identify a specific UI element, including the
top-level window. They are not limited to container activities and can be used in any activity
within an automation workflow.

On the other hand, partial selectors are specific to container activities, such as "Use Application"
or "Browser Activity." These container activities store information related to the top-level
window, and the activities within them use partial selectors. Partial selectors don't
include information about the top-level window.

In the Classic Design Experience, full selectors are more commonly used across all activities.

However, in modern design, the child activities within container activities use partial selectors,
which store only the necessary information for identifying the UI elements within the container.

Default is modern

To access classic, filter classic

Click activity, classic