As it seems by briefly reading Workflow Management API documentation, when we use
workflowManagementServer.SetUserStatus(@"K2:K2WORKFLOW\Me", UserStatusses.OOF),
user that executes the API call should be Admin on K2 server. If we use that in SmartForms, users will not be able to configure OOF if the "Impersonation" has been enabled on ServiceBroker unless they are Admins on K2. Would it be wise to expose Out of Office settings through Client API, by using connection.SetUserStatus(@"K2:DOMAIN\Sharer", UserStatuses.OOF);
As it seems by briefly reading Workflow Management API documentation, when we use workflowManagementServer.SetUserStatus(@"K2:K2WORKFLOW\Me", UserStatusses.OOF), user that executes the API call should be Admin on K2 server. If we use that in SmartForms, users will not be able to configure OOF if the "Impersonation" has been enabled on ServiceBroker unless they are Admins on K2. Would it be wise to expose Out of Office settings through Client API, by using connection.SetUserStatus(@"K2:DOMAIN\Sharer", UserStatuses.OOF);