Unfair
At present, "Workflow" has become a technical hotspot, and a large number of application solutions are considering using workflow-based technology. The key to learning workflow is to understand the workflow model. Let's take a look at the workflow model of the workflow model for the workflow model of the workflow middleware of the WW.INFORBUS.COM of Zhongchu Software Commercial Middleware Co., Ltd.
The value of the application workflow is primarily applied to the process-processed business system (we calls the process application), and the process is such a generally existing, telecommunications, finance, government affairs, etc. involving a large number of processes. There are two special prominent issues for process applications: First, some processes are very complicated, and there are different organizations, involving a variety of character characters, and there are many special processing links, which has always been very painful for such complex processes. Do things. Second, the process is the easiest thing to change, such as the so-called "reform" is a change process. Today, in order to improve the efficiency of work, it is possible to increase the processing link in order to strict control. As a software development, it has never hate users to change, but there is no way, only the ability to transform yourself make your own software can have the ability to adapt to changes. For process applications, this can be done by means of a workflow middleware like Inforflow. The key value of the use of workflow middleware is in these two aspects, on the one hand, by using the workflow middleware to better decompose the system, and the process of the business process is handed over to the workflow middleware, and the application developer It only needs to implement business components, which can reduce development difficulty, reduce development workload; on the other hand, it is also more important, the process logic is given to workflow middleware processing, due to process logic and business logic separation, Reducing the influence of process logic changes to business logic changes, and like Inforflow This workflow middleware guarantees the ability of process logic to adapt to change, so that the capacity of the entire application adaptation is greatly improved.
Workflow solving Idea Workflow Solution The idea is actually very simple: separate the process part of the application logic (called process logic), establish a model for process logic, define the performance and processing of the process, and process The logical and business logic interface, the process model is implemented by the workflow middleware, and then, it is only necessary to implement business logic.
Seeing the process - understanding the process in reality to understand the workflow model, first need to understand the process in reality. Below is the popular understanding of the process of the reality: the so-called process is actually a process of business processing. This process consists of a series of links, and the link is performed in one order. Each link is completed by a person with a certain role, this People must complete certain tasks on this link. This is the popular disclosure of the process. As can be seen in this explanation, the flow contains the following basic elements: link: one of the processes, the point in this point, to complete a certain task by a person with a particular role. The sequence of processing of the link: is the flow of the process, and sometimes this flow will be affected by business data. For example, the loan to apply for 10 million yuan needs to pass a leader, and the loan applied for 10,000 yuan will not need to go. This link. Handling of the link: Who is on this step of work: The thing to complete in this link (business logic) always said, the so-called process is, a series of tasks, according to certain order, by each link The person performs the completed business processing process.
From the reality process to the inforflow workflow model, the basic elements of the process are talked about, and these elements are mapped to the Inforflow workflow model below. The following figure is the workflow model of INFORFLOW: We are described in terms of the basic elements mentioned above. Routine: Use "Node" in Inforflow to represent the process of the process, complete a certain task by a person with a particular role on a "node". Sequence of the link: Inforflow is a process of processing the "node" by "connecting arc" by a "connecting arc", which describes the processing order of the node by "connecting arc". Then, if the constraint condition is added to the node or an arc, it defines the rules that flow to be affected by the service data, and this constraint condition is referred to as "transfer conditions". Handling of the link: This handler is called "executive" in Inforflow, this "executive" can be described according to the role, or directly designate someone. Tasks on the link: Tasks on each of INFORFLOW correspond to a service component called "Business Unit". In addition, if you need to control the flow on the node, the control package of these pairs of flows is "operation". Totally, the process in Inforflow is actually a series of "business unit" components in order to execute the order, and these "business unit" components are implemented on different nodes by people with different roles. Based on the development of Inforflow, it is easy to understand the development process after understanding of this model: 1. Analysis Process: What is the analysis of each process? And do these links in what order. Especially for the tasks on the node, the "business unit" component is decomposed as much as possible in accordance with the idea of componentization. 2. Implement these "Business Unit" components that complete the business logic outside the flow logic in these business unit components. 3. Register these "Business Unit" components into the Inforflow Designer (Process Modeling Tool), define your process in the designer, hung on the "Business Unit" component to the desired node. 4. Finally, release the process
There are two cases of how to adapt to the change process: one is to increase the process processing link, the other is to adjust between the links. It is usually necessary to do both aspects during a process adjustment (especially for the first case, the first case is particularly related to the second adjustment). In Inforflow, the first case is to increase the process "node", the second case is to adjust the "business unit" on the "node". When the process is adjusted, as long as the "business unit" component itself changes, it is not necessary to modify the code.
