1. Developing SOA Applications with Oracle SOA Suite
  2. Using the Human Workflow Service Component
  3. Configuring Human Tasks
  4. Escalating, Renewing, or Ending the Task
  5. How to Specify a Policy to Expire

How to Specify 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 drop-down list of the Deadlines section, select Expire after, as shown in Figure 29-51.
  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 29-51 indicates that the task expires in three days.

    Figure 29-51 Expire After Policy

    Description of Figure 29-51 follows
    Description of "Figure 29-51 Expire After Policy"

    Note:

    The escalation time is limited to future times that are before the year 2286. Using a value that is greater results in runtime errors. The technical limit of the future value is 9,999,999,999,999 milliseconds since January 1, 1970, 00:00:00 GMT.