Bot Creator Introduction

A Bot Creator is a software tool in Automation Anywhere used to create and test
automation bots.
Bots are programs that do tasks automatically without human help.

Main Points to Remember:

1. Purpose – To make bots that can run tasks based on predefined rules.
2. Registration – When you log in for the first time, your computer is linked (registered)
to the Control Room.
3. Parts of Bot Creator:
o Task Editor – Place where you design bots (add commands, set actions, add
variables).
o Event Watcher – Watches for events and runs actions.
o Reports – Shows status of bots and time saved.
o Bot Player – Runs the bots.
4. Background Services:
o Auto-login – Lets bots log in to target machines automatically.
o Control Room Communication – Keeps connection with the Control Room.
o Local Scheduler – Runs bots on time as per schedule.

Recorders in RPA
What is a Recorder?

A Recorder in RPA is like a video camera for your computer actions.

It watches what you do (click, type, scroll, etc.) and saves those steps so the bot can repeat
them automatically.
Recorders are tools in RPA used to capture user interactions (mouse clicks, keyboard inputs,
etc.) with applications or systems, and convert them into automation scripts without manual
coding.

Types of Recorders:
1. Screen/Desktop Recorder
o Purpose: Captures all user actions on the computer screen.
o Usage: For desktop applications, browsers, and GUI automation.
o Advantage: Visual and intuitive — no programming required.
2. Web Recorder
o Purpose: Captures interactions within web browsers.
o Usage: For automating web-based tasks like filling forms, clicking links,
navigating pages.
o Advantage: Can identify web elements and handle dynamic web pages.

Common Features:
 Recording Modes: Recordings can often be done in different modes, such as "Record,"
"Playback," and "Edit," allowing users to capture actions, play them back, and make
adjustments.
 Element Identification: Recorders may provide the ability to identify and interact with
specific elements on the screen or web page, such as buttons, text fields, and
dropdowns.
 Parameterization: Some recorders allow users to parameterize recorded actions,
making it possible to use variables and handle dynamic data
 Conditional Logic: Advanced recorders may include options for adding conditional
logic, loops, and error handling to the recorded scripts.

Special Recorders in Automation Anywhere:

1. Universal Recorder:
o Records clicks, reads, and writes on UI objects.
o Works with UI elements instead of coordinates/images (more reliable).
o Example: Capture hyperlink → choose to click or get text.
2. AISense Recorder:
o For Citrix/RDP or legacy apps where object-based automation is hard.
o AI-powered, resilient to screen resolution and UI changes.
Smart Recorder
1. What is Smart Recorder?
 Smart Recorder is a special tool in Automation Anywhere that captures window
objects for automation.
 It can capture:
o Coordinates (position of items on the screen)
o Object properties (like name, ID, type)
o Images (for image-based automation)
o Playback mode (how the recorded steps are replayed)
 It also allows adjusting object identification criteria using AA Binoculars
(Automation Anywhere’s object property inspector).

2. Why Use Smart Recorder?

 Best for automating desktop applications and system settings.
 Helps when you need to record steps exactly as they appear.
 Allows you to choose what property is most important for identifying objects (e.g.,
button name, control ID).

3. Example: Changing the Time Zone in Windows (Automation Example)

Procedure:
1. Open the system control panel on your PC.
(Prepare the action to record – in this case, changing the time zone)
2. In Enterprise Client:
o Click New to create a new task.
o Select Smart Recorder.
o Click Record.
3. Select “Control Panel” from the list and click Start.
4. Perform the required actions (Smart Recorder is now capturing your steps):
a. Click Date and Time in Control Panel.
b. Select Clock and Region.
c. Click Change the time zone.
d. Click Change time zone….
e. Select a new time zone from the list.
 f. Click OK.
g. Click OK again on the Date and Time window.
5. Click Stop to end recording.
6. Save the recorded task:
o Enter a file name.
o Choose a directory to save it.

4. Key Points to Remember

 Smart Recorder works well with both coordinate-based and object property-based
automation.
 You can fine-tune object recognition for better accuracy.
 Good for repetitive desktop operations.
 Not limited to one application — can record actions across multiple windows.

Web Recorder
1. What is Web Recorder?
 A Web Recorder is an RPA tool that captures your actions in a web browser and
automatically converts them into automation commands.
 It is used in IBM RPA Studio (and similar RPA tools) for web browser automation.
 It can:
o Map web elements (buttons, text fields, links, etc.)
o Record browser actions (clicking, typing, navigating)
o Generate automation scripts automatically.

2. Why Use Web Recorder?

 Saves time — no need to write code for web automation.
 Can handle form filling, page navigation, and data extraction.
 Works with major browsers: Chrome, Edge, Firefox.

3. How to Use Web Recorder in IBM RPA Studio

1. Log in to IBM RPA Studio.
2. Create a new script or open an existing one.
 3. On the Home tab, click Start Recorder.
4. Click the Activate Web Recorder icon.
5. Select a browser option:
o Chrome
o Edge
o Firefox
6. In your chosen browser, click the Web Recorder extension to activate it:
o Gray icon → Plug-in installed & working.
o Blue icon → Recorder is active and sending commands to IBM RPA Studio.
o Red icon → Plug-in installed but not communicating with IBM RPA service.

4. Key Points to Remember

 Web Recorder is browser-specific — must enable the extension.
 Records user actions and element properties.
 Generates a Use Application/Browser activity with the recorded steps.
 Speeds up web automation for non-programmers.

Task Editor
1. Definition
Task Editor is a Graphical User Interface (GUI) tool in RPA used to create, edit, and manage
automation workflows (bots).
Allows drag-and-drop or point-and-click design — no coding needed.

Here's a breakdown of the typical process involved in using a task editor:

1. Opening the Task Editor: Launch the RPA software and navigate to the task editor module.
2. Creating a New Task: Start by creating a new task or workflow within the task editor.
This often involves selecting a template or starting from scratch.
3. Defining Steps: Using drag-and-drop or point-and-click interfaces, define the sequence of
actions or steps the robot will perform. These steps can include opening applications,
entering data, clicking buttons, navigating menus, extracting information, and more.
4. Configuring Actions: For each step, configure the specific actions the robot should
perform. This may involve setting parameters, defining conditions, specifying input data,
or customizing options based on the requirements of the task.
5. Testing and Debugging: Before finalizing the task, it's essential to test and debug the
automation workflow to ensure it functions correctly. Many task editors provide built-in
testing tools or simulation features for this purpose.
6. Iterating and Refining: Refine the task as needed based on testing results or feedback.
This may involve tweaking actions, adjusting parameters, or optimizing the workflow for
efficiency and reliability.
7. Saving and Publishing: Once satisfied with the automation workflow, save the task within
the task editor. Depending on the RPA platform, you may also have the option to publish the
task to a central repository or schedule it for execution at specific times.
8. Monitoring and Maintenance: After deployment, monitor the performance of the
automated task and address any issues or updates as necessary. This may involve making
changes to the task editor or updating the automation logic to adapt to changes in the
underlying systems or processes.
Overall, the task editor serves as a crucial tool for designing, implementing, and managing
RPA automation workflows, allowing users to streamline processes and improve productivity
in various business scenarios.

Variables – RPA
1. Definition
 Variables are storage locations that hold values used in automation or experiments.
 They can be created in the editor or during execution.
 Variables are global (accessible anywhere in the experiment) if added to the global list.

2. Where Variables are Managed

 Found in the "Variables" tab of the main navigation panel.
 By default, not added to the global list (to avoid clutter).
 To make global: Click "view in global list" under variable properties.

3. Variables in Task Editor

 Variables for the current frame are shown in the Variables tab (top right).
 Properties shown: Category, Data type, and Name.
 Actions: Copy, Delete, Inspect, or Edit properties.
 Can create new variables at any time using "New Variable" icon.
4. How Variables Work
 Changing a variable can trigger an event.
 Events can also change variable values.
 Variables can control the state of certain objects.

5. Categories of Variables
1. System Variables – Built-in variables provided by the platform.
2. Factor Variables – Represent factors/conditions in experiments.
3. Object Variables – Linked to UI objects.
4. Custom Variables – User-defined variables for specific needs.
5. Unused Variables – Variables created but not currently used.

Command Library
1. Definition

 A Command Library in RPA is a collection of pre-built automation

commands/actions used to perform specific tasks in a workflow.
 Purpose: Makes bot creation easier by allowing drag-and-drop of ready-made
commands without coding.
2. Benefits

 Saves development time.

 Easy for non-programmers.
 Ensures consistency in automation workflows.

3. Common Types of Commands in RPA Command Library

1. Input & Output Commands

o Read data from files, databases, APIs.
o Write/update data to files, databases, or other destinations.
2. User Interface (UI) Interaction Commands
o Click buttons, enter text, select dropdowns.
o Screen scraping and extracting data from UI elements.
3. Control Flow Commands
o If statements, loops, switches.
o Error handling for exceptions.
4. System Integration Commands
o Connect with other applications or external APIs.
5. File & Folder Commands
o Copy, move, delete files/folders.
6. Data Transformation Commands
o Modify or transform data.
o Use regular expressions for pattern matching and extraction.
7. Variable & Data Storage Commands
o Create, modify, and manage variables.
o Work with different data storage solutions.
8. Logging & Debugging Commands
o Log information for debugging.
o Pause or step through automation for testing.
9. Security Commands
o Handle secure data and encryption.
10. Notification Commands
o Send alerts or notifications.

4. Usage

 In most RPA platforms (e.g., UiPath, Automation Anywhere, Blue Prism), commands
are dragged onto the workflow canvas and configured for the task.
 Supports custom commands to allow reusability.
Loop Command
1. Definition
 A Loop Command in RPA is used to repeat a set of actions until a condition is met.
 Essential for automating repetitive tasks and iterating over collections of data.
 Syntax and options may vary depending on the RPA tool (UiPath, Automation
Anywhere, Blue Prism, etc.).

2. Types of Loops
A. For Each Loop
 Purpose: Go through each item in a collection (list, array, records).
 Usage: Actions inside the loop are executed for each item.
 Example: Loop through a list of employees and process each one.
For Each (item) in (collection)
{
// Actions for each item
}

B. While Loop
 Purpose: Repeat actions while a condition is true.
 Usage: Stops when the condition becomes false.
 Example: Continue until a counter reaches a certain value.
While (condition)
{
// Actions while condition is true
}

C. Do-While Loop
 Purpose: Similar to While, but executes at least once before checking the condition.
 Usage: Condition is checked after running the loop body.
 Example: Perform an action, then check if it should repeat.
Do
{
// Actions at least once
}
While (condition)

D. For Loop
 Purpose: Run a set of actions for a specific number of times.
 Usage: Used when the number of iterations is known in advance.
 Example: Repeat an action 10 times.
For (initialization; condition; increment/decrement)
{
// Actions for each iteration
}

3. Key Points
 Loops help avoid manual repetition in automation.
 Conditions can be fixed or dynamic (based on data).
 In UiPath – loops appear as "For Each", "While" activities.
 In Automation Anywhere – loops are configured using the "Loop" command.

XML Command
1. Definition
 XML (eXtensible Markup Language) is used for storing and exchanging structured
data.
 In RPA, XML Commands are used to read, write, modify, and process XML data
during automation.
 Useful for data interchange between applications, APIs, and systems.

2. Common XML Commands & Their Purpose

1. Read XML
o Purpose: Read XML from a file or string.
o Example: Get data from an XML API response.
2. Write XML
o Purpose: Create or update XML documents.
o Example: Save updated product details in XML format.
3. XPath Navigation
o Purpose: Navigate and extract data using XPath expressions.
o Example: Get the value of a specific <price> tag.
 4. XML Element Creation / Modification
o Purpose: Add or edit XML elements or attributes.
o Example: Add a new <customer> node.
5. XML Validation
o Purpose: Check if XML follows a specific schema (XSD).
o Example: Validate an XML invoice format.
6. XPath Query Execution
o Purpose: Run queries to get specific nodes or values.
o Example: Retrieve all <order> elements with status "Pending".
7. Transform XML (XSLT)
o Purpose: Convert XML to another format using XSLT.
o Example: Convert XML to HTML for display.
8. XML Parsing
o Purpose: Break down XML into smaller structured parts for processing.
o Example: Extract <name> and <email> values.
9. XML Serialization / Deserialization
o Purpose: Convert XML into program objects (and back).
o Example: Load XML into memory as objects for easy manipulation.
10. Append / Remove XML Nodes
o Purpose: Add or delete XML elements/attributes.
o Example: Remove an outdated <address> tag.

3. Key Points
 Cross-platform: All major RPA tools (UiPath, Automation Anywhere, Blue Prism)
support XML commands.
 Best Use Cases: Data exchange with APIs, structured data handling, document
automation.
 Note: Syntax may vary per RPA platform.

Object Cloning Command

 Purpose: Allows bots to identify and interact with GUI elements (buttons, text fields,
dropdowns, etc.) in desktop or web applications.
 Used for creating Task Bots or MetaBots to automate actions within specific
application technologies.
Play Modes
1. Object Mode
o Captures objects based on their properties.
o Works with technologies like Microsoft Windows, HTML, Java, Oracle EBS,
Flex.
o Highly precise and flexible.
2. Coordinates Mode
o Captures the coordinates of an object.
o Useful for objects invisible to the capturing technology (e.g., Remote Desktop,
Citrix).
3. Image Mode
o Captures an image of the object and searches for it.
o Ideal for static images (e.g., drop-down arrow button).
o Limitations: Not effective when multiple identical images are present.

When to Use vs. Web Recorder

 Use Object Cloning:
o For Windows applications and technologies like Flex, Silverlight, Java,
HTML.
o Works with Internet Explorer, Google Chrome, Mozilla Firefox.
 Use Web Recorder:
o Only for web-based tasks in Internet Explorer.
 Browser Limitation:
o

o Cannot record in IE and play in Edge.

o On Chromium-based Edge, cannot capture/play on Chrome and Edge
simultaneously.

Citrix Integration
 Supports automation on remote Citrix Virtual Apps servers.
 Requires Enterprise Client installation on Citrix VMs.
 May need remote agent or plugin for capturing.
 If unable to capture on Citrix XenApp Server, follow troubleshooting guides.

Key Settings & Actions

 Delay Setting:
 o Adds a pause between bot actions (especially in Set Text).
 Set Text Action:
o Inputs/replaces text into an object control.
 Select Technology:
o Allows specifying the application technology for better object recognition.
 Troubleshooting:
o Select Window display issues – fix recognition problems.
o PowerBuilder platform controls – some actions may fail; workarounds
available.

PDF Integration Command

Used for performing various PDF manipulation tasks such as extracting, merging, splitting,
encrypting, decrypting, converting, and validating PDF files.

Core Functions

1. PDF to Image
o Converts a PDF into an image format (e.g., PNG, JPEG).
2. Extract Form Fields
o Retrieves all form field data and selected text, stores in variables.
3. Extract Text
o Pulls text from a PDF into a text file for further processing.
4. Merge Documents
o Combines multiple PDF files (encrypted or unencrypted) into one.
5. Split Document
o Splits a PDF into separate files based on specified criteria.
6. Encrypt Document
o Secures the PDF with a password and sets user permissions.
7. Decrypt Document
o Removes password protection from a secured PDF.
8. Extract Images
o Retrieves embedded images from PDFs for separate processing.
9. OCR (Optical Character Recognition)
o Extracts editable text from scanned PDFs or images within PDFs.
10. Fill Form Fields
o Automatically inputs data into predefined PDF form fields.
11. Stamp or Watermark
o Adds stamps or watermarks such as logos, timestamps, or labels.
12. Redact Content
o Permanently removes sensitive/confidential text or images.
13. Convert PDF to Text Format
o Converts the full PDF content into plain text for analysis.
14. Extract Metadata
 o Retrieves author info, creation date, keywords, and other metadata.
15. Validate PDF Structure
o Checks compliance with PDF standards, ensuring file integrity.
16. Compare Documents
o Detects differences between PDF versions for version control.
17. Convert PDF to Other Formats
o Converts PDF to Word, Excel, HTML, or other formats for interoperability.