Lesson Overview

This lesson introduces learners to the use of toolkits and platforms in Robotic Process Automation (RPA). Learners will explore different automation toolkits available in the market, their advantages and disadvantages, and how they are applied in business environments. The lesson also covers robots and robot types, workflow development tools, automation management tools, installation, user interfaces, the Software Development Life Cycle (SDLC), and how to understand a specific vendor toolkit or platform before using it in an automation project.

Lesson Outcomes

After completing this lesson, learners will be able to:

• Assess various automation tools and platforms for suitability and use
• Explain the advantages, disadvantages, applications, and uses of toolkits in the market
• Describe how toolkits/platforms are used to plan, build, manage, run, and measure automation
• Identify robots and their types in an RPA environment
• Explain workflow development tools and automation management tools
• Describe installation and user interface considerations
• Explain the Software Development Life Cycle and its application
• Describe what a specific vendor toolkit/platform offers to users

KT0101: Various Toolkits in the Market

A toolkit or platform is a software environment that provides tools, features, and components used to create applications or automation solutions. In RPA and automation environments, toolkits help users design workflows, create bots, manage processes, integrate systems, and automate repetitive tasks.

The source material explains low-code platforms as tools that allow applications to be created with little coding. These platforms use visually driven development environments and graphical user interfaces, often including drag-and-drop features that allow users to build applications by placing elements such as buttons, text, images, maps, icons, and other components into a workflow or application screen.

Advantages of Low-Code and Automation Platforms

Low-code and automation platforms offer several advantages in business and RPA environments.

Business agility
Businesses operate in fast-changing environments. Low-code platforms allow organisations to respond more quickly to new requirements because applications and workflows can be developed faster than with traditional coding approaches.

Increased productivity
Low-code platforms often provide prebuilt elements, templates, components, and drag-and-drop functionality. This reduces the amount of time developers spend writing code from scratch.

Democratised application development
The source material explains that low-code platforms allow business users or “citizen developers” to build applications even if they have limited programming knowledge. This is useful because business users often understand the process problem clearly, even if they are not professional developers.

Cost savings
Low-code platforms can reduce development costs because existing employees may be able to use the platform without requiring large specialist development teams for every application.

Cloud hosting and faster deployment
Low-code platforms can support flexible deployment, including cloud-based delivery. This allows applications and automation solutions to be made available more quickly.

Improved user experience
Many platforms include built-in styles, screen templates, user interface components, logic, and layouts. These features help users create applications that are easier to use and more visually organised.

Disadvantages of Low-Code and Automation Platforms

Automation platforms also have limitations that must be considered before adoption.

Limited flexibility
Some platforms only allow users to customise within the features provided. If the platform does not support a required function, developers may need to write custom code or use another tool.

Security risks
The source material notes that low-code platforms may include built-in security protocols, but they may not always provide the same level of security as standalone development technologies. Organisations may also depend on the platform provider to fix security issues.

Vendor lock-in
Vendor lock-in occurs when an organisation becomes dependent on one platform provider. If the platform does not allow easy export or modification of code, it may become difficult to move the solution to another system later.

Shadow IT
Shadow IT occurs when departments or individuals use unapproved software tools without proper IT oversight. This creates security, compliance, and resource risks.

Complex business logic
Some platforms are suitable for simple automations or prototypes, but complex business logic may still require skilled professionals and more advanced development methods.

KT0102: Toolkit/Platform to Plan, Build, Manage, Run and Measure Automation and Its Products

RPA software uses bots to automate routine tasks within software applications. These are tasks normally performed by employees and are often repetitive, time-consuming, and tedious. The purpose of using an automation platform is to reduce manual effort and improve process efficiency.

A complete automation platform usually supports the automation lifecycle:

Plan

Planning involves identifying what process should be automated, what systems are involved, and what outcome is expected. The organisation must decide whether the process is suitable for automation.

Planning may include:

• Identifying repetitive tasks
• Understanding the business process
• Reviewing the systems involved
• Determining risks and dependencies
• Selecting the correct automation tool

Build

Building involves designing and developing the automation workflow or bot.

This may include:

• Creating workflows
• Adding activities
• Configuring rules
• Connecting applications
• Setting input and output data
• Testing each part of the automation

Manage

Managing automation involves monitoring, organising, and controlling bots and automation workflows.

This may include:

• Managing bot schedules
• Monitoring performance
• Controlling access
• Tracking errors
• Reviewing logs
• Updating workflows

Run

Running automation means executing the bot or workflow.

Automation can run:

• Manually when started by a user
• Automatically according to a schedule
• Based on a trigger or system event

Measure

Measuring automation helps organisations determine whether the automation is successful.

Measurement may include:

• Time saved
• Error reduction
• Cost savings
• Number of completed tasks
• Bot performance
• Process accuracy

A good automation platform should help organisations plan, build, manage, run, and measure automation in a controlled and reliable way.

KT0103: Robots and Their Types

In RPA, a robot is not a physical machine. It is a software robot, also called a bot, that performs tasks within digital systems.

Bots imitate human actions such as:

• Opening applications
• Logging into systems
• Copying and pasting data
• Completing forms
• Reading emails
• Moving files
• Generating reports
• Updating records

Attended Robots

Attended robots work with human users. They are usually started by an employee and assist with specific tasks while the employee continues working.

Example: A call centre employee uses an attended bot to pull customer information from several systems during a customer call.

Unattended Robots

Unattended robots run independently without direct human involvement. They may be scheduled to run at certain times or triggered by system events.

Example: A bot generates daily reports every evening and sends them to managers automatically.

Hybrid Use

Some organisations use both attended and unattended robots. Attended bots support employees during work, while unattended bots process large volumes of work in the background.

KT0104: Workflow Development Tools Overview

Workflow development tools allow users to design, build, and organise automation processes.

A workflow is a sequence of activities required to complete a task. In RPA, workflows may include actions such as opening an application, reading data, applying conditions, making decisions, and saving results.

Workflow development tools usually provide:

• Visual design areas
• Drag-and-drop activities
• Decision structures
• Sequence building
• Application integration
• Error handling
• Testing tools

These tools help developers create automation logic in a structured way.

Workflow tools are important because automation must follow a clear process. If the workflow is poorly designed, the bot may fail, produce incorrect results, or become difficult to maintain.

KT0105: Automation Management Tools

Automation management tools help organisations control, schedule, monitor, and manage automation activities.

These tools are useful when an organisation has multiple bots, workflows, users, and business processes.

Automation management tools may support:

• Scheduling bot execution
• Monitoring bot status
• Reviewing process logs
• Managing queues
• Assigning robot resources
• Handling exceptions
• Tracking performance
• Managing credentials and permissions

Scheduling

Scheduling allows bots to run at specific times.

Example: A bot may be scheduled to process invoices every weekday at 18:00.

Monitoring

Monitoring allows users to see whether bots are running successfully or failing.

Logs

Logs record bot activity. Logs are useful for troubleshooting, auditing, and performance review.

Exception Management

Exception management helps identify and handle situations where automation cannot complete a task as expected.

Automation management tools are important because they help organisations maintain control over automated processes.

KT0106: Installation

Installation refers to setting up the toolkit or platform so it can be used for automation development and execution.

Installation may involve:

• Downloading the platform installer
• Installing required software components
• Setting up user accounts
• Configuring licences
• Connecting to required systems
• Installing extensions or plugins
• Testing that the platform runs correctly

Before installation, users should check:

• Hardware requirements
• Operating system compatibility
• Internet access
• Licence requirements
• Security permissions
• Required integrations

Correct installation is important because a poorly installed platform may cause errors, security issues, or failed automation execution.

KT0107: The User Interface (UI)

The User Interface, or UI, is the part of the toolkit or platform that users interact with.

A good UI helps users:

• Create workflows
• Access tools and menus
• Configure automation activities
• View errors
• Manage files
• Run and test processes

In low-code platforms, the UI is especially important because much of the development happens visually.

Common UI elements include:

• Menus
• Buttons
• Panels
• Workflow design canvas
• Properties panel
• Activity libraries
• Error messages
• Run and debug controls

The source material explains that low-code platforms often use graphical interfaces and drag-and-drop features to support development. This makes the platform easier for both technical and non-technical users to work with.

KT0108: Software Development Life Cycle (SDLC)

The Software Development Life Cycle, or SDLC, is a systematic process used to plan, build, test, deploy, and maintain software. The source material explains that SDLC aims to produce high-quality software that meets customer expectations within a defined time and cost.

SDLC is important in automation because RPA solutions must also be planned, developed, tested, deployed, and maintained properly.

Stage 1: Requirement Analysis

Requirement analysis involves understanding what the client or business needs.

This includes identifying:

• What process must be automated
• What systems are involved
• What data is required
• What rules must be followed
• What outcome is expected

The source material notes that before creating a product, a clear understanding of the product is necessary. Requirements must be precise so that the solution can be properly designed.

Stage 2: Defining Requirements

After analysis, the requirements must be documented clearly.

This is often done in a software requirement specification document, or SRS.

The SRS describes what the product or solution must do.

Stage 3: Designing the Software

Design involves planning how the solution will work.

In an RPA context, this may include:

• Process flow design
• Workflow structure
• Bot activities
• Application interactions
• Input and output data
• Error handling approach

Stage 4: Developing the Project

This is where the automation or software is built.

Developers use tools such as:

• Automation platforms
• Compilers
• Interpreters
• Debuggers
• Workflow designers

In RPA, development may involve creating workflows, configuring bots, adding decision rules, and integrating applications.

Stage 5: Testing

Testing checks whether the solution works according to the requirements.

Testing may include:

• Unit testing
• Integration testing
• System testing
• Acceptance testing

Testing is important because automation must produce accurate and reliable results.

Stage 6: Deployment

Deployment happens when the solution is released for use.

The source material explains that once software is certified and no bugs or errors are stated, it is deployed. After deployment, maintenance begins.

Stage 7: Maintenance

Maintenance involves supporting, updating, and improving the solution after users begin using it.

Maintenance may include:

• Fixing errors
• Updating workflows
• Improving performance
• Adapting to business changes
• Responding to system changes

SDLC helps ensure that automation solutions are planned, built, tested, deployed, and maintained in a structured way.

KT0109: Understanding the Specific Vendor Toolkit/Platform

Before using a vendor toolkit or platform, learners must understand what the platform offers and how it applies to the organisation’s automation needs.

The source material notes that vendor tools allow organisations to manage vendors consistently through collaboration and monitoring. It also explains that selecting the right tool requires planning and assessment.

In the context of RPA, understanding a vendor platform means knowing:

• How to install it
• What it is used for
• What features it provides
• What limitations it has
• Whether it suits the business process
• Whether it supports security and compliance
• Whether it can integrate with existing systems

Installation

Learners should know the installation process for the chosen toolkit/platform.

This includes:

• Software requirements
• Licence setup
• User account setup
• Required plugins
• System permissions
• Connection to other applications

Application

The application of the toolkit refers to how it is used in real business or automation tasks.

A platform may be used to:

• Build workflows
• Create bots
• Automate business processes
• Manage schedules
• Monitor performance
• Integrate with applications
• Generate reports

What Is It Offering Us?

When evaluating a vendor platform, learners should consider what the platform provides.

This may include:

• Ease of use
• Visual workflow design
• Drag-and-drop tools
• Scheduling features
• Bot management
• Reporting
• Security features
• Integration options
• Support and documentation
• Scalability

A platform should be assessed for suitability before being used in an automation project.

Key Notes

• KM-06-KT01 focuses on using a toolkit/platform for automation.
• Low-code platforms allow applications and workflows to be created with little coding.
• Advantages of low-code platforms include business agility, productivity, cost savings, cloud hosting, and improved user experience.
• Disadvantages include limited flexibility, security risks, vendor lock-in, shadow IT, and difficulty with complex business logic.
• RPA platforms help users plan, build, manage, run, and measure automation.
• Software robots, or bots, may be attended or unattended.
• Workflow development tools help design automation steps visually and logically.
• Automation management tools support scheduling, monitoring, logging, and exception handling.
• Installation requires attention to system requirements, licences, permissions, and integrations.
• The User Interface is important because it affects how easily users can build and manage workflows.
• SDLC provides a structured process for requirement analysis, design, development, testing, deployment, and maintenance.
• A vendor toolkit/platform must be assessed for what it offers, how it is installed, and how it applies to automation needs.