Examples

You can specify a task Due in value in days, hours, or minutes, with an optional clock time.

In these examples, assume that the assigned time schedule for our sample task is Monday through Friday, 9 AM to 5 PM, which means that only 8 hours of work time are available on each business day. Depending on the task Due in value assignment, this time schedule assignment has the following impact when it comes to the task due date calculation:
  1. If you specify the task Due in value as 24 hours, the task is allowed to take 3 days (meaning 3 business days), because each business day contains only 8 hours of available work time.
  2. If you specify the task Due in value as 7200mins or 120hours, this time is divided by 8 hours per business day, based on the time schedule. The calculated task due date therefore moves out into the future, because for every business day available identified by the time schedule, only 8 hours per business day can be worked on the task.
  3. If you specify the task Due in value as 5 days (meaning 5 business days), this means 5 business days as available according to the time schedule. In our examples, all Saturdays and Sundays are excluded, which means that more than 5 days might pass before the task is due.
  4. If a holiday schedule is assigned, and if the assigned time schedule allows the days identified by the Holiday Schedule value to be excluded from the task due date calculation, the task due date moves even further out into the future.
In some cases, the due date calculation for a process instance is different from that of a task instance. See the dW Answers post Why Task Due date is different from BPM due date?