Deploy robots

  1. When you are done creating robots with trigger events, open the Desktop Automation Service configuration on the remote device and perform the following.

    • Clear the Single User option and specify the Management Console where the robots will be deployed.

    • Open the Windows tab and select Lock package.

      The Lock package setting is necessary for trigger robots to run in production.

  2. Upload the robots to the Management Console by right-clicking the robots in the Projects view and clicking Upload.

  3. Open the Management Console and go to Repository > Robots.

    The Management Console provides a list of uploaded robots in the repository with the corresponding triggers.

  4. Go to Repository > Device Mappings and click Create a device mapping. Specify the same device mapping name used while building your robot.

    For more information, see Device mappings.

  5. Go to Repository > Trigger Mappings and select one of the following tabs.

    • To create a trigger-user mapping, select the Users tab.

    • To create a trigger-label mapping, select the Labels tab.

  6. After selecting a tab, click the plus sign to create a new trigger mapping.

    For more information, see Trigger mappings.

    Once trigger mappings are created, the running Desktop Automation Services start monitoring for any triggers executed by the mapped users and initiating the relevant robots when intercepted.

  7. If you want to tie the trigger to an individual user account on a desktop running Desktop Automation Service, select the attended automation robot and a user.

Before running robots with trigger events on the Management Console, switch off the Single User Mode in the Desktop Automation Service configuration and restart for the changes to take effect. This allows the Desktop Automation Service to communicate with the Management Console and monitor for triggers on the desktop.