Solution Naming Conventions
It is normal in all software development to have a common approach to naming the various artifacts developed within a solution. K2 is no different and it is highly recommended that a naming convention be established and followed for K2 artifacts such as SmartForms, SmartObjects, Workflows and the Category System.
Learn more about solution naming conventions
Planning for Multiple Developer Solution Development Teams
K2 is a platform that caters to development teams of many sizes. Certain practices are necessary when working with larger teams of developers. This guide is intended to illustrate the considerations and practices around team development that has proven to be successful when collaborating in larger sized development teams. The goal is to promote an environment that encourages the successful delivery of projects whilst minimizing the impact of change.
Learn more about multiple developer environments
There are a number of ways to deploy solutions built on the K2 platform and there are benefits and considerations to all methods. Based on the current requirements for a project deployment there are a number of options. The most practical advice here is, as always, use the simplest solution that meets the requirements.
Learn more about solution deployment
One of the key value propositions of the K2 platforms is its ability to combine people and systems into a single seamless solution. As a result K2 solutions are frequently coupled with many disparate components and technologies. Additionally, K2 as a business process application platform, typically is used for solutions where the business requirements change over the course of time. As a result of these two considerations it is imperative that a solution versioning strategy be developed and the discipline instilled during the development cycles to execute it to ensure stability of operations as well as organize maintenance of artifacts. Failing to properly account for change across releases can have the undesirable effects of introducing regression issues, or complicating maintenance and testing.
Learn more about solution versioning