Robotic Automation glossary
adapter control | bundle | CommonConfig.xml file | deployment level | execution context | inheritance | Interaction Manager | interactions | Interaction.xml file | native control | package | Pega Robot Manager | project | RuntimeConfig.xml | Runtime-only users | solution | StudioConfig.xml | target | translator | UI Connector
Adapter controls are components displayed in Pega Robot Studio Object Explorer and used by automation developers. The properties, methods, and events of these controls provide a way to interact with native controls.
When you use the option to build a solution in Pega Robot Studio, the system creates a bundle that includes all the files needed by Pega Robot Runtime to execute that solution plus files that Pega Robot Manager and Pega Synchronization Server use to ensure that the files are safe.
The CommonConfig.xml configuration file contains information necessary to connect to and work with systems that are external to Pega Robot Studio and Pega Robot Runtime (such as Pega Robot Manager). This file is copied to your computer when Pega Robot Studio and Pega Robot Runtime are first installed.
The deployment level denotes the various stages a Pega Robot Studio solution goes through as it moves from development to production. The first and last stages, Development and Production, are built into the system for you. You can define any intermediary stages you need, such as stages for testing and staging.
An execution context represents a single run of a Pega Robot Studio automation. Each execution context is started with an event, such as a button click. Any links started as a result of a button click are part of the same context. If an automation calls another automation, the links executed in the second automation are part of the same context. Any child threads that are created are also part of the same context.
To Pega Robot Manager, inheritance is applicable when making package assignments. For example, inheritance means that when you are placed in a department, you will inherit the package assignments and configuration settings made for that department. Conversely, if you leave that department, you would disinherit those assignments.
The Interaction Manager component connects customer interactions through the configuration of its properties, events, and methods. The Interaction Manager maintains a direct link to the contents of the interaction.xml file and stores the context values defined for each interaction.
In Pega Robotic Automation Agile Desktop an interaction is a session with a customer. For example, the session could be a phone call or a chat. An interaction is sometimes called a transaction.
The interaction.xml file defines the contexts, activities, and plug-ins that comprise the implementation that you are designing.
A native control is a control in the application that you are automating.
A package is a deployable solution ready to be used by Pega Robot Runtime. A deployment package comprises two files, with these extensions: .openspan and .manifest. The .openspan file contains the specific adapter, translators, and custom components that make up the solution. The .manifest file contains a list of the contents of the .openspan file, along with project version information.
Pega Robot Manager helps you configure, manage, and deploy these automations, bundled into projects, from a centralized, cloud-based portal. Pega Robot Manager sits on top of the Pega Platform / Server.
Pega Studio bundles functionality in projects. Project iRobot tems let you integrate applications, monitor events, and automate tasks. Adapters, automations, and global containers are stored as .os files in the solution and project folders.
The RuntimeConfig.xml file contains the configuration settings primarily used by Pega Robot Runtime. Pega Robot Runtime is installed as a stand-alone application and also with a Pega Robot Studio installation.
Runtime-only users only use Pega Robot Runtime and do not use other Pega Robotic Automation products like Pega Robot Studio.
Within Pega Robot Studio, solutions and projects are containers for all of the items required to build and run the project. Solutions can include multiple projects. Once you deploy a solution to the Pega Robot Manager, it is known as a package.
The StudioConfig.xml file contains the configuration settings for Pega Robot Studio.
A target is an object created in the adapter control that represents a native control in the application that you are automating. There are many types of targets and each target represents a specific type of control. So a GridTarget knows how to get cell values, set cell values, and so on. A ListBoxTarget provides a count of items and returns the items as a list.
Translators are Pega Robotic Automation objects that are injected into the adapter application and operate directly against the native control. Translators are designed to operate against a specific type of control. For instance the .NET DataGrid translator works against System.Windows.Forms.DataGrid or any objects that inherit from DataGrid.
UI Connectors are C# classes that are created and compiled into your Pega Robot Studio project. UI Connectors contain the logic for mapping the target implementation to the native control. The adapter control communicates with the UI Connector and the UI Connector uses the target to make reflective calls to the native control.