K2 implements dynamic configuration of process nodes

In the past, this blog talked about how K2 blackpearl works with the moss form library to implement the leave process.
K2.net2003

I first came into contact with K2 blcakpearl and developed a moss-based process. We feel that K2 blcakpearl is very powerful and has provided
Many wizard, many items need to be configured and configured, or modified based on the code generated by him. K2 blcakpearl also has a bigger advantage that K2 blcakpearl is based on WF at the bottom layer, therefore, it is more closely connected to Ms. Because many wizard interfaces are provided, there is no K2 on the operation interface. Net is concise. It is not easy for developers to get started. Still give WF, WCF, and WPF, but there are still many areas where flexibility is not enough.
K2 has been used recently. . NET development project. K2.net is easy to start ., It is also very simple. Scalability is also very powerful ..

This is a process recently implemented:
The process is simple .. The focus of this process is that users can flexibly configure nodes in the database. It is easy to disable nodes. Enable nodes

Implementation principle of this process: the user submits the process-> level activity to determine the level of the current applicant to go through the process.
When you go through the process, determine whether the approval node is disabled. If it is disabled, go to the next process node,
If the next node is not disabled, the application is approved. After approval, the process is transferred to level activity again to determine whether the sub-level of the process is disabled. If disabled, go down level 1 again... .. It is easy to solve the dynamic problem of process nodes.
The flowchart is as follows:

 

 

 

Hope to give you some help...