SRI VIDYA MANDIR ARTS & SCIENCE COLLEGE

(AUTONOMOUS)
[An Autonomous College Affiliated to Periyar University, Salem]
[Recognized under Section 2(f) & 12(B) of the UGC Act, 1956]
[Accredited by NAAC with “A” Grade [CGPA=3.27/4.00]]
VIGNESH NAGAR, KATTERI - 636 902, UTHANGARAI (TK),
KRISHNAGIRI (DT), TAMIL NADU
PG & RESEARCH DEPARTMENT OF COMPUTER SCIENCE & APPLICATIONS

COURSE CODE: 23UAD6C07 PROGRAM: [Link] CS(AI &

DS)
COURSE TITLE: Robotics Process Automation

Unit I:
Robotic Process Automation (RPA): Fundamentals of RPA – Programming basics from
RPA perspective – Applying RPA – RPA development methodology – Architecture of RPA –
RPA and emerging ecosystem.
Unit II:
Basics of RPA – RPA benefits – Processes that can be automated – Types of Robots.
Automation and RPA Concepts: Business models for implementing RPA – Centre of Excellence
– Types and their applications – Building an RPA team – Approach for implementing RPA
initiatives.
Unit III:
Automation stages and the role of a Business Manager – Guidelines for tracking the
implementation success – Metrics/Parameters to be considered for gauging success – Chossing
the right licensing option.
Unit IV:
Introduction – Automation debugging – Automation library – Activities Packages –
Basic automation tasks – Text and Image automation. Setting up the Uipath Environment –
Introduction to Uipath – The User Interface – Keyboard Shortcuts.
Unit V:
Tables in RPA – Data Manipulation in Excel – Extracting Data from PDF – Using
anchors in PDF.
 UNIT - I
ROBOTIC PROCESS AUTOMATION (RPA)
FUNDAMENTALS OF RPA
Robotic Process Automation (RPA) is a technology that uses software robots (bots) to
automate repetitive, rule-based tasks in digital systems. These bots interact with applications
and systems like humans do but operate faster and more accurately. Below are the key
fundamentals of RPA:

1. Definition and Purpose

RPA focuses on automating routine tasks to:

 Reduce
human errors.
 Enhance productivity by allowing employees to focus on higher-value tasks.
2. Key Features

Rule-Based Processes: RPA is ideal for tasks that follow predefined rules.
Non-Invasive Integration: Bots can operate on top of existing IT infrastructure without
requiring changes to systems.
Scalability: Easy to scale up or down based on business needs.
3. Core Components

Software Robots (Bots): Programs that execute tasks like data entry, extraction, and
system navigation.
RPA Tools: Platforms like UiPath, Automation Anywhere, and Blue Prism that provide
 bot development and management capabilities.
Workflow Designer: A visual interface for designing automation workflows.
4. How RPA Works

Recording Actions: Captures human actions like mouse clicks and keystrokes.
Rule Implementation: Encodes decision-making logic.

Execution: Performs the task automatically without human intervention.

5. Use Cases

Finance and Accounting: Invoice processing, reconciliations.

Human Resources: Onboarding, payroll
automation.
Customer Support: Handling queries, updating
records.
IT Operations: System monitoring, password
resets.
6. Benefits

Cost Savings: Reduces operational costs by automating manual tasks.

Speed and Accuracy: Bots perform tasks faster and with fewer errors.
Compliance: Ensures adherence to regulatory standards through consistent processes
7. Limitations

Rule Dependence: RPA is not suitable for tasks requiring judgment or creativity.
Initial Investment: May involve significant upfront costs for setup and training.
Process Optimization: Automation requires well-defined and optimized processes.
8. Future Trends

Intelligent Automation: Integration with AI and Machine Learning for smarter

bots.
Hyperautomation: Combining multiple technologies for end-to-end process
automation.
Cloud-Based RPA: Deploying RPA solutions on the cloud for flexibility and
scalability.
RPA is a transformative technology that continues to evolve, offering significant potential
for businesses to streamline operations and drive innovation.

The Graphical User Interfaces

A GUI is generally considered to be much more user-friendly than other interface systems, such as
the ones using text-based commands. It is a software system that uses interactive visual components
(for example, a pointer and icons). This is accomplished by displaying icons/symbols that
communicate information and represent responses the user can understand. These objects include
buttons, icons, and cursors, and can change size, color, or visibility when interacted with. The
graphical elements can sometimes be enhanced with sounds or with visual effects, such as
transparency and drop shadows.

One of the GUI’s greatest strengths is its user friendliness. It is much easier to learn than other
operating systems. This is because text commands don’t have to be memorized, as the system uses
icons and clicks. Nor do users need to be familiar with programming languages. GUI systems have
dominated today’s computer market with their easy-to-use controls and modern appearance.

RPA allows people who do not write code to create workflows using wireframes, such as a GUI. An
RPA can provide users with a GUI interface, which they can use to organize, arranging the steps in a
data-processing workflow. Robotic process automation also allows people to interact with other parts
of the software through the GUI. (An RPA also records its interactions with humans, so that
appropriate responses can be automated.)

Machine Learning and Robotic Process Automation

Machine learning models, such as image recognition, can be inserted into RPA workflows to perform
machine perception tasks. With this combination, ML can perform tasks (for example, visual
inspections) that humans normally perform in less than a second. RPA (also referred to as “software
robotics”) is a form of process automation technology. It can be used for a variety of tasks, ranging
from assembly line inspections to email responses.

RPA can also be used to improve the data’s quality. As the amounts and types of data continue to
grow, robotic process innovation provides useful solutions for improving the results for all areas of
analytics. RPA, when augmented by ML and AI, can streamline the input (images and documents)
while improving the process by monitoring the RPA logs.
PROGRAMMING BASICS FROM RPA PERSPECTIVE
Robotic Process Automation (RPA) focuses on automating repetitive, rule-based tasks,
and while many RPA tools are designed for minimal coding, understanding basic
programming concepts can significantly enhance the development and efficiency of bots.
Below are the programming basics relevant to RPA:
1. Variables and Data Types
Variables: Used to store data values that can change during execution.
Example: username = "JohnDoe"

Data Types: Common types include:

String: Text data (e.g.,
"Invoice123")
Integer: Whole numbers (e.g.,
100)
Boolean: Logical values (True or
False)
Array/List: Collection of items
(e.g., [1, 2, 3])
Dictionary: Key-value pairs (e.g., {"Key": "Value"})
Use in RPA: Store and manipulate inputs, outputs, and intermediate data (e.g., capturing
user data from forms).
2. Control Flow (Decision-Making)
Conditional Statements: Used to make decisions based on conditions.
 If-Else Statement: Executes a block of code if a condition is true; otherwise, another
block. if status == "Approved":
send_email(
) else:
escalate_issue()
Switch/Case (depending on tool): Simplifies multiple conditions.
Use in RPA: Direct bots to take actions based on logic, like processing valid data and
skipping invalid data.

3. Loops
For Loop: Iterates over a collection of
items.
for file in file_list:
process_file(file)
While Loop: Repeats as long as a condition is
true.
while not task_complete:
check_status()
Use in RPA: Automate repetitive tasks, such as reading rows in a spreadsheet or
processing multiple files.
4. Functions/Modules
Functions: Reusable blocks of code to perform specific
tasks. def calculate_tax(amount):
return amount * 0.1
Modules: Group of related functions.
Use in RPA: Create modular workflows for better readability and reuse (e.g., a function
to validate email addresses).
5. Exception Handling
Try-Catch Blocks: Handle errors
gracefully. try:
open_file("[Link]"
) except
FileNotFoundError:
log_error("File not found")
Use in RPA: Ensure bots handle unexpected issues (e.g., missing files or invalid inputs)
without stopping the entire process.
6. File and Data Handling
File Handling: Reading, writing, and updating files.
Example: Reading an Excel file to process data.
Data Structures: Use lists, arrays, and dictionaries to manage and process structured data.
Use in RPA: Manipulate files, databases, and web elements (e.g., extracting and updating
customer information).
7. APIs and Web Services
APIs: Allow bots to interact with external systems and retrieve/send data
programmatically.
Example: Fetching weather data using an API.
Use in RPA: Extend functionality by integrating with third-party tools or services.
8. Logging and Debugging
Logging: Captures process details for monitoring and troubleshooting.
Debugging: Identifies and resolves issues in workflows.
Use in RPA: Ensure processes are transparent and error-free by maintaining logs and
debugging efficiently.
9. Object-Oriented Concepts
Classes and Objects: Create reusable components for bots with shared properties and
behaviors.
class Bot:
def init (self, name):
[Link] = name
Use in RPA: Advanced customization for complex workflows.
APPLYING RPA

The application of Robotic Process Automation (RPA) involves automating repetitive,

rule-based tasks across various business processes. Implementing RPA transforms
workflows, improves efficiency, and reduces errors. Below is a guide to applying RPA
effectively:
1. Identify Suitable Processes for Automation

Not all tasks are ideal for RPA. The best candidates share the
following characteristics:
Rule-Based: Clear, predefined rules and decision logic.
High Volume: Tasks performed frequently and in large quantities.
Repetitive: Routine tasks requiring
minimal variation.
Structured Data: Input data is organized
and digital.
Error-Prone: Processes susceptible to
human errors.
Examples:
Invoice processing
Data entry
Data migration
Report generation
Customer support ticket handling
2. Select the Right RPA Tool

Choose an RPA platform that aligns with your business requirements. Popular tools
include:
UiPath: User-friendly interface and extensive integrations.
 Automation Anywhere: Scalable and cloud-compatible.
Blue Prism: Strong in security and governance.
Microsoft Power Automate: Seamless integration with Microsoft tools.
Considerations:
 Scalability
 Ease of use
 Integration capabilities
 Licensing costs

3. Design and Develop Workflow

Process Mapping: Break down the process into steps.

Workflow Design: Use RPA tools' drag-and-drop interfaces or custom scripts to
create workflows.
Testing: Simulate scenarios to ensure accurate bot performance.
Optimization: Refine workflows to enhance speed and accuracy.
4. Deploy and Manage Bots

Bot Deployment: Assign bots to production environments.

Monitoring: Track bot performance through dashboards and
logs.
Maintenance: Update workflows as business requirements
evolve.
5. Integrate with Other Systems

RPA works best when integrated with existing business systems and technologies:
APIs: Enable bots to interact with external systems programmatically.
OCR (Optical Character Recognition): Extract text from scanned documents.
AI and ML: Enhance decision-making for semi-structured processes.
6. Examples of RPA Applications
Across Industries Finance and
Accounting:
 Invoice processing
 Bank reconciliation
 Tax reporting
Human Resources:
 Employee onboarding
  Payroll processing
 Leave management
Customer Service:
 Chatbot integration for query resolution
 Customer data updates
 Order Tracking
IT Operations:
 Password resets
 System monitoring
 Data backups
7. Benefits of Applying RPA

Cost Savings: Reduces operational costs by minimizing manual effort.

Accuracy: Eliminates human errors.
Productivity: Allows employees to focus on higher-value activities.
Compliance: Ensures adherence to regulatory requirement.

8. Challenges and Solutions

 Processing complexity
 Employee resistance to automation
 High initial setup costs
Solutions:
 Conduct thorough process assessments.
 Provide training and change
management support.
 Start with pilot projects before
scaling.
 9. Future Trends in Applying RPA

Hyper automation: Combining RPA with AI, ML, and other technologies for end-to- end
automation.
Cloud-Based RPA: Leveraging cloud platforms for flexibility and scalability. Citizen
Development: Empowering non-technical users to build simple automation solutions
Conclusion:
By following these steps and principles, RPA can be successfully applied to drive
efficiency, reduce costs, and streamline operations.
RPA DEVELOPMENT METHODOLOGY
Robotic Process Automation (RPA) development follows a systematic methodology to
ensure successful implementation. Below is a step-by-step outline of the RPA development
process:
1. Discovery Phase

Objective: Identify and evaluate processes for automation.

Steps:
Conduct a process assessment to identify repetitive, rule-based tasks with structured
data.

 Analyze the volume, frequency, and complexity of tasks.

 Prioritize processes based on ROI, feasibility, and business impact.
2. Analysis Phase

Objective: Gather detailed requirements for the selected processes.

Steps:
1. Document the current process workflows
(as- is process).
2. Identify variations, exceptions,
and dependencies.
3. Validate the process with stakeholders.
4. Outcome: Create a process design document (PDD) for reference.
3. Design Phase

Objective: Create a detailed design for the automation solution.

Steps:
1. Develop the to-be process workflow.
2. Define the input, output, and success criteria for the bot.
3. Select appropriate tools and technologies (e.g., UiPath,
Blue Prism).
4. Prepare the Solution Design Document (SDD) to
guide development.
4. Development Phase

Objective: Build and configure the automation workflow.

Steps:
1. Use RPA tools to design and develop the bot.
2. Implement business rules, data handling,
and integrations.
3. Use modular development for easier maintenance.
4. Test the bot in a development environment.
5. Testing Phase

Objective: Validate the bot's performance and accuracy.

Steps:
1. Perform unit testing for
individual components.
2. Conduct end-to-end testing of the bot
with real data.
3. Test for exceptions and error
handling scenarios.
4. Ensure the bot meets business and compliance requirements.
6. Deployment Phase

Objective: Release the bot into the production environment.

Steps:
1. Deploy the bot to production servers or
cloud environments.
2. Monitor initial performance to ensure stability.
3. Conduct user acceptance
testing (UAT).
 4. Obtain sign-off
from stakeholders.
7. Maintenance and Monitoring Phase

Objective: Ensure the bot continues to function optimally post-deployment.

Steps:
1. Monitor bot performance through logs
and dashboards.
2. Handle updates for changing
business requirements.
3. Perform regular maintenance
and optimization.
4. Address exceptions and system
changes proactively.
8. Optimization Phase

Objective: Improve and scale automation.

Steps:
1. Analyze bot performance and
identify bottlenecks.
2. Refactor workflows to improve efficiency.
3. Expand RPA to other processes or integrate with AI for intelligent automation.
By following this methodology, organizations can implement RPA solutions effectively,
ensuring high ROI, scalability, and seamless integration into existing processes.
ARCHITECTURE OF RPA
The architecture of Robotic Process Automation (RPA) is designed to streamline
automation processes, enabling bots to mimic human interactions with digital systems. It
comprises various components that work together to ensure seamless automation. Below is a
breakdown of the key components of RPA architecture:
1. Bot Creator/Development Environment

Purpose: Used to design, develop, and configure RPA workflows.

Features:
 Drag-and-drop interfaces for easy development.
 Support for scripting and programming logic (e.g., Python,
.NET).
 Tools for testing and debugging bots.
Examples: UiPath Studio, Automation Anywhere Developer, Blue Prism Design Studio.
2. Control Center/Orchestrator

Purpose: Manages the bots and automation processes centrally.

Features:
 Bot scheduling and triggering.
 Monitoring bot performance and maintaining logs.
 Role-based access control for security.
 Scalability to manage multiple bots across environments.
Examples: UiPath Orchestrator, Automation Anywhere Control Room.
3. Bot Runner/Execution Environment
 Purpose: Executes the automation workflows created by the Bot Creator.
Features:
 Executes scripts or workflows on target systems.
 Operates in attended (with human interaction) or unattended (autonomous) modes.
 Communicates with the Control Center for updates and status reporting.
4. Input Sources

Purpose: Provide data required for automation processes.

Examples:
 Structured data from Excel files,
databases, and APIs.
 Semi-structured data from emails,
forms, or invoices.
 Unstructured data using OCR for
scanned documents.
5. Target Systems/Applications

Purpose: Systems or applications with which bots interact to perform tasks.

Examples:
 Enterprise applications like SAP, Salesforce,
or Oracle.
 Web portals for data extraction or entry.
 Legacy systems using screen scraping.
6. Exception Handling and Logging

Purpose: Manage errors and maintain records of bot activities.

Features:
 Automated retries for common errors.
 Real-time alerts and notifications for
critical issues.
 Detailed logs for auditing and compliance.
7. Integration Layer

Purpose: Enables bots to integrate with other tools, systems, or APIs.

Components:
APIs: Facilitate interaction with external systems for data
exchange.
AI/ML Models: Enhance decision-making capabilities for
dynamic tasks.
Third-party Tools: Integrate with CRM, ERP, or BPM platforms.
8. Security and Compliance Layer

Purpose: Ensures the secure and compliant operation of bots.

Features:
 Role-based access control.
 Data encryption during storage and transmission.
 Compliance with industry standards like
GDPR and HIPAA.
9. Monitoring and Analytics

Purpose: Tracks bot performance and provides insights for optimization.

Features:
 Dashboards for visualizing metrics like efficiency and
error rates.
 Predictive analytics to identify potential improvements.
 Real-time reporting for quick decision-making.
Workflow in RPA Architecture
The Bot Creator designs an automation workflow. The workflow is deployed to the
Control Center, which schedules and assigns tasks to bots. Bots in the Bot Runner
environment execute the tasks, interacting with Input Sources and Target Systems. Logs and
performance data are sent back to the Control Center for monitoring. Exception Handling
ensures smooth operation, while Analytics provide insights for future improvements. This
modular and scalable architecture ensures that RPA solutions are efficient, secure, and
adaptable to various business needs.
RPA AND EMERGING ECOSYSTEM
Robotic Process Automation (RPA) is increasingly being integrated into a broader digital
transformation ecosystem, which combines technologies like artificial intelligence (AI),
machine learning (ML), cognitive automation, and cloud computing. The convergence of
these technologies is shaping the future of automation and expanding the capabilities of RPA
beyond traditional rule-based tasks. Below are key components of this emerging ecosystem
and how RPA fits into it:
1. RPA and AI/ML Integration

AI & ML Capabilities: AI and ML technologies can enhance RPA by enabling bots to

handle more complex, data-driven tasks that require decision-making and adaptability. While
RPA automates structured, rule-based processes, AI and ML provide cognitive capabilities to
automate semi-structured and unstructured data tasks, such as sentiment analysis, image
recognition, and decision-making based on historical data.
Example: RPA bots can extract data from invoices using OCR (Optical Character
Recognition), while ML models predict invoice discrepancies based on historical data,
improving the accuracy of the automation process.
2. Cognitive Automation

Definition: Cognitive automation is a subset of AI that uses natural language processing

(NLP), machine learning, and computer vision to allow bots to understand, learn, and
interact in a more human-like manner.
Role in RPA: Cognitive automation broadens the scope of RPA by allowing bots to
interpret unstructured data (e.g., emails, scanned documents, voice interactions). RPA bots,
integrated with cognitive capabilities, can automatically extract meaningful information,
classify it, and make decisions.

Example: An RPA bot enhanced with NLP can process customer service emails,
recognize intent, and route them to the appropriate team, reducing human intervention.
3. Hyper automation

Definition: Hyperautomation refers to the combination of RPA, AI, ML, business process
management (BPM), and other advanced technologies to automate complex business
processes end-to-end.
Role in RPA: Hyperautomation takes traditional RPA a step further by automating not
only tasks but entire workflows. It incorporates AI to handle exceptions, integrates data from
multiple systems, and adapts to dynamic changes in business processes. The result is a more
agile and intelligent automation framework.
Example: A customer onboarding process can be fully automated using RPA for
document gathering, AI for customer verification, and ML for fraud detection, ensuring a
seamless and efficient experience.
4. Cloud RPA

Definition: Cloud RPA involves deploying and running RPA bots in the cloud, leveraging
cloud infrastructure to scale automation solutions more efficiently.
Role in RPA: Cloud-based RPA offers flexibility, scalability, and cost-efficiency. It
eliminates the need for on-premise infrastructure and allows bots to be accessed and
managed remotely. Cloud RPA also integrates with other cloud-based technologies,
enhancing automation capabilities.
Example: Companies using cloud-based RPA can automate processes like invoice
processing or HR tasks without maintaining dedicated servers, making it easier to scale
automation across global operations.
5. Low-Code and No-Code Development Platforms

Definition: Low-code and no-code platforms enable users with minimal technical
expertise to create and deploy RPA bots and workflows using visual interfaces and drag-and-
drop functionality.
Role in RPA: These platforms democratize automation by allowing business users
(citizen developers) to build their automation solutions, reducing the dependency on IT and
accelerating the implementation of RPA solutions.
Example: A business analyst can use a no-code RPA tool to automate customer data entry
tasks, reducing the burden on IT and speeding up the automation process.
6. Integration with IoT (Internet of Things)

Definition: IoT refers to a network of interconnected devices that communicate and share
data with each other, often in real time.
 Role in RPA: RPA can integrate with IoT devices to automate processes based on real-
time data from connected devices. For example, data from sensors can trigger automation
workflows, enabling bots to respond dynamically to changing conditions.
Example: In a smart warehouse, IoT sensors can track inventory levels, and RPA bots can
automatically reorder stock when levels drop below a certain threshold.
7. Block chain and RPA

Definition: Block chain is a distributed ledger technology that ensures data integrity and
transparency through decentralized and immutable records.
Role in RPA: Block chain can enhance RPA by providing a secure, transparent, and
auditable way of recording transactions. RPA bots can automate tasks such as contract
management, compliance checks, and data validation, while blockchain ensures the integrity
of the data processed.
Example: In supply chain management, RPA can automate inventory tracking, while
blockchain ensures the accuracy and security of transaction records.
8. Robotic Desktop Automation (RDA)

Definition: RDA is a subset of RPA that focuses on automating tasks on a single user's
desktop.
Role in RPA: RDA is often used in environments where user-specific tasks, such as data
entry, report generation, or customer support, need to be automated. It operates in the
background while the user continues working, improving efficiency without disrupting
workflows.
Example: RDA can automatically log a user into multiple systems, gather data from
different applications, and compile it into a report.
9. Digital Twin of an Organization (DTO)

Definition: A digital twin is a virtual representation of an organization, its processes,

systems, and operations.
Role in RPA: RPA can feed data into a digital twin model to simulate and optimize
business operations. By observing how processes perform in the digital twin, RPA bots can
be adjusted for better performance, ensuring optimal results.
Example: In a manufacturing company, a DTO of the production process can be used to
analyze and automate maintenance tasks by predicting machine failures and triggering
preventive actions through RPA.
Conclusion
The emerging RPA ecosystem, powered by AI, ML, cognitive automation, and other
advanced technologies, is transforming how businesses approach automation. By integrating
RPA with these technologies, companies can achieve hyper automation, scale automation
processes more effectively, and create intelligent systems that adapt to changing business
environments. As RPA continues to evolve, its role in the digital transformation journey will
expand, driving efficiency, innovation, and agility across industries.
 UNIT - II
Basics of RPA
Robotic Process Automation (RPA) is a software technology that uses software
robots (or bots) to mimic human actions and automate repetitive, rule-based tasks in digital
systems. Think of an RPA bot as a virtual employee that can interact with applications and
systems— just like a person would—to execute a predefined set of instructions.
RPA Working procedure:

RPA bots operate by interacting with the user interface (GUI) of applications, meaning
they don't typically require complex system-to-system integration (like APIs). The core
process involves:
1. Observing and Recording: A human user performs the task while an RPA tool
records the mouse clicks, keystrokes, and interactions with applications.
2. Developing a Workflow: The recorded actions are turned into a detailed, step-by-
step workflow or script. This is the set of rules the bot must follow. This step is often
done using low-code or no-code development tools within the RPA platform.
3. Execution (Bot Runner): The script is deployed to a Bot Runner, which executes
the automated task.
4. Monitoring and Management: A central Control Center manages, schedules,
monitors, and analyzes the performance of all deployed bots
5. Development Studio: This is the environment where a person designs and builds the
automation workflow, often using a drag-and-drop, low-code interface.
 6. The Bot (Software Robot): This is the executor. It runs the pre-programmed steps to
complete the task.
7. Control Center (Orchestrator): This is the central hub that schedules, manages,
monitors, and tracks the performance of all the deployed bots.
Types of RPA
There are two main types of RPA bots, categorized by the level of human interaction
required:
That's a very important distinction in RPA! The choice between Attended and
Unattended determines where and how the automation is deployed. Here is
a breakdown of the two main types of RPA bots:
Feature Attended RPA Unattended RPA
Metaphor Virtual Assistant Virtual Employee
Human Required. The human user mustNot Required. The bot operates
Interaction trigger the bot and may need to autonomously from start to finish.
intervene or make decisions
during the process.
Location Runs directly on the human Runs on a dedicated server or virtual
employee's machine in the background (Back-
desktop/workstation (Front- Office).
Office).
Trigger Manual/Event-based. Triggered Automatic/Scheduled. Triggered by a
by a user's click, a hotkey, or a system event (e.g., a file arriving) or
specific event (like on a preset schedule (e.g., every
receiving a customer call). night at 11 PM).
Best For Tasks that are part of a larger High-volume, repetitive tasks that
process involving real-time require zero human oversight and
customer interaction or human can run 24/7
judgment.
● Attended bots boost the productivity of individual employees in real-time. They are
collaborative tools.
● Unattended bots handle automation for the entire organization at scale, managing
long, resource-intensive processes.
 Many organizations use a Hybrid model, where attended bots on the front-end interact
with customers and then pass off standardized, high-volume work to unattended bots on the
back-end.
Benefits of RPA
RPA is highly effective for automating tasks that are repetitive, rule-based, high-
volume, and use structured data.
● Increased Accuracy: Bots follow instructions precisely, eliminating human errors
and ensuring 100% consistency.
● Higher Efficiency: Bots can work 24/7 and complete tasks much faster than a human,
leading to increased throughput and speed.
● Cost Reduction: Automating tasks lowers operational costs and provides a fast
Return on Investment (ROI).
● Improved Compliance: Consistent execution of processes makes it easier to comply
with regulatory standards and provides a clear audit trail.
● Enhanced Employee Satisfaction: Employees are freed from mundane, tedious tasks
to focus on work that requires human judgment, creativity, and strategic thinking.
● Accuracy: Eliminates human errors, ensuring $100\%$ consistency.
● Speed: Bots can work $24/7$ and execute tasks much faster than people.
● Cost Reduction: Lowers operational costs by automating time-consuming work.
● Employee Focus: Frees up human employees to concentrate on high-value, strategic
work that requires creativity and judgment.

Implementing RPA isn't just about buying software; it involves a structured, multi-
phase project, often referred to as the RPA Lifecycle.
The RPA Implementation Lifecycle
1. Discovery & Assessment (The "What" and "Why")
This is the strategic starting point where you decide what to automate and why.
● Process Identification: Identify business processes that are good candidates for
automation. The best candidates are usually:
o Highly Repetitive: Done frequently (daily/weekly).
o Rule-Based: Have clear, consistent steps with few exceptions.
o High Volume: Lots of transactions to process.
o Structured Data: Data inputs are consistent and predictable.
● Feasibility & ROI Analysis: Determine the technical feasibility of automating the
process and calculate the Return on Investment (ROI). You want to prioritize
processes that deliver the highest value quickly (known as "quick wins").
● Documentation: Document the process exactly as it is performed today ("As-Is"
process). This is critical for the next phase.
2. Design & Solution Architecture (The "How")
In this phase, you create the blueprint for the bot.
● Process Optimization: Before automating, simplify and standardize the current
process ("To-Be" process). Don't automate a bad process!
● Solution Design: The RPA Architect designs the technical solution, mapping out the
step-by-step logic, exception handling, data inputs/outputs, and how the bot will
interact with various applications.
● Platform Selection: If not already chosen, this is when you select the specific RPA
tool (e.g., UiPath, Automation Anywhere, Blue Prism) that best fits the requirements.
3. Development (The "Build")
This is where the bot is physically built using the chosen RPA tool.
● Bot Creation: The RPA Developer translates the "To-Be" design into a sequence of
actions, developing the automation script using the studio environment.
● Coding & Configuration: The developer configures the bot to perform tasks like
logging into systems, scraping data, applying business rules, and handling expected
errors.
● Modular Approach: Developers often use a modular approach, creating reusable
components to make the bot easier to maintain and scale.
4. Testing & Quality Assurance (The "Verify")
The most critical phase for ensuring reliability.
 ● Unit Testing: The developer tests small, individual components of the bot.
● System Integration Testing (SIT): Testing the entire workflow to ensure the bot
interacts correctly with all target applications (e.g., CRM, Excel, Email).
● User Acceptance Testing (UAT): The business user (the Subject Matter Expert or
SME) tests the bot to confirm it meets all business requirements and functions exactly
as a human would.
5. Deployment & Monitoring (The "Go Live")
The bot is moved from the testing environment to the live production environment.
● Deployment: The bot is securely installed and scheduled using the central Control
Center (or Orchestrator).
● Pilot Launch: The bot often runs in a controlled environment for a period, with
performance closely monitored.
● Monitoring: The team continuously tracks key metrics: transaction volume, error
rate, and time saved. This ensures the bot provides continuous value and runs
smoothly.
6. Scale, Optimization, and Governance (The "Grow")
This phase is about expanding the program across the organization.
● Optimization: Based on monitoring data, the bot is fine-tuned for better performance
and efficiency.
● Scaling: More processes are identified and added to the automation pipeline.
● Center of Excellence (CoE): A centralized team is often established to manage the
entire RPA program, set standards, provide training, and govern the development
lifecycle.
Processes that can be automated
The Different Types of Process Automation
Today’s RPA tools can execute scripts, have specialized tooling to automate complex
business processes, and they have the ability to interact with user interfaces. But RPA tools
go way beyond those basic capabilities. At a very high level, automation can be broken down
into four categories:
1. Front-End Automation
UI automation
2. Back-End Automation
API automation
3. Native Actions
Specialized actions that target specific business applications
4. Intelligent Automation
Machine learning & artificial intelligence for when more critical thinking is needed.
Combining these four types of automation gives users the ability to automate a wide variety
of tasks. And by including intelligent automation it introduces human decision-making logic
into the process.
Front-End Automation: UI Automation
UI automation provides the mechanisms to mimic human interactions with user interfaces
such as Windows applications and web browsers. UI automation capabilities generally fall
into three categories:
1. Legacy and Windows applications
2. Browser applications
3. Remote desktop applications via RDP, and others
The Windows and browser-based capabilities, for the most part, interact with the
underlying controls. For example, the automated action of a button click will cause a “button
click” event to be fired on that button. When interacting with a remote desktop, however, the
underlying application controls are not accessible to the remote session. Therefore, to mimic
a button click on a remote desktop, the RPA application needs to recognize graphical regions
that represent the button.
Pros of UI Automation
● Easy to use. Since UI automation mimics the steps that a human takes to complete
a task, a non-technical citizen developer can use it to automate their work.
● Only option to automate some applications. Some applications only provide a
UI. For example, a browser-based UI may be the only option available to the user to
 interact with that application. UI automaton may be the only option available for legacy
Windows applications as well.
Cons of UI Automation
● Changes to UIs may break automations. User interfaces change frequently for
many reasons including improving the user experience or to add features. When a
UI is changed, it may break the automation. Sometimes changing the size of a
window may cause the application UI to reconfigure itself to provide a better user
experience which may also break automations.
● Automating the decision-making process. Many of the UI actions that are
performed are a result of some human decision-making processes which are not
necessarily captured in the action itself. To represent the thought process, the user
will need to extend the recording to represent the decision-making logic.
● Takes over the desktop. The UI automation task takes over the mouse and keyboard
to mimic the user actions. As such, the user cannot be working on the computer at
the same time.
Modern RPA applications include recorders. Recorders make it much easier to
develop UI automations. Recorders fall into two categories:
1. Macro Recorders
Macro recorders “watch” the steps the user is performing and then runs those exact steps
in the exact same order. While macro recorders make it very easy to create automation, it’s
also a “one and done” process that you can’t edit or update.
2. Step Recorders
With step recorders, you record each UI action that you need to perform. While it’s
more tedious to create automaton, it has many advantages over macro recorders. For
example, you can edit and update recordings, debug recordings, and most of all, you’re
able to introduce your thought process in terms of business logic into the recording—all
from within the recorder.
Back-End Automation: API Automation
API automation is used to reach out to application programming interfaces (APIs) to
accomplish a task. For example, you can use API automation to automate the transfer of loan
application information from a loan origination service to a loan processing service.
Generally, APIs are either web service APIs or HTTP based RESTful APIs. (Note that web
services are an older technology that is no longer under active development, and as such, may
be deemed obsolete.)
 With API automation, the RPA application interacts with a pre-defined interface
provided by the external application to perform a task. Exchange of data is done using
standard data exchange formats such as XML or JSON.
As API automation involves the transfer of data, the API automation capability must
provide not only the capability to connect to APIs, but also the capability to process the data.
Pros of API Automation
● Robustness. One of the biggest advantages of API integration is robustness. APIs
rarely change, and even when the provider needs to update an API, they support the
older version of the API for some length of time. In addition, API interactions are
not impacted by changes to the desktop such as changing a window size or window
color scheme.
● Background execution. API automations can be executed while the user continues
to use their desktop.
Cons of API Automation
● Technical knowledge required. Working with APIs and common interchange
formats requires some technical knowledge. As such, API integration tasks target the
power user with some technical knowledge.
Related Content > RPA vs. API: Differences and Use Cases
Native Actions
Native actions provide user-friendly interfaces to automate activity against a specific
application such as an FTP application, Microsoft applications, databases, and more. While
UI automation and API automation are generally automations that can be used with multiple
applications that support the technology (i.e., an API or UI), native actions are designed to
provide a user-friendly interface to automate tasks against a specific application. A native
action is provided primarily for one of two reasons:
● The application is widely used in RAP activity, for example, email.
● The application does not provide a UI, nor a standard API, for example, databases.
While databases provide UIs to manage the database, in order to execute queries and
obtain results in a machine-readable format, the user essentially has to use specific
technologies such as database connections. In this case the native action is designed to
mask the complexity of working with that application.
Pros of Native Actions
● Easy to use. Native actions are probably the easiest to use as they are custom-built to
work with a particular application.
 ● Robustness. As they are custom-built to work with a particular application, they are
robust actions.
● Background execution. Native actions run in the background so the user can
continue to work using their desktop.
Cons of Native Actions
● Limited availability. As there are a very large number of applications that span
automation, it is almost impossible to provide native actions to all applications.
Intelligent Automation
Intelligent automation is designed to introduce “intelligence” into automation. Similar
to custom actions, intelligent automation is custom built. But unlike native actions, it is
custom built to satisfy a particular capability, in this case artificial intelligence (AI) and
machine learning (ML), rather than a particular application.
AI and ML are complementary technologies. They are used to aid in the decision-
making process. Some consider ML as the current state-of-the-art technology for AI, while
others consider ML the most widely used specialization of AI. The technology supporting AI
and ML is growing at a rapid pace supported by some of the biggest technology companies.
As such, the automation community is better served by RPA tools that integrate with industry
standard frameworks and industry specific solutions provided by companies that have the
expertise, rather than providing their own AI and ML solutions. In this sense, intelligent
automation is similar to a custom action that integrates with either a specific AI/ML
framework such as TensorFlow or [Link], or a specific intelligent solution that is provided
by experts in that solution space.
Attended vs Unattended Automation
No discussion about automation is complete without talking about attended vs
unattended automation. Unattended automation is an automated work item that can be
completed without the intervention of a human being. On the other hand, attended automation
requires human input at some point in the automated process. The human input could be as
simple as clicking a button or could include more complex scenarios requiring the filling of
forms, reviewing data, making corrections, and more.
When we think of state-of-the-art RPA, attended and unattended automation are
fundamental capabilities. When comparing attended and unattended automation to the four
types of automation discussed previously, they are not types of automation or the tools of
automation, rather they are one way to categorize the types of problems that RPA can solve.
Automate RPA
Automate is an RPA solution from Fortra. Automate has over 600 native actions that
span front-end automation and back-end automation, and a wide array of custom actions and
intelligent automation capabilities. It is a complete RPA solution that our customers count on
to transform virtually any business or IT process and brings together the applications that
keep their businesses running.
While Automate has many differentiating features, we would like to introduce a few
of our most powerful here. In peer reviews and industry publications, Automate is
consistently rated at the top for its ease-of-use. That’s because Automate’s no-code approach
makes building automation easy for citizen developers, while also providing advanced
options for power users to automate more complex tasks. The key advantages of having an
easy-to-use. RPA tool are twofold:
● Brings RPA to the citizen developer
● Minimizes technical debt
Another key differentiator is that Automate is simply RPA focused. There are many
complementary technologies to RPA, for example AI and ML, process discovery, workload
scheduling, capacity management, and the list goes on. In Automate, we believe in a best-of-
breed tooling approach. We strive to make Automate the best RPA tool that provides a
powerful API to integrate complementary technologies. Here too, the advantages are twofold:
● We have a singular focus – provide a solid RPA solution
● Customers can pick and choose the complementary solutions that best suit
their budgets and needs
Automate provides an innovative feature set and focuses on usability. Automate also
provides an innovative step recorder while our competitors almost exclusively provide macro
recorders when the limitations of macro recorders have been well documented. Our
innovative features focused on usability are also on display in our JSON action and our
approach to AI and ML.
And finally, in peer reviews Automate is constantly rated high in business value created.
When combined with our easy-to-use approach that minimizes technical debt, Automate
becomes even more attractive from a total-cost-of-ownership point of view. With this holistic
approach to automation, Automate allows users to get up and running quickly and see fast
ROI. Classification of Robots
The most common distinction is between fixed and mobile robots. These two types of
robots have very different working environments and therefore require very different
capabilities. Fixed robots are mostly industrial robotic manipulators that work in well-
defined environments adapted for robots. Industrial robots perform specific repetitive tasks
such soldering or painting parts in car manufacturing plants. With the improvement of
sensors and devices for human-robot interaction, robotic manipulators are increasingly used
in less controlled environment such as high-precision surgery.
By contrast, mobile robots are expected to move around and perform tasks in large,
ill- defined and uncertain environments that are not designed specifically for robots. They
need to deal with situations that are not precisely known in advance and that change over
time.
There is no clear dividing line between the tasks carried out by fixed robots and
mobile robots humans may interact with industrial robots and mobile robots can be
constrained to move on tracks—but it is convenient to consider the two classes as
fundamentally different.
There are three main environments for mobile robots that require significantly
different design principles because they differ in the mechanism of motion: aquatic
(underwater exploration), terrestrial (cars) and aerial (drones).
Robots for these three environments can be further divided into subclasses: terrestrial
robots can have legs or wheels or tracks, and aerial robots can be lighter-than-air balloons
or heavier-than-air aircraft, which are in turn divided into fixed-wing and rotary-wing
(helicopters).

Industrial Robots
One could argue that these are really automata and not robots. However, today’s
automata often rely on sensors to the extent that they can be considered as robots. However,
their design is simplified because they work in a customized environment which humans
are not allowed to access while the robot is working.
However, today’s robots need more flexibility, for example, the ability to manip- ulate
objects in different orientations or to recognize different objects that need to be packaged in
the right order. The robot can be required to transport goods to and from warehouses. This
brings additional autonomy, but the basic characteristic remains: the environment is more-
or-less constrained and can be adapted to the robot.
Additional flexibility is required when industrial robots interact with humans and this
introduces strong safety requirements, both for robotic arms and for mobile robots. In
particular, the speed of the robot must be reduced and the mechanical design must ensure
that moving parts are not a danger to the user.
The advantage of humans working with robots is that each can perform what they do
best: the robots perform repetitive or dangerous tasks, while humans perform more complex
steps and define the overall tasks of the robot, since they are quick to recognize errors and
opportunities for optimization.
Autonomous Mobile Robots
Many mobile robots are remotely controlled, performing tasks such as pipe inspec-
tion, aerial photography and bomb disposal that rely on an operator controlling the device.
These robots are not autonomous; they use their sensors to give their oper- ator remote
access to dangerous, distant or inaccessible places. Some of them can be semi-autonomous,
performing subtasks automatically. The autopilot of a drone stabilizes the flight while the
human chooses the flight path. A robot in a pipe can control its movement inside the pipe
while the human searches for defects that need to be repaired.
Fully autonomous mobile robots do not rely on an operator, but instead they make
decisions on their own and perform tasks, such as transporting material while navigating in
uncertain terrain (walls and doors within buildings, intersections on streets) and in a
constantly changing environment (people walking around, cars moving on the streets).
Efforts are being made to make systems more flexible, so that they can learn from a
human or adapt to new situations. Another active field of research addresses the interaction
between humans and robots. This involves both sensing and intelligence, but it must also
take into account the psychology and sociology of the interactions.
Humanoid Robots
Science fiction and mass media like to represent robots in a humanoid form. We are
all familiar with R2-D2 and 3-CPO, the robotic characters in the Star Wars movies, but the
concept goes far back. In the eighteenth century, a group of Swiss watchmakers—Pierre
and Henri-Louis Jaquet-Droz and Jean-Frédéric Leschot— built humanoid automata to
demonstrate their mechanical skills and advertise their watches. Many companies today
build
humanoid robots for similar reasons.
Humanoid robots are a form of autonomous mobile robot with an extremely complex
mechanical design for moving the arms and for locomotion by the legs. Humanoid robots
are used for research into the mechanics of walking and into human- machine interaction.
Humanoid robots have been proposed for performing services and maintenance in a
house or a space station. They are being considered for providing care to the elderly who
might feel anxious in the presence of a machine that did not appear human. On the other
hand, robots that look very similar to humans can generate repulsion, a phenomenon
referred to as the uncanny valley.
Educational Robots
Advances in the electronics and mechanics have made it possible to construct robots
that are relatively inexpensive. Educational robots are used extensively in schools, both in
classrooms and in extracurricular activities. The large number of educational robots makes it
impossible to give a complete overview. Here we give few examples that are representative
of robots commonly used in education.
Pre-Assembled Mobile Robots
These robots are relatively inexpensive, robust and contain a large number of sensors
and output components such as lights. An important advantage of these robots is that you
can implement robotic algorithms “out of the box,” with- out investing hours in mechanical
design and construction. However, pre-assembled robots cannot be modified, though many
do support building extensions using, for example, LEGO® components.
Robotics Kits
The LEGO Mindstorms robotics kits were introduced in 1998. A kit consists of
standard LEGO bricks and other building components, together with motors and sensors,
and a programmable brick which contains the computer that controls the components of the
robot.
The advantage of robotics kits is that they are flexible: you can design and build a
robot to perform a specific task, limited only by your imagination. A robotics kit can also
be used to teach students mechanical design. The disadvantages of robotics kits are that
they are more expensive than simple pre-assembled robots and that exploration of robotics
algorithms depends on the one’s ability to successfully implement a robust mechanical
design.
Robotic Arms
To act on its environment, the robot needs an actuator which is a component of a
robot that affects the environment. Many robots, in particular robotic arms used in industry,
affect the environment through end effectors, usually grippers or similar tools
 Educational robots are usually mobile robots whose only actuators are its motors and
display devices such as lights, sounds or a screen. End effectors can be built with robotics
kits or by using additional components with pre-assembled robots, although educational
robotic arms do exist Manipulation of objects introduces.
Differential Drive

The robot is a small autonomous vehicle with differential drive, meaning that it has
two wheels that are driven by independent motors . To cause the robot to move, set the motor
power to a value from −100 (full power backwards) through 0 (stopped) to 100 (full power
forwards). There is no predefined relationship between the motor power and the velocity of
robot. The motor can be connected to the wheels through different gear ratios, the type of
tires on the wheels affects their traction, and sandy or muddy terrain can cause the wheels to
slip. Proximity Sensors
The robot has horizontal proximity sensors that can detect an object near the robot.
There exist many technologies that can be used to construct these sensors, such as infrared,
laser, ultrasound; the generic robot represents robots that use any of these technologies. We
do specify that the sensors have the following capabilities: A horizontal proximity sensor
can measure the distance (in centimeters) from the robot to an object and the angle (in
degrees) between the front of the robot and the object.

The Algorithmic Formalism

Algorithms that are implemented as computer programs are used by the embedded
computer to control the behavior of the robot. We do not give programs in any specific
programming language; instead, algorithms are presented in pseudo code, a structured
format
 using a combination of natural language, mathematics and pro- gramming structures.

Business models for implementing RPA

Business models for implementing RPA include deploying it through attended,
unattended, or hybrid models, depending on the level of human-bot collaboration needed.
Another approach is to use RPA-as-a-Service, where a vendor provides the automation
solution. Successful implementation requires a strategic approach, including a business case,
selecting the right processes to automate, building a strong team, and establishing governance
and monitoring.
RPA deployment models
Attended RPA: Bots work alongside human employees in real-time to assist with
interactive tasks, such as providing a customer service agent with information as they speak to a
customer.
Unattended RPA: Bots operate independently without human intervention, running
on a schedule or when triggered by specific events, to handle high-volume, rule-based tasks.
Hybrid RPA: This model combines both attended and unattended automation to
create more dynamic workflows that leverage the strengths of both humans and bots.
Strategic and service-based models
Building an RPA business from scratch: This involves creating a business focused
on providing RPA services to clients, including developing a niche, building a team, and creating
a use case library.
RPA-as-a-Service (RPA-as-a-Service): A service-based model where a vendor
provides RPA solutions, tools, and management, which can be attractive for companies with
limited internal resources or expertise.
Center of Excellence (CoE): Establishing a dedicated team or "Center of Excellence"
within the organization to drive RPA strategy, development, and governance across the
enterprise.
RPA for successful implementation
Business Case: Develop a clear business case that outlines goals, potential ROI,
timelines, and risks to get executive buy-in.
Process Identification: Start by automating high-volume, rule-based, and repetitive
tasks with low exceptions, focusing on processes that offer a tangible return on investment.
 Talent and Skills: Reskill employees to use low-code/no-code RPA platforms
(citizen- led development) or train them to work alongside bots.
Governance and Monitoring: Establish clear rules and guardrails for your
automations and continuously monitor their performance to ensure they remain accurate and
efficient.
Integration with AI: For more complex tasks, integrate RPA with artificial
intelligence (AI) to enable intelligent automation that can handle both structured and unstructured
data.

Centre of Excellence
RPA or Robotic Process Automation automates manual, repetitive, high-volume tasks
that humans perform every day. For example, an RPA could take over the task of entering
data into a spreadsheet. The robot or bot as they are popularly called would enter all the
information, exactly the same way, each time, saving you time and effort.
Another example can be an employee submitting a request to update his address,
contact information, etc., and the bot would automatically update it in all the relevant
database fields for various departments such as payroll, HR, IT, and so on.
As you can see, Robotic Process Automation is more about Automation Software and
not the shiny physical robots roaming around. RPA bots interpret, communicate with other
systems, and trigger actions to automate a wide variety of manual repetitive and rule-based
business processes. These bots are ‘trained’ to mimic human interaction and can interact with
any IT application or website in the same way a human would.
What is an RPA Center of Excellence (CoE)
RPA adoption is increasing by leaps and bounds across various industries. According
to a report by Grand View Research, the global RPA market was valued at USD 1.89 billion
in 2021 and is expected to grow at a CAGR of 38.2% from 2022 to 2030.
When done correctly, Robotic Process Automation provides many benefits to the
business otherwise it can be a costly overhead. Sometimes, organizations proceed to RPA
implementation without proper planning and fail miserably at it. This is where an RPA
Center of Excellence can be useful.
 A Center of Excellence for RPA is a central unit that identifies automation
opportunities, builds use cases for automation, and provides structure, best practices, support,
and runs automation projects in an organization.
It helps a business achieve end-to-end automation of business processes by combining
people, technology, and processes together. It also measures the success of RPA initiatives in
an organization. The responsibilities of an RPA CoE are listed in the image below.

Need CoE for RPA

RPA CoE is essential to realize the full potential of RPA in an organization. It helps
break down silos and encourages better communication among various entities and business
processes within an organization.
The main benefits of RPA CoE are listed below-
● Maximize ROI and reap full benefits of RPA investments
● Implement and embed RPA effectively and efficiently
● Monitor, measure, and accelerate automation
● Manage RPA pipeline and delivery
● Make automation scalable and achievable
● Improve operational efficiency
Steps to Setup Robotic Process Automation CoE
Follow the step-by-step process explained below to set up a Center of Excellence
for Robotic Process Automation in your company.
Step 1 – Select a cross-functional team for CoE
It is important to have representation from different functional areas in the Center of
Excellence. These may include executives and/or business leaders, project managers,
architects, automation developers, testers, etc. It is essential to select the team members based
on their skills, relevant experience, and necessary qualifications.
Team size will depend on the size of your company and the scope of RPA projects
you plan to implement. You need to find the right balance as a small team size will be more
agile but you also need to provide enough resources to handle the workload effectively.
Step 2 – Define team structure and governance framework
The next step is to build a governance framework that includes operational guidelines,
best practices to follow, change management and release management guidelines, and
standards for bot management. This is an important step for the smooth functioning of the
RPA Center of Excellence that should not be overlooked.
Step 3 – Define responsibilities for RPA CoE Team Members
Once you have the team in place and the operational framework is ready, you need to
clearly assign responsibilities to team members so there is no ambiguity and communication
gap. This step will set the expectations right among the team members and also define who is
responsible for what.
Step 4 – Design your automation roadmap
Designing an automation roadmap starts with reviewing the current processes and
shortlisting the candidates fit for automation.
Next, you need to start asking questions like what are your goals? Which processes
will be automated first? What is the target RoI for RPA? What tools you will need? Which
RPA platform is the ideal fit for your needs?
Brainstorming the above questions and recording the findings will lead to a well-formed
automation roadmap.
Step 5 – Launch your RPA CoE
With all the basic planning in place, you are now ready to roll out the Center of
Excellence for Robotic Process Automation for your company. Start small but aim and
prepare for big goals. Initially, start with small goals like preparing templates for automation
tasks such as processing a new bot request or fixing issues with existing bots, etc.
It might take months to see measurable progress but it is important to keep reviewing
the RPA implementation and refining the CoE model. Having a great RPA tool like
Automation Anywhere is quite helpful to monitor, measure and analyze your progress.
Factors to consider while selecting an Automation Tool
● Enterprise Ready – Tool should have all the necessary functionalities such as
reporting, auditing, asset management, release management, etc. that an enterprise
will need.
● Scalability – Does the tool support scalability? Consider on-prem as well as on-cloud
deployment as a must-have requirement.
 ● Security – The Automation tool must have security built into its DNA. With the
unprecedented rise in cyber-attacks and data breaches, this is a non-negotiable feature
that you must consider while selecting a tool.
● Easy to use – The tool must be intuitive and easy to use for better adoption.
● Flexibility – The RPA tool should be flexible and easy to integrate with 3rd party
tools.
Types of RPA
There are 3 major types of robotic process automation: attended automation,
unattended automation, and hybrid RPA.
1. Attended Automation
This type of bot resides on the user’s machine and is usually invoked by the user.
Attended automation is best suited for tasks that are triggered at points that are
programmatically hard to detect.
For instance, let’s say a customer service representative would normally need up to 3
screens and complete 5 manual steps so as to complete a transaction. Instead of going through
all of these, the customer service rep can choose to launch an automation code.
RPA bots can work like a rep, perform the needed operations and ask for guidance
from the rep if there is a need. For employees that face customers and still need to complete
manual work, attended automation can be deployed to augment these tasks.
2. Unattended Automation
These bots are like batch processes on the cloud and data processing tasks are
completed in the background. Unattended automation is deal for reducing the work of back-
office employees. Unattended automation can be launched in the following ways: data input
in a specified location, bot initiated, orchestrator initiated, and specified intervals.
3. Hybrid RPA
In this type of RPA, attended and unattended RPA boys are combined so as to provide
automation for both back and front office activities. This allows for end to end automation of
a process.
Types of Robotic Process Automation Tools
When you’re looking for automation tools for your project you need to know
which type to use. Here are 3 types of RPA tools.
Macros
They automate processes that are in a single system and they are also the oldest tools
in automation. If the process you want to automate is simple enough and requires only one
tool
like a spreadsheet then macros are the best fit. Macros can be used to organize data, make
calculations etc.
IT Process Automation
They can automate complex multi-system dependent processes; these are function
specific automation tools. IT PA is behind the scenes bots but they are built and require
supervision by experienced IT professionals.
They handle complex tasks like alerts from multiple sources, prioritize action plans,
and deploy one of your defined possible action plans. They also notify key members on your
team that require notifications of the activity before closing the ticket.
Cognitive Automation Tools
These bots has screen scraping capabilities which allow them to make use of a
desktop like a person to complete tasks that require multiple systems. They are not as precise
as ITPA tools and they are easy to use. By a simple drag-and-drop programming interface,
they are augmented with artificial intelligence capabilities that will help them learn from
previous examples. They use natural language processing and they can also be called
intelligent or cognitive bots.
Cost Savings
RPA can lead to a 40% reduction in average handling cycle time. You can also expect
it to enhance the customer experience and make a business resilient and operational 24/7.
And when it comes to cost businesses can see processing costs reduced by 30 to 80%. That
means, driving return on investment in quarters versus years.
Robotic process automation will drive operational efficiencies and cost savings across
core lines of business. Thus, transforming customer outcomes reducing business risk and
optimizing existing processes and systems.
Benefits of RPA
Lack of Human Error
All of the processes are performed without human error. Yep, every process is
performed exactly as per the rules that are defined.
By default, that’s already a great achievement.
When it comes to quality the ability to create a full audit trail reduces compliance and
business risk.
Human error is eliminated while there is a greater than 40% increase in FTEs,
operations will now be able to focus on customers in the area of delivery.
Compliance
The next benefit is around compliance that quality and adherence to process is perfect
for compliance. So, if you’re in a heavily regulated industry, where you need to demonstrate
that you are performing the processes against certain rules and legislation, this is a great
opportunity to leverage RPA for those benefits.
Speed
These processes can be performed 24/7 and can be scaled across a larger flexible
workforce. That means that if you need to respond to a surging demand, you’re able to do so
a lot quicker than if you were to use people in the traditional model.
RPA also brings with it great agility. However, you get agility with regards to being
able to transform your process or make process changes much quicker than if you were to roll
it across a manual workforce.
Data
When you’re performing this scale of automation you get a huge amount of data. The
great thing is, you can see all of the data in any of the systems at the point of which you
perform the transaction.
More than that, you can capture within a single database giving you a great
opportunity to get some real insight from the data. This would also allow you to understand
the patterns behind the transactions and also what’s driving certain behaviors.
Experienced Employee
Experience and staff experience can both be improved positively with RPA. Be it if
you are performing pay integration if you’re onboarding a new employee, or if you’re
responding to customer queries.
The ability to do it to quality quicker than you would be able to do it manually really
gives rise to a better experience.
Cost Benefit
RPA typically performs at a third of a cost of an optional resource in the ninth of the
cost of an onshore [Link] 1/3 of the cost.
Having said that, that’s not really the main driver that we see behind businesses
adopting this. Sometimes this is really more about how do you expand and grow your
business.
Especially without the linear costs associated with recruiting more people to do the
same work. In essence, through automation you are able to free up your best people to do
your best work.
Building an RPA team
Setting up and managing an RPA team is a foundational piece of the equation, in
which people management matters just as much as the automated technology in use.

The goal of Robotic Process Automation (RPA) is to transform and streamline

business processes by automating repetitive, time-consuming tasks.
However, like any large-scale technology implementation, a successful RPA project
hinges on effective project management, including a carefully assembled team with the right
skills, and a robust testing and quality assurance process.
But according to Ernst & Young, the probability for RPA initial project failure is as
high as 50%.So, only with proper planning can organizations reduce that risk of failure.
RPA Team and Project Management Fundamentals
Robust project management principles are the cornerstone of a successful RPA
implementation. Apply these examples:
Clearly Defined Scope: Outline project objectives, deliverables, and timelines. Identify
processes ideal for automation and determine success metrics.
Risk Management: Proactively identify potential risks, such as data security concerns or
resistance to change. Develop mitigation strategies.
Stakeholder Communication: Maintain clear communication with all stakeholders,
including business users, IT, and management. Transparency ensures buy-in and smooth
execution.
Agile Methodology: Consider an agile approach, breaking the project into smaller phases
with regular feedback loops. This allows for flexibility and course corrections.
Team Roles and Requirements
Implementing RPA requires a diverse set of skills, including technical and non-
technical talent.
These are the core resources your team needs:
Business Analysts (BAs): They play a pivotal role in process analysis and documentation.
BAs identify potential automation targets, gather requirements, and ensure alignment with
business goals.
RPA Developers: These are the technical wizards who design, configure, and implement the
RPA bots. They require expertise in the chosen RPA software and basic programming
knowledge.
Project Manager: This is the orchestrator who keeps the project on track and manages
resources effectively. Strong communication and organizational skills are a must.
Quality Assurance (QA) Testers: The QA team meticulously tests RPA bots in a staging
environment, ensuring they function as intended and meet all requirements.
Project Management and Collaboration Tools
Leveraging the right tools can streamline collaboration and promote more efficiency:
Project Management Software (Asana, Jira): Manage tasks, allocate resources, track
progress, and manage reporting. Asana
Process Documentation Tools (Visio, Lucidchart): Create detailed process flow diagrams,
which are crucial for RPA development.
Collaboration Platforms (Slack, Microsoft Teams): Facilitate seamless communication and
file sharing among team members.
Quality Assurance (QA) and User Acceptance Testing (UAT)
Meticulous testing is critical to ensure RPA bots function as expected and deliver the
intended value.
QA Testing
Test Case Development: A thorough test plan outlines different scenarios that bots must
handle, including edge cases and exceptions.
Test Execution: QA testers rigorously execute test cases, then identify and reporting defects.
User Acceptance Testing (UAT): Business users test the RPA solution in a real-world
environment, validating functionality and usability. This ensures the automation meets their
needs and addresses their pain points.
Here are some additional tips for RPA teams and a successful implementation project:
Start Small: Take baby steps. Begin with a pilot project targeting a well-defined process, and
focus on a process area with a potential for high ROI.
Change Management: Address potential employee concerns early on. Communicate
benefits of RPA and provide adequate training to ensure smooth adoption.
Governance Model: Establish clear roles, responsibilities, and decision-making processes for
the ongoing management of your RPA program.
The Benefits of an Internal RPA Team:

Deeper Process Understanding: Internal teams possess a nuanced understanding of your

specific business processes and their pain points. This allows for the development of highly
customized and efficient automation.
Agility and Scalability: An in-house team fosters agility, enabling quicker adaptation to
changing business needs and faster deployment of new automations.
Reduced Reliance on External Vendors: Building internal expertise lessens dependence on
external vendors, potentially reducing long-term costs.
The Power of the CoPilot Approach:
While building an internal team offers significant advantages, it’s crucial to recognize the
value experienced RPA vendors bring to the table. Here’s where the CoPilot approach shines:
Vendor Expertise + Internal Knowledge: CoPiloting combines the deep process
understanding of your internal team with the vendor’s RPA development expertise. This
ensures automations are built with best practices in mind, leading to robust and future-proof
solutions.
Knowledge Transfer: Experienced vendors can act as mentors, transferring valuable RPA
development knowledge and best practices to your internal team. This empowers your team
to become self-sufficient over time.
Vendor Support: The CoPilot approach doesn’t end with development. Vendors can provide
ongoing support, troubleshooting issues, and offering guidance on complex automation
challenges.
The CoPilot Advantage:The CoPilot approach creates a synergy that surpasses the benefits
of either a purely internal or external solution. Here’s how:

Building Your Successful RPA Team:

Implementation of Robotic Process Automation (RPA)

For the successful implementation of RPA within a business organization, RPA
designers and developers need to follow six major steps which are listed and explained below
 Identify processes to automate
 Get organization-wide support
 Select the right RPA tool/software
 Prepare an implementation plan
 Test the RPA solution
  Deploy and improve
Let's discuss each of these steps of RPA implementation in detail.
Step 1: Identify Processes to Automate
RPA implementation starts with identifying the right, high-impact processes to automate.
In a business organization, not all workflows or processes are suitable for RPA, hence this
step helps picking up only those processes which have higher impacts and ROI.
We should choose only those processes for RPA that meet some specific criteria which
are given below −
 Rule-base, repetitive tasks
 High volume processes
 Processes which are highly prone to human errors
 Processes that have least exceptions
Step 2: Get Organization-Wide Support
RPA implementation is a digital transformation of a business, hence it needs support from
teams and stakeholders across the organization to be successful.
An organization can achieve success in RPA implementation by −
 Educating its teams about RPA’s working and benefits
 Resolving employees concerns like fear of job displacement
 Explaining how RPA will improve their productivity, etc.
Step 3: Selecting the Right RPA Tool/Software
In RPA implementation, selecting the right RPA tool is a very important step. There
are several RPA tools are available in the market, and each of them have its own unique
features.
The business organization must select the most appropriate tool that aligns with its
business operation goals.
While selecting an RPA tool, the organization may also consider the following parameters
 Ease of use and interface complexity.
 How easily it is scalable.
 It is compatible with existing systems or not.
 How strong customer support the developer provides, etc.
Step 4: Prepare an Implementation Plan
After identifying processes to automate, getting support from teams, and selecting the
right automaton tool, now the organization must prepare an effective plan that can be used as
a roadmap to implement RPA within the organization. This plan is supposed to provide
process
 mapping details, methods to save time and reduce errors, and realistic timelines for
implementation phases.
Step 5: Test the RPA Solution
Before deploying the RPA solution into the actual working environment, it must be
tested thoroughly to ensure its desired functionality. This step involves observing the
performance, identifying and fixing the bugs, and making the potential improvements.
Step 6: Deploy and Improve
Once, the RPA solution is successfully tested, it is to be deployed in the actual environment and
continuously monitored to evaluate its performance. Also, it is improved or optimized to provide better
accuracy over time.

Unit :3
Automation stages and the role of a Business Manager:
RPA stands for Robotic Process Automation. Hearing the word Robotic, people assume
that physical robots complete the task. But what RPA actually means is - "It is the technique
of automating an actual business process to complete a task without the intervention of
human beings".
 Robotic - Robots are entities developed to complete tasks performed by human.
 Process - Process is a sequence of tasks combined to perform a meaningful action.
 Automation - Automation is done to perform tasks without human intervention.

RPA Tools :
 Blue Prism
 Ui Path
 Automation Anywhere

Life Cycle Of RPA Project :

1. Identify
2. Analyse
3. Design
4. Develop
5. Test
6. Implement

1. Identify and Analyze - The initial stage is to identify the business process that is to be
automated. Once the process is identified, a team of RPA architects joins to discuss the
solution for their process, it's complexity and decides how to carry on with the project.
2. Design and Develop - RPA architects create a Process Definition Document (PDD) which
explains each step in every process. Next, an Object Model Diagram or a flowchart is drawn
to determine the sequence of steps. An RPA tool (Blue Prism, UiPath, Automation
 Anywhere, etc) to work with is now decided. The flow chart is then converted into a bot with
the help of the tool.
3. Testing - Once the bot is developed, it is being tested to check if it satisfies all the
requirements. Testing is either done by the development team itself or by a separate testing
team.
4. Implement - The bot is now deployed. If any issues are encountered at this stage, the project
is again sent to the development and testing phase for enhancements.

First Stage- Identify

The RPA bot’s life cycle begins with a crucial step where businesses need to decide which process
requires automation. If not done carefully, then the next stages will be a total waste of time and yield
no profitable results.

Refer to the list below to understand what kind of processes can be automated using RPA. Processes
that are:

• Manual and repetitive in nature (the frequency of repetitiveness can be daily, weekly, monthly, or
yearly)

• Activated by readable input types such as input from excel sheets, word files, etc

• Rule-based and do not require much human intervention

• Structured and contains stable inputs

• Voluminous in nature

Processing of huge volumes of invoices, sales order entry, ERP data entry, P2P process, and human
resources-related processes such as leave authorization, attendance management, onboarding, etc.
fall under the above categories. You can choose any process that fits your future business operations
and brings a suitable ROI to you.

Second Stage- Discover and Analyse

To ensure that your RPA bot project does not fail miserably, it is important to do the process
analysis. Here, you will get answers to important questions like-

• How much time your business will save by automating that process?
• Is the process dependent on too many systems?

• Is the process a high-volume task or not?

• Is it prone to too many errors when done manually?

• Is the process fit for automation?

These questions help you select the right process for automation which is not vulnerable to bot
errors and deliver tangible returns. An RPA expert, Subject Matter Expert, and the operation user
will work together at this stage to check whether the process is automation friendly or not which
ultimately prevents breakdowns and bot failures.

It also helps businesses to get process clarity, stability in business continuity plans, and improve
productivity and ROI. As a result, RPA implementation can be done at a faster rate. At this stage,
complexity analysis of the process, scalability, code re-usability, technology landscape, and ROI
analysis is also done.

The advantages of automating the task should also be taken into consideration at the discovery stage
to make the analysis process fully proven. It can be any of the following things a business must want
to achieve with automation:

1. Increase in profit

2. Better productivity of employees

3. Higher efficiency with minimal resources

4. Reducing manual errors

5. Standardizing the process

6. Improve compliance

7. Gain better scalability

8. Provide better customer experience

Third Stage- Solution Design

The actual process of RPA implementation begins from the third stage where a technical architect
and process architect create a process definition document (PDD) which contains detailed steps of
the process.

The purpose of PDD is to provide as much information as required to successfully implement the
RPA and recognize any gaps or possibilities in the process. It has information like- what would be
the process flow, common errors, and metrics to be judged, any dependencies, transaction load,
resource availability for support, any exceptions, etc.

The budget for the RPA project, time to be spent on it, team requirements, a necessary tool, and
other information are also mentioned in the PDD. The next step is creating an Object Model
Diagram which is nothing but a flowchart to give a bigger picture of the process to be automated.
Also, the developer will get to understand the process requirements at each step.
Fourth Stage- Development

Though RPA is better than traditional programming and requires no serious technical knowledge of
programming language, it is still best to have some level of understanding. Because this stage is very
crucial and any mistakes at this point means your bot is not going to meet the expectation.

You also need RPA tools for development. Here’s a list of some of the popular tools offered by the
reputed vendors:

• Automation Anywhere- It is a widely used open-source cloud-native web-based automation

platform that allows businesses to automate complex tasks. The best part about automation
anywhere RPA tool is that it offers script less automation. Meta bots, task bots, and IQ bots are the
types of RPA bots that can be developed using this tool.

• UI Path- High-scale automation is possible through this open-source RPA tool. It can automate
any web app or desktop application and make the bots smarter using NLP and AI/ML technologies.
UiPath offers cloud hosting options along with advanced screen scraping solutions. It consists of
three components- Uipath Studio, UiPath Robot, and UiPath Orchestrator.

• UI. Vision- Another open-source RPA software that you can pick is UI. Vision formerly known as
Kantu. It is a cross-platform tool that offers browser extension for visual desktop automation.
Compatibility with Selenium IDE, screen scrapping, command line interface, visual UI testing, and
the ability to work offline are a few features of UI. Vision.

• WorkFusion- An all-in-one RPA tool for enterprises is WorkFusion which comes with intelligent
automation feature. Pre-built bots, analytics, an automation studio, and an automation orchestrator
are some more features of this SaaS crowd computing platform.

RPA tools are used to create automation scripts and codes. Each code executes the step as
mentioned in the PDD. Also, the script should be such that the bot can handle variations in inputs.

Fifth Stage- User Acceptance Tests

Once the automation scripts for your digital workforce i.e., RPA bots are developed completely, a
user acceptance test is run to check whether it satisfies the requirement or not under a pre-production
environment. The bot may exhibit errors during testing, in that case, the fourth stage is repeated to
remove the flaws from the bot. Again, a UAT is run on the bot to check if it’s working as desired.

If the bot successfully passes the test, then it is deployed in the next stage.

Sixth Stage- Deployment and Maintenance Phase

Deployment is the second last stage in the RPA life cycle where the functioning of the bot is
guaranteed. Here, it runs on the production environment or host environment and is managed
through an orchestrator.

If any errors occur in RPA bot. it is sent back to the testing phase to fix the final errors. After
ensuring that the automated bot is ready to be implemented in the business architecture, it is moved
to the last and final stage i.e., execution where it provides the expected results of automation.
 However, the Robotic Process Automation lifecycle does not end there, continuous support and
maintenance is needed at each stage to ensure that the bot does its task with high precision.
Otherwise, businesses cannot reap the benefits of RPA some of which include an increase in per-
employee output, a reduction in processing cost, the safety of sensitive data, scalability of business
opportunities, and more.

These benefits are the reason why the demand for RPA is proliferating, and most companies
consider this technology as its integral part.

Guidelines for tracking the implementation success

To track implementation success, define clear, measurable goals (SMART), establish KPIs like
ROI, user adoption, efficiency gains, and performance metrics, and continuously monitor progress
against a detailed plan with regular reviews, feedback loops, risk management, and strong
communication to ensure alignment with the project's core purpose and business value.
1. Define Clear Objectives & Scope:

 SMART Goals: Ensure goals are Specific, Measurable, Achievable, Relevant, and Time-bound
(e.g., "Increase sales by 10% in 3 months").

 Business Value: Link objectives to tangible benefits like increased revenue, efficiency, or
customer satisfaction.

2. Establish Key Performance Indicators (KPIs):

 Financial: Track Return on Investment (ROI).

 Operational: Monitor efficiency (e.g., % reduction in manual tasks), uptime, response times, and
error rates.

 User-Focused: Measure adoption rates (training completion, usage), and customer satisfaction
scores.

 Fidelity/Reach: Assess how well the implementation matches the plan and the percentage of the
target audience reached.

3. Plan & Execute Methodically:

 Detailed Plan: Create a roadmap with milestones, tasks, timelines, and resource allocation.

 Assign Roles: Clearly define responsibilities for all stakeholders.

 Risk Management: Proactively identify and plan for potential risks and changes.

4. Monitor & Evaluate Continuously:

 Regular Reviews: Build in evaluation and review processes for ongoing progress checks.

 Feedback Loops: Gather feedback from users and stakeholders to make adjustments.

 Performance Monitoring: Track KPIs throughout the lifecycle, not just at the end.

5. Foster Communication & Alignment:

 Team Communication: Maintain open, consistent communication with the project team.

 Stakeholder Alignment: Ensure leadership and the entire organization understand and are aligned
with the vision and goals.

6. Focus on Purpose & Quality:

 Core Purpose: Keep the "why" (the business purpose) central to all activities.

 Quality Control: Don't just focus on time/budget; ensure quality is maintained.

Phase 1: The Foundation (Pre-Implementation Essentials)

You cannot measure success if you do not know where you started. The biggest mistake
organizations make is failing to document the "before" state.

1. Establish a Documented Baseline Before automating a process, you must quantitatively define
how it performs manually.

 Manual Average Handling Time (AHT): How long does it take a human to do one
transaction?
 Manual Error Rate: What percentage of transactions currently require rework due to
human error?
 Current Volume: How many transactions occur daily/weekly/monthly?
 Current Cost: What is the fully loaded cost (salary, benefits, overhead) of the human
effort currently dedicated to this task?

2. Define Explicit Success Criteria per Process Don't just say "We want to automate Invoice
Processing." Define what success looks like for that specific process.

 Example: "Success for Invoice Processing means reducing AHT from 12 minutes to under
2 minutes and achieving a straight-through processing rate of 90%."

3. Align with Business Objectives Ensure the metrics you choose matter to the leadership team.
Are they focused on cost cutting, improving customer experience speed, or reducing compliance
risk? Your tracking must reflect their priorities.
Phase 2: Defining the Key Performance Indicators (KPIs)

RPA metrics generally fall into three categories: Operational, Financial, and Strategic. You need a
mix of all three.

A. Operational Metrics (Bot Health & Efficiency)

These metrics tell you if the technology is working correctly.

 Bot Uptime/Availability: The percentage of scheduled time the bot is actually running
and available to work.
 Throughput: The number of transactions processed per time unit (e.g., invoices per hour).
Compare this against the manual baseline.
 Success vs. Failure Rate: The percentage of transactions completed successfully versus
those that failed due to system errors or exceptions.
 Average Handling Time (Bot AHT): How fast the bot performs the task compared to the
human baseline.
 Utilization Rate: Are your bots busy? If a bot only runs for one hour a day, you are
underutilizing your license infrastructure.

B. Financial Metrics (The "Hard" Numbers)

These are the metrics that CFOs care about.

 Hours Returned to the Business: The most common metric. (Manual AHT – Bot AHT) *
Volume = Hours Saved.
 FTE Reallocation Value: Crucial distinction: Don't just track "headcount reduction."
Track the value of the work the employees are doing now that they aren't performing the
manual task.
 Cost per Transaction: How much did it cost to process an item manually vs. via
automation?
 ROI (Return on Investment): (Total Value Generated – Total Cost of Ownership) / Total
Cost of Ownership.
o Total Value: Savings + Revenue Gains + Cost Avoidance.
o Total Cost (TCO): Licenses + Infrastructure + Developer Costs + Maintenance
Support.

C. Strategic & Quality Metrics (The Business Impact)

These measure the ripple effects of automation.

 Error Reduction Rate: Improvement in accuracy compared to the manual baseline.

 Compliance/Audit Trail: 100% of bot actions are logged. The ability to produce a perfect
audit trail instantly is a massive success metric in regulated industries.
 Scalability: The ability to handle a 200% spike in volume during peak season without
hiring temporary staff (cost avoidance).
 Cycle Time Reduction: The total time from the start of a business process to the end.
(e.g., Does a customer get their loan approved faster?).

Phase 3: The Mechanics of Tracking

How do you actually gather and present this data?

1. Utilize the RPA Platform's Analytics Modern RPA platforms (UiPath, Automation
Anywhere, Blue Prism, Microsoft Power Automate) have built-in analytics dashboards (e.g.,
UiPath Insights, AA Bot Insight).

 Guideline: Configure these tools immediately. Do not rely on spreadsheets to track bot
performance.

2. Create Tiered Dashboards Different stakeholders need different data Views:

 The Operational Dashboard (For RPA Controllers): Real-time view of bot status,
current queue items, immediate failures, and utilization.
 The Process Owner Dashboard (For Managers): Daily/Weekly view of throughput,
exceptions handled by humans, and speed vs. baseline.
 The Executive Dashboard (For C-Suite): Monthly/Quarterly view of aggregated ROI,
total hours saved across the enterprise, and strategic wins.

3. Track Exception Handling (The Hidden Metric) Tracking how many items the bot could not
process is vital.

 If a bot has a 40% business exception rate (items sent back to humans for review), the
implementation may be a failure, even if the bot technically ran successfully. High
exception rates indicate poor process selection or poor developmen

Phase 4: Qualitative Measures (Beyond the Numbers)

Success isn't always a number on a spreadsheet.

1. Employee Satisfaction (CSAT/ESAT) Survey the employees who used to do the manual task.
Are they happier now that they are focusing on higher-value work? Or are they stressed because
the bot breaks constantly and they have to fix its mess?

 Warning Sign: If employees are secretly running the manual process parallel to the bot
because they don't trust it, your implementation has failed.

2. Customer Satisfaction Did the automation result in faster responses to customers or fewer
errors in their orders? Track Net Promoter Score (NPS) related to the automated processes.

Phase 5: Governance and Continuous Improvement

Tracking is not a one-time event. It is a lifecycle.

1. The Role of the CoE (Center of Excellence) The RPA CoE is responsible for defining
standard metrics and ensuring every deployed process reports against them. They own the "single
source of truth" for RPA data.

2. Post-Deployment Reviews Schedule mandatory reviews at 30, 90, and 180 days post-go-live.
Compare actual performance against the business case predicted in Phase 1.

3. The Optimization Loop Tracking should lead to action.

 If utilization is low, find more processes for that bot license.

 If error rates are increasing (due to underlying application changes), schedule maintenance
development.
 If theROI is failing to materialize, re-evaluate if this process should remain automated.
 Metrics/Parameters to be considered for gauging success
Gauging RPA success involves Financial Metrics (ROI, Cost Savings, Payback
Period), Operational Metrics (Productivity, Cycle Time Reduction, Throughput, Accuracy,
Exception Rate, Bot Utilization), and Business/Human Metrics (Employee Satisfaction,
Compliance, Customer Experience), focusing on quantifiable gains like FTE savings, faster
processes, fewer errors, and freed-up staff for higher-value work to prove tangible business
value.

Financial & ROI Metrics

Return on Investment (ROI): Compares benefits (cost savings) against RPA costs (licenses,
development).

Cost Savings: Reduced labor costs (FTE reduction), error correction costs, and compliance
fines.

Payback Period: Time to recoup initial RPA investment.

Operational & Efficiency Metrics

Productivity: Increased output (tasks/transactions per hour/day).

Cycle Time Reduction: Time to complete a process drops significantly.

Throughput: Higher volume of work processed.

Accuracy & Quality: Near-zero errors, ensuring consistent, high-quality output.

Bot Utilization Rate: Percentage of time bots are actively working vs. idle.

Exception Rate: Frequency of tasks needing human intervention (lower is better).

Automation Rate: Percentage of processes automated.

Business & Human Impact Metrics

 Employee Satisfaction: Staff redeployed to more engaging, strategic tasks.

 Compliance & Consistency: Bots follow rules perfectly, reducing risk.

 Customer Satisfaction: Faster service and fewer errors improve CX.

 Scalability: Ability to easily scale automation up or down.

Key Steps to Measure

1. Establish Baseline: Measure performance before automation.

2. Define KPIs: Choose metrics aligned with business goals (e.g., cost savings for finance, speed
for operations).
3. Track Continuously: Monitor metrics post-implementation to show ongoing value and identify
improvements.

RPA Metrics
1. Total Automated Processes

This is the sum of all the automated processes you have in production that
make up your bot portfolio. This operational metric acts as an indication of
how RPA programs evolve and grow, how adept teams are at identifying RPA
opportunities and prioritizing them through to development.

Learn more: Automation Uptime: The Key to Maximizing the Value of

RPA

2. Velocity

Velocity refers to the average time it takes for an automated process to

execute. This RPA metric is commonly tracked because it quantifies the time
and cost savings of having a bot do the work quicker than an employee.

3. Utilization

Utilization is how often an automated process is executed and when.

Utilization indicates if you are leveraging 24/7 bot availability, which is one of
RPA’s key benefits.

4. Accuracy

Accuracy refers to how often the automated process is executed with errors.
This metric indicates if your automations deliver another key RPA selling
point: improved process output quality that yields fewer errors than manual
execution.

5. Expected Business Value

Expected Business Value is an RPA metric that essentially consolidates all the
other KPIs. At its most basic, Expected Business Value is the sum of all the
cost savings accrued from increased velocity, utilization, and improved
accuracy multiplied by the cost of an FTE over a given period.

Enterprise Metrics
Following are the enterprise metrics to measure the success of an RPA ?
Time gains' value (TGV)? Time gains' value(TGV) compares the costs of processes
carried out by humans with RPA bots. This equation may be used to calculate it.

TGV= (EC ? AC)/AC x 100%

Where,
EC is the costs of processes performed by employees, including wages (including
leaves and vacations), taxes, and office and workplace expenses (rent, utilities,
etc).

AC stands for the expenses associated with the services provided by bots,
including license fees, development costs, virtual machine/hosting costs, and
maintenance costs.

Your baseline metric for determining RPA ROI is TGV.

RPA Return on Investment(ROI) ? Processes Robotics Automated A key
business metric called return on investment (ROI) should demonstrate how much
money your organisation was able to make (or save) as a result of using RPA.
To determine the RPA ROI, consider the Value of Time Gains (above point). In
order to fully understand RPA ROI, two more factors must be considered ?
Process speedup A?Value ? A?The value of process acceleration reveals how
much actual money was earned by using automation. This may be shown, for
instance, by how expediting the customer onboarding process affects the number
of customers handled before and after automation, multiplied by the average
benefit per client.
B?Value of error reduction ? Value of error reduction? This measure shows
how much money can be saved by eliminating mistakes. It should correspond to
the priorities of your company.
It could, for instance, represent the total cost of business deals lost as a result of
errors or protracted processing, the cost of manually correcting errors
(represented by payroll costs, such as 30% of 1 FTE), the rise in the proportion of
cases that meet SLAs, the improvement in data quality, or anything else that is
essential for a specific process or organization.
Once VoPA, VoER, and VTG have been calculated, we may calculate the RPA ROI
as follows.

[(TGV*AC + Value of Process Acceleration + Value of Error Reduction) ? AC]/AC x

100%

Business Value Assumed ? The RPA indicator called as Expected Business

Value compiles all extra business?related KPIs connected to RPA. It is calculated
by multiplying the overall cost savings (achieved through greater performance,
better resource usage, and fewer errors) by the average FTE costs during a
certain time frame.

Rise in productivity ? The "gained productivity" metric is one of the most often
utilized by enterprises to assess the performance of RPA. It demonstrates how
many FTEs were added as a result of automating a certain operation. For
instance, if automation replaced the manual labour of 4 people who would
normally spend 2 hours per day doing the activity, the productivity gain would be
1 FTE/month.

Cost per Error ? The cost of an error that occurred during a specific automation
is disclosed by this measure. It should include the cost of the labour hours
needed to fix the problem as well as the total value lost due to downtime.
Utilization of License ? License utilization gauges how much the business uses
their RPA provider license. If your UiPath?based bots are using the license to the
greatest degree possible but are unavailable for 10% of the time over a given
period due to maintenance or downtime, your license utilization will be at 90% in
this case.

Technical Metrics
Following are the technical metrics to measure the success of an RPA ?

Speed of Process Automation ? When using an automated process, you may

look at the process velocity to determine the typical time needed to finish one
case or project.

Average Automation Development Time ? These statistics show how long it

typically takes to create and set up one RPA bot, as well as how many hours an
RPA developer works on it, in terms of FTEs or the number of hours they work on
it.

Bot Success Rate ? Bot Success Rate/Bot Accuracy Rate shows the proportion
of cases handled by the bot for a certain operation. RPA success rates of 80% or
more are considered ideal. An RPA bot with a 99% accuracy rate is definitely
possible to build.

Scalable automation ? This statistic shows how easy it is to scale a certain

method. The time and cost to install a new machine or reproduce the bot should
be compared to the time and cost to hire and onboard a human processor to
carry out the same tasks, including the payroll costs (for instance, 30% FTE).

In general, if the RPA bots are developed following all other best practices, they
should grow pretty quickly.

Scalability in development ? Demonstrates the portion of the old automation

code that can be applied to the new automation. Since they can be created by
re?constructing the existing ones, adding a new bot typically gets easier and
takes less time as the amount of automation produced for one business
increases.

Failure Rate ? The proportion of time that your bot may be completing a task
but isn't due to a problem or maintenance is known as the downtime rate.

Person Hours for Break?Fix ? Data on the amount of time needed to resolve a
specific problem is available in the Break?Solve Person Hours metric. The
quantity of FTEs or man?hours required to correct the automation and bring it
back on track should be specified.
Robot licensing
A licensing process most commonly starts with activating your Orchestrator license.
Afterward, you license your Robot by connecting it to Orchestrator or from the Command
Line, using the LicenseTool utility.

When your Robot is not connected to Orchestrator, you can activate the license with the
help of the Command Prompt.

Attended licenses
To execute attended automations, you need to allocate one or more user licenses to your
robots.

For this, you need to have a robot account in Orchestrator. Once the user license is
assigned to a specific username, that user can run one or more attended automations on
the computer under their username.

The following user licenses are available for attended automations:

 Attended

 Citizen Developer

 Automation Developer

Unattended licenses
To execute unattended automations, you need to allocate one or more robot licenses
(or runtimes) to your robots, specifically to the machine that hosts your robots. The
number of runtimes assigned to a machine represents the maximum number of
concurrent executions. For example, with one runtime, you can execute only one
unattended automation at a time. With five runtimes, you can execute up to five
unattended automations at the same time, on the same host machine.

Depending on the type of automation, allocate the runtimes as follows:

 For foreground automations - allocate one runtime, as this type of automations are
executed one at a time.
  For background automations - Windows machines require one runtime, as they
execute one background automation at a time. Windows-Server machines can
execute several background automations simultaneously, which represents a
concurrent execution.

 For concurrent executions - allocate more than one runtime. The number of
allocated runtimes determines how many automations you can execute
simultaneously on the same machine.

The following runtimes are available for unattended automations:

 Production (Unattended)

 Testing

LicenseTool utility
The [Link] is a command-line utility which enables you to activate
your machine online or offline, and update your license information.
The LicenseTool utility activates your license locally, which requires you to select the
Standalone license type when creating a robot in Orchestrator.

The following sections provide the most common commands for online, offline, and
generic licensing operations. The commands need to be initiated in the same folder
where the utility resides, which be default is the "C:\Program Files\UiPath\Studio" folder.

Online Operations

The following commands require an active internet connection in order to process your
request.

Activate
The activate command is used to activate a license online via an existing license code.
The following parameters are supported:

Parameter Description Priority

-l, -- The license code required for activation. Mandatory

LicenseCode

-u, --ProxyUrl The URL used for the proxy connection (such Optional
as [Link]

-p, --ProxyPort The Port number of the proxy connection. Optional.

Mandatory if the -
u parameter is used.

-s, --ProxyUser The username associated with your proxy connection. Optional.
Mandatory if the -
u parameter is used.

-w, -- The password for the user associated with your proxy Optional.
 Parameter Description Priority

ProxyPassword connection. Mandatory if the -

u parameter is used.
C:\Program Files\UiPath\Studio\[Link] activate -l 1234-1234-
2194-5598
License registration state: ActiveLicense
License successfully activated!

Online activation can also be done from Studio.

Update
The update command is used update an existing license online. The following parameters
are supported:

Parameter Description Priority

-u, --ProxyUrl The URL used for the proxy connection (such Optional
as [Link]

-p, --ProxyPort The Port number of the proxy connection. Optional.

Mandatory if the -
u parameter is used.

-s, --ProxyUser The username associated with your proxy connection. Optional.
Mandatory if the -
u parameter is used.

-w, -- The password for the user associated with your proxy Optional.
ProxyPassword Mandatory if the -
connection.
u parameter is used.
C:\Program Files\UiPath\Studio\[Link] update
License registration state: ActiveLicense
License successfully updated!
Deactivate
The deactivate command is used to deactivate a local license. This way, the license
becomes available for activation on a different computer. The following parameters are
supported:

Parameter Description Priority

-u, --ProxyUrl The URL used for the proxy connection (such Optional
as [Link]

-p, --ProxyPort The Port number of the proxy connection. Optional.

Mandatory if the -
u parameter is used.

-s, --ProxyUser The username associated with your proxy connection. Optional.
 Parameter Description Priority

Mandatory if the -
u parameter is used.

-w, -- The password for the user associated with your proxy Optional.
ProxyPassword Mandatory if the -
connection.
u parameter is used.
C:\Program Files\UiPath\Studio\[Link] deactivate
License registration state: NoLicenseAvailable
License successfully deactivated!

Offline Operations
Activation-Request
The activation-request command is used to generate an activation token from your
license code. The generated token needs to be used on the Activation Portal to generate
the corresponding license file. The following parameters are supported:

Parameter Description Priority

-l, -- The license code required for activation. Mandatory

LicenseCode

-o, --FileName Writes the license information to file. If this parameter is not Optional
specified, the license information is displayed in the command
prompt window.
C:\Program Files\UiPath\Studio\[Link] activation-request -l
1234-2303-2194-5598
Activation Token:
eyJsaWNlbnNlQ29kZSI6Ijk1NTUtMjMwMy0yMTk0LTU1OTgiL12345WFpbCI6InNvbWUuZW1haWxAZ
XhhbXBsZS5vcmciLCJtZXRhZGF0YSI6eyJyYW0iOiIzNDE0NjA0MTg1NiIsImRpc3BsYXlOYW1lIjo
iSW50ZWwoUikgVUhEIEdyYXBoaWNzIDYzMCIsInZlcnNpb24iOiIxOS43LjAiLCJzeXN0ZW1MYW5nI
joiMDQwOSIsInN5c3RlbU1vZGVsIjoiT3B0aVBsZXggNTA2MCIsIm9zTmFtZSI6IlBDLURPRE9JVUI
iLCJ1c2VyTmFtZSI6ImJvZ2Rhbi5kb2RvaXUiLCJzeXN0ZW1OYW1lIjoiUEMtRE9ET0lVQiIsImRpc
3BsYXlSZXMiOiIxMDI0IGJ5IDc2OCBwaXhlbHMsIFRydWUgQ29sb3IsIDYwIEhlcnR6IiwicHJvY2V
zc29yIjoiSW50ZWwoUikgQ29yZShUTSkgaTctODcwMCBDUFUgQCAzLjIwR0h6Iiwic3lzdGVtVHlwZ
SI6Ing2NC1iYXNlZCBQQyJ9LCJsaWNlbnNpbmdNb2RlbERhdGEiOnsidXNlcklkIjoiYm9nZGFuLmR
vZG9pdSIsIm1hY2hpbmVJZCI6IlBDLURPRE9JVUIifX0=
Go to [Link] and paste the activation token in the
dialogue box to generate the license file for offline activation.
Activate-Offline
The activate-offline command is used to activate a license offline. It uses the license
file generated by the Activation Portal from the provided activation token generated by
the activation-request command. The following parameters are supported:

Parameter Description Priority

-f, --LicenseFile The path to the license file obtained from the activation Mandatory 1
portal.
 Parameter Description Priority

-i, -- The content of the license file received after using Mandatory1
LicenseContent the Activation-Request operation.

 1
- You can only use either the -f or -i parameters with the activate-
offline operation. They are not both supported at the same time.
 C:\Program Files\UiPath\Studio\[Link] activate-offline -
f c:\Downloads\[Link]
 License registration state: ActiveLicense
License successfully activated!

Offline activation can also be done from Studio.

Update-Request
The update-request command is used to generate an update token for your license. The
update token needs to be used on the Activation Portal to generate the corresponding
license file. The following parameters are supported:

Parameter Description Priority

-o, -- Writes the license information to file. If this parameter is not specified, Optional
FileName
the license information is displayed in the command prompt window.
C:\Program Files\UiPath\Studio\[Link] update-request
Update Token:
eyJsaWNlbnNlQ29kZSI6Ijk1NTUtMj102345yMTk0LTU1OTgiLCJlbWFpbCI6bnVsbCwibWV0YWRhd
GEiOnsicHJvY2Vzc29yIjoiSW50ZWwoUikgQ29yZShUTSkgaTctODcwMCBDUFUgQCAzLjIwR0h6Iiw
ic3lzdGVtTW9kZWwiOiJPcHRpUGxleCA1MDYwIiwidXNlck5hbWUiOiJib2dkYW4uZG9kb2l1IiwiZ
GlzcGxheVJlcyI6IjEwMjQgYnkgNzY4IHBpeGVscywgVHJ1ZSBDb2xvciwgNjAgSGVydHoiLCJ2ZXJ
zaW9uIjoiMTkuNy4wIiwicmFtIjoiMzQxNDYwNDE4NTYiLCJzeXN0ZW1MYW5nIjoiMDQwOSIsIm9zT
mFtZSI6IlBDLURPRE9JVUIiLCJkaXNwbGF5TmFtZSI6IkludGVsKFIpIFVIRCBHcmFwaGljcyA2MzA
iLCJzeXN0ZW1UeXBlIjoieDY0LWJhc2VkIFBDIiwic3lzdGVtTmFtZSI6IlBDLURPRE9JVUIifSwib
GljZW5zaW5nTW9kZWxEYXRhIjp7InVzZXJJZCI6ImJvZ2Rhbi5kb2RvaXUiLCJtYWNoaW5lSWQiOiJ
QQy1ET0RPSVVCIn19
Go to [Link] and paste the update token in the dialogue
box to generate the license file for offline update.
Update-Offline
The update-offline command is used to update a license offline. It uses the generated
file by the Activation Portal from the provided update token generated by the update-
request command. The following parameters are supported:

Parameter Description Priority

-f, --LicenseFile The path to the license file obtained from the activation Mandatory 1
portal.

-i, -- The content of the license file received after using Mandatory 1
LicenseContent the Update-Request operation.

 1
- You can only use either the -f or -i parameters with the update-
offline operation. They are not both supported at the same time.
 C:\Program Files\UiPath\Studio\[Link] update-offline -f
c:\Downloads\[Link]
  License registration state: ActiveLicense
License successfully updated!
Deactivation-Request
The deactivation-request command is used to deactivate a local license offline and
generate a deactivation token. The license is immediately deactivated on the local
computer and another one can be activated if needed. The generated deactivation token
needs to be used on the Activation Portal to deactivate the license. Please note that the
license which was deactivated offline with this command can not be reused until it is
released. The following parameters are supported:

Parameter Description Priority

-o, -- Writes the license information to file. If this parameter is not specified, Optional
FileName
the license information is displayed in the command prompt window.
C:\Program Files\UiPath\Studio\[Link] deactivation-request
Deactivation Token:
eyJsaWNlbnNlQ29kZSI6Ijk123458My0yMTk0LTU1OTgiLCJsaWNlbnNpbmdNb2RlbERhdGEiOnsid
XNlcklkIjoiYm9nZGFuLmRvZG9pdSIsIm1hY2hpbmVJZCI6IlBDLURPRE9JVUIifSwibWV0YWRhdGE
iOnsib3NOYW1lIjoiUEMtRE9ET0lVQiIsInVzZXJOYW1lIjoiYm9nZGFuLmRvZG9pdSIsInZlcnNpb
24iOiIxOS43LjAiLCJkaXNwbGF5UmVzIjoiMTAyNCBieSA3NjggcGl4ZWxzLCBUcnVlIENvbG9yLCA
2MCBIZXJ0eiIsInN5c3RlbU5hbWUiOiJQQy1ET0RPSVVCIiwicHJvY2Vzc29yIjoiSW50ZWwoUikgQ
29yZShUTSkgaTctODcwMCBDUFUgQCAzLjIwR0h6Iiwic3lzdGVtVHlwZSI6Ing2NC1iYXNlZCBQQyI
sInJhbSI6IjM0MTQ2MDQxODU2IiwiZGlzcGxheU5hbWUiOiJJbnRlbChSKSBVSEQgR3JhcGhpY3MgN
jMwIiwic3lzdGVtTGFuZyI6IjA0MDkiLCJzeXN0ZW1Nb2RlbCI6Ik9wdGlQbGV4IDUwNjAifX0=
License successfully deactivated locally!
To release the license on the sever side and use it on another machine, go to
[Link] and paste the deactivation request certificate as
text in the <code>Deactivate your licence</code> tab.

Generic Operations

The [Link] utility also contains a few generic commands. They provide
information about your license, and can help you get accustomed to the supported
commands and parameters.

Command Description

info Displays information about the license, such as:

 Activation Id
 License registration state
 License code
 Start date
 End date
 Grace Period (days)
 End date including grace period
 Next check date

help Displays information about all the supported commands and parameters.

version Displays the version of the [Link] utility.

 UNIT:4
Automation Debugging

Debugging
Debugging is the process of identifying and removing errors that prevent the project from
functioning correctly. It is recommended to perform debugging during the design stage of
the automation project, at activity, file and project level.

Debugging can be performed using several options, defined in the ribbon and explained
in the Debugging Actions page.

By default, debugging is performed on the local robot. You can run or debug your
projects using a robot on a remote machine by enabling remote debugging.

Several panels make it easier to view the debugging process, add values or monitor
variables and arguments.

Start Debugging
The options for running and debugging a file or project are available both in
the Design and Debug tabs.

Option Description

Debug Click Debug or use F5 to debug the whole project.

 Option Description

Run Click Run or use Ctrl + F5 to run the whole project.

Debug File Click Debug File or use F6 to debug the current file.

Run File Click Run File or use Ctrl + F6 to run the current file.

The default action under Run/Debug ribbon button can be configured from Backstage
View > Settings > Design tab. Pick from Debug File, Run File, Debug Project,
or Run Project, as the default action when clicking the button.

During debug, click the Break button to pause. The activity which is being debugged
remains highlighted when paused. Once this happens, you can choose other debug
actions like Step Into or press Stop to exit and return to design mode. The keyboard
shortcut for the Stop button is F12.

It is recommended to use Break along with Slow Step so that you know exactly when
debugging needs to be paused.

The Continue option is available when the debug process is paused.

Automation Library:

In robotic process automation (RPA), an automation library is a collection of pre-built functions

and methods that a software robot uses to interact with various applications and systems. These
libraries save developers from writing code from scratch for common tasks like clicking buttons,
entering data, or working with files.
RPA libraries can be categorized based on their functionality and the platforms they automate:
General-Purpose RPA Libraries and Frameworks
These solutions offer a wide range of capabilities for both desktop and web automation, often
within a single ecosystem.
 RPA Framework: An open-source collection of libraries designed for use with both Robot
Framework and Python. It provides a comprehensive set of tools for web, desktop, email, and file
system automation, including specific libraries for interacting with applications like Excel, Outlook,
and SAP.

 Robot Framework: While originally for test automation, it has extensive libraries for RPA, using a
keyword-driven approach that is human-friendly and versatile.

 RPA for Python (formerly TagUI for Python): Offers a simple and powerful API for automating
tasks across websites, desktop applications, and the command line.

Python-Specific Libraries for Focused Tasks

For developers working within the Python ecosystem, several specialized libraries are commonly
used to handle specific aspects of automation:
 PyAutoGUI: A cross-platform library for GUI automation that mimics human actions like mouse
movements, clicks, and keystrorokes. It is highly useful for automating repetitive tasks that
involve interacting with the screen directly.

 Selenium: A popular library primarily used for automating web browsers. It allows scripts to
interact with web pages, fill out forms, and extract data, making it a staple for web-based RPA.

 Pywinauto: A library specifically for automating Windows GUI interactions.

 Openpyxl and Pandas: Libraries used for working with Excel files and data manipulation,
analysis, and cleaning in data-centric RPA projects.

 PyPDF2 (or similar PDF libraries): Used to read and write PDF documents, a common task in
many business processes.

Commercial RPA Tools with Integrated Libraries

Major commercial RPA platforms also include extensive built-in libraries and drag-and-drop
interfaces that abstract the underlying code, making automation accessible to non-developers.
 UiPath: A widely used platform featuring process recording and integration libraries for popular
enterprise applications.

 Automation Anywhere: A cloud-based platform that includes an extensive library of pre-built

automation components and a marketplace for sharing workflows.

 Blue Prism: Offers a comprehensive automation suite with a visual "Object Studio" for building
workflows using a drag-and-drop interface.

Activation Packages:

About the UI Automation activity package

The UI Automation activity package contains all the basic activities used for creating
automation projects.

These activities enable the robots to:

 Simulate human interaction, such as performing mouse and keyboard commands

or typing and extracting text, for basic UI automation.
 Use technologies such as OCR or image recognition to perform Image and text
automation.
 Create triggers based on UI behavior, thus enabling the robot to execute certain
actions when specific events occur on a machine.
 Perform browser interaction and window manipulation.

To create automations, choose one of the following experiences:

 Low-code—Use low-code automations paired with Classic, Modern, and Computer

Vision activities. Low-code automations use a visual interface with drag-and-drop
activities from activity packages, making it accesible for a broad user base.
 Coded—Use coded automations, paired with UI Automation APIs. Coded
automations, which utilize UiPath services (equivalent to activity packages) and
 their corresponding APIs (equivalent to activities), allow you to create automations
using code. Moreover, coded automations can use .NET NuGet packages, and
custom C# classes that you build within UiPath Studio. The UI Automation activity
package supports APIs starting with v23.10.3.
IMPORTANT: Automation processes that use UI Automation activities cannot run under
a locked screen.
NOTE:
 Starting with v20.10.5, the UI Automation Next package has been deprecated and
the existing UI Automation package has been expanded to include all the modern
features previously available in UI Automation Next. You are also able to install the
unified UI Automation activity package even on Studio versions 2020.4.1 and
lower. This displays all the classic and modern activities in the activities pane.
Read more about the Modern Design Experience.
 Starting with [Link] v19.11, all Abbyy related activities
have been moved to a separate package. Install the [Link]
package if you want to use its activities for OCR, Cloud OCR, classification, and
data extraction.
 As of v18.3.6877.28298, the [Link] package was split into the UI
Automation and System packages. Find out more about the Core Activities Split.

Dependencies
The UI Automation activity package contains the following internally-developed
dependencies:

 [Link] - enables the functionality of OCR and Computer Vision engines.

 UiPath - an essential library for UI Automation activities.

The [Link] dependency package includes third-party libraries. These external

dependencies are used exclusively for the purpose of enabling the implementation of
specific activities in the [Link] package. Here are some
examples:

 [Link] - used exclusively in the Abbyy Cloud OCR activity, at run-

time, as a wrapper over the Abbyy online service calls.
 [Link] - used exclusively in the Abbyy OCR activity, at run-
time, as a wrapper over the Abbyy FineReader Engine calls.
 [Link] - used exclusively in the Microsoft OCR activity, at run-time,
when executed on a Windows 7 or Windows Server machine.

Particular scenarios might require management of strict UI Automation dependencies

versions. For example, a language for the Tesseract OCR engine must be manually
installed per [Link] version. This means that for processes using that language
you need to use the corresponding UI Automation activity package. You can find out
more on this page.

The table below enlists the dependencies shipped with each version of the package:

[Link] [Link] UiPath

25.10.22 3.16.0 25.10.160.17874

 [Link] [Link] UiPath

25.10.21 3.16.0 25.10.160.17874

25.10.20 3.16.0 25.10.158.57528

25.10.19 3.16.0 25.10.155.37129

25.10.16 3.15.0 25.8.152.27793

25.10.13 3.15.0 25.6.146.54041

25.10.12 3.15.0 25.6.142.41639

Core Activities split

Starting with the v2018.3 release, the Core Activities Package is split into two distinct
packages, [Link] and [Link]. This has
been done with the intention of offering you more control over which activity versions
you use in the execution of your automation projects. In correlation with the Project
Dependencies feature, this split enables you to choose exactly the version of activities
you want to use as a dependency for your project.
Whenever a project created with a version of Studio older than v2018.3 is opened with
Studio v2018.3 or higher, the project is automatically migrated and the
new System and UI Automation packages replace the old Core package.

Remember to properly migrate your processes when updating the 2018.3 UiPath
Platform. The dependencies and activities installation algorithm has improved, which can
cause conflicts when executing processes with packages installed from local feeds. If you
encounter any issues while updating, check out possible solutions on this page. Also,
remember to check out how to Open Projects Created with Previous Versions.

NOTE: Once the migration is performed, you cannot revert the project to use the
old Core package.
Starting with Studio v2018.3 or higher, you cannot install the Core package from
the Package Manager. However, rest assured that
the [Link] and [Link] packages contain
all the activities that were in the old one. Additionally, from v2018.3 on, you can use any
combination of activity packages regardless of what version of Studio you are using at
that moment.
NOTE: Once a project is published with v2018.3 or higher, it can no longer be executed
by using a v2018.2 or lower Robot.
Please note that the location of the tessdata folder which is used to install languages for
the Google OCR engine has been moved from %ProgramFiles(x86)%\UiPath\Studio
essdata to %UserProfile%\.nuget\packages\[Link]. You can read more about
installing and changing the language for the Google OCR engine on this page.
For more information on how this change impacts Studio, you can read more here.

Core Legacy Activities

The Core Legacy Activities package (the [Link] meta-package) was

created as a result of the Core Activities Split to ensure compatibility between Legacy
Processes and Robot versions v2018.3 or newer. The Core Legacy Activities and Legacy
 Processes are defined as follows:
 Core Legacy Activities - The [Link] meta-package is available
starting with the v2018.3 release. It references
the [Link] and [Link] packages
whenever a legacy process is executed by a v2018.3 or newer Robot.
 Legacy Process - A process created with Studio v2018.2 or lower which uses the
former [Link] package as a dependency.

While the Robot is resolving dependencies, it searches for the UI

Automation and System packages. If they are not available, it uses the Lowest
Applicable Version runtime rule to determine what UI Automation and System package
versions to use, which needs to be greater than the default one.

Using a different UI Automation package

If a different version of the [Link] package is needed for

executing a process, the [Link] v18.3.6897.22543 package
needs to be removed from the following locations and replaced with the required one:
 The Orchestrator feed.
 The default packages location - %Program Files (x86)%\UiPath\Studio\
Packages in versions prior to 2021.4 or %Program Files%\UiPath\Studio\
Packages starting with version 2021.4.
 The NuGet cache - %userprofile%\.nuget\packages\[Link].

If the Robot machine has access to the Internet, then the Official feed from
the [Link] file must be removed to prevent the Robot from downloading it again.
Read more about Managing Packages.

Activation Packages:
RPA (Robotic Process Automation) "Activity Packages" are pre-built collections of automation
components (like activities, workflows) in tools like UiPath that enable robots to perform tasks like
data entry, web scraping, UI interaction, and system API connections, bundling functions for
finance, HR, customer service, etc., to automate repetitive, rule-based business processes.
Common Activity Package Categories & Examples
 UI Automation: (Core package) Simulates human actions like mouse clicks, keyboard input, text
extraction, browser interaction, and OCR for image/text recognition.

 System Activities: File management, email automation, scheduling, application launching, and
managing processes.

 Data Manipulation: Excel, CSV, JSON, XML processing, data mapping, and data transformation
activities.

 Web Automation: Specific activities for web scraping, browser automation (Chrome, Edge,
Firefox), and interacting with web elements.
 Application-Specific: Packages for SAP, Salesforce, Oracle, or other enterprise systems,
allowing direct interaction with their interfaces or APIs.

 Integration Packages: Connects to databases (SQL), cloud services (Azure, AWS), or

enterprise systems via APIs.

Common Business Processes Automated by Packages

 Finance: Invoice processing, bank reconciliation, expense reports, financial reporting.

 Human Resources: Employee onboarding/offboarding, payroll, attendance tracking, resume

screening.

 Customer Service: Ticket routing, customer query responses (chatbots), data updates in CRM.

 IT Operations: User provisioning, system monitoring, password management.

 Supply Chain: Inventory management, order processing, logistics tracking, catalog updates.

How They Work

These packages contain activities (like "Click," "Type Into," "Read Text," "Extract Table") that
developers chain together in a workflow, essentially telling a digital robot what steps to take, on
which applications, and with what data, automating processes previously done manually.
Basic automation Tasks:
Basic Robotic Process Automation (RPA) tasks involve automating repetitive, rule-based digital
activities that mimic human actions, such as data entry, copying/pasting, filling
forms, extracting data, generating reports, processing invoices, and managing employee
onboarding, primarily by interacting with various applications like a human would, improving
speed and accuracy.
Common Basic RPA Tasks
 Data Entry & Migration: Moving data between systems, updating CRM records, or inputting
information from spreadsheets.

 Form Filling: Automatically completing online forms with data from other sources.

 Data Extraction: Pulling specific data from documents (invoices, emails, PDFs) or websites (web
scraping).

 Email Management: Opening emails, extracting information from attachments, and sorting
messages.

 Report Generation: Compiling data from multiple sources and formatting it into standard reports.

 File & Folder Management: Moving, copying, renaming, and organizing digital files.

 Application Launch & Login: Automatically opening applications and logging in with
credentials.

 Payroll Processing: Automating salary calculation and distribution.

 Customer Service: Handling routine inquiries, processing simple orders, or updating customer
information.

About Image and Text Automation

To enable image and text-based process automation, Studio features activities that
simulate keyboard and mouse input, such as clicking, hovering or typing, text
recognition and OCR activities that use screen scraping to identify UI elements,
and image recognition activities that work directly with images to identify UI elements.
Specialized recording wizards for Screen Scraping and Citrix recording can also
automatically generate the activities required for each process. For more information,
refer to About recording.

Image and Text automation is useful in situations when UI automation does not work,
such as in virtual machine environments, where selectors cannot be found by using
normal methods.

Text and image automation in RPA uses technologies like OCR (Optical Character Recognition)
and image recognition to "see" and "read" digital content, enabling bots to process unstructured
data from screenshots, documents, or virtual environments (like Citrix) where traditional selectors
fail, allowing for data extraction, clicks on visual elements, and data entry for complex, end-to-end
process automation, bridging gaps left by pure UI automation.
Key Technologies & How They Work
 Optical Character Recognition (OCR): Converts images of text (typed, handwritten) into
machine-readable data.

o Use: Extracts data from invoices, scanned forms, or virtual desktops where text isn't directly
selectable.

 Image Recognition: Identifies and interacts with specific images or visual elements on screen,
regardless of underlying code.

o Use: Clicks buttons, icons, or areas on virtual machines (Citrix) or applications with unstable UIs.

 Natural Language Processing (NLP): Understands and processes human language, enabling
bots to interpret text for context, sentiment, and entity extraction (names, addresses).

o Use: Automating customer service, transcribing calls, or generating reports from extracted data.

Common Applications & Use Cases

 Virtual Environments: Automating tasks in Citrix, virtual desktops, or legacy systems where
traditional element selectors (like IDs) don't work, using image/text clicks instead.

 Document Processing: Extracting invoice details, claim information, or patient records from
scanned documents using OCR and AI.

 Data Entry: Reading data from images (like checks) and entering it into systems.
 Customer Support: Using NLP to understand emails/chats and RPA to take action, or
transcribing voice calls for processing.

How RPA Platforms Handle It

 Activities/Commands: Platforms like UiPath offer specific activities like "Click Image," "Click
Text," "Scrape Relative," and "OCR Text".

 AI Integration: Modern RPA tools use AI/ML to enhance OCR accuracy for handwritten text and
understand image context, moving towards true intelligent automation.

Benefits
 Automates complex, unstructured data processes.

 Works in difficult environments (virtual, legacy).

 Relieves humans from tedious data extraction.

 Increases efficiency, accuracy, and provides audit trails.

Keyboard Shortcuts
The complete list of keyboard shortcuts for UiPath Studio:

File Management
Ctrl + Shift + N - Creates a new Blank Process.

Ctrl + C - Copies a file from the Project panel into clipboard. Use Ctrl + V to paste it
anywhere in the tree.

Ctrl + O - Enables you to open a previously created workflow, either

the .xaml or [Link] file.
Ctrl + L - Opens the folder where the Log files are stored.

Ctrl + S - Saves the currently opened workflow.

Ctrl + Shift + S - Saves all the workflows that are currently open.

Ctrl + V - Pastes a file from clipboard into the Project panel.

Ctrl + Tab - Moves focus between workflows opened in the Designer panel.

Ctrl + W - Closes the workflow file that is in focus in the Designer panel.

Alt + F7 - Moves focus between Studio panels. When you use Ctrl + Tab or Alt + F7 and
hold the modifier key (Ctrl or Alt respectively), the following window appears, allowing
you to switch between active files and panels in Studio.
Search
F3 or Ctrl + Shift + P - Opens the Command Palette.

Ctrl + Shift + T - Opens the Add an Activity search bar.

Ctrl + Shift + F - Opens the Go to file search bar.

Ctrl + F - Opens the Universal Search bar.

Ctrl + J - Opens the Jump to activity search bar.

Ctrl + 1 - Switches to the Current File tab in the Universal Search bar.

Ctrl + 2 - Switches to the All Files tab in the Universal Search bar.

Ctrl + 3 - Switches to the Activities tab in the Universal Search bar.

Ctrl + 4 - Switches to the Variables tab in the Universal Search bar.

Ctrl + 5 - Switches to the Arguments tab in the Universal Search bar.

Ctrl + 6 - Switches to the Imports tab in the Universal Search bar.

Ctrl + 7 - Switches to the Project Files tab in the Universal Search bar.

Ctrl + 8 - Switches to the Dependencies tab in the Universal Search bar.

Ctrl + 9 - Switches to the Snippets tab in the Universal Search bar.

Ctrl + Alt + A - Opens and focuses the Properties panel.

Ctrl + Alt + F - Sets the focus to the search box in the Activities panel.

Ctrl + Alt + O - Sets the focus to the search box in the UI Objects Browser panel.
Ctrl + Alt + P - Opens and focuses the search bar in the Project panel.

Ctrl + Alt + S - Opens and focuses the search bar in Snippets panel.

Tab - Navigates to the next item in the panel or the next element in the activity.

A list of useful keyboard shortcuts is displayed in the Designer panel, when all project
files are closed, as illustrated in the image below:

Comment
Ctrl + D - Ignores the activity that is currently selected by placing it into a Comment
Out container.

Ctrl + E - Removes the activity from the Comment Out container it was placed in.

Debugging
F9 - Marks the selected activity with a breakpoint.

Ctrl + Shift + B - Opens the Breakpoints panel.

Ctrl + Alt + E - Opens the Error List panel.

F10 - When debugging, steps over the execution of a block of activities in the currently
selected workflow.

F11 - When debugging, enables you to step into a block of activities and executes the
first one.
Shift + F11 - When debugging, steps out of the current container after its last activity is
executed.

Recording
Ctrl + Alt + B - Opens the Basic Recording toolbar.

Ctrl + Alt + C - Opens the Citrix Recording toolbar.

Ctrl + Alt + D - Opens the Desktop Recording toolbar.

Ctrl + Alt + W - Opens the Web Recording toolbar.

F2 - Adds delay during a recording activity.

F3 - Lets you specify a custom recording region.

F4 - Lets you choose the UI Framework to record, which can be Default, AA, and UIA.

Workflow Analysis and Execution

F5 - Runs the current project in debugging mode, starting with the .xaml file set as Main.
Ctrl + F5 - Runs the current project.

F6 - Runs the currently opened .xaml file in debugging mode.

Ctrl + F6 - Runs the currently opened .xaml file.
F7 - Checks the file for validation errors and Workflow Analyzer violations.

Shift + F7 - Checks the whole project for validation errors and Workflow
Analyzer violations.

F8 - Checks the currently opened workflow for validation errors.

Shift + F8 - Checks all project files for validation errors.

Pause - Pauses the execution of the current workflow, in both normal and debug mode.

F12 - Stops the execution of the current workflow, in both normal and debug mode.

Selected Activity
Ctrl + T - Places the activity inside the Try section of a Try Catch activity.

Ctrl + N - Creates a new Sequence Diagram in the current project.

Ctrl + C - Copies the selected activity or activities to the clipboard.

Ctrl + V - Pastes the copied activity or activities inside the selected item.

Ctrl + K - Creates a variable of the same type as the required type of the activity when
used in an input field or the Expression Editor. If an expression already exists in the
field, before pressing CTRL + K, you can select that expression or a part of it to use the
selected text as the name of the new variable.
Ctrl + M - Creates an In argument of the same type as the required type of the activity
when used in an input field or the Expression Editor. If an expression already exists in
the field, before pressing CTRL + M, you can select that expression or a part of it to use
the selected text as the name of the new argument.

Ctrl + Shift + M - Creates an Out argument of the same type as the required type of
the activity when used in an input field or the Expression Editor. If an expression
already exists in the field, before pressing CTRL + Shift + M, you can select that
expression or a part of it to use the selected text as the name of the new argument.

Ctrl + Shift + E - Opens the Expression Editor when used inside activity input fields.

Ctrl + Space - Opens the IntelliPrompt window.

F2 - Allows for renaming the selected activity.

Shift + F2 - Adds an annotation to a selected activity.

Enter - Saves the data added in the activity input field.

Shift + Enter - Adds a new line in the activity input field.

Tab - Moves through the fields and buttons in the activity, including the menu
displayed when you hover the mouse over an input field.

Test Automation
Ctrl + Alt + T - Open Test Explorer panel. You can use this anywhere within
the Designer panel.

Alt + Down Arrow - Open the Run All in View menu from the Test Explorer.

Alt + T - Open Test Results sub-panel in Test Explorer. You can use this only in
the Test Explorer panel.

Alt + A - Open Activity sub-panel in Test Explorer. You can use this only in the Test
Explorer panel.

Arguments Dialogs
The following keyboard shortcuts are available in Arguments dialog boxes available in
activities such as Invoke Workflow File and Inject .NET Code:

Tab - Moves through the items in the grid.

Delete - Deletes the item selected in the grid.

F2 - Highlights the current cell for editing, positioning the cursor at the end of the line.

Ctrl + Tab - Moves through the options available in the window for the selected item in
the grid (Delete, Move up, Move Down).
Status Bar
Alt + D - Access the Source Control, Orchestrator folders, and Orchestrator/Cloud
Connection menus in the status bar, and then use Shift + Tab to cycle through the
menus. Once a menu is selected, press Enter to open it.

Backstage View
CTRL + Tab - Moves focus between tabs. This also applies to the sub-tabs inside
the Tools and Settings tabs.

Tab - Moves focus between the content inside tabs.

Miscellaneous
F1 - Enables you to access a help topic associated with the currently selected element.

Alt + F4 - Closes the current window.

Alt + - - Opens the Options context menu in the title bar of the currently selected panel.
Please note that this works with the hyphen key above the character keys, not with the
minus key in the numpad.

Windows key + Up Arrow - Maximizes the current window.

Windows key + Down Arrow - Restores down the current window.

Ctrl + P - Opens the Manage Packages window.

Esc - Closes the Publish, Manage Packages, File Diff windows.

Ctrl + F1 - Minimizes or expands the ribbon.

Ctrl + Shift + R - Removes all unused project dependencies.

Shift + Tab - Navigates to the previous activity or node in the Activities panel.

Ctrl + Z - Undo the last action.

Ctrl + Y - Redo the last action you've undone.

Shift + F10 - Open the context menu for the selected item (right-click).

Ctrl + Tab - Moves the focus out of multiline text boxes where pressing the Tab key
inserts a tab.

Ctrl + Shift + F10 - Dismisses the tooltip content for the selected item.

Ribbon and Home Tab Shortcut Keys

You can quickly get to most of the options in the Home tab (Studio Backstage View) and
the ribbons in the Design and Debug tabs by pressing and releasing the Alt key, and
then pressing one or more keys.
When you press and release the Alt key, one or more letters or digits appear over the
options in the current view. To use an option, press the corresponding key or keys. For
some options, additional keys are available after you press the initial key combination.

For a list of shortcuts, see the following sections.

Design Tab Ribbon Keys

If you are in the Design tab or Debug tab, press Alt+D to access the shortcut keys for the
Design tab ribbon.

Key(s) Action Performed Additional Keys and Actions

N Open the New drop-down –

S Open the Save drop-down S - Save as

L - Save all

ET Open the Export as Template window –

R Open the Debug File drop-down C - Run file

B - Debug project
D - Run project

X Cut the selected activities –

C Copy the selected activities –

V Paste the copied activities –

MP Open the Manage Packages window –

ME Open the Manage Entities window –

EW Open the Service Editor window –

U Open the UI Explorer window –

 Key(s) Action Performed Additional Keys and Actions

IU Open the Remove Unused drop-down F - Remove Unused Workflows

A - Remove Unused Variables
B - Remove Unused Arguments
C - Remove Unused Dependencies
D - Remove Unused Imports
E - Remove Unused Screenshots

A Open the Analyze File drop-down B - Analyze Project

C - Validate File
D - Validate Project
S - Workflow Analyzer Settings

EX Open the Export to Excel window –

P Open the Publish window –

Debug Tab Ribbon Keys

If you are in the Design tab or Debug tab, press Alt+E to access the shortcut keys for the
Debug tab ribbon.

Key(s) Action Performed Additional Keys and Actions

R Open the Debug File drop-down C - Run file

B - Debug project
D - Run project

B Break execution –

T Stop execution –

S Step Into –

V Step Over –

O Step Out –

ER Retry –

EI Ignore –

ES Restart –

F Focus –
 Key(s) Action Performed Additional Keys and Actions

P Open the Breakpoints drop-down T - Toggle Breakpoints

P - Show Breakpoints Panel

LS Set Slow Step speed –

LE Enable / disable Execution trail –

LH Enable / disable Highlight Elements –

LA Enable / disable Log Activities –

LC Enable / disable Continue on Exception –

LP Enable / disable Picture in Picture –

LR Open the Remote Debugging drop-down C - Configure Remote Debugging

LO Open the Logs folder –

Title Bar Keys

To access keys for the buttons in the Studio title bar (top-right side of the window), press
the Alt key.

Key(s) Action Performed Additional Keys and Actions

F Open the Send feedback window,

L Open the Help drop-down.

I Open the Sign in / Sign out menu

Home Tab Keys

If you are in the Design tab or Debug tab, press Alt+H to open the Home tab (Studio
Backstage View) and access the shortcut keys for the Home tab. If you are already in the
Home tab, all you need to do is press the Alt key.

Key(s) Action Performed Additional Keys and Actions

Z Go back to the previous tab, if a project –

is open

O Open a project –

C Close the currently open project –

Key(s) Action Performed Additional Keys and Actions

S Open the Start tab O - Open a Local Project

C - Clone or Check Out a Project
P - Create a Process
L - Create a Library
A - Create a Test Automation
T - Create a Template
1...9 - Open one of the nine most recent projects

T Open the Templates tab –

M Open the Team tab –

L Open the Tools tab U - Open the UI Explorer

M - Open the Project Dependencies Mass
Update Tool
R - Open the Repair Tool for Microsoft Office
C - Install the Chrome extension
F - Install the Firefox extension
E - Install the Edge extension
J - Install the Java extension
S - Install the Silverlight extension
T - Install the Citrix extension
W - Install the Windows Remote Desktop
extension
V - Install the VMware Horizon extension

E Open the Settings tab G - Open the General tab

D - Open the Design tab
L - Open the Locations tab
M - Open the Manage Sources tab
P - Open the License and Profile tab
T - Open the Team tab
B - Open the Labs tab

H Open the Help tab D - Open the Product Documentation link

F - Open the Community Forum link
M - Open the Help Center link
A - Open the Academy link
R - Open the Release Notes link
S - Open the Take a short survey link
 Key(s) Action Performed Additional Keys and Actions

T - Open the Quick Tutorial link

C - Copy the license information

Text and image automation

Text and image automation encompasses two primary areas: using automation to extract or
interact with existing text and images within applications, and using automation and AI to
generate new images and text from data or prompts.

About Image and Text Automation

To enable image and text-based process automation, Studio features activities that
simulate keyboard and mouse input, such as clicking, hovering or typing, text
recognition and OCR activities that use screen scraping to identify UI elements,
and image recognition activities that work directly with images to identify UI elements.
Specialized recording wizards for Screen Scraping and Citrix recording can also
automatically generate the activities required for each process. For more information,
refer to About recording.

Image and Text automation is useful in situations when UI automation does not work,
such as in virtual machine environments, where selectors cannot be found by using
normal methods.

Automation for Interaction and Data Extraction

This form of automation is often part of Robotic Process Automation (RPA) and is particularly
useful in environments where standard UI automation is difficult, such as in virtual machines or
legacy systems.
Key techniques include:
 Optical Character Recognition (OCR): OCR technology is used to "read" and extract printed or
handwritten text from images, scanned documents, and PDFs, converting them into machine-
encoded, editable text. This extracted text can then be used in other applications or stored in
databases.
 Image Recognition: This involves software identifying specific visual elements, patterns, or
icons on a screen. Automation tools can then simulate user actions like mouse clicks or keyboard
inputs relative to these identified images to navigate applications and perform tasks.

 Screen Scraping: This technique is a form of output automation that captures and extracts data
from an application's display, which can include both text and image data, for use elsewhere in a
workflow.

Common tools for this type of automation include UiPath, Power Automate, and Automation
Anywhere.
Automation for Content Generation
This involves automatically creating new visual and textual content, which is widely used in
marketing, social media, and design.
Key applications include:
 Image Generation from Data/Templates: Marketers can automatically generate thousands of
personalized images (e.g., ad banners, social media posts, personalized email graphics) by
pulling data like names, product images, and prices from spreadsheets or databases and
inserting them into pre-designed templates.

 AI Text-to-Image: Using AI models (like those from Canva or Runway), users can input text
descriptions (prompts) to generate unique, original images or artwork.

 Automated Social Media Content: Workflows can be set up using integration platforms
like Zapier or [Link] to automatically create text, images, and videos from source content
(like a voice note) and publish them across various social media platforms.

 Image Annotation and Captioning: AI can automatically analyze image content and generate
descriptive text (alt text) or full captions, which aids in accessibility and image search
optimization.

 This process uses AI models to create new text and images from a given input,
often a simple text
prompt.

Flowchart for the proposed text recognition system

 The general workflow involves:
1. Text Analysis: The AI uses Natural Language Processing (NLP) to understand the input
prompt, identifying key elements, context, and descriptive words.

2. Feature Mapping: The system maps the textual elements to specific visual or stylistic
features (colors, shapes, objects, writing style).

3. Generation: Using models like Generative Adversarial Networks (GANs) or diffusion

models, the AI generates content that aligns with the mapped features.

4. Refinement & Output: The content is refined to ensure quality and coherence before
being output as a new image, article, or social media post

Setting UI path Environment

Set Environment Variable

[Link]

Use this activity to set an environment variable, providing the name and the value for it.
If the variable does not already exist, it will be created automatically.

NOTE: You can only set a User Environment Variables using this activity.

Properties
Common
 DisplayName - The display name of the activity. This field supports
only Strings or String variables.
Input
 Name - The name of the new environment variable. This field supports
only Strings or String variables.
  Value - The value of the new environment variable. This field supports
only Strings or String variables.
Misc
 Private - If selected, the values of variables and arguments are no longer logged
at Verbose level.

Setting up the UiPath environment involves signing up for an Automation Cloud account,
installing UiPath Studio (often via the cloud portal), and then configuring it to connect to your
cloud Orchestrator, which includes setting up Folders, Robots, and assigning users with roles for
managing automations in a structured way (like for attended or unattended processes). You'll use
the cloud portal to get credentials and manage resources, while the local installation handles
development and execution, connecting to the cloud for deployment and monitoring.
1. Cloud Account & Orchestrator Setup (Automation Cloud)
 Sign Up: Go to [Link] and click "Try UiPath Free" to create an account and organization.

 Access Orchestrator: Log in to the Automation Cloud ([Link]) and select your tenant.

 Create Folders: Create specific folders (e.g., Unattended ) for organizing your automations and
robots.

 Manage Users & Roles: Add users and assign them roles (like Administrator, Developer, or
Robot role) to control access and permissions.

2. Install UiPath Studio & Robot

 Download: In Automation Cloud, navigate to Home and find the download link for UiPath
Studio (usually an MSI file).

 Install: Run the installer, choosing "Custom" for advanced options if needed, and select
the appropriate installation type (User Mode for attended, Service Mode for unattended).

 Connect: During setup or in Studio/Assistant settings, connect to your Orchestrator

instance using the URL and machine key or Client ID/Secret for authentication.

3. Configure Robots & Environments (Orchestrator)

 Add Machines: In Orchestrator, add the machines where your robots will run (often done
automatically).

 Create Environments (Optional but Recommended): Create logical groups

(Environments) for related robots (e.g., "Production Robots") and assign them for easier
management.
 Create Robot Accounts: In Orchestrator, create Robot accounts (e.g., Rakesh-Robot )
and link them to your machines and users, assigning them to specific folders.

Key Components
 Automation Cloud: The central web platform for managing licenses, Orchestrator, and users.
 Orchestrator: Manages and deploys automations, queues, and robot fleets.

 Studio: The development environment for building automations.

 Robot (Assistant/Service): Executes the automations on local machines, connecting back to

Orchestrator.

Setting up the UiPath environment typically involves three main levels of

configuration: installing the local design tool (UiPath Studio), connecting it to a
management platform (UiPath Orchestrator), and configuring local system
variables for advanced use cases.
1. Local Installation (UiPath Studio)
The foundation of your environment is UiPath Studio, where you build automations.
 Download: Create an account on the UiPath Automation Cloud to download the installer
from the Resource Center.

 Installation Modes:
o User Mode (Recommended for Developers): Installs per user in %localappdata%\
Programs\UiPath and does not require administrator privileges.

o Service Mode (Recommended for Unattended Robots): Installs globally in C:\

Program Files\UiPath\Studio and runs as a Windows service.

 Extensions: During setup, ensure you install necessary extensions for the applications
you plan to automate (e.g., Chrome/Edge, Excel Add-in, or Java).

2. Orchestrator Configuration
Orchestrator acts as the "brain," managing your robots and processes.
 Folders & Environments: In modern Orchestrator setups, you create folders to
organize robots and users. In classic setups, you group Robots into Environments to
deploy specific processes to them.

 Connection: Connect your local UiPath Assistant to the cloud by signing in with your
UiPath account or using a Machine Key.

 Robot Setup: Assign your robot to a folder or environment so it can receive and execute
tasks published from Studio.

3. Configuring System & Environment Variables

For advanced automation (like using WebDrivers or custom scripts), you may need to
adjust Windows environment variables.
 System Path Variable: If you are using a standalone WebDriver for browser automation,
you must add the folder containing the [Link] (or similar) to your
Windows Path environment variable.
 UiPath Specific Variables:
o UIPATH_ROBOTJS_ALLOWLIST : Used to allow specific URLs to connect to the Robot

JavaScript SDK.
o PACKAGES_FOLDER : Can be set as an environment variable to change where the Robot
downloads automation packages (default is %userprofile%\.nuget\packages ).

 Accessing Variables in Workflows: Within UiPath Studio, you can access environment
data (like [Link] or [Link] ) directly in your code
to make automations dynamic across different machines.

4. Important Configuration Files

If you need to change core behaviors (like proxy settings or default paths):
 [Link]: Located in the installation folder (e.g., C:\Program Files\UiPath\
Studio\[Link] ), this file controls low-level robot and studio behaviors.

 User Settings: Personal Studio settings are stored in %AppData%\Roaming\UiPath .

Introduction to UiPath
UiPath is a robotic process automation tool for large-scale end-to-end automation. For an
accelerated business change, it provides solutions for businesses to automate routine office
activities. It uses a variety of methods to transform tedious tasks into automated processes.

Robotic process automation (RPA) has significantly benefitted the companies trying to
ride the wave of artificial intelligence (AI) powered applications. UiPath is one of the
widely used RPA tools. UiPath allows IT departments to set up software robots that
collect and interpret data in various applications to automate routine tasks. If you’re
wondering what UiPath is, then you’re in the right place.

What Is UiPath?

UiPath is a robotic process automation tool for large-scale end-to-end automation. For an
accelerated business change, it provides solutions for businesses to automate routine
office activities. It uses a variety of methods to transform tedious tasks into automated
processes.

Features of UiPath

Now that you have understood what UiPath is, this tutorial will now look at the key
features of UiPath.

Drag and Drop Workflow

The UiPath user will develop visual process steps by dragging and dropping related tasks
onto the graphical workspace. Then, with user interface properties, they can transform
those process steps into a visual workflow. Users may also use the recorder wizard in the
UiPath tool to build web-based or application workflows.

Record and Playback

The user can use this function to record actions and transform them into an automated
process series. UiPath has the following types of recording options:

 Basic recording- It focuses on automating single tasks and is commonly used to develop each
activity's complete selector.

 Desktop recording- It can be used for a variety of actions as well as application development.

 Web recording- Web recording is a common tool for viewing and recording web page
activities.

 Citrix recording- It is very widely used for recording stuff like pictures and virtualized
environment automation.

Inbuilt activities in UiPath

UiPath comes with over 300 built-in activities covering a wide range of process
automation and application integration design tasks. You can find these activities in the
Activities pane, which covers most design tasks such as data extraction, data entry, and
automation.

Advanced Scraping Options

Scraping data from web pages and applications is easier with UiPath Screen Scraping.
Furthermore, the data scraping wizard helps in the scraping of data with a repetitive
structure. Scraping solution works flawlessly with any program, including .Net, Java,
Flash, PDF, Legacy, and SAP.
High Security and Robustness

You can create super-smart, durable robots with UiPath. With a simple visual canvas,
everyone in the company can use these bots. UiPath offers high-security auto-login
functionality to run the bots and operates with a locked screen, allowing automated
processes to run in complete privacy.

UiPath Architecture

Now that you have understood what UiPath is, and what its components are, it’s time to
understand the UiPath architecture.

It consists of 2 sections.

 The Client and Server Side

 The three layers

The Client and Server Side

 Client-side UiPath components are those that the user or developer can communicate with
directly. UiPath Studio, Robot, Browser, and UiPath Agent are usually included.
 UiPath's backend operations are considered server-side. It saves the tasks and workflows that
a user produces in the databases.

 The UiPath Orchestrator chooses the necessary functions and software robots to carry out the
code's tasks.

 The robots' logs and statistics are stored in the backend. The records are useful for analyzing
robot performance and detecting errors.

 UiPath robot comprises of two elements, namely-

Agent Support for UiPath:

This service in UiPath serves as a mediator between the client-side and the server-side
of UiPath. All of the information and data are conveyed via the handler. It also logs
messages in the Orchestrator before being moved to the SQL server. The service can be
used to search all the currently available tasks in the device tray. It also can change
device settings and start/stop current tasks.

Executor Service for UiPath:

Software robots use this service to carry out the tasks specified in a Windows session.

The Three Layers

1. Presentation Layer

 The UiPath components that are open to users make up the client layer. It includes UiPath
Studio, Robots, Browsers, UiPath Agent, and Executors.

 A user or a developer may use these components to design and create different tasks that can
be automated. Computer robots are commonly used to complete these tasks. The client layer
is another name for this layer.

2. Server Layer

 The server layer is the UiPath architecture's significant sheet. The cloud layer shows all server
information. The Orchestrator is the most crucial part of the server layer. When the robots
perform the tasks, it periodically uploads the entire project to the server.

 The Orchestrator is in charge of the whole band. It keeps track of project development,
schedules software robots for execution, and produces summary reports based on filtered
parameters.

 The server layer helps synchronize software and software robots so that they can continue to
perform routine tasks. It helps the project meet its project requirements, service levels, and
deadlines, thanks to its web-based management system.

3. Persistence layer

 Database servers make up the bulk of this sheet. In this layer, all the robots' configuration
information is saved. Users insert data, robots, assigned tasks, logging info, and asset details,
among other items, into the Orchestrator's configuration details.
 Furthermore, the persistence layer is in charge of keeping the log information updated by the
UiPath agent services. Elastic search is used to store these logs. The logs are primarily useful
for locating and correcting errors.

 Process-level data is usually saved in relational database management systems such as SQL
Server. This makes processing logs from the vast volume of data a lot simpler. Hence, the
queues’ tasks are often taken care of by the persistence layer.

Benefits of UiPath

Increased Productivity

UiPath automates with quick speed and accessibility. Consider an RPA bot that allows a
worker to produce a monthly report in 20 minutes. When done manually, it would take
four hours. The company's productivity would increase as a result of process automation.

High Efficiency

RPA software does not need a break; it can operate 24 hours a day, seven days a week,
365 days a year. It also does not take a break or become ill. In most cases, a single RPA
robot may replace two to five full-time workers, if not more. Robots can do the same
amount of work in less time, or more work than humans at the same time.

Customer Experience
In an RPA-adopted business, routine, repetitive, and boring tasks are assigned to robots,
allowing employees to focus more on customer service. Companies may meet consumer
needs with the help of professional and knowledgeable employees.

Highly Secure

There is no risk of information leakage from one component to another because it only
performs single tasks. As a result, data access is strictly monitored and reported.

Cost-Effective

UiPath has minimal operating costs and more efficient use of IT resources.

UiPath Components

1. UiPath studio- UiPath studio is a user-friendly interface that allows users to visually plan and
design various automation processes through diagrams, using the drag-and-drop functionality.
These diagrams are merely a structural reflection of specific tasks that must be completed.

2. UiPath robot- After you've built your process, the next move is to put it into action in the UiPath
studio. UiPath Robots are used to translate the strategies into tasks, which are then executed.
These robots are used to assign various tasks and carry them out in the same manner as
humans but without human interference. When a given operation occurs on the computer,
they program UiPath robots to begin executing tasks automatically.
 3. UiPath Orchestrator-The Orchestrator is a web-based application in UiPath. It has features for
deploying, monitoring, scheduling, and controlling automated bots and processes. It's a
centralized forum for managing and maintaining all software bots.

User Interface:

The user interface (UI) in Robotic Process Automation (RPA) is crucial, allowing software bots to
mimic human actions like clicks and key presses on applications' graphical user interfaces (GUIs)
to automate tasks, learn processes through recording, and extract data, essentially acting as a
"digital worker" interacting directly with screens and systems without needing APIs, making
automation accessible for many repetitive jobs. Key UI aspects include mouse/keyboard
emulation, screen scraping (reading screen data), and tools like the UiPath Assistant,
enabling attended (human-assisted) or unattended (fully automatic) operations across desktop
and web apps.
Key UI Interaction Methods
 Mouse & Keyboard Emulation: Bots simulate human input, moving cursors, clicking buttons,
and typing data into fields just like a person.

 Screen Scraping: Robots read and extract information directly from what's displayed on the
screen, even from legacy systems without APIs.

 Recording/Mimicry: Users perform a task once, and the RPA tool records these steps, allowing
the bot to replay the exact sequence.

How It Works
 Learning from Humans: RPA learns by watching users navigate applications, building a list of
actions to automate.

 Direct GUI Interaction: Bots interact with applications at the visual level, understanding
elements on the screen (like buttons or text fields) to perform tasks.

 Types of Automation:

o Attended: Bots work alongside humans on desktops (e.g., Robotic Desktop Automation).

o Unattended: Bots run independently on servers for background processes.

User-Facing Tools & Experience

 Desktop Assistants: Tools like the UiPath Assistant run on user desktops, offering a simple
interface to launch automations and review results.

 Focus on Usability: Effective RPA design ensures that the process owner's knowledge is easily
translated into automation, making the tool intuitive and engaging for both builders and end-
users.

Future Trends
 While UI automation is powerful, advancements in AI (like NLP) and increased availability of APIs
are shifting some automation towards more intelligent, API-driven, or conversational interfaces,
reducing reliance on purely visual UI interaction over time.

User Interface Components

o. Name Description

1 Ribbon Tabs Access the three main areas of Studio:

Home - Go to the Studio Backstage View where you can
open and create projects, configure Studio, and more.
Design - Build automations using the tools available in
the Command Palette, and Studio panels.
Debug - Use a comprehensive set of tools to debug your
workflows. For more information, see About Debugging.

2 Title Bar Open the Command Palette.

Send Feedback.
Access Help resources.
Sign in to your account.

3 Designer Build your automation by managing the activities added to

Panel the current workflow file.

4 Command Search within your project using the available search bars:
Palette Add activity
Universal search
Go to File
Jump to activity

5 Variables Manage variables.

Panel

6 Arguments Manage arguments.

Panel

7 Imports Panel Manage imported namespaces.

8 Project Panel View the contents of your current project, manage files,
folders, and dependencies, and adjust project settings.

9 Activities View all available activities and add activities to your

Panel automation.

1 Snippets Use pre-built workflows and add your own reusable

0 Panel automations.

1 Properties View and configure the properties of a selected activity.

1 Panel

1 Data Manage the data in your project.

2 Manager
Panel

1 Outline Panel View the hierarchy of the current workflow and all available
3 nodes.

1 Object Create and reuse UI taxonomies inside and across projects.

o. Name Description

4 Repository
Panel

1 Test Explorer View information related to test automation.

5

1 Output Panel View the output of the Log message and Write
6 Line activities, status information regarding the execution
of your project, errors generated by activities packages,
and more.

1 Find View all the places where an element is referenced in your

7 References project.
Panel

1 Error List View all the errors generated when running the Workflow
8 Panel Analyzer.

1 Breakpoints Manage breakpoints added to the project.

9 Panel

2 Status Bar View status information and manage the Orchestrator

0 connection and source control integration.
Unit V:
Tables in RPA
Introduction

Tables is a library for manipulating tabular data inside Robot Framework.

It can import data from various sources and apply different operations to it.
Common use-cases are reading and writing CSV files, inspecting files in
directories, or running tasks using existing Excel data.

Import types

The data a table can be created from can be of two main types:

1. An iterable of individual rows, like a list of lists, or list of dictionaries

2. A dictionary of columns, where each dictionary value is a list of values

For instance, these two input values:

data1 = [
{"name": "Mark", "age": 58},
{"name": "John", "age": 22},
{"name": "Adam", "age": 67},
]
[Link]

Tables is a library for manipulating tabular data inside Robot Framework.

It can import data from various sources and apply different operations to it.
Common use-cases are reading and writing CSV files, inspecting files in
directories, or running tasks using existing Excel data.

Import types

The data a table can be created from can be of two main types:

1. An iterable of individual rows, like a list of lists, or list of dictionaries

2. A dictionary of columns, where each dictionary value is a list of values
For instance, these two input values:
data1 = [
{"name": "Mark", "age": 58},
{"name": "John", "age": 22},
{"name": "Adam", "age": 67},
]

data2 = {
"name": ["Mark", "John", "Adam"],
"age": [ 58, 22, 67],
}
Would both result in the following table:

Inde
Name Age
x

0 Mark 58

1 John 22

2 Adam 67

Indexing columns and rows

Columns can be referred to in two ways: either with a unique string name or their
position as an integer. Columns can be named either when the table is created, or
they can be (re)named dynamically with keywords. The integer position can
always be used, and it starts from zero.

For instance, a table with columns “Name”, “Age”, and “Address” would allow
referring to the “Age” column with either the name “Age” or the number 1.

Rows do not have a name, but instead only have an integer index. This index also
starts from zero. Keywords where rows are indexed also support negative values,
which start counting backwards from the end.

For instance, in a table with five rows, the first row could be referred to with the
number 0. The last row could be accessed with either 4 or -1.

Examples

Robot Framework

The Tables library can load tabular data from various other libraries and
manipulate it inside Robot Framework.
*** Settings ***
Library [Link]

*** Keywords ***

Files to Table
${files}= List files in directory ${CURDIR}
${files}= Create table ${files}
Filter table by column ${files} size >= ${1024}
FOR ${file} IN @{files}
Log ${file}[name]
 END
Write table to CSV ${files} ${OUTPUT_DIR}${/}[Link]
Python

The library is also available directly through Python, where it is easier to handle
multiple different tables or do more bespoke manipulation operations.
from [Link] import Tables

library = Tables()
orders = library.read_table_from_csv(
"[Link]", columns=["name", "mail", "product"]
)

customers = library.group_table_by_column(rows, "mail")

for customer in customers:
for order in customer:
add_cart(order)
make_order()
Excel and CSV-like packages deal with data, lots of rows and columns. The way
RPA products solve this is with a Data Table object that comes from the
underlying language they use. So the data table concept comes from the
language that the RPA tool is built on and the language provides the tools to
interact with the object like adding, and removing rows and columns.

Robomotion takes a simpler approach. The data table is just a simple JSON
object.

Columns and Rows

Robomotion uses a simple JSON object instead of a heavy Data Table object
managed by the robot.

Here is how this JSON object looks like;

[Link] = {
"columns": ["name", "age", "location"],
"rows": [
{"name":"John", "age":54, "location": "Boston"},
{"name":"Jane", "age":47, "location": "London"}
]
}

columns is a Javascript array of strings, rows is an array of objects. Every row

object holds a key-value pair for every column's value.

Headers and Jsonify

When you use an Excel Get Range node and read an Excel file, the node will
output this type of structure.
The column names come from the first line of an Excel file and it is optional.

If you do not select Headers the columns will be named like below;

[Link] = {
"columns": ["A", "B", "C"],
"rows": [
{"A":"John", "B":54, "C": "Boston"},
{"A":"Jane", "B":47, "C": "London"},
]
}

If you select Headers and not Jsonify the column names will be the same as the
Excel file. So if it has spaces and uppercase characters, these will not change. But
if you select the Jsonify option then the column name first will be converted to
lowercase and the space between the words will be replaced with an underscore.

Price Range -> price_range

Adding a New Row

Because it is a JSON object, the only way to manage this data is with a Function
node and Javascript.

So if you have a table like the above and you need to add a new row, you first
need to create a row object as below.

var my_row = {"name":"Tom", "age":28, "location":"Chicago"}

Now you need to add this row to the table's row array as below;

[Link](my_row)

The result JSON object should look like below;

{
"columns": ["name", "age", "location"],
 "rows": [
{"name":"John", "age":54, "location": "Boston"},
{"name":"Jane", "age":47, "location": "London"},
{"name":"Tom", "age":28, "location":"Chicago"}
]
}

Data manipulation in excell

Excel is a versatile tool for data analysis, offering a wide range of features and
functions that allow users to manipulate, analyse, and visualise data effectively. It
provides a user-friendly interface and a wide range of built-in tools that make it suitable
for performing basic to advanced data manipulation tasks. With its wide range of
features and functions, users can manipulate, analyse, and visualise data effectively to
gain insights and make informed decisions.

Learn about the uses and applications of Excel in different fields with the IIT Mandi
Certificate Programme in Applied Artificial Intelligence and Machine Learning .

What is Data Manipulation in Excel?

Data manipulation refers to altering or transforming data to make it more useful for
analysis, presentation, or storage. It is a fundamental aspect of data analysis and is
crucial in preparing data for use in various applications such as business intelligence,
scientific research, machine learning, etc. It offers several advantages. It facilitates
data preparation by cleaning, filtering, and transforming raw data into an analysable
format, ensuring accuracy and relevance.

Advantages of Data Manipulation (Analysis)

Data Analysis enhances data quality by identifying and rectifying errors,

inconsistencies, and missing values, leading to more reliable analysis outcomes.
Moreover, data manipulation enables analysts to perform various operations such as
aggregation, sorting, and calculation, thus empowering them to extract valuable
insights and discern patterns within the data.

Furthermore, it supports data integration by harmonising disparate sources, providing a

holistic view for comprehensive analysis. Organising data effectively allows decision-
makers to access pertinent information swiftly, fostering efficient decision-making. The
flexibility and scalability of data manipulation techniques allow organisations to handle
large datasets efficiently and adjust analytical approaches as needed. Automation of
data manipulation processes reduces manual effort and ensures reproducibility and
consistency in analysis results.

Techniques for Data Manipulation in Excel

Data Cleaning: Excel offers features like Find and Replace, Text to Columns, and
Remove Duplicates to clean data by removing unwanted characters, correcting errors,
and eliminating duplicate records.
Sorting and Filtering: Excel allows you to sort data alphabetically or numerically and
filter data based on specific criteria, enabling you to focus on relevant information and
organise data effectively.

Formulas and Functions: Excel's vast library of functions, such as SUM, AVERAGE,
VLOOKUP, and IF, enables you to perform calculations, look up values, and apply
conditional logic to manipulate data dynamically.

PivotTables and PivotCharts: PivotTables allow you to summarise and analyse large
datasets by rearranging and summarising data dynamically. PivotCharts provides visual
representations of PivotTable data for easier interpretation and analysis.

Data Validation: Excel's Data Validation feature allows you to define rules and
restrictions for data entry, ensuring data accuracy and consistency.

Conditional Formatting: Conditional formatting in Excel enables you to apply visual

cues to highlight important information, such as data bars, colour scales, and icon sets,
based on specified conditions.

Data Consolidation: Excel's Consolidate feature allows you to combine data from
multiple worksheets or workbooks into a single summary sheet, facilitating analysis and
reporting.

Text Functions: Excel provides various text functions, such as CONCATENATE, LEFT,
RIGHT, and MID, for manipulating text strings, extracting substrings, and combining
text from multiple cells.

Date and Time Functions: Excel's date and time functions, including TODAY, DATE,
TIME, and WEEKDAY, enable you to perform calculations and manipulations on dates
and times, such as calculating differences between dates or extracting components of
date/time values.

Data Analysis Toolpak: Excel's Data Analysis Toolpak add-in offers advanced
statistical and data analysis tools, such as regression analysis, histogram generation,
and descriptive statistics, for complex data manipulation and analysis.

Challenges with Data Manipulation Using Excel

Performance Issues: Excel may become slow or unresponsive when working with large
datasets or performing complex calculations. This can lead to delays in data manipulation
tasks and hinder productivity.

Limited Data Capacity: Excel has size limitations on how much data it can handle, such
as the number of rows (1,048,576 rows in Excel 2016 onwards) and columns (16,384).
Large datasets may exceed these limits, making it difficult to analyse or manipulate all
the data within Excel.

Data Quality Issues: Excel needs built-in data quality features, making it challenging to
identify and correct errors, inconsistencies, and missing values in the data. Users may
need manual inspection or third-party data cleaning and validation tools.
 Complexity of Formulas and Functions: Excel's formulas and functions have the
potential to become intricate and challenging to handle, especially in large worksheets
with multiple calculations. Debugging errors or changing complex formulas can be time-
consuming and prone to mistakes.

Version Compatibility Issues: Excel files created in newer software versions may not
be compatible with older versions, leading to compatibility issues when sharing or
collaborating on files. Users may need to convert files to older formats or use alternative
methods for compatibility.

Extracting Files From PDF

Extracting data from PDFs involves manual copy-paste for simple tasks, using built-in features in
apps like Excel or Adobe to import tables, or employing specialized tools (online converters,
Python scripts, AI parsers like Doc AI, Amazon Textract) for automated, complex, or scanned
documents (using OCR) to get structured data into formats like Excel or CSV. The best method
depends on PDF type (native vs. scanned) and volume.
Methods for Extraction:
1. Manual (Copy & Paste):

 Best for: Simple, few documents, native PDFs (not scans).

 How: Select text/tables and paste into Excel/Word.

2. Using Software/Tools:

 Excel (Data Tab): Import PDF directly, select tables, and bring data into Excel.

 Adobe Acrobat/Online Converters: Upload PDF to convert to Excel/CSV (e.g., Adobe

Acrobat, PDF24, Smallpdf).

 [Link]: Free tool specifically for extracting tables from native PDFs.

3. Automated & Advanced (for Scanned/Complex Docs):

 OCR (Optical Character Recognition): Tools like iLovePDF make scanned PDFs searchable
and extractable.

 AI/ML Parsers: Use services like Google Cloud Document AI or Amazon Textract for structure,
complex tables, and context.

 Programming (Python): Use libraries like tabula-py , PyPDF2 , or Adobe's Extract API for
custom solutions.

General Steps (Using Online Tools):

1. Upload: Go to an online PDF tool (e.g., Adobe, PDF24) and upload your file.

2. Convert: Choose to convert to Excel/CSV or extract text/pages.

3. Download: Save the structured data to your computer.

Anchor-based data extraction using Intelligent Form
Extractor
The example below explains how to extract data from a form that may also include
handwritten text. The following use-case scenario explains how to extract data from a
purchase order.

It presents activities such as Digitize Document, Data Extraction Scope, or Intelligent

Form Extractor. You can find these activities in
the [Link] package.

Creating the workflow

The following packages need to be installed prior to creating the below workflow:

 [Link]
 [Link]
 [Link]
 [Link]
 [Link]

Steps:

1. Open Studio and create a new Process.

2. Add a Sequence container in the Workflow Designer, name it Sequence1, and
create the variables shown in the following table:

Table 1. Variables to be created

Variable Type Default value

N/A
item String

N/A
classificationResult ClassificationResult[]

N/A
outputFileName GenericValue

3. Add another Sequence container in the Workflow Designer, after the first one,
name it Sequence2, and create the variables shown in the following table:

Table 2. Variables to be created

Variable Type Default value

N/A
text String

N/A
taxonomy DocumentTaxonomy

N/A
dom Document

N/A
documentPath String
 Table 2. Variables to be created

Variable Type Default value

N/A
classificationResult2 ClassificationResult[]

N/A
outputFileName2 GenericValue

4. Add a Message Box activity inside the sequence.

 In the Properties panel, select the Ok option from the Buttons dropdown.
Add the following message in the Text field: "Select a PDF file".
5. Select the check box for the TopMost option. This brings the message box to the
foreground.
6. Add a Select File activity after the Message Box activity.
 In the Properties panel, add the following text in the Filter field: Pdf
files (*.pdf)|*.pdf
 Add the documentPath variable in the SelectedFile field.
7. Add an Assign activity after the Select File activity.
 Add the outputFileName2 variable in the To field.
 Add the expression ".temp/" + [Link](documentPath) in
the Value field.
8. Add a Deserialize JSON activity after the Assign activity.
 Add the expression [Link]("DocumentProcessing
[Link]") in the JSON String field.
 In the Properties panel, select
the [Link]
onomy option from the TypeArgument dropdown list.
 Add the taxonomy variable in the JsonObject field.
9. Add a Digitize Document activity after the Deserialize JSON activity.
 In the Properties panel, add the value 1 in
the DegreeOfParallelism field.
 Add the documentPath variable in the DocumentPath field.
 Add the dom variable in the DocumentObjectModel field.
 Add the text variable in the DocumentText field.
 Add the UiPath® Document OCR engine inside the activity.
 Add your API Key inside the ApiKey field.
 Add the "[Link] expression in the Endpoint field.
10. Add a Write Text File activity after the Digitize Document activity.
 Add the [Link](dom) expression in the Text field.
 Add the outputFileName2 + ".[Link]" expression in the FileName field.
11. Add another Write Text File activity after the Write Text File activity.
 Add the text variable in the Text field.
 Add the outputFileName2 + ".[Link]" expression in the FileName field.
12. Drag another Sequence container in the Workflow Designer, name
it Sequence3, and create the variables shown in the following table:
 Table 3. Variables to be created

Variable Type Default Value

N/A
extractionResult ExtractionResult

N/A
validatedResults ExtractionResult

N/A
doubleValidatedResults ExtractionResult

N/A
dataset DataSet

N/A
i Int32

13. Add a Data Extraction Scope activity inside the Sequence3.

 In the Properties panel, add the dom variable in
the DocumentObjectModel field.
 Add the documentPath variable in the DocumentPath field.
 Add the text variable in the DocumentText field.
 Add the "[Link]" expression in
the DocumentTypeId field.
 Add the taxonomy variable in the Taxonomy field.
 Add the extractionResult variable in the ExtractionResults field.
14. Add an Intelligent Form Extractor activity inside the Data Extraction
Scope activity.
 Add your API Key in the ApiKey field.
15. Add a Write Text File activity after the Data Extraction Scope activity.
 Add the [Link](extractionResult) expression in
the Text field.
 Add the outputFileName2 + ".[Link]" expression in
the FileName field.
16. Add a Present Validation Station activity after the Write Text File activity.
 Add the extractionResult variable in
the AutomaticExtractionResults field.
 Add the dom variable in the DocumentObjectModel field.
 Add the documentPath variable in the DocumentPath field.
 Add the text variable in the DocumentText field.
 Add the taxonomy variable in the Taxonomy field.
 Add the validatedResults variable in
the ValidatedExtractionResults field.
17. Add a Write Text File activity after the Present Validation Station activity.
 Add the [Link](validatedResults) expression in
the Text field.
 Add the outputFileName2 + ".[Link]" expression in
the FileName field.
18. Add another Write Text File activity after the Write Text File activity.
 Add
the [Link](doubleValidatedResults) expression in
the Text field.
 Add the outputFileName2 + ".[Link]" expression
in the FileName field.
19. Run the process. The automation process should open the Validation Station,
extract the data, validate it, and store it in the Output folder.
Visit the following link to download the example in a ZIP format: Example.

Defining your taxonomy

You have created your workflow, defined all variables, and customized all activities. Now
it's time to define your taxonomy. Visit Load Taxonomy to learn about defining your own
taxonomy.

Create your taxonomy to be able to extract information from an invoice. You should be
focused on creating an Invoice document type, with the fields shown in the following
table:

Table 4. Invoice document type

fields

Field Type

InvoiceNo Text

Subtotal Number

SalesTax Number

Total Number

Figure 1. Overview of the finished taxonomy with the previously mentioned fields
Creating your template
It is now time to create the template for the extraction process. Visit Load Taxonomy to
learn how to create a template.

For this example, configure the template using the following values:
 Document Type: Invoice.
 Template Name: Invoice-example.
 Template Document: Select the target file.
 OCR Engine: Microsoft OCR.
 Languages: en.
 Profile: Scan.
 Scale: 1.

Figure 2. Animated image example showing the configuration of the template

Setting anchors in the template

Anchors are a very special and useful feature to use when you need to extract precise
information from a document. By defining an extraction area with an anchor, you can
expect a high accuracy in data extraction.

Once the taxonomy is defined and the template created, you can start configuring the
template by using anchors, meaning that the extraction area is defined in a box, and
anchors are used for defining the box position.
 Check the following list for some pointers before starting adding anchors to your
template:

 The anchor box should be as big as possible (height, width) to cover any type of
invoice number, long, short, big font, etc.
 One extraction area can have as many anchors as needed, but only one defined as
main (the first one).
 Use anchors formed of multiple side-by-side words.
 The main anchor should be as close as possible to the extraction area.
 The positions of the extraction area and the main anchor are fixed in the template,
even when applied to different documents. The only thing that can vary is the
distance between the main anchor and the secondary ones.

Let's continue configuring the template and see how you can extract data using an
anchor.

1. Set the extraction area:

 In the right area of the Validation Station, select Selection modes.

 Select Anchor.
 Start selecting the desired area.
NOTE:

The main anchor should contain two or three words for high accuracy and
better results in the extraction process.

Select multiple words when tagging an anchor by pressing CTRL and

selecting the desired words.

2. Set the main anchor:

a. While still in the Anchor selection mode, select the desired area as your
main anchor.
b. Select Extract value for the desired field.
3. Set the secondary anchors:
a. Ensure you're still in the Anchor selection mode, and with the main anchor
selections activated.
b. Select the new areas for the secondary anchors.
c. Select Options for the desired field, and then select Change extracted
value.

Repeat the process until you finished defining all extraction areas and adding all your
anchors. Once finished, save the template.

Anchors in PDFs create internal links to specific locations (text or images) for navigation, often
called "Named Destinations," allowing users to jump within a document or to another file using
links like [Link]#nameddest=overview . You create them in PDF editors (like Adobe
Acrobat, Affinity Publisher), defining a location and naming it, then use the link tool to point text or
graphics to that anchor, making long documents navigable via a table of contents or interactive
elements.
How to Use Anchors in PDFs (Adobe Acrobat Example)
1. Create the Destination (Anchor):
 Go to the Destinations panel (sometimes under Tools > Edit PDF > Link > Add or Edit).

 Navigate to the spot you want users to land on.

 Click to create a new destination and give it a unique, space-free name (e.g., "Chapter1Start").

2. Create the Link:

 Highlight the text or select the object you want to act as the clickable link.

 Right-click and choose Create Link.

 In the dialog, select "Go to a page view" or "Open a web page" (if linking externally).

 For internal links, choose the destination you created, or

type #[AnchorName] (e.g., #Chapter1Start ) in the URL field for external linking.

 Set link appearance (invisible, border, etc.) and click OK.

Key Concepts
 Named Destinations: The technical term for anchors in PDF, acting as hidden bookmarks.

 Linking: You link from one element (text/image) to a destination.

 URL Fragments: For external links, you use #AnchorName at the end of the URL.

Common Uses
 Table of Contents (TOC): Link chapter titles to the start of each chapter.

 Navigation Menus: Create buttons to jump to sections.

 Interactive Forms: Link fields to instructions or definitions.

Important Notes
 Browser Support Varies: Some built-in PDF viewers (like those in browsers) may not support all
destination types or link formats.

 Accessibility: Anchors are crucial for creating accessible PDFs, helping screen readers navigate
content.