Specifying Multilingual Settings Click the Search icon to select the style sheet as an attachment.

Designing Human Tasks 27-59 ■ Maximum Escalation Levels Number of management levels to which to escalate the task. This field is required. ■ Highest Approver Title The title of the highest approver for example, self, manager, director, or CEO. These titles are compared against the title of the task assignee in the corresponding user repository. This field is optional. The escalation policy specifies the number of times the task can be escalated on expiration and the renewal duration. In Figure 27–60 , when the task expires, it is escalated at most three times. It does not matter if the task expired at the LoanAgentGroup participant or the Supervisor participant. Figure 27–60 Escalate After Policy

27.3.9.6 Specifying Escalation Rules

This option allows a custom escalation rule to be plugged in for a particular workflow. For example, to assign the task to a current user’s department manager on task expiration, you can write a custom task escalation function, register it with the workflow service, and use that function in task definitions. The default escalation rule is to assign a task to the manager of the current user. To add a new escalation rule, follow these steps. To specify escalation rules: 1. Implement the following interface: oracle.bpel.services.workflow.assignment.dynamic.IDynamicTaskEscalationFunction This implementation must be available in the class path for the server. 2. Log in to Oracle Enterprise Manager Fusion Middleware Control.

3. Expand the SOA folder in the navigator.

4. Right-click soa-infra, and select SOA Administration Workflow Task Service

Properties . The Workflow Task Service Properties page appears. 5. Add a new function. For example: ■ Function name: DepartmentSupervisor ■ Classpath: oracle.bpel.services.workflow.assignment.dynamic.patterns. DepartmentSupervisor 27-60 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite ■ Function parameter name ■ Function parameter value

6. In the Custom Escalation Java Class field of the Deadlines section, enter the

function name as defined in the Workflow Task Service Properties page for the escalation rule. For more information, see Section 31.3.3, Custom Escalation Function.

27.3.9.7 Specifying a Due Date

A due date indicates the date by which the task should be completed. Note that the due date is different from the expiration date. When a task expires it is either marked expired or automatically escalated or renewed based on the escalation policy. The due date is generally a date earlier than the expiration date and an indication to the user that the task is about to expire. You can enter a due date for a task, as shown in Figure 27–56 . A task is considered overdue after it is past the specified due date. This date is in addition to the expiration policy. A due date can be specified irrespective of whether an expiration policy has been specified. The due date enables Oracle BPM Worklist to display a due date, list overdue tasks, highlight overdue tasks in the inbox, and so on. Overdue tasks can be queried using a predicate on the TaskQueryService.queryTask... API. To specify a due date: 1. In the Deadlines section, select the Action Requested Before checkbox. 2. Select By Duration to enter a time duration or select By Expression to dynamically enter a value as an XPath expression. Note the following details: ■ The due date can be set on both the task using the Create ToDo Task dialog in Oracle BPM Worklist and in the .task file using the Human Task Editor. This is to allow to-do tasks without task definitions to set a due date during initiation of the task. A due date that is set in the task a runtime object overrides a due date that is set in the .task file. ■ In the task definition, the due date can only be specified at the global level, and not for each participant. ■ If the due date is set on the task, the due date in the .task file is ignored. ■ If the due date is not set on the task, the due date in the .task file is evaluated and set on the task. ■ If there is no due date on either the task or in the .task file, there is no due date on the task. For more information, see Section 29.3.4, How To Create a ToDo Task.

27.3.10 How to Specify Participant Notification Preferences

Figure 27–61 shows the General tab of the Notification section of the Human Task Editor when fully expanded. Note: You cannot specify business rules for to-do tasks.