Difference between revisions of "Events"
| Line 14: | Line 14: | ||
An event has four parts: | An event has four parts: | ||
| − | A pre-defined trigger | + | * A pre-defined trigger |
| − | An action | + | * An action |
| − | A set of conditions | + | * A set of conditions |
| − | |||
| − | + | A ''trigger'' is the initiation of an event when the conditions of the event have been satisfied. | |
| + | E.g. Your customer's invoice becomes overdue today (the predefined condition is met, trigging the event) therefore the system will initiate an email (perform an action) to advise the customer that their invoice is overdue. | ||
| − | + | An ''action'' is what the system will do once the condition is met. Each action occurred only one a template has been set up by the Service Provider. The template for an event gives you the ability to customise the action any way you choose. Email events can be plain text, or HTML/CSS based. | |
| − | + | E.g. email, sms, log. | |
| + | ''Conditions'' are the pre-determined status of a dynamic object, or instance, that trigger an event to occur. | ||
| + | E.g. a customer reaches 90% of their usage allocation for a given period. | ||
| − | [[SystemEvents/Templates|Event Templates]] | + | |
| + | |||
| + | [[SystemEvents/Templates|Setting up your Event Templates]] | ||
| + | [[Editing SystemEvents/Actions|Event Actions]] | ||
Revision as of 11:53, 10 July 2014
Introduction to Events
The Emersion Events System is a notifications system. It automates many activities that typically support to Emersion's core features. Examples of how events can be used are:
- Sending the customer their invoice via email.
- Scheduling a report to be sent to a nominated email address.
- Sending a customer a welcome letter.
- SMS a customer when they have reached a given % of their available usage.
Emersion provides a set of default events to you during your implementation. We have events for Wholesale & Retail Service Providers. We also have events
Anatomy of an Event
An event has four parts:
- A pre-defined trigger
- An action
- A set of conditions
A trigger is the initiation of an event when the conditions of the event have been satisfied. E.g. Your customer's invoice becomes overdue today (the predefined condition is met, trigging the event) therefore the system will initiate an email (perform an action) to advise the customer that their invoice is overdue.
An action is what the system will do once the condition is met. Each action occurred only one a template has been set up by the Service Provider. The template for an event gives you the ability to customise the action any way you choose. Email events can be plain text, or HTML/CSS based. E.g. email, sms, log.
Conditions are the pre-determined status of a dynamic object, or instance, that trigger an event to occur. E.g. a customer reaches 90% of their usage allocation for a given period.
