You are here: Robotic automations > Configuring Robotic Process Automation > Configuring your environment to register robotic automation virtual machines

Configuring your environment to register robotic virtual machines

Robotic virtual machines (VMs) must first register with the Pega 7 Platform before they can retrieve assignments that are routed to their work queues. A successful registration allows your Pega 7 application to monitor, track, and report on automation activity.

Complete the following steps:

  1. Create the administrative operator.

    2. You must configure an administrative operator whose credentials are used by Pega Robotics Runtime to run the registration process for a VM. You can assign to the administrative operator any access group that points to your application, but the access group must contain the PegaRULES:RoboticAdministrator role, which provides the minimum privileges need to register a VM.

    ClosedComplete the following steps:

    1. Create the operator. For more information about operators, see About Operator ID data instances 

    2. Create an access group for the operator and assign it to the operator. For more information about access groups, see Access Group data instances.

    3. Add the PEGARULES:RoboticAdministrator role to the access group that you created. For more information, see Access Group form Completing the Definition tab.

  2. Configure the work group and work queues.

    3. Each VM registers with a specified work group that contains one or more work queues from which the VMs will obtain assignments. Use work groups to group related case assignments (for example, Billing, Customer Service, or Claims).

    ClosedComplete the following steps:

    1. Create a work group that contains the work queues from which the robots obtain assignments. The work group should be associated with a ruleset in your application stack. For more about work groups information, see About Work Group data instances 

    2. Create a work queue for each robot. For more information about work queues, see About Workbasket data instances .

    3. Configure the work queue to use automated processing.

      ClosedComplete the following steps:

      1. Click the Workbasket tab.

      2. From the Type list, select Robotic.

      3. In the Maximum queue length field, enter the maximum number of assignments that should be in the work queue at any time.

        If the number of queued items exceeds this threshold, the queue turns red on your Pega Robotic Automation Management Console (Robotic Console), indicating that assigned VMs are not keeping pace with the incoming rate of work. You can change this value in the Robotic Console, which is available on Pega Exchange.

      4. In the Maximum automation execution time (seconds) field, enter the amount of time that the VMis expected to take to run the automation that is specified on the assignments in this work queue.

        5. If the VM takes longer to run the automation than this value, the VM turns red in the Robotic Console, indicating that an administrator might need to investigate issues with the VM.

        You can change this value in the Robotic Console.

    4. In the Work group field, enter the work group to which the work queue belongs.

    5. Configure other work queue settings, as appropriate.

    6. Click Save to save the rule form.

  3. Map access groups and work groups.

    4. The system generates an Operator ID record for each VM that registers with the system. Before the Operator ID is generated, the system runs the logic in the pyGetAccessGroupForRobotByWorkGroup decision table to determine which access group to assign to the generated Operator ID record. You can override this decision table in your application to control the access groups and access roles that is assigned to register the VMs.

    ClosedComplete the following steps:

    1. Click Records in the Explorer panel to open the Records Explorer.

    2. Expand Decision and click Decision tree.

    3. Save the decision table to your application ruleset.

    4. Add the work groups and their corresponding access groups in the application. For more information about decision tables, see About Decision Tables.

    5. Click Save to save the rule form.

  4. Configure the heartbeat interval.

    5. Each VM sends a heartbeat, or periodic message, to your Pega 7 application to indicate that the VM is still running and available. The default interval is one heartbeat message every 30 seconds, and you can modify this value.

    ClosedComplete the following steps:

    1. Click Records in the Explorer panel to open the Record Explorer.

    2. Expand SysAdmin and click Dynamic System Settings.

    3. Click Pegarobotics/HeartbeatInterval in the Pega-ProcessEngine ruleset.

    4. In the Settings tab, in the Value field, enter the interval, in seconds, during which each VM sends a heartbeat to the system.

    5. Click Save to save the rule form.

    For more information about dynamic system settings, see Dynamic System Settings data instances.

  5. Add and configure the Route to robotic queue smart shape to your case type. See Configuring the Assign to robot queue shape.
Related information

Open topic with navigation