Things just BLEW UP the other night. I connected to the development server, opened my solution in K2 Studio, started to edit, and BLAMMO! Everything went black.
Administrators had to rebuild my blown profile on the server. Once I was able to get into the desktop again, I figured I should have been able to drop shortcuts to K2 Studio and Visual Studio onto my desktop. No big deal, right?
I was able to open K2 Studio, load my solution, but was surprised to see that the solution was not connected to the (local) development environment.
I was even more surprised when anything I tried to do that was related to the server (like open an IPC, for example) yielded a nasty “Primary Credentials Not Authenticated” exception that threw me out of K2 Studio completely.
We have a demo instance and a production instance of a particular workflow. I got a frantic call from one of the business people telling me that she didn’t have access to all of the roles in the demo instance that she does in production.
I verified this and attempted to correct it by assigning her to the various additional roles. When I asked her to close her browser, then re-open it and navigate back to her worklist, no change had been made.
I started a dialog with K2 Support a few days ago to gather some requirements for adopting SharePoint 2013 as part of our Business Process Management strategy.
One element of managing workflows through the K2 Workspace that has always been a little tricky has been the addition of users to a role. There are some details about it which seem to me to be easy to miss. I’d like to help with that. Continue reading