How to Specify a Due Date

A due date indicates the date by which the task should be completed. 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 29-49. 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, filter 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:

In the Deadlines section, select the Action Requested Before check box.
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 box 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.

Note:

You cannot specify business rules for to-do tasks.

For more information, see How To Create a ToDo Task.