The Send Email 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 Email 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.
Assignment Options: Unattended
NOTE: 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
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.
If users and groups have already been entered in the textbox, the users and group are replaced with the expression.
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 entering the message manually, you can 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 Email Templates folder of the Appian 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, as shown below:
The specified template is automatically parsed for substitution fields.
Substitution keys identified from the template file appear under the Find in template document column in the substitution grid. This column cannot be edited directly. Under the Replace with column, enter the text you wish to replace the substitution key with by entering an expression that results in a text string value enclosed by quotation marks in the expression. When the activity is executed, each expression is evaluated and displayed in the email. The field can be left blank, in which case the key is replaced with a blank space.
If you change the template document, click Re-scan Template on the substitution grid toolbar. The template is then rescanned for substitution keys and the grid is repopulated. Whenever the template path is changed, the specified document is parsed for substitution keys. Any matching keys in the new document are retained in the grid, and their corresponding mappings are also retained. If, at run-time, the template document is found not to include any of the keys, processing continues normally — the appropriate substitutions are not performed.
If the node configuration is saved by clicking OK and the wizard is reopened, the field is shown if it has a defined value. (It is hidden by default.) The body of the message entered using the HTML Area Editor is inserted between the header and the footer (if selected.) Click Validate to check the name of the file entered in the field.
NOTE: 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.
Error Log Outputs
AC!UsersWithMissingAddresses: (Type User Array) List of Appian users with missing email addresses
AC!InvalidAddresses: (Type 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.
AC!ToValidAddresses: (Type Email Recipient Array) List of valid email addresses included in the email.
AC!CcValidAddresses: (Type Email Recipient Array) List of valid email addresses included as a Cc in the email.
AC!BccValidAddresses: (Type 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.
An exception pauses the process at this node if you run it as a user that doesn't have the right to view the members of a group specified as recipients.
The node cannot automatically handle bounced-back emails. (If your server administrator has a custom email sender defined in the
From: field that has a valid and existing email address, bounce notifications are sent to this email address.)
If the email addresses cannot be resolved (or if an invalid expression has been specified in the
Bcc: fields,) the process is paused at this node. A notification is then sent to all process administrators and the process initiator.
An exception pauses the process at this node if an expression used to specify your attachment doesn't return a document. This can also happen if you run the node under a user account that does not have the right to retrieve the documents included as attachments.
An exception pauses the process at this node if your template file is missing, or if the user selected to run the node does not have the right to access the template.
If you are unable to receive an email message sent through the Send Email activity, contact your network administrator to ensure that your spam filters and security software are not blocking these messages (or communication with the SMTP server.)