Disclosure of Invention
The invention aims to provide a low-code rule engine method and a platform supporting dynamic service adjustment, and aims to solve the problems in the background technology.
In order to solve the technical problems, the technical scheme of the invention is as follows:
in a first aspect, a low code rule engine method supporting dynamic traffic adaptation, the method comprising:
acquiring original rule data, wherein the original rule data comprises a plurality of condition items and corresponding action items for business judgment, and an initial rule pair is formed between each condition item and each action item;
Carrying out structural transformation on the original rule data, and unifying format specifications to obtain structural rule data;
Generating a visual rule assembly according to the structural rule data, presenting rule logic through a graphical interface, supporting business personnel to edit and modify under the condition of no need of coding, and converting a modification result into assembly rule data;
Analyzing and checking the component rule data in real time to obtain operation rule data;
Version identification is carried out on the operation rule data, and the operation rule data is stored in a rule warehouse;
And automatically selecting the operation rule data based on the current business context matching applicable version, and loading the operation rule data into a rule execution engine for execution.
Preferably, the method for obtaining the structural rule data includes the steps of:
extracting field information from each condition item in the original rule data, and carrying out standardized processing based on field types to form a standard condition field set;
Extracting execution parameters from each action item in the original rule data, and carrying out unified processing based on a parameter format to form a standard action parameter set;
And constructing structural rule data according to the standard condition field set and the standard action parameter set.
Preferably, the method includes generating a visual rule assembly according to structural rule data, presenting rule logic through a graphical interface, supporting service personnel to edit and modify without coding, and converting modification results into assembly rule data, including:
Generating a condition node assembly according to a standard condition field set in the structural rule data, wherein the condition node assembly displays condition attributes in the form of editable fields;
Generating an action node assembly according to a standard action parameter set in the structure rule data, wherein the action node assembly displays action contents in a parameter configuration form;
and combining the condition node component and the action node component through a logic connection line to form a rule link diagram, and extracting updating contents of the rule link diagram after a user edits and adjusts the rule link diagram in a graphical interface to generate corresponding component rule data.
Preferably, the analyzing and verifying the component rule data in real time to obtain operation rule data, where the operation rule data is adapted to a dynamic rule loading interface in an operation environment, includes:
Analyzing node attributes and connection relations in the component rule data, and reconstructing a rule expression set conforming to the execution engine standard;
Carrying out validity check on the rule expression set, and if conflict or deletion exists, returning an error prompt and preventing the generation of operation rule data;
And packing the rule expression set passing through the validity verification to generate operation rule data, wherein a rule version identifier is added in the operation rule data.
Preferably, the automatic selection of the operation rule data based on the matching applicable version of the current business context is carried out, and the operation rule data is loaded into a rule execution engine for execution, including:
Receiving current service context data, and extracting service identification information and environment attribute parameters;
Searching matching conditions in a rule warehouse according to the service identification information, and screening out an operation rule data version conforming to the environment attribute parameters;
and loading the screened operation rule data version into a rule execution engine memory area, and triggering the rule engine to execute corresponding rule logic to complete service judgment.
Preferably, extracting field information for each condition item in the original rule data, performing standardization processing based on field types to form a standard condition field set, including:
Extracting the field name, the field type and the field constraint information of each condition item according to the original rule data to generate a preliminary field set;
based on a preset field standardization rule, carrying out field type unified processing on the preliminary field set, and mapping fields with different sources and the same logic meaning into a standard field set;
Detecting field naming conflict in a standard field set, if the naming conflict exists and the field types are consistent, carrying out naming distinction by adding a data source identifier in the field names, and if the field types are inconsistent, refusing to combine and generating conflict warning information;
And generating a standard condition field set according to the standard field set after naming adjustment, and establishing a mapping relation between the original field and the standard field.
Preferably, the condition node component and the action node component are combined through a logic connection to form a rule link diagram, after the rule link diagram is edited and adjusted in the graphic interface by a user, the updating content of the rule link diagram is extracted to generate corresponding component rule data, and the method comprises the following steps:
generating a condition node set according to the standard condition field set, and setting a field editable attribute and a logic expression editing inlet in each condition node;
generating an action node set according to the standard action parameter set, and setting a parameter verification template and an execution configuration entry in each action node;
Establishing a connection relation between the conditional node set and the action node set based on a preset connection rule, only allowing node combinations conforming to service logic constraint, detecting whether the connection is legal or not in real time, prompting an error and prohibiting node connection storage if the connection violates the predefined constraint;
after the rule link diagram editing is completed, the node information and the connection relation which are changed are extracted, incremental update data are generated and fused into the component rule data, and updated component rule data are formed.
Preferably, the validity check on the regular expression set includes:
Extracting a rule expression set according to the updated component rule data, and establishing a reference index table according to the expression reference relation;
According to the reference index table, carrying out field validity check on each rule expression, and if the field is found to be not in the standard condition field set, recording field reference errors and positioning to a specific node;
Performing integrity check on the execution parameters of the action nodes in the rule expression, and if the necessary filling parameters are absent, recording the missing errors of the parameters and marking the missing errors to a parameter configuration interface;
Connectivity and logic rationality analysis are carried out on the connection relation of the regular link diagram, and if cyclic reference, isolated nodes or broken links exist, abnormal structure errors are recorded;
and generating a verification comprehensive report of the hierarchical prompt according to all the field reference errors, the parameter missing errors and the structure exception errors, and indicating error nodes and error types in a highlighting mode.
Preferably, generating a verification comprehensive report of the hierarchical hint according to all field reference errors, parameter missing errors and structural exception errors, and indicating error nodes and error types in a highlighting manner, wherein the method comprises the following steps:
extracting corresponding error node information according to the field reference errors, and listing the corresponding error node information in a verification comprehensive report in the form of node numbers and field names;
Extracting a missing parameter list of the action node according to the parameter missing error, and marking the missing of the necessary filling item and the position of the corresponding action node in the verification comprehensive report;
according to the structural anomaly errors, analyzing and forming an error connection relation graph, marking node path information with circulation, isolation or chain breakage, and drawing an anomaly link schematic in a verification comprehensive report;
classifying and summarizing the field reference errors, the parameter deletion errors and the structure abnormality errors respectively, giving priority identification, and displaying various error information according to the priority highlighting;
and setting an interactive jump function in the verification comprehensive report, and supporting the user to click the error item to be directly positioned to the corresponding node position in the graphical interface.
In a second aspect, a low code rule engine platform supporting dynamic business adaptation, the platform comprising:
the system comprises an original data acquisition module, a rule processing module and a rule processing module, wherein the original data acquisition module is used for acquiring original rule data, the original rule data comprises a plurality of condition items and corresponding action items for business judgment, and an initial rule pair is formed between each condition item and each action item;
the original data processing module is used for carrying out structural transformation on the original rule data and unifying format specifications to obtain structural rule data;
The rule component generating module is used for generating a visual rule component according to the structural rule data, presenting rule logic through a graphical interface, supporting business personnel to edit and modify under the condition of no need of coding, and converting a modification result into component rule data;
The rule analysis and verification module is used for analyzing and verifying the component rule data in real time to obtain operation rule data, and the operation rule data is adapted to a dynamic rule loading interface in an operation environment;
the version management module is used for carrying out version identification on the operation rule data and storing the operation rule data into a rule warehouse, wherein the rule warehouse is used for maintaining rule history version and change record and supporting rollback and reload of any version;
And the rule scheduling module is used for automatically selecting the operation rule data based on the matching application version of the current service context and loading the operation rule data into the rule execution engine for execution.
The scheme of the invention at least comprises the following beneficial effects:
The invention provides a low-code rule engine method supporting dynamic service adjustment, which effectively solves the problems of static deployment, rule adjustment lag and incapability of dynamically updating rules in real time in operation commonly existing in rule engines in the prior art. In the invention, the original rule data is obtained and is subjected to structural transformation, the format specification is unified, the structural rule data is formed, and the consistency and standardization of rule definition are ensured. By further generating a visual rule component according to the structural rule data and presenting rule logic on the graphical interface, service personnel are supported to edit and modify the rules under the condition of no need of coding, so that the response speed of service adjustment is greatly improved, and the dependence of rule change on development resources is reduced.
By analyzing and checking the component rule data in real time, the operation rule data adapting to the operation environment is generated, and the rule logic can be ensured to be quickly and accurately converted into an executable format. After the rule data is generated, the version identification is carried out on the rule data and is stored in a rule warehouse, so that the maintenance of the history version of the rule and the rollback and reloading of any version are supported, and the flexibility and traceability of rule management are effectively improved. Particularly importantly, the invention introduces a mechanism for dynamically matching the applicable version based on the current business context, can automatically select the running rule data version which is most in line with the current scene according to different business identification information and environment attribute parameters, and loads the running rule data version into a rule execution engine for immediate execution, thereby realizing the dynamic effect of rule logic without stopping.
Through the improvement, the invention can support the online dynamic adjustment of rule logic under the scene of high-frequency service adjustment such as insurance claim audit and the like, thereby avoiding the problem of delay of claim settlement decision caused by shutdown deployment required by rule change and remarkably improving customer experience. Meanwhile, when the insurance supervision policy is temporarily changed, new rules can be rapidly introduced or existing rules can be rapidly adjusted, the compliance risk generated due to untimely rule response is reduced, and the overall flexibility, stability and compliance are improved. In general, the method and the system have the prominent substantial characteristics and remarkable beneficial effects by innovating from multiple aspects of rule data standardization, visual editing, dynamic analysis and execution, version management, context awareness matching and the like.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As shown in fig. 1, an embodiment of the present invention proposes a low code rule engine method supporting dynamic service adjustment, the method comprising:
S100, acquiring original rule data, wherein the original rule data comprises a plurality of condition items and corresponding action items for business judgment, and an initial rule pair is formed between each condition item and each action item;
s200, carrying out structural transformation on the original rule data, and unifying format specifications to obtain structural rule data;
S300, generating a visual rule assembly according to the structural rule data, presenting rule logic through a graphical interface, supporting business personnel to edit and modify under the condition of no need of coding, and converting a modification result into assembly rule data;
S400, analyzing and checking the component rule data in real time to obtain operation rule data, wherein the operation rule data is adaptive to a dynamic rule loading interface in an operation environment;
s500, carrying out version identification on the operation rule data, and storing the operation rule data into a rule warehouse, wherein the rule warehouse is used for maintaining a rule history version and a change record and supporting rollback and reloading of any version;
and S600, automatically selecting the operation rule data based on the current business context matching applicable version, and loading the operation rule data into a rule execution engine for execution.
In the embodiment of the invention, the structural rule data is obtained by acquiring the original rule data, carrying out structural conversion on the original rule data and unifying format specifications, so that service logic descriptions with different sources and different formats can be effectively unified. The visual rule component is further generated through the standardized structural rule data, and the service logic is visually presented through the graphical interface, so that service personnel can directly edit and adjust the rule under the condition of no need of coding. After editing is completed, the modified content can be converted into new component rule data in real time, so that the threshold of manually modifying codes by a developer in the prior art is effectively reduced, and the rule adjustment efficiency and accuracy are improved.
And then, analyzing and checking the component rule data in real time to generate operation rule data. By adapting the dynamic rule loading interface in the operation environment in the operation rule data, the new rule can be ensured to be directly applied under the condition that the existing stable operation is not influenced, and the service interruption risk caused by rule adjustment is avoided. By carrying out version identification on the operation rule data and storing the operation rule data into a rule warehouse, the history information of each version rule can be completely reserved, and rollback and reloading of subsequent versions are supported, so that the flexibility and traceability of rule management are improved.
In the specific business operation process, the applicable rule version can be dynamically matched based on the current business context. By extracting service identification information and environment attribute parameters, the operation rule data version conforming to the current condition is accurately screened, and the screened version is rapidly loaded into a rule execution engine for execution, so that the accuracy of rule adaptation under different service scenes is ensured. The whole process supports dynamic loading and takes effect quickly, can respond to policy change, market adjustment or personalized requirements in time under the high-frequency changing service environment, and greatly enhances the adaptability to external changes and the stable operation capability.
Through the processing, the technical problems that in the prior art, rule adjustment depends on developers, adjustment period is long, and shutdown is required to be updated due to incapability of dynamic loading can be effectively solved, standardized modeling, visual editing, dynamic loading and version management of rule logic under a low-code environment are realized, the method has the advantages of being outstanding in substantial characteristics and remarkable in beneficial effects, and the method is suitable for various industrial application scenes needing quick and flexible response to service changes, such as the fields of insurance claim auditing, financial wind control approval, supply chain flow management and the like.
The method comprises the steps of acquiring original rule data, namely extracting rule content for judging the service through the existing service flow definition, rule configuration file or database table in enterprise information, and specifically comprises the step of reading condition item and action item information related to a specific service scene from a stored service rule configuration table. Each condition item is used for describing a judgment criterion that needs to be satisfied in a specific situation, for example, whether the payable amount is smaller than a set threshold value, and whether the reason for the risk is in the category of quick claims. Each action item is used to describe a processing action that should be taken when the condition item is satisfied, such as triggering a quick claims process, initiating a manual audit instruction, and so forth.
In the extraction process, the original rule is matched with the corresponding action item according to the corresponding relation between the condition item and the action item, namely, each condition item is matched with the corresponding action item, and an initial rule pair is formed. These initial rule pairs preserve the original existing logical structure and serve as input data sources in subsequent processing. By the method, the existing decision rules in the business process can be comprehensively collected, damage to the original logic is avoided, and the integrity and accuracy of the original rule data acquisition are ensured.
In a preferred embodiment of the present invention, the method for performing structural transformation on the original rule data and unifying format specifications to obtain structural rule data includes:
extracting field information from each condition item in the original rule data, and carrying out standardized processing based on field types to form a standard condition field set;
Extracting execution parameters from each action item in the original rule data, and carrying out unified processing based on a parameter format to form a standard action parameter set;
And constructing structural rule data according to the standard condition field set and the standard action parameter set.
In the embodiment of the invention, the original rule data is subjected to structural transformation, the format specification is unified, and in the process of obtaining the structural rule data, the rule condition definitions from different service modules or different data sources can be effectively unified by extracting the field information from each condition item in the original rule data and carrying out standardized processing based on the field type. The method comprises the steps of extracting field names, field types and field constraint information to form a preliminary field set, carrying out unified processing on the preliminary field set according to a preset field standardization rule, and carrying out standardized mapping on fields with the same logic meaning but different expression forms to form a standard condition field set with good consistency.
Similarly, by extracting the execution parameters of each action item in the original rule data and carrying out unified processing based on the parameter format, the action items can be ensured to be analyzed and executed according to a unified parameter template during subsequent processing, and rule logic errors caused by parameter definition differences are avoided. And through the combination of the standard condition field set and the standard action parameter set, unified and normative structural rule data is constructed, so that the consistency and accuracy of basic data of a visual rule component generated subsequently are ensured.
The process not only improves the compatibility and expansibility of the rule data, but also effectively reduces the ambiguity risk in the data processing process, ensures the consistency and standardization of rule logic modeling, lays a solid data foundation for subsequent visual editing, dynamic analysis and execution, and greatly enhances the stability and flexible adaptability.
The method comprises the steps of extracting execution parameters from each action item in original rule data, carrying out unified processing based on a parameter format to form a standard action parameter set, wherein each action item is generally defined by a group of parameters in the original rule data, and the parameters describe specific requirements of action execution, such as notification types, approval nodes, time-limited completion time and the like. For each action item, firstly, analyzing the parameter fields of the action item, including attribute information such as parameter names, data types, default value ranges, whether the action item is a necessary item or not, and the like.
And after the extraction is finished, carrying out format unification processing on the parameter data. Specifically, for the parameters of the text type, standard character coding is adopted uniformly, invalid characters are cleaned, for the parameters of the numerical value type, the parameters are processed uniformly into a floating point number format, unit standardization is carried out, for example, an amount field is unified into a human civil unit, for the parameters of the Boolean type, standard value representation of true or false is adopted uniformly, and for the parameters of the date and time type, international standard time format is adopted uniformly for expression. After the normalization processing, the execution parameters of all the action items are organized and stored according to the unified data specification to form a standard action parameter set.
The standard action parameter set not only eliminates the compatibility problem caused by format difference among different action definitions, but also lays a data foundation for the subsequent generation of a visual component and automatic analysis of rule logic, and ensures the accuracy and consistency of action items in execution.
The method specifically comprises the steps of building structural rule objects according to the corresponding relation between each condition item and each action item in original rule data after the standard condition field set and the standard action parameter set are generated. Each structure rule object at least comprises two parts of contents, namely, a corresponding conditional logic expression in a standard condition field set, namely, a value range of each field, a comparison relation and a combination logic relation, and a corresponding action execution parameter configuration in a standard action parameter set, namely, parameter setting and execution mode description required by action execution.
In the process of establishing the structural rule data, standardized binding needs to be carried out on the association relationship between the condition logic and the action parameters. For example, if certain conditional logic determines that the payoff amount is less than five thousand yuan and the reason for the risk is of the accident type, the corresponding action parameters should be configured to initiate a fast claim settlement process and complete the audit within a specified time. The binding process ensures the consistency of the internal conditions and actions of each piece of structural rule data, and avoids execution logic errors caused by condition and action mismatch.
And finally, storing and managing all the formed structural rule objects according to a unified data format to form a complete structural rule data set. The set is used as a direct data source generated by a subsequent visual rule component, and provides a standard, stable and extensible data base for graphic rule configuration, rule real-time adjustment and dynamic execution in a low-code environment.
In a preferred embodiment of the present invention, a visual rule component is generated according to structural rule data, rule logic is presented through a graphical interface, and service personnel are supported to edit and modify the structural rule component without coding, and a modification result is converted into component rule data, including:
Generating a condition node assembly according to a standard condition field set in the structural rule data, wherein the condition node assembly displays condition attributes in the form of editable fields;
Generating an action node assembly according to a standard action parameter set in the structure rule data, wherein the action node assembly displays action contents in a parameter configuration form;
and combining the condition node component and the action node component through a logic connection line to form a rule link diagram, and extracting updating contents of the rule link diagram after a user edits and adjusts the rule link diagram in a graphical interface to generate corresponding component rule data.
In the embodiment of the invention, the visual rule assembly is generated according to the structural rule data, and rule logic is presented through the graphical interface, so that service personnel can edit and modify the structural rule assembly under the condition of no need of coding, and the modification result is converted into assembly rule data. By generating condition node components according to a standard condition field set in the structural rule data, each condition node component presents condition attributes in the form of editable fields, so that service personnel can intuitively understand and configure condition logic. Meanwhile, the action node assembly is generated according to the standard action parameter set, and the action content is displayed in the form of a parameter configuration form, so that the operation complexity is further reduced, and the configuration accuracy is improved.
When the rule logic link is constructed, the condition node assembly and the action node assembly are logically connected and combined to form a rule link diagram, so that complex rule relations are displayed in a graphical mode, and service personnel can understand, edit and adjust the service flow in a visual interface conveniently. Through adjustment and editing of rule links in the graphical interface, updated content can be extracted in real time, new component rule data is generated, and service logic adjustment can be ensured to be fed back to an execution layer rapidly.
Through the process, the technical threshold for rule logic adjustment based on the traditional coding mode is effectively reduced, the rule on-line period is shortened, and the flexibility and maintainability of rule management are improved. Meanwhile, the patterned rule configuration mode greatly reduces error rate in the rule modeling and adjusting process, improves the intelligent level and response speed of the overall business process management, and has good application prospect and popularization value.
The method comprises the steps of reading information of each standard field in the standard condition field set, extracting a field name, a field type, a field value range and a field constraint condition. Based on the extracted information, a corresponding condition node component is instantiated for each standard field, wherein the condition node component comprises a field display area and a field editing area.
The field display area is used for visually presenting basic attribute information of the field, such as a field name and a brief description thereof, so that service personnel can understand the service meaning of the field conveniently. The field edit field allows the user to edit specific judgment conditions such as setting comparison symbols (e.g., greater than, less than, equal to) of field values, setting desired values or desired value ranges, and configuring logical relationships (e.g., and/or) between fields based on field types. For the numeric type field, a numeric input box and a comparator selector are provided, for the string type field, a text match or inclusion decision option is provided, and for the date and time type field, a date selector and a time interval editor are provided.
By generating the condition node assembly, the standard condition field set can be embodied as an editable logic judging unit in the graphical interface, so that service personnel can conveniently configure and adjust rule condition logic in an intuitive and code-free mode, and the flexibility and accuracy of rule modeling are improved.
Generating an action node component according to a standard action parameter set in the structure rule data, wherein the action node component displays action content in a parameter configuration form, and specifically comprises traversing each action parameter item in the standard action parameter set, and instantiating the action node component according to action types and parameter definitions. The action node component mainly comprises an action name display area and a parameter configuration form area.
The action name display area is used for definitely identifying the action represented by the node, such as triggering payment, sending reminding, modifying state and the like, so that the service personnel can conveniently and quickly understand the function of the node. The parameter configuration form field generates corresponding form input controls, such as text boxes, drop-down selectors, date selectors, or boolean value switches, based on different types of action parameters. The form control of each parameter item sets a default value, a check rule and a filling prompt according to a preset rule, so that a user can follow the data integrity requirement when configuring the action parameters.
After the user fills in the parameter form of the action node in the graphic interface, the value of each parameter is recorded in real time and used for generating the component rule data subsequently. Through the generation of the action node assembly, the standard action parameter set can be clearly and structurally displayed in the graphical interface, so that service personnel can intuitively and normally configure action execution logic, and the accuracy and reliability of a rule execution stage are further ensured.
In a preferred embodiment of the present invention, real-time parsing and checking are performed on component rule data to obtain operation rule data, where the operation rule data is adapted to a dynamic rule loading interface in an operation environment, and the method includes:
Analyzing node attributes and connection relations in the component rule data, and reconstructing a rule expression set conforming to the execution engine standard;
Carrying out validity check on the rule expression set, and if conflict or deletion exists, returning an error prompt and preventing the generation of operation rule data;
And packing the rule expression set passing through the validity verification to generate operation rule data, wherein a rule version identifier is added in the operation rule data.
In the embodiment of the invention, the component rule data is analyzed and checked in real time to obtain the operation rule data, and in the process of adapting the operation rule data to the dynamic rule loading interface in the operation environment, the node attribute and the connection relation in the component rule data are analyzed at first, so that the rule expression set conforming to the standard of the execution engine can be accurately reconstructed. Through the analysis step, consistency and correctness of rule logic can be ensured when the rule logic is converted from the graphic interface expression to the execution engine language, and rule failure or logic error caused by expression difference is avoided.
After the regular expression set is generated, validity verification is further performed on the set. By timely finding conflict or missing problems in rule definition in a verification stage and returning error prompts and preventing generation of operation rule data when the problems are found, the logic error rules can be effectively prevented from being deployed to an execution engine, and the stability and reliability of overall operation are improved. Only the rule expression set passing through all the validity checks can be packed and final operation rule data can be generated, and the rule version identification is added in the generation process, so that the follow-up rule version management and dynamic loading operation can be dependable.
Through the processing flow, seamless connection from graphic editing to standard format execution of rule logic can be realized, an automatic verification mechanism is introduced in the process, and the accuracy and the safety of rule online are greatly improved. Particularly, under the dynamic service adjustment scene, the process ensures that the rule adjustment can take effect in real time without damaging the normal operation of the existing service, and obviously improves the quick response capability to the service change and the operation continuity.
The method specifically comprises the steps of reading each node object in the component rule data, extracting node type, node field information and configuration parameters, and simultaneously reading connection relation information among the nodes. Extracting field editing contents of the conditional nodes, wherein the field editing contents comprise comparison logic, value intervals and association logic; and extracting specific execution parameters recorded in the parameter configuration form of the action node.
After analyzing the attribute information of the single node, deducing a trigger path from the conditional node to the action node according to the connection relation between the nodes, and organizing a logic expression according to the path sequence. Specifically, each logic path is formed by combining judgment logic of a condition node and an execution instruction of an action node. The expression sequence of the logic paths strictly follows the node connection direction, and if a plurality of conditional node combinations exist, the priority and the combination mode of the expressions are determined according to the logic symbols (such as AND or OR) in the connection relation.
Through the analysis process, the rule expression set meeting the standard grammar requirement of the execution engine is finally reconstructed, and can be directly used for subsequent validity check and operation rule data generation, so that the logical consistency and correctness from graphical editing to execution are ensured.
The method comprises the steps of packaging a rule expression set passing through validity verification to generate operation rule data, wherein rule version identifiers are added to the operation rule data, and packaging each legal rule expression into a standard rule record according to a preset format after the rule expression set passes through the validity verification. The standard rule record contains the condition logic description of the rule, the action execution instruction and the logic association mode between the rule and the action execution instruction, and is organized according to a unified data structure to form operation rule data.
And simultaneously generating the operation rule data, automatically attaching a rule version identifier to each piece of operation rule data. Rule version identification is typically composed of a time stamp, version number, and source information for uniquely identifying the lot-generated rule data. By recording the rule version identification, the rule version management and tracing can be realized, and the subsequent version rollback, difference comparison and dynamic version switching operation can be supported.
By packaging legal rule expression sets into operation rule data and adding version identification, compatibility and accuracy of a rule execution layer facing different service versions can be ensured, and controllability and flexible adaptability of the rule data in a dynamic service environment are enhanced.
In a preferred embodiment of the present invention, the method for automatically selecting and loading the operation rule data into the rule execution engine for execution based on the matching applicable version of the current service context includes:
Receiving current service context data, and extracting service identification information and environment attribute parameters;
Searching matching conditions in a rule warehouse according to the service identification information, and screening out an operation rule data version conforming to the environment attribute parameters;
and loading the screened operation rule data version into a rule execution engine memory area, and triggering the rule engine to execute corresponding rule logic to complete service judgment.
In the embodiment of the invention, the running rule data is automatically selected based on the matching applicable version of the current service context, and is loaded into the process of executing in the rule execution engine, the current service context data is received first, and the service identification information and the environment attribute parameters are extracted. This processing step ensures that the actual characteristics of the current service request can be precisely known, providing a basis for dynamic matching of subsequent rule versions.
And then, searching the matching conditions in the rule warehouse according to the extracted service identification information, and screening out the operation rule data version meeting the requirement of the environment attribute parameters. Through the screening mechanism, the most suitable rule version can be applied under different service scenes, and service logic execution errors or anomalies caused by mismatching of the rule versions are avoided. Meanwhile, by fine granularity screening based on environment attribute parameters, more flexible and dynamic service adaptation strategies can be supported, such as application of different rule logics under different scenes of different regions, different product lines, different client types and the like.
After screening out the operating rule data version meeting the conditions, loading the version into a memory area of a rule execution engine, and triggering the rule engine to execute corresponding rule logic to realize the automatic processing of service decision. By the mechanism for dynamically selecting the rule version based on the service context, intelligent decision capability and adaptability can be greatly improved, accuracy and high efficiency of service circulation are ensured, and the mechanism is particularly suitable for service scenes with high concurrence and high change frequency, and is beneficial to improving overall stability and customer experience quality.
The method comprises the steps of receiving current service context data, extracting service identification information and environment attribute parameters, and specifically comprises the step of analyzing context information related to current service processing from the request data after receiving a request from a service. Business context data typically includes, but is not limited to, business process identification, operational user information, geographic location, request time, version number, and other environmental variables. The service identification information is extracted from the service identification information and used for representing the service type, the sub-flow identification or the specific service rule application scene of the service request, such as classification identifications of car insurance claims, health insurance claims and the like in the insurance claims. At the same time, environment attribute parameters are further extracted, and the parameters are mainly used for describing external environment characteristics, such as operation version, client class, region position, access channel and the like.
The extraction process analyzes and classifies according to a preset data extraction template or a context segment mapping table, so that all service identification information and environment attribute parameters can be output in a standardized mode and used by a subsequent rule screening module. By the processing, the context characteristic information required by rule screening can be accurately extracted in real time on the premise of not increasing the service change burden, so that the rule version suitable for dynamic matching is supported, and the accuracy and the adaptability of service rule application are ensured.
The method specifically comprises the steps of loading the screened operation rule data version into a rule execution engine memory area, triggering the rule engine to execute corresponding rule logic to complete service judgment, and loading the data of the version into a preset rule execution engine after screening the matched operation rule data version according to service identification information and environment attribute parameters. The loading process comprises the operations of initializing a rule expression set, configuring execution parameters, preheating a cache and the like, so that the rule execution environment can instantly identify and call the newly loaded rule set.
After the rule data is loaded, triggering an execution flow of the rule engine according to the current service request data, judging whether the service data accords with a specific rule by the rule engine according to conditional logic defined in the operation rule data, and executing corresponding action logic according to a judging result, such as allowing the flow to pass, sending an abnormal warning or triggering a further approval flow. The whole process is completed in real time in the service background without interrupting service or performing manual intervention, so that the application efficiency of the rule after dynamic adjustment is effectively improved.
By fast loading and immediately triggering and executing the screened rule versions, not only is the continuity of service processing ensured, but also the service requirement of high-frequency change and external policy adjustment can be flexibly dealt with, and the intelligent level and response speed of the service are obviously improved.
In a preferred embodiment of the present invention, in retrieving matching conditions in a rule repository according to service identification information, and in a process of screening a version of operation rule data conforming to an environmental attribute parameter, version screening is performed based on comprehensive suitability score, including:
according to the service context data, extracting service identification information, environment attribute parameters and history call records, and respectively calculating service matching degreeDegree of environmental matchingAnd historical stability;
According to the calculation result、AndThe comprehensive fitness Score is calculated according to the following formula:
;
Wherein, theThe comprehensive fitness score characterizes the overall fitness of the current running rule version and the business context, and the higher the score is, the more suitable the score is;
Normalizing the weight for the service matching degree weight coefficient, and determiningContribution ratio to Score;
normalizing the weights for the environmental matching degree weight coefficients, and determiningContribution ratio to Score;
normalizing weights for stability parameter weight coefficients, determiningContribution ratio to Score;
Is the firstPersonal service identification field values such as service type, product number, etc. (from the current service context);
Is the firstDefinition of corresponding fields in the rule data of the individual rule version field values;
Is thatAnd (3) withSimilarity scores between the two are in the range of 0,1 represents complete matching, and 0 represents complete mismatch;
The total number of the service identification fields is the number of the fields involved in matching;
Is the firstEnvironmental attribute field values such as geographic location, version number and other environmental parameters;
Is the firstCorresponding field definitions in the rule data of the individual rule version field values;
Is thatAnd (3) withSimilarity score between the two ranges of [0,1];
the total number of the fields participating in matching is the total number of the environmental attribute fields;
a response delay set when the rule version is called for the history call response delay sequence in the past;
the variance of T is used for measuring the stability of the calling delay, and the smaller the value is, the more stable the value is;
。
in the embodiment of the invention, the final score is obtained through the comprehensive calculation of the three indexes in the whole formula:
Service matching degreeComparing the similarity of the current service identification field and the rule version definition field, normalizing and averaging the multiple fields, and embodying the suitability of the whole service scene.
Degree of environmental matchingComparing the current environment parameter with the environment suitability defined by the rule, and normalizing and averaging the multiple fields to reflect the consistency of the external environment.
Historical stabilityThe smaller the variance, the more stable the rule execution is, the higher the score.
Finally by weight coefficient、、Weighted summation to form comprehensive fit degree. Then selectThe highest version is the final execution version.
In a preferred embodiment of the present invention, extracting field information for each condition item in the original rule data, performing normalization processing based on field types to form a standard condition field set, including:
Extracting the field name, the field type and the field constraint information of each condition item according to the original rule data to generate a preliminary field set;
based on a preset field standardization rule, carrying out field type unified processing on the preliminary field set, and mapping fields with different sources and the same logic meaning into a standard field set;
Detecting field naming conflict in a standard field set, if the naming conflict exists and the field types are consistent, carrying out naming distinction by adding a data source identifier in the field names, and if the field types are inconsistent, refusing to combine and generating conflict warning information;
And generating a standard condition field set according to the standard field set after naming adjustment, and establishing a mapping relation between the original field and the standard field.
In the embodiment of the invention, the field information is extracted from each condition item in the original rule data, the standardized processing is carried out based on the field type, and in the process of forming the standard condition field set, the service logic key information defined in the original rule data can be comprehensively captured by firstly extracting the field name, the field type and the field constraint information of each condition item. Then, based on a preset field standardization rule, the extracted preliminary field set is subjected to field type unified processing, so that fields with different sources and consistent logic meaning can be mapped into the same standard field, and the problem of inconsistent fields caused by heterogeneous data sources is solved.
After the standardization processing, further carrying out field naming conflict detection in a standard field set, and if naming conflicts exist and the field types are consistent, carrying out naming distinction by adding a data source identifier in the field names, so as to ensure that the field directions are clear in the subsequent processing process, and avoid logic confusion caused by naming repetition. If the field types are inconsistent, combination is refused and conflict warning information is generated, so that the consistency and reliability of the data in the rule modeling process are ensured. And finally, generating a standard condition field set according to the standard field set after naming adjustment, and establishing a mapping relation between the original field and the standard field, so that the traceability of the original data is reserved, and the high consistency and standardization of the subsequent processing process are ensured.
Through the standardized processing flow, definition and compatibility of rule data are improved, a solid foundation is laid for subsequent rule component generation, graphical editing and dynamic analysis, capability of complex business rule management is remarkably improved, adaptability to variable business demands is flexibly met, and the method has a good application and popularization prospect.
The method comprises the steps of carrying out field type unified processing on a preliminary field set based on a preset field standardization rule, and mapping fields with different sources and the same logic meaning into a standard field set. The field standardization rules include a field name standardization rule, a field type standardization rule, and a field unit standardization rule.
In the field name standardization, fields with the same logical meaning but different names are unified into standard field names by keyword matching and business dictionary comparison and peer-to-peer modes, for example, different names such as 'compensation amount', 'claim amount', and the like are unified into the standard field 'claim amount'. In the field type standardization aspect, if the original data types of the fields from different sources are different, for example, one field stores the amount of money in a character string form, and the other field stores the amount of money in a floating point number form, the fields are uniformly converted into a standard numerical format. For fields with physical quantity unit difference, if the length field is represented by two units of 'meters' and 'centimeters', conversion is performed according to a unified unit, so that consistency and comparability of field values are ensured.
Through the standardization processing, the fields with different sources, different formats and consistent logic are uniformly mapped into the standard field set, so that data ambiguity is eliminated in the subsequent rule generation and execution process, and the accuracy and reliability of rule application are improved.
Detecting field naming conflict in a standard field set, if naming conflict exists and field types are consistent, naming and distinguishing are carried out by adding a data source identifier into field names, and if the field types are inconsistent, merging is refused and conflict warning information is generated. If two or more fields are detected to have the same name and the field types are consistent, for example, the two fields are both floating point type and the name is "pay amount", a source identifier is added on the basis of the original field name, for example, a suffix of "_source A" or "_source B" is added behind the fields, naming and distinguishing are carried out, and therefore each field can be accurately identified in subsequent processing.
If the condition that the names are the same but the field types are not consistent is detected, for example, one of the fields with the same name is numerical value and the other is text, the conflict cannot be resolved through simple naming distinction, so that the fields are refused to be combined, and conflict warning information is generated. The conflict warning information comprises the name of the conflict field, the respective data type of the conflict field and the conflict source, so that service personnel or an administrator can manually decide the processing mode according to the actual requirement.
Through the naming conflict detection and processing mechanism, the internal consistency and the resolvable performance of the standard field set are ensured, and rule logic execution errors caused by field naming ambiguity or type confusion are prevented, so that the stability and the correctness of the overall operation of the rule engine are improved.
In a preferred embodiment of the present invention, a rule link diagram is formed by combining a condition node component and an action node component through a logic connection, and after a user edits and adjusts the rule link diagram in a graphical interface, the user extracts update content to generate corresponding component rule data, including:
generating a condition node set according to the standard condition field set, and setting a field editable attribute and a logic expression editing inlet in each condition node;
generating an action node set according to the standard action parameter set, and setting a parameter verification template and an execution configuration entry in each action node;
Establishing a connection relation between the conditional node set and the action node set based on a preset connection rule, only allowing node combinations conforming to service logic constraint, detecting whether the connection is legal or not in real time, prompting an error and prohibiting node connection storage if the connection violates the predefined constraint;
after the rule link diagram editing is completed, the node information and the connection relation which are changed are extracted, incremental update data are generated and fused into the component rule data, and updated component rule data are formed.
In the embodiment of the invention, the condition node components and the action node components are combined through the logic connection lines to form the rule link diagram, and after the rule link diagram is edited and regulated in the graphical interface by a user, in the process of extracting the updating content of the rule link diagram to generate corresponding component rule data, the condition node set is firstly generated according to the standard condition field set, and the field editable attribute and the logic expression editing inlet are arranged in each condition node, so that service personnel can conveniently perform personalized configuration on the condition logic in the graphical interface. Meanwhile, an action node set is generated according to the standard action parameter set, and a parameter verification template and an execution configuration entry are arranged in each action node, so that standardization and accuracy of action configuration are guaranteed.
After the node generation is completed, the connection relation is established between the conditional node set and the action node set based on the preset connection rule, so that unreasonable node combination is effectively limited, only the node connection conforming to the service logic constraint is allowed, and the occurrence of potential logic errors is avoided. Meanwhile, whether the connection is legal or not is detected in real time in the connection operation process, if the connection violates the predefined constraint, errors are immediately prompted, and node connection storage is forbidden, so that introduction of invalid logic is prevented in an editing stage, and the overall quality and stability of rule link data are improved.
After the regular link diagram editing is completed, the node information and the connection relation which are changed can be extracted in real time, incremental update data are generated, full data reconstruction is avoided, and processing efficiency is improved. By fusing the increment updating data into the component rule data to form updated component rule data, the high efficiency and reliability of the rule adjusting process can be ensured, the service logic modification can be synchronized to the subsequent analysis and execution stage in time, and the flexibility, the controllability and the running stability of rule maintenance are obviously improved.
The method comprises the steps of establishing a connection relation between a conditional node set and an action node set based on a preset connection rule, only allowing node combinations conforming to service logic constraint, detecting whether the connection is legal or not in real time, prompting errors and prohibiting node connection storage if the connection violates the predefined constraint, and specifically comprises the steps of controlling logic according to the predefined connection rule after the conditional node set and the action node set are generated, and allowing a user to perform inter-node connection operation in an interface. The preset connection rule includes, but is not limited to, that a condition node can only be connected to an action node, that an action node cannot be an upstream node of the condition node, that the same condition node can be connected to a plurality of action nodes, but that an action node cannot be connected to a plurality of condition nodes as direct upstream, unless a composite condition logic module is configured.
When a user initiates a connection request, whether the connection meets the rule constraint is judged in real time. If the connection violates the rule, for example, the condition node is connected to another condition node, or the action node is connected back to itself, the error prompt information is popped up on the interface immediately, and the connection operation is refused to be saved, thereby preventing the formation of logic error or invalid flow path. Through the process, the correctness of the service logic of the node combination can be ensured in the rule link construction stage, and the risk of abnormal execution of the follow-up rules is reduced.
After the user completes node adding and deleting, attribute modifying or connecting line adjusting operation of the regular link diagram in a graphic interface, node data and connecting line data which are changed compared with the original link state are extracted based on an operation log or a difference comparison mechanism.
The change of the node data comprises modification of the node attribute, such as condition field change and action parameter update, and the change of the connection data comprises new connection relation or deletion of the original connection relation. The change parts are independently arranged to form incremental update data, so that the performance cost caused by full data reconstruction is avoided. And then, carrying out fusion updating on the incremental updating data and the existing component rule data, and updating only the changed nodes or wires to keep the data stability and continuity of the unchanged parts.
By adopting the incremental updating mode, the response speed of rule editing and saving can be effectively improved, the data processing load is reduced, meanwhile, the user editing and modifying content can be accurately synchronized into component rule data, and an accurate rule basis is provided for subsequent rule analysis and execution.
In a preferred embodiment of the present invention, the validity check on the regular expression set includes:
Extracting a rule expression set according to the updated component rule data, and establishing a reference index table according to the expression reference relation;
According to the reference index table, carrying out field validity check on each rule expression, and if the field is found to be not in the standard condition field set, recording field reference errors and positioning to a specific node;
Performing integrity check on the execution parameters of the action nodes in the rule expression, and if the necessary filling parameters are absent, recording the missing errors of the parameters and marking the missing errors to a parameter configuration interface;
Connectivity and logic rationality analysis are carried out on the connection relation of the regular link diagram, and if cyclic reference, isolated nodes or broken links exist, abnormal structure errors are recorded;
and generating a verification comprehensive report of the hierarchical prompt according to all the field reference errors, the parameter missing errors and the structure exception errors, and indicating error nodes and error types in a highlighting mode.
In the embodiment of the invention, in the process of verifying the validity of the regular expression set, the regular expression set is firstly extracted according to the updated component rule data, and a reference index table is established according to the expression reference relation. By establishing the reference index table, the fields and the action parameters related to each expression can be accurately recorded, and the clear association foundation of the subsequent verification operation is ensured. And aiming at each extracted regular expression, checking the field validity, and if the reference field is found not to exist in the standard condition field set, timely recording the field reference error and positioning to a specific node, thereby being beneficial to quickly finding and correcting the reference omission or error.
And carrying out integrity check on the execution parameters of the action nodes in the rule expression, if the necessary filling parameters are absent, automatically recording the parameter missing errors, marking the parameter missing errors to a parameter configuration interface, and reminding business personnel to timely supplement missing information so as to avoid rule execution abnormality caused by parameter missing. In the aspect of structural logic, connectivity and logic rationality analysis are carried out on the connection relation of the rule link diagram, so that structural anomalies such as cyclic reference, isolated nodes or broken links can be detected, structural anomaly errors can be recorded in time, and unexpected flow interruption or dead cycle risks in the rule execution process are prevented.
And finally, generating a verification comprehensive report of the hierarchical prompt according to all field reference errors, parameter missing errors and structure exception errors, and indicating error nodes and error types in a highlighting mode, so that service personnel can intuitively know the source and severity of the problem. Through the fine-entry micro-legitimacy verification process, the accuracy, the robustness and the execution reliability of rule data are greatly improved, the probability of logic loopholes or abnormal business after the rule is online is greatly reduced, and the whole stability and the business continuity guarantee capability are remarkably improved.
And if the fields are found not to exist in the standard condition field set, recording the field reference error and positioning to a specific node, wherein the specific method comprises the steps of establishing a reference index relation between the rule expression and the condition field after analyzing the component rule data and reconstructing the rule expression set, and recording the field name and the corresponding node referenced by each rule expression.
When the field validity check is performed, the field names related in the rule expression are traversed one by one, and whether the standard condition field set has corresponding definitions or not is queried. If a field is found to be not registered in the standard condition field set, indicating that the field is illegally referenced, recording the error in an error list, and marking the position of a specific condition node or action node referencing the field so as to facilitate the subsequent service personnel to locate the problem.
By the verification, the problem of illegal field reference caused by field omission, spelling errors or version inconsistency can be timely found, so that logic abnormality or execution failure is prevented before regular formal operation, and overall reliability is improved.
The method comprises the steps of carrying out integrity check on the execution parameters of action nodes in the rule expression, recording the missing errors of the parameters and marking the missing errors to a parameter configuration interface if the necessary parameters are absent, and specifically comprises the step of carrying out check on each action node according to a parameter configuration template defined in an action node component after extracting a rule expression set. The verification process includes checking whether each fill-in parameter has been properly filled or configured, and whether it meets the data type and value range requirements.
If the condition that the necessary parameters are not filled in and are filled in as null or format errors exist in the action nodes is detected, the errors are recorded in an error list, and the parameter items with the defects or the errors are marked obviously in a parameter configuration area of the graphical interface in a highlighting mode, a prompting bubble mode and the like, so that service personnel can find and correct the parameter items in time.
Through the integrity verification of the execution parameters of the action nodes, the action execution failure or abnormality caused by parameter deletion or configuration error can be effectively avoided, and the stability and fault tolerance of the rule execution process are greatly improved.
If the condition of cyclic reference, isolated node or broken link exists, the abnormal structure error is recorded, and the method specifically comprises the steps of detecting the connection relation of the whole node through a connectivity analysis algorithm after the construction of the regular link diagram is completed. The detection content comprises the steps of judging whether an isolated node which can not reach an action node from a starting node exists, judging whether a circulating reference path for connecting the node or forming a closed loop exists or not, and judging whether a broken link condition that part of logic links can not be executed in a closed loop due to broken links exists or not.
When the abnormal structure situation is detected, immediately recording related abnormality to an abnormal structure error list, and intuitively displaying abnormal nodes or abnormal path positions in the modes of interface highlighting, connection warning identification and the like. Business personnel can adjust node connection or correct logic structure according to the prompt, so as to ensure that the regular link meets the requirement of correct execution flow.
By detecting and feeding back the structural integrity and logic rationality of the rule link diagram in real time, the risk of service processing failure caused by logic design defects is greatly reduced, and the robustness and maintainability of the whole rule are improved.
In a preferred embodiment of the present invention, generating a verification comprehensive report with hierarchical hints according to all field reference errors, parameter missing errors and structure exception errors, and indicating error nodes and error types in a highlighting manner includes:
extracting corresponding error node information according to the field reference errors, and listing the corresponding error node information in a verification comprehensive report in the form of node numbers and field names;
Extracting a missing parameter list of the action node according to the parameter missing error, and marking the missing of the necessary filling item and the position of the corresponding action node in the verification comprehensive report;
according to the structural anomaly errors, analyzing and forming an error connection relation graph, marking node path information with circulation, isolation or chain breakage, and drawing an anomaly link schematic in a verification comprehensive report;
classifying and summarizing the field reference errors, the parameter deletion errors and the structure abnormality errors respectively, giving priority identification, and displaying various error information according to the priority highlighting;
and setting an interactive jump function in the verification comprehensive report, and supporting the user to click the error item to be directly positioned to the corresponding node position in the graphical interface.
In the embodiment of the invention, a verification comprehensive report with a grading prompt is generated according to all field reference errors, parameter missing errors and structure exception errors, and in the process of indicating error nodes and error types in a highlighting mode, corresponding error node information is firstly extracted according to the field reference errors, and is accurately listed in the verification comprehensive report in the form of node numbers and field names, so that service personnel can clearly know the source and specific positions of each error. Meanwhile, a missing parameter list of the action node is extracted according to the parameter missing error, and the necessary filling item missing and the corresponding action node position are marked in the verification comprehensive report, so that a user is helped to quickly locate and supplement necessary parameters.
In the aspect of structural anomaly errors, an error connection relation diagram is formed through analysis, node path information with circulation, isolation or chain breakage is marked, and abnormal link schematic is further drawn in a verification comprehensive report, so that the problem of the whole rule structure can be displayed in a visual mode, and service personnel can conveniently and rapidly understand and correct logic defects. In order to promote availability and emergency management of the verification report, field reference errors, parameter deletion errors and structure abnormality errors are respectively classified and summarized, priority identification is given, and therefore business personnel can reasonably arrange repairing sequences according to the problem severity, and debugging efficiency is optimized.
And setting an interactive jump function in the verification comprehensive report, and supporting a user to click an error item to be directly positioned to a corresponding node position in the graphical interface, so that the time cost of manual searching and checking is obviously reduced, and the rule adjustment and correction efficiency is improved. Through the mechanism, the invention not only greatly improves the speed of error discovery and positioning, but also effectively reduces the maintenance difficulty caused by the increase of rule complexity, improves the overall experience of rule configuration and management, and further strengthens the usability and intelligence level under high-complexity service scenes.
Analyzing and forming an error connection relation graph according to the structural anomaly errors, marking node path information with circulation, isolation or broken links, and drawing an anomaly link schematic in a verification comprehensive report.
The method comprises the steps of detecting a cyclic reference error, recording a node set and a connecting path which lead to loop formation, marking a loop structure in an error connecting relation diagram by a closed loop path, highlighting nodes and connections which lead to loop, identifying a condition node or an action node which is not effectively connected with any action node or an initial node for the isolated node error, highlighting the isolated node in the connecting relation diagram, marking the unconnected state of the isolated node, analyzing the node and the connecting breaking point with breaking positions in a link for the broken link error, drawing a breaking mark in the connecting relation diagram, and clearly indicating the specific position where the link cannot be closed.
The error connection relation diagram is used as an abnormal link diagram to be embedded into a verification comprehensive report, so that service personnel can intuitively understand the specific position, error type and association node relation of structural abnormality when viewing the report, and subsequent quick correction and reconstruction of a correct regular link structure are facilitated. By drawing the abnormal link schematic, the labor cost for checking the logic errors of the complex rules is effectively reduced, and the maintainability and the debugging efficiency of the rule modeling are improved.
The method comprises the steps of classifying and summarizing field reference errors, parameter missing errors and structure abnormal errors respectively, giving priority identification, and displaying various error information according to the priority highlight. The field reference error mainly comprises a reference undefined field or a field reference spelling error, the parameter missing error mainly comprises that the necessary parameters in the action nodes are not configured or the configuration content is invalid, and the structure abnormal error mainly comprises a circular reference, an isolated node or a broken chain structure problem.
On the basis of classification, a predefined priority identification is given to each type of error. The priority definition follows the risk assessment principle, e.g. a structural anomaly error is given the highest priority as it may cause the whole rule link to be non-executable, a parameter missing error gives a medium-high priority as it affects the action node to execute correctly, a field reference error gives a medium priority as it may cause a judgment logic deviation.
In the verification comprehensive report, different highlighting modes are adopted according to the priority of each error, such as different colors, font thickening, frame flickering and other modes are adopted to distinguish the severity, so that service personnel are led to preferentially treat the problem with larger influence on stability. The error items with high priority are ranked at the front in the verification report, so that the error items can be paid attention to and repaired preferentially before rule adjustment and release, and the overall rule quality and the online success rate are improved.
Through the classification, prioritization and highlighting mechanism, the rule auditing work can be more standardized, and the business personnel can be helped to efficiently identify and preferentially correct key errors when facing complex rules, so that the stable operation and business continuity of a rule engine are effectively ensured.
The embodiment of the invention also provides a low-code rule engine platform supporting dynamic business adjustment, which comprises:
the system comprises an original data acquisition module, a rule processing module and a rule processing module, wherein the original data acquisition module is used for acquiring original rule data, the original rule data comprises a plurality of condition items and corresponding action items for business judgment, and an initial rule pair is formed between each condition item and each action item;
the original data processing module is used for carrying out structural transformation on the original rule data and unifying format specifications to obtain structural rule data;
The rule component generating module is used for generating a visual rule component according to the structural rule data, presenting rule logic through a graphical interface, supporting business personnel to edit and modify under the condition of no need of coding, and converting a modification result into component rule data;
The rule analysis and verification module is used for analyzing and verifying the component rule data in real time to obtain operation rule data, and the operation rule data is adapted to a dynamic rule loading interface in an operation environment;
the version management module is used for carrying out version identification on the operation rule data and storing the operation rule data into a rule warehouse, wherein the rule warehouse is used for maintaining rule history version and change record and supporting rollback and reload of any version;
And the rule scheduling module is used for automatically selecting the operation rule data based on the matching application version of the current service context and loading the operation rule data into the rule execution engine for execution.
It should be noted that, the system is a system corresponding to the above method, and all implementation manners in the above method embodiment are applicable to the embodiment, so that the same technical effects can be achieved.
Embodiments of the present invention also provide a computing device comprising a processor, a memory storing a computer program which, when executed by the processor, performs a method as described above. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effect can be achieved.
Embodiments of the present invention also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform a method as described above. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effect can be achieved.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.