Select Use External Routing from the list. Click the Edit icon, as shown in

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 27-56 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite checkbox, then those settings take precedence over settings specified in the Deadlines section routing slip level. You can also specify that a task be escalated to a user’s manager after a specified time period. For more information, see Section 27.3.6.1.2, Specifying a Time Limit for Acting on a Task. Figure 27–56 Human Task Editor — Deadlines Section

27.3.9.1 Introduction to Escalation and Expiration Policy

This section provides an overview of how specifying the expiration duration at this level makes this setting the expiration duration of the task across all the participants. For example, participant LoanAgentGroup and participant Supervisor have three days to act on the task between them, as shown in Figure 27–57 : Figure 27–57 Expire After Policy If there is no expiration specified at either the participant level or this routing slip level, then that task has no expiration duration. If expiration duration is specified at any level of the participants, then for that participant, the participant expiration duration is used. However, the global expiration duration is still used for the participants that do not have participant level expiration duration. The global expiration duration is always decremented by the time elapsed in the task. The policy for interpreting the participant level expiration for the participants is described as follows: ■ Serial Each assignment in the management chain gets the same expiration duration as the one specified in the serial. Note that the duration is not for all the assignments resulting from this assignment. If the task expires at any of the assignments in the management chain, the escalation and renewal policy is applied. ■ Parallel: