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.
K2 for SharePoint applications may consist of several core application elements, such as SmartObjects (“Data”), Forms, Workflows and Reports. These applications could also include or depend on other artifacts and elements such as external data sources, SharePoint entities, non-SharePoint SmartObjects and more. When you need to manage these applications over their lifecycles, for example packaging and deploying applications between SharePoint and K2 environments, or updating application elements, or managing dependencies, there are some best practices and considerations to keep in mind that will assist you to do so.
These whitepapers describe how to plan and manage the lifecycle of developing, packaging, deploying and maintaining K2 applications for SharePoint. The whitepapers cover multiple scenarios, describe best practices to package and deploy K2 artefacts (including using Package by Reference), and detail other considerations to bear in mind when managing K2 for SharePoint applications over their lifecycles.
Note that there are two seperate whitepapers: one that applies to K2 4.7 and later, another that applies to versions of K2 prior to K2 4.7. Please download the appropriate version of the whitepaper for your version of K2.