Workflow Notification Template Customization

Item Key : WFMAIL
Item Key Name : System mailer
Purpose : Message templates which will be used by other workflow notifications.

Create a custom version of the Standard System Mailer Workflow

1. Open the System: Mailer
2. Save it as XXSYSML
3. Open its wft in textpad and search and repace WFMAIL by XXSYSML
4. Now open this XXSYSML.wft file and change the Name of Workflow from "System: Mailer" to "XX System: Mailer"
5. Now you can modify the templates within this workflow as desired.
6. Now, go back to your PO Approval Workflow and attach a new attribute of name for FYI, #WFM_OPEN_MAIL_FYI
7. Make the value of this attribute point to custom version of "System: Mailer" template

Setting Up Notification Mailers

Please click here for Setting Up Notification Mailers

Oracle Workflow in Multiple Languages

WF_LANGUAGES View
Oracle Workflow uses a view called WF_LANGUAGES that identifies the languages defined in your Oracle installation. Oracle Workflow uses the WF_LANGUAGES view to create, in its translatable tables, a row for each language that maps to a row found in the corresponding non-translated base table. Installed_Flag column is the Flag to indicate if the language is installed and available for use. Ref Oracle Database Globalization Support Guide

Display Oracle Workflow Web Pages in Other Languages
For Oracle Workflow embedded in Oracle Applications, you select and install additional languages as part of the Oracle Applications installation. Users can set their language preference to an installed language through the Personal Homepage in order to view Oracle Applications screens in that language. See: Selecting NLS Settings, Installing Oracle Applications and Set Preferences, Oracle Applications User's Guide.


For the standalone version of Oracle Workflow, the server installation and upgrade are available only in English. To support access to Oracle Workflow web pages in another language, you must load that language after the installation using the Oracle Workflow Configuration Assistant. See the installation documentation for your release and platform.

The Oracle Workflow Configuration Assistant performs the following tasks to set up a language:


1. Runs the script wfnlena.sql to enable the language.
2. Runs the script WFNLADD.sql to create rows for the enabled language in each workflow object translation table.
3. Loads translated resource files for the user interface using the Workflow Resource Generator, translated versions of the standard and demonstration workflow definitions using the Workflow Definitions Loader, and translated Business Event System object definitions using the Workflow XML Loader.
Note: To display Oracle Workflow web pages properly, the character sets on the database tier and middle tier must match.

To Create and View Workflow Definitions in Other Languages using Oracle Workflow Builder


1. Set the NLS_LANG environment variable for the new language, territory, and encoded character set that you want to use for the workflow definition. For example, for Windows NT, run the regedit32 command and locate the NLS_LANG setting under the HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE hierarchy. Double click on NLS_LANG. Then set the variable to the new value and save your work. Specify the value for NLS_LANG in the following format:

LANGUAGE_TERRITORY.CHARSET

For more information about setting NLS_LANG, see: Globalization Support, Oracle Database Installation Guide.

2. Start Oracle Workflow Builder. Create a translated version of your workflow definition and save it as a flat file (.wft), or open and view a workflow definition that is already translated.

Note: Although you can enter and view property values for your workflow definitions in other languages, the Oracle Workflow Builder user interface is still displayed in English.

To Load Workflow Definitions in Other Languages to a Database


1. Ensure that the WF_LANGUAGES view has been created in your workflow server. This view is automatically created during installation.

2. Ensure that the language you want is set up in the database.

For Oracle Workflow embedded in Oracle Applications, you select and install additional languages as part of the Oracle Applications installation. See: Selecting NLS Settings, Installing Oracle Applications.

For standalone Oracle Workflow, the server installation automatically adds all available languages to your workflow database. See the installation documentation for your release and platform.

For standalone Oracle Workflow, the server installation and upgrade are available only in English. To support access to workflow definitions in another language, you must load that language after the installation using the Oracle Workflow Configuration Assistant. See the installation documentation for your release and platform.

3. Load the translated workflow definition to your workflow database using either the Workflow Definitions Loader or the Workflow Builder.

Before running the Workflow Definitions Loader program, you must set the NLS_LANG environment variable to the appropriate territory and character set for the workflow definition you want to load. The character set must match the character set encoding used to create the workflow definition file, which is determined by the NLS_LANG value that was set on the client PC before the .wft file was created in the Workflow Builder. For example, if the .wft file was created in the Japanese native character set encoding JA16SJIS, then you must specify JA16SJIS in the character set portion of NLS_LANG before loading the file, and you cannot specify a different character set such as UTF8.

To set NLS_LANG before running the Workflow Definitions Loader, use the following format:

_TERRITORY.CHARSET

Note that it is important to include the underscore (_) before the territory name and the period (.) between the territory name and the character set name in the NLS_LANG value. For example, if the .wft file was created in the Japanese native character set encoding JA16SJIS, set NLS_LANG to the following value:

_JAPAN.JA16SJIS.

You do not need to include the language in this NLS_LANG value because the Workflow Definitions Loader uses the language specified within the .wft file to determine the language to load.

Note: If you create all your translated workflow definition files in Unicode encoding, you can simply set NLS_LANG to .UTF8 before loading these files. In this case you will not need to reset NLS_LANG for translated files in different languages, because the .UTF8 character set applies to all the files in Unicode encoding.


Before using the Workflow Builder to save a translated workflow definition to the database, you must set the NLS_LANG environment variable to the appropriate language, territory, and character set. If you are saving several workflow definitions in different languages, you must reset NLS_LANG for each language. See: Opening and Saving Item Types, Oracle Workflow Developer's Guide.

Note: The translated versions of Oracle Workflow's standard and demonstration workflow definitions are provided in native character set encoding, not in UTF8.

To Send E-mail Notifications in Other Languages


1. Determine whether Oracle has translated the e-mail notification templates to the language you wish to set by checking for the file containing the templates in the appropriate language subdirectory, $ORACLE_HOME/wf/res/ for the standalone version of Oracle Workflow or $FND_TOP/import/ for the version of Oracle Workflow embedded in Oracle Applications. The standard templates are delivered in a file called wfmail.wft. See: Modifying Your Message Templates.

2. If the e-mail templates are available for the desired language, Oracle Workflow uses the language preference for the notification recipient to determine the language for an e-mail notification.

Oracle Applications users can set their language preference in the Preferences page. This preference is also stored in the ICX: Language profile option. See: Set Preferences, Oracle Applications User's Guide.

Note: In Oracle Applications, users can select a session-level language in the login window, which overrides their user-level language preference for that session. However, Oracle Workflow still uses the user-level language preference to determine the language in which e-mail notifications are sent.

For standalone Oracle Workflow, as the workflow administrator, you can specify the default language setting in the Global Preferences page. Individual users can override the default language setting by specifying their own preferred language in the User Preferences page. See: Setting Global User Preferences and Setting User Preferences, Oracle Workflow User's Guide.


Further reference Clcik here

Oracle Workflow Notification System

Good link covering notifications in depth.

Click here

Workflow Notification Mailer Attributes

You can use special message attributes to control how a notification
mailer generates the e–mail message for a notification, if the recipient
has a notification preference to receive e–mail notifications. For
example, if you want to customize notifications from a particular
department, you can define these attributes for those notifications.
• #WFM_FROM – Define this attribute for a message to specify the
value that appears in the From field of the message header when
the e–mail notification message is delivered to a user. If the
#WFM_FROM message attribute is defined for a notification, the
notification mailer that sends the message will use the
#WFM_FROM attribute value in the From field for that message,
overriding the mailer’s From Address parameter value.
• #WFM_REPLYTO – Define this attribute for a message to specify
the address of the e–mail account that receives incoming
messages, to the which e–mail notification response should be
sent. If the #WFM_REPLYTO message attribute is defined for a
notification, the notification mailer that sends the message will
use the #WFM_REPLYTO attribute value as the reply address for
that message, overriding the mailer’s Reply To parameter value.
• #WFM_HTMLAGENT – Define this attribute for a message to
specify the base URL that identifies the HTML web agent that
handles HTML notification responses. This URL is required to
support e–mail notifications with HTML attachments. The
default URL is derived from the Workflow Web Agent specified
in the Global Preferences web page, but you can override this
default by defining a different value for this attribute. If the
#WFM_HTMLAGENT message attribute is defined for a
notification, the notification mailer that sends the message will
use the #WFM_HTMLAGENT attribute value as the HTML web
agent for that message, overriding the mailer’s HTML Agent
parameter value.

Account Generator Workflows

Inventory COGS Account Generator
Item Type = INVFLXWF
Display Name = ‘Inventory Cost of Goods Sold Account’
Run by the concurrent program ‘Create Intercompany AP Invoices’, short name INCIAP

OM COGS Account Generator
Item Type = OECOGS
Display Name = ‘OM : Generate Cost of Goods Sold Account’
Run by the concurrent program ‘Interface Trip Stop’, short name WSHINTERFACE

To Debug change the said profiles
Account Generator:Purge Runtime Data = No
Account Generator:Run in Debug Mode = Yes

Some learnings in Oracle Workflow Notification

Message Templates : Oracle comes seeded with Message templates in the System: Mailer Item type (WFMAIL). If there are any extra messages that comes in the notification apart from that mentioned in the message body, the same comes from the Message template.

Points to note
1. Do not modify Oracle Supplied Message templates
2. One can add new custom Message templates in the Item Type System: Mailer or in your own Item Type.

To reference the Custom Message Template
1. Create a message attribute by name "#WFM_OPEN_MAIL_FYI" under the message which has your information.
2. The value much have the template message given in format :

Message Attirbutes : Allow you to modify fetures of Workflow notification, without having to create seperate workflow mailers. Various Special Message attributes like few given below
#WFM_FROM - Change the from email address in notification
#WFM_REPLYTO - Changes the Reply To Email

Document Message Attribute : Allow you to build a message body from a query. These type of attribute references PL/SQL procedures to build a text stream.
Document Attributes Values plsql:/
procedure = PL/SQL Procedure
document_identifier = usually a concatenation of ITEM_TYPE:ITEM_KEY
example
apps.wf_engine.setitemattrdocument
(itemtype => 'WWAPAPR',
itemkey => l_curval,
aname => 'WW_OUTPUT_ATTACH',
documentid => 'PLSQLBLOB:ww_ap_pay_approval_wf_pkg.ww_set_ntf_attr/'
|| TO_CHAR (g_request_id)
);

PROCEDURE ww_set_ntf_attr (
document_id IN VARCHAR2,
display_type IN VARCHAR2,
document IN OUT BLOB,
document_type IN OUT VARCHAR2
)

document_id has the value passed from g_request_id

Workflow messages are not versioned and so any addition in the message attributes will effect the immediatly running notifications.

Workflow Notification Testing
1. Modify the Workflow Mailer Configuration using OAM
2. Enter an email address for the Test Address

Further reference
http://www.jrpjr.com
http://www.norcaloaug.org

How to trace back Workflow notification history?

1 CREATE OR REPLACE FUNCTION get_hist ( p_nid IN PLS_INTEGER
2 , p_disp_type IN VARCHAR2 DEFAULT WF_NOTIFICATION.doc_text ) RETURN VARCHAR2 AS
3 v_hist VARCHAR2(32767);
4 BEGIN
5 Wf_Notification.GetComments2 ( p_nid => p_nid
6 , p_display_type => NVL(p_disp_type,WF_NOTIFICATION.doc_text)
7 , p_hide_reassign => 'Y'
8 , p_hide_requestinfo => 'Y'
9 , p_action_history => v_hist );
10
11 RETURN v_hist;
12
13 END get_hist;
14*

APPS@SOLDEV2 on 18-SEP-2008 10:43:34> select get_hist(1574024) from dual;

GET_HIST(1574024)
————————————————————————————————————————
Action History
Num : Action Date : Action : From : To : Details
1 : 17-JUL-2008 12:03:45 : Submit : SYSADMIN : Searle, Matthew :
2 : 18-SEP-2008 10:21:00 : Request Information : Searle, Matthew : SEARLEM4B : Hello


--------------------------------------------------------------------------------