After you have created a process automation, you can check it into a public workspace, making it accessible to all users assigned to the relevant team or role. To enable parallel branch execution, ensure that Bot Runner users are added to a device pool for seamless process runs.

Complete the following configuration steps before running a process with parallel branches:
Note: Only users with Automation Co-Pilot Business User license can schedule a process from public workspace.
  1. Log in to the Control Room.
  2. User and role setup
    1. Navigate to Administration > Users .
    2. Create a custom user named pooladmin and assign the AAE_Pool Admin system role to the user. This user will manage bot runners, bot creators, and device pools.
    3. Create Bot Runner users. For example, (User 1 and User 2). These users will consume device pool resources.
      Note: When creating User 1 and User 2, enter identical device login credentials (same device username and device password) for both users.
  3. Custom role creation
    1. Create a custom role named Process Runner with permissions on the following features:
      • Activity
      • Bots
      • Devices
      • Automation Co-Pilot Setup
      • Process Composer > Scheduler

      Select all relevant check boxes within each feature permission.

    2. In the Bots tab, select the folders containing the automations you want users to access.
    3. Assign Run and View permissions to these folders for the Process Runner role.
    4. In the Run as section, select the unattended Bot Runner users (User 1 and User 2). This step determines which devices the role can access.
    5. Select user (User 1 and User 2) from the list who will be using this role.
    6. Save the changes.
  4. Device Pool Configuration
    1. Log in as an administrator or a user with the AAE_Pool Admin role.
    2. Create a device pool with a unique name and add the Bot Runner users.
      Note: Ensure you have Create device pools permission to create a device pool.
    3. Select devices associated with the Bot Runner users, ensuring both devices use the same username and password. If device credentials differ, process execution will fail.
    4. Add the Process Runner role as a consumer, allowing User 1 and User 2 to view and use the device pool.
    5. Click Create Device Pool.

How Device Pools enable parallel processing

A device pool contains multiple machines, allowing processes to be deployed to any available device within the pool. When you run a process, the system automatically identifies and utilizes available devices. If the first device is busy, the system moves to the next available device. Parallel branches can therefore execute concurrently across multiple devices in the pool.

If more branches are scheduled than there are available devices, excess branches are queued and executed as soon as resources become available. For example, if a process has three parallel branches but only two devices are available, two branches will run immediately, and the third will be queued until a device is free.