Runtime configuration files
With Pega Robot Manager, you can manage all configuration files of Pega Robot Runtime from the Robot Manager portal. For example, the ability to control the configuration of your robots remotely from a centralized location:
- Allows the robot to download updates at startup.
- Simplifies how you can provide updates for attended and unattended robots.
- Allows you to specify general application settings for both testing and production environments.
Remote configuration management is also helpful in testing; in this case, you can enable debugging traces within the configuration file to understand issues with a single machine without direct access.
As various parts of your organization use robots differently, you can assign a specific Runtime configuration file to a department, a work group, a user, or a robot. After you set a Runtime configuration file, the Runtime system deploys the file when it starts. The Runtime configuration file manages the settings shown in the following table:
| Icon | Description |
|---|---|
|
|
Configuring general Pega Robotic Automation features |
 |
General log file categories |
 |
General run-time application settings |
 |
Enabling and defining what type of diagnostic information to record |
Note: After Pega Robot Runtime connects to Robot Manager, the system uses the Runtime configuration file assigned through Robot Manager.
Runtime configuration file inheritance
When you create a new Robot Manager application, the master Runtime configuration file version becomes the default Runtime configuration file. Robot Manager allows you to use multiple Runtime configuration files within one application scope. When a robot connects to Robot Manager, the system decides which Runtime configuration file to apply by using the following criteria:
|
Unattended |
Attended |
|---|---|
|
Direct assignment to the robot |
Direct assignment to the user |
|
Direct assignment to the work group |
Direct assignment to immediate parent department |
|
Default assignment to the robot’s application |
Assignment to a department higher in the hierarchy, until the top-level department is reached |
|
Master configuration file |
Default assignment to the user’s application |
|
|
Master configuration file |
Note: The Runtime configuration file assignment occurs in order of precedence. If a condition is true, the system ignores all other criteria.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?