Remote integration in Pega Robot Manager
Remote integration is about using Pega Robot Manager™ to complete Robotic Process Automation (RPA) tasks while running primary cases on a separate server.
To accomplish this, you define or assign remote queues to perform RPA tasks in Robot Manager while monitoring your Case, running on a different system. For example, customers require external systems to run credit or insurance policy checks. These external processes are generic and can be reused across many different applications and departments throughout your business.
In this example, a Robot Manager application containing these processes, as defined by different departments and applications, can complete assignments by using the Case Types from which they require the tasks, such as Credit check or Policy check. You can then declare the Case work queue, also known as an assignment type in Robot Manager, as being remote, and define the input and output parameters required for it to run. Once you configure the assignment type as remote, the case management systems can use it to finish tasks.
As an administrator, you can create a new work queue for the Case Type (the corresponding assignment type), or set an existing one as remote. Using remote queues in Robot Manager enables you to finish RPA tasks across different systems and also provides the following benefits:
- reduced operational costs and complexities,
- increased efficiencies across your enterprise.
In Robot Manager, you can generate a new remote assignment type when adding a new remote robot queue. This results in a templated Case Type with one robot automation step, as shown in the following figure:
In Pega Platform™, update the smart shape in the case life cycle to be an alternative approach to setting remote access for a work queue, as shown in the following figure:
Remote Queues in Cases
When setting up remote integration, you can use templated Case Types in Robot Manager to generate new remote robotic assignments, or use App Studio to modify an existing assignment type and define it as a remote robot queue.
When adding a new Assign to robot queue step to an existing Case for remote access, you must consider whether any previous steps in the Case Type can prevent it from reaching the Assign to robot queue step without user intervention. The following image shows the multiple steps that you must complete before the credit check automation runs. Without considering the possible blocks to the previous steps, the process could not reach the assignment step, which results in blocking the request for an assignment.
You should adhere to a particular workflow if a primary Case includes a robotic automation step that routes to a robot queue on the Robot Manager server. For more information on the steps for a robot queue running remote cases in Robot Manager, see Remote Integration.
In addition to following the best practices workflow for running cases that include remote queues, additional steps are necessary for setup and access. For more information on setting up remote queues, see the information in the following links:
- Setting up Remote integration
- Enabling and disabling robot remote queues
- Modifying routing to remote robot queues
- Accessing remote robot queues from Pega Case Management system
Check your knowledge with the following interaction:
This Topic is available in the following Modules:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?