Linking event triggers to a Bot Runner

An Control Room administrator or users with Manage event triggers permission can add event triggers by associating users or roles with a bot. This enables Bot Runner users to trigger the bot when they perform a specified event.

When a user with a Bot Creator license creates a bot and checks it in a repository, the bot is available in the Public workspace. An Control Room administrator or user with Manage event triggers permission and access to that Public workspace can then link an event trigger.

A Bot Runner (attended or unattended) user must log into the Control Room to start the event trigger, and can choose to log out after that event trigger is activated.

Optionally, administrator can also enable the auto-login feature in the Control Room for unattended Bot Runner users.

See Configure auto-login settings.

Note: Among all the triggers, you can associate any trigger only with a user who has a Bot Runner license. Also, for a user with unattended Bot Runner license, if you associate triggers such as Hot key, Interface, or Window, the following conditions apply:
  • The default device must not be in the logged-off or locked state.
  • The user must be logged in to the device to perform the predefined task that can trigger the bot.

Procedure

  1. On the left pane, click Automation.
  2. Click Run bot.
  3. Click Run with event triggers.
  4. Click the right arrow (→) to add your selection.
  5. Click Next.
  6. Select one of the following to link the bot:
    OptionDescription
    Roles Select the custom role you have created.
    Users Select the Bot Runner (attended or unattended) user who is associated with this custom role.
  7. Click Add event triggers.
When the Bot Runner user logs in to Control Room and performs the trigger event, the bot is deployed. The event trigger will continue to work until one of the following changes occur:
  • Associated bot is deleted from the public workspace.
  • The linked Bot Runner user account is deleted.
  • The default device is logged off.
  • The default device enters the sleep or hibernate mode.