Oracle Workflow Guide
Release 2.6.2

Part Number A95265-02
Previous Next       Contents Index Glossary
         Previous  Next          Contents  Index  Glossary

To Create a Configuration File for the Notification Mailer

Note: If you are using the version of Oracle Workflow embedded in Oracle Applications and you have implemented Oracle Applications Manager, you can use Oracle Workflow Manager to configure and run the Notification Mailer. For more information, please refer to the Oracle Applications Manager online help.

Attention: The CONNECT parameter is not required if you submit the Notification Mailer as a concurrent program from the version of Oracle Workflow embedded in Oracle Applications. In this case, the concurrent manager passes in the database connection information for the Notification Mailer to use.

Attention: If you want to start the Sendmail version of the Notification Mailer, you must also specify the full path of the Sendmail executable directory in your PATH environment variable.

Attention: If you are using the version of Oracle Workflow embedded in Oracle Applications, and want to start the Sendmail version of the Notification Mailer concurrent program, then the Account parameter must be set to the account from which you start the Concurrent Manager.

Note: You can only run one Notification Mailer per instance, and each Notification Mailer must use a separate e-mail account to process responses.

Attention: The FROM parameter is only used to set the From: field value by the UNIX Sendmail version of the Notification Mailer. The MAPI-compliant version of the Notification Mailer uses the display value that is set up for the mail account specified in the ACCOUNT parameter.

Attention: If you include the HTML_MAIL_TEMPLATE parameter in your configuration file, the Notification Mailer will ignore the DIRECT_RESPONSE parameter when sending messages to users with a notification preference of 'MAILATTH'. Instead, all users with this notification preference will receive the plain text message body defined for the Workflow Open Mail for Outlook Express template, which uses the templated response method. Consequently, if you do not need to use the Workflow Open Mail for Outlook Express template, you should comment out the HTML_MAIL_TEMPLATE parameter to let the DIRECT_RESPONSE parameter take effect.

Warning: Note that there are limitations when you set ALLOW_FORWARDED_RESPONSE to N. For example, suppose a notification is sent to a distribution list mail alias that does not have a USER/ROLE relationship in the Oracle Workflow directory service. If any user from the distribution list responds to the notification, the Notification Mailer will always treat their notification response as unsolicited mail, because the "From:" e-mail address, which is an individual user's e-mail address, will never match the distribution list mail alias.

Attention: The REPLYTO parameter is only used to set the reply-to address by the UNIX Sendmail version of the Notification Mailer. The MAPI-compliant version of the Notification Mailer uses the display value that is set up for the mail account specified in the ACCOUNT parameter.

Note: For the UNIX Sendmail version of the Notification Mailer, the DISCARD value must always be the full path name of a mail file.

Note: For the UNIX Sendmail version of the Notification Mailer, the PROCESS value must always be the full path name of a mail file.

Note: For the UNIX Sendmail version of the Notification Mailer, the UNPROCESS value must always be the full path name of a mail file.

Attention: Only a message response that contains a notification ID is checked by the tag file. If the Notification Mailer receives a message response that does not contain a notification ID, it moves the message response to the discard folder and sends a 'Warning' message to the sender that it received unsolicited mail. See: Workflow Warning Mail Message.

		Status "Matching string"

Attention: It is important that you uniquely identify bounced messages and auto-replies from normal responses in the tag file. If you do not identify bounced and auto-reply messages, the Notification Mailer can mistake these as invalid responses, send an 'Invalid' message and continue to wait for a reply. In both cases a perpetual loop would occur where the Notification Mailer keeps sending out an 'Invalid' message and the 'Invalid' message bounces back or is auto-replied.

		ERROR "-- Unsent message follows --"

Attention: If a message response matches more than one string in the tag file, it gets tagged with the status of the first string it matches in the file. That is, the Notification Mailer performs a top to bottom comparison against the tag file. Due to this behavior, you should prioritize your strings listing the ERROR tags first, followed by the UNAVAIL and then IGNORE tags.

Attention: If you include the HTML_MAIL_TEMPLATE parameter in your configuration file, the Notification Mailer will ignore the DIRECT_RESPONSE parameter when sending messages to users with a notification preference of 'MAILATTH'. Instead, all users with this notification preference will receive the plain text message body defined for the Workflow Open Mail for Outlook Express template, which uses the templated response method. Consequently, if you do not need to use the Workflow Open Mail for Outlook Express template, you should comment out the HTML_MAIL_TEMPLATE parameter to let the DIRECT_RESPONSE parameter take effect.

Note: The HTML_MAIL_TEMPLATE parameter does not apply to users with a notification preference of 'MAILTEXT'.

See: Implementing the Notification Mailer

See: Response Processing

See: Modifying Your Message Templates

See: Defining Rules for Automatic Notification Processing


         Previous  Next          Contents  Index  Glossary


Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.