Brief description of each plan option of K2

Here is a brief description of each plan option. There are a lot of other settings that will play a role in the outcome of the following. 

Options such as:
- Slot count or Slot per Destination
- Resolve Role or Slot per role
- Dynamic Roles 

Destination Instances
- Plan per Destination works exactly like K2.net 2003. The events will be executed for each user specified in the destination rule. That is why your wizard, only works in this option.
- The ActivityInstance will have a list of ActivityInstanceDestinations, one for each user and each ActivityInstanceDestination will have a list of EventInstances for each event.
- The User property is available here, because each user has its own ActivityInstanceDestination.

Slot instances 
- Slot instances doesn’t have users. 
- When the Activity is configured for slots, it will execute the events for the number of slots specified. Almost like a FOR LOOP 1 to 5. 
- Slot Instances is very much the same as Plan per Destination, except that there are no users. K2.net 2003 users normally added dummy users to simulate this. 

Single Instance
- This option is the default. The activity will execute the events only once, and not for each destination added in the Dest Rule. 
- With single instance, you do not really have a known list of users, because of Dynamic Roles and Groups. And While the client event is active, users can be added or removed from the single task item via Delegation. Which will not fire your mail event code.
- Keep in mind that the Destinations for an activity can be a Role, Group or User. (Groups only available in 807).
- If you have a client event, that there will only be one Task Item (Serial Number)
- The ActivityInstance will only have one ActivityInstanceDestination which is a container of one or more EventInstances.
- The ActivityInstanceDestination will in fact have a list of destinations.
- The ActivityInstance will have one or more WorklistSlots, which will collect the data from the destinations as they execute actions and complete or Update datafields. 
- For your sample down below, There will be one ActivityInstance for DefaultActivity, and the events will only execute once, that leaves you with one ActivityInstanceDestination with 2 event Instances, one for mail event and another for the Client Event.
- Custom Notifications on the EventBus will solve your problem. It reacts on Events raised by the K2 Workflow Server, as soon as the user receive rights to a task item, you can execute a custom event, in this case, you will send out an email. This will guarantee the correct results each time.