Call / Notify / Record

The Call / Notify / Record action triggers a Service Event, an instance of a user-defined Internal Event Type](....\SendingNotifications\InternalEvent.html in the account. An Event Type serves as a container for 3 types of actions, a call to a sub routine, a notification or data flow and can contain a number of fields; when the system triggers an instance of an Event Type:

• Call- Triggers a sub routine and passes teh variables defined into that sub routine
• Notify- Sends out all notifications contained within that type.
• Record- Initiates a data flow action, sending message data to an alternate storage location of the customers choosing

A user must select one of the event types defined for this account; if none are defined, the user cannot create an action.

The notifications contained within the selected event type can often include the fields of the event type within their messages, and the values of these fields can be set by the Call \ Notify \ Record action. By using this action in conjunction with "If, Then, Else" statements, routines can send out notifications only when certain conditions are met and populate those notifications with information about those conditions.

For example, if a Routine determines that the temperature value in a newly-received device message is too high, it could trigger a Notify action for the "Alarm" event type, setting the "Alarm Type" field to "Temperature Too High". Elsewhere, if the routine determines that the temperature value is too low, it could trigger a separate Notify action and set the "Alarm Type" field to "Temperature Too Low". The "Alarm" event type could include an email notification containing a subject line of "${alarm_type}", and all recipients of the notification would receive an email titled "Temperature Too High" or "Temperature Too Low" whenever a device reported a high or low temperature, respectively.