Automation invocation for Pega Platform

A Flow Action in a Case Type calls attended Automations to run before or after completing a task. In Pega Platform, a Flow Action defines how users interact with forms to complete assignments. The following figure shows a Flow Action within a flow for a case where a Pega Platform application uses an automation to requests a user’s information:

The Flow Action can specify whether the Automation runs as a:

• Pre-processing event: Retrieves required data from applications to display to a user for completing the Step
• Post-processing events: Adds, updates, or removes data in applications after an end user completes the Step.

For more information about how pre-processing and post-processing actions work in Pega Platform, see Flow Action integration.

The following image shows possible pre-processing and post-processing actions for a Flow Action:

Flow Actions defined on Data Types in all Pega Platform applications, can trigger Automations alongside pre-processing and post-processing events. To integrate attended robotic Automations in Constellation applications, ensure you have the minimum release of Pega Platform release 25.1, the design system, and the latest version of Pega Attended RPA™. For more information, see Configuring attended automations on Pega Platform. 

Use a robot queue in a Case workflow to invoke an unattended Automation. When a Case workflow assigns work to a robot queue, one or more robots that subscribe to the queue perform tasks by polling for work at regular intervals:

The robot runs through the following process:

1. Retrieves the Assignment from the queue.
2. Obtains the Case data associated with the assignment.
3. Performs the specified Automation Task.
4. Sends the updated data, the assignment, or confirmation back to the Sase.
5. Retrieves the next Assignment to process.

The following figure shows a Case that contains a robot queue Step in the second Stage:

The Process credit report step assigns work to a designated robotic Work Queue in Pega Robot Manager and specifies the automation that does the work. In the Case Step, you specify the appropriate Work Queue in the Route to queue field, and in the Run robotic automation field, you enter the Automation name.

Data Pages source on-demand data for Pega Platform applications. A Data Page can call attended Automations that run locally or unattended Automations through a robot queue. For example, you can configure an Automation to pull the customer's FICO score from another application, as shown in the following figure. The Automation loads the score onto the Data Page and then populates fields in the Pega Customer Service™ application.

The UI field is based on a property that references the Data_CustomerCreditProfile Data Page. This Data Page sources its information by calling an automation that retrieves a FICO score, as shown in the following figure:

 In the following image, click the + icons to learn more about the configuration necessary for the Data Page in the credit score example: