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:
|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:
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:
Verify that the following Java processes are running to confirm that the triggers are active:
- 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.
Optional: To confirm that java.exe or javaw.exe are associated with a node manager or trigger listener, respectively:
- Bot agent or node manager Note: The name for this is java.exe
- Trigger listener Note: The name for this is javaw.exe
- Copy the details of this task
Press CTRL+C after you clicked the task name.
- Paste the details to a notepad.
- Verify the jar files. Note: Node manager is node-manager.jar and the trigger listener is triggerlistener.jar
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 in order to activate the associated triggers.