Setting up Transmission Actions
Transmission Actions refers the different mode of actions you can configure on a message. Besides setting the main delivery to be of a certain type, you can transform the message attributes, determining additional routes as well as other options. Below is screenshot of the first tab Delivery
Main Message Delivery Method
You can define the main delivery method to be SMS, SMTP, SNMP, SYSLOG, POP3 and HTTP.
Once the delivery method is selected, the corresponding outbound profiles will be shown for selection.
Delivery Server if Applicable
This refers to SMTP outbound option only.
This will be utilized in the case of email alert to ownself upon success or failure sending.
Route as email to Users
You can also utilize this option to send the message to other users in the system.
Send transmission success notification emails
This option will send an alert to ownself if the transmission is successful.
Route to another Transmission Action
You can utilize this option to route to another Transmission Action. For example if the first Transmission Action is SMTP email, you can route it to syslog. Please note there will not be self routing to own Transmission Action.
In this tab you are able to transform message attributes as desire.
This option allows body message transformation.
This option allows subject transformation.
This option allows recipient transformation of email address or mobile number for SMS and SMTP delivery method. This will not be applied if the recipient belongs to a group alias. Normal group operation will apply.
Send Body Text Only / Send Subject and Body Text (For SMS Only)
This option allows whether to combine body message and subject in a single SMS. This is only applicable for SMS transmission from email.
This module allows comprehensive manipulation of text. Static text or variables can be added in the text. Text operations can also be applied:
- Removal of part string
- Include a part string
- Replace a part string
- Uppercase a string
- Lowercase a string
This module caters for management operations after a message fails to send.
Number of Failure Retries
After failure, the message will be subjected to a schedule. The system will try sending the message until it is success. The maximum number of retries is specified here.
This specifies the interval between retries. The resolution is up to hour, minute and second.
Send Message to another Mail Server after FAILURE
The system can route the message to another mail server by SMTP. This is on top of the retries.
Send transmission failure notification emails via
Option to send failure alert to owner user.
The system can route to another Transmission Action.
This tab allows you send escalation SMS or email. Escalation policies make sure the right people are notified at the right time. They connect services to schedules. A service can only have one escalation policy. Escalation process will start if there is no acknowledgment from the first message recipient.
Is Escalate Message
Determine whether a message should be an escalation process.
The escalation schedule will be activated after the first message is sent.
The escalated parties after the first message is sent when there is no acknowledgment and schedule is up. The escalation parties can be selected from contact or entered manually in the ad hoc field.
This tab configures if you need to send repetitive message to your recipient.
Reminder Message After Successful Send
Set the option whether you want to send repetitive message.
If yes set the schedule for it.