Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring Pega Robot Studio for the Pega Robotic Automation Importer component 8.3.1

Updated on September 10, 2021

Before you publish an automation package to your Pega Platform development environment, configure Pega Robot Studio.

Note: This functionality requires Pega Robot Studio 19.1.7 or later.

Before you begin

Configure access to an automation repository. For more information, see Configuring access to an automation repository.

Configuring Pega Robot Studio

  1. Navigate to Program Data\Pegasystems, and then open the CommonConfig.xml file in a text editor.
  2. Update the PegaDevServer section with the URL of your Pega Platform development server.

    The default Pega Platform address is https://<hostname>:<port>/prweb.

  3. Save the CommonConfig.xml file and close the text editor. This change takes effect when you start Pega Robot Studio.

Result: You can now publish automation packages from Pega Robot Studio to a Pega Platform development environment. The rules and data records that you generate are relayed to a Pega server that hosts the Robot Manager.

What to do next

Test your configurations. For more information, see Testing configurations for the Pega Robotic Automation Importer component.

  • Previous topic Configuring the Pega Robot Manager host server and authentication profile 8.3.1
  • Next topic Testing configurations for the Pega Robotic Automation Importer component 8.3.1

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us