Configuring the Error Assignee

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: 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.