With the release of K2 Five, we will be removing support for several third-party products, as many of these are product versions no longer supported by the original product vendor. As such, any issues found with these older versions will not be eligible for code fixes by K2.
If you are installing a new, clean K2 environment, you should ensure that you are on supported versions of technologies required for your installation, such as Windows operating systems or database versions.
If you are using any of the technologies flagged as Blocked by Installer, you will not be able to upgrade existing environments or install on new, clean environments until you have upgraded the technology to a supported version.
If you are upgrading your existing K2 environment, you will be able to do so as long as the technology version is not flagged as Blocked by Installer. However, issues found related to the underlying technology product will not be eligible for code fixes.
If you have solutions that integrate with older, no longer supported technologies, you should consider upgrading those systems and modifying your solutions to use the updated, supported integrations.
If you absolutely must remain on a technology that is blocked by the K2 installer, you cannot upgrade to K2 Five. You may remain on K2 4.7 until such time you can move onto a supported technology and rebuild your processes and forms that rely on that integration.
Legacy components are not installed with clean K2 Five installations. For upgrades from K2 blackpearl, legacy components are still supported with K2 Five (for example, K2 Studio or the Silverlight designer). They will be marked as legacy, but you can still open support tickets about these components and we will provide code fix support through the K2 Five support window.
When you upgrade your environment, if you have one of the blocked components or technologies listed below, you cannot proceed with the upgrade. You must remove the blocked component first.
K2 integrates with InfoPath using web services provided in SharePoint 2010. Since InfoPath and InfoPath Services did not have a remote client API released with the 2013 wave of Microsoft products, K2’s InfoPath Integration remained with the web services and SharePoint 2010 solution. K2 does not integrate with the InfoPath client, only through the K2 web service component.
K2 Five's release blocks solutions built with SharePoint 2010 and only supports native SharePoint 2013, SharePoint 2016, and SharePoint Online integrated solutions that use the remote client APIs for integration. Therefore, any InfoPath solutions, either using InfoPath 2010 or InfoPath 2013 in 2010 mode, are no longer supported. You will be blocked when upgrading to K2 Five.
To remain supported, K2 encourages our customers to upgrade to a supported release. This will ensure that you are able to receive code fix support if necessary. For more information about our product support policy, see the K2 Product Support and Release Strategy at https://help.k2.com/k2releasestrategy.
With K2 Five, the following will apply:
Please contact your K2 Account Manager should you have any specific questions.
K2 Product Team