Online Help for Oracle SOA Suite

3.20 Human Task Editor - Deadlines Page

Use to specify the expiration duration of a task. How?

Element	Description
Task Duration Settings	Specify the expiration duration of the task: Never expire: Specify for a task to never expire. Expire after: Specify for a task to expire after a certain date. You specify the maximum time period for the task to remain open. 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. Renew after: Renew the expiration period for a task when the user does not respond within the allotted time. The renewal policy specifies the number of times the task can be renewed on expiration and the renewal duration. Escalate after: Escalate a task (for example, to the user's manager) after a certain date if the user does not respond within the allotted time. You specify the number of management levels to which to escalate the task and 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.
Custom Escalation Java Class	Specify custom escalation Java classes. 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.
Action Requested Before	Select to enter a due date for a task. A task is considered overdue once 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.

Element

Description

Task Duration Settings

Specify the expiration duration of the task:

Never expire: Specify for a task to never expire.
Expire after: Specify for a task to expire after a certain date. You specify the maximum time period for the task to remain open. 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.
Renew after: Renew the expiration period for a task when the user does not respond within the allotted time. The renewal policy specifies the number of times the task can be renewed on expiration and the renewal duration.
Escalate after: Escalate a task (for example, to the user's manager) after a certain date if the user does not respond within the allotted time. You specify the number of management levels to which to escalate the task and 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.

Custom Escalation Java Class

Specify custom escalation Java classes. 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.

Action Requested Before

Select to enter a due date for a task. A task is considered overdue once 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.