Attended Automation is a new way to automate your remote computers by creating a robot that reacts to an event on a remote device.

After uploading a robot with a trigger to a Management Console, map the robot to users and labels. After that the Management Console provides a list of triggers to the Device Automation Service based on created mappings. When a trigger event is detected on a remote device, the Device Automation Service sends a notification to the Management Console and the robot performs some programmed steps. For example, you can program the robot to insert or extract some data when a certain application is opened. Use the Trigger Choice step to define triggers and actions that start when a certain event is detected.

Don'ts for robots with triggers

• Do not add robots with triggers to schedules and do not start robots with triggers manually. The robot started by schedule or manually will wait forever (or some specified RoboServer timeout), because the trigger is never activated by any remote Device Automation Service.

• Do not add robots with triggers to Kapplets.

Trigger events are used on the automated devices, and therefore you must create device mappings before you can use trigger events. Trigger mappings are used to assign users and labels to robots with trigger events in the Management Console. You can also assign mappings and suspend and activate triggers on the Repository > Robots tab in the Management Console.

When a trigger event is detected, the robot might prevent the user from using the mouse and keyboard. To inform the user of the action performed by the robot, use the Notify step.

If triggers are suspended in the Management Console, the robot is not triggered by the remote Device Automation Service. Note that the refresh of trigger information runs during the connection to a remote device and then every minute. There might be a situation when a trigger is shown as suspended, but is still running in the Management Console. In this case, a trigger event may still be detected.