First, explain two concepts:
Workflow, work broken down into different paragraphs tasks, and then executed by certain rules and process these tasks and monitor them, to improve efficiency, reduce production costs and improve the competitiveness of enterprises and other purposes. It is mostly used in office automation.
Traffic flow: it is the data flow between internal resources, general comprehensive integrated management of enterprise logistics, capital flow and information flow through the enterprise resource planning system (ERP).
However, in actual business, it is often some demand, OA systems need to switch back and forth and ERP systems, such as: purchase with money application, payment vouchers do ERP system is functional (as shown below).
In addition, enterprises in the post-approval use oa workflow system will produce some business data, business data and these in turn may be the ERP system of external data sources, such as procurement costs on the map application data. In order to avoid duplication of data and to ensure that the only source of data, a workflow system is generated and the traffic flow system integration requirements.
Current common integration approach, summed up in two categories
1): Integrated encapsulation mode of the interface, the use of OA, the interface provided by each of ERP (meaning the interface comprising: a database table structure, web service interfaces, other custom interface), the exchange of visits between the two data.
2): intermediate mode table based on visits, sharing of data between the data in the same model different storage systems by way of the data table the two systems are operated directly, data access between different systems, and data consistent and real-time delivery.
From the above analysis, this integration is difficult, at least with varying degrees of secondary development, if it is the use of secondary development, I personally prefer web service, web service that we often hear soa architecture, it is a kinds of integrated services platform architecture, the core point is to achieve complete separation of services and technologies, in order to achieve integration and restructuring services to the greatest extent. (Note, if the erp development, I strongly oppose the use of architecture soa I intuition of a soa only in certain business scenarios, the most appropriate way to provide services interfaces), why not use table it? Because
Approval ERP further special stream, which process is actually performed the transfer of control between two subsystems, if the access pattern is based on cross table, which is tightly coupled integrated way, the system will affect the flexibility and scalability, impede adjustment and optimization of business processes, is not conducive to the development of enterprises.
Recent research in the country of an open source system FireWorkflow (http://www.fireflow.org), and its source code are analyzed (the first to be advertising, then I will analyze source code written procedure blog, for everyone AC, correct me).
Some ideas Fireworkflow mentioned, very agreeable to me, for example, an ordinary process leave
Executing this flowchart is described as follows:
First, the workflow subsystem to start a new business process instance, and then create a new task instance - "Shen
Please "and control to the business subsystem, subsystem waits business applicants fill out the form. After the applicant complete the form, once again handed over control of the workflow subsystem, the next step of the route is determined by it. This work is Synchronize r from the element called completed (FIG labeled "S" in a circle). in this operational example, it is calculated by the next operation is "department manager for approval." Create a so called "manager approval task instance ", and control to the business subsystem, subsystem waits business department manager for approval to do the operation.
Figure workflow logic and business logic share is very clear, which business operations performed after approval by a workflow logic subsystem "action" decision. Business logic subsystem "approval" is only responsible for the operation to complete specific business logic has nothing to do with the other, that is what I want, a good erp, should include workflow subsystem and subsystem traffic flow , and these two subsystems are both unrelated and can collaborate with each other, not associated refers to the less one of them, the other can work properly. Mutual cooperation means that they can take advantage of each other, the better for business development services
