Hello,
I want to voice that I am not happy with the option for migration in K2. When a new version of K2 comes out we are required to upgrade within a certain amount of time or we will no longer be supported by K2 Helpdesk. The upgrade options are not easy and require us to fix or rework our current processes. Currently we are looking at upgrading to K2 Five. We are on 4.6.11. If we upgrade in place to 4.7 we take the risk of our applications breaking which require us to spend a large amount of time "putting out fires". We cannot package and deploy from 4.6.11 to 4.7 because of the difference in the package and deploy tool. We cannot package and deploy from 4.7 to K2 Five because because the package and deploy tool is incompatible. If we upgrade from 4.7 to K2 Five we will not be able to edit our workflows and we will encounter errors in our applications.
Our only real option is to do a fresh install of K2 Five on a new server then sacrafice pending workflows to rebuild these applications in a new environment. The second option is to run a dual production environment. One with K2 Five and one with 4.6.11. This would require us to buy another production license. (Probably part of the plan). So with all of this said we have the option to continue on 4.6.11 and simply stop paying a maintenance fee and forego support or we can upgrade to 4.7 and spend our time fixing problems and when that support runs out we stop paying annual maintenance and stay with 4.7. The other option is we purchase another Business Process Management solution from another company that does not put their customers in this kind of corner. Maybe we simply use Microsoft Flow. Either way the thought is what will happen if we migrate all of our applications to K2 Five which will take a lot of time to rework. Then K2 gives us K2 5.2. Are we going to have to rework all of our applications again? Are we stuck redeveloping our applications from here on out? What happens when hundreds of processes need to be migrated?
For our company this is not going to work. The processes we build are important and it will not be acceptable to have down time and it will not be fair to our users to redevelop these processes every time there is an upgrade. With the upgrade required or we will lose support. I do not know any other company that puts their customers into this kind of situation. So with all of this said we are at a point where we need to consider ditching K2 for another product (there are dozens) that will take into account the impact of future migrations on their customers or we continue with K2 and take a chance that future updates will put us in the same situation.
We do not like the idea of buggy upgrades and testing in production. It feels like these upgrades are put into production for the customers to test. This is not how we do business.
Thanks,
Bryan Peters