Design method of relational database-based workflow engine system

Abstract

The invention provides a design method of a relational database-based workflow engine system. The method comprises the following steps of: designing and establishing the correlation table of a workflow engine in a database system; designing and developing the operating method of the workflow engine in a database; when the workflow engine is used in a specific software application system, integrating the workflow engine with the application system; and according to the requirements of service functions, processing the flow of service logic by a corresponding method which is provided by the workflow engine in the software application system. The method is characterized by low cost, high flexibility, high processing capability and high stability.

Description

technical field [0001] The invention relates to a design method of a workflow engine system, in particular to a design method of a workflow engine system based on a relational database. Background technique [0002] Workflow is a business process that can be fully or partially automatically executed. According to a series of process rules, documents, information or tasks can be transferred and executed between different executors. The full English name of the workflow engine is: WorkFlow Engine, which refers to it as a part of the application system, and provides core solutions for each application system, such as information transmission routing, content level, etc. plan. [0003] The core part of the workflow system is the workflow engine, which is the main component that drives the process flow. It is responsible for interpreting the workflow process definition, creating and initializing process instances, controlling the flow path of the process, recording the running s...

AI Technical Summary

Problems solved by technology

Existing workflow engines require a certain software and hardware environment, and workflows based on J2EE technology require middleware service systems and hardware servers. For two-tier C / S application systems, additional money must be purchased, which will increase additional cost

At the same time, the middleware link is added to the whole system, which increases the complexity of the system, increases the failure points of the system, and puts forward higher requirements for the maintenance and guarantee of the system.

[0009] 2. Poor flexibility: Different types of workflow engines have their own independent set of workflow models, workflow definition languages ​​and API functions

Without a standard specification, once the user selects a product, it is difficult to transition to other similar products; and the lack of interoperable interfaces between different systems makes the scalability of the system unguaranteed

[0010] 3. Operational performance issues: At present, most workflow products have a certain lack of operational response time and concurrent processing capabilities, which cannot meet the needs of enterprises to process tens of thousands of businesses per day, or even thousands of businesses per hour.

[0011] 4. Lack of flexibility: whether it is process model definition or authority role analysis, the existing workflow system shows different degrees of flexibility and poor characteristics

The actual application of some projects often has dynamic requirements for execution routing and dynamic selection of work item executors. The current workflow system cannot provide good support for these requirements.

[0012] 5. Poor stability: In the actual application of the workflow system in the enterprise, some unconventional operations often cause process execution errors

[0013] 6. Immature implementation technology: none of the current implementation technologies used in workflow products or prototype systems can reach the level of relational database management systems

At the same time, because the workflow uses a separate database session, it often causes the key problem of data inconsistency between the workflow and the business system