example of scheduling

For an activity to arrive on the work list of an employee several procedures must be performed.

Initiating a business process

For an employee to be able to initiate a business process via the Worklist Handler two conditions must be met, the employee must be linked to the role that matches one linked to the business process and this role must be linked as a initiator role.

Scheduling of activities

If an employee initiates a business process in the Worklist Handler, the activities of the business process will be scheduled to the employees that have a role that matches a role linked to the activity.

Starting an activity

An employee can start an activity (work item) via the Worklist Handler.

Important

The activity that receives the ready answer of a triggered business process, must not have extended scheduling options modelled. If you do model extended scheduling options correct handling of the triggering business process can not be guaranteed.

Via the extended scheduling options of an activity you can define conditions based on which the activity instances are scheduled to the employees.

How to get there:

  • Start the Business Processes (tgbrg5500m000) session.
  • Select a business process and start the Enterprise Modeler Editor.
  • Double-click the activity of which you want to model the extended scheduling options.
How the extended scheduling options work:

The first three options on the Extended Scheduling tab exclude each other. These options are:

First of all, the employee that initiates the business process is automatically the process instance creator and the process instance owner.

So if you check the Process Instance Creator or Process Instance Owner check box the activity is scheduled to the employee that initiated the business process.

The employee will remain the process instance creator until the process instance has finished.

This means that if you check the Process Instance Creator check box the activity instance is always scheduled to the employee that initiated the process instance.

An employee will remain the process instance owner until an activity instance is carried out by another employee and the Make Executor Instance Owner check box is selected. The employee that carries out the activity instance will become the new process instance owner.

Another option is the Executor Specific Activity check box. This option is very handy if the activity may only be executed by an employee that executed a previous activity. A reason for this could be that the employee needs some information that was processed in this previous activity.

Then there are two options left:

  • Schedule the activity instance to a specific employee group
  • Schedule the activity instance to the employee with the least amount of work on his or her worklist.

The first is set if you select the Specific Employee Group check box. All the employees in the selected employee group will receive the activity instance in his or her worklist. Of course only if they have the correct role!

The second is set if you select the User with Least Workload check box. In this case the employee with the least amount of work on his or her worklist will receive the activity instance in his or her worklist. The amount of work is calculated based on the employment percentage and the number of activity instances on his or her worklist.

Above two options work in combination with the first three, each other excluding, options.