Using the Trigger Manager

Use the Trigger Manager to display, add, modify, and delete triggers you have set for your tasks.

Over time, you might create several triggers that run various automated tasks. For example, a single task might be run using five different triggers, or a single trigger might run five different tasks. As the number of tasks and triggers grow in number, you will want to organize and manage these triggers.

Using the Trigger Manager, you can:

  • Add a trigger
  • Modify a trigger
  • Delete a trigger
  • Enable a trigger
  • Disable a trigger

To use the Trigger Manager, follow these steps:

  1. In the main Automation Anywhere window, click the Trigger Manager tab on the left side. The Trigger Manager window opens, showing the tasks that are driven by each trigger.
  2. Add additional triggers or work with your existing triggers:
    • To add a new trigger, click the Add option.
    • To edit an existing trigger, click the Edit option.
    • To delete an existing trigger, click the Delete option and click Yes to confirm.
    • To enable a trigger, ensure that the check box in the far left column is selected.
    • To disable a trigger, clear the check box in the far left column.

To enable or disable all triggers at once, select or clear the check box at the top of the Trigger Manager window.

If you find that triggers are not working with a Microsoft Office file that is modified, you have to select When file is renamed from the Action list. The trigger now works correctly. This is the inherent behavior of Microsoft Office.

Note: When using on Windows login, the trigger for scheduled tasks can take some time to start. Wait for the trigger event to launch when you start your machine and use Windows credentials to log in.

If you set the trigger on a text file that is located on a shared path and the text file is modified, the player is triggered multiple times. This is an expected behavior of Microsoft Notepad. For information about how to resolve this, see this article: Modified file is triggered multiple times against a text file located on network drive (A-People login required).