The Send E-Mail smart service is used to send an email to one or more recipients. The message body of the email supports HTML, in addition to normal text.
Data transferred using the Send E-Mail smart service is not encrypted. Exchange of unencrypted sensitive or confidential data is not a recommended practice. Application-level security is the responsibility of each customer.
Use the Run as whoever designed this process model option if you are using an email to start another process model.
See also: Smart Services
This section contains tab configuration details specific to this smart service. For more information about common configurations see the Process Node Properties page.
From: Select one of the options listed below to display as the sender of the email.
Fromemail header. The email's domain will be sent in the
Return-Pathheaders to specify that the email was sent from a system on behalf of the
Fromaddress. To learn more, see Configuring Custom Email Senders.
To: Enter the Appian user and group names to receive the email.
toemailrecipient(pp!initiator). Appian, however, automatically casts values of type User, Group, or People to Email Recipient.
Cc: Click Add Cc to enable the Cc: field and enter the Appian user and group names to receive a courtesy copy of the email.
Bc: Click Add Bc to enable the Bc: field and enter the Appian user and group names to receive a blind courtesy copy of the email.
Attachments: Click Add Attachments to enable the Attachments: field and add an attachment.
Subject: (Optional) Enter the desired subject line for the email or enter an expression that defines the subject.
Priority: (Optional) Select High or Low to define the priority of the email.
Message Body: Select Enter text here to type the message directly in the field using the Rich Text Area, or select Use a text or HTML template to look up and select a file to use as the message template.
If the Message Body of the email contains information that is input by an end user, wrap any user-entered process variables in
fn!stripHtml. Otherwise an end user could try to send malicious HTML to the email recipients.
For example, say your process model has a Send E-Mail node and the body of the email displays information from a User Input Task. In the form for that User Input Task, a user could enter HTML into a paragraph field that includes something like a phishing message. You could avoid this by wrapping the process variable for that paragraph field in
If entering the message manually, click the Use Header Template and Use Footer Template links to look up and select a file to use as a template for the header and/or footer. A template file is specified by default from the E-mail Templates folder of the System Knowledge Center.
If selecting a template, click the Validate button to check the name of the file entered in the field. Once you have selected a template file, the substitution grid is populated with the keys found within the template file. The specified template is automatically parsed for substitution fields.
Error Log Outputs
|Users with invalid email addresses||User array||List of Appian users with missing email addresses.|
|Invalid email addresses||Text array||List of invalid email addresses (per RFC822). For more information on the RFC 822 Standard, see also: http://www.faqs.org/rfcs/rfc822.html.|
|Valid To email addresses||Email Recipient array||List of valid email addresses included in the email.|
|Valid Cc email addresses||Email Recipient array||List of valid email addresses included as a Cc in the email.|
|Valid Bcc email addresses||Email Recipient array||List of valid email addresses included as a Bcc in the email.|
Apart from these outputs, you can also specify any kind of expression as a node output. Node outputs can be stored in process variables of the same data type for use elsewhere in the process model.
Email messages that are larger than allowed by your mail server or service provider fail without error notification, and do not trigger an activity exception.
From:field that has a valid and existing email address, bounce notifications are sent to this email address.
Bcc:fields,) the process is paused at this node. A notification is then sent to all process administrators and the process initiator.
On This Page