I was so delighted to discover my favourite k2.net 2003 feature “repair error” in k2[blackpearl]. This little cutie appears in VS.NET under the View menu, named as “K2 error repairing”. UPDATE: It is now called “Instance Management”
When you launch this it allows you to connect to your choice of K2 environment and pull down the process instances that are in error states. You can sort them by error profiles.
Once you select an error’ed instance it shows you the process flow in graphical form 🙂 and you can see where the error is happening. This is a great enhancement! You can then open this instance, which loads the solution into VS.NET and allows to look at the code where the problem is occuring.
You can make any relevant changes and apply them to the selected instance OR all the running instances with this error.
Pretty cool, huh?
UPDATE: here’s a recent video on how to repair workflow errors
2 responses to “Fixing Running Workflow Instance Errors with K2[blackpearl]….”
[…] I also showed this class how they could use the process management plug-in to hookup to an error’ed process instance and debug it while re-trying it. […]
This is really cool, MUCH better than the crappy dialog in the server manager in K2 2003. The problem I have though:
1. How do you debug processes?
2. How do you see the data inside the error’d process? (eg in K2 2003 you look in the workspace “all processes” report and drill down and are able to see process and activity level data per process)
You must log in to post a comment.