K2 worfklow and its Versioning

Hi IPO

Firstly, you can download the sourcecocde for each workflow version from the K2 workpace. Next to each process version is a download link.

I am not sure if you are talking about source control, or versioning of your solutions (or both)?

One approach to source control and versioning is to use Package and Deploy (P&D). You can create a package at any point which will wrap up all K2 artifacts and store this package somewhere appropriate. Typically you will have a package for every version of a solution you release to production. Granted, this will not allow you to do things such as compare versions and branching etc, however you can redploy a package if you want to revert to an earlier version.

Using P&D for solution versioning is a tricky subject because it depends on what has changed between versions as to how easy it is to revert to an earlier version. For example, if you make a change to a database and then a K2 smartobject, if you try and revert to a previous version (redeploy an earlier package) you will need to know to change the database also - which will not be included in the P&D package.

You can also use TFS or other source code systems inside of Visual Studio for your workflows and SmartObjects (provided they are developed in VS) but this of course does not include your forms/views and other artifacts.