Print      Open PDF Version of Online Help


Previous Topic

Next Topic

Creating Workflow Actions: Send Email

A Send Email action on a workflow rule automatically sends email when the conditions on the workflow rule are met.

NOTE: You can create multiple actions for a workflow rule, up to a maximum of 25 actions for each rule.

About the From Address in Emails Sent by Workflow Actions

When you specify the From address for the emails that are sent by a Send Email workflow action, you can select one of the following options:

  • Default Email Address

    If you select this option, then the From address in the email is donotreply@crmondemand.com and the Sender field in the email is set to support@crmondemand.com. If the email recipient attempts to respond to the email, then the address in the To field in the reply is automatically set to support@crmondemand.com.

    NOTE: Starting with Release 20 of Oracle CRM On Demand, the default From address in the emails that are sent by Send Email workflow actions is donotreply@crmondemand.com. In releases of Oracle CRM On Demand earlier than Release 20, the default From address was support@crmondemand.com.

  • Current User

    If you select this option, then the email is sent on behalf of the signed-in user who triggers the workflow. The From address in the email is donotreply@crmondemand.com, and the Sender field in the email is set to the email address of the user. If the email recipient responds to the email, then the address in the To field in the reply is automatically set to the email address of the signed-in user who triggers the workflow rule.

  • Specific Email Address

    If you select this option, then the email is sent on behalf of the email address that you specify on the workflow action. The From address in the email is donotreply@crmondemand.com, and the Sender field in the email is set to the email address that you specified. If the email recipient responds to the email, then the address in the To field in the reply is automatically set to the specific email address that you specified on the workflow action.

NOTE: Oracle CRM On Demand appends a string to each workflow email so that the email can be tracked in the email delivery system at Oracle.

The following procedure describes how to create a Send Email action.

NOTE: The workflow functionality in Oracle CRM On Demand is not intended for use as a tool for mass email sending. If you have a requirement to send a lot of email to your customers, then it is recommended that you use a product such as Oracle CRM On Demand Marketing to fulfill your requirements.

Before you begin. To perform the following procedure, you must have the Manage Workflow Rules privilege in your user role. For information on adding privileges to roles, see Adding Roles.

To create a Send Email action

  1. Navigate to the rule where you want to create the action:
    1. In the upper-right corner of any page, click the Admin global link.
    2. In the Business Process Management section, click Workflow Configuration.
    3. On the Workflow Rules List page, find the rule where you want to create the action.

      For information about searching for workflow rules in the list page, see Filtering Lists.

  2. Click the Workflow Name link on the rule.
  3. In the Actions title bar on the Workflow Rule Detail page, click Menu, and select Send Email.

    NOTE: The trigger event on the workflow rule determines what types of actions can be created on the rule.

    TIP: You can create a copy of an existing workflow rule action by clicking the Copy link for the action.

  4. In the Workflow Action Edit page, enter a name for the action.
  5. If you want to enable the action, select the Active check box.
  6. In the From field, select or enter the address that the email is to be sent from, as follows:
    • Select the Default Email Address option to send the email from the default address.
    • Select the Current User option to send the email on behalf of the signed-in user who triggers the workflow.
    • Select the Specific Email Address option to send the email on behalf of a specific address, and then specify the address.

      When entering the address, the following restrictions apply:

      • You can enter the email address directly, or click the fx icon beside the field, and use Expression Builder to define the email address.
      • Specify only one email address. Multiple addresses are not supported in the From field.
      • If you specify an absolute email address, you must enclose the address in single or double quotation marks.
      • Expression Builder checks only the syntax of the address expressions. It does not check that the address is valid.
      • This field can contain a maximum of 1024 characters.
  7. In the To field, select or enter the email address of the email recipient, as follows:
    • Select Specific User or Relative User on Record, and then select the recipient, as follows:
      • If you select Specific User, click the Lookup icon, and select the user.
      • If you select Relative User on Record, select the recipient from the list.

        If you select a team role as the recipient, the workflow rule sends the mail to each user who has the assigned team role.

        NOTE: For accounts, contacts, and opportunities, any custom roles that are added to the record type are available in the list of Relative User on Record recipients. For more information on customizing records, see Record Type Application Customization Page.

    • Select the Specific Email Address option, and then specify the addresses.

      When entering the addresses, the following restrictions apply:

      • You can enter email addresses directly, or click the fx icon beside the field, and use Expression Builder to define email addresses.
      • To enter multiple addresses, use a semi-colon (;) delimiter.
      • You must enclose absolute email addresses in single or double quotation marks.
      • Expression Builder checks only the syntax of the address expressions. It does not check that the addresses are valid.
      • This field can contain a maximum of 1024 characters.

        The following example shows an entry with multiple addresses:

        PRE('<EmailField1>') + ";" + [<EmailField1>] + ";" + "john.doe@company.com"

  8. Enter the subject line for the email.

    You can embed functions and field names in the text. Three percent signs (%%%) before and after an embedded function or field name indicate that it is to be converted to a text value.

    For example, the text might include the following:

    A new %%%[<AccountType>]%%% account has been created

    If you type a function or field name directly in the field, you must type three percent signs before and after it. If you use Expression Builder to embed a function or field name, the percent signs are automatically added. If you use Expression Builder to embed a complex expression, the percent signs might not be added at the appropriate places. In that case, ensure that the percent signs are placed before and after the entire expression so that the expression is evaluated correctly.

    For example, %%%Today() + 30%%% adds 30 days to the current date, but %%%Today() %%%+ 30 concatenates 30 to the string representation of the current date.

    To use Expression Builder to embed functions and field names in the field, click the fx icon beside the field. If you are entering only static text, you do not need to use Expression Builder.

    This field can contain a maximum of 1024 characters, including the percent signs before and after the functions and field names.

  9. Enter the message for the email.

    You can embed functions and field names in the text, as described in Step 3.

    For example, the text might include the following:

    Hello Mr %%%[<ContactLastName>]%%%,

    This field can contain a maximum of 2000 characters, including the percent signs before and after the expressions.

  10. Save the action.

For step-by-step procedures for creating other types of workflow actions, see the following topics:

Related Topics

See the following topics for related information about workflows:


Published 5/4/2012 Copyright © 2005, 2012, Oracle. All rights reserved. Legal Notices.