Using Role as Event Destination gives error "An Activity with a client event should at least have one destination."

[#1]

Symptoms

Workflow isn't recognizing all roles when the role is added from the K2 management site directly to a workflow.

After explicitly assigning a role to a workflow from within K2 management site under the workflow role tab, client events that use that role as a destination error out with "An Activity with a client event should at least have one destination."

Diagnoses

Verified:
-Role has users assigned and UMUser SMO Get Role users method returns results for the role.
-Used a list view to display users of the Role to verify the role can be resolved

Compared results when using Workspace versus management site to discover difference in behavior.

Resolution

Confirmed and logged as a bug in K2 Blackpearl 4.7. There are currently two viable options for workarounds. One is to not assign the role directly to the workflow, but rather to let that happen automatically by only selecting the role as a destination for an event and letting the role automatically get added when the workflow is deployed/actioned. The other is to use the Management features within K2 Workspace rather than the Management Site for adding roles to workflows.