Skip to main content

Overriding work groups in unattended (RPA) implementations

Suggest edit Updated on December 14, 2021

To override the default work group when Pega Robot Runtime starts in an unattended (RPA) implementation, include the Workgroup= parameter in the command that you use to start Pega Robot Runtime.

These instructions are only valid if you are using Pega Robot Manager version 5 or earlier. You must also have Robotic Automation Runtime version 8.0.1058 or later to use the Workgroup= parameter on the command line.

In an unattended (RPA) implementation, you typically use the workgroup setting in the CommonConfig.xml file to specify the work group to which this robot belongs. This in turn tells Pega Robot Manager which package (or project) this robot should run. Include the Workgroup= parameter in the command that starts Pega Robot Runtime to override the value in the CommonConfig.xml file and specify a different work group for this Robotic Process Automation (RPA) robot.

To override the work group, perform the following steps:

  1. Open a command prompt window.
  2. At the command prompt, enter the command to start Pega Robot Runtime and include the Workgroup= parameter.

The following example shows the syntax for version 19.1 and later:

C:\{path to synch engine install}\Pega.Loader.exe --args Workgroup="work group name"

The following example shows the syntax for version 8.0 SP1:

(program executable path) Workgroup="work group name"

Include the quotation marks ("). For example, to specify a work group named Customer service, enter the following on the command line:

C:\{path to synch engine install}\Pega.Loader.exe --args Workgroup="Customer service"

For more information about the CommonConfig.xml file, see Common Configuration Settings.

Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

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