Send Email Quick Action

Use this quick action to compose an email to send to a designated person or group. For example, you can send a confirmation email when a change has been approved. The email can be populated with data, such as field values, functions, counters, or global values.

You also can send updates to the calendar application of the target group, such as task updates when an change occurs in an incident or change record.

Group emails are facilitated using address book-style functionality. The default is to send one email. To send an email for each record in a relationship, click the appropriate radio button, then select the related object from the drop-down list. This also allows you to select email targets for the parent record and related record when completing the email template.

You can also send emails to child object records associated with the parent business object. An email is sent for each instance of the child object.

Parameter	Description
From	The address from which the email is sent. Can only contain one entry. Click Add or click Address Book to enter the address.
To	The address or addresses to which the email is sent. This field can contain multiple entries. Click Add or click Address Book to enter the addresses.
Add CC	Adds a CC (carbon copy) field to the form. Enter the addresses you want.
Add BCC	Adds a BCC (blind carbon copy) field to the form. Enter the addresses you want.
Subject	The subject of the email. You can either enter a subject or create an expression-based subject.
Email body text area	The body of the email. Construct the body of your email using the controls in the email body area.
Attach a file	Allows you to include attachments. Click to attach a file to the email.
Attach from related	Allows you to attach a related business object. Click to link to a related business object and include its attachments. See Creating a Link to a Custom Object.
Prompt for attachments	Asks if you want to attach a file.

Journal.Email records are linked to the parent business object when running the Send Email quick action and business rule, regardless of whether the relationship “internal reference name” is defined or not.

2014.3 behavior for escalation and workflow services:

Only one relationship is expected to exist between two business objects.
If more than one relationship is found, then the relationship references cannot be resolved unless one of the relationships has an empty "internal reference name".
If more than one relationship exists and neither one can be removed, then the customer needs to contact support to remove the internal reference name. This allows escalation and workflow services to uniquely identify it.