I have a few instances of a process that have thrown an error. I have since tracked down the source of the error, and have deployed a new version with a fix for the bug.

Is it possible to retry the instances of the process that are in error, but force them to use the new version of the process?
If so, how do I go about doing this?

Thanks in advance for any assistance on this!

Hi arduk,

You can use the Process Management view in Visual Studio to repair and redeploy a particular process instance in error to a new version of the process:
-Open Visual Studio on the machine where the K2 Workflow project resides.
-Select View -> K2 Process Management
-In the treeview on the left drill down to the desired Error Profile
-In the right-hand pane select the process instance in error and click the Open button.
-This will open the K2 project/process and you can make the necessary changes to correct the problem.
-Save the project.
-Navigate back to the Process Management tab and click the "Redeploy" button
-Enter a 'Repair Label' and 'Repair Description' as desired and click OK to redeploy the process.

The newly deployed process will only be applicable to the process instance(s) being repaired.  Note that this will not change the default version of the process either.

You may also want to take a look at the following video:
http://www.k2underground.com/blogs/howtok2/archive/2008/07/24/process-error-repair.aspx

HTH
Blake

---

The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.

Hi Blake,

Thanks for the great information - I knew about Process Management, but didn't know that the new version deployed only affected the instances that are in error.

I have one problem with this technique, which hopefully you may be able to shed some light on. I currently have an unrelated problem, in which the datasources of the infopath web form are not updated correctly when you deploy to production (see note 14497 - https://portal.k2workflow.com/support/report/snapshot.aspx?id=14497)

Any idea on what will happen to my forms if I use Process Management to fix the error and then re-deploy? The workaround for this problem is to look at the template for the form in the form library, save it as its source files, and then re-publish it to the form library. I am a little concerned that if I use process management to fix the error, I will then need to use this workaround, which will then overwrite my production form? This would have the potential to stop all of the latest versions of the form from working, so I am a little hesitant to try this.

Thanks again for the info, and if you have any ideas on the best way to go here it would be very much appreciated!

Thanks in advance!

Hi arduk,

Good question.  I believe when you open the process instance in error from Process Management it will only open the .kprx file rather than the entire project and when you re-deploy, the InfoPath form template(s) will not get re-deployed to MOSS.  You may want to confirm this in your development environment.

Thanks

Blake

---

The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.

Hi Blake, thanks very much for getting back to me

Is there any way I can confirm that the form templates are not re-deployed?

It sounds like it might be OK, unfortunately I only have a development and a production environment, so I am not going to be able to test it in my development environment - when I deploy to the development environment, the forms deploy without a problem, it is only when I deploy it to a different (production) site collection that the problem arises.

Regards

Richard

I tested this and this time it did actually open the entire K2 project, so I could see the form template etc. in the Solution Explorer.  However, when I fixed the error and redeployed from Process Management it did not re-deploy the form template to the form library.

---

The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.

Thanks blake.   Good stuff

Awesome - thanks very much for that Blake!

I have now used this to fix all of my processes that were in error - what a great feature (now that I know how it works)!!

Thanks again for you assistance on this - I really appreciate you taking the time to test that for me!

Blake,

We just redeployed a process to fix a specific issue (via process management) and, while the InfoPath form was not deployed, the process itself seems to be tied to the InfoPath form on my local drive.  That is, users that open the task get an InfoPath error indicating that the form template cannot be found at xxx where xxx is the path of the item on my own local drive.  Is that something that you have experienced?  Is there any way to fix it without redeploying the process completely? 

 

---

Tim Byrne
Clarity Consulting
http://www.claritycon.com

Hi Tim,

I have not seen anything like this.  So if I understand correctly, any user that opens a task for the specific process instance(s) that was repaired gets an error referencing the path on the machine where the process was re-deployed via Process Management?

Blake

---

The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.

Blake,

You are correct, that is exactly what we are experiencing.  I was able to resolve the problem by going to the _ProcXml table and modifying the Value and MetaData values from href="c:\...." to href="http:\\...".  This fixed all new requests (after restarting the K2 service).  As for my existing requests, I located the infopath xml in the list where they are stored on SharePoint (configured during the InfoPath Integration Wizard) and made the same modification to them.

I haven't reported this as a bug, I chalked it up to not fully understanding what a repair process does when there is InfoPath integration involved.

 

---

Tim Byrne
Clarity Consulting
http://www.claritycon.com