Using External Routing Define state machine routing rules for your task using Oracle Business Rules.

27-54 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Each subtask has its own copy of the payload. Internally, this option provides lesser performance and storage space consumption because more storage space is consumed.

7. Click OK.

For more information about users, groups, or application roles, see Section 26.2.1.1.3, Participant Assignment.

27.3.8 How to Specify Multilingual Settings and Style Sheets

The Presentation section shown in Figure 27–54 enables you to specify resource bundles for displaying task details in different languages in Oracle BPM Worklist and WordML and custom style sheets for attachments. Figure 27–54 Presentation Section

27.3.8.1 Specifying WordML and Other Style Sheets for Attachments

To specify WordML style sheets for attachments: 1. In the Stylesheet for Attachments list of the Presentation section, select one of the following options: ■ Word ML : This option dynamically creates Microsoft Word documents for sending as email attachments using a WordML XSLT style sheet. The XSLT style sheet is applied on the task document. ■ Other : This option creates email attachments using an XSLT style sheet. The XSLT style sheet is applied on the task document.

2. Click the Search icon to select the style sheet as an attachment.

27.3.8.2 Specifying Multilingual Settings

You can specify resource bundles for displaying task details in different languages in Oracle BPM Worklist. Resource bundles are supported for the following task details: ■ Displaying the value for task outcomes in plain text or with the messagekey format. ■ Making email notification messages available in different languages. At runtime, you specify the hwf:getTaskResourceBundleStringtaskId, key, locale? XPath extension function to obtain the internationalized string from the specified resource bundle. The locale of the notification recipient can be retrieved with the function hwf:getNotificationPropertypropertyName. Resource bundles can also simply be property files. For example, a resource bundle that configures a display name for task outcomes can look as follows: Designing Human Tasks 27-55 ■ APPROVE=Approve ■ REJECT=Reject To specify multilingual settings: 1. In the Presentation section, click the Add icon across from Resource Bundle. The Resource Details dialog shown in Figure 27–55 appears. Figure 27–55 Resource Details Dialog

2. In the Resource Name field, enter the name of the resource used in the resource

bundle. This should be a .properties-based resource bundle file.

3. In the Resource Location field, click the Search icon to select the JAR or ZIP

resource bundle file to use. The resource bundle is part of your system archive SAR file. If the resource bundle is outside of the composite project, you are prompted to place a local copy in SCA-INFlib. If the resource bundle file is not in the composite class loader directly under SCA-INFclasses or in a JAR file in SCA-INFlib, you must specify its location. For example, if the resource bundle is accessible from a location outside of the composite class loader for example, an HTTP location such as http:host:portbundleApptaskBundles.jar, then this location must be specified in this field.

4. Click OK to return to the Human Task Editor.

For more information, see Section 31.2.6, How to Configure Notification Messages in Different Languages.

27.3.9 How to Escalate, Renew, or End the Task

Figure 27–56 shows the Deadlines section of the Human Task Editor. You can specify the expiration duration of a task in this global policy section also known as the routing slip level. If the expiration duration is specified at the routing slip level instead of at the participant type level, then this duration is the expiration duration of the task across all the participants. However, if you specify expiration duration at the participant type level through the Limit allocated duration to