| Previous | Next |  | Contents | Index | Glossary

## Step 4 Creating the WF_LANGUAGES View

The field values in the property pages of Oracle Workflow Builder and the workflow notifications delivered to your users can be translated to the languages defined in your Oracle installation. However, in order for this to be possible, you must create a view called WF_LANGUAGES that identifies the languages defined in your Oracle installation. Oracle Workflow uses this view to create in its translatable tables, a row for each language that maps to a row found in its non-translated base table.

The WF_LANGUAGES view must include the following columns:

- Code--The language code.

- Display_Name--The display name of the language.

- NLS_Language--The value of the Oracle NLS_LANGUAGE initialization parameter that specifies the default language-dependent behavior of a session.

- NLS_Territory--The value of the Oracle NLS_TERRITORY initialization parameter that specifies the default territory-dependant date and numeric formatting of a session.

- NLS_Codeset--The character set for the language.

- Installed_Flag--Flag to indicate if the language is installed and available for use.

A sample WF_LANGUAGES view is included in the script of each of the predefined directory services that Oracle Workflow provides.

Context: You need to perform this step only once.

See: To display user defined objects in Oracle Workflow Builder in other languages (for standalone version only)

See: To display an Oracle Workflow web session in other languages (for standalone version only

See: To display e-mail notifications in other languages

See: Predefined Directory Services

See: Oracle8i National Language Support Guide

| Previous | Next |  | Contents | Index | Glossary