New and updated features
Pega Robot Studio version 22.1 is a redesign of the product, with many new and improved features.
New features
Feature | Description | More detail |
Start screen | The new Start screen simplifies creating a new project or working with existing ones. ![]() | Overview of creating a project |
Project Explorer | When a project is open, the main screen is the Project Explorer. The Project Explorer provides a clean, easy-to-use experience for creating, updating, and organizing your automation projects. The Project Explorer shows important information about recent projects. ![]() | Managing projects with Project Explorer |
Toolbox | The Toolbox contains components and variables, organized into logical sections. In addition, we have extracted properties, methods, and events from the utility components (such as stringUtils) and placed them directly in the Toolbox. You can easily search for and locate the item you need. Recently used objects display at the top of the Toolbox. In addition, you can right-click an item and add it to your Favorites, which are always handy at the top of the list. ![]() | Working in the Toolbox |
Palette | The Palette replaces the Object Explorer. Like an artist’s palette, it provides a clean, well-organized location containing only the items that are relevant to build the current automation. The Palette always occupies the left side of the screen. ![]() | Working in the Palette |
Application designer | Adapters are now referred to as application project items. The matching window has been redesigned. The single property grid on the right side of the screen is used to evaluate all sections—match rules, targets, and selected controls—and swaps views based on the item in focus. | Working in the Application Designer |
Automation surface | Visually, the automation surface has been updated but the general workflow of automations has not changed. The Select action dialog is used to add blocks to the automation surface; select an item from the Palette and drop it onto the automation surface to show the Select action dialog. Select a pinned property, method, or event, or click More to explore all properties, methods, and events that are available. | Building automations on the Automation Surface |
Intelligent recording | Intelligent Recording records the steps in an application and
builds an automation as you work, illustrating how to build
automations that can be modified and expanded. You can delete,
reorganize, configure, and test steps as needed. ![]() A login sequence is automatically recognized and can be moved to a new automation, ignored, or not included in your automation, which promotes modularity and reusability. | Intelligent Recording |
X-ray Vision | X-ray Vision automates the process of uniquely identifying controls for .NET, WPF, Chrome, and Edge applications. The use of Artificial Intelligence and Machine Learning ensure that Robot Studio and Robot Runtime continues to correctly identify controls, even as applications change. | X-ray Vision |
Security and sensitive data | Sensitive values like Personally Identifiable Information (PII)
should never show in logs or be visible on the user interface.
Robot Studio automatically marks
passwords and other confidential data as sensitive. You can mark
other controls as sensitive.![]() In addition, application login credentials are stored via DPAPI and applied automatically at design time for Robot Studio users, ensuring that credentials are secured and speeding up the login process. | Sensitive data |
Testing and debugging | Automation testing allows users to debug automations for currently running applications, which provides rapid debugging across different sets of input data without restarting and logging into the application. The black-eye icon has been added to the Palette to identify issues, highlighting duplicate matches to address. When debugging, property values display on automation blocks, providing immediate feedback. | Debugging and testing automations |
Application methods | Application methods are single-purpose automations that are created by automation developers and used in an automation just like any out-of-the-box method of an application. Application methods isolate key functionality in small components or modules that are easy to reuse, test, and share. | Application methods |
Assets | Assets are reusable automation components. An experienced
developer can create an application and a series of methods for it.
The developer can then deploy the application as an asset, making
the application and its methods available for reuse in
automations.![]() Other developers can download assets from a Robot Manager 8.8 repository and import them into projects. | Assets |
Build automations faster | Many of the new features mentioned in this table work together
with new UI developments to streamline the process of building
automations. From Quick Start and Quick Add dialog boxes to wizards
that step through tasks, to the Palette that shows only relevant
items, Robot Studio has been completely
redesigned to make automation development easier and faster.![]() | Creating robotic automations |
Robot Runtime | Citrix packages are now streamed to a remote context, which greatly simplifies infrastructure and setup for new package versions. Lazy loading of automation projects at runtime ensures that project items are loaded as needed. This speeds the loading of big projects and allows attended RPA users to be up and running much faster. A new delivery method for the Chrome/Edge extension through the Pega Browser Extension simplifies updates for enterprises. | Citrix |
PBE (Pega Browser Extension) | The new Pega Browser Extension (PBE) component ensures that the Google Chrome and Microsoft Edge browser extensions comply with the Chromium Project Manifest V3 specification. PBE is a standalone component, just like Pega RPA Service and Pega Native Foundation that’s used to automate Chrome and Edge applications. PBE includes the extension and the Messaging Host. | PBE |
Environment overrides | Environment overrides replace Configurations in prior versions of Robot Studio but work in much the same way. Use environment overrides to customize your project to run in different environments. Some examples of environments that you may need to customize for are Development, QA, and Production. You can override property values for variables, controls, and match rules at runtime for each environment.You can set values of certain variables and properties at runtime based on the environment you're running. | Environment overrides |
Text applications | Use Text applications to integrate with terminal emulator applications. Pega Robot Studio lets you create projects that integrate with mainframe applications. Robot Studio supports the most commonly used WinHllapi- and EHllapi-based emulator software. | Text applications |
Script component | The script component lets you add custom C# methods to your solutions. The script component can only be added to Globals. | Adding a Script component |
Manage references | The Manage references dialog allows you to add references to your project that are required for your C# scripts. You can access this dialog from the Script editor. | Manage references |
Add existing project items | You can now add a project item to your project that exists within another project. You can also use the Generate new ID capability to safely duplicate a project item that exists within your project. You can add an automation, an application, or a Windows form. In the Project Explorer, select Add > Existing file. ![]() | Add existing project item |