Triggered Events Log

As of version 3.8, the Patron and Item Triggered Events Logs have been reimplemented in Angular as well as given improvements in query efficiency.

The Patron Triggered Events Log provides an interface where library staff can view and sort triggered events and notifications associated with circulations and holds on a patron’s account. This feature is often used to identify if a notice, such as an overdue notice, was generated by Evergreen for a patron. Entries remain in the Triggered Events Log for a time period established in the Trigger Event Definition field Retention Interval.

The Triggered Events Log can be accessed by retrieving a patron record and selecting Other → Triggered Events / Notifications. As of 3.8, this interface will open in a new browser tab. Future developments for Evergreen may include integration with the existing patron account interface. In order to view the Triggered Events Log, a staff member will need the VIEW_TRIGGER_EVENT permission either directly or by a group or profile membership.

The Patron Triggered Events Log separates Hold Events and Circulation Events into their own tabs.

The Circulation tab will display events such as predue notices, overdue notices, and autorenewal notices, as well as events like Mark Item Lost or Mark Item Long Overdue. The Hold tab will display events such as hold notifications and curbside pickup offers. Both email and text/SMS notification events that are generated by Evergreen will display in this interface.

There are two available actions, Cancel Selected Events and Reset Selected Events. Cancel will set an event to invalid and Reset will set an event back to pending. Cancel does not check the current event state so staff should use caution when using this action.

More information about the Notifications/Actions Triggers feature in Evergreen, which generates patron notices, can be found here.

When retrieved from a patron record, the Triggered Event Log interface shows only patron-related events, and only specific events that have been scheduled or executed.

Filtering and sorting are available in the column headers. Filtering is case-sensitive, and more information about how column filters work is available here.

This interface displays the following columns for Circulation & Hold Events. The default columns for display are note in italics:

The Item Triggered Events Log displays the same information as the Patron Triggered Events Log, but from the perspective of a specific item. In order to view the Triggered Events Log, a staff member will need the VIEW_TRIGGER_EVENT permission either directly or by a group or profile membership. Entries remain in the Triggered Events Log for a time period established in the Trigger Event Definition field Retention Interval.

The Triggered Events Log can be accessed from the Item Status interface (or any access point that invokes this interface). With a single item selected in Item Status, navigate to Detail View and then select the Triggered Events tab. This will open the rewritten Triggered Events Log in a new browser tab. Alternatively, from either the Item Status List View or Detail View, navigate to the Actions Menu and select Show Triggered Events.

The rewritten Triggered Events Log separates Hold Events and Circulation Events into their own tabs.

Circulation Events include predue notices, overdue notices, and autorenewal notices as well as events like Mark Item Lost or Mark Item Long Overdue. Hold Events include hold notifications and curbside pickup offers. Circ and Holds notices can be sent via SMS or Email.

There are two available actions, Cancel Selected Events and Reset Selected Events. Cancel will set an event to invalid and Reset will set an event back to pending. Cancel does not check the current event state so staff should use caution when using this action.

A full list of Events, including lists of Hooks, Reactors, and Validators can be seen in the Admin interface Notifications / Action Triggers. More information about Events can be seen here.

Filtering and sorting are available in the column headers. Filtering is case-sensitive, and more information about how column filters work is available here.

Columns for Circulation & Hold Events (default columns in italics):