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