Events Overview

The Event Broker listens for incoming events from clients, determines the name of the event, forwards the event to the configured event handler, and, if required, returns a response to the event. Event messages contain enough basic information to be handled without the need to retrieve additional data from APIs.

The events that are exposed to the Event Broker can be consumed in custom code (for example, C# event handlers) or workflows that automate tasks and enable data to be exchanged between systems.

Anthology events are grouped in the categories depicted below. 

• Saving events and Deleting events are captured and visible at the UI level. VB .NET code is required to intercept these events. Data validation occurs. Saving and Deleting event workflows must be stored on the host that is running the application on which the event is captured, for example, Anthology Student.

• Saved events and Deleted events are captured at the database trigger level. These events are only visible in the event log of the Windows Service NextGen Nexus Event Workflows. Saved and Deleted event workflows must be stored on a host that has a direct database connection, for example, COM Server.

• Constructed events are captured and visible at the UI level when the components of a record are assembled. No data validation occurs. VB .NET code is required to intercept these events.

The available event categories depend on the entities. For example, the Person entity in Anthology CRM is associated with Constructed, Saving, and Saved events, while the Student Enrollment Period entity in Anthology Student is associated only with Saved and Deleted events.

Forms Builder events fall into a different category. These events are triggered whenever the Raise Event rule is encountered in a sequence.

Note: The initial Workflow and Eventing versions support Saved events and Saving events for CampusNexus CRM and Anthology Student and the Raise Event rule for Forms Builder.

Workflow Composer enables you to intercept the events and create activities that are triggered by the events. Activities in a workflow can be triggered by Saved and Saving events.

Events published to the Event Broker are application-specific, that is, a distinct set of events is available for Anthology Student (see SIS Events), another set of events is available for CampusNexus CRM, another set for Forms Builder, and so on. Contracts define the messages that will be exchanged between the applications.