WO2020015191A1

WO2020015191A1 - Business rule releasing and managing method, electronic device and readable storage medium

Info

Publication number: WO2020015191A1
Application number: PCT/CN2018/108214
Authority: WO
Inventors: 赵骏; 宋杰
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-07-18
Filing date: 2018-09-28
Publication date: 2020-01-23
Also published as: CN109284106A

Abstract

The present application relates to a business rule releasing and managing method, an electronic device and a readable storage medium. The method comprises: providing a preset rule generation interface after a request for releasing a business rule is received; obtaining a preset original business rule of a uniform format uploaded by a user on the rule generation interface, and compiling, according to a preset rule, the original business rule to generate an executable business rule file; performing preset permission setting on the generated executable business rule file and pushing the generated executable business rule file to a test platform pre-deployed with a test environment for testing; and if the test is successful, establishing a rule version number for the generated executable business rule file, and releasing the executable business rule file of the rule version number to the corresponding one or more business systems. According to the application, there is no need to manually manage a large number of business rules, and the efficiency of business rule releasing and managing is improved.

Description

Method for publishing and managing business rules, electronic device and readable storage medium

Declaration of priority

This application is based on the Paris Convention and claims the priority of a Chinese patent application filed on July 18, 2018 with an application number of CN201810792782.5 and a name of "Publication Management Method, Electronic Device and Readable Storage Medium for Business Rules", which is a Chinese patent application The entire contents of the are incorporated herein by reference.

Technical field

The present application relates to the field of computer technology, and in particular, to a method for issuing and managing business rules, an electronic device, and a readable storage medium.

Background technique

At present, multiple business systems in large Internet finance companies involve a large number of rules engine applications. The rules applied in business systems need to be written by developers, compiled and tested manually, and then operated by related rule engine systems. Personnel cooperate with the push application to the business system. All operations are done manually. Business systems often need to change business rules. The existing manual management of business rules is inefficient.

Summary of the invention

The purpose of this application is to provide a method for publishing and managing business rules, an electronic device, and a readable storage medium, so as to improve the efficiency of publishing and managing business rules.

To achieve the above object, a first aspect of the present application provides an electronic device, the electronic device includes a memory and a processor, and the memory stores a release management system of a business rule that can run on the processor. When the release management system of a business rule is executed by the processor, the following steps are implemented:

Provide a preset rule generation interface after receiving a request to publish a business rule;

Acquiring a preset unified format original business rule uploaded by the user on the rule generation interface, and compiling the original business rule into an executable business rule file according to the preset rule;

Perform preset permission settings on the generated executable business rule file, and push the generated executable business rule file to a test platform with a test environment pre-deployed for testing;

If the test is successful, a rule version number is created for the generated executable business rule file, and the executable business rule file with the rule version number is published to the corresponding one or more business systems.

In addition, in order to achieve the foregoing objective, the second aspect of the present application also provides a method for managing and publishing a business rule. The method for managing and publishing a business rule includes:

Further, in order to achieve the above object, the third aspect of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores a release management system of business rules, and the release management system of the business rules may be at least A processor executes to cause the at least one processor to execute the steps of the method for publishing management of a business rule as described above.

The method for publishing and managing a business rule, an electronic device, and a readable storage medium provided in the present application, obtain a preset uniform business format original business rule uploaded by a user on a preset rule generation interface, and convert the original business according to the preset rule. Compile rules to generate executable business rule files; set preset permissions for the generated executable business rule files, and push the generated executable business rule files to a test platform with a test environment pre-deployed for testing; if the test is successful, Then, a rule version number is established for the generated executable business rule file, and the executable business rule file of the rule version number is published to the corresponding one or more business systems. Because the original business rules uploaded by users can be compiled into executable business rules files and pushed to a preset test platform, a test environment is deployed on the preset test platform, and the test environment and the real production environment are multiple business systems. The rule engine application environment is the same. If the executable business rule file formed by the test runs successfully in the test environment, the formed executable business rule file can be automatically pushed to the real production environment, that is, the rule engine application environment of multiple business systems. In order to realize automatic configuration, publishing and management of business rules, there is no need to manually manage a large number of business rules, which improves the efficiency of business rule publishing and management.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of an operating environment of a preferred embodiment of a release management system 10 for business rules of this application;

FIG. 2 is a schematic flowchart of an embodiment of a method for issuing and managing a business rule of this application.

detailed description

In order to make the purpose, technical solution, and advantages of the present application clearer, the following further describes the present application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

It should be noted that the descriptions related to "first" and "second" in this application are only for descriptive purposes, and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. . Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but must be based on those that can be realized by a person of ordinary skill in the art. When the combination of technical solutions conflicts or cannot be realized, such a combination of technical solutions should be considered nonexistent. Is not within the scope of protection claimed in this application.

This application provides a management system for issuing business rules. Please refer to FIG. 1, which is a schematic diagram of an operating environment of a preferred embodiment of a release management system 10 of a business rule of the present application.

In this embodiment, the business rule issuance management system 10 is installed and run in the electronic device 1. The electronic device 1 may include, but is not limited to, a memory 11, a processor 12, and a display 13. FIG. 1 only shows the electronic device 1 with components 11-13, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.

The memory 11 is at least one type of readable computer storage medium. In some embodiments, the memory 11 may be an internal storage unit of the electronic device 1, such as a hard disk or a memory of the electronic device 1. The memory 11 may also be an external storage device of the electronic device 1 in other embodiments, such as a plug-in hard disk, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, Flash card, etc. Further, the memory 11 may further include both an internal storage unit of the electronic device 1 and an external storage device. The memory 11 is configured to store application software installed on the electronic device 1 and various types of data, such as program codes of the distribution management system 10 of the business rule. The memory 11 may also be used to temporarily store data that has been or will be output.

In some embodiments, the processor 12 may be a central processing unit (CPU), a microprocessor, or other data processing chip, configured to run program codes or process data stored in the memory 11, such as A release management system 10 or the like that executes the business rules.

In some embodiments, the display 13 may be an LED display, a liquid crystal display, a touch-type liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, or the like. The display 13 is configured to display information processed in the electronic device 1 and to display a visual user interface, such as a preset rule generation interface, and a test result of an executable business rule file generated on a test platform. The components 11-13 of the electronic device 1 communicate with each other through a system bus.

The business rule release management system 10 includes at least one computer-readable instruction stored in the memory 11, and the at least one computer-readable instruction can be executed by the processor 12 to implement the embodiments of the present application.

Wherein, the execution management system 10 of the foregoing business rules implements the following steps when executed by the processor 12:

Step S1: After receiving a request for publishing a business rule, a preset rule generation interface is provided;

Step S2: Obtain a preset unified format original business rule uploaded by the user on the rule generation interface, and compile the original business rule into an executable business rule file according to the preset rule;

Step S3: Perform preset permission setting on the generated executable business rule file, and push the generated executable business rule file to a test platform with a test environment pre-deployed for testing;

Step S4: if the test is successful, establish a rule version number for the generated executable business rule file, and publish the executable business rule file with the rule version number to the corresponding one or more business systems.

In this embodiment, the business rule publishing management system receives a business rule publishing request from a user, for example, a business rule publishing request sent by a user through a terminal such as a mobile phone, a tablet computer, or a self-service terminal device, such as receiving a user on a mobile phone or tablet computer. , A business rule publishing request sent from a pre-installed client in a terminal such as a self-service terminal device, or a business rule publishing request sent by a user on a browser system in a terminal such as a mobile phone, tablet computer, or self-service terminal device.

In this embodiment, a user such as a developer can write original business rules such as various rule sets on a preset rule generation interface, and decompress, analyze, and compile the rule set written by the developer to form a runnable rule program. After the rule set compiled by the developer compiles the runnable rule program and sets the permissions and parameters (such as access rights and ownership), the runnable rule program can be pushed to a preset test platform. The preset test platform A test environment is deployed on the test environment, which is consistent with the real production environment, that is, the rule engine application environment of multiple business systems. If the testable runnable rule program runs successfully in the test environment, the formed runnable rule can be automatically The program is pushed to the real production environment, that is, the rule engine application environment of multiple business systems, to automatically configure, publish, and manage business rules.

Specifically, in this embodiment, when a business rule publication request from a user is received and a new version of a business rule needs to be established, the following steps are included:

Obtain users such as developers upload and write original business rules such as rule set zip packages. For example, a rule generation interface such as a rule compilation tool rule builder is set in advance. When a developer wants to add a new business rule to a business system, he can click the "rule writing" button on the business rule release management system. The rule release management system provides and displays the rule generator rule builder. Developers can write additional new business rules on the rule builder. Developers can click the "Upload" button after writing business rules. The business rule release management system can Compress the business rules written by developers into a unified format such as zip. Of course, developers can also compress the written business rules into a unified format such as zip, and then upload the business rule zip package to the business rule release management system, so that the business rule release management system zips the business rules in a uniform format. Package for subsequent processing.

The business rules release management system will decompress, analyze, and compile the uploaded rule set zip package to generate executable business rule files. Because the business rule file written by the developer based on the rule compilation tool rule builder is not a program that can be directly run, it needs to be parsed and compiled to become a program that can be run. Therefore, the business rule release management system decompresses, analyzes, and compiles the uploaded rule set zip package to generate an executable business rule file. The executable business rule file includes an enterprise-level application business rule ear package and an executable program SDK. package. Among them, the ear package is a set of business rules that can be run, and the SDK package is an executable program package that can be directly used by other systems such as business systems. For example, in a specific implementation, the rule compilation tool rule builder set in the release management system of the business rule can support natural language writing, and the developer can use the natural language on the rule builder in the release management system of the business rule. Write the added new business rules. Then, the business rules release management system decompresses, analyzes, and compiles the uploaded rule set zip package, and compiles the written natural language rule set into a working program language. For example, acquiring a natural language rule written by a user on the rule generation interface, that is, a rule compiling tool rule builder; extracting a preset identification vocabulary and a preset keyword vocabulary in the acquired natural language rule; The mapping relationship with the Java rule template determines the Java rule template corresponding to the preset identification word in the natural language rule, and converts the preset keyword sink in the natural language rule into a corresponding code, and converts the converted The code is filled to the corresponding position in the determined Java rule template; the filled Java rule template is compiled to generate an executable Java rule file.

Permissions and parameter settings. Users can set permissions on an executable business rule file compiled by a rule set compiled by a developer on the business rule release management system, including the enterprise-level application business rule ear package and the The access and download permission settings of the executable program SDK package, and the business system permission settings corresponding to the generated executable business rule file, etc. For example, you can set the access permissions of the executable business rules file, that is, which users can access to view and download the ear package and SDK package in the executable business rules file, or limit which corresponding applications the executable business rules file can belong to. On the business system, or set the executable business rule file to be associated with other versions of the executable business rule file, and so on. Further, in the business rule issuance management system of this embodiment, when different users log in, they can identify the identity information of different users according to their usernames, account numbers, etc., and classify and set permissions for users with different identities. Users are divided into four roles: developer, deployer, operator, and manager. These four roles have different operation rights on the release management system of business rules. The details are as follows: For developers, they can be allowed to Compile and download business rules (download the ear package and SDK package), and apply association configuration (for example, the same business system may use multiple business rule sets at the same time in the release management system of the business rules). Business rule sets). For deployers, they can be allowed to publish business rules in the release management system of the business rules (for example, the deployer will automatically push the test ok business rules to the real production environment, which is the corresponding business system). For operating personnel, they can be allowed to perform associated system management of business rules in the release management system of business rules (using business rules in several associated business systems), operation logs (such as business rule compilation logs, version logs, releases Logs, etc.) query, rights management (can manage the operation rights of different roles on the release management system of business rules), role authorization (authorize to the corresponding role according to different user identities). For management personnel, they can be allowed to perform business system related system management (using business rules in several related business systems) and operation logs (such as business rule compilation logs, version logs, and releases) in the business rule release management system. Logs, etc.) query, rights management (can manage the operation rights of different roles on the release management system of business rules), role authorization (authorize the corresponding role according to different user identities), and download (ear and SDK package download) .

One-click push test platform. After receiving the user's test instruction, the generated executable business rule file can be pushed to a preset test platform for testing. A test environment is deployed on the test platform. The test environment is consistent with the real production environment and the real production environment. That is, the rule engine application environment of one or more business systems that can be applied to the executable program language is set. At the same time, a rule version number of the generated executable business rule file is established.

Automatically push production environment. If the test executable business rule file runs successfully in the test environment, the generated executable business rule file can be automatically pushed to the real production environment, that is, one or more of the generated executable business rule file that can be applied A rule engine application environment for each business system to automatically publish business rules, making rule set publishing without the cooperation of rule engine system operators, reducing labor costs. In addition, if the executable business rule file formed by the test fails to run in the test environment, the version is rolled back according to the rule version number of each executable business rule file to ensure that when the newly added business rule is wrong, it can be restored Go to the previous correct version of the business rules to ensure the stable operation of related business systems.

Compared with the prior art, this embodiment obtains an original business rule of a preset unified format uploaded by a user on a preset rule generation interface, and compiles the original business rule into an executable business rule file according to the preset rule; Perform preset permission settings on the generated executable business rule file and push the generated executable business rule file to a test platform with a test environment pre-deployed for testing; if the test is successful, the generated executable business rule file A rule version number is established, and an executable business rule file of the rule version number is released to the corresponding one or more business systems. Because the original business rules uploaded by users can be compiled into executable business rules files and pushed to a preset test platform, a test environment is deployed on the preset test platform, and the test environment and the real production environment are multiple business systems. The rule engine application environment is the same. If the executable business rule file formed by the test runs successfully in the test environment, the formed executable business rule file can be automatically pushed to the real production environment, that is, the rule engine application environment of multiple business systems. In order to realize automatic configuration, publishing and management of business rules, there is no need to manually manage a large number of business rules, which improves the efficiency of business rule publishing and management.

Further, in an optional embodiment, on the basis of the above-mentioned embodiment of FIG. 1, when using the release management system of a business rule to update the version of a business rule, this embodiment includes the following steps:

Download an existing rule set.

The developer uploads the modified ruleset zip package. Developers can modify business rules on the rule compilation tool (rule builder) set in the release management system of the business rules. After the modification is completed, they can click the "Upload" button. The release management system of the business rules can The modified business rules written are compressed into a uniform format such as zip. Of course, developers can also compress and write the modified business rules into a unified format, such as zip, and then upload the business rule zip package to the business rule's release management system, so that the business rule's release management system can handle the business of the unified format. The regular zip package is used for subsequent processing.

The business rule release management system decompresses, analyzes, compiles and uploads the uploaded ruleset zip package to generate ear packages and SDK packages.

Permissions and parameter settings (application-related configuration such as access permissions and ownership, etc.).

One-click push test platform. Establish the rule CQ version number and push it to the test environment for deployment.

If the test is successful, the production environment is pushed; if the test is not successful, the version is rolled back.

Further, in an optional embodiment, when there is a problem with the current version of the business rule, this embodiment uses the business rule release management system to change the business rule, including the following steps:

Roll back the latest version of the business rule set to the previous version.

The developer obtains the rolled-back version of the business rule from the business rule's release management system, and makes modifications based on the previous version of the business rule. For example, the developer can set the rule compilation tool rule builder in the release management system of the business rule. Rule generator) to modify the previous version of the business rules. After the modification is complete, click the "Upload" button. The business rule release management system can compress the modified business rules written by the developer into a unified format such as zip processing. . Of course, developers can also compress and write the modified business rules into a unified format, such as zip, and then upload the business rule zip package to the business rule's release management system, so that the business rule's release management system can handle the business of the unified format. The regular zip package is used for subsequent processing.

Further, the business rule issuance management system in this embodiment supports a download function. For example, users who comply with the authority can download ear packages and SDK packages of different versions of business rules, and users can download ear packages and SDK packages of different versions of business rules. For development testing, you can also directly call the downloaded SDK package to apply to other rule engines that need to be used.

As shown in FIG. 2, FIG. 2 is a schematic flowchart of an embodiment of a method for publishing and managing a business rule of this application. The method for managing and publishing a business rule includes the following steps:

Step S10: After receiving a request for publishing a business rule, a preset rule generation interface is provided;

Step S20: Obtain a preset unified format original business rule uploaded by the user on the rule generation interface, and compile the original business rule into an executable business rule file according to the preset rule;

Step S30: Perform preset permission setting on the generated executable business rule file, and push the generated executable business rule file to a test platform with a test environment deployed in advance for testing;

Step S40: If the test is successful, establish a rule version number for the generated executable business rule file, and publish the executable business rule file with the rule version number to the corresponding one or more business systems.

Further, in an optional embodiment, on the basis of the above embodiment, when using the release management system of a business rule to update the version of a business rule, this embodiment includes the following steps:

Download an existing rule set.

Roll back the latest version of the business rule set to the previous version.

The developer obtains the rolled-back version of the business rule from the business rule's release management system, and makes modifications based on the previous version of the business rule. For example, the developer can set the rule compilation tool rule builder in the release management system of the business rule. Rule generator) to modify the previous version of the business rules. After the modification is complete, click the "Upload" button. The business rule release management system can compress the modified business rules written by the developer into a unified format such as zip processing. . Of course, developers can also compress and write the modified business rules into a unified format, such as zip, and then upload the business rule zip package to the business rule's release management system, so that the business rule's release management system can handle the business of the unified format The regular zip package is used for subsequent processing.

Further, the download function is supported in this embodiment. For example, users who comply with the authority can download ear packages and SDK packages of different versions of business rules. Users can download ear packages and SDK packages of different versions of business rules for development and testing. Invoke the downloaded SDK package to apply it to other required rule engines.

In addition, the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores a release management system of business rules, and the release management system of the business rules can be executed by at least one processor, so that the At least one processor executes the steps of the method for publishing and managing a business rule in the foregoing embodiment. The specific implementation processes of steps S10, S20, and S30 of the method for publishing and managing a business rule are as described above, and are not repeated here.

It should be noted that, in this article, the terms "including", "including" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, It also includes other elements not explicitly listed, or elements inherent to such a process, method, article, or device. Without more restrictions, an element limited by the sentence "including a ..." does not exclude that there are other identical elements in the process, method, article, or device that includes the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, can also be implemented by hardware, but in many cases the former is Better implementation. Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, The optical disc) includes several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of the present application.

The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and thus do not limit the scope of rights of the present application. The above-mentioned serial numbers of the embodiments of the present application are merely for description, and do not represent the superiority or inferiority of the embodiments. In addition, although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

Those skilled in the art can implement this application without departing from the scope and essence of this application. For example, the features of one embodiment can be used in another embodiment to obtain another embodiment. Any modification, equivalent replacement and improvement made within the application of the technical idea of this application shall fall within the scope of rights of this application.

Claims

An electronic device is characterized in that the electronic device includes a memory and a processor, and the memory stores a release management system of a business rule that can run on the processor, and the release management system of the business rule is When the processor executes, the following steps are implemented:

Provide a preset rule generation interface after receiving a request to publish a business rule;

Acquiring a preset unified format original business rule uploaded by the user on the rule generation interface, and compiling the original business rule into an executable business rule file according to the preset rule;

Perform preset permission settings on the generated executable business rule file, and push the generated executable business rule file to a test platform with a test environment pre-deployed for testing;

If the test is successful, a rule version number is created for the generated executable business rule file, and the executable business rule file with the rule version number is published to the corresponding one or more business systems.
The electronic device according to claim 1, wherein the processor is further configured to execute a release management system of the business rule to implement the following steps:

If the test fails, the version is rolled back according to the rule version number of the generated executable business rule file, and the executable business rule file corresponding to the previous rule version number of the rule version number is published to the corresponding one or more services. System; or,

If the business rule on the business system runs incorrectly, the business rule on the business system is automatically rolled back to the executable business rule corresponding to the previous rule version number of the current rule version number.
The electronic device according to claim 1, wherein the generated executable business rule file comprises an enterprise-level application business rule ear package and an executable program SDK package.
The electronic device according to claim 3, wherein the preset permission setting of the generated executable business rule file comprises:

Access and download permission settings for the enterprise-level application business rule ear package and executable program SDK package in the generated executable business rule file, and the business system permission settings to which the generated executable business rule file corresponds.
The electronic device according to claim 1, wherein the original business rules of the preset unified format uploaded by the user on the rule generation interface are natural language rules, and the presets uploaded by the user on the rule generation interface are acquired The steps of uniformly formatting the original business rule and compiling the original business rule into an executable business rule file according to a preset rule include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine the Java rule template corresponding to the preset identification vocabulary in the natural language rule according to the mapping relationship between the predetermined preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
The electronic device according to claim 2, wherein the original business rules of the preset unified format uploaded by the user on the rule generation interface are natural language rules, and the presets uploaded by the user on the rule generation interface are acquired The steps of uniformly formatting the original business rule and compiling the original business rule into an executable business rule file according to a preset rule include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine the Java rule template corresponding to the preset identification vocabulary in the natural language rule according to the mapping relationship between the predetermined preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
The electronic device according to claim 3, wherein the original business rules of the preset unified format uploaded by the user on the rule generation interface are natural language rules, and the presets uploaded by the user on the rule generation interface are acquired The steps of uniformly formatting the original business rule and compiling the original business rule into an executable business rule file according to a preset rule include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine the Java rule template corresponding to the preset identification vocabulary in the natural language rule according to the mapping relationship between the predetermined preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
The electronic device according to claim 4, wherein the original business rules of the preset uniform format uploaded by the user on the rule generation interface are natural language rules, and the presets uploaded by the user on the rule generation interface are acquired The steps of uniformly formatting the original business rule and compiling the original business rule into an executable business rule file according to a preset rule include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine a Java rule template corresponding to the preset identification vocabulary in the natural language rule according to a predetermined mapping relationship between the preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
A method for publishing and managing a business rule is characterized in that the method for publishing and managing a business rule includes:

Provide a preset rule generation interface after receiving a request to publish a business rule;

Acquiring a preset unified format original business rule uploaded by the user on the rule generation interface, and compiling the original business rule into an executable business rule file according to the preset rule;

Perform preset permission settings on the generated executable business rule file, and push the generated executable business rule file to a test platform with a test environment pre-deployed for testing;

If the test is successful, a rule version number is created for the generated executable business rule file, and the executable business rule file with the rule version number is published to the corresponding one or more business systems.
The method for publishing and managing a business rule according to claim 9, further comprising:

If the test fails, the version is rolled back according to the rule version number of the generated executable business rule file, and the executable business rule file corresponding to the previous rule version number of the rule version number is published to the corresponding one or more services. System; or,

If the business rule on the business system runs incorrectly, the business rule on the business system is automatically rolled back to the executable business rule corresponding to the previous rule version number of the current rule version number.
The method according to claim 9, wherein the generated executable business rule file comprises an enterprise-level application business rule ear package and an executable program SDK package.
The method according to claim 11, wherein the preset permission setting of the generated executable business rule file comprises:

Access and download permission settings for the enterprise-level application business rule ear package and executable program SDK package in the generated executable business rule file, and the business system permission settings to which the generated executable business rule file corresponds.
The method for publishing and managing a business rule according to claim 9, characterized in that the original business rule of the preset uniform format uploaded by the user on the rule generation interface is a natural language rule, and the acquiring user uses the rule generation interface The steps of uploading the original business rules in a preset unified format, and compiling the original business rules into an executable business rule file according to the preset rules include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine the Java rule template corresponding to the preset identification vocabulary in the natural language rule according to the mapping relationship between the predetermined preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
The method for publishing and managing a business rule according to claim 10, wherein the original business rule of a preset uniform format uploaded by the user on the rule generating interface is a natural language rule, and the acquiring user uses the rule generating interface The steps of uploading the original business rules in a preset unified format, and compiling the original business rules into an executable business rule file according to the preset rules include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine the Java rule template corresponding to the preset identification vocabulary in the natural language rule according to the mapping relationship between the predetermined preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
The method for managing the issuance of a business rule according to claim 11, characterized in that the original business rules of the preset uniform format uploaded by the user on the rule generation interface are natural language rules, and the acquiring user uses the rule generation interface The steps of uploading an original business rule in a preset unified format and compiling the original business rule into an executable business rule file according to the preset rule include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine the Java rule template corresponding to the preset identification vocabulary in the natural language rule according to the mapping relationship between the predetermined preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
The method for managing the issuance of a business rule according to claim 12, wherein the original business rule of a preset unified format uploaded by the user on the rule generation interface is a natural language rule, and the acquiring user is on the rule generation interface The steps of uploading an original business rule in a preset unified format and compiling the original business rule into an executable business rule file according to the preset rule include:

Obtaining a natural language rule written by a user on the rule generation interface;

Extracting the preset identification vocabulary and preset keywords in the acquired natural language rules;

Determine a Java rule template corresponding to the preset identification vocabulary in the natural language rule according to a predetermined mapping relationship between the preset identification vocabulary and the Java rule template, and convert the preset keyword pool in the natural language rule For the corresponding code, fill the converted code to the corresponding position in the determined Java rule template;

Compile the filled Java rule template to generate an executable Java rule file.
A computer-readable storage medium is characterized in that a release management system of a business rule is stored on the computer-readable storage medium, and when the release management system of the business rule is executed by a processor, the following steps are implemented:

Provide a preset rule generation interface after receiving a request to publish a business rule;

Acquiring a preset unified format original business rule uploaded by the user on the rule generation interface, and compiling the original business rule into an executable business rule file according to the preset rule;

Perform preset permission settings on the generated executable business rule file, and push the generated executable business rule file to a test platform with a test environment pre-deployed for testing;

If the test is successful, a rule version number is created for the generated executable business rule file, and the executable business rule file with the rule version number is published to the corresponding one or more business systems.
The computer-readable storage medium of claim 17, further comprising:

If the test fails, the version is rolled back according to the rule version number of the generated executable business rule file, and the executable business rule file corresponding to the previous rule version number of the rule version number is published to the corresponding one or more services. System; or,

If the business rule on the business system runs incorrectly, the business rule on the business system is automatically rolled back to the executable business rule corresponding to the previous rule version number of the current rule version number.
The computer-readable storage medium of claim 17, wherein the generated executable business rule file comprises an enterprise-level application business rule ear package and an executable program SDK package.
The computer-readable storage medium of claim 19, wherein the preset permission setting of the generated executable business rule file comprises:

Access and download permission settings for the enterprise-level application business rule ear package and executable program SDK package in the generated executable business rule file, and the business system permission settings to which the generated executable business rule file corresponds.