We have built a workflow that has the destination of the next activity chosen by the user in the previous user event.
The code in each activity destination rule looks something like this...
public void Main(ref DestinationRuleContext K2) {
K2.ResolveQueuesToUsers = true;
K2.Destinations.Add(DestinationType.User,"domainusername");
}
(there is code that figures out the username, but I've left that out).
The issue we have hit is that each user requires admin privileges on the workflow for the above to work, which is totally unexpected. Any ideas why ? Looking at the code generated by a normal destination rule - such as "Send to Originator" has no special configuration for security...
Any explanation would be great. Obviously we don't want to give all users admin privileges.
Jonathan Beckett