Skip to main content

Robot Activities in Pega Robot Studio

Pega Platform™ cases require a Robot Activity component to invoke an automation. The Robot Activity component is the connection point between Pega Platform and the automation. You can use the component to invoke the following:

  • Attended automations – Automations invoked from a Pega Platform application, run in a local browser, and use the Pega Constellation Messaging service to communicate between a Pega Platform application and Pega Robot Runtime​™.
  • Unattended automations – Automations invoked from Pega Robot Manager™ that communicate across a network with the local Pega Robot Runtime clients.

To access this component, you drag and drop the toolbox component to the automation designer window.

robot activity in the Toolbox

Each automation that is called by a case must contain a Robot Activity component.

In the following image, click the + icons to learn more about each section of the Robot Activity component.

Note: As a best practice, name the robot activity component similar to the activity name and automation name. Use this ActivityName in Pega Platform to identify the automation that you are using in the case.
post processing automation
  • When clicking the ellipses on the Fields property, Pega Robot Studio prompts the user for the following Pega Platform connection settings default to the value provided during installation and stored the StudioConfig.xml:
    • The URL location of the Pega Platform application.
    • The user name and password with proper access to the ClassName that retrieves the relevant records.

Any updates to the connection settings persist for future use.

pega server connectivity popup

Component usage

The Robot Activity component contains the ActivityStarted event. The ActivityStarted event begins when a Pega Platform application flow invokes an automation with the corresponding ActivityName. You can access an activity’s properties only when the activity is active — from the start of the ActivityStarted event until its completion. The following image shows the automation identifier in the Pega Platform post-processing action and the corresponding automation that contains the ActivityStarted event.

Example automation using robot activity design blocks

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.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice