Gabriel does a great job explaining the default activity planning model on this thread (http://k2underground.com/forums/thread/20262.aspx). I've extracted the pertinent part here:
"The default creation style for an activity in BP has changed from a 'plan per destination' to 'plan once'. I assume for this reason the ActivityInstanceDestination if not available. I've not confirmed this, but try the following to see if my suspicion is right. When on the destination rule, click back and then select 'Advanced wizard view'. On the Activity planning page, select 'Plan per destination - all at once'. This will force the workflow server to create an activity destination instance for each destination and put each activity instance in the context of the destination(s). Note: You have to be aware of the result of planning per destination. For high performance systems where multiple users participate in an activity (i.e. call center style queuing), the performance impact of planning per destination should be considered"
The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.