Welcome to the Synergy Technical Blog and Technical Knowledge Base – a resource that shares intelligent and creative solutions that have been built and implemented on real-time projects on behalf of Velocity clients.
There is an unbelievable useful (and often overlooked) feature in K2 blackpearl Workspace that allows you view a paginated list of all in-flight process instances in K2.
You might want to quickly list all processes in the K2 database that is started by a particular originator, or view all processes that are in error state with the intention to perform a goto activity. This can simply be achieved by opening K2 workspace, navigating to the Management Console, expanding Processes, right click on it and selecting Manage Process Instances.
K2 SmartForm data labels are powerful controls that allow you to set expressions and so on based in form data and context.
To change a default control, open the K2 SmartForm or K2 Appit designer and open the view that contains the control you want to change to a K2 data label. This is typically a K2 SmartForm textbox. Click on the control you wish to change
K2 blackpearl ships with the K2 SmartObject Tester tool that allows you to configure and run everything to do with K2 SmartObjects. It is a vital element of K2 development and administration. This tool gets installed in the bin folder under the K2 blackpearl program files directory and is a thick client application.
K2 Viewflow is a powerful tool that enables you to view the actual in-flight and completed K2 Appit or K2 blackpearl process instances.
Each K2 process instance has an unique identifier that auto increments every time you start a new process instance. When you develop K2 processes, you will start quite a few instances to test changes or additional steps that might have been added to the workflow.
A typical K2 blackpearl workflow process design pattern is to associate a business object (for example a leave request) with a K2 process, and this process is typically a long running process that moves the object to its finite state. An example final state might be approved.
Updates made to data, or more specifically business objects, during this long running process sometimes require a K2 workflow processes to be started to react to this update. It could be that a change in one of the data objects’ properties requires an approval process to be initiated if its value is above a certain threshold. While the business logic in the approval process might have been called as part of the sequential long running K2 process, it is required to be executed again to evaluate and to ensure the appropriate K2 workflow actions are taken.
The K2 blackpearl IPC event is extremely powerful and provide the means to connect separate K2 Workflow processes. It is good practice to implement a process in K2 as a collection of sub-processes and connect them using the K2 Inter Process Communication (IPC) event. These K2 processes are generally in the same K2 for Visual Studio project, but bigger enterprise level Business Process Automation using K2 blackpearl generally results in K2 processes being spread amongst several K2 for Visual Studio projects.