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.
I think there is some confusion and misunderstanding here
I am not sure what you mean by breaking applications when upgrading from 4.6.11 to 4.7 or to K2 FIVE.
Have you upgraded to K2 4.7 already and experienced issues with your existing applications?
If you upgrade from 4.6.11 or 4.7 to K2 FIVE you cannot edit the old processes in the new workflow designer but you will still be able to edit your processes in legacy mode and you will still have K2 Studio, I am not sure where you got the information that you cannot edit your existing workflows in K2 FIVE
We have asked your customer account manager to reach out to you to have a discussion about this and give you all the required information
The real frustration for me is K2 Five is a "work in progress" and honestly we can't use it for our projects yet until some features are included. I don't think you should stop supporting legacy tools until you complete the product
I one of the presentations for K2 Five, the sales mention a customer with 600 K2 Forms.... I can't believe if those forms are in K2 4.6.11 got upgraded to k2 4.7 then for the transition to K2 Five you know will be forced to re-work on 600 apps if you choose to edit, this meand creating a K2 Five Workflow and re-building the old to the new.
If you don't do that will be only for 1 year. then you are facing the same issue. K2 Five should have a broader comprehensive path for upgrade. seems like is to much re-work on the same thing just to allow upgrade. makes you wonder what will happen in 2 years if you have to Re-Work every single think you build?. then all the cost savings are no longer going to be there.
Let me chime in on this topic.
First off, great post and the sentiments expressed are exactly like what i felt when we jumped from an earlier version to 4.7 ( i think i even posted about the experience on here)
We had broken workflows, forms not working, data labels not being transferred, SMTP Mail stopped working in hybrid mode, an important custom process stopped working which we were told would not be supported moving forward, it was a horrific time for us.
Like you said, it did feel like we the customers were the Beta testers for the new verison, then having to wait weeks while bug fixes were being created, in the meantime getting ear ache from our users.
Reading Bryans post gave me flashbacks, because i lived it.... and that was supposed to be a simple upgrade without any issues with legacy forms/workflows like K2 Five...
Having got over that and now we have v4.7 tuned to perfection, we are gearing up to move to K2 Five... again this is purely because of the schedule that K2 put forward to not support older versions, not because of us wanting to move.
There is no way i am going back and re-visiting all our current Live Smartforms and Workflows again (which took years to get this point) and re-creating them again in K2 Five, so our hands are tied and can only go one route.
That route is New Server with new OS, SQL etc etc -> Install v4.7, spend ages migrating all the forms/data/workflows/config file customisations, mail etc etc across -> Expect lots of problems (because there will be) and then upgrading to K2 Five and whatever unknown issues that will bring.
Why couldn't K2 provide a tool to migrate K2 v4.7 or older (which K2 now refer to as "legacy" already) to K2 Five?
As mentioned, you can still edit the workflows using the legacy K2 Studio, not sure about the Smartforms, can v4.7 forms still be edited using the Web Designer in K2 Five??? I'm not even sure how easy the New Forms/Workflow design tools will be in K2 Five, time will tell.
Either way, I have a feeling it's gonna be a pain and i'm stocking up on Energy Drinks and chocolate :-)
From a business point of view, you have to weigh up the amount of time taken to troubleshoot upgrades vs development time...
In a nutshell, K2 is amazing when it works and you're in the midst of form design and workflows there is nothing better, but when it comes to applying any form of Cummulative Update or Version, i get nervous, very nervous.
Not sure why this far along K2 still has that air of uncertainty, personally i've felt like a K2 employee Tester when any form of upgrade is required. Hope this is something that K2 can work on sooner than later.
Hopefully K2 Five upgrade goes ok, but i'll keep you all posted. However, i will question K2 as a product if i have a similar experience as last time.
In the meantime, it would be great for all those that have upgraded to share their experiences and any pitfalls or potential problems to look out for.
Great comments about the K2 upgrades. I lead a team of K2 developers at our company and find it's a great tool for application development. K2 upgrades are a different story. All the situations mentioned above, we have also experienced. We are on 4.7 and plan on going to K2Five early 2019. Also pushed off to 2019 because the extensive testing we're going to do in a Dev environment with K2Five. We will spend a large amount of time regression testing our app before even getting to the QA environment. More time than we care to but, the confidence factor is not there. We got burned on the last 2 upgrades with light regression testing and were fixing Production SmartForm issues (refactoring) for weeks. Learned our lesson there. K2 can't believe it's taking us this long to upgrade and it should be a simple process.
If anyone has any K2Five upgrade experiences recently, good or bad, would be appreciated if they shared. thanks!
I am totally agree with you !! I am very much unhappy with migration .
I have only one sentence that "You can't move the soltion on k2 5 easily as workable like on current state." So either dont do it or re-deveolop in k2 5 .
#Unhappy # Timetaken #NoWorkablesolution.
I totally agree with every post. It is good to know that we are not alone in this, what I now call "Struggle" (the word migration does not have any meaning here anymore). We to are in the Struggle(migration) phase from 4.7 to now 5.1 FP12.
I feel like we started the migration way to early and should have waited for the complete bug fixing. We are also at the same time "migrating" applications from SharePoint on-Prem to SharePoint online and for one application, we have run into a show stopper and are now getting information from Support that what we are doing is not supported :-(). We also have learned that migrating the old workflows to the new workflow engine is not possible, reworking the workflows is the only solution, which in turn is causing the budget to run over (Finance is not happy with us) - ROI - forget it!
While I believe that the application in itself is very good, I am beginning to run out of patience and have begun to look at alternatives, Nintex and the like.
All the comments are exciting me to share my more experience.
Here is the list of issue we are facing during migration.
1. SharePoint solution from on prem to Online is not possilble .
2. Legacy workflow migration doest not support at all.
3. You can't user any exiting DLL based solution.
4. All the workflow cusotm code event are breaking.
5. Manaul workflow deployment is also not possible say's smart object not found.
6.SQL Azure connection for k2 data base was an stopper , Installation was not working.
7.Custom functions are removed ( so not supported )
8. Activity destionation user event is not supported so all the older mapping get loss.
9. Lithium theme was breaking , was not working at all.
10.After migration k2 category was breaking for soltution .
11. Duplicate email was sending in k2 5 while send email.
12. View flow navigation doest not work for IPC .
13. YOu can't navigate to sub process by clicking on view flow as previous versions.
14. IPC was taking 3 hours to start child workflow.
15. Redirect was not updating the user's in view flow .
I have encountered this much error till now . Many more are fixed and many more we are getting every day...