Adapters overview
Overview of adapters
Pega Robot Studio™ uses adapters to integrate and interact with systems. Communication between applications is difficult when applications are separate. Companies can improve workflow by using adapters to integrate applications to interact with one another.
Companies can create custom APIs to communicate between applications; however, maintaining custom APIs is time-consuming and challenging with application updates. Pega Robot Studio provides specific adapters that allow developer access to the workflow process without the need for custom APIs or when Pega Platform™ cannot handle the communication and integration between applications.
Pega Robot Studio integrates with various types of applications such as Windows applications, web applications, and emulator applications. Pega Robot Studio provides specific adapters for the different applications that allow a developer to access the application to assist in the workflow process.
An adapter is a class that encapsulates the data in an application and permits automation to monitor and modify how the application works. Adapters have accessible properties, methods, and events that launch, monitor, and expose enterprise applications for automation. Pega Robot Studio does not require the target application to be recompiled or modified.
Common adapters
Common adapters are Windows, Web, and Universal Web adapters. While adapters share some common properties, there are specific properties that allow the developer to mimic how a user interacts with the application. These settings provide Pega Robot Studio with powerful options that other solutions (API, workflow changes, and so on) cannot always offer easily and quickly.
For example:
Adapter Type | Applications |
---|---|
Windows | Windows applications, including Java applications and SAP GUI |
Web | Web-based applications that run on Internet Explorer |
Universal Web | Web-based applications that use Google Chrome and Mozilla Firefox |
Text Adapter | Host-based or mainframe applications accessed through an emulator |
When deciding which adapter to add based on the application, you must consider the type of environment in which the application is accessed, such as a training, testing, or production environment. Understanding the accessed environment provides the developer with the necessary information to configure the adapter. The configuration and properties of the adapter adhere to development and production requirements in the project documentation.
This Topic is available in the following Module:
- Adapters v1
Want to help us improve this content?