Solution Structure and Governance

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.

Solution Deployment

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.

Solution Versioning

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.

K2 Platform Technical Enablement

It is important that resources tasked with implementing a K2 solution for the first time have the ability to properly learn the platform. We offer a comprehensive training program to help clients achieve maximum value from their investment, which is organized into five technical competencies, allowing for focus on particular aspects of the solutions, or the entire story.

Solution Structure and Governance

An overview of best practices for naming conventions, teams with multiple developers, solution deployment and solution versioning.

Data and Integration Planning

Learn more about K2 database practices, SmartObjects and reporting.

Common Technologies Overview

Common usage scenarios for some of the most utilized technologies seen within the greater K2 community.

Process Design

This section provides more information on process design tools, design best practices, destination rules best practices, workflow design patterns, line rule considerations, and external system call backs to K2 workflows.

K2’s SmartForms Design

These SmartForms design considerations and performance tuning guidelines will help you get the most out of your forms.

K2 and Mobility

The K2 platform provides the ability to interact with K2 applications on mobile devices.  The K2 mobility story falls into two categories: mobile resident applications and mobile friendly forms development.  This section covers these two areas in more detail and highlight content that can provide more specific technical details.

K2 Language Support

By default all K2 design time and runtime elements display in English.  If there is a need to design solutions that accommodate other languages then it is important plan appropriately.  This involves understanding what language support the K2 platform offers as well as which areas must be accommodated within solution design.