Difference between revisions of "SystemEvents/Actions"
From Emersion
| Line 20: | Line 20: | ||
---- | ---- | ||
| − | |||
=== See also === | === See also === | ||
Revision as of 13:26, 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 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. |
See also
