Difference between revisions of "SystemEvents/Actions"

From Emersion
Jump to: navigation, search
m (initial page)
Line 2: Line 2:
  
 
=== Introduction ===
 
=== Introduction ===
 +
Actions determine what activities the system performs when an event is triggered. Multiple action types may be configured per event. For example, when the ‘Invoice Overdue’ event is triggered, the system can record the details in the system log, as well as send an email to the customer and your accounts staff. Event actions must be associated with at least one account profile to trigger an event (see below).
  
Actions determine what happens to an event once it has been triggered. Multiple action types may be defined per action. Actions are linked to a specific Event Type.
+
The actions currently available in Emersion are shown in table below.
 
 
----
 
 
 
=== Create New Action ===
 
<gallery caption="Screenshots" perrows="6">
 
Image:Actions_001.png|System Events - Actions List
 
Image:Actions_002.png|System Events - Create New Action
 
</gallery>
 
<br style="clear:both"/>
 
 
 
*Navigate to <code>Events > Actions</code> (From here you can also view a list of actions)
 
*Click '''Create New Action'''
 
*Select an appropriate '''Account Profile''' this action will act upon (remembering that customer accounts MUST be attached to an account profile to have the applicable event type triggered)
 
*Select the Event Type you are creating an action for (Only '''Invoice Delivery''' & '''Invoice Post''' will currently work)
 
*Enter a description for your action (not mandatory)
 
*Select '''Enabled''' or '''Disabled''' to Enable or Disable the action
 
*Set a '''Priority''' (visual only - all actions are currently treated at the same priority)
 
*Select an action '''TYPE''' ('''Important''' - See below)
 
 
 
----
 
 
 
=== Action Types  ===
 
<gallery caption="Screenshots" perrows="6">
 
Image:Actions_003.png|System Events - Action Types
 
</gallery>
 
<br style="clear:both"/>
 
 
 
Action Types define what each Action does. The following is a list of current actions types...
 
  
 
{| border="1" style="border-width: 1px; border-style: solid; border-color: #000; padding: 0"
 
{| border="1" style="border-width: 1px; border-style: solid; border-color: #000; padding: 0"
 
|+ <u>Action Types</u>
 
|+ <u>Action Types</u>
! Action Type !! Description !! Notes
+
! Action Type !! Description
 
|-
 
|-
| Log || This type will store a log entry of the event type details || ''Not currently in use''
+
| Message || Creates an email message using the ''message template''. You can configure each message template with various recipients, fields and text. A separate message template can be created for each action type. When the event is triggered, the system automatically creates emails that are queued for delivery.
 
|-
 
|-
| Message || This type will create a Message based on the selected ''Message Template'' ||
+
| Log || Writes a record into the system log containing details of the event and a ''tag''. A ''tag'' is a keyword or term that you assign to an event to quickly identify the information. You can set up different tags for each event, as well as configure the log template with various fields and text. When the event is triggered, the system automatically creates the log entry.
 
|-
 
|-
| Notification || This type will cause a notification to be displayed when logging into Cumulus || ''Not currently in use''
+
| Notification || Causes a ''notification'' ''alert'' or message to display at the top of the page when users log into the system. The message is visible to all users. You can set up the message template with the text and other information to show.
 
|-
 
|-
| Workflow || Used to call an internal workflow process || ''Used internally only''
+
| Workflow || Used to call an internal system ''workflow'' or process, such as running daily reports, generate invoices, and provisioning. Workflow actions can only be set up by the Emersion support staff. Please contact our support team for further information.
 
|}
 
|}
  
For each action that you create, you are able to create multiple '''action types''' that are attached to it.
 
''Currently, only the action type '''Message''' is fully supported.''
 
 
By default, when you create an action for the first time, a single action type is also created based on what you have asked the action to do.
 
 
----
 
----
 
 
  
 
[[Category:SystemEvents]]
 
[[Category:SystemEvents]]

Revision as of 12:35, 30 September 2011

System Events - Actions

Introduction

Actions determine what activities the system performs when an event is triggered. Multiple action types may be configured per event. For example, when the ‘Invoice Overdue’ event is triggered, the system can record the details in the system log, as well as send an email to the customer and your accounts staff. Event actions must be associated with at least one account profile to trigger an event (see below).

The actions currently available in Emersion are shown in table below.

Action Types
Action Type Description
Message Creates an email message using the message template. You can configure each message template with various recipients, fields and text. A separate message template can be created for each action type. When the event is triggered, the system automatically creates emails that are queued for delivery.
Log Writes a record into the system log containing details of the event and a tag. A tag is a keyword or term that you assign to an event to quickly identify the information. You can set up different tags for each event, as well as configure the log template with various fields and text. When the event is triggered, the system automatically creates the log entry.
Notification Causes a notification alert or message to display at the top of the page when users log into the system. The message is visible to all users. You can set up the message template with the text and other information to show.
Workflow Used to call an internal system workflow or process, such as running daily reports, generate invoices, and provisioning. Workflow actions can only be set up by the Emersion support staff. Please contact our support team for further information.