Export code modules

  • 23 April 2008
  • 3 replies
  • 0 views

Badge +4
When I export K2 processes to our server, the code modules do not seem to be exported. Process changes are fine, but changes made in the sourcecode of code modules in K2 studio are not going live. Is there any setting that affects whether code modules are automatically exported or not? Any other ideas what is wrong here? Thanks

3 replies

Badge +9
The code changes in the code modules should only affect newly created instances after the export.  Are you saying that the code changes are not happening for newly started process instances?
Badge +4

I assumed that process code changes would not affect running process instances, but code module changes would? Are you saying that the code modules are compiled into each individual process?

Badge +5

Yes that is 100% correct.  A process definition is not only defined by activities on the canvas but also code modules that you create.  Also assemblies that you reference.  This is an excellent feature of K2 2003 because it allows us to host multiple versions of an assembly that coincides with a particular process definition.

 If you want to always run the same assembly across all process definitions than you need to GAC the assembly.  When you GAC and assembly you need to of course be aware of current running process instances and how those may be effected.  What you will find useful is overloading methods which will allow you to put forth new changes without effecting those running process instances.

 
Hope this helps.
 

Reply