Business rule engine system with flexible configuration capability and design method thereof

Abstract

The invention discloses a business rule engine system with flexible configuration capability and a design method thereof, and the business rule engine system realizes different triggering conditions of different organizations for the same rule through differentiated configuration; meanwhile, external data can be obtained through a data sharing interface to serve as parameters for rule judgment and execution. The engine supports various types of business rules, is high in flexibility, and can be flexibly configured in a differentiated manner according to actual requirements; data interaction and sharing with other systems can be conveniently carried out, and expansion is easy; the system is simple in configuration, and can effectively meet the complex and changeable business requirements of a Chinese building construction integrated platform.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of building informatization, in particular to a business rule engine system and a design method thereof. BACKGROUND

[0002] In the process of building project management, a large number of business rules and processes are involved, such as verification rules, risk rules, and custom rules. The traditional processing method often relies on manual review and judgment, which is not only inefficient but also prone to errors. With the continuous development of information technology, the business rule engine, as an intelligent processing tool, has been gradually applied in the field of building project management. However, the existing business rule engine systems mostly have problems such as complex configuration and insufficient flexibility, which are difficult to meet the efficiency and accuracy requirements of the development platform for business rule processing. SUMMARY

[0003] The present application provides a business rule engine design method based on a unified development platform and having flexible configuration capability. The engine system designed based on the method has the advantages of simple configuration, strong flexibility, and easy extension, and can efficiently process various business rules in building project management.

[0004] The business rule engine design method provided by the present application has the following steps: S1: defining new business rules and designing the basic information of the rules, including: rule type, rule trigger time, branch condition in the rule, and execution action; S2: configuring the rules, including: parameters, variables, and data that the rule branch condition and execution action depend on; S3: when different organizations or projects have different trigger conditions for the same rule, differentiating the configuration of the rule; S4: enabling and deploying the business rule.

[0005] Compared with the prior art, the present application has the following advantages: (1) strong flexibility: supporting multiple types of business rules and allowing differentiated and flexible configuration according to actual needs; (2) easy to extend: through data sharing interfaces, data interaction and sharing with other systems can be easily realized; (3) automatically processing business rules, efficient and accurate; (4) through the visual interface, the configuration and acquisition of parameters are realized by using the relevance of forms and data interfaces, reducing the complexity of configuration; (5) supporting multiple trigger methods, which can be triggered by program code running in a specified scenario, or by configuring the operation action button of the form associated with the platform. BRIEF DESCRIPTION OF DRAWINGS

[0006] The above and other objects, features and advantages of this disclosure will become more apparent from the more detailed description of exemplary embodiments of this disclosure taken in conjunction with the accompanying drawings, in which the same reference numerals generally represent the same components.

[0007] Figure 1 A schematic diagram illustrating the design and implementation process of the business rules engine based on this disclosure; Figure 2 Flowchart for updating rule scripts to serve business users; Figure 3 To execute rules and processes for business stakeholders. Detailed Implementation

[0008] Preferred embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art.

[0009] This disclosure provides a business rules engine with flexible configuration capabilities, designed to improve the efficiency and accuracy of business processing in construction project management.

[0010] In one exemplary implementation, the design of the business rules engine mainly consists of two phases: (1) Phase 1: Rule Design and Configuration Phase The main process for business users to design rules is as follows: maintenance of basic rule information, management of rule parameters, management of associated data, management of variables, and design of rule expressions.

[0011] This phase involves basic information configuration, parameter management, data association, variable management, branch conditions, and execution action design, specifically including: a. Basic information configuration: Associate specific business documents.

[0012] b. Parameter Management: The parameter refers to the key parameter that needs to be judged in the rule branch condition. Its threshold value can be a constant, such as 10:00; or it can be a variable, such as time.

[0013] In this embodiment, by associating with specific business documents, the condition parameter key in the rules is extracted and selected directly from the drop-down list during configuration, reducing the workload of configuration.

[0014] c. Related Data: Through data interfaces, data interaction and sharing with other systems are achieved, and external data that the rule execution depends on is injected.

[0015] The interface can be provided in the form of API, including input parameters and output parameters. The data sharing system obtains relevant data through the input parameters provided by the rule engine system and then returns it in the form of output parameters.

[0016] d. Variable Management: Used for managing variables in rules.

[0017] For example, the threshold value variable used as the parameter key, and the differentiated variables designed for differentiated business rules, so that different organizations can set different trigger conditions for the same rule.

[0018] e. Branching conditions and execution action design: Configure appropriate execution rules using various parameters, variables, and conditions, and determine the actions to be executed after the rules are met. For example: When the contract amount (the key obtained from the corresponding form) is greater than the application amount (related data, which can generally be an external API), a certain action is executed.

[0019] (2) Phase Two: Business Rule Implementation Phase The runtime process involves fetching rule scripts, executing rules, and providing feedback on the execution results.

[0020] Based on the above approach, a business rule engine system designed for China's integrated construction platform is constructed. This system can efficiently manage and execute various business rules, including verification rules, risk rules, and custom rules, and mainly includes: (1) Rule definition module: used to define and manage various business rules, including rule types (validation rules, risk rules and custom rules), rule triggering events or triggering times, branching conditions within the rules and execution rules, etc.

[0021] (2) Rule execution module: Based on user operation or system trigger conditions, execute the corresponding business rules and return the processing results.

[0022] (3) Differentiated configuration module: Provides differentiated rule configuration functions for different organizations or projects to meet business needs in different scenarios.

[0023] (4) Interface Management Module: Used to configure and manage interfaces with external systems to enable data interaction and sharing.

[0024] In this embodiment, the design and implementation process of the rules engine is as follows: Figure 1 As shown, the main steps include: 1. Step 1: In the rule definition module, add a new business rule and configure the design of basic information, parameter management information, associated data (if needed), variable management (if needed), rule branch conditions and execution actions, etc.

[0025] 2. Step Two: Based on business needs, select the appropriate rule type (such as verification rule, risk rule, or custom rule) and configure the corresponding triggering time and execution action. Among them: (1) Verification rules The system supports configuring validation rules to verify whether form fields conform to preset rule designs. These rules can be triggered during actions such as saving, modifying, and submitting for review, and can perform actions such as prohibiting, prompting, or ignoring based on conditions. In this embodiment, the configuration of the validation rules is flexible, supporting multiple combinations of validation conditions for form fields to ensure the accuracy and compliance of the data.

[0026] (2) Risk rules The system supports setting risk rules to indicate whether form fields meet the risk level specified in the rule. Once a rule is triggered, the system will provide the corresponding risk level information to help users identify potential risks promptly.

[0027] The configuration of risk rules is also flexible, and different triggering times and conditions can be set according to business needs.

[0028] (3) Custom rules The system provides a custom rule function, allowing users to assign values ​​to form fields. When the set conditions are met, the system will assign values ​​to the output parameter fields, either constants or the values ​​of expressions.

[0029] Custom rules have a wide range of applications and can be used to automate the processing of form data and improve work efficiency.

[0030] 3. Step Three: On the rule design page, set the condition group and execution action. The condition group is used to define the conditions that trigger the rule, and the execution action is used to define the operation to be performed when the conditions are met.

[0031] In this embodiment, multiple triggering methods are supported. For example, the rules can be triggered by program code running in a set action scenario; or by configuring form action buttons (modify, add, delete, etc.) associated with the platform.

[0032] 4. Step Four: For business rules requiring differentiated configuration, set up variable management in the differentiated configuration module and reference these variables in the rule design page. Then, select the organization or project that requires differentiated configuration and configure the corresponding differentiated values.

[0033] This embodiment provides a rule-differentiated configuration function, allowing different organizations to set different trigger conditions for the same rule. This solves the problem of differences in business rules between different organizations and improves the applicability and flexibility of the system.

[0034] The configuration process for rule differentiation is simple and clear, and users can easily complete the configuration through the system interface.

[0035] 5. Step Five: Enable and deploy business rules. After deployment, the system can execute the corresponding business rules based on user actions or system trigger conditions and return the processing results.

[0036] The workflow for updating rules in a business service within a rule engine designed using this method is shown in the attached figure. Figure 2 As shown; the business side's execution rules and procedures are attached. Figure 3 As shown.

[0037] The business rule engine system provided in this embodiment is powerful and supports the setting and execution of various business rules, which can meet the complex and ever-changing business needs of the China Construction Integrated Construction Platform. Meanwhile, the system is easy to operate, and users can easily complete the configuration and management of various rules through the system interface; It has rich capabilities, such as the rule engine supporting the association of form data, making it easy to obtain rule configuration metadata, and supporting multiple data retrieval methods; It supports differentiated configuration, providing rule threshold differentiation configuration based on the organization dimension, allowing the same rule script to have different effective thresholds in different scenarios.

[0038] The above technical solutions are merely exemplary embodiments of the present invention. For those skilled in the art, based on the application methods and principles disclosed in the present invention, it is easy to make various types of improvements or modifications, and not limited to the methods described in the specific embodiments of the present invention. Therefore, the methods described above are merely preferred and not restrictive.

Claims

1. A design method for a business rules engine with flexible configuration capabilities, comprising the following steps: S1: Define new business rules and design the basic information of the rules, including: rule type, rule triggering time, branching conditions and execution actions in the rule; S2: Configure the rules, including: the rules' branch conditions and the parameters, variables, and data that the execution actions depend on; S3: When different organizations or projects have different triggering conditions for the same rule, the rule can be configured differently. S4: Enable and deploy business rules.

2. The method according to claim 1, characterized in that, The rule types include one or more of the following: verification rules, risk rules, and custom rules; wherein: The custom rules are used by users to assign values ​​to form fields and are triggered during automated form data processing. When the set branch conditions are met, the output parameter fields are assigned values, which are either constants or the values ​​of expressions.

3. The method according to claim 1, characterized in that, The parameters used to configure rules come from: Extract relevant fields from the associated specific business documents and select them from these fields when configuring the rules.

4. The method according to claim 3, characterized in that, When configuring rules that depend on data, the data acquisition methods include: Obtained through manual settings; Retrieve from the associated form; Data is obtained from relevant data sharing systems via data interfaces.

5. The method according to claim 4, characterized in that, The data interface includes: Public data interfaces provided by external systems, and data interfaces provided by internal systems; Methods for obtaining condition parameter threshold data from relevant systems via data interfaces include: According to the definition of the data interface, the conditional parameters in the rules are provided as input parameters to the data interface. Alternatively, if only one field is provided, the rule engine system will use the correlation between form fields to automatically complete the input parameters that need to be provided to the data interface; The relevant data sharing system obtains input parameters through the data interface, and after obtaining the values ​​of the parameters, it feeds them back to the rule engine as output parameters.

6. The method according to claim 1, characterized in that, The specific method of step S3 includes: For business rules that require differentiated configuration, define and manage the corresponding variables; Reference these variables in the rule design page; Then select the organization or project that needs differentiated configuration and configure the corresponding differentiated variable values ​​for the rule.

7. The method according to claim 1, characterized in that, Step S4 specifically includes: After the rules are deployed, the system judges the rules based on the triggering time and branch conditions, executes the corresponding business rules, and returns the processing results.

8. A business rule engine system with flexible configuration capabilities that applies the method described in any one of claims 1-7, characterized in that, include: Rule definition module: Used to define and manage various business rules; Differentiated configuration module: Provides differentiated rule configuration functions for different organizations or projects to meet business needs in different scenarios; Rule execution module: Based on user operations or system trigger conditions, execute the corresponding business rules and return the processing results; Interface Management Module: Used to configure and manage interfaces with external systems to enable data interaction and sharing.

Images