{//% unless portal.user.is_agent %} Tickets
Login Submit a Ticket News {//% endunless %}


Emails can be send manually to a crew member or messages can be generated automatically whenever a roster change is made or when you release the roster.
A number of settings need to be done before we can send Email.
COM channel:
Shall be OUT
Details from you email provider
SSL stands for Secured Socket Layer - basically it is a secure way of providing authentication and encryption during communication online between your computer and the mail server
User Name & Password
User and psw to your email account
Communication type: 
File Type:
Setup parameters:
Default email sender, which is used when no user email is provided.
The Email sender is called the ORIGINATOR. The Email of the logged in user will be used.
Add emails for receivers of Com Channel failures. Separate emails with ";"
Email receivers for RaidoAPI failures
If the setting UseDefaultEmailSender is set to TRUE, Sleipner will send all outgoing e-mails from the "DefaultEmailSender" address and not the user email address  (who did the change).
The templates are made in the Integration factory.
We will make 4 templates, two for Revision notifications (Body and Header) that is used every time we make a revision. And two for Roster Releases (Body and Header) that will send an Email when you release the roster.
Revision Notification:
Step 1:
Name: Mandatory, use a descriptive name.
Data Type: Must be of type "Human Resources"
Step 2:
Data Element: Text
Add: This will create an empty template.
Template: Add the elements you want in the message. 
Follow the same process for the Header.
Roster Release:
The process is the same as for Revision Notification
The Events are created in the Automation factory. When an event like a roster revision happen, the Event is triggered and Sleipner will send the message to the COM and the message will go out. 
In the Events section we create our two notifications
RevisionNotification and RosterRelease
The way the two events are set up is the same, except for the Event type and the template.
Step 1:
Event: The system has a long list of built in events. For this exercise we use Roster REV and ROSTER PUBL
Datatype: Human Resources
Filter: None, but you could use any of the HR Filters.
Station: None, but you could use Station specific messages
Bounce message: isn't used for SMS
Step 2:
Template Type: Own meassage
Template: RevisionNotification Body
Header Template: RevisionNotification Header
Step 3:
Com Channel: Email
Com Channel Instance: Select you COM Email instance
Address: Write the Email Address types you want to include, multiple addresses can be separated by semicolon (see Email Types). The system will look after the Email type type on the crew and send the email to the corresponding email address
Send as unique:
If the COM channel is EMAIL you have the option , this will send individual emails
click finish 
Manual Email:
From the roster gantt you can send Email direct to a crew member.
Right click on the crew and select the Email icon
Originator: the email address of the user logged in.
Receiver: The email address of the crew.
You can send the message to multiple crew by mark the crew
Manual Email to Contacts:
From the search dialog  you can send email to user that isn't loaded into the Gantt.
Click on the email address in the Email column and the email dialog will open.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.