Events occur either when:
new data is added,
existing data is modified (eg: status of a service ticket is changed) or
periodically at a set time (eg: every Monday morning at 9 AM).
Events can be reused across bots. Depending on the data source some external configuration may be necessary.
An event represents a change to an entity (table). Each event has the following attributes:
- Event type. This attribute indicates the kind of change that triggers the event.
- Condition (optional). If specified, this condition is checked before firing the Action.
- Target data. Indicates which schema would trigger the event, if changed.
- Update event. Indicates the type of schema change that would trigger the event (i.e. additions, updates, deletions, etc.).
In our example, as shown in the image below, the New Event is a “Data Change” event only triggered by additions to the “Employees” table.
Below is an example of a “Schedule” event type. In the case below, where ForEachRowInTable is not enabled, you can select any event except “Data change” as a valid step type in the process. You may want to use this option if your process doesn’t rely on data in any table.
However, if the ForEachRowInTable option is enabled, the option to specify a filter condition appears. Use this option if you want to run a process for each row of data in the table.