Pega Robotic Automation glossary
This glossary defines terms used inPega Robotic Automation.
| Term | Definition |
| applications | A Windows or web software program that you can add to a project in Pega Robot Studio and use to match controls in an automation. Formerly known as adapter. |
| attended automations | An attended automation requires manual supervision. For example, an automation might launch and log into all the applications that users needs to start their day. During processing, the automation requires users to accept a security banner and enter a single set of credentials. |
| automations | The automated processes that you create in Pega Robot Studio to perform tasks and follow workflows. |
| bundle | When you opt to build a solution in Pega Robot Studio, the system creates a bundle that includes all the files that Pega Robot Runtime needs to execute that solution, plus files that Pega Robot Manager and Pega Synchronization Server use to ensure that the files are safe. |
| CommonConfig.xml file | The CommonConfig.xml configuration file contains
information that is 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 Robot Studio and
Robot Runtime are first installed. |
| deployment level | The deployment level denotes the various stages that 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. |
| execution context | An execution context represents a single run of a Pega Robot Studio automation. Each execution context starts with an event, such as a button click. Any links that you start as a result of a button click are part of the same context. If an automation calls another automation, the links that are executed in the second automation are part of the same context. Any child threads that are created are also part of the same context. |
| forms | Standard Windows forms for communicating or interacting with the users of the solution. |
| inheritance | To Pega Robot Manager, inheritance is applicable when making package assignments. For example, inheritance means that when you are placed in a department, you inherit the package assignments and configuration settings made for that department. Conversely, if you leave that department, the systems disinherit you from those assignments. |
| Interaction Manager | The Interaction Manager component connects
customer interactions through the configuration of its properties,
methods, and events. The Interaction Manager
maintains a direct link to the contents of the
interaction.xml file and stores the context
values that are defined for each interaction. |
| interactions | 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. |
| Interaction.xml file | The interaction.xml file defines the contexts,
activities, and plug-ins that comprise the implementation that you are
designing. |
| native control | A native control is a control in the application that you are automating. |
| package | A package is a deployable solution ready to be used by Pega Robot Runtime. A deployment package comprises two files,
with these extensions: .pega and
.manifest. The .pega 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.pega file, along with
project version information. |
| Pega Robot Manager | Pega Robot Manager helps you configure, manage, and deploy your automations, which are bundled into projects, from a centralized, cloud-based portal. Pega Robot Manager sits on top of the Pega Platform Server. |
| PegaRuntimeConfig.xml | The PegaRuntimeConfig.xml file contains the
primary configuration settings that Pega Robot Studio uses.
Pega Robot Runtime is installed as a stand-alone application
and also with a Pega Robot Studio installation. |
| PegaStudioConfig.xml | The PegaStudioConfig.xml file contains the
configuration settings for Pega Robot Studio. |
| project | Pega Robot Studio bundles functionality in projects. With project items, you can integrate applications, monitor events, and automate tasks. The solution and project folders store the applications, automations, and global containers. |
| Runtime-only users | Runtime-only users use Pega Robot Runtime and do not use other Pega Robotic Automation products like Pega Robot Studio or Pega Robot Manager. |
| solution | 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 becomes a package. |
| target | A target is an object that is created in the automation that represents a native control in the application that you are automating. There are many types of targets. Each target represents a specific type of control. For example, a GridTarget can retrieve cell values or set cell values. A ListBoxTarget provides a count of items and returns the items as a list. |
| translator | Translators are Robot Studio 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 Microsoft .NET
DataGrid translator works against
System.Windows.Forms.DataGrid or any objects
that it inherits from DataGrid. |
| UI Connector | 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. |
| Unattended automation | An unattended automation can run in the background on a server without supervision. For example, when an automobile insurance claim is submitted, an automation can analyze the submitted information, look up and verify policy holder information, and then update web, cloud, or on-premise applications with the new information. Unattended automations optimize system resources and reduce peak loads, often by queuing updates for off-hours. |
Previous topic Ensuring that the connection is trusted