Advice for migration of custom solution to K2 Cloud?

Good day Sajna_M

When building applications either in or targeted for K2 Cloud, customers should be aware that the following features available in on-premises deployments of K2 are not currently supported in K2 Cloud.

When looking to deploy on-premises K2 applications to K2 Cloud, these items will need to be removed or will be excluded from the K2 Cloud deployment package.

 USAGE OF NON-MICROSOFT AZURE ACTIVE DIRECTORY IDENTITIES K2 Cloud utilizes Microsoft Azure Active Directory (AAD) for authentication and will not resolve any other identity provider including deployments of Active Directory (which is common amongst K2 on-premises customers).

If customers deploy applications into K2 Cloud that contain non-AAD identities within application assets (i.e. in a workflow Task Destination that is configured for DOMAINUSER or DOMAINGROUP) these assets may not operate as expected or as they did in the on-premises environment.

Customers that utilize identities this way will need to refactor those assets to account for AAD-based identities.

LEGACY WORKFLOW DEFINITIONS K2 Cloud does not allow for legacy design tools such as K2 Studio or K2 for Visual Studio to deploy assets into K2 Cloud. Additionally, K2 applications that contain workflow definitions designed in legacy designers cannot be deployed into K2 Cloud via Package and Deployment.

Customers will need to remove any legacy K2 workflow definitions from a K2 application prior to deployment into K2 Cloud.

K2 CUSTOMIZATIONS The following customizations are not currently available within K2 Cloud:

• Custom K2 SmartForm Controls
• Custom K2 SmartForm Themes
• Custom K2 SmartObject Service Brokers
• Custom User Managers
• Custom Inline Functions
• Custom code

Some customers have decided to implement custom code within K2 applications – often as ‘code behind’ in K2 workflow definitions – and will need to refactor the location and access to this code if it is still required for applications in K2 Cloud.

One popular design pattern as solutions move to the cloud is to encapsulate this code in a web service; K2 Cloud can integrate with SOAP, WCF, OData and REST-based web service endpoints.

 Once the code is exposed as a web service it can be surfaced in workflows, forms and views within K2 Cloud.

Should you find this information relavant and simulteneosly useful please mark as "Kudo and/or Accepted Solution ", as this will  help other k2 users on upgrading.

Regards;

Dumisani

K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member