This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
This issue occurs when you have integrated a SharePoint list with data and forms, and you then use the SharePoint Integration wizard in K2 Studio or K2 for Visual Studio to add a workflow to the list. After packaging and deploying the solution using the SharePoint UI to a new list on the same K2 environment, the workflow on the original list is lost and only functions with the new list.
K2 Studio and K2 for Visual Studio processes can only be integrated with a single list. This is because they do not have a unique system name, and therefore the workflow association moves from the original list to the new one on deployment. This does not occur for workflows created using the SharePoint UI, only for workflows created in K2 Studio and K2 for Visual Studio.
There are two workarounds for this issue:
- Create the workflow using K2 for SharePoint rather than K2 Studio or K2 for Visual Studio.
- Create a new K2 Studio or K2 for Visual Studio workflow to integrate with the original SharePoint list and deploy it.