Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Pega Robot Runtime work group provisioning

Work group provisioning

Provisioning is the process of successfully registering an unattended robotic process automation (RPA) robot and assigning it to a work group. The system considers the Dynamic System Setting (DSS) and the robot type to determine a robot's default work group. For each type of robot, two possible processes can occur for work group provisioning: RPA Service-assisted and Stand-alone. The processes below reference the decision tables in Dev Studio. You can modify these decision tables through the robot registration decision mapping in the Pega Robot Manager portal.

    RPA Service-assisted provisioning

    The Pega RPA Service is a Windows service that you can use to monitor and control a robot from the Pega Robot Manager interface. You must install and run the Pega RPA Service on the same machine as Pega Robot Runtime. When an RPA Service-assisted robot starts and registers, the robot is provisioned within the default work group. The robot considers the Dynamic System Setting (DSS) value and any previous work group assignment to determine which of the following two processes is used to provision the work group:

    • If the robot has a previously assigned work group, the last work group association is retained and used. When a robot is reset, it starts working in the work group to which it belonged when it stopped. If a robot is stopped, moved to a new work group, and then restarted, the robot starts in the work group to which it moved.
    • If the robot does not have a previously assigned work group, the DSS determines the order of the robot registration and provisioning of the work group.
      • If the WorkgroupSpecifiedInPayloadTakesPrecedence = False:
        1. Check the pyGetWorkgroupbyRobotId decision table.
        2. If a value is invalid or does not exist in pyGetWorkgroupbyRobotId, check the pyGetWorkGroupForRobotByRequestorOperatorID decision table.
        3. If a value is invalid or does not exist in the pyGetWorkGroupForRobotByRequestorOperatorID decision table, check the CommonConfig.xml file or the Command Line parameter when Pega Robot Runtime starts.
        4. If a value is invalid or does not exist in the CommonConfig.xml or Command Line parameter, provisioning and registration fails.
      • If the WorkgroupSpecifiedInPayloadTakesPrecedence = True:
        1. Check the CommonConfig.xml file or the Command Line parameter when Pega Robot Runtime starts.
        2. If a value is invalid or does not exist in the CommonConfig.xml or Command Line parameter, provisioning and registration fails.
    Note: It is a best practice to use the Pega RPA Service and set WorkgroupSpecifiedInPayloadTakesPrecedence = False for robot registration and work group provisioning.

    Stand-alone robot provisioning

    Stand-alone robot provisioning occurs when an organization does not use the Pega RPA Service.  With stand-alone, there is no communication to Pega Robot Manger for controlling the robots.  When using this approach, administrators need to manually access the robot windows machines to start, stop, terminate, or schedule robots.  The provisioning process used is determined by the DSS value. 

    • If WorkgroupSpecifiedInPayloadTakesPrecedence = TRUE:
      1. Check the CommonConfig.xml file or the Command Line parameter when Pega Robot Runtime starts.
      2. If a value is invalid or does not exist in the CommonConfig.xml file or command line parameter, check the pyGetWorkGroupByRobotID decision table.
      3. If a value is invalid or does not exist in the pyGetWorkGroupByRobotID decision table, check the pyGetWorkGroupForRobotByRequestorOperatorID decision table.
      4. If a value is invalid or does not exist in the pyGetWorkGroupForRobotByRequestorOperatorID decision table, registration and provisioning fails.
    • If WorkgroupSpecifiedInPayloadTakesPrecedence = FALSE: 
      1. Check the pyGetWorkGroupByRobotID decision table.
      2. If a value is invalid or does not exist in the pyGetWorkGroupByRobotID decision table, check the pyGetWorkGroupForRobotByRequestorOperatorID decision table.
      3. If a value is invalid or does not exist the pyGetWorkGroupForRobotByRequestorOperatorID decision table, check the CommonConfig.xml file or the command line parameter. 
      4. If a value is invalid or does not exist in the CommonConfig.xml file or command line parameter, registration and provisioning fails.

    This Topic is available in the following Module:

    If you are having problems with your training, please review the Pega Academy Support FAQs.

    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 Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

    Close Deprecation Notice