Skip to main content

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

Configuring the pyGetWorkGroupForRobotByRequestorOperatorID decision table

Updated on November 29, 2022

To map the user credentials to work groups in your application, use the pyGetWorkGroupForRobotByRequestorOperatorID decision table.

For example, if you use Kerberos authentication, your decision table maps the Microsoft Windows user principal name (UPN) from a valid Kerberos ticket to a work group in your system. All robots registered by using these credentials are assigned to the work group specified in the decision table.

With Pega Robot Manager, you can update the pyGetWorkGroupForRobotByRequestorOperatorID decision table through the Pega Robot Manager user interface. For more information, see Changing settings from the Pega Robot Manager interface.

  1. In the navigation panel of Pega Robot Manager, click Records.
  2. Expand the Decision category, and then click Decision Tree.
  3. Click the pyGetWorkGroupForRobotByRequestorOperatorID decision table in the @baseclass class and save it to your application ruleset.
  4. Add the user names and their corresponding work group IDs to the decision table. For example,
    For example: For Kerberos authentication, add the user principal names (UPNs) and their corresponding work groups to the decision table.
    For more information about decision tables, see About Decision tables.
  5. Click Save.
  6. Set the sequence in which the system registers robots (either from within the registration request of a robot or through the decision tables) by editing WorkgroupSpecifiedInPayloadTakesPrecedence dynamic system setting.
  • Previous topic Configuring the pyGetWorkGroupByRobotID decision table
  • Next topic Defining work groups that a robot can move to

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