A rule configuration system, method, device, and medium

Abstract

This application discloses a rule configuration system, method, device, and medium, relating to the field of computer technology. The rule configuration system includes: a first module for configuring one or more rules, each rule including at least one input parameter; and a second module for invoking the rules and providing service implementation based on the business logic of the target node and the rules. This application can combine business logic with parameter rules, lowering the barrier to entry for technical personnel, while also allowing for flexible invocation of configured rules, resulting in a highly flexible system.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically to a rule configuration system, method, device, and medium. Background Technology

[0002] We are currently entering the knowledge economy era, and enterprises are gradually moving into the market economy. The global wave of information technology is impacting the financial management industry. Through a financial rules platform, the quality and efficiency of corporate financial management can be comprehensively improved, thereby translating into market effectiveness and competitiveness. Therefore, a good financial rules platform is crucial.

[0003] Existing financial rule platforms have the following drawbacks: 1. The rule engine places too high demands on technical personnel, requiring them to understand the corresponding scripting knowledge; 2. Technical personnel need to edit scripts online, and no syntax checking or advance compilation hints are provided; 3. The utilization rate of rule features is limited, as it is merely a rule engine encapsulated based on existing business logic, resulting in poor system flexibility.

[0004] Application content

[0005] To address at least one of the problems mentioned in the background art, this application provides a rule configuration system, method, device, and medium that can combine business logic with parameter rules, reducing the usage threshold for technical personnel, while also enabling flexible invocation of configured rules, resulting in good system flexibility.

[0006] The specific technical solutions provided in this application are as follows:

[0007] Firstly, a rule configuration system is provided, including:

[0008] The first module is used to configure one or more rules, each rule including at least one input parameter;

[0009] The second module is used to invoke the rules and provide service implementation based on the business logic of the target node and the rules.

[0010] Furthermore, the first module also provides a visualization page for configuring one or more rules;

[0011] The visualization page is also used to edit and / or manage the rules.

[0012] Furthermore, the rule also includes at least one judgment condition, which is used to determine whether the input parameter satisfies the condition information;

[0013] The rule also includes processing logic, which is executed in response to satisfying all the determination conditions under the rule.

[0014] Furthermore, the rule also includes corresponding header information, which includes attribute values;

[0015] The attribute value is used to determine the execution priority of the rule when all the determination conditions under multiple rules are met simultaneously.

[0016] The larger the attribute value, the higher the execution priority.

[0017] Furthermore, the system also includes:

[0018] The third module is used to provide service interfaces and store the correspondence between the service interfaces and the service implementations.

[0019] Furthermore, the service interface is defined according to the rules, and the service implementation is provided based on the definition information of the service interface.

[0020] Furthermore, the system also includes:

[0021] The fourth module is used to identify the service class that implements the service interface and pass the service class to the rule corresponding to the service interface for use by the rule.

[0022] Secondly, a rule configuration method is provided, including:

[0023] Configure one or more rules, each rule including at least one input parameter;

[0024] The rules are invoked to provide services based on the business logic of the target node and the rules themselves.

[0025] Thirdly, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the rule configuration method when executing the program.

[0026] Fourthly, a computer-readable storage medium is provided, storing computer-executable instructions for executing the rule configuration method.

[0027] The embodiments of this application have the following beneficial effects:

[0028] This application provides a rule configuration system, method, device, and medium that can combine financial rules and business systems, achieving the integration of underlying technology and engineering projects. Simultaneously, it can combine financial rule services and a series of customized standards on a rule engine, utilizing industry-leading rule engine technology to create a financial rule platform suitable for financial business logic. Based on the concept of input and output, the financial rule platform is independent, modularized, and can be integrated with any business system. It provides service interfaces, enables controllable design, offers manageable flexibility, and ensures security and reliability. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This diagram illustrates the structure of the rule configuration system provided in an embodiment of this application.

[0031] Figure 2 A schematic diagram illustrating a visual interface according to an embodiment of this application;

[0032] Figure 3 A simplified rule configuration diagram of a visual interface according to an embodiment of this application is shown.

[0033] Figure 4 A schematic diagram illustrating the complex rule configuration of a visual interface according to an embodiment of this application is shown.

[0034] Figure 5 This diagram illustrates the interaction between a financial rules platform and a business system according to an embodiment of this application.

[0035] Figure 6 This document shows a general flowchart of the rule configuration method provided in an embodiment of this application;

[0036] Figure 7 Exemplary systems that can be used to implement the various embodiments described in this application are shown. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0038] It should be understood that, in the description of this application, unless the context explicitly requires it, the words "comprising," "including," and similar terms throughout the specification and claims should be interpreted as encompassing rather than being exclusive or exhaustive; that is, meaning "including but not limited to."

[0039] It should also be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0040] It should be noted that the terms "S1," "S2," etc., are used only for descriptive purposes and do not specifically refer to the order or sequence, nor are they intended to limit this application. They are merely for the convenience of describing the method of this application and should not be construed as indicating the sequential order of the steps. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0041] Example 1

[0042] This application provides a rule configuration system 100, referring to... Figure 1 ,include:

[0043] The first module 101 is used to configure one or more rules, each rule including at least one input parameter;

[0044] The second module 102 is used to invoke rules and provide service implementation based on the business logic of the target node and the rules.

[0045] Specifically, the first module 101 may include a front-end, i.e., the website's front-end, which is provided for users to browse. The front-end may include a web front-end, an app front-end, a mini-program, etc. Users can configure login rules through the front-end login rule configuration system 100. The front-end may include login pages adapted to various organizations for user login. When configuring login rules through the login rule configuration system 100, users can enter their account information in the input boxes on the login page of the rule configuration system 100. The account information may include a username and password, and then a login request is sent to the back-end through the login control on the login page.

[0046] Specifically, authorized users can perform front-end development, which includes implementing the website's front-end code. This can correspond to markup languages ​​such as HTML (HyperText Markup Language), CSS (Cascading Style Sheets), and JavaScript, used to display web pages. The latest advanced versions include HTML5, CSS3, and SVG.

[0047] Specifically, the second module 102 may include a backend, which may correspond to business logic code, database interactions, etc. The backend can also obtain the user's account information from the login request and confirm whether the account information is correct, that is, verify whether the username and password match the user data. If they match, the login rule configuration system 100 is allowed; if they do not match, relevant warning information is displayed to remind the user that the account information was entered incorrectly. The warning information may include: username or password error.

[0048] Specifically, users can invoke rules on the backend, as the backend handles business logic code and database interactions. Therefore, users can combine the target node's business logic, database interactions, and pre-configured financial rules on the frontend to complete the service and business processing. In this process, because the frontend financial rules are already configured, users only need to understand the functionality of the corresponding financial rules, without needing to understand the scripting knowledge. This low barrier to entry allows users to freely invoke and combine multiple financial rules based on their needs. This reduces the barrier to entry while improving business and development efficiency.

[0049] Specifically, refer to Figure 5The rule configuration system can include a financial rule platform, which can be used to process financial data, handle financial transactions, and provide financial business implementation. Based on this, rules can be financial rules, configuring financial conditions; when these conditions are met, financial processing logic is executed. The financial rule platform is based on a rule engine and can be combined with financial services and a series of customized standards. It can integrate a rule SDK, giving the financial rule platform modularity and independence, allowing it to be integrated with any business system and offering strong adaptability.

[0050] In some embodiments, refer to Figure 2 The first module 101 also provides a visualization page for configuring one or more rules; the visualization page is also used to edit and / or manage the aforementioned rules.

[0051] Specifically, Figure 2 This diagram illustrates the visual interface. Users can create / configure rules within the interface based on their permissions; and perform operations on these rules. These operations can include editing, deleting, grouping, naming, renaming, and adding notes, etc. Because the number of financial rules is enormous in actual business operations, naming, renaming, and grouping them allows for effective differentiation of financial rules. Grouping financial rules through functions or processing logic also aids in prioritizing them.

[0052] Specifically, users can also obtain financial rule information from the notes within the visual interface to understand the processing logic and implementation of the financial rules. By accessing information such as the creator, updater, creation date, and update date of each financial rule, users can quickly understand its basic information. The pagination feature and customizable number of items per page allow users to select the number of rules they wish to view per page, resulting in a better user experience. Users can also search for the financial rules they need.

[0053] In some embodiments, the rule further includes at least one decision condition, which is used to determine whether the input parameter satisfies the condition information; the rule further includes processing logic, which is executed in response to all decision conditions under the rule being satisfied.

[0054] In some embodiments, the rule also includes corresponding header information, which includes attribute values;

[0055] The attribute value is used to determine the execution priority of a rule when all the decision conditions under multiple rules are met simultaneously; the larger the attribute value, the higher the execution priority.

[0056] Specifically, the configuration information for financial rules can include the financial rule name, financial rule header information, whether the rule is met (financial rule condition information), the processing logic when the financial rule conditions are met, and remarks. The financial rule name is consistent with the naming convention used in the front-end; the remarks information is mainly used to provide a functional explanation of the financial rule.

[0057] For example, refer to Figure 2 as well as Figure 3 , Figure 3 This illustrates a simple rule configuration diagram based on a visual interface. (Corresponding...) Figure 2 As can be seen from the `GROUP_INTFC_CONVERT`, this group primarily performs interface conversion. The following explanation focuses on the financial rule named `DATA_CONVERT_ARINTRECIN_SOURC ENAME_YL_PAY`. Its condition is "if the payment's sourceName equals YL_PAY", with the corresponding decision code `ArintRecin(sourceName == "YL_PAY")`. The corresponding processing logic is "convert sourceName to ORDER", with the logic code `ArintRecin.setSourceName("ORDER")`. The input parameter is `sourceName`, and its value is the value of `sourceName`. The implementation process is as follows: the external system has already read the value of the data source name, and it checks whether the value of that data source name is YL_PAY. Here, YL_PAY specifically refers to UnionPay payment. That is, it checks whether the financial data source is UnionPay payment data. If it is UnionPay payment data, its source (data source name) is uniformly converted to "ORDER" so that downstream services can identify it and continue data processing. Of course, YL_PAY here can also be changed to other values ​​to include other payment methods, such as WeChat Pay, Alipay, and payments from other organizations.

[0058] For example, refer to Figure 2 as well as Figure 4 , Figure 4 The illustrated financial rule is an implementation of accounts receivable data processing for a single company. This rule includes three decision conditions, two of which are iterative. The processing logic under this rule will only be executed if all three conditions are met simultaneously. This processing logic comprises a script containing multiple statements, each representing a logic block. It can be combined with existing code to create more complex financial rules. Alternatively, it can be nested with other code for further integration.

[0059] For example, refer to Figure 4 The financial rule includes header information. This header information can include attribute values, specifically the `salience` attribute. Under this financial rule, the `salience` attribute has a value of 20, and this value determines the priority of the financial rule. A higher attribute value indicates a higher execution priority. You can choose to execute the financial rule with the highest priority (the one with the largest `salience` value), execute rules in descending order of priority, or select the first few rules in the priority order. The execution method can be determined based on the specific use case.

[0060] In some embodiments, the rule configuration system 100 further includes:

[0061] Module 3, 103, provides service interfaces and the correspondence between these interfaces and service implementations. The service interfaces are defined according to rules, and the service implementations are provided based on the definition information of the service interfaces.

[0062] For example, a service interface is defined based on financial rules. Meeting these rules constitutes implementing the service interface. After implementation, the ruleManager is configured in Drools global, and the service class implementing the interface is a read-only API (Application Programming Interface), which cannot be updated or written. This prevents the rule engine from becoming overly flexible. This technical solution ensures that the flexibility of financial rules is controllable, achieving a robust control design that improves development flexibility while guaranteeing security and reliability.

[0063] In some embodiments, the rule configuration system 100 further includes:

[0064] The fourth module 104 is used to identify the service class that implements the service interface and pass the service class to the rule corresponding to the service interface for the rule to use.

[0065] Specifically, by customizing standardized designs, service classes that conform to financial rules can be automatically scanned, i.e., the service classes that implement service interfaces mentioned above. These service classes can then be injected into the financial rules for use by the financial rules, providing diversified services.

[0066] In this embodiment, financial rules and business systems can be combined to achieve the integration of underlying technology and engineering projects. At the same time, financial rule services and a series of customized standards can be combined on the rule engine to create a financial rule platform suitable for financial business logic using industry-leading rule engine technology. Based on the concept of input and output, the financial rule platform is independent, modularized, and can be combined with any business system. It provides service interfaces, realizes controllable design, has controllable flexibility, and ensures security and reliability.

[0067] Example 2

[0068] Corresponding to the above embodiments, this application also provides a rule configuration method, referring to... Figure 6 The methods include:

[0069] S1. Configure one or more rules, wherein the rules include at least one input parameter.

[0070] S2. Invoke the rules to provide services based on the business logic of the target node and the rules.

[0071] In some embodiments, S1 further includes:

[0072] S11. Configure one or more rules, and edit and / or manage the rules.

[0073] Specifically, authorized users can perform front-end development, extracting simple logic and service implementations from the software code and presenting them on a visual interface as an online financial rules platform. Rules can be configured, edited, and managed within this platform. Rules can be sourced from various sources, supporting online changes to rules from page-based rules and Maven-Java projects.

[0074] In some embodiments, the rule further includes at least one decision condition, which is used to determine whether the input parameter satisfies the condition information; the rule further includes processing logic, which is executed in response to all decision conditions under the rule being satisfied.

[0075] In some embodiments, the rule also includes corresponding header information, which includes attribute values;

[0076] The attribute value is used to determine the execution priority of a rule when all the decision conditions under multiple rules are met simultaneously; the larger the attribute value, the higher the execution priority.

[0077] Specifically, the configuration information for financial rules can include the financial rule name, financial rule header information, whether the rule is met (financial rule condition information), the processing logic when the financial rule conditions are met, and remarks. The financial rule name is consistent with the naming convention in the front end; the remarks information is mainly used to provide a functional explanation of the financial rule.

[0078] Specifically, header information can include attribute values. In actual business processing, various rules exist, and multiple similar rules within the same family or group may simultaneously satisfy all the decision conditions under a given rule, thus fulfilling its execution logic. In this case, it's necessary to determine the execution priority or order of the rules. This can be done by determining the size of the attribute values ​​stored in the rule header information. Then, based on the specific use case, the execution logic of the rule is determined. Specific examples are detailed in the rule configuration system and will not be elaborated upon here.

[0079] In some embodiments, the method further includes:

[0080] S3. Define the service interface, and define and store the correspondence between the service interface and the service implementation.

[0081] In some embodiments, S3 further includes:

[0082] S31. Define a service interface according to the rules, obtain the definition information of the service interface, and provide service implementation according to the definition information.

[0083] In some embodiments, the method further includes:

[0084] S4. Obtain the service class that implements the service interface, and pass the service class to the rule corresponding to the service interface for use by the rule.

[0085] For example, refer to the following code:

[0086] / ** Code comment *executeRule(String group, Object...objects) The objects parameter has no order; the rule engine matches them based on class. * /

[0087] ruleManager.executeRule(ArConstants.Rule.GROUP_AUTOXLA,arCfgXlaAccount,arMainCashReceipt,arAutoAccountantSegment);

[0088] log.info(LoggerFormatUtil.toStrByMsgParams("Processing - Receipt Creation - Debit: Cash Already Received (REMITTANCE)","arAutoAccountantSegment Information",

[0089] JsonUtil.toStr(arAutoAccountantSegment)));}

[0090] Boolean flag=ArAutoAccountantSegmentUtil.validateArAutoAccountantSegment(arAutoAccountantSegment); String ccCode=ArAutoAccountantSegmentUtil.getCcCode(arAutoAccountantSegment);

[0091] if(flag){log.info(LoggerFormatUtil.toStrByMsgParams("Processing - Receipt Creation - Debit: Cash Already Remitted (REMITTANCE","Automatic Accounting Segment",ccCode));}

[0092] else { throw new JobRuntimeException("Incomplete segment information: " + ccCode);}

[0093] Specifically, this entire code snippet is equivalent to a rule SDK. `arCfgXlaAccount`, `arMainCashReceipt`, and `arAutoAccountantSegment` represent the first, second, and third financial rules, respectively, and are invoked within the code. After processing by these rules, the input data source information undergoes data modification and continues to participate in the overall processing logic. Similarly, one or more rules can be invoked according to actual needs, and they can be called from different locations within the code, thus offering high flexibility in usage.

[0094] Specifically, to prevent the financial rules platform from being too flexible, the scope of flexibility needs to be controlled. Service interfaces are introduced; only service classes that implement these interfaces can be passed the corresponding financial rules for use. This not only allows for control design through interface standards but also combines service classes, customized standards, and the rule engine, improving project iteration efficiency, managing the engine's flexibility risks, and achieving a balance between security and flexibility.

[0095] In this embodiment, users do not need extensive scripting knowledge or to upgrade their systems; they can adjust rules online. Furthermore, the diverse sources of rules allow for the integration of financial rules with business systems. Flexible rule management through service interfaces improves project iteration efficiency while ensuring system security and reliability.

[0096] Example 3

[0097] Corresponding to the above embodiments, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor can implement the above-described rule configuration method when executing the program.

[0098] like Figure 7 As shown, in some embodiments, the system can function as any of the aforementioned electronic devices for rule configuration methods in each of the described embodiments. In some embodiments, the system may include one or more computer-readable media (e.g., system memory or NVM / storage device) having instructions and one or more processors (e.g., one or more processors) coupled to the one or more computer-readable media and configured to execute the instructions to implement the module and thus perform the actions described in this application.

[0099] In one embodiment, the system control module may include any suitable interface controller to provide any suitable interface to at least one of the processors(s) and / or any suitable device or component communicating with the system control module.

[0100] The system control module may include a memory controller module to provide an interface to the system memory. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0101] System memory can be used, for example, to load and store data and / or instructions for the system. In one embodiment, system memory may include any suitable volatile memory, such as suitable DRAM. In some embodiments, system memory may include Double Data Rate Type Quad Synchronous Dynamic Random Access Memory (DDR4 SDRAM).

[0102] In one embodiment, the system control module may include one or more input / output (I / O) controllers to provide interfaces to the NVM / storage device and (one or more) communication interfaces.

[0103] For example, an NVM / storage device can be used to store data and / or instructions. An NVM / storage device may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable (one or more) non-volatile storage devices (e.g., one or more hard disk drives (HDDs), one or more optical disc drives (CDs), and / or one or more digital universal optical disc (DVD) drives).

[0104] NVM / storage devices may include storage resources that are physically part of a device on which the system is mounted, or that can be accessed by the device without necessarily being part of it. For example, an NVM / storage device may be accessed over a network via one or more communication interfaces.

[0105] One or more communication interfaces may provide the system with an interface to communicate over one or more networks and / or with any other suitable device. The system may wirelessly communicate with one or more components of a wireless network in accordance with any of the standards and / or protocols in one or more wireless network standards and / or protocols.

[0106] In one embodiment, at least one of the processors may be logically packaged with one or more controllers of the system control module (e.g., a memory controller module). In one embodiment, at least one of the processors may be logically packaged with one or more controllers of the system control module to form a system-in-package (SiP). In one embodiment, at least one of the processors may be integrated with the logic of one or more controllers of the system control module on the same die. In one embodiment, at least one of the processors may be integrated with the logic of one or more controllers of the system control module on the same die to form a system-on-a-chip (SoC).

[0107] In various embodiments, the system may be, but is not limited to, a server, workstation, desktop computing device, or mobile computing device (e.g., laptop computing device, handheld computing device, tablet computer, netbook, etc.). In various embodiments, the system may have more or fewer components and / or different architectures. For example, in some embodiments, the system includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0108] It should be noted that this application can be implemented in software and / or a combination of software and hardware, for example, using an application-specific integrated circuit (ASIC), a general-purpose computer, or any other similar hardware device. In one embodiment, the software program of this application can be executed by a processor to implement the steps or functions described above. Similarly, the software program of this application (including related data structures) can be stored in a computer-readable recording medium, such as RAM memory, magnetic or optical drives, floppy disks, and similar devices. Furthermore, some steps or functions of this application can be implemented in hardware, for example, as circuitry that cooperates with a processor to perform the various steps or functions.

[0109] Furthermore, a portion of this application can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to this application through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0110] Communication media include media through which communication signals containing, for example, computer-readable instructions, data structures, program modules, or other data are transmitted from one system to another. Communication media can include guided transmission media (such as cables and wires (e.g., optical fibers, coaxial cables, etc.)) and wireless (unguided transmission) media capable of propagating energy waves, such as sound, electromagnetic, RF, microwave, and infrared. Computer-readable instructions, data structures, program modules, or other data can be embodied as modulated data signals in, for example, wireless media (such as carrier waves or similar mechanisms embodied as part of spread spectrum technology). The term "modulated data signal" refers to a signal whose one or more characteristics are altered or set in a manner that encodes information in the signal. Modulation can be analog, digital, or a hybrid modulation technique.

[0111] Herein, one embodiment of this application includes an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the apparatus is triggered to run a method and / or technical solution based on the foregoing embodiments of this application.

[0112] Example 4

[0113] Corresponding to the above embodiments, this application also provides a computer-readable storage medium storing computer-executable instructions for executing a rule configuration method.

[0114] In this embodiment, a computer-readable storage medium may include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. For example, a computer-readable storage medium includes, but is not limited to, volatile memories such as random access memory (RAM, DRAM, SRAM); and non-volatile memories such as flash memory, various read-only memories (ROM, PROM, EPROM, EEPROM), magnetic and ferromagnetic / ferroelectric memories (MRAM, FeRAM); and magnetic and optical storage devices (hard disks, magnetic tapes, CDs, DVDs); or other currently known media or those developed hereafter capable of storing computer-readable information / data for use by a computer system.

[0115] Although preferred embodiments have been described in this application, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of this application.

[0116] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A rule configuration system, characterized in that, include: The first module is used to configure one or more rules, each rule including at least one input parameter; The second module is used to invoke the rules and provide service implementation based on the business logic of the target node and the rules. The third module is used to provide service interfaces and store the correspondence between the service interfaces and the service implementations; The fourth module is used to identify the service class that implements the service interface and pass the service class to the rule corresponding to the service interface for use by the rule; The service interface is defined according to the rules, and the service implementation is provided according to the definition information of the service interface. After implementing the service interface, configure it to the global variable of the business rule engine, and make the service class implementing the service interface a read-only interface; The rule also includes at least one judgment condition, which is used to determine whether the input parameter satisfies the condition information; The rule also includes processing logic, which is executed in response to satisfying all the determination conditions under the rule; The rule also includes corresponding header information, which includes attribute values; The attribute value is used to determine the execution priority of the rule when all the determination conditions under multiple rules are met simultaneously. The larger the attribute value, the higher the execution priority.

2. The rule configuration system according to claim 1, characterized in that, The first module also provides a visualization page for configuring one or more rules; The visualization page is also used to edit and / or manage the rules.

3. A rule configuration method for implementing the rule configuration system according to any one of claims 1 to 2, characterized in that, include: Configure one or more rules, each rule including at least one input parameter; Invoke the rules to provide service implementation based on the business logic of the target node and the rules; Provide service interfaces and store the correspondence between the service interfaces and the service implementations; Identify the service class that implements the service interface, and pass the service class to the rule corresponding to the service interface for use by the rule.

4. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the rule configuration method as described in claim 3.

5. A computer-readable storage medium storing computer-executable instructions, characterized in that... The computer-executable instructions are used to execute the rule method of claim 3.

Images