Solution Naming Conventions
In software development, a key best practice is to maintain a common approach to naming the various artifacts developed within a solution. K2 solutions are no different, as 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
The K2 platform 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 while minimizing the impact of change.
There are a number of ways to deploy solutions built on the K2 platform and there are benefits and considerations to all methods. 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 and are typically is used in situations where 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. It is equally as critical that it be implemented with discipline during development cycles 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 and/or complicating maintenance and testing.
Learn more about solution versioning.