Skip to main content

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

Managing robot configuration remotely

Updated on October 7, 2021

Deliver robot configuration updates to multiple machines at once by modifying Pega Robot Runtime configuration files in Pega Robot Manager.

The ability to remotely manage the configuration of your robotic workforce from a centralized location simplifies the provisioning of updates and patches for both attended and unattended robots. Depending on your needs, you can use Robot Manager to manage Runtime configuration for an entire organization, department, unit, or individual robot machines.

Runtime configurations are sourced from xml files that enable robot administrators to control various aspects of your robotic workforce's behavior, for example:

  • Configuring general Pega Robotic Automation features.
  • Enabling diagnostics and determining what type of diagnostic information to record.
  • Defining logging categories and determining which events to record.
  • Specifying general application settings, for example, what project should be loaded automatically when Pega Robot Runtime starts.

As various parts of your organization star to use robots differently, you can assign a specific Runtime configuration file to a department, work group, user, or robot. After you assign a Runtime configuration file, the file is immediately deployed when the Runtime system starts.

The mechanism of assigning customized Runtime configuration files to various entities in your organization facilitates troubleshooting. For example, you can enable debugging traces to understand issues with a single machine without requiring access to the machine or having to instruct the operator how to extract the troubleshooting information.

Learn more about the management of Runtime configuration files by reading the following articles:

  • Configuration file inheritance

    You can create multiple Runtime configuration files within the scope of a single application. When you create a new configuration file, the system decides which Runtime configuration file to apply by using a set of inheritance criteria.

  • Creating configuration files in Pega Robot Manager

    Create a new Runtime configuration file version by copying an existing file. For example, you can create settings that are specific to a single robot, a work group, or an entire application.

  • Updating robot settings

    Use the XML-aware editor in Robot Manager to quickly and conveniently adjust Runtime configuration files to your business needs.

  • Assigning configuration files

    Assign Runtime configuration files to different departments, users, work groups, or robots, depending on the different types of tasks that your robotic workforce performs, or the various configuration variations across your organization.

  • Updating configuration file assignments

    Adjust a direct or inherited Runtime configuration file association for a work group, department, user, or a robot.

  • Restoring previous configuration file versions

    You can trace the changes that you made to a Runtime configuration file and revert to an earlier version if necessary.

  • Updating configuration files locally

    Edit robot settings in your preferred third-party XML editor or reuse robot configurations in a different application context by downloading, modifying, and re-uploading the Runtime configuration files.

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

Close Deprecation Notice
Contact us