WO2024087909A1 - Attribute linkage rule-based page data processing method, and medium - Google Patents

Abstract

An attribute linkage rule-based page data processing method, and a medium. The method comprises: detecting a user assignment operation on a master attribute, determining whether the master attribute has an executable attribute linkage rule, and if yes, acquiring a data change condition of the master attribute; acquiring a corresponding slave attribute list according to the master attribute and the data change condition thereof, determining an action type of a slave attribute according to the attribute linkage rule, and determining a data processing rule of the slave attribute according to the action type; and substituting the data processing rule of the slave attribute into a render API method for page data rendering. According to the method, an interface data relation and a data processing mode are encapsulated by setting an attribute linkage rule, thereby achieving unified management of page data rules, reducing the complexity of the page code logic, and reducing the number of pages; and page data is automatically processed on the basis of a data processing method defined by the attribute linkage rule, thereby solving the page data processing flexibility problem.

Description

A page data processing method and medium based on attribute linkage rules Technical Field

The present invention belongs to the technical field of rule engine application, and in particular relates to a page data processing method and medium based on attribute linkage rules.

Background technique

With the development of business and technology, front-end functions are becoming more and more complex, and the technology stack is becoming richer and richer. Front-end development is no longer scattered throughout the entire system architecture as in the past, but tends to be an engineering, modular and systematic development method. In the existing technology, user needs are usually abstracted into metadata information such as objects, attributes, dictionaries, etc., and the flexible display of the user interface is achieved through metadata configuration. However, this method has the following defects: when the user needs to process the values of multiple attributes on the interface or execute a piece of operation logic, the corresponding code needs to be customized for development, and even some additional pages need to be made to adapt to user needs, which leads to complex code logic, a large number of pages and cumbersome data processing.

Summary of the invention

The purpose of the present invention is to provide a page data processing method and medium based on attribute linkage rules, so as to solve the problems of complex code logic, large number of pages and cumbersome data processing in the front-end page development in the prior art.

In order to achieve the above object, the present invention adopts the following technical solutions:

A first aspect provides a page data processing method based on attribute linkage rules, comprising:

Detect the user's assignment operation on the main attribute, and determine whether the main attribute has an executable attribute linkage rule. If so, obtain the data change of the main attribute;

Obtain the corresponding subordinate attribute list according to the main attribute and its data change, determine the action type of the subordinate attribute according to the attribute linkage rule, and determine the data processing rule of the subordinate attribute according to the action type, wherein the action type includes value linkage;

Match the rendering API according to the action type, substitute the data processing rules from the attributes into the rendering API method to render the page data, and display the data rendering results in the user interface.

In a possible design, the action type of the subordinate attribute is determined according to the attribute linkage rule, and the data processing rule of the subordinate attribute is determined according to the action type, including:

According to the dictionary value of the attribute action type in the attribute linkage rule table, determine the action type corresponding to the dictionary value;

If the action type is value linkage, the mapping relationship between the value range of the primary attribute and the value range of the secondary attribute is obtained, so as to substitute the mapping relationship into the rendering API method to render the page data;

If the action type is non-value linkage, the calculation rules defined in the calculation logic of the slave attribute are obtained so that the calculation rules are substituted into the rendering API method to render the page data.

In a possible design, before detecting the user's assignment operation on the primary attribute, the method further includes:

Create a form instance to enter page initialization, and obtain the initialization message of the dynamic component through the basic form information. The basic form information includes the form type and form template path, and the initialization message includes the basic form attributes and attribute linkage rule table;

Rendering a basic page according to the basic attributes of the form, using the attribute linkage rule table as a global variable of the form, and setting a linkage function corresponding to each linkage rule;

Set a listening event in each subcomponent of the form so that each subcomponent can detect the user's assignment operation on the main attribute based on the listening event.

In a possible design, a form instance is created to enter page initialization, and the initialization message of the dynamic component is obtained through the basic form information, including:

Call the created method of the VUE template to create an instance, and call the intipage method to enter the page initialization;

Request a message to the backend through the form type metaClassName and the form template type viewConfigName, so that the backend can generate an initialization message in jason format according to the message request;

Receive the initialization message returned by the backend, where the initialization message contains the form basic attributes formGroups and the attribute linkage rule table attrRules.

In a possible design, a basic page is rendered according to the basic attributes of the form, including:

Call the parseForm method to convert the basic form attributes formGroups into the basic form identification object of the Element-UI library, and render the basic page.

In a possible design, after determining whether the main attribute has an executable attribute linkage rule, the method further includes:

When the child component's listening event listens to the data change of the parent component, the assignment information is passed back to the parent component through the listening event through the callback function, so that the parent component can judge whether the current value of the main attribute meets the preset requirements.

In a possible design, whether the current value of the primary attribute meets the preset requirements is judged, including:

If the form currently needs to execute and the triggered main attribute has executable attribute linkage rules and linkage functions, then set local variables in the linkage function, and further determine whether the executable attribute linkage rule is triggered by the default value and the current value is the default value;

If the executable attribute linkage rule is triggered by the default value and the current value is the default value, the value of the local variable is considered to be true or false, otherwise the value of the local variable is considered to be undefined;

If the executable attribute linkage rule is configured with additional judgment rules, and the current value meets the additional judgment rules, the value of the local variable is considered true, otherwise it is false.

In a possible design, the data processing rules from the attributes are substituted into the rendering API method to render the page data, including:

Determine the corresponding linkage logic according to the data processing rules of the slave attributes, and call the corresponding linkage logic in the rendering API method to render the page data. The linkage logic includes value linkage logic, dictionary range value logic, text logic, attribute write-back logic and object write-back logic.

In a possible design, the value linkage logic includes changing the Boolean value of the subcomponent attribute to the value of the local variable, wherein an undefined value is converted to a true process;

The dictionary range value logic includes reading the dictionary range data of the dictionary configuration table and putting it into the global cache. If there is no dictionary list and the configuration dictionary exists, the first value of the dictionary is taken. If the dictionary list exists and the configuration dictionary data exists, the dictionary list is filtered as the configuration value. If the currently selected dictionary paper is in the filtered dictionary list, the current display value of the subordinate attribute is not changed, otherwise it is left blank.

The text logic includes terminating execution if the value of the local variable is false, otherwise executing the corresponding text operation function and placing the execution result into the display value of another specified subcomponent;

The attribute write-back logic includes: if the query pop-up window result exists, then process it according to the result data type and merge it into the form data;

The object write-back logic includes: traversing the form data, converting the matching fields according to the configuration rules and incorporating them into the pop-up query conditions.

The second aspect provides a page data processing device based on attribute linkage rules according to the first aspect, comprising:

The data change acquisition module is used to detect the user's assignment operation on the main attribute and determine whether the main attribute has an executable attribute linkage rule. If so, the data change of the main attribute is obtained;

The data processing rule determination module is used to obtain the corresponding subordinate attribute list according to the main attribute and its data change, determine the action type of the subordinate attribute according to the attribute linkage rule, and determine the data processing rule of the subordinate attribute according to the action type, wherein the action type includes value linkage;

The page data rendering module is used to match the rendering API according to the action type, substitute the data processing rules from the attributes into the rendering API method to render the page data, and display the data rendering results on the user interface.

A third aspect provides a storage medium having instructions stored thereon. When the instructions are executed on a computer, a page data processing method based on attribute linkage rules as described in any possible design of the first aspect is executed.

Compared with the prior art, the present invention has the following beneficial effects:

The present invention detects the user's assignment operation on the main attribute, and determines whether the main attribute has an executable attribute linkage rule. If so, the data change of the main attribute is obtained; the corresponding subordinate attribute list is obtained according to the main attribute and its data change, the action type of the subordinate attribute is determined according to the attribute linkage rule, and the data processing rule of the subordinate attribute is determined according to the action type, wherein the action type includes value linkage; the rendering API is matched according to the action type, and the data processing rule of the subordinate attribute is substituted into the rendering API method to render the page data, and the data rendering result is displayed in the user interface. Thus, the traditional page development mode of user interface + metadata is broken, and a new page development mode based on user interface + rule adaptation + metadata is provided. The interface data relationship and data processing method are encapsulated by pre-setting attribute linkage rules, and the unified management of page data rules is realized, the complexity of page code logic is reduced, and the number of pages is reduced; when the user's operation on the interface is detected, the page data is automatically processed based on the data processing method defined by the attribute linkage rule, and the problem of page data processing flexibility is further solved on the basis of realizing flexible display of page attributes.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of a method for processing page data based on attribute linkage rules in an embodiment of the present invention;

FIG2 is a simplified flow chart of a page data processing method based on attribute linkage rules in an embodiment of the present invention;

FIG3 is a logical diagram of an attribute linkage page in an embodiment of the present invention;

FIG4 is a schematic diagram of a basic page in an embodiment of the present invention;

FIG5 is a schematic diagram of value linkage filling in an embodiment of the present invention;

FIG6 is a schematic diagram of the value linkage effect in an embodiment of the present invention;

FIG7 is a schematic diagram of attribute operation in an embodiment of the present invention;

FIG8 is a schematic diagram of attribute operation effects in an embodiment of the present invention;

FIG9 is a schematic diagram of an assembly linkage method according to an embodiment of the present invention;

FIG10 is a schematic diagram of an assembly effect in an embodiment of the present invention;

FIG. 11 is a schematic diagram of a calculation linkage method in an embodiment of the present invention.

FIG12 is a schematic diagram of an associated control writing back to a lower level in an embodiment of the present invention;

FIG. 13 is a schematic diagram of an associated control write-back form in an embodiment of the present invention.

Detailed ways

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the present invention will be briefly introduced below in combination with the drawings and the description of the embodiments or the prior art. Obviously, the following description of the structure of the drawings is only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. It should be noted that the description of these embodiments is used to help understand the present invention, but does not constitute a limitation of the present invention.

Example

In order to solve the problems of complex code logic, large number of pages and cumbersome data processing in the front-end page development in the prior art, an embodiment of the present application provides a page data processing method based on attribute linkage rules. The method separates business decisions from application code and uses a predefined rule model to write business decisions, thereby breaking the traditional user interface + metadata page development model and providing a new page development model based on user interface + rule adaptation + metadata. The interface data relationship and data processing method are encapsulated by pre-setting attribute linkage rules to achieve unified management of page data rules, reduce the complexity of page code logic, and reduce the number of pages; when a user operation on the interface is detected, the page data is automatically processed based on the data processing method defined by the attribute linkage rule, which further solves the problem of page data processing flexibility on the basis of realizing flexible display of page attributes.

It is worth noting that before describing the page data processing method based on the attribute linkage rule, it is first necessary to describe in detail the construction process of the attribute linkage rule in the embodiment of the present application, as follows:

In order to achieve the visualization and configuration capabilities of interface data processing rules, the embodiments of the present application model interface data processing through multiple dimensions such as user data (including dictionary values, strings, numbers and foreign key references, etc.), data processing actions (including data linkage, data calculation, state changes and API calls, etc.) and data processing scope (master-slave linkage and group linkage, etc.), and at the same time introduce a rule processing module to monitor user operations on the interface based on the rules, execute the data processing method defined by the rules, and finally reflect the data processing results on the interface.

Among them, the attribute linkage rules in the embodiment of the present application refer to: usually a page is composed of multiple attributes, each attribute has specific characteristics, and needs to be described by different controls. The attribute/component linkage mainly refers to the data change mode in which when the main attribute/component (the object on which the user performs business operations) changes (value or status), the slave attribute/component or attribute group/component group changes synchronously, which has a domino-like chain effect.

In order to establish the attribute linkage rules in the embodiment of the present application, the following steps are specifically required:

Step 1: Scenario abstraction, that is, analyzing the common page data processing process from the user scenario, and finding out the manifestation of the one-way influence between the main attribute and the subordinate attribute in the data processing process. Specifically, from the application analysis of business scenarios, it can be seen that the influence relationship between the main and subordinate attributes/attribute groups is mainly divided into four categories, including:

1) Value linkage: when the primary attribute value changes, the secondary attribute value changes with the pre-configured result;

2) Rendering linkage: when the value of the main attribute changes, the rendering state of the subordinate attribute changes accordingly;

3) Calculation linkage: when the primary attribute value changes, the secondary attribute value changes with the calculation formula;

4) Rule linkage: When the primary attribute value changes, the secondary attribute value changes with the API logic.

For ease of understanding, as shown in Table 1, the embodiment of the present application shows attribute linkage rules and rule descriptions corresponding to different business scenarios.

Table 1 Description of linkage rules applicable to different business scenarios

Step 2: Group definition, further structure the result of scene abstraction, define the range of the list of subordinate attributes affected by the change of the main attribute, and conduct rule modeling for the group relationship in the abstract result based on comprehensive consideration of the combination with the metadata model and the extensibility of the rule table itself. Specifically, the methods for defining group relationships can include:

1) Setting the specification IDspec_id to adapt the metadata model and associate it with the attribute description defined by the metadata;

2) Set the main attribute name m_attr_name to describe the main attribute and the monitoring scope of the linkage rule;

3) Set the subordinate attribute name s_attr_name to describe the scope of influence of changes in subordinate attributes and main attributes. When a main attribute affects multiple subordinate attributes, it can be described by multiple rules.

For ease of understanding, as shown in Table 2, an embodiment of the present application shows a preferred attribute rule linkage table for explaining the scope of the subordinate attribute list affected by the change of the main attribute.

Table 2 X_RULE_ATTR_RELA rule attribute linkage table

Step 3: Action definition, further deconstruct the result of scene abstraction, define the possible impact of changes in the main attribute on the subordinate attribute, model the rules based on the action type obtained by analysis, and consider the requirements of later scalability, set a dictionary description for the action type to facilitate flexible expansion. Specifically, the action type definition method may include: the rule type s_attr_act in Table 2 is a typical field for describing several types of main attributes affecting subordinate attributes, and the specific dictionary value of the typical field is described as follows:

Table 3 Definition table of master-slave attribute influence type

Step 4: Relationship definition, further deconstruct the result of scene abstraction, and define the specific expression of the influence of changes in the main attribute on the content of the subordinate attribute. For example: the subordinate attribute needs to change its value range according to the value range of the main attribute, or the subordinate attribute needs to change its attribute state according to the change of the main attribute, etc. The above-mentioned value range and attribute state are the specific expressions of the influence content. Specifically, the main ways of relationship definition can be:

1) The action types of the main attribute affecting the subordinate attribute are classified into: one is the influence of the custom value range, the value linkage mentioned above, mapped to the action type in Table 3, that is, the action type corresponding to the dictionary value 0; the other is the influence on the data based on established rules, such as the logical operation mentioned above, mapped to the action type in Table 3, that is, the graying corresponding to the dictionary value 1, the required field corresponding to the dictionary value 2, the assembly corresponding to the dictionary value 3, the calculation corresponding to the dictionary value 4, and the JS code corresponding to the dictionary value 5.

2) The "Rule Action s_attr_rule" field in Table 2 is defined as a specific expression that affects the content. For example, when the action type (X_RULE_ATTR_RELA.s_attr_act) = [Assemble], the specific expression that affects the content (X_RULE_ATTR_RELA.s_attr_rule) = a string such as "[Attribute A]||[Attribute B]||'Test'", which means that when the main attribute changes, the value of the subordinate attribute becomes "[Main attribute A] assembled with [Subordinate attribute B] assembled with a text string [Test]". For another example, when the action type (X_RULE_ATTR_RELA.s_attr_act) = [Calculation], the specific expression that affects the content (X_RULE_ATTR_RELA.s_attr_rule) = a string of "[attribute A]+[attribute B]*[attribute C]+1", which means that when the main attribute changes, the value of the subordinate attribute becomes "[the value of the main attribute A] plus [the value of the subordinate attribute B] multiplied by [the value of another attribute C] plus 1".

In addition, the relationship definition also includes the definition of the logical operation relationship and the value linkage relationship. The logical operation relationship can be defined in the following way: when the "s_attr_act rule type" field in Table 2 is not equal to the value linkage, it is defined by the "s_attr_rule rule action" in Table 2; the value linkage relationship can be defined in the following way: when the "s_attr_act rule type" field in Table 2 is equal to the value linkage, it is defined by the mapping relationship between the primary and secondary attribute value ranges defined in Table 4.

Table 4 X_Main_Slave_Rela dictionary value table

Based on the above detailed description of the pre-setting process of the attribute linkage rule, the page data processing method based on the attribute linkage rule provided in the embodiment of the present application will be described in detail below.

As shown in FIG. 1 to FIG. 3, it is a flow chart of the method provided in the embodiment of the present application, and the method is implemented by steps S1 to S3 but is not limited to:

Step S1. Detect the user's assignment operation on the main attribute and determine whether the main attribute has an executable attribute linkage rule. If yes, then obtain the data change of the main attribute;

It should be noted that a form contains multiple components, each component contains properties and methods, wherein the property linkage rules of one or more properties are preset and bound, so that when the property value or state changes, that is, after the user operates the property value on the interface, it is necessary to determine whether the property has a preset property linkage rule, so as to enter the subsequent step of automatic data processing based on the property linkage rule.

Before step S1, the method further includes:

Step S01. Create a form instance to enter page initialization, and obtain the initialization message of the dynamic component through the basic form information, wherein the basic form information includes the form type and the form template path, and the initialization message includes the basic form attributes and the attribute linkage rule table;

Among them, the form uses VUE+Element-UI as the basis to build the main application, realize the dynamically configurable basic form, and the mutual linkage of each element component in the form, based on the initialization message of the dynamic component provided by the backend, the message describes in detail all the fields of each attribute, and renders the overall form attributes, the type of each attribute, the attribute verification rules and the attribute linkage rules. Among them, as shown in Table 5, one of the form attribute field tables in the embodiment of the present application is shown as follows:

Table 5 Form attribute field table

Among them, one of the optional attribute field types in the embodiment of the present application is:

1) Input text box: Based on the el-input method, it distinguishes between normal text input TextEditor, number input, password input PasswordEditor, etc.;

2) Drop-down selection box, based on el-select, distinguishes between single-select drop-down ChooseDictionary and multiple-select drop-down ChooseMultipleDictionary, and the initialization data contains the drop-down dictionary selection;

3) Date selection box, based on el-time-picker/el-date-picker method, distinguishes between time selection ChooseDateTime and date selection ChooseDate;

4) The associated object selector, ChooseRelation, is based on the el-input method and uses the click event showRelationFun (display relationship function) bound to the el-icon-search icon. According to the initialization parameter configuration, a custom associated object query component nested in the el-dialog pops up and selects an object before filling it back into the el-input input box of the current form.

Among them, an optional attribute verification rule in the embodiment of the present application can be to bind each attribute rule to the rules of the el-form form through the tool class util.parseValidators, and verify it through the validate event when submitting the form. Specifically, it includes the following verification items:

1) Field required validation RequiredValidator, binding validation attribute required;

2) Data range validation RangeValidator, binding validation attribute maximum max/min value;

3) Data length check LengthValidator, converted into text length regular expression check;

4) Regular matching validation RegExpValidator, bind validation attribute regular expression pattern.

It is worth noting that the attribute verification rules can only meet the simple rules of a single form attribute when initializing the interface. On this basis, the aforementioned attribute linkage rules are applied to realize the specific attribute linkage function.

In a specific implementation, a form instance is created to enter page initialization, and an initialization message of a dynamic component is obtained through basic form information, specifically including:

Call the created method of the VUE template to create an instance, and call the intipage method to enter the page initialization;

Request a message to the backend through the form type metaClassName and the form template type viewConfigName, so that the backend can generate an initialization message in jason format according to the message request;

Receive the initialization message returned by the backend, where the initialization message contains the form basic attributes formGroups and the attribute linkage rule table attrRules.

Step S02. Rendering a basic page according to the basic attributes of the form, using the attribute linkage rule table as a global variable of the form, and setting a linkage function corresponding to each linkage rule;

Specifically, if the backend database is configured with executable attribute linkage rules, the backend will read the executable rule list and bind it to the form as a global variable of the form when the template is loaded, and build the linkage function of the corresponding rule into the form component.

As shown in FIG. 4 , in a specific implementation manner, rendering a basic page according to the basic attributes of the form includes:

Call the parseForm method to convert the basic form attributes formGroups into the basic form identification object of the Element-UI library, and render the basic page.

Step S03: Setting a monitoring event in each subcomponent of the form so that each subcomponent can detect the user's assignment operation on the main attribute based on the monitoring event.

It should be noted that the various sub-components of the form in the embodiment of the present application are generated by calling the form drawing drawView method during the form creation phase according to the form type and form properties defined in the template, and the form data is passed unidirectionally from the parent component to the child component to set the properties and display values of the sub-component.

In a possible design, after determining whether the main attribute has an executable attribute linkage rule, the method further includes:

When the child component's listening event listens to the data change of the parent component, the assignment information is passed back to the parent component through the listening event through the callback function, so that the parent component can judge whether the current value of the main attribute meets the preset requirements.

In a possible design, whether the current value of the primary attribute meets the preset requirements is judged, including:

If the form currently needs to execute and the triggered main attribute has executable attribute linkage rules and linkage functions, then set local variables in the linkage function, and further determine whether the executable attribute linkage rule is triggered by the default value and the current value is the default value;

If the executable attribute linkage rule is triggered by the default value and the current value is the default value, the value of the local variable is considered to be true or false, otherwise the value of the local variable is considered to be undefined;

If the executable attribute linkage rule is configured with additional judgment rules, and the current value meets the additional judgment rules, the value of the local variable is considered true, otherwise it is false.

Step S2. Obtain the corresponding subordinate attribute list according to the main attribute and its data change, determine the action type of the subordinate attribute according to the attribute linkage rule, and determine the data processing rule of the subordinate attribute according to the action type, wherein the action type includes value linkage;

In a specific implementation of step S2, the action type of the subordinate attribute is determined according to the attribute linkage rule, and the data processing rule of the subordinate attribute is determined according to the action type, including:

According to the dictionary value of the attribute action type in the attribute linkage rule table, determine the action type corresponding to the dictionary value;

If the action type is value linkage, the mapping relationship between the value range of the primary attribute and the value range of the secondary attribute is obtained, so as to substitute the mapping relationship into the rendering API method to render the page data;

If the action type is non-value linkage, the calculation rules defined in the calculation logic of the slave attribute are obtained so that the calculation rules are substituted into the rendering API method to render the page data.

Step S3. Match the rendering API according to the action type, substitute the data processing rules of the slave attribute into the rendering API method to render the page data, and display the data rendering result on the user interface.

In a specific implementation of step S3, the data processing rules of the slave attributes are substituted into the rendering API method to render the page data, including:

Determine the corresponding linkage logic according to the data processing rules of the slave attributes, and call the corresponding linkage logic in the rendering API method to render the page data. The linkage logic includes value linkage logic, dictionary range value logic, text logic, attribute write-back logic and object write-back logic.

Specifically, the value linkage logic includes changing the Boolean value of the subcomponent attribute to the value of the local variable, wherein the undefined value is converted to true processing;

The dictionary range value logic includes reading the dictionary range data of the dictionary configuration table and putting it into the global cache. If there is no dictionary list and the configuration dictionary exists, the first value of the dictionary is taken. If the dictionary list exists and the configuration dictionary data exists, the dictionary list is filtered as the configuration value. If the currently selected dictionary paper is in the filtered dictionary list, the current display value of the subordinate attribute is not changed, otherwise it is left blank.

The text logic includes terminating execution if the value of the local variable is false, otherwise executing the corresponding text operation function and placing the execution result into the display value of another specified subcomponent;

The attribute write-back logic includes: if the query pop-up window result exists, then process it according to the result data type and merge it into the form data;

The object write-back logic includes: traversing the form data, converting the matching fields according to the configuration rules and incorporating them into the pop-up query conditions.

Based on the above disclosed content, the embodiment of the present application detects the user's assignment operation on the main attribute, and determines whether the main attribute has an executable attribute linkage rule. If so, the data change of the main attribute is obtained; the corresponding subordinate attribute list is obtained according to the main attribute and its data change, the action type of the subordinate attribute is determined according to the attribute linkage rule, and the data processing rule of the subordinate attribute is determined according to the action type, wherein the action type includes value linkage; the rendering API is matched according to the action type, and the data processing rule of the subordinate attribute is substituted into the rendering API method to render the page data, and the data rendering result is displayed in the user interface. Thus, the traditional page development mode of user interface + metadata is broken, and a new page development mode based on user interface + rule adaptation + metadata is provided. The interface data relationship and data processing method are encapsulated by pre-setting attribute linkage rules, and the unified management of page data rules is realized, the complexity of page code logic is reduced, and the number of pages is reduced; when the user's operation on the interface is detected, the page data is automatically processed based on the data processing method defined by the attribute linkage rule, and the problem of page data processing flexibility is further solved on the basis of realizing flexible display of page attributes.

In order to illustrate the specific application effect of the embodiment of the present application, a specific attribute linkage application example is given below to further verify the page data processing method based on attribute linkage rules in the embodiment of the present application, as follows:

Example of value linkage: The use of attribute linkage rules needs to be configured in Table 2 and Table 4. For example, as shown in Figure 5, the specified rule_no changes the value range of s_attr_val (subordinate attribute) according to the value of m_attr_val (primary attribute value). The linkage effect is shown in the figure. As can be seen from Figure 6, when setting the linkage, when the primary attribute takes the specified value, when the subordinate attribute dictionary value range changes, it is automatically set to the first item of the new dictionary range (only filtering), and the original dictionary range is restored when it is not triggered; when setting the default value, when setting m_attr_val (primary attribute value) to null (empty), the default dictionary range of the template will be modified. If the subordinate attribute is not a character, the first s_attr_val (subordinate attribute value) will be filled in as the default value (can be cleared).

Example of attribute operation: As shown in Figures 7 and 8, attribute operations include attribute switches, common configurations, suffix buttons, and other configurations. When the attribute switch operation is performed, the attribute to be operated is written in the s_act_rule (rule action) field [attribute = true/false] and concatenated with the & symbol. When the equal sign is omitted, the attribute is assumed to be true (when the main attribute condition is met); common configurations include true/false modification operations of parameters such as required, disabled, readonly, and pDisabled; the display and icon configuration of the input box suffix button [suffixIcon = el-icon-edit] is added to the suffix button, and the button method uses a callback function to call its own method according to prop; other configurations include other native input type values that can also be configured for switches. When the main attribute is a dictionary and multiple values correspond to the same operation, // can be used to concatenate the main attribute value.

Assembly (multi-attribute) example: The assembly rules are shown in Figure 9, and the assembly effect can be seen in Figure 10. It should be noted that the applicable conditions for assembly are that all attributes that need to be assembled need to be configured in the form, and it is recommended to use the back-end assembly logic; the assembly order is to sort from small to large according to ruleNo outside the area, and the backfill value of the dictionary or the input box text can be assembled (when the m_attr_val field is not empty, the non-compliant value will not be assembled); when the assembly method is to add a new assembly rule code (written in the calculationFormulas.js file of the generateFrom component on the front end), set the s_act_rule field to the method name of the new assembly rule code.

Calculation (multi-attribute) example: The calculation rules are shown in Figure 11, where the applicable conditions for the calculation are that all attributes that need to be calculated need to be configured in the form (ignore non-numbers when calculating numbers, and also apply to reading the number of inputs of the main attribute to change the value of the subordinate attribute); the calculation method is to add a new calculation rule code (written in the calculationFormulas.js file of the generateForm component on the front end), and then modify the s_act_rule field to the method name of the calculation rule code; for example: Total antenna downtilt angle = mechanical downtilt angle + electrical downtilt angle_FDD1.8G + electrical downtilt angle_NR3.5G + electrical downtilt angle_800M + electrical downtilt angle_2.1G + built-in downtilt angle.

Example of associative control writing back to the lower level: As shown in Figure 12, its applicable condition is that both the primary and secondary attributes are configured as associative controls, the attributes brought out are non-association relationships (attributes without @), and then the association relationship configured in the secondary attribute query template is filled in s_act_rule; the write-back order is that if the association relationship pop-up window itself has a trigger field that will increase its own attributes, and the field name is the same as the secondary attribute field to be backfilled, the backfilled value covers the initial value brought in by the trigger field, for example: after selecting the device (M), the device (R) to which the port (S) belongs is written back, and after selecting the owned device (M), the owned device (R) in the owned board (S) is written back.

An example of the association control writeback form is shown in Figure 13. Its applicable condition is that the main attribute is configured as an association control, and the attribute brought out must be an association relationship (attribute with @), and then fill in the association relationship configured in the main attribute query template in s_act_rule. Its special application scenario is that the installation location brings out the station and the latitude of the station, and the upper BTS brings out the base station identification according to the network type (multiple-select dictionary field). When automatically clearing, when the main attribute is cleared, the subordinate attribute will be cleared as well.

Among them, it should be noted that the applicable components of the above-mentioned attribute linkage examples include but are not limited to the generateForm component and its upper-level components such as generateGroupForm and parseView; the conditional judgment adopted is that when the main attribute value (m_attr_val) is null (empty), any text triggers the rule by default, and when there is a value, it is identified as a fixed value (the fixed value will be ignored when it does not match) to trigger the rule; the rule judgment adopted is that a main attribute can be associated with multiple sub-attributes, and only when the main attribute + subordinate attribute + rule action + rule template are the same, they are judged as the same type of rules; the rule loading method adopted is spec_id to support the configuration of the main category of equipment. If there is a sub-category specification, the detailed category specification takes precedence (the detailed category replaces the main category).

The second aspect provides a page data processing device based on attribute linkage rules according to the first aspect, comprising:

The data change acquisition module is used to detect the user's assignment operation on the main attribute and determine whether the main attribute has an executable attribute linkage rule. If so, the data change of the main attribute is obtained;

The data processing rule determination module is used to obtain the corresponding subordinate attribute list according to the main attribute and its data change, determine the action type of the subordinate attribute according to the attribute linkage rule, and determine the data processing rule of the subordinate attribute according to the action type, wherein the action type includes value linkage;

The page data rendering module is used to match the rendering API according to the action type, substitute the data processing rules from the attributes into the rendering API method to render the page data, and display the data rendering results on the user interface.

The working process, working details and technical effects of the aforementioned device provided in the second aspect of this embodiment can be referred to the method described in the first aspect or any possible design of the first aspect, and will not be repeated here.

In a third aspect, the present invention provides a computer-readable storage medium having instructions stored thereon. When the instructions are run on a computer, the method described in any possible design of the first aspect is executed.

The computer-readable storage medium refers to a carrier for storing data, which may include but is not limited to floppy disks, CDs, hard disks, flash memories, USB flash drives and/or memory sticks, etc. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

The working process, working details and technical effects of the aforementioned computer-readable storage medium provided in the third aspect of this embodiment can be referred to the method described in the first aspect or any possible design of the first aspect, and will not be repeated here.

Finally, it should be noted that the above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims (10)

A page data processing method based on attribute linkage rules, characterized by comprising: Detect the user's assignment operation on the main attribute, and determine whether the main attribute has an executable attribute linkage rule. If so, obtain the data change of the main attribute; Obtain the corresponding subordinate attribute list according to the main attribute and its data change, determine the action type of the subordinate attribute according to the attribute linkage rule, and determine the data processing rule of the subordinate attribute according to the action type, wherein the action type includes value linkage; Match the rendering API according to the action type, substitute the data processing rules from the attributes into the rendering API method to render the page data, and display the data rendering results in the user interface. The page data processing method based on attribute linkage rules according to claim 1 is characterized in that the action type of the subordinate attribute is determined according to the attribute linkage rule, and the data processing rule of the subordinate attribute is determined according to the action type, including: According to the dictionary value of the attribute action type in the attribute linkage rule table, determine the action type corresponding to the dictionary value; If the action type is value linkage, the mapping relationship between the value range of the primary attribute and the value range of the secondary attribute is obtained, so as to substitute the mapping relationship into the rendering API method to render the page data; If the action type is non-value linkage, the calculation rules defined in the calculation logic of the slave attribute are obtained so that the calculation rules are substituted into the rendering API method to render the page data. The page data processing method based on attribute linkage rules according to claim 1 is characterized in that before detecting the user's assignment operation on the primary attribute, the method further comprises: Create a form instance to enter the page initialization, and obtain the initialization message of the dynamic component through the basic form information. The basic form information includes the form type and form template path, and the initialization message includes the basic form attributes and attribute linkage rule table; Rendering a basic page according to the basic attributes of the form, using the attribute linkage rule table as a global variable of the form, and setting a linkage function corresponding to each linkage rule; Set a listening event in each subcomponent of the form so that each subcomponent can detect the user's assignment operation on the main attribute based on the listening event. The page data processing method based on attribute linkage rules according to claim 3 is characterized in that the page initialization is entered by creating a form instance, and the initialization message of the dynamic component is obtained through the basic information of the form, including: Call the created method of the VUE template to create an instance, and call the intipage method to enter the page initialization; Request a message to the backend through the form type metaClassName and the form template type viewConfigName, so that the backend can generate an initialization message in jason format according to the message request; Receive the initialization message returned by the backend, where the initialization message contains the form basic attributes formGroups and the attribute linkage rule table attrRules. The page data processing method based on attribute linkage rules according to claim 3 is characterized in that rendering a basic page according to the basic attributes of the form comprises: Call the parseForm method to convert the basic form attributes formGroups into the basic form identification object of the Element-UI library, and render the basic page. The page data processing method based on attribute linkage rules according to claim 3 is characterized in that after determining whether the main attribute has an executable attribute linkage rule, the method further comprises: When the child component's listening event listens to the data change of the parent component, the assignment information is passed back to the parent component through the listening event through the callback function, so that the parent component can judge whether the current value of the main attribute meets the preset requirements. The page data processing method based on attribute linkage rules according to claim 6 is characterized in that judging whether the current value of the main attribute meets the preset requirements includes: If the form currently needs to execute and the triggered main attribute has executable attribute linkage rules and linkage functions, then set local variables in the linkage function, and further determine whether the executable attribute linkage rule is triggered by the default value and the current value is the default value; If the executable attribute linkage rule is triggered by the default value and the current value is the default value, the value of the local variable is considered to be true or false, otherwise the value of the local variable is considered to be undefined; If the executable attribute linkage rule is configured with an additional judgment rule and the current value meets the additional judgment rule, the value of the local variable is considered true, otherwise it is false. The page data processing method based on attribute linkage rules according to claim 7 is characterized in that the data processing rules from the attributes are substituted into the rendering API method to render the page data, comprising: Determine the corresponding linkage logic according to the data processing rules of the attributes, and call the corresponding linkage logic in the rendering API method to render the page data. The linkage logic includes value linkage logic, dictionary range value logic, text logic, attribute write-back logic and object write-back logic. The page data processing method based on attribute linkage rules according to claim 8 is characterized in that: The value linkage logic includes changing the Boolean value of the subcomponent attribute to the value of the local variable, wherein the undefined value is converted to true processing; The dictionary range value logic includes reading the dictionary range data of the dictionary configuration table and putting it into the global cache. If there is no dictionary list and the configuration dictionary exists, the first value of the dictionary is taken. If the dictionary list exists and the configuration dictionary data exists, the dictionary list is filtered as the configuration value. If the currently selected dictionary paper is in the filtered dictionary list, the current display value of the subordinate attribute is not changed, otherwise it is left blank. The text logic includes terminating execution if the value of the local variable is false, otherwise executing the corresponding text operation function and placing the execution result into the display value of another specified subcomponent; The attribute write-back logic includes: if the query pop-up window result exists, then process it according to the result data type and merge it into the form data; The object write-back logic includes: traversing the form data, converting the matching fields according to the configuration rules and incorporating them into the pop-up query conditions. A storage medium, characterized in that instructions are stored on the storage medium, and when the instructions are run on a computer, the page data processing method based on attribute linkage rules as described in any one of claims 1 to 9 is executed.