SystemEvents - Revision history

Scarpenter at 05:38, 3 September 2018

2018-09-03T05:38:29Z

Dcowan at 05:36, 13 February 2017

2017-02-13T05:36:21Z

Tyates at 02:31, 10 December 2014

2014-12-10T02:31:43Z

Kberkidge at 03:02, 30 September 2011

2011-09-30T03:02:14Z

Kberkidge at 03:01, 30 September 2011

2011-09-30T03:01:05Z

Kberkidge at 02:59, 30 September 2011

2011-09-30T02:59:40Z

Kberkidge at 02:55, 30 September 2011

2011-09-30T02:55:56Z

Kberkidge at 02:49, 30 September 2011

2011-09-30T02:49:50Z

Kberkidge at 02:49, 30 September 2011

2011-09-30T02:49:34Z

Kberkidge at 02:40, 30 September 2011

2011-09-30T02:40:52Z

@@ Line 1: / Line 1: @@
-== System Events ==
+=This Content Has Moved House=
-=== See [[Events]] ===
+This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
-=== Introduction ===
+We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home.
-The Emersion Events System processes a set of pre-defined [[SystemEvents/Triggers|'''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 [[SystemEvents/Triggers|trigger]], an [[SystemEvents/Actions|action]], [[SystemEvents/AccountProfiles|account profile]], and a [[SystemEvents/Templates|template]].
+[https://resources.emersion.com/display/EKB/Events Take me to the Emersion Knowledge Base article]
-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.
+[[file:new_home_sm.jpg|900px]]

← Older revision		Revision as of 05:36, 13 February 2017
Line 1:		Line 1:
	== System Events ==		== System Events ==
		+
		+	=== See [[Events]] ===

	=== Introduction ===		=== Introduction ===

← Older revision		Revision as of 02:31, 10 December 2014
Line 14:		Line 14:

	<br style="clear:both" />		<br style="clear:both" />
−
−	~~[[Category:SystemEvents]]~~

← Older revision		Revision as of 03:02, 30 September 2011
Line 8:		Line 8:

	There are basically two [[SystemEvents/EventTypes\|type 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.		There are basically two [[SystemEvents/EventTypes\|type 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.
		+
		+	Within each event category, there are many [[SystemEvents/EventTypes\|'''event types''']], each with a set of specific, system defined trigger points or conditions.

	----		----

@@ Line 7: / Line 7: @@
 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.
+There are basically two [[SystemEvents/EventTypes|type 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.
 ----

@@ Line 3: / Line 3: @@
 === 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 ''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''.
+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.

@@ Line 9: / Line 9: @@
 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.
 <br style="clear:both" />
 [[Category:SystemEvents]]