|
|
| (9 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | == Introduction to Events == | + | =This Content Has Moved House= |
| | | | |
| − | The Emersion Events System is more than just a notifications system. It automates many activities that typically support to Emersion's core features. Examples of how events can be used are:
| + | This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. |
| | | | |
| − | * Sending the customer their invoice via email.
| + | We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home. |
| − | * 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 specific to service types, and various features. These will be added to you on an as-needed basis.
| + | [https://resources.emersion.com/display/EKB/Events Take me to the Emersion Knowledge Base article] |
| | | | |
| − | * [[Introduction to Events Video]]
| + | [[file:new_home_sm.jpg|900px]] |
| − | * [[SystemEventMappingReport | System Event Mapping Report]]
| |
| − | | |
| − | == Anatomy of an Event ==
| |
| − | | |
| − | An event comprises three 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.
| |
| − | | |
| − | = See Also =
| |
| − | * [[Introduction to Events Video]]
| |
| − | * [[InvoiceDeliveryApproval| Invoice Delivery and Approval Settings]]
| |
| − | * [[SystemEvents/EventTypes|List of all Event Types]]
| |
| − | * [[System_Event_Mapping_Report | System Event Mapping Report]]
| |
| − | == Advanced Event Features ==
| |
| − | | |
| − | * [[Events/Event Text Library|The Event Text Library]]
| |
| − | * [[SMS Event Gateways | SMS Gateway information for SMS events]]
| |
| − | * [[InvoiceEmailTemplate|Setting up the Invoice Delivery (via email) template]]
| |
| − | * [[SystemEvents/Templates|Setting up your Event Templates]]
| |
| − | * [[Editing SystemEvents/Troubleshooting|Troubleshooting Events]]
| |
This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home.
