Setting the due date and work schedule for a BPD

The due date for a process instance is the expected date and time that all activities related to a process instance should be completed. At run time, this due date is used to calculate whether a process instance is on track for a timely completion. The due date is affected by the work schedules of the users who receive the tasks involved in the process.

About this task

By default, each instance of a business process definition (BPD) is due 8 hours after it is started. The actual due date for an instance is affected by the work schedule specified for the BPD.

The default work schedule for all BPDs is specified in the 99Local.xml configuration file in the following directory, where server_type is either process-server or process-center: PROFILE_HOME\config\cells\cell_name\nodes\node_name\servers\server_name\server_type\config\system. If you do not specify a work schedule for a BPD, or if you leave the settings at use default, date calculations for instances of the BPD are based on the <default-work-schedule> in the configuration file.

You can specify your own due date and work schedule for each BPD.

Procedure

In the Overview tab for the BPD, specify a value in the Due in field that reflects how long the entire process instance is expected to take to complete. If you select Days for the duration, you can also add hours and minutes to the elapsed time, for example 2 days, 4 hours, and 30 minutes.
In the Work Schedule section, specify the working hours that users are available to complete work.
- The Time Schedule specifies the normal business hours that work can be completed. For example, if you expect the users completing the task to be available Monday through Friday, 9 AM to 5 PM, you can select this schedule from the list.
- Timezone specifies the timezone that you want to apply to running instances of the current BPD. All standard time zones are available.
- The Holiday Schedule is a list of dates that are exceptions to the normal time schedule.
If you use the default values for any of these fields, the values are taken from corresponding settings in the 99Local.xml file.

Tip: If you expect some activities to be completed by users with a specific work schedule, you can specify a different work schedule for that activity in the Properties view for that activity.
For all of the work schedule values, you can use a JavaScript expression with predefined variables. You can enter either a String (or String-generated JavaScript) or a JavaScript expression that returns a TWTimeSchedule or TWHolidaySchedule variable. If you use a String, then IBM® BPM looks up the schedule by name according to those rules. If you use one of the TWSchedule variables, then IBM BPM assumes that the schedule is filled in appropriately. To view the parameters of the TWTimeSchedule or TWHolidaySchedule variables, open them from the System Data toolkit.
You can also write an IBM BPM service to dynamically set the overall work schedule for a BPD and store the entire work schedule in the TWWorkSchedule variable. The TWWorkSchedule variable includes parameters for timeSchedule, timeZone, and holidaySchedule. To view the parameters of the TWWorkSchedule variable, open it from the System Data toolkit.