Previous	Next		Contents	Index	Glossary

The Notification Mailer uses the Text Body defined for the message in the Message Body property page to generate the plain text body of the e-mail. It also generates an HTML version of the notification message and sends it as an attachment called HTML Message Body to the plain text e-mail. The Notification Mailer generates the content of the HTML attachment from the HTML Body defined for the message. If no HTML Body is defined, it uses the Text Body to generate the HTML mail. The Notification Mailer token replaces all message attributes referenced in the plain text message body with plain text values and token replaces all message attributes referenced in the attached HTML message with HTML-formatted values. See: Sending Plain Text E-mail and Sending HTML-Formatted E-mail.

If your e-mail reader supports HTML-formatting in the message body, then the HTML attachment will also appear in line in the message body.

Note: Message attributes that have Attach Content checked in their Attributes property page, are appended as HTML-formatted attachments. For example:

• If the message attribute is a URL attribute, an attachment called Notification References is appended to the message. This attachment includes a link to each URL attribute for the message that has Attach Content checked. You can navigate to a URL by choosing its link.

• If the message attribute is a PL/SQL document attribute, the fully generated PL/SQL document is fetched and attached to the message.

• If the message attribute is a Document Management document attribute, a URL anchor to the document management integration screen is attached. You need to select the anchor to display the login page of the document management integration screen. Once you log in, the screen displays the referenced document. See: To Access a DM Document Sent by a Notification

Note: PL/SQL CLOB document attributes cannot be used in e-mail notifications.

The notifications received by a user whose notification preference is 'Plain text with HTML attachments' always contain at least two attachments. The first attachment is HTML Message Body and the other is Notification Detail Link. When you select Notification Detail Link, your e-mail reader opens a browser window that displays your notification in the Notification Details web page. You can respond directly to your notification from this web page, bypassing the need to process your response through the Notification Mailer. See: To Respond to a Plain Text E-mail Notification with an HTML Attachment.

Alternatively, a recipient of this type of notification can respond in one of two other ways:

• Manually reply to the notification and enter response values following the instructions provided in the notification. See: To Respond to a Plain Text E-mail Notification Using Templated Response and To Respond to a Plain Text E-mail Notification Using Direct Response.

• Select the HTML Message Body attachment to display the HTML-formatted version of the e-mail message, and click on the HTML link that represents the response. The response link generates a plain text e-mail response that includes a response template updated with the predefined response value you select.

Note: The file name of the HTML Message Body attachment is determined by the text value for the WF_HTML_MESSAGE resource token, or by the token name if no text value is defined. Similarly, the file name of the Notification Detail Link attachment is determined by the text value for the WF_URL_NOTIFICATION resource token, or by the token name if no text value is defined; and the file name of the Notification References attachment is determined by the text value for the WF_URLLIST_ATTACHMENT resource token, or by the token name if no text value is defined. The default file names are "HTML Message Body.html", "Notification Detail Link.html", and "Notification References.html", respectively. If you want to specify different file names for these attachments, you must first create a .msg source file specifying the new file names as the text values for the WF_HTML_MESSAGE, WF_URL_NOTIFICATION, and WF_URLLIST_ATTACHMENT resource tokens. Then use the Workflow Resource Generator program to generate a new Oracle Workflow resource file (wf<language>.res) from the source file and to upload the new seed data from the source file to the database table WF_RESOURCES. See: To Run the Workflow Resource Generator and Setting the WF_RESOURCES Environment Variable.