Notification mailers use message templates defined in Oracle Workflow Builder to generate e-mail notifications. Oracle Workflow provides a set of standard templates which are used by default, as well as some alternative templates for certain types of messages. These message templates are defined in the System: Mailer item type.
Although message templates are defined as messages in Oracle Workflow Builder, they are not true messages. Rather, they serve as outlines for e-mail messages sent by notification mailers. Message templates determine the basic format of an e-mail notification, including what header information to include, and whether and where to include details such as the message due date and priority. Message templates for notifications that require a response should also describe the syntax the reply should follow and list the information needed to confirm the notification.
It is not recommended to modify the standard templates. However, you can optionally customize the message templates used to send your e-mail notifications by either using the alternative templates provided in the System: Mailer item type by Oracle Workflow, or creating your own custom message templates in the System: Mailer item type using the Workflow Builder. You can implement alternative standard or custom templates in the following ways:
Assign the templates you want to a particular notification mailer service component in the mailer configuration parameters. The templates assigned to a mailer override the default System: Mailer templates. See: Notification Mailer Configuration Wizard.
Assign the templates you want to a particular notification in a workflow process by defining special message attributes. In this case the templates assigned to the notification override both the templates assigned to a mailer and the default System: Mailer templates. See: Notification Mailer Message Template Attributes.
The templates in the System: Mailer item type have message attributes that represent every part of the notification message. Within the body of a template, the message attributes are token substituted to insert the specific information for a particular instance of a notification into the message outline.
Note: Do not modify, add new attributes to, or delete existing attributes from the standard message templates in the System: Mailer item type.
If you create new custom templates, your custom templates should contain only the high-level notification layout and general information common to all e-mail notifications. You must name the message attributes for these templates with the same standard names as the message attributes for the standard templates. Do not create any new custom message attributes in your templates with nonstandard names, and do not reference any nonstandard attribute tokens in the template message body. A notification mailer can only token substitute the attributes in the message body if you use the standard attribute names. To include additional information in a custom message template, enter that information directly into the template message body, without using tokens.
You can optionally omit some of the standard tokens from your custom templates, if you do not want to send the information they represent. However, you should not omit the tokens that represent the key information to be conveyed in the notification. For example, if you define a custom version of a template that includes the &BODY token, you must include the &BODY token in the custom template as well, in order to include the body text of the particular notification that is being sent into the template outline.
Oracle Workflow provides the following message templates.
Note: In addition to the message templates listed here, the System: Mailer item type also includes some other messages which are not currently used.
See: Reviewing Notifications via Electronic Mail.
If you use the templated response method, the Notification System uses the Workflow Open Mail (Templated) message as a default template for e-mail notifications that require a response. The notification template includes generic instructions on how to respond to a notification. It also includes the date that a response is due and any history of actions on the notification.
Note: The templated response method is the default response method for Oracle Workflow. Notification mailers use the templated response method unless you select the Direct Response parameter in the notification mailer configuration wizard. See: Notification Mailer Configuration Wizard.
The response instructions in the plain text message body describe how to reply manually using the templated response method. This message is used for notifications sent to performers with a notification preference of MAILTEXT or MAILATTH. The response instructions in the HTML-formatted message body describe how to reply using the automatically generated response template. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
The Workflow Open Mail (Templated) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the actual notification message definition. |
| MAILTO | The content of the HTML tag that a recipient would click on to respond to a notification. This attribute is used only for HTML e-mail notifications. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is not currently used. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. This attribute is not currently used. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| HISTORY | The history of actions on the notification. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Open Mail (Templated) message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE ______________________Start of Response Template______________________ Response Template for &NOTIFICATION To submit your response, reply to this message, including this response template with your reply. Copy and paste from this message if necessary to obtain an editable copy of the template. Insert your response value between the quotes following each response prompt. &RESPONSE ______________________End of Response Template_______________________ Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&HEADER <P>&BODY <P>Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes. <P>&MAILTO <P>&HISTORY </BODY> </HTML>
Oracle Workflow provides the Orig. Workflow Open Mail (Templated) message as an alternative template that you can optionally use as a template for e-mail notifications that require a response if you use the templated response method. This template does not include the header attributes that are displayed in the Workflow Open Mail (Templated) message.
The Orig. Workflow Open Mail (Templated) notification template includes generic instructions on how to respond to a notification. It also includes the following information about a message: the name of the sender of the message, message priority, date that a response is due, and any comments from the sender or, if the notification is forwarded from another user, any comments from the forwarder.
Note: The templated response method is the default response method for Oracle Workflow. Notification mailers use the templated response method unless you select the Direct Response parameter in the notification mailer configuration wizard. See: Notification Mailer Configuration Wizard .
The response instructions in the plain text message body describe how to reply manually using the templated response method. This message is used for notifications sent to performers with a notification preference of MAILTEXT or MAILATTH. The response instructions in the HTML-formatted message body describe how to reply using the automatically generated response template. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
The Orig. Workflow Open Mail (Templated) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the actual notification message definition. |
| MAILTO | The content of the HTML tag that a recipient would click on to respond to a notification. This attribute is used only for HTML e-mail notifications. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is not currently used. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification From: &SENDER &COMMENT ______________________Start of Response Template______________________ Response Template for &NOTIFICATION To submit your response, reply to this message, including this response template with your reply. Copy and paste from this message if necessary to obtain an editable copy of the template. Insert your response value between the quotes following each response prompt. &RESPONSE ______________________End of Response Template_______________________ Notification Details: &BODY Due Date: &DUE_DATE
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P> <P>From: <B>&SENDER</B> <P><B><FONT SIZE=+1>&COMMENT</FONT> </B> <P>&BODY <P><B>Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes.</B> <P>&MAILTO </BODY> </HTML>
If you select the direct response method, the Notification System uses the Workflow Open Mail (Direct) message as a default template for e-mail notifications that require a response. The notification template includes generic instructions on how to respond to a notification. It also includes the date that a response is due and any history of actions on the notification.
Note: To select the direct response method for a notification mailer, you must select the Direct Response parameter in the notification mailer configuration wizard. See: Notification Mailer Configuration Wizard.
The response instructions in the plain text message body describe how to reply using the direct response method. This message is used for notifications sent to performers with a notification preference of MAILTEXT or MAILATTH. The response instructions in the HTML-formatted message body describe how to reply using the automatically generated response template. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
Note: Responses that are generated automatically from an HTML-formatted notification or attachment always use a response template, regardless of which response method you select.
The Workflow Open Mail (Direct) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the actual notification message definition. |
| MAILTO | The content of the HTML tag that a recipient would click on to respond to a notification. This attribute is used only for HTML e-mail notifications. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is not currently used. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. This attribute is not currently used. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| HISTORY | The history of actions on the notification. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Open Mail (Direct) message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE ________________________________________________________________________ Response Instructions for &NOTIFICATION To submit your response, reply to this message, including this note with your reply. The first lines of your reply must be your responses to the notification questions. Instructions below detail exactly what should be placed on each line of your reply. &RESPONSE ________________________________________________________________________ Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&HEADER <P>&BODY <P>Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes. <P>&MAILTO <P>&HISTORY </BODY> </HTML>
Oracle Workflow provides the Orig. Workflow Open Mail (Direct) message as an alternative template that you can optionally use as a template for e-mail notifications that require a response if you select the direct response method. This template does not include the header attributes that are displayed in the Workflow Open Mail (Direct) message.
The Orig. Workflow Open Mail (Direct) notification template includes generic instructions on how to respond to a notification. It also includes the following information about a message: the name of the sender of the message, message priority, date that a response is due, and any comments from the sender of the message or, if the notification is forwarded from another user, any comments from the forwarder.
Note: To select the direct response method for a notification mailer, you must select the Direct Response parameter in the notification mailer configuration wizard. See: Notification Mailer Configuration Wizard.
The response instructions in the plain text message body describe how to reply using the direct response method. This message is used for notifications sent to performers with a notification preference of MAILTEXT or MAILATTH. The response instructions in the HTML-formatted message body describe how to reply using the automatically generated response template. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
Note: Responses that are generated automatically from an HTML-formatted notification or attachment always use a response template, regardless of which response method you select.
The Orig. Workflow Open Mail (Direct) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the actual notification message definition. |
| MAILTO | The content of the HTML tag that a recipient would click on to respond to a notification. This attribute is used only for HTML e-mail notifications. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is not currently used. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification From: &SENDER &COMMENT ________________________________________________________________________ Response Instructions for &NOTIFICATION To submit your response, reply to this message, including this note with your reply. The first lines of your reply must be your responses to the notification questions. Instructions below detail exactly what should be placed on each line of your reply. &RESPONSE ________________________________________________________________________ Notification Details: &BODY Due Date: &DUE_DATE
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P> <P>From: <B>&SENDER</B> <P><B><FONT SIZE=+1>&COMMENT</FONT> </B> <P>&BODY <P><B>Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes.</B> <P>&MAILTO </BODY> </HTML>
If you use an e-mail application such as Microsoft Outlook Express as your e-mail client, you should select the standard Workflow Open Mail (Outlook Express) message as a template for e-mail notifications that require a response, for users with a notification preference of MAILHTML, MAILHTM2, or MAILATTH. This message includes a link to the Notification Details Web page to let users respond to the notification there. This template is provided to accommodate e-mail applications that cannot process the response links included in the Workflow Open Mail (Templated) and Workflow Open Mail (Direct) templates.
Note: If you select the Workflow Open Mail (Outlook Express) message template for a notification mailer, then you should also select the Workflow More Information Request (Outlook Express) message template for that notification mailer. See: Workflow More Information Request (Outlook Express) Message.
The response instructions in the plain text message body describe how to reply manually using the templated response method. This message is used for notifications sent to performers with a notification preference of MAILATTH. The HTML-formatted message body includes a link called "Click here to respond" which lets users access the notification in the Notification Details Web page to respond to the notification. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
Note: When users choose the "Click here to respond" link, it automatically attempts to establish a Web session with the Web server. Users must be able to connect to the Web server to use this link to respond to a notification. Users must log in to Oracle Workflow to access the Notification Details page, unless you enable guest access in Oracle E-Business Suite. See: Reviewing Notifications via Electronic Mail and Responses Through the Notification Detail Link Attachment.
The Workflow Open Mail (Outlook Express) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the actual notification message definition. |
| MAILTO | The content of the HTML tag that a recipient would click on to respond to a notification. This attribute is not currently used. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is used only for HTML e-mail notifications. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. This attribute is not currently used. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| HISTORY | The history of actions on the notification. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Open Mail (Outlook Express) message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE ---------- Start of Response Template ------------------------------------------ Response Template for &NOTIFICATION To submit your response, reply to this message including this response template in your reply. Insert your response value between the quotes following each response prompt. &RESPONSE ---------- End of Response Template -------------------------------------------- Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&HEADER <P>&BODY <P>&CLICK_HERE_RESPONSE <P>&HISTORY </BODY> </HTML>
Oracle Workflow provides the Orig. Workflow Open Mail (Outlook Express) message as an alternative template that you can optionally use as a template for e-mail notifications that require a response if you use an e-mail application such as Microsoft Outlook Express as your e-mail client. This template does not include the header attributes that are displayed in the Workflow Open Mail (Outlook Express) message.
The Orig. Workflow Open Mail (Outlook Express) message includes the name of the sender of the message, any comments from the sender or forwarder, and a link to the Notification Details Web page to let users respond to the notification there. This template can be used to accommodate e-mail applications that cannot process the response links included in the Orig. Workflow Open Mail (Templated) and Orig. Workflow Open Mail (Direct) templates.
Note: If you select the Orig. Workflow Open Mail (Outlook Express) message template for a notification mailer, then you should also select the Workflow More Information Request (Outlook Express) message template for that notification mailer. See: Workflow More Information Request (Outlook Express) Message.
The response instructions in the plain text message body describe how to reply manually using the templated response method. This message is used for notifications sent to performers with a notification preference of MAILATTH. The HTML-formatted message body includes a link called "Click here to respond" which lets users access the notification in the Notification Details Web page to respond to the notification. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
Note: When users choose the "Click here to respond" link, it automatically attempts to establish a Web session with the Web server. Users must be able to connect to the Web server to use this link to respond to a notification. Users must log in to Oracle Workflow to access the Notification Details page, unless you enable guest access in Oracle E-Business Suite. See: Reviewing Notifications via Electronic Mail and Responses Through the Notification Detail Link Attachment.
The Orig. Workflow Open Mail (Outlook Express) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the actual notification message definition. |
| MAILTO | The content of the HTML tag that a recipient would click on to respond to a notification. This attribute is not currently used. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is used only for HTML e-mail notifications. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification From: &SENDER &COMMENT ---------- Start of Response Template ------------------------------------------ Response Template for &NOTIFICATION To submit your response, reply to this message including this response template in your reply. Insert your response value between the quotes following each response prompt. &RESPONSE ---------- End of Response Template -------------------------------------------- Notification Details: &BODY Due Date: &DUE_DATE
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P> <P>From: <B>&SENDER</B> <P><B><FONT SIZE=+1>&COMMENT</FONT> </B> <P>&BODY <P>&CLICK_HERE_RESPONSE </BODY> </HTML>
The Notification System uses the Workflow Open FYI Mail message as a default template for all e-mail notifications that do not require a response. The template indicates that the notification is for your information (FYI) and does not require a response. In addition to the message, the template also includes any history of actions on the notification.
The Workflow Open FYI Mail message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. This attribute is not currently used. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| HISTORY | The history of actions on the notification. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the text that appears in the body of the Workflow Open FYI Mail template, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent. The boilerplate text for the plain text message body is as follows:
Oracle Workflow Notification (FYI) &TIMEZONE ________________________________________________________________________ &HEADER &BODY &HISTORY
The boilerplate text for the HTML-formatted message body is as follows:
<HTML><HEAD><TITLE>Oracle Workflow Notification (FYI)</TITLE><STYLE> <! - &TEMPLATE_STYLE - > </STYLE></HEAD> <BODY BGCOLOR="#FFFFFF"> <SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&HEADER <P>&BODY <P>&HISTORY </BODY> </HTML>
Oracle Workflow provides the Orig. Workflow Open FYI Mail message as an alternative template that you can optionally use as a template for e-mail notifications that do not require a response. This template does not include the header attributes that are displayed in the Workflow Open FYI Mail message.
The Orig. Workflow Open FYI Mail template indicates that the notification is for your information (FYI) and does not require a response. In addition to the message, the template also includes the name of the sender of the message and any comments from the sender or forwarder.
The Orig. Workflow Open FYI Mail message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| BODY | The text of the body defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
The boilerplate text for the plain text message body is as follows:
Oracle Workflow Notification (FYI) From: &SENDER &COMMENT ________________________________________________________________________ &BODY
The boilerplate text for the HTML-formatted message body is as follows:
<HTML><HEAD></HEAD> <BODY BGCOLOR="#FFFFFF"><b>Oracle Workflow Notification (FYI)</b> <br> From: <B>&SENDER</B> <br>&COMMENT <hr> <P>&BODY </BODY> </HTML>
Oracle Workflow provides the Workflow View From UI message as an alternative template that you can optionally use for open response-required notifications whose content you do not want to send in e-mail. An e-mail message generated from this template will still include the header attributes for the notification, as well as any history of actions on the notification. However, the e-mail message will exclude the message body for the notification and will not enable responses through e-mail. Users can only view and respond to such notifications through the Notification Details Web page.
The notification template informs the recipient that the notification is best viewed from the Web page and directs the recipient to access the online version of the notification.
The Workflow View From UI message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. This attribute is not currently used. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| HISTORY | The history of actions on the notification. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow View From UI message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE Notification Details: &HEADER This notification is best viewed from the Notification Detail page. Please access the online version of this notification. &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&HEADER <P>This notification is best viewed from the Notification Detail page.<BR> Please access the online version of this notification. <P>&HISTORY </BODY> </HTML>
Oracle Workflow provides the Workflow View FYI From UI message as an alternative template that you can optionally use for open FYI notifications whose content you do not want to send in e-mail. An e-mail message generated from this template will still include the header attributes for the notification, as well as any history of actions on the notification. However, the e-mail message will exclude the message body for the notification. Users can only view such notifications through the Notification Details Web page.
The notification template informs the recipient that the notification is best viewed from the Web page and directs the recipient to access the online version of the notification.
The Workflow View FYI From UI message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| START_DATE | The date the message is sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. This attribute is not currently used. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| HISTORY | The history of actions on the notification. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow View FYI From UI message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE Notification Details: &HEADER This notification is best viewed from the Notification Detail page. Please access the online version of this notification. &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&HEADER <P>This notification is best viewed from the Notification Detail page.<BR> Please access the online version of this notification. <P>&HISTORY </BODY> </HTML>
The Notification System uses the Workflow URL Attachment message as a default template to create the Notification References attachment for HTML-formatted notification messages that include URL attributes with Attach Content checked. The template includes a list with links to each URL.
Note: The Workflow URL Attachment message template is used only for notifications that do not include embedded Oracle Application Framework regions. For a notification that includes an embedded region, Oracle Workflow includes the Related Applications region in the e-mail message, instead of appending the Notification References attachment.
The Workflow URL Attachment message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| URLLIST | The list of URLs to be included in the attachment. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the text that appears in the body of the Workflow URL Attachment template, where an attribute preceded by an ampersand (&) is token substituted with a runtime value when the notification is sent. The boilerplate text for the HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification References </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><h2 class="OraHeader">Notification References</h2> <HR WIDTH="100%"> <BR> &URLLIST <BR> <HR WIDTH="100%"> <BR> </BODY> </HTML>
The default Workflow Canceled Mail message informs the recipient that a previously sent notification is canceled. You can set the Send E-mails for Canceled Notifications mailer parameter in the notification mailer configuration wizard to determine whether or not notification mailers should send notification cancellation messages. See: Notification Mailer Configuration Wizard.
The Workflow Canceled Mail message has the following message attributes, with values that are drawn from the message definition associated with the canceled notification activity:
| START_DATE | The date the original message was sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line of the original message. |
| BODY | The text of the original message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
The boilerplate text for the plain text message body is as follows:
&TIMEZONE You earlier received the notification shown below. That notification is now canceled, and no longer requires your response. You may simply delete it along with this message. ________________________________________________________________________ &HEADER &BODY
The boilerplate text for the HTML-formatted message body is as follows:
<html><Head><STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </Head> <body> <SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>You earlier received the notification shown below. That notification is now canceled, and no longer requires your response. You may simply delete it along with this message. <hr> &HEADER <P>&BODY </body></html>
Oracle Workflow provides the Orig. Workflow Canceled Mail message as an alternative template that you can optionally use to inform the recipient that a previously sent notification is canceled. This template does not include the header attributes that are displayed in the Workflow Canceled Mail message.
You can set the Send E-mails for Canceled Notifications mailer parameter in the notification mailer configuration wizard to determine whether or not notification mailers should send notification cancellation messages. See: Notification Mailer Configuration Wizard.
The Orig. Workflow Canceled Mail message has the following message attributes, with values that are drawn from the message definition associated with the canceled notification activity:
| START_DATE | The date the original message was sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line of the original message. |
| BODY | The text of the original message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
The boilerplate text for the plain text message body is as follows:
You earlier received the notification shown below. That notification is now canceled, and no longer requires your response. You may simply delete it along with this message. ________________________________________________________________________ &BODY
The boilerplate text for the HTML-formatted message body is as follows:
<html><Head></Head><body>You earlier received the notification shown below. That notification is now canceled, and no longer requires your response. You may simply delete it along with this message. <hr> &BODY </body></html>
The Workflow Invalid Mail message is sent to a user by default when a user responds incorrectly to a notification. For example, if a response message from a user contains a valid notification ID (NID) line matching it with a notification, but does not contain any response value or contains an invalid response value, the notification mailer sends a Workflow Invalid Mail message to the user. This message describes how to respond to the notification correctly. The message attributes are as follows:
| START_DATE | The date the original message was sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line of the original message. |
| BODY | The text of the original message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified by the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the original message definition. |
| MAIL_ERROR_MESSAGE | An error message that the mail program generates if an error occurs upon processing the response. |
| MAIL_ERROR_STACK | An error stack of arguments that the mail program generates if an error occurs upon processing the response. This attribute is not currently used. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is not currently used. |
| MAIL_VALUE_FOUND | The invalid response value found in the user's response message. |
| MAIL_EXP_VALUES | Information about the expected valid response values. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| HISTORY | The history of actions on the notification. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
The boilerplate text for the plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE Warning: Your previous response to this message was invalid (see error message below). Please resubmit your response. Important: Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is included in full and contains the prefix 'NID' and all the details between the square brackets when responding. Error Message: &MAIL_ERROR_MESSAGE Value Found: &MAIL_VALUE_FOUND Remarks: &MAIL_EXP_VALUES ________________________________________________________________________ Response Instructions for &NOTIFICATION To submit your response, reply to this message, including this original with your reply. This note contains a special 'NID' string that is required to process the reponse. The first lines of your reply must be your responses to the notification questions. You should enter one line for each response required by the notfication; any additional lines will be ignored. You may leave a line blank to accept the default value for that specific response. You must supply a value or a blank line for each question asked. Instructions below detail exactly what should be placed on each line of your reply. &RESPONSE ________________________________________________________________________ Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for the HTML-formatted message body is as follows:
<html> <Head> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </Head> <body> <SPAN class="OraTipLabel">&TIMEZONE</SPAN> <p>Warning: Your previous response to this message was invalid (see error message below). Please resubmit your response. <P>Error Message: &MAIL_ERROR_MESSAGE <BR> <BR>Value Found: &MAIL_VALUE_FOUND <BR> <BR>Remarks: &MAIL_EXP_VALUES <HR> <P>&HEADER <P>&BODY <P><B>Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes.</B> <P><B>Important:</B> Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is included in full and contains the prefix 'NID' and all the details between the square brackets when responding. <P>&MAILTO <P>&HISTORY </BODY> </HTML>
Oracle Workflow provides the Orig. Workflow Invalid Mail message as an alternative template that you can optionally use when a user responds incorrectly to a notification. This template does not include the header attributes that are displayed in the Workflow Invalid Mail message.
The Orig. Workflow Invalid Mail message describes how to respond to the notification correctly. The message attributes are as follows:
| START_DATE | The date the original message was sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line of the original message. |
| BODY | The text of the original message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified by the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| RESPONSE | The user response section as defined by the Respond message attributes in the original message definition. |
| MAIL_ERROR_MESSAGE | An error message that the mail program generates if an error occurs upon processing the response. |
| MAIL_ERROR_STACK | An error stack of arguments that the mail program generates if an error occurs upon processing the response. This attribute is not currently used. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is not currently used. |
| MAIL_VALUE_FOUND | The invalid response value found in the user's response message. |
| MAIL_EXP_VALUES | Information about the expected valid response values. |
The boilerplate text for the plain text message body is as follows:
Oracle Workflow Notification &COMMENT Warning: Your previous response to this message was invalid (see error message below). Please resubmit your response. Important: Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is inlcuded in full and contains the prefix 'NID' and all the details between the square brackets when responding. Error Message: &MAIL_ERROR_MESSAGE Value Found: &MAIL_VALUE_FOUND Remarks: &MAIL_EXP_VALUES ________________________________________________________________________ Response Instructions for &NOTIFICATION To submit your response, reply to this message, including this original with your reply. This note contains a special 'NID' string that is required to process the reponse. The first lines of your reply must be your responses to the notification questions. You should enter one line for each response required by the notfication; any additional lines will be ignored. You may leave a line blank to accept the default value for that specific response. You must supply a value or a blank line for each question asked. Instructions below detail exactly what should be placed on each line of your reply. &RESPONSE ________________________________________________________________________ Notification Details: &BODY Due Date: &DUE_DATE
The boilerplate text for the HTML-formatted message body is as follows:
<html><Head></Head><body>Warning: Your previous response to this message was invalid (see error message below). Please resubmit your response. <P>Error Message: &MAIL_ERROR_MESSAGE <BR> <BR>Value Found: &MAIL_VALUE_FOUND <BR> <BR>Remarks: &MAIL_EXP_VALUES <HR><P><B><FONT SIZE=+1>&COMMENT</FONT> </B> <P>&BODY <P><B>Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes.</B> <P><B>Important:</B> Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is inlcuded in full and contains the prefix 'NID' and all the details between the square brackets when responding. <P>&MAILTO </BODY> </HTML>
The default Workflow Closed Mail message informs the recipient that a previously sent notification is now closed. It has the following message attributes, with values that are drawn from the message definition associated with the closed notification activity:
| START_DATE | The date the original message was sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line of the original message. |
| BODY | The text of the original message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
The boilerplate text for the plain text message body is as follows:
&TIMEZONE You earlier received the notification shown below. That notification is now closed, and no longer requires your response. You may simply delete it along with this message. ________________________________________________________________________ &HEADER &BODY
The boilerplate text for the HTML-formatted message body is as follows:
<html><Head><STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </Head> <body><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>You earlier received the notification shown below. That notification is now closed, and no longer requires your response. You may simply delete it along with this message. <hr> &HEADER <P>&BODY </body></html>
Oracle Workflow provides the Orig. Workflow Closed Mail message as an alternative template that you can optionally use to inform the recipient that a previously sent notification is now closed. This template does not include the header attributes that are displayed in the Workflow Closed Mail message.
The Orig. Workflow Closed Mail message has the following message attributes, with values that are drawn from the message definition associated with the closed notification activity:
| START_DATE | The date the original message was sent. |
| TO | The role the notification is sent to; the performer. |
| SUBJECT | The subject line of the original message. |
| BODY | The text of the original message. |
| COMMENT | Comments added by the sender or the forwarder. |
| PRIORITY | The priority of the notification message. |
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
The boilerplate text for the plain text message body is as follows:
You earlier received the notification shown below. That notification is now closed, and no longer requires your response. You may simply delete it along with this message. ________________________________________________________________________ &BODY
The boilerplate text for the HTML-formatted message body is as follows:
<html><Head></Head><body>You earlier received the notification shown below. That notification is now closed, and no longer requires your response. You may simply delete it along with this message. <hr> &BODY </body></html>
The Notification System uses the Workflow Summary Mail (HTML) message by default as a template to send a summary of workflow notifications to users and roles that have their notification preference set to SUMMARY or SUMHTML in the Oracle Workflow directory service. The Workflow Summary Mail (HTML) message summarizes all currently open notifications for a given user/role. The HTML-formatted message body also provides a link to the Worklist Web page as well as links to each notification in the Notification Details Web page.
The Workflow Summary Mail (HTML) message has the following message attributes, with values that are drawn from the message definition associated with the open notification activity:
| SUMMARY | Summary report. |
| USER_NAME | The user/role the notification summary is sent to; the performer. |
| SYSDATE | The current date. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
The plain text message body is used for notifications sent to performers with a notification preference of SUMMARY. The boilerplate text for the plain text message body is as follows:
&TIMEZONE &SUMMARY
The HTML-formatted message body is used for notifications sent to performers with a notification preference of SUMHTML. The boilerplate text for the HTML-formatted message body is as follows:
<HTML><HEAD> <STYLE> &TEMPLATE_STYLE </STYLE> <TITLE>Summary Notification</TITLE> </HEAD> <BODY><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&SUMMARY </BODY> </HTML>
The Notification System uses the Workflow Warning Mail message as a default template to send a message to a user the first time it receives unsolicited mail from that user. For example, if a message from a user does not contain a notification ID (NID) line matching it with a notification, or contains an incorrectly formatted NID line, the notification mailer sends a Workflow Warning Mail message to the user.
Note: You can optionally use the Send Warning for Unsolicited E-mail mailer parameter to prevent notification mailers from sending any warning messages. See: Notification Mailer Configuration Wizard.
The Workflow Warning Mail message has the following message attributes, with values that are drawn from the unsolicited mail:
| UBODY | The text of the unsolicited mail message body. |
| USUBJECT | The text of the unsolicited mail subject line. |
| UFROM | The address of the user that sent the unsolicited mail. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
The boilerplate text for the plain text message body is as follows:
Messages sent to this account are processed automatically by the Oracle Workflow Notification Mailer. The message you sent did not appear to be in response to a notification. If you are responding to a notification, please use the response template that was included with your notification. Take care to include the 'NID' line of the template in your reply. If you are not responding to a notification, please do not send mail to this account. Important: Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is included in full and contains the prefix 'NID' and all the details between the square brackets when responding. ________________________________________________________________________ From: &UFROM Subject: &USUBJECT &UBODY
The boilerplate text for the HTML-formatted message body is as follows:
<html><head> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </head><body> <B>Messages sent to this account are processed automatically by the Oracle Workflow Notification Mailer. The message you sent did not appear to be in response to a notification. If you are responding to a notification, please use the auto-generated reply created when responding to the original message. This contains the 'NID' line which is necessary for identification. If you are not responding to a notification, please do not send mail to this account. <P><B>Important:</B> Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is included in full and contains the prefix 'NID' and all the details between the square brackets when responding. <hr> <P>From: &UFROM <BR>Subject: &USUBJECT <P>&UBODY </body></html>
The Notification System uses the Workflow Signature Required Mail message as a default template for e-mail notifications that require an electronic signature in the user's response. Users can only respond to such notifications through the Notification Details Web page, where they can enter either a password-based signature or a certificate-based digital signature, depending on the notification's requirements, to sign the response. The notification template informs the recipient that a signature is required and that the response cannot be submitted through e-mail. Instead, the notification template directs the recipient to access the online version of the notification to submit a reponse.
The plain text message body is used for notifications sent to performers with a notification preference of MAILTEXT or MAILATTH. The HTML-formatted message body additionally includes a link called "Click here to respond" which lets users access the notification in the Notification Details Web page to respond. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
Note: When users choose the "Click here to respond" link, it automatically attempts to establish a Web session with the Web server. Users must be able to connect to the Web server to use this link to respond to a notification. Users must also log in to Oracle Workflow to access the Notification Details page. See: Reviewing Notifications via Electronic Mail.
However, if you enable guest access for links to the Notification Details page, the "Click here to respond" link does not appear in the HTML-formatted message body. When electronic signatures are required, users must log in with their own user names and passwords to enter their signatures with their notification responses. See: Responses Through the Notification Detail Link Attachment.
The Workflow Signature Required Mail message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| BODY | The text of the body defined in the message. |
| NOTIFICATION | Required notification code used to identify the information in the notification. For notifications that require an electronic signature to be entered online, this notification code does not include the access key or node identifier information that would be needed for an e-mail response. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. This attribute is not currently used. |
| SUBJECT | The subject line defined in the message. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| HISTORY | The history of actions on the notification. |
| COMMENT | Comments added by the sender or the forwarder. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a notification. This attribute is used only for HTML e-mail notifications. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Signature Required Mail message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE This notification requires a signature in your response. You cannot respond to this notification through e-mail. Please access the online version of the notification to submit your response. Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>&HEADER <P>&BODY <P><B>This notification requires a signature in your response. You cannot respond to this notification through e-mail. Please access the online version of the notification to submit your response.</B> <P>&CLICK_HERE_RESPONSE <P>&HISTORY </BODY> </HTML>
See: #WF_SIG_POLICY Attribute.
The Workflow Signature Warning Mail message is sent to a user by default if that user sends an e-mail response containing the notification ID (NID) line of a notification that requires an electronic signature. A valid response to such a notification can only be submitted through the Notification Details Web page. The notification template informs the recipient that a signature is required and that the response cannot be submitted through e-mail. Instead, the notification template directs the recipient to access the online version of the notification to submit a response.
The Workflow Signature Warning Mail message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| SUBJECT | The subject line of the original message. |
| COMMENT | Comments added by the sender or the forwarder. |
| BODY | The text of the original message. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Signature Warning Mail message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE &COMMENT Warning: You earlier received the notification shown below. This notification requires a signature in your response. You cannot respond to this notification through e-mail. Please access the online version of the notification to submit your response. ________________________________________________________________________ &HEADER &BODY
The boilerplate text for an HTML-formatted message body is as follows:
<html><Head><STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </Head> <body><P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>Warning: You earlier received the notification shown below. This notification requires a signature in your response. You cannot respond to this notification through e-mail. Please access the online version of the notification to submit your response. <hr> <P><B><FONT SIZE=+1>&COMMENT</FONT> </B> <P>&HEADER <P>&HISTORY <P>&BODY </body></html>
See: #WF_SIG_POLICY Attribute.
The Notification System uses the Workflow Secure Mail Content message as a default template for notifications that include sensitive content that cannot be sent in e-mail for security reasons. You can mark notifications as including secure content using the special #WF_SECURITY_POLICY message attribute. Users can only view and respond to such notifications through the Notification Details Web page. The notification template informs the recipient that the notification content cannot be sent in e-mail and directs the recipient to access the online version of the notification instead.
The Workflow Secure Mail Content message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| SUBJECT | The subject line defined in the message. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Secure Mail Content message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification ________________________________________________________________________ Notification &NOTIFICATION This notification contains secure content which cannot be sent through e-mail. Please access the online version of the notification to see the details. ________________________________________________________________________
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P> <P>Notification: &NOTIFICATION <br><br> <B>This notification contains secure content which cannot be sent through e-mail. Please access the online version of the notification to see the details.</B> </BODY> </HTML>
See: #WF_SECURITY_POLICY Attribute.
The Notification System uses the Workflow Open Mail (More Information Request) message as a default template to send a request for more information about a notification from one user to another user. The notification template includes generic instructions on how to respond with the requested information. It also includes the following information about a message: the name of the sender of the message, any history of actions on the notification, and the date that a response is due.
The response instructions in the plain text message body describe how to reply manually. This message is used for notifications sent to performers with a notification preference of MAILTEXT or MAILATTH. The response instructions in the HTML-formatted message body describe how to reply using the automatically generated response template. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
The Workflow Open Mail (More Information Request) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| BODY | The text of the body defined in the message. |
| SUBJECT | The subject line defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
| HISTORY | The history of actions on the notification. |
| QUESTION | Details about what information is being requested. |
| RESPONSE | The user response section. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Open Mail (More Information Request) message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE ______________________Start of Response Template______________________ More Information Template for &NOTIFICATION User &SENDER has requested more information for the notification. Please reply to this message, including this response template with your reply. Copy and paste from this message if necessary to obtain an editable copy of the template. Insert your comments between the quotes against the prompt. Question: &QUESTION &RESPONSE ______________________End of Response Template______________________ Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE><STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P> <P>Question: <B>&QUESTION</B> <P><B>Please click on the following link to automatically generate an E-mail response for this question. Before sending the E-mail response, ensure desired comments within quotes.</B> <P>&MAILTO <P><B>Notification Details:</B> <P>&HEADER <P>&BODY <BR> Question: <B>&QUESTION</B> <P><B>Please click on the following link to automatically generate an E-mail response for this question. Before sending the E-mail response, ensure desired comments within quotes.</B> <P>&MAILTO <P>&HISTORY </BODY> </HTML>
Oracle Workflow provides the Orig. Workflow Open Mail (More Information Request) message as an alternative template that you can optionally use as a template to send a request for more information about a notification from one user to another user. This template does not include the header attributes that are displayed in the Workflow Open Mail (More Information Request) message.
The Orig. Workflow Open Mail (More Information Request) notification template includes generic instructions on how to respond with the requested information. It also includes the following information about a message: the name of the sender of the message, the date that a response is due, and any history of actions on the notification.
The response instructions in the plain text message body describe how to reply manually. This message is used for notifications sent to performers with a notification preference of MAILTEXT or MAILATTH. The response instructions in the HTML-formatted message body describe how to reply using the automatically generated response template. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
The Orig. Workflow Open Mail (More Information Request) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| BODY | The text of the body defined in the message. |
| SUBJECT | The subject line defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
| HISTORY | The history of actions on the notification. |
| QUESTION | Details about what information is being requested. |
| RESPONSE | The user response section. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification ______________________Start of Response Template______________________ More Information Template for &NOTIFICATION User &SENDER has requested more information for the notification. Please reply to this message, including this response template with your reply. Copy and paste from this message if necessary to obtain an editable copy of the template. Insert your comments between the quotes against the prompt. Question: &QUESTION &RESPONSE ______________________End of Response Template______________________ Notification Details: &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P> <P>User &SENDER has requested more information for the following notification. <P>&BODY <P>Question: <B>&QUESTION</B> <P><B>Please click on the following link to automatically generate an E-mail response for this question. Before sending the E-mail response, ensure desired comments within quotes.</B> <P>&MAILTO <P>&HISTORY </BODY> </HTML>
If you use an e-mail application such as Microsoft Outlook Express as your e-mail client, you should select the standard Workflow More Information Request (Outlook Express) message as a template for requests for more information about a notification from one user to another user, for users with a notification preference of MAILHTML, MAILHTM2, or MAILATTH. This message includes a link to the Notification Details Web page to let users respond to the request there. This template is provided to accommodate e-mail applications that cannot process the response links included in the Workflow Open Mail (More Information Request) template. In particular, if you select the Workflow Open Mail (Outlook Express) message template for a notification mailer, then you should also select the Workflow More Information Request (Outlook Express) message template for that notification mailer. See: Workflow Open Mail (Outlook Express Message).
Note: You can use the Open Notification (More Information Request) parameter in the notification mailer configuration wizard to select the appropriate message template. See: Notification Mailer Configuration Wizard.
The response instructions in the plain text message body describe how to reply manually using the templated response method. This message is used for notifications sent to performers with a notification preference of MAILATTH. The HTML-formatted message body includes a link called "Click here to respond" which lets users access the notification in the Notification Details Web page to respond to the request for information. This message is used for notifications sent to performers with a notification preference of MAILHTML or MAILHTM2, and is also attached to notifications sent to performers with a notification preference of MAILATTH.
Note: When users choose the "Click here to respond" link, it automatically attempts to establish a Web session with the Web server. Users must be able to connect to the Web server to use this link to respond to a notification. See: Reviewing Notifications via Electronic Mail.
The Workflow More Information Request (Outlook Express) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| BODY | The text of the body defined in the message. |
| SUBJECT | The subject line defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
| HISTORY | The history of actions on the notification. |
| QUESTION | Details about what information is being requested. |
| RESPONSE | The user response section. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| TIMEZONE | The time zone of the dates and times displayed in the notification, based on the time zone of the server from which the notification was sent. |
| CLICK_HERE_RESPONSE | The content of the HTML tag that a recipient would click on to access the Notification Details page to respond to a request for more information. This attribute is used only for HTML e-mail notifications. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow More Information Request (Outlook Express) message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification &TIMEZONE ______________________Start of Response Template______________________ More Information Template for &NOTIFICATION User &SENDER has requested more information for the notification. Please reply to this message, including this response template with your reply. Copy and paste from this message if necessary to obtain an editable copy of the template. Insert your comments between the quotes against the prompt. Question: &QUESTION &RESPONSE ______________________End of Response Template______________________ Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </HEAD> <BODY BGCOLOR="#FFFFFF" > <P><SPAN class="OraTipLabel">&TIMEZONE</SPAN> <P>From: &SENDER <P>Question: <B>&QUESTION</B> <P><B>Please click on the following link to respond to this request for more information</B> <P>&CLICK_HERE_RESPONSE <P><B>Notification Detail:</B> <P>&HEADER <P>&BODY <BR> Question: <B>&QUESTION</B> <P><B>Please click on the following link to respond to this request for more information</B> <P>&CLICK_HERE_RESPONSE <P>&HISTORY </BODY> </HTML>
The Workflow Invalid Open Mail (More Information Request) message is sent to a user by default when a user responds incorrectly to a request for more information. For example, if an answering message from a user contains a valid notification ID (NID) line matching it with a request for more information about a notification, but does not contain any response value, the notification mailer sends a Workflow Invalid Open Mail (More Information Request) message to the user. This message describes how to respond to the request for information correctly.
The Workflow Invalid Open Mail (More Information Request) message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| DUE_DATE | The date by which a response is required, specified in the notification activity. |
| BODY | The text of the body defined in the message. |
| SUBJECT | The subject line defined in the message. |
| COMMENT | Comments added by the sender or the forwarder. |
| SENDER | The name of the sender of the message, as displayed in the From column in the Worklist. |
| HISTORY | The history of actions on the notification. |
| QUESTION | Details about what information is being requested. |
| RESPONSE | The user response section. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| HEADER | Standard header attributes and any custom header attributes defined to hold key information for the message. See: Header Attributes. |
| MAIL_EXP_VALUES | Information about the expected valid response values. |
| MAIL_VALUE_FOUND | The invalid response value found in the user's response message. |
| MAIL_ERROR_MESSAGE | An error message that the mail program generates if an error occurs upon processing the response. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
You can customize the boilerplate text that appears in the body of the Workflow Invalid Open Mail (More Information Request) message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification Warning: Your previous response to this message was invalid (see error message below). Please resubmit your response. Important: Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is included in full and contains the prefix 'NID' and all the details between the square brackets when responding. Error Message: &MAIL_ERROR_MESSAGE Value Found: &MAIL_VALUE_FOUND Remarks: &MAIL_EXP_VALUES ______________________Start of Response Template______________________ More Information Template for &NOTIFICATION User &SENDER has requested more information for the notification. Please reply to this message, including this response template with your reply. Copy and paste from this message if necessary to obtain an editable copy of the template. Insert your comments between the quotes against the prompt. Question: &QUESTION &RESPONSE ______________________End of Response Template______________________ Notification Details: &HEADER &BODY Due Date: &DUE_DATE &HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<html> <Head> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </Head> <body> <SPAN class="OraTipLabel">&TIMEZONE</SPAN> <p>Warning: Your previous response to this message was invalid (see error message below). Please resubmit your response. <P>Error Message: &MAIL_ERROR_MESSAGE <BR> <BR>Value Found: &MAIL_VALUE_FOUND <BR> <BR>Remarks: &MAIL_EXP_VALUES <HR><P>Question: <B>&QUESTION</B> <P><B>Please click on the following link to automatically generate an E-mail response for this question. Before sending the E-mail response, ensure desired comments within quotes.</B> <P>&MAILTO <P>&HEADER <P>&BODY <P><B>Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes.</B> <P><B>Important:</B> Some mail clients, notably early releases of Microsoft Outlook Express, may not copy the 'NID' line properly in your response. Please verify that the 'NID' line is included in full and contains the prefix 'NID' and all the details between the square brackets when responding. <P>Question: <B>&QUESTION</B> <P><B>Please click on the following link to automatically generate an E-mail response for this question. Before sending the E-mail response, ensure desired comments within quotes.</B> <P>&MAILTO <P>&HISTORY </BODY> </HTML>
Oracle Workflow sends the Workflow More Info Answered Mail message to a user if the user sends another response to a request for more information that has already been answered, or if the user sends an unsolicited e-mail formatted as a more information response. The message informs the recipient that no further response is required.
The Workflow More Info Answered Mail message has the following message attributes. The values are drawn from the message definition associated with a notification activity.
| MAIL_ERROR_MESSAGE | An error message that the mail program generates if an error occurs upon processing the response. |
| NOTIFICATION | Required notification code used to identify the information in the notification. |
| FROM | The user who sent the request for more information, as displayed in the From column in the Worklist. |
| QUESTION | Details about what information was requested in the most recent question. |
You can customize the boilerplate text that appears in the body of the Workflow More Info Answered Mail message, where attributes preceded by an ampersand (&) are token substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
You earlier received a more information request for notification mentioned below. That request is now answered, and no longer requires your response. You may simply delete it along with this message. Error Message: &MAIL_ERROR_MESSAGE ________________________________________________________________________ Notification Details: Notification ID : &NOTIFICATION Question : &QUESTION From : &FROM
The boilerplate text for an HTML-formatted message body is as follows:
<html><Head><STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </Head> <body><SPAN class="OraTipLabel"></SPAN> <p>You earlier received a more information request for notification mentioned below. That request is now answered, and no longer requires your response. You may simply delete it along with this message. <P>Error Message: &MAIL_ERROR_MESSAGE <BR> <P>Notification Details: <BR> <P>Notification ID: &NOTIFICATION <P>Question : &QUESTION <P>From: &FROM <BR> </BODY> </HTML>
Oracle Workflow sends the User Notification Preference Update Report message to the SYSADMIN user when a user's notification preference is set to DISABLED. The message informs the recipient that an e-mail notification could not be sent to one or more recipients, that the notification preference for those recipients has been set to DISABLED, and that those recipients' original notification preferences, which are listed, should be reset after the issues that caused the failures are corrected. See: Outbound Notification Mailer Processing and Handling Mailer Errors.
This message has the following message attributes:
| NOTIFICATION_ID | The identifier of the original notification for which an e-mail failure occurred. |
| ROLE | The role to which the original notification was sent. |
| UPDATED_USER_REPORT | A list of the recipients of the original notification to whom e-mail could not be delivered, and of those recipients' original notification preference settings before their notification preferences were set to DISABLED. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
The boilerplate text for the plain text message body is as follows:
The notification with the ID of &NOTIFICATION_ID experienced problems when attempting to dispatch an email notification to the role &ROLE. Subsequently the notification preference for the following users has been set to DISABLED. Please correct the issue and re-enable their notification preference. -------------------------------------------------------------------------------- &UPDATED_USER_REPORT
The boilerplate text for the HTML-formatted message body is as follows:
<html> <head> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </head> <body> <p>The notification with the ID of <b>&NOTIFICATION_ID</b> experienced problems when attempting to dispatch an email notification to the role <b>&ROLE</b>. Subsequently the notification preference for the following users has been set to <b>DISABLED</b>. Please correct the issue and re-enable their notification preference. <p> <hr> <p> <span style="font-family:monospace,courier">&UPDATED_USER_REPORT</span> </body></html>
Oracle Workflow sends the Invalid Email Address Warning message to the SYSADMIN user when a notification could not be sent to one or more e-mail addresses for a user, but was sent successfully to at least one valid e-mail address defined for the user. The message informs the recipient that an e-mail notification could not be sent to one or more e-mail addresses for the role, that those addresses should be either corrected or removed from the list of e-mail addresses defined for the role, and that Oracle Workflow will not attempt to send any further notifications to these addresses until the notification mailer is restarted. Until that time, notifications will be sent only to the address or addresses for the role to which the original notification was successfully sent. See: Outbound Notification Mailer Processing and Handling Mailer Errors.
This message has the following message attributes:
| NOTIFICATION_ID | The identifier of the original notification for which an e-mail failure occurred. |
| ROLE | The role to which the original notification was sent. |
| USER_INVALID_EMAIL | The invalid e-mail address or addresses for the user to whom the original notification was sent. |
| TEMPLATE_STYLE | The stylesheet that determines the appearance of the HTML-formatted message body. |
The boilerplate text for the plain text message body is as follows:
The notification with the ID of &NOTIFICATION_ID experienced problems when attempting to dispatch an email notification to the role &ROLE of the below specified email address or addresses. Please correct these email addresses or remove them from the role's email address list if they are invalid, and then stop and restart the notification mailer. Oracle Workflow will not attempt to send any further notifications to these addresses until the notification mailer is restarted. -------------------------------------------------------------------------------- &USER_INVALID_EMAIL
The boilerplate text for the HTML-formatted message body is as follows:
<html> <head> <STYLE> <! - &TEMPLATE_STYLE - > </STYLE> </head> <body> <p>The notification with the ID of <b>&NOTIFICATION_ID</b> experienced problems when attempting to dispatch an email notification to the role <b>&ROLE</b> of the below specified email address or addresses. Please correct these email addresses or remove them from the role's email address list if they are invalid, and then stop and restart the notification mailer. Oracle Workflow will not attempt to send any further notifications to these addresses until the notification mailer is restarted. <p> <hr> <p> <span style="font-family:monospace,courier">&USER_INVALID_EMAIL</span> </body></html>
Oracle Workflow sends the Notification Mailer Override Address Verification message when an administrator sets an override address where the notification mailer should send all outgoing e-mail notifications for testing purposes. The message requests the recipient to verify the override address to ensure that the address is accessible and that its use is authorized. This message must not be customized. See: Reviewing Service Component Details.