Design Tool Considerations
The K2 platform offers multiple design tools which should be considered prior to selecting.
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 stakeholders.
In the simplest sense, a workflow task requires the use of client event and the configuration of that activity’s destination rule. This is an important element of workflow design as it can provide for very dynamic task assignments as well as lower the level of effort required to maintain a workflow.
Learn more about destination rules.
Workflow Design Patterns
We provide robust workflow design tooling that allows 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 solutions is valuable to any workflow designer.
Learn more about workflow design patterns.
Line Rule Considerations
The K2 Studio workflow design tool provides 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.
Learn more about line rules.
External System Call Backs to K2 Workflows
Sometimes, workflows have dependencies on another system. The first thought of many developers in this case is to build some polling mechanism into the K2 workflow, however, this approach should be avoided. Instead, asynchronous server events should be considered as a much more scalable approach.
Learn more about external system call backs.