To the right of Rules Dictionary, click the Edit icon, as shown in

Designing Human Tasks 27-53 Figure 27–53 Error Assignment Details

4. Click the Add icon and select a user, group, or application role to participate in

this task. The Identification Type column of the Starting Participant table displays your selection of user, group, or application role. 5. See Step 4 through 6 of Section 27.3.6.1.1, Creating a Single Task Participant List for instructions on selecting a user, group, or application role. 6. If you are using parallel participant types, you can specify where to store the subtask payload with the following options. ■ Use server settings The SharePayloadAcrossAllParallelApprovers System MBean Browser boolean property in Oracle Enterprise Manager Fusion Middleware Control determines whether to share the payload of subtasks in the root task. By default, this property is set to true. If set to true, the All task participants share the same payload better performance and less storage space option is used. If this property is set to false, the Each parallel participant has a local copy of the payload option is used. To change this property, perform the following steps:

a. Right-click soa-infra and select Administration System MBean

Browser .

b. Expand Application Defined MBeans oracle.as.soainfra.config

Server: server_name WorkflowConfig human-workflow.

c. Click SharePayloadAcrossAllParallelApprovers.

d. Change this property in the list, and click Apply.

■ All task participants share the same payload better performance and less storage space The payload for the subtasks is stored in their root task. This means that the payload of the root task is shared across all its subtasks. Internally, this option provides better performance and storage space consumption. Less storage space is consumed because the payload of the root task is shared across all its subtasks. ■ Each parallel participant has a local copy of the payload 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: