Symptoms
When building a K2 workflow in K2 for Visual Studio or K2 Studio, a user has the ability to CC client event notifications to other users within their user base. One of the objects you can use in place of an Active Directory Group or User is a K2 role. However, in K2 Blackpearl 4.6.8, if you CC a Role with two or more users, the task itself will get assigned properly according to the destination rule that is configured, but the client event notification itself will not be sent.
Diagnoses
This was found to be a bug with how K2 concatenates the emails for the users in the Role, hence creating a problem when that email destination is sent through the specified mail protocol. You will see an error in K2 to the effect that there was a failure sending the message.
Resolution
A fix can be supplied for this issue. The fix essentially concatenates the Role users' emails properly so that whatever mail protocol being used to send Client Event Notifications can properly understand the destination. The following bug was logged for the behavior to be fixed fully in 4.6.12:
Bug 564703: Client event notification: Add a role with more that one user in it to be CC'ed on the client event notification fails.
Bug 564720: [Coldfix item 469] Client event notification: Add a role with more that one user in it to be CC'ed on the client event notification fails
After applying the fix, it is important to know that there must be an update of the design templates in all processes displaying this behavior, as well as an update to the filter used for the role in the CC field (double click the role item in the CC field for the client event notification, hit next twice until you get to the List Options screen, choose "Return all results that match filter", finish), then a redeploy.
Please contact K2 Support in order to get a copy of the fix for 4.6.8, or if you are experiencing this behavior in later versions of the product.
