Edit workload management automations

You can edit a workload management (WLM) automation (in use queue) and update processing time, run-as users, and device pool details.

Prerequisites

You must have the following roles and permissions to edit the workload management automation (in use queue):
Feature type Privileges
Activity permissions Provide the following permissions for all bots and its dependencies:
  • View my in progress activity
  • View my scheduled bots
  • Schedule my bots to run
  • View ALL scheduled activity from my Folders
  • Manage ALL scheduled activity from my Folders
  • Schedule permission at the folder level.
Note: The bot must be linked to the same work item structure as the queue.
User role Your custom role must have the following:
  • Consumer access to the queue you want to process
  • Consumer access to the device pool on which you want to process the queue
  • Run as user assigned to the role

When you select the View and manage automation option for the In use queues, you can edit a paused or active automation to update details.

When you edit a workload management automation:
  • You cannot edit the Bot and dependencies, Queue, Run history, and General details.
  • The automation ID does not change.
  • You can edit any paused or active automation.

Procedure

  1. Log in as administrator to the Control Room.
  2. Navigate to Manage > Queues.
  3. Hover over or click the three dots icon next to the queue that is in the In use status and click View and manage automation.
    The queue details are displayed.
  4. Click Edit to update the following details:
    1. Processing time: To change the running time, days, and time slots for the selected queue.
      To add a running time, perform the following steps:
      1. Click the Add running time button.

        A Running time 1 section appears.

      2. Click the Time zone drop-down menu to specify the time zone for automation execution.
      3. Use the Days of the week field to select the specific days to run the automation.

        For example, if you want to run this specific automation only on alternate days starting from the first day of the week, select Monday, Wednesday and Friday.

      4. Use the Start time field to enter or select a start time for the automation.
      5. Use the End time field to enter or select an end time.
      6. Click Add time button to add another a different Start time and End time.

        If you have added more than one additional times for the automation execution, click Remove time to delete the any additional items.

      7. If you have added multiple running times, click Remove running time button to delete the specific item.
      8. Click Save.
      Note: Ensure that you do not choose overlapping time slots for Start time and End time.

      For example, if you add one Start time as 1 pm and End time as 3 pm, then add another Start time as 2 pm and End time as 4pm; an error is displayed.

    2. Run as: Select or update the Bot Runner devices for the selected queue.
      Note: If you select the Run on bot running devices option, you must include all the run-as users' default devices in the same device pool (which will be available to select on the Device pools page).
    3. Device pool: Select or update the device pool for the selected queue.
      Note:
      • The workload management automation is processed based on the order of the automation queue. If the device pool has priority-based deployment, then the automation will be processed at the end of the priority.
      • If you do not change the device pool, then the order of the automation queue does not impact the automation deployment.
  5. Click Save.
    The existing automation is stopped and automation details are updated immediately.
    Note:
    • When you stop the existing automation, it does not impact bots which have been deployed on the Bot Runners.
    • When you edit the automation, the audit log entries are recorded on the Administration > Audit log page with the Update automation event type. You can view the old and new automation values in the audit log entries.
    • During the execution of the WLM automation, bots are not deployed when Bot Runners are mapped one-on-one with their default (single user) devices with Run on bot running devices option selected and one or more devices in the selected device pool is disconnected.