Difference between revisions of "SystemEvents"
Line 3: | Line 3: | ||
=== Introduction === | === Introduction === | ||
− | The Emersion Events System processes a set of pre-defined ''triggers'' that automatically initiate system [[SystemEvents/Actions|''Actions'']] when the particular condition is detected. Each | + | The Emersion Events System processes a set of pre-defined ''triggers'' that automatically initiate system [[SystemEvents/Actions|'''Actions''']] when the particular condition is detected. Each [[SystemEvents/Actions|action]] is characterised by a [[SystemEvents/Templates|'''Template''']] that defines the action the system performs. Actions are linked to one or many [[SystemEvents/AccountProfiles|'''Account Profiles''']] to determine what accounts the action is performed against''.'' So an event is simply the complete mapping of a ''trigger'', an [[SystemEvents/Actions|action]], [[SystemEvents/AccountProfiles|account profile]], and a [[SystemEvents/Templates|template]]. |
Events are configured by Emersion’s support team specifically to your individual requirements. Each event ''trigger'' is defined for each ''action'' and mapped accordingly to suit your business. Please contact our support team to configure events and triggers for you. | Events are configured by Emersion’s support team specifically to your individual requirements. Each event ''trigger'' is defined for each ''action'' and mapped accordingly to suit your business. Please contact our support team to configure events and triggers for you. |
Revision as of 12:55, 30 September 2011
System Events
Introduction
The Emersion Events System processes a set of pre-defined triggers that automatically initiate system Actions when the particular condition is detected. Each action is characterised by a Template that defines the action the system performs. Actions are linked to one or many Account Profiles to determine what accounts the action is performed against. So an event is simply the complete mapping of a trigger, an action, account profile, and a template.
Events are configured by Emersion’s support team specifically to your individual requirements. Each event trigger is defined for each action and mapped accordingly to suit your business. Please contact our support team to configure events and triggers for you.
There are basically two types of events available: account centric; or process centric. Account centric events examine customer records to determine whether certain conditions exist within the customer accounts, such as invoice overdue, credit card expired, and add new customer or service. Process centric events check for other system process driven conditions, such as usage threshold reached, payment failed, and payment received. The Emersion support staff will set up the right event type to suit your business rules.