The introduction of BCC to the SendEmail functionality causes issues for solutions created in previous versions.
In SR2 the Visual Script Activity displays an additional parameter for BCC in existing solutions but this is at the bottom of the parameter list. The SendEmail activity expects BCC to be the third parameter and therefore uses the parameters in an incorrect order. Solutions will deploy OK if the BCC parameter is set but the SendEmail functionality will fail.
The resolution is to remove the existing activity and replace with a new one which now has the parameters in the correct order. Presumably a similar change will be required to coded implementations.
It would have been nice if the designer could have picked up the correct ordering of parameters so that only the new parameter needed setting, even better if the new parameter had been optional and avoided the need for a code change.
Perhaps this kind of information could be highlighted in release notes and installation instructions in future.
