A notification consists of four types of data generated from multiples sources and internationalized differently.

To configure notification messages in different languages:

1. Use one of the following methods to internationalize messages in the notification content:

   1. To use values from the resource bundle specified during the task definition, use the following XPath extension function:

      hwf:getTaskResourceBundleString(taskId, key, locale?)
      

      This function returns the internationalized string from the resource bundle specified in the task definition.

      The locale of the notification recipient can be retrieved with the following function:

      hwf:getNotificationProperty('locale')
      

      The task ID corresponding to a notification can be retrieved with the following function:

      hwf:getNotificationProperty('taskId')
      

   2. If a different resource bundle is used, then use the following XPath extension to retrieve localized messages:

      orcl:get-localized-string()
      

However, for all internationalized notifications, the locale is obtained from the BPMUser object of the identity service.

• Prepackaged strings (action links, comments, Oracle BPM Worklist, and so on)

  These strings are internationalized in the product as part of the following package:

  oracle.bpel.services.workflow.resource
  

  The user's locale is used to get the appropriate message.

• Task details attachment

  The user's locale is used to retrieve the task detail HTML content.

• Task outcome strings (approve, reject, and so on)

  The resource bundle for outcomes is specified when the task definition is modeled in the Advanced Settings section of the Human Task Editor. The key to each of the outcomes in the resource bundle is the outcome name itself.

• Notification message

For more information, see How to Specify Multilingual Settings.