I meant to add more but had to leave the office suddenly.
There are a couple of other ways to get the email notification to only go to the intended recipients. It may depend on where in the path this takes place. If it's on initial creation, then I'm not sure. We're setting our CRs up right now and the intent is to make every downstream group look at every CR and determine if they need to give input or not (rather than let the creator or some other person outside their department make that determination for them). If the intent is for the team selection to take place during an assigned activity, then the two things that come to mind are Transition & Routings or the Set Up Participants tab.
For the Transitions & Routings, the assignment page (the one with the Complete Task button) could have a list of check boxes. The assignee simply checks a box for each group or person that is to get the Change Request. From that assigned activity, one or more action paths are fired off: one for each chosen group. This does make for a cluttered workflow template, but that's really only something the admin sees anyway (IME). Then, when the next assignments are started, with the Activity tab's 'Send Notification' box checked, the new assignee gets whatever message is in the Instructions field.
The Set Up Participants tab keeps the workflow clean while allowing the assignee to choose who gets the next action in the path. The cludgy part in my experience is that the same assigned activity is used for all participants. This means generic instructions like, "Review Change Request and give input". That's okay for early in the flow when it's an overview list like estimates for dates, tools, man-hours, etc. Later in a workflow when you might want to explicitly define the work each participant needs to do is when this method falls off in usefulness.
