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.

To create an Application method, right-click on an application in the Project Explorer.

Application methods should be limited in scope. For example, an Application method might contain only a login or search sequence. Limiting the scope makes it easier to share, reuse, and test Application methods.

The Project Explorer shows the dependency of the Application methods to their application, as in the following figure.

When creating Application methods, you only see the controls and methods that exist for the Application method. For example, there is no access to Globals and you cannot reference other 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 can be added with the Project Explorer Add button or in the Quick Start wizard.

The script component lets you add custom C# methods to your solutions. The script component can only be added to Globals.

Use the Preview migration utility to migrate your Robot Studio 19.1 solutions to 21.1 projects, so you can open and test them. For more detail, see the Preview Migration Utility.

Environment overrides in v21 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.

At runtime, the overrides are applied to the project before the project is run. In the following figure, the Text for a Windows form in the Test environment is Test Form and in the Production environment it is Production Form.

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.

The Current tab shows the references used in the Project. You can also add references from:

• .NET (GAC or Global Assembly Cache)
• Pega (installation folder)
• PublicAssemblies folder (in AppData)

Use the UI Connectors feature to develop translators for .NET and Java applications and extend support for additional controls. With this feature, you build the integration points that provide the ability to automate the controls for an application.

• Mimic the power and control that Robot Studio provides out-of-the-box.
• Map the properties and methods of a control to the standard items used by automation developers.
• Use when you interrogate an application and the application controls are not identified.

Added support for StartMyDay.

StartMyDay provides a set of accelerator methods that are used to start applications on demand or automatically at project startup. StartMyDay also allows a user to visually arrange the applications on their desktop to their preference.

StartMyDay methods and properties are in the Toolbox, under Accelerators.

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.

Support for adjusting logging levels by category has been added to Robot Studio and Robot Runtime as in the following example:

<Category name="Automation" logLevel="3"/>

Logging categories and their log levels are maintained in PegaStudioConfig.json and PegaRuntimeConfig.xml, in the %appdata%\Pegasystems folder.

You can now reorder steps in the Recording assistant.

Click and drag the Drag handle of a step to change the order of steps in the Recording assistant.

• GetProjectPath()
• GetDeploymentVersion()
• GetRuntimeVersion()
• GetProjectVersion()
• RobotNotReadyForWork event
• RobotReadyForWork event

Message manifest support is now included. Message manifest methods are available on the Toolbox. You can manage message definitions from the Project properties panel.

• Math methods (Utilities folder of Toolbox)
• Financial methods (Data Handling folder of Toolbox)
• Process methods (Data Handling folder of Toolbox)

The features available in Robot Inspector are being incorporated into Robot Studio v21 and will be made available through Robot Runtime.

Automation playback provides the ability to step through a Robot Runtime log through the lens of the automation developer in Robot Studio.

Stay tuned...

For most features, Robot Manager integration will require a minimum version of Robot Manager 8.6.1. This integration will be available in a future release of the v21 Preview. Notable features that are not part of Robot Manager 8.6.1 (or Platform 8.6) include:

• In v21, we are redesigning how attended bots are invoked from Pega applications. This integration will no longer include the use of the Robot Runtime REST service. Support will be added in Pega Platform and Robot Manager 8.7.
• Automation package signing will be added to Robot Manager 8.7.

Pega Platform 8.7 and Robot Manager 8.7 are in development now and expected to be released in Q4, 2021.

Translator support for the following software is not yet available:

• ComponentOneOCX
• Delphi
• LegaSuite
• OracleForm6
• PowerBuilder
• QuickBooks

Start screen

Pega Academy Startup topic

The new Start screen simplifies creating a new project or working with existing ones.

Quick start: The new Quick Start feature lets you quickly name a project, select an application, and begin recording an automation.

You can also open an existing project or build a new project from scratch. You can also add folders as needed, to help with organizing your project.

Project Explorer

Pega Academy Project Explorer topic

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.

The Project Explorer lists all project items, which are described below:

• Globals
• Applications
• Automations
• Windows forms

Toolbox

Pega Academy Toolbox topic

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.

The Toolbox displays on the left side of the screen, beside the Palette. Its content changes based on the type of project item selected (automation versus Globals, for example).

The Toolbox has icons that indicate whether an item is a variable (V icon), component (C), property (P), method (M), or event (E).

Palette

Pega Academy Palette topic

The Palette replaces the Object Explorer. Like an artist’s palette, it provides a clean, well-organized location containing only the necessary items used to build the current automation. The Palette always occupies the left side of the screen.

To add or remove a project item—Windows forms, automations, or applications—click Include at the top of the Palette. To add a Toolbox item, drag it to the design area.

Globals

Pega Academy Globals topic

Each project has a single Globals project item by default. This item is docked at the top of the Project Explorer and displayed on the Palette for each automation. This project item replaces the Global Containers that were used in previous versions. You can add folders to Globals to make the content more manageable. In a later version of the Preview, when 19.1 projects are upgradeable, the system will create a folder for each Global Container.

When dragging items that are designed to be global in scope to an automation from the Toolbox, the item is moved automatically to Globals.

Application designer

Pega Academy application designer topic

-Also-

Pega Academy UseKeys topic

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.

The Palette has icons that indicate the matching status and cloning. A green eye represents a successful match.

For a cloned item, you will see the number of cloned items. (The number is accurate from 0-9; when more than 9 items are matched, you will see 9+.)

Automation surface

Pega Academy Automation surface module

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.

Sensitive data

Pega Academy sensitive data topic

Sensitive values like Personally Identifiable Information must never show in logs or be visible on the automation surface. New features have been added to help you ensure that sensitive data is protected.

• A sensitive-data variable has been added, to use as an input/output parameter or local/global variable.
• You can use the Property Grid to mark existing variables as sensitive.
• Robot Studio automatically marks interrogated password controls as sensitive.
• You can mark other interrogated controls as sensitive.

Testing and debugging

Pega Academy debugging module

There are two ways to debug in v21 Preview: either by running the project or by testing an automation. Choose Run all to debug the entire project, as in 19.1.

Testing is a new capability in v21, which makes debugging faster and easier. Testing allows you to debug a single automation plus any subautomations. Automations being tested use any currently open applications.

When debugging, property values display on automation blocks, providing immediate feedback.

We are especially interested in hearing how this new feature works for you.

Intelligent Recording

Pega Academy Intelligent Recording module

Intelligent Recording records the steps in an application and builds an automation as you work. You can modify and delete steps as needed.