Click the Assignment tab. Click the Add icon to assign reviewers or error assignees, as shown in

Designing Human Tasks 27-57 – In a parallel workflow, if the parallel participants are specified as a resource, a routing slip is created for each of the resources. The expiration duration of each created routing slip follows these rules: The expiration duration equals the expiration duration of the parallel participant if it has an expiration duration specified. The expiration duration that is left on the task if it was specified at the routing slip level. Otherwise, there is no expiration duration. – If parallel participants are specified as routing slips, then the expiration duration for the parallel participants is determined by the routing slip.

27.3.9.2 Specifying a Policy to Never Expire

You can specify for a task to never expire. To specify a policy to never expire: 1. In the dropdown list in the Deadlines section, as shown in Figure 27–56 , select Never Expire .

27.3.9.3 Specifying a Policy to Expire

You can specify for a task to expire. When the task expires, either the escalation policy or the renewal policy at the routing slip level is applied. If neither is specified, the task expires. The expiration policy at the routing slip level is common to all the participants. To specify for a task to expire: 1. In the dropdown list of the Deadlines section, select Expire after, as shown in Figure 27–58 . 2. Specify the maximum time period for the task to remain open. The expiration policy for parallel participants is interpreted as follows: ■ If parallel participants are specified as resources in parallel elements, there is no expiration policy for each of those participants. ■ If parallel participants are specified as routing slips, then the expiration policy for the routing slip applies to the parallel participants. Figure 27–58 indicates that the task expires in three days. Note: When the parent task expires in a parallel task, the subtasks are withdrawn if those tasks have not expired or completed. 27-58 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 27–58 Expire After Policy

27.3.9.4 Extending an Expiration Policy Period

You can extend the expiration period when the user does not respond within the allotted time. You do this by specifying the number of times the task can be renewed upon expiration for example, renew it an additional three times and the duration of each renewal for example, three days for each renewal period. To extend an expiration policy period: 1. In the dropdown list of the Deadlines section, select Renew after, as shown in Figure 27–59 . 2. Specify the maximum number of times to continue renewing this task. In Figure 27–59 , when the task expires, it is renewed at most three times. It does not matter if the task expired at the LoanAgentGroup participant or the Supervisor participant. Figure 27–59 Renew After Policy

27.3.9.5 Escalating a Task Policy

You can escalate a task if a user does not respond within the allotted time. For example, if you are using the escalation hierarchy configured in your user directory, the task can be escalated to the user’s manager. If you are using escalation callbacks, the task is escalated to whoever you have defined. When a task has been escalated the maximum number of times, it stops escalating. An escalated task can remain in a user inbox even after the task has expired. To escalate a task policy: 1. In the dropdown list of the Deadlines section, select Escalate after, as shown in Figure 27–60 . 2. Specify the following additional values. When both are set, the escalation policy is more restrictive.