Print      Open PDF Version of Online Help

Administering Oracle CRM On Demand > Business Process Management > Workflow Configuration > HTML Code in Workflow Email Messages

HTML Code in Workflow Email Messages

When using HTML code in the Message field in an email in a workflow Send Email action, note the following points:

• When you save your workflow action, extra line breaks and spaces might be added to the email message. These extra lines and spaces do not appear in the email that is sent to the recipient.
• If an expression within the HTML email message evaluates to a string that contains an HTML tag, then when Oracle CRM On Demand sends the email, the tag is encoded so that it is treated as text rather than HTML code by the recipient's email application.

  For example, assume that an email message contains the expression %%%[{Description}]%%% to return the value of the Description field, and that the Description field contains the following HTML code:

  <b>This is the description</b>

  In this case, when the expression is evaluated, the tags that are returned as part of the value of the field are not interpreted as HTML code. Instead, the value of the Description field appears in the email message exactly as it appears in the Description field in Oracle CRM On Demand, including the <b> and </b> tags.

• If the recipient's email application does not support HTML, then the email application determines how the HTML message is displayed for that recipient.
• For the HTML email message, Oracle CRM On Demand supports a subset of the elements that are supported in HTML5. If you use an HTML element that Oracle CRM On Demand does not support for use in a workflow email message, then the tags for the unsupported element are removed from the email message when you save the workflow action. No error message appears. In the case of certain elements, the content of the element is also removed from the message.

  The rest of this topic provides details of the supported and unsupported elements.

Supported Elements and Attributes

The following table lists the elements that Oracle CRM On Demand supports for use in a workflow email message and the attributes that are supported for the elements. For information about the properties that are supported for use with the style attribute, see the Supported Properties for the style Attribute section of this topic.

For more information about HTML5, see the HTML5 specification on the World Wide Web Consortium (W3C) Web site.

Supported Properties for the style Attribute

The following cascading style sheet (CSS) properties are supported for use with the style attribute, which can be used with all of the elements that are supported for use in the messages in workflow emails:

• color
• font-family
• font-size
• font-style
• list-style-position
• list-style-type
• text-align

If you use a property that Oracle CRM On Demand does not support for use with the style attribute, then the unsupported property is removed from the style attribute when you save the workflow action.

Unsupported Elements

If you use an HTML element that Oracle CRM On Demand does not support for use in a workflow email message, then the tags for the unsupported element are removed from the email message when you save the workflow action. No error message appears. The content of the element is retained in the message, except in the case of the following elements. For these elements, both the tags and the content of the element are removed for security reasons:

• <applet>
• <area>
• <base>
• <basefont>
• <big>
• <button>
• <center>
• <font>
• <form>
• <frame>
• <frameset>
• <iframe>
• <input>
• <isindex>
• <label>
• <link>
• <map>
• <menu>
• <noframes>
• <noscript>
• <object>
• <optgroup>
• <option>
• <param>
• <script>
• <select>
• <strike>
• <style>
• <textarea>
• <tt>

Example of an HTML Message

The following example shows how Oracle CRM On Demand handles an HTML message in a workflow email. In this example, the workflow action sends an email to the members of a team when an opportunity with high priority is created.

The message might be entered in the Message field in the Send Email workflow action as follows:

<html>

<body>

<pre>

<b>Team,</b>

<big>Good News!</big>

The <i>%%%[{Name}]%%%</i> opportunity created by %%%[{Created By Full Name}]%%% appears to be a <b>high potential</b> opportunity. <b>Please target it as a priority so that we can add it to the next quarter.</b>

Thanks and regards,

David

</pre>

</body>

</html>

NOTE: If you do not use the <pre> element to enclose the message content, then you must use the <br> tag to specify each line break.

The email message as it was entered includes instances of the <html>, <body>, and <big> elements, which are not supported. When the workflow action is saved, the tags for the <html> and <body> elements are removed, but the contents of these elements are retained. In the case of the <big> element, both the tags and the content of the element are removed. The message then appears as follows in the saved workflow action:

<pre>

<b>Team,</b>

The <i>%%%[{Name}]%%%</i> opportunity created by %%%[{Created By Full Name}]%%% appears to be a <b>high potential</b> opportunity. <b>Please target it as a priority so that we can add it to the next quarter.</b>

Thanks and regards,

David

</pre>

When the email is sent, the message appears as follows in an email application that supports HTML:

Team,

The Auto Manufacturer opportunity created by Amanda Jacobsen appears to be a high potential opportunity. Please target it as a priority so that we can add it to the next quarter.

Thanks and regards,

David