A workflow engine and rule engine conversion control system

Through the loosely coupled workflow engine and rule engine conversion control system, the problems of large development workload and low efficiency caused by tight coupling in the prior art are solved, and dynamic management of complex business rules and system scalability are realized.

CN115964055BActive Publication Date: 2024-11-29ZHONGJIN TECH (GUANGDONG) CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202211713543.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-12-28
Publication Date
2024-11-29
Estimated Expiration
2042-12-28

AI Technical Summary

Technical Problem

In the prior art, the workflow engine and the rule engine are tightly coupled, resulting in large development workload and low efficiency, and the inability to effectively support complex business rules application scenarios.

Method used

A loosely coupled conversion control system between workflow engine and rule engine is designed, and communication between the two is achieved through model warehouse, workflow warehouse and rule warehouse. The rule engine and workflow are used to use Groovy rule script generator and Netty service. Engine interaction, supports dynamic rule updates and process activity configuration.

Benefits of technology

It realizes loose coupling between the workflow engine and the rule engine, reduces development difficulty and maintenance costs, supports dynamic management of complex business rules, and improves the scalability and efficiency of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115964055B_ABST
    Figure CN115964055B_ABST
Patent Text Reader

Abstract

The present invention discloses a workflow engine and rule engine conversion control system, which belongs to the technical field of business process software. The conversion control system ZTran sets up a communication channel between a workflow engine ZWE and a rule engine ZRE, receives upstream system data and encapsulates it before forwarding it to the rule engine ZRE, which processes it and then returns a decision result. The conversion control system ZTran includes a model warehouse, a workflow warehouse and a rule warehouse; a data model is defined according to an upstream data source, or a workflow form is converted into a data model; the definition of the workflow is published to the workflow warehouse, and the rule engine ZRE obtains the activity data of the workflow through the conversion control system ZTran, and configures rules for the activities; the rule engine ZRE publishes rules to the rule warehouse, and the workflow engine can obtain rule version data through the conversion control system ZTran, and dynamically update the rules by applying the latest version of the rules.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of business process software, and in particular to a workflow engine and rule engine conversion control system. Background Art

[0002] At present, in financial enterprises, such as banking enterprises and insurance enterprises, most of their business processes have been automated in a computer application environment by combining workflow engines. However, in some specific scenarios, such as credit approval business, complex logical calculations and flexible rule changes are usually required. However, workflow is essentially a process of transferring documents, information or tasks between multiple participants according to certain predefined rules. The workflow engine is not suitable for complex and changeable business rule application scenarios. Therefore, it is necessary to introduce a component for the workflow engine that can reduce the difficulty of business logic implementation and reduce maintenance and scalability costs. This component is the rule engine, which is suitable for scenarios with complex business rules and frequent and dynamic changes in rules.

[0003] At present, in the research of workflow technology based on rule engines, the mainstream traditional technology is to introduce ECA rules. ECA (Event Condition Action) originated from active database technology. It uses events, conditions, and behaviors to describe business logic, and defines the rule condition judgment and behavior processing content that meets the conditions when an event occurs. The mature products of workflow technology based on ECA rules on the market are mainly developed by combining the open source workflow engine Activiti with the Drools rule engine.

[0004] Activiti is the most widely used open source workflow engine in enterprises. It supports multiple process definition specifications such as BPMN2.0, XPDL, jPDL, etc., standardizes the design and development of business processes, and improves work efficiency. The Activiti workflow engine requires professional developers to design and deploy processes, and secondary development is required to connect to the rule engine. Drools is also an open source rule engine project. It uses the Rate algorithm to match the rules in the rule library and the data in the fact library, and draws corresponding conclusions and performs corresponding actions. The Drools rule engine defines and encapsulates business logic with rule files, saves program data with objects, and realizes the separation of business logic and data. However, it also requires professional developers to write and maintain rule files, and can only connect to the Activiti workflow engine in a hard-coded form.

[0005] Therefore, as a conventional workflow platform, its workflow engine and rule engine are mostly tightly coupled, and an additional interface needs to be developed to call the rule engine, which not only requires a large amount of development work but also has low efficiency.

[0006] Therefore, we developed a conversion control system suitable for loose coupling between the workflow engine and the rule engine. Summary of the invention

[0007] The purpose of the present invention is to provide a workflow engine and rule engine conversion control system to solve the technical problems in the prior art that the workflow engine and the rule engine are tightly coupled and the development workload is large.

[0008] The present invention provides a workflow engine and rule engine conversion control system, which is used for the conversion control of the workflow engine and the rule engine in a workflow platform. The workflow platform includes a workflow engine ZWE, a rule engine ZRE and a conversion control system ZTran. The workflow platform needs to go through workflow definition, workflow deployment and workflow operation. The conversion control system ZTran sets up a communication channel between the workflow engine ZWE and the rule engine ZRE, receives upstream system data and encapsulates it and forwards it to the rule engine ZRE, which processes it and then returns the decision result. The conversion control system ZTran includes a model warehouse , workflow warehouse and rule warehouse; define data models according to upstream data sources, or convert workflow forms into data models, and save these data models in the model warehouse as common models and share them with workflow engines and rule engines as process variables, parameters, and result variables; publish the definition of the workflow to the workflow warehouse, and the rule engine ZRE obtains the activity data of the workflow through the conversion control system ZTran, and configures rules for the activities; the rule engine ZRE publishes rules to the rule warehouse, and the workflow engine can obtain the rule version data through the conversion control system ZTran, and apply the latest version of the rules to dynamically update the rules.

[0009] Furthermore, after saving the process model, the system will generate an XML file that complies with the BPMN2.0 standard, and submit the process definition basic information and the XML file to the conversion control system ZTran for conversion into workflow warehouse data. The conversion control system ZTran parses the XML activity node information to generate the corresponding ZNode object, and automatically generates the business event object of the rule engine, which is used by the subsequent rule engine to configure rules for process activities.

[0010] Furthermore, the main attributes of the business event object include node category, event Key that triggers rule matching, input and output metadata, and transfer node, ie, child ZNode.

[0011] Furthermore, when defining a workflow, business personnel use the workflow engine ZWE to define the required form data and enter the interface, and export the data structure in JSON format through the workflow engine ZWE and submit it to the conversion control system ZTran. The conversion control system ZTran generates a Protobuf data structure file and type description information based on the data structure and in combination with the template engine Freemaker, and saves it in the Protobuf data source warehouse. Similarly, the upstream external system can also generate a unified Protobuf data source structure by exporting the JSON data structure and importing the JSON data structure in the conversion control system ZTran.

[0012] Furthermore, when defining a workflow, the rule engine ZRE can obtain data type description information through the data source warehouse of the conversion control system ZTran, obtain the data structure of input rule variables, parameters and output results, and use this to design rules and generate expression scripts through the Groovy rule script generator, which are saved in the rule warehouse of the conversion control system ZTran for workflow activity configuration.

[0013] Furthermore, when defining a workflow, the rule engine ZRE reads the data of the workflow warehouse of the conversion control system ZTran, generates business events corresponding to the rule engine according to the ZNode, and selects or creates rules for the activities of the workflow gateway, automatic task, and manual task types in the rule engine ZRE, and updates the association between the data in the workflow warehouse and the data in the rule warehouse.

[0014] Furthermore, when deploying the workflow, the data of the associated data source warehouse and rule warehouse are found according to the workflow, the data is packaged to build the data source producer and the Netty service is started. Before starting the Netty data source producer, the Protobuf dynamic compiler will be used to precompile the proto file and type description information of the data source to generate a Protobuf object in Java format. If an error occurs at this time, the Netty service will not be started and the deployment failure will be returned.

[0015] Furthermore, when deploying the workflow, after the Netty data source producer is successfully started, the conversion control system ZTran passes the relevant rule data to the rule engine ZRE, builds the data source consumer and starts the Netty client. After the Netty data source consumer is started, the rule data is compiled and cached in the memory, and then the corresponding data source producer Netty server is connected and a long connection is maintained.

[0016] Furthermore, after the Netty server and the Netty client are successfully connected, the process converter of the conversion control system ZTran reversely generates the BPMN2.0 standard workflow description file based on the ZNode information of the associated rule data in the workflow, and pushes it to the workflow engine ZWE. The workflow engine ZWE starts the workflow instance based on this XML file and starts executing process activities.

[0017] Compared with the prior art, the beneficial effects of the present invention are:

[0018] In the prior art, as a conventional workflow platform, its workflow engine and rule engine are mostly tightly coupled, and an additional interface needs to be developed to call the rule engine. The development workload is large and the efficiency is low. In the present invention, a workflow system is developed based on the lightweight business process engine Flowable, and a rule engine is developed based on the Groovy dynamic scripting language and the expression engine Aviator. The rule engine is integrated by the system as an extensible plug-in of the workflow system, and the business process logic and business rule logic are extracted from the application at the same time to establish a system that combines processes and rules but is independently managed. In particular, in this platform, the conversion control system ZTran is used as an adaptor and interactive component between the workflow engine and the rule engine. It manages the node routing flow of the workflow under the guidance of business rules. As well as dynamic assignment of executors and form processing, it can define data models based on upstream data sources, and can also convert workflow forms into data models. These data models are saved to the model warehouse and shared as common models to the workflow engine and rule engine as process variables, parameters, result variables, etc. In addition, the definition of the workflow is published to ZTran's workflow warehouse, and the rule engine obtains the activity data of the workflow through ZTran and configures rules for the activities; the rule engine publishes rules to ZTran's rule warehouse, and the workflow engine can obtain rule version data through ZTran, and apply the latest version of the rules to achieve the effect of dynamically updating the rules. Using a loosely coupled approach, ZTran only needs to generate a bar deployment package based on the configured workflow engine to publish the workflow and interact with the rule engine. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 It is a system flow diagram of a workflow platform in the prior art;

[0021] Figure 2 This is a schematic diagram of the system flow of the workflow platform in the present invention:

[0022] Figure 3 A schematic diagram of a workflow platform in the present invention defining a business process;

[0023] Figure 4 This is a schematic diagram of the business process deployed on the workflow platform in the present invention:

[0024] Figure 5 This is a schematic diagram of the workflow platform node operation process in the present invention:

[0025] Figure 6 It is a flow chart of the conversion control system ZTran in the present invention. DETAILED DESCRIPTION

[0026] The technical solution of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Specific embodiment 1:

[0028] like Figure 1 The figure shows the process flow diagram of the current workflow platform. In the research of workflow technology based on rule engines, the mainstream traditional technology is to introduce ECA rules. ECA (Event Condition Action) originated from active database technology. It uses events, conditions, and behaviors to describe business logic, and defines the rule condition judgment and behavior processing content that meets the conditions when an event occurs. The mature products of workflow technology based on ECA rules on the market are mainly developed by combining the open source workflow engine Activiti with the Drools rule engine.

[0029] Activiti is the most widely used open source workflow engine in enterprises. It supports multiple process definition specifications such as BPMN2.0, XPDL, jPDL, etc., standardizes the design and development of business processes, and improves work efficiency. The Activiti workflow engine requires professional developers to design and deploy processes, and secondary development is required to connect to the rule engine. Drools is also an open source rule engine project. It uses the Rate algorithm to match the rules in the rule library and the data in the fact library, and draws corresponding conclusions and performs corresponding actions. The Drools rule engine defines and encapsulates business logic with rule files, saves program data with objects, and realizes the separation of business logic and data. However, it also requires professional developers to write and maintain rule files, and can only connect to the Activiti workflow engine in a hard-coded form.

[0030] Among them, the workflow engine is tightly coupled with the rule engine, and an interface needs to be developed to call the rule engine, which results in large development workload and low efficiency.

[0031] Combine the following Figures 2 to 5 As shown, in this workflow platform, the following steps are included: define metadata, which can be divided into form data, interface data and push data according to the data source. The form data is designed with a visual form UI in the form design module of the workflow engine, and the form model can be automatically generated after the design is completed. After the form data is submitted to ZTran, it will be converted into a general data output model for use by the rule engine; interface data refers to the data actively pulled from the external system by this system, which is defined in ZTran according to the input and output of the external data interface. ZTran generates the corresponding client call code and the general data output model, and the event triggers the client to call the external interface to obtain data for use by the rule engine; push data refers to the data pushed by the external system passively received by this system, and the input data structure is defined in ZTran as the input data of the rule engine;

[0032] After completing the metadata definition, you can define the workflow model in the workflow engine, including defining the active nodes of the process, the flow path (sequential flow), and the form for configuring the node. The node form can select form data and interface data. Selecting form data will automatically render the UI interface for manual data input according to the form model. Selecting interface data will directly display it according to the interface data model for reviewers to review.

[0033] After saving the process model, the system will generate an XML file that complies with the BPMN2.0 standard, and submit the process definition basic information and XML file to ZTran for conversion into workflow warehouse data. ZTran parses the XML activity node information to generate the corresponding ZNode object. The main attributes of this object include node category, event key (trigger rule matching), metadata (input and output), and transfer node (child ZNode), etc., and automatically generates the business event object of the rule engine, which is used by the subsequent rule engine to configure rules for process activities;

[0034] After selecting a business event in the rule engine, the entire workflow can be rendered by associating ZNodes, and then the activity nodes that need to be configured with rules, such as gateway nodes, rule nodes, dynamic assignment nodes, etc., can be selected to add / modify rules for the nodes. The rule engine submits rules and business event data to ZTran, which saves the rule warehouse and updates the association between the workflow warehouse data and the rule flow warehouse data:

[0035] The tightly coupled method requires updating the process model in the workflow engine, while the loosely coupled method only requires ZTran to generate a bar deployment package based on the configured workflow engine to publish the workflow and interact with the rule engine. Specific embodiment 2:

[0037] like Figure 6 As shown, an embodiment of the present invention provides a workflow engine and rule engine conversion control system, which is used for conversion control of workflow engine and rule engine in a workflow platform. The workflow platform includes a workflow engine ZWE, a rule engine ZRE and a conversion control system ZTran. The workflow platform needs to go through workflow definition, workflow deployment and workflow operation. The conversion control system ZTran sets up a communication channel between the workflow engine ZWE and the rule engine ZRE, receives upstream system data and encapsulates it and forwards it to the rule engine ZRE, which processes it and then returns the decision result. The conversion control system ZTran includes Model warehouse, workflow warehouse and rule warehouse; define data models according to upstream data sources, or convert workflow forms into data models, these data models are saved in the model warehouse, and shared with workflow engines and rule engines as common models as process variables, parameters, and result variables; the definition of the workflow is published to the workflow warehouse, and the rule engine ZRE obtains the activity data of the workflow through the conversion control system ZTran, and configures rules for the activities; the rule engine ZRE publishes rules to the rule warehouse, and the workflow engine can obtain rule version data through the conversion control system ZTran, and apply the latest version of the rules to dynamically update the rules.

[0038] In the prior art, as a conventional workflow platform, its workflow engine and rule engine are mostly tightly coupled, and an additional interface needs to be developed to call the rule engine. The development workload is large and the efficiency is low. In the present invention, a workflow system is developed based on the lightweight business process engine Flowable, and a rule engine is developed based on the Groovy dynamic scripting language and the expression engine Aviator. The rule engine is integrated by the system as an extensible plug-in of the workflow system, and the business process logic and business rule logic are extracted from the application at the same time, so as to establish a system that combines processes and rules but is independently managed. In particular, in this platform, the conversion control system ZTran is used as a component that adapts and interacts between the workflow engine and the rule engine, with business Rules serve as a guide to manage the node routing flow of workflows, the dynamic assignment of executors, and form processing. It can define data models based on upstream data sources, and can also convert workflow forms into data models. These data models are saved in the model warehouse and shared as common models with the workflow engine and rule engine as process variables, parameters, result variables, etc. In addition, the definition of the workflow is published to ZTran's workflow warehouse, and the rule engine obtains the activity data of the workflow through ZTran and configures rules for the activities; the rule engine publishes rules to ZTran's rule warehouse, and the workflow engine can obtain rule version data through ZTran, and apply the latest version of the rules to achieve the effect of dynamically updating the rules. Using a loosely coupled approach, ZTr an only needs to generate a bar deployment package based on the configured workflow engine to publish the workflow and interact with the rule engine.

[0039] Furthermore, after saving the process model, the system will generate an XML file that conforms to the BPMN2.0 standard, and submit the basic process definition information and the XML file to the conversion control system ZTran to convert them into workflow warehouse data. The conversion control system ZTran parses the activity node information of the XML to generate the corresponding ZNode object, and automatically generates the business event object of the rule engine, which is used by the subsequent rule engine to configure rules for process activities.

[0040] In this embodiment, the main attributes of the business event object include node category, event Key that triggers rule matching, input and output metadata, and transfer node, ie, child ZNode.

[0041] In this embodiment, when defining a workflow, the business personnel use the workflow engine ZWE to define the required form data and enter the interface, and export the data structure in JSON format through the workflow engine ZWE and submit it to the conversion control system ZTran. The conversion control system ZTran generates a Protobuf data structure file and type description information based on the data structure and in combination with the template engine Freemaker, and saves it in the Protobuf data source warehouse. Similarly, the upstream external system can also export the JSON data structure and import the JSON data structure in the conversion control system ZTran to generate a unified Protobuf data source structure; the rule engine ZRE can obtain the type description information of the data through the data source warehouse of the conversion control system ZTran, obtain the data structure of the input rule variables, parameters and output results, and use this to design rules and generate expression scripts through the Groovy rule script generator, which are saved in the rule warehouse of the conversion control system ZTran for the activity configuration of the workflow: the rule engine ZRE reads the conversion control system ZTran and the expression scripts are generated by the Groovy rule script generator, and are saved in the rule warehouse of the conversion control system ZTran for the activity configuration of the workflow: The data in the workflow warehouse of an generates business events of the corresponding rule engine according to ZNode, and then selects or creates rules for the activities of the workflow gateway, automatic task, and manual task types in the rule engine ZRE, and updates the association between the data in the workflow warehouse and the data in the rule warehouse.

[0042] In this embodiment, when the workflow is deployed, the data of the associated data source warehouse and rule warehouse are found according to the workflow, the data is packaged to build a data source producer and the Netty service is started. Before the Netty data source producer is started, the Protobuf dynamic compiler will pre-compile the proto file and type description information of the data source to generate a Protobuf object in Java format. If an error occurs at this time, the Netty service will not be started, and the deployment failure will be returned; after the Netty data source producer is successfully started, the conversion control system ZTran passes the relevant rule data to the rule engine ZRE, builds a data source consumer and starts the Netty client. After the Netty data source consumer is started, the rule data is compiled and cached in the memory, and then the corresponding data source producer Netty server is connected and a long link is maintained; after the Netty server is successfully connected to the Netty client, the process converter of the conversion control system ZTran reversely generates a BPMN2.0 standard workflow description file based on the ZNode information of the associated rule data in the workflow, and pushes it to the workflow engine ZWE. The workflow engine ZWE starts the workflow instance according to this XML file and starts to execute the process activities.

[0043] In particular, after the workflow is started, the business personnel specified by the process activity can perform approval or form entry. When the process is executed to the activity that needs to call the rule (gateway, automatic task, manual task type), the process activity pushes the form data (Json format) to the Netty data source producer according to the data source configuration information; and the Netty data source producer passes the form data to the Protobuf dynamic compiler. The Protobuf dynamic compiler combines the Protobuf object (Java), type description information and form data to generate Protobuf self-description information, and sends it to the corresponding Netty data source consumer client: The Netty data source consumer inputs the Protobuf self-description message into the Protobuf self-description message parser, and its Protobuf self-description message parser completes the interpretation of the message and generates a DynamicMessage object. It is encapsulated into a Groovy object through the Groovy reflection caller, corresponding to the rule script (such as customer.age) based on the object call attribute. Input the Groovy object to the corresponding Aviator expression executor to perform expression evaluation, and then encapsulate the rule result into a DynamicMessage object after obtaining it, and return it to the Netty data source producer; the Netty data source producer then parses the DynamicMessage object and reversely outputs the rule result in Json format data and returns it to the workflow engine. The workflow engine can control the direction of the process and display the rule output according to the rule result.

[0044] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A workflow engine and rule engine conversion control system, which is used for the conversion control of the workflow engine and the rule engine in a workflow platform. The workflow platform includes a workflow engine ZWE, a rule engine ZRE and a conversion control system ZTran. The workflow platform needs to go through workflow definition, workflow deployment and workflow operation, and is characterized by: The conversion control system ZTran sets up a communication channel between the workflow engine ZWE and the rule engine ZRE, receives the upstream system data and encapsulates it and forwards it to the rule engine ZRE, which processes it and then returns the decision result. The conversion control system ZTran includes a model warehouse, a workflow warehouse and a rule warehouse; Define data models according to upstream data sources, or convert workflow forms into data models. These data models are saved in the model warehouse and shared with the workflow engine and rule engine as common models as process variables, parameters, and result variables: The definition of the workflow is published to the workflow warehouse. The rule engine ZRE obtains the activity data of the workflow through the conversion control system ZTran and configures rules for the activities: The rule engine ZRE publishes rules to the rule warehouse, and the workflow engine can obtain rule version data through the conversion control system ZTran and apply the latest version of the rules to dynamically update the rules.

2. A workflow engine and rule engine conversion control system according to claim 1, characterized in that: After saving the process model, the system will generate an XML file that conforms to the BPMN2.0 standard, and submit the basic process definition information and the XML file to the conversion control system ZTran to convert them into workflow warehouse data. The conversion control system ZTran parses the XML activity node information to generate the corresponding ZNode object, and automatically generates the business event object of the rule engine, which is used by the subsequent rule engine to configure rules for process activities.

3. A workflow engine and rule engine conversion control system according to claim 2, characterized in that: The main attributes of the business event object include node category, event Key that triggers rule matching, input and output metadata, and transfer node, ie, child ZNode.

4. A workflow engine and rule engine conversion control system according to claim 1, characterized in that: When defining a workflow, business personnel use the workflow engine ZWE to define the required form data and enter the interface, and export the data structure in JSON format through the workflow engine ZWE and submit it to the conversion control system ZTran. The conversion control system ZTran generates Protobuf data structure files and type description information based on the data structure and in combination with the template engine Freemaker, and saves them in the Protobuf data source warehouse. Similarly, upstream external systems can also generate a unified Protobuf data source structure by exporting the JSON data structure and importing the JSON data structure in the conversion control system ZTran.

5. The workflow engine and rule engine conversion control system according to claim 1, characterized in that: When defining a workflow, the rule engine ZRE can obtain data type description information through the data source warehouse of the conversion control system ZTran, obtain the data structure of input rule variables, parameters and output results, and use this to design rules and generate expression scripts through the Groovy rule script generator, which are saved in the rule warehouse of the conversion control system ZTran for workflow activity configuration.

6. A workflow engine and rule engine conversion control system according to claim 5, characterized in that: When defining a workflow, the rule engine ZRE reads the data of the workflow warehouse of the conversion control system ZTran, generates business events corresponding to the rule engine according to the ZNode, and selects or creates rules for the activities of the workflow gateway, automatic task, and manual task types in the rule engine ZRE, and updates the association between the data in the workflow warehouse and the data in the rule warehouse.

7. A workflow engine and rule engine conversion control system according to claim 1, characterized in that: When deploying a workflow, find the data of the associated data source warehouse and rule warehouse according to the workflow, package the data to build a data source producer and start the Netty service. Before starting the Netty data source producer, the Protobuf dynamic compiler will precompile the proto file and type description information of the data source to generate a Protobuf object in Java format. If an error occurs at this time, the Netty service will not be started and a deployment failure will be returned.

8. A workflow engine and rule engine conversion control system according to claim 7, characterized in that: When deploying a workflow, after the Netty data source producer is successfully started, the conversion control system ZTran passes the relevant rule data to the rule engine ZRE, builds a data source consumer and starts the Netty client. After the Netty data source consumer is started, the rule data is compiled and cached in the memory, and then the corresponding data source producer Netty server is connected and a long connection is maintained.

9. A workflow engine and rule engine conversion control system according to claim 7, characterized in that: After the Netty server and the Netty client are successfully connected, the process converter of the conversion control system ZTran reversely generates the BPMN2.0 standard workflow description file based on the ZNode information of the associated rule data in the workflow, and pushes it to the workflow engine ZWE. The workflow engine ZWE starts the workflow instance based on this XML file and starts executing process activities.

Citation Information

Patent Citations

  • Flow implementation method and system based on rule engine

    CN112990850A

  • WEB system development framework based on combination of form drive combined with dynamic rule engine

    CN113849178A

  • Enterprise-level workflow engine implementation method and system based on micro-service SaaS

    CN114493479A

  • Configurable system and method based on rule engine, device, and storage medium

    WO2019179056A1