Data and Integration Planning

K2 Product Database Practices

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

  • Only designated administrators should be granted access to the K2 product databases
  • Consider restricting the deployment of K2 databases to the same SQL instance used by K2 product
    • 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 should never be modified
  • Indexes and foreign keys on K2 product tables should not be modified
  • Custom triggers and functions on K2 product tables are not allowed
  • Custom .NET assemblies should not be added to the K2 product databases
  • Stored procedures and views provided by K2 should not be modified
  • New stored procedures and views on the K2 product tables should be abstracted to a new database
  • The only schema within the K2 database that may be considered for read-only access is the “ServerLog” schema
  • Directly inserting, updating or deleting data into K2 database tables outside of the API is not allowed
    • The only exception to this rule is the K2 SmartBox-created tables

SmartObject Considerations

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

Learn more about SmartObjects.

Reporting Considerations

Metrics and reporting are commonly important elements of K2 solutions. The K2 platform provides some out-of-the-box reports to provide visibility into business processes.

However, 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.

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.

Common Technologies Overview

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

Solution Structure and Governance

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

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.