Event triggers
- Updated: 2024/02/27
Event triggers
An event trigger is a predefined action that runs an associated bot. All the bots with event triggers are listed under the Event triggers tab.
Available role permissions for event triggers
A Control Room administrator must provide the required permissions to ensure the associated users can access event triggers. The following table lists the available permissions:
Permission | Description |
---|---|
View event triggers | Select this permission if the users can only view the event triggers but not run or delete them. |
Manage event triggers |
The Manage event triggers permission is available only if View event triggers is enabled. Select this permission if the users can:
|
Supported actions
In Automation 360, click to view the table that lists all the available bots with event triggers. The following actions are available for this table.
- Enter a keyword from the BOT PATH in the
Search field to find an event trigger.
For example, if the bot path of an event trigger is Bots\file--created--event--Salesinfo, enter Sales in the Search field to find this event trigger.
- Use the Run with event triggers option to add event triggers.
- User can also delete any associated (active or inactive) event triggers.
- View the trigger status, bot path, user name, role, and modification
details.Optional: On the specific device, to view trigger details:
- Open the tab.
- Right-click on the column in the list of app entries.
- Click Select columns.
- Click Command Line item to enable the column.
To confirm that the triggers are active, verify that the following Java processes are running:- Bot Agent or node manager (name is NodeManager.exe)
- Trigger listener (name is TriggerListener.exe)
Note: When you install or update the Bot Agent, you must add the NodeManager.exe and TriggerListener.exe files to the safe recipients or trusted (allowed) list. You use a trusted list to designate specific files that are pre-approved for access by the Bot Agent.Consider a scenario where triggers are associated with a Bot Runner user who logs off or signs out of a device. This Bot Runner user must log in to the Control Room on that device to activate the associated triggers.