Skip to main content

My 5 yr old process now has 7 different versions, all of which have active instances. I have a need to make a few code changes in some succeeding rules, but need to make it apply to all versions.


Is there any way to directly modify the code without causing havoc?


If I could force an error in the succeeding rule of an activity then I would have access to the code to modify it (for that process version). My destination rules read a db to get the destination user, so I can put a bogus userid in the db and when K2 tries to send it's client notification email it will throw an error.  But how can I force an error in the succeeding rule? I'm using Infopath ... could I do something there that would force an error in a succeeding rule?


I have developed and tested my new succeeding rule code block in my development environment, and need to apply that specific block of code to all production versions. Could I do a sql update, setting the _code value = to the value in the dev _code table?


Thanks for any help you all can give me.

It could be done (not supported) but try it in non-production environment first.


EDIT:  The following info about migration only applies to K2 blackpearl and this thread is K2.net 2003. Leaving the content just in case a blackpearl customer stumbles across this:


Have you thought about deploying the updated process as a new version and migrating all the existing instances to the new version using the management API? The are definately some serious considerations to think about when doing this but might be something to look into. 


The _code table is the place to update but might invalidate your support contract. I suggest you log a support ticket to get someone to take you through the process.


Otherwise make sure you test your changes properly in a dev/test environment.


HTH


Reply