Process Design

Design Tool Considerations

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

Learn more about design tool considerations

General Design Best Practices

It is important to understand certain foundational design principles on which to base K2 development such as rules, data field usage and exception handling.

Learn more about best practices

Destination Rules Best Practices

The K2 Studio and K2 for Visual Studio workflow designers provide many ways for tasks to be assigned to people. In the simplest sense a workflow task requires the use of Client Event and the configuration of that Activity’s Destination Rule within K2. This is an important element of workflow design as it can provide for dynamic task assignments as well as lower the level of effort required to maintain a workflow. This document will highlight common scenarios in an effort to assist with workflow design.

Learn more about destination rules

Workflow Design Patterns

K2 provides robust workflow design tooling allowing for designers to configure a number of different types of business processes. For example it is common for a workflow to have to handle sequential execution, parallel execution, rework, looping, and a dynamic number of approvals. Understanding how to implement these within K2 is valuable to any K2 workflow designer.

Learn more about workflow design patterns

Line Rule Considerations

The K2 Studio and K2 for Visual Studio workflow designers provide for a flexible design experience in order to model complex, real world business processes. Within a running K2 process, direction of workflow execution is determined by logic that resides within Line Rules.

This document will discuss how to leverage a Line Rules in a number of common ways to affect workflow direction.

Learn more about line rules

External System Call Backs to K2 Workflow

When a workflow needs to wait for an event to occur within another system, for example if a workflow needs to wait for a record to change within a database, the first thought of many developers is to build some polling mechanism into the K2 workflow. There are more efficient ways of achieving the desired functionality. Asynchronous Server events are a much more scalable approach.

Learn more about external system call backs

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.

Data and Integration Planning

Learn about the governance rules that are encouraged with regards to the K2 product database within SQL Server instance for K2 blackpearl.

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.