Data and Integration Planning

K2 Product Database Practices

The following governance rules are encouraged with regards to the K2 product database within SQL Server instance for K2 blackpearl:

  • Only designated administrators should be granted access to the K2 product databases
  • If custom databases are needed for a given solution they should be hosted on a different database instance or a different SQL Server than the K2 product databases
  • The table structure of K2 product tables must not be modified
  • Indexes and foreign keys on K2 product tables must not be modified
  • Custom triggers and functions on K2 product tables are not allowed
  • Custom .NET assemblies must not be added to the K2 product databases
  • Stored procedures and views provided by K2 must not be modified
  • The only schema within the K2 database that may be considered for direct read only access is the “ServerLog” schema
  • Directly inserting, updating, or deleting data into K2 database tables outside of the API is not allowed

SmartObject Considerations

The SmartObject framework is an integral component within the K2 platform and is considered as essential in any K2 solution. There are a number of factors to consider when using SmartObjects and proper design and implementation are important cornerstones of a stable solution.

Learn more about SmartObjects

Reporting Considerations

Metrics and reporting are important elements of K2 solutions. The K2 platform provides out of the box reports to provide visibility into business processes. It is also common to have to accommodate custom or complex reporting needs. Proper understanding of out of the box functionality as well as common design techniques can help developing a reporting strategy.

Learn more about reporting considerations

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 K2 platform. K2 offers multiple options around technical enablement.

Solution Structure and Governance

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.

Process Design

The K2 platform offers multiple design tools. As such it is important to understand the differences between them.

K2’s SmartForms Design

This document provides a number of best practices with regards to designing and constructing K2 smartforms solutions.

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 to plan appropriately. This involves understanding what language support the K2 platform offers as well as which areas must be accommodated within solution design.