What is an Event?

Events are triggered by settings in CM4D. For example, that a CM4D managed document contains a table, and the cells of that table are configured to turn red if the data in a DataSet is out of tolerance. Also, in the same managed document, the Event Properties have been set up so that when the data in the DataSet is out of tolerance, an event happens. At the time that CM4D changes the color of the cells of the table, it also sends information about the event to EventSmith, and EventSmith sends it by email to any users who have subscribed to that event.

How Does EventSmith Work?

Users subscribe to the events they want to be notified of in EventSmith. When CM4D generates events, the events are placed in the Event Queue. The Event Queue is checked by the EventSmith Service. If the EventSmith Service finds events in the Event Queue it processes them, and sends notifications to users who are subscribed to the events. EventSmith then clears events which have been processed from the Event Queue, and records them in the Event Log.

 

EventSmith—Receive Email Notifications when Data Triggers User-Defined Alarms

When a Report is generated by CM4D Scheduler, a defined condition may be triggered on the data in that Report. EventSmith will then notify the person who needs to know about it via email.

Users who subscribe to the data condition that was triggered will receive an email telling them what data was triggered and why.

What these notification emails contain and how they appear can all be defined by an Event designer at the time the system is set up. There are many pre-defined Events as well as a very large variety of custom options for what data conditions can trigger an Event, but the most commonly used conditions are:

„  Data is Out of Tolerance

„  Data is Out of Control

„  New Data Was Processed

So for example, if data in a Report is not within 70% of the upper and lower Tolerance band, the user who has signed up for (subscribed to) that Event in EventSmith will get an email containing information about the data that is outside their Out of Tolerance specification. With this information, the user can then respond promptly to the situation as needed.