Previous	Next		Contents	Index	Glossary

• Name--The internal name of the user as referenced by the Workflow Engine and Notification System. For example, an internal name for a user can be mbeech or 009, where 009 represents the user's employee ID.

Attention: The Name column must be sourced from a column that is less than 30 characters long and is all uppercase. If your source table does not have a column that meets these criteria, DO NOT use string functions to force these restrictions. Instead, define the Name column to be <orig_system>:<orig_system_id> so that Oracle Workflow can reference the original base table where users are stored and a unique user in that table. For example, "PER_PEOPLE:009" represents a user whose employee ID is 009 and is stored in the personnel table called PER_PEOPLE.

• Display_Name--The display name of the user. An example of a display name can be 'Beech, Matthew'.

• Description--An optional description of the user.

• Notification_Preference--Indicate how this user prefers to receive notifications. A value of MAILTEXT, MAILHTML,or MAILATTH allows users to receive and respond to notifications by plain text e-mail, HTML-formatted e-mail or by plain text e-mail with HTML attachments, respectively. A value of QUERY allows users to query notifications from the Notifications Web page. Finally, a value of SUMMARY allows users to get periodic e-mail summaries of their open notifications. However, to respond to the individual notifications, they have to query the notification from the Notification Web page. See: Overview of Notification Handling and Notification Preferences.

Note: A notification preference of MAILTEXT, MAILHTML, or MAILATTH also allows users to query their notifications from the Notifications Web page.

Note: You can map the Notification_Preference column over the Oracle Workflow preferences table using the statement below. The benefit of this is that you can then globally set the default notification preference for all users in your enterprise using the Global Preferences web page and let individual users override that default value by changing their notification preference in the User Preferences web page. See: Global Preferences, User Preferences and get_pref.

			NVL(wf_pref.get_pref(USR.USER_NAME,'MAILTYPE'),

			'MAILHTML')

• Language--The value of the database NLS_LANGUAGE initialization parameter that specifies the default language-dependent behavior of the user's notification session. Refer to your Oracle Database user's guide or installation manual for the list of supported language conventions.

Note: You can globally set the language for all the users in your enterprise, by specifying a language in the Global Preferences web page. Individual users may override that default value by changing their language in the User Preferences web page. See: Global Preferences, User Preferences and get_pref.

Note: You can map the Language column over the Oracle Workflow preferences table using the statement below. The benefit of this is that you can then globally set the default Language for all users in your enterprise using the Global Preferences web page and let individual users override that default value by changing their Language in the User Preferences web page. See: Global Preferences and User Preferences.

			NVL(wf_pref.get_pref(USR.USER_NAME,'LANGUAGE'),

			FNDL.NLS_LANGUAGE)

Attention: Make sure that the e-mail templates used by the Notification Mailer to send notifications has been translated by Oracle to the language you wish to set. The e-mail templates are delivered in a file called wfmail.wft under the subdirectory $ORACLE_HOME/wf/res/<lang>. You can check the appropriate language subdirectory to verify if the templates have been translated to the language you wish to set. See: Modifying Your Message Templates.

• Territory--The value of the database NLS_TERRITORY initialization parameter that specifies the default territory-dependant formatting used in the user's notification session. Refer to your Oracle Database user's guide or installation manual for the list of supported territory conventions.

Note: You can map the Territory column over the Oracle Workflow preferences table using the statement below. The benefit of this is that you can then globally set the default Territory for all users in your enterprise using the Global Preferences web page and let individual users override that default value by changing their Territory in the User Preferences web page. See: Global Preferences, User Preferences and get_pref.

			NVL(wf_pref.get_pref(USR.USER_NAME,'TERRITORY'),

			FNDL.NLS_TERRITORY)

• Email_Address--A valid electronic mail address for this user or a mail distribution list defined by your electronic mail system.

• Fax--A Fax number for the user.

• Orig_System--A code that you assign to the directory repository that this view is based on. For example, if this view is based on the personnel data stored in a Human Resource Management System, Orig_System can be defined as PER.

• Orig_System_ID--The primary key that identifies the user in this repository system. For example, Orig_System_ID can be defined as the value stored in a column called PERSON_ID in a Human Resources database table called PER_PEOPLE.

• Status--The availability of the user to participate in a workflow process. The possible statuses are: active (ACTIVE), unavailable for an extended period (EXTLEAVE), permanently unavailable (INACTIVE), and temporarily unavailable (TMPLEAVE). These statuses are also stored in the lookup type called WFSTD_AVAILABILITY_STATUS.

• Expiration_Date--The date at which the user is no longer valid in the directory service.