Skip to main content


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

Testing configurations for the Pega Robotic Automation Importer component 8.2

Updated on September 3, 2019

To verify that your settings for the Pega Robotic Automation Importer component are correct, test your end-to-end configuration.

Before you begin

Configure Pega Robot Studio. For more information, see Configuring Pega Robot Studio for the Pega Robotic Automation Importer component.

Testing your connection

  1. Log in to Pega Robot Studio.

    Use credentials with an access group that points to the Pega application to which you want to publish your automations.

    The credentials must have the pxPostPackageMetadata privilege that is required for package publishing. This privilege is included in the PegaRoboticAutomationImporter:PackagePublisher role, which is provided by default with the Pega Robotic Automation Importer component.

  2. In Pega Robot Studio, open a project that you want to test.
  3. In the toolbar, click the Deploy Project button.
  4. In the Project Deployment dialog box, enter a descriptive comment about the current version of the automation package, and then click OK.
  5. In the header of Dev Studio in your Pega Platform development environment, click the name of your application, and then click Definition.
  6. Verify that the new Package component is in your application design-time stack.

For more information, see Pega Robotic Automation Importer component.

  • Previous topic Configuring Pega Robot Studio for the Pega Robotic Automation Importer component 8.2
  • Next topic Pega Robot Manager authentication mechanisms

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