A method for acquiring a table component and a computing device

Abstract

This application provides a method and computing device for obtaining table components. The method includes: acquiring raw business data; wherein the raw business data includes attribute information of multiple table headers and attribute information of multiple table bodies; determining a table header structure based on table header merging rules and the attribute information of multiple table headers; wherein the table header structure indicates the hierarchical relationship between multiple table headers, the display result of each table header, and the display attributes of each table header; the table header display attributes include the number of rows spanned and the number of columns spanned; determining a table body structure based on table body merging rules, the table header structure, and the attribute information of multiple table bodies; wherein the table body structure indicates the display result of multiple table bodies, the display attributes of the table bodies, and the table headers corresponding to the table bodies; the table body display attributes include the number of rows spanned or a hidden / show flag; and rendering the table header structure and table body structure to obtain a table component. This method improves the efficiency and accuracy of obtaining table components.

Description

Technical Field

[0001] This application relates to the field of computing device technology, and in particular to a method for obtaining a table component and a computing device. Background Technology

[0002] In modern information management, tables are a commonly used method for displaying data.

[0003] In related technologies, it is usually necessary to manually analyze the actual situation of the original business data and then write corresponding conversion code. Based on the coded conversion code, the original business data is converted into a table component (also known as a user interface (UI) table component) for client applications on terminal devices to display and process.

[0004] However, the methods in these technologies require manual analysis of the actual situation of each type of original business data, and then writing corresponding conversion code, which leads to the problem of low efficiency in obtaining table components. Summary of the Invention

[0005] This application provides a method and computing device for obtaining table components, which improves the efficiency of obtaining table components.

[0006] In a first aspect, embodiments of this application provide a method for obtaining a table component, including:

[0007] Obtain the raw business data; the raw business data includes attribute information of multiple table headers and attribute information of multiple table bodies;

[0008] Based on the header merging rules and the attribute information of multiple headers, the header structure is determined; the header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header; the header display attributes include the number of rows spanned and the number of columns spanned.

[0009] The table body structure is determined based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies. The table body structure indicates the table body display results, table body display attributes, and the table headers corresponding to the table bodies. The table body display attributes include the number of rows spanned or the hidden / show flags.

[0010] The table header and body structures are rendered to obtain the table component.

[0011] In this solution, by utilizing pre-configured header merging rules to process the attribute information of multiple headers in the original business data to obtain the header structure, the efficiency and accuracy of obtaining the header structure are improved. Similarly, by utilizing pre-configured body merging rules to process the attribute information of multiple body data in the original business data to obtain the body structure, the efficiency and accuracy of obtaining the body structure are improved. By merging and rendering the header and body structures, table components are obtained, eliminating the need for manual analysis of the original business data and writing corresponding conversion code based on individual expertise. This lowers the barrier to obtaining table components and improves the efficiency of obtaining them. Furthermore, compared to merging data during rendering, which leads to low rendering efficiency, this embodiment of the application can merge data before rendering, thus improving rendering efficiency.

[0012] In one implementation, the table header's attribute information includes the table header name, table header identifier, parent table header identifier, and hierarchy information; based on the table header merging rules and the attribute information of multiple table headers, the table header structure is determined, including:

[0013] Determine the hierarchical relationship between multiple table headers based on the parent header identifier and the header identifier of multiple table headers;

[0014] Retrieve multiple merge rules from the header merge rules;

[0015] For any given merge rule, the target table header corresponding to the merge rule is determined from multiple table headers based on the merge conditions in the merge rule; the hierarchical information of the target table header is matched with the hierarchical information in the merge conditions.

[0016] Based on the header name, determine the header display result corresponding to the target header;

[0017] Based on the merge action configuration information in the merge rules, determine the number of columns spanned corresponding to the target table header;

[0018] Set the preset row span number to the row span number corresponding to the target table header.

[0019] In this scheme, the computing device can first determine the hierarchical relationship (belonging to the header structure) between multiple headers based on the parent header identifier and the header identifiers of multiple headers. For any merge rule in the header merge rules, the computing device can determine the target header corresponding to the merge rule from multiple headers according to the merge conditions in the merge rule; the hierarchical information of the target header matches the hierarchical information in the merge conditions. The computing device can determine the header display result corresponding to the target header based on the header name, and determine the number of columns spanned by the target header according to the merge action configuration information in the merge rule, and set the preset number of rows spanned as the number of rows spanned by the target header. Through the above method, even if the headers in the original business data change, the computing device can still accurately identify the hierarchical relationship (also known as the dependency link) between headers, improving the efficiency and accuracy of obtaining the hierarchical relationship. In addition, through the above method, the number of columns spanned and rows spanned corresponding to each header can be determined, thereby improving the efficiency and accuracy of determining the number of columns spanned and rows spanned corresponding to the header, and thus improving the display effect of the table component.

[0020] In one implementation, the number of columns spanned corresponding to the target header is determined based on the merge action configuration information in the merge rules, including:

[0021] When the target merge type in the merge action configuration information is cross-child node merge, the header set corresponding to the target header is determined based on the header identifiers of multiple headers and the parent header identifiers of multiple headers; the header set includes multiple candidate headers; the target header is the direct parent header or indirect parent header of the candidate headers;

[0022] Based on the hierarchical information of each candidate header, determine multiple selected headers from the multiple candidate headers;

[0023] The total number of selected headers is set as the number of columns spanned by the target header.

[0024] In this scheme, when the target merge type in the merge action configuration information is a cross-child node merge, the computing device determines the set of headers corresponding to the target header based on the header identifiers of multiple headers and their parent header identifiers. The header set includes multiple candidate headers; the target header is either a direct parent or indirect parent header of one of the candidate headers. The computing device can then determine multiple selected headers from the candidate headers based on their hierarchical information, and the total number of selected headers is used to determine the number of columns spanned by the target header. This method improves the efficiency and accuracy of determining the number of columns spanned.

[0025] In one implementation, based on the hierarchical information of each candidate header, multiple selected headers are determined from the multiple candidate headers, including:

[0026] For any candidate header, determine whether the candidate header is a leaf header based on the hierarchy information of the candidate header;

[0027] If the candidate header is determined to be a leaf header, then the candidate header is selected.

[0028] In this scheme, for any candidate header, the computing device can determine whether the candidate header is a leaf header based on its hierarchical information. If the computing device determines that the candidate header is a leaf header, it can then select it as the chosen header. This improves the accuracy of selecting the header, and consequently, improves the accuracy of determining the number of columns spanned.

[0029] In one implementation, the number of columns spanned corresponding to the target header is determined based on the merge action configuration information in the merge rules, including:

[0030] If the target merge type in the merge action configuration information is "no merge", the preset number of columns to be spanned will be set to the number of columns to be spanned corresponding to the target table header.

[0031] In this scheme, when the target merging type is non-merging, the computing device can determine the preset number of column spans as the number of column spans corresponding to the target table header. This method improves the efficiency of determining the number of column spans.

[0032] In one implementation, the table body's attribute information includes the table body name, ranking information, prefix information, and grouping attributes; the table body structure is determined based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies, including:

[0033] Based on the grouping attributes of multiple table bodies and the table header structure, multiple table bodies are grouped to obtain multiple groups corresponding to table headers; wherein, the table header structure includes the table header; the grouping attributes of the table bodies included in the group corresponding to the table header are consistent with the table header identifier;

[0034] For any group corresponding to a header, the header is defined as the header corresponding to the table body included in the group;

[0035] Based on the ranking information of the first table body, determine the table body display attributes of the first table body; the first table body can be any one of multiple table bodies;

[0036] Based on the template information, the ranking information of the first table body, and the prefix information of the first table body, generate the ranking display result corresponding to the first table body;

[0037] Based on the table body name of the first table body and the ranking display result corresponding to the first table body, determine the table body display result of the first table body.

[0038] In this scheme, the computing device can group multiple table bodies according to their grouping attributes and header structure, resulting in groups corresponding to multiple headers. The header structure includes the header itself; the grouping attributes of the table bodies included in the group corresponding to the header are consistent with the header identifier of the header. For any group corresponding to a header, the computing device can determine the header as the header corresponding to the table bodies included in the group. The computing device can determine the display attributes of the first table body based on its ranking information; the first table body can be any one of multiple table bodies. The computing device can generate the ranking display result corresponding to the first table body based on template information, the ranking information of the first table body, and the prefix information of the first table body. The computing device can determine the display result of the first table body based on its name and the ranking display result. By processing the attribute information of multiple table bodies using the above-mentioned table body merging rules, the table body structure can be constructed. This improves the efficiency and accuracy of the computing device in obtaining the table body structure, thereby improving the efficiency of the computing device in obtaining table components.

[0039] In one implementation, the table body display attributes of the first table body are determined based on the ranking information of the first table body, including:

[0040] Determine whether the ranking information in the first table body is within a numerical range;

[0041] If the ranking information of the first table body is determined to be within a numerical range, the first table body is expanded according to the ranking information to obtain at least one expanded table body.

[0042] The number of rows spanned is determined based on at least one extended table body and the first table body;

[0043] The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the extended table body are determined to include the hiding of the display marker.

[0044] In this scheme, once the ranking information of the first table body is determined to be within a numerical range, the computing device can expand the first table body based on the ranking information to obtain at least one expanded table body. The computing device can then determine the number of row spans based on the at least one expanded table body and the first table body. The computing device can determine that the display attributes of the first table body include the number of row spans, and that the display attributes of the expanded table bodies include hiding / showing markers. Through this method, the display attributes of the first table body can accurately reflect its actual situation, thereby enabling the table component to match the actual situation of the original business data.

[0045] In one implementation, the method further includes:

[0046] If it is determined that the ranking information of the first table body is not within a numerical range, then it is determined whether there is at least one target table body in the group to which the first table body belongs; wherein, the grouping attribute of the first table body is consistent with the grouping attribute of the target table body, and the ranking information of the first table body is consistent with the ranking information of the target table body; the first table body and at least one target table body are tables with consecutive sorting numbers; the sorting number is obtained by sorting the business data of multiple tables body included in the group according to the ranking information of the business data of the tables body in the group to which the first table body belongs;

[0047] If it is determined that there is at least one target table body, the number of rows spanned is determined based on the at least one target table body and the first table body;

[0048] The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the target table body are determined to include the hiding of display tags.

[0049] In this scheme, when it is determined that the ranking information of the first table body is not within a numerical range, the computing device can determine whether there is at least one target table body in the group to which the first table body belongs. Specifically, the grouping attributes of the first table body and the target table body are consistent, and the ranking information of the first table body is consistent with the ranking information of the target table body. The first table body and at least one target table body are tables with consecutive sorting numbers. The sorting number is obtained by sorting the business data of multiple tables included in the group based on the ranking information of the business data of the tables in the group to which the first table body belongs. When it is determined that there is at least one target table body, the computing device can determine the number of rows spanned based on the at least one target table body and the first table body. The computing device can also determine that the display attributes of the first table body include the number of rows spanned, and that the display attributes of the target table body include hidden display markers. Through this method, even when the ranking information of the first table body is not within a numerical range, the number of rows spanned by the first table body can be accurately determined, thus ensuring that the display attributes of the first table body accurately reflect its actual situation, and ultimately enabling the table component to match the actual situation of the original business data.

[0050] Secondly, embodiments of this application provide a method for obtaining a table component, applied to a terminal device, the method comprising:

[0051] The system retrieves a table component sent by the computing device. This table component is rendered based on the header and body structures. The header structure is determined by header merging rules and the attribute information of multiple headers in the original business data. The body structure is determined by body merging rules, the header structure, and the attribute information of multiple bodies in the original business data. The header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header. Header display attributes include the number of rows spanned and the number of columns spanned. The body structure indicates the body display result of multiple bodies, the body display attributes, and the corresponding headers for each body. Body display attributes include the number of rows spanned or a hidden / show flag.

[0052] Perform display processing on the table component.

[0053] In this scheme, the terminal device can obtain the table component sent by the computing device and perform display processing on the table component. By having the computing device process the original business data using pre-configured header and body merging rules, the header and body structures are obtained, and then these are rendered to obtain the table component. This eliminates the need for manual analysis of the original business data and writing corresponding conversion code based on individual expertise, lowering the barrier to obtaining the table component and improving its efficiency. Furthermore, compared to the terminal device merging data during rendering, which leads to low rendering efficiency and consequently low efficiency in displaying the table component, this embodiment allows the computing device to merge data before rendering, thus improving rendering efficiency.

[0054] Thirdly, embodiments of this application provide a device for acquiring table components, including:

[0055] The acquisition module is used to acquire raw business data; the raw business data includes attribute information of multiple table headers and attribute information of multiple table bodies.

[0056] The processing module is used to determine the header structure based on the header merging rules and the attribute information of multiple headers. The header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header. The header display attributes include the number of rows spanned and the number of columns spanned.

[0057] The processing module is also used to determine the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies; wherein, the table body structure indicates the table body display result, table body display attributes, and the table header corresponding to the table body of multiple table bodies; the table body display attributes include the number of rows spanned or the hidden display flag;

[0058] The processing module is also used to render the table header and body structures to obtain table components.

[0059] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0060] In one implementation, the table header's attribute information includes the table header name, table header identifier, parent table header identifier, and hierarchy information; the processing module is specifically used for:

[0061] Determine the hierarchical relationship between multiple table headers based on the parent header identifier and the header identifier of multiple table headers;

[0062] Retrieve multiple merge rules from the header merge rules;

[0063] For any given merge rule, the target table header corresponding to the merge rule is determined from multiple table headers based on the merge conditions in the merge rule; the hierarchical information of the target table header is matched with the hierarchical information in the merge conditions.

[0064] Based on the header name, determine the header display result corresponding to the target header;

[0065] Based on the merge action configuration information in the merge rules, determine the number of columns spanned corresponding to the target table header;

[0066] Set the preset row span number to the row span number corresponding to the target table header.

[0067] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0068] In one implementation, the processing module is specifically used for:

[0069] When the target merge type in the merge action configuration information is cross-child node merge, the header set corresponding to the target header is determined based on the header identifiers of multiple headers and the parent header identifiers of multiple headers; the header set includes multiple candidate headers; the target header is the direct parent header or indirect parent header of the candidate headers;

[0070] Based on the hierarchical information of each candidate header, determine multiple selected headers from the multiple candidate headers;

[0071] The total number of selected headers is set as the number of columns spanned by the target header.

[0072] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0073] In one implementation, the processing module is specifically used for:

[0074] For any candidate header, determine whether the candidate header is a leaf header based on the hierarchy information of the candidate header;

[0075] If the candidate header is determined to be a leaf header, then the candidate header is selected.

[0076] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0077] In one implementation, the processing module is specifically used for:

[0078] If the target merge type in the merge action configuration information is "no merge", the preset number of columns to be spanned will be set to the number of columns to be spanned corresponding to the target table header.

[0079] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0080] In one implementation, the table body's attribute information includes the table body name, ranking information, prefix information, and grouping attributes; the processing module is specifically used for:

[0081] Based on the grouping attributes of multiple table bodies and the table header structure, multiple table bodies are grouped to obtain multiple groups corresponding to table headers; wherein, the table header structure includes the table header; the grouping attributes of the table bodies included in the group corresponding to the table header are consistent with the table header identifier;

[0082] For any group corresponding to a header, the header is defined as the header corresponding to the table body included in the group;

[0083] Based on the ranking information of the first table body, determine the table body display attributes of the first table body; the first table body can be any one of multiple table bodies;

[0084] Based on the template information, the ranking information of the first table body, and the prefix information of the first table body, generate the ranking display result corresponding to the first table body;

[0085] Based on the table body name of the first table body and the ranking display result corresponding to the first table body, determine the table body display result of the first table body.

[0086] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0087] In one implementation, the processing module is specifically used for:

[0088] Determine whether the ranking information in the first table body is within a numerical range;

[0089] If the ranking information of the first table body is determined to be within a numerical range, the first table body is expanded according to the ranking information to obtain at least one expanded table body.

[0090] The number of rows spanned is determined based on at least one extended table body and the first table body;

[0091] The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the extended table body are determined to include the hiding of the display marker.

[0092] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0093] In one implementation, the processing module is also used for:

[0094] If it is determined that the ranking information of the first table body is not within a numerical range, then it is determined whether there is at least one target table body in the group to which the first table body belongs; wherein, the grouping attribute of the first table body is consistent with the grouping attribute of the target table body, and the ranking information of the first table body is consistent with the ranking information of the target table body; the first table body and at least one target table body are tables with consecutive sorting numbers; the sorting number is obtained by sorting the business data of multiple tables body included in the group according to the ranking information of the business data of the tables body in the group to which the first table body belongs;

[0095] If it is determined that there is at least one target table body, the number of rows spanned is determined based on the at least one target table body and the first table body;

[0096] The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the target table body are determined to include the hiding of display tags.

[0097] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0098] Fourthly, embodiments of this application provide a device for acquiring a table component, comprising:

[0099] The acquisition module is used to acquire table components sent by the computing device. The table components are rendered based on the header and body structures. The header structure is determined based on header merging rules and the attribute information of multiple headers in the original business data. The body structure is determined based on body merging rules, the header structure, and the attribute information of multiple bodies in the original business data. The header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header. The header display attributes include the number of rows spanned and the number of columns spanned. The body structure indicates the body display result of multiple bodies, the body display attributes, and the corresponding headers for each body. The body display attributes include the number of rows spanned or a hidden / show flag.

[0100] The control module is used to handle the display of the table component.

[0101] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0102] Fifthly, embodiments of this application provide a computing device, including:

[0103] The processor, and the memory that is in communication with the processor;

[0104] Memory is used to store instructions that the computer executes;

[0105] The processor is used to execute computer execution instructions stored in memory to implement the method of the first aspect.

[0106] The computing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0107] Sixthly, embodiments of this application provide a terminal device, including:

[0108] The processor, and the memory that is in communication with the processor;

[0109] Memory is used to store instructions that the computer executes;

[0110] The processor is used to execute computer execution instructions stored in memory to implement the method of the second aspect.

[0111] The computing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0112] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method of the first aspect or the second aspect.

[0113] When the computer-executable instructions in the computer-readable storage medium provided in this application are executed by a processor, the technical solutions shown in the above method embodiments can be implemented. The implementation principle and beneficial effects are similar, and will not be repeated here.

[0114] Eighthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, is used to implement the method of the first aspect or the second aspect.

[0115] When the computer program in the computer program product provided in this application is executed by a processor, it can implement the technical solution shown in the above method embodiments. The implementation principle and beneficial effects are similar, and will not be repeated here. Attached Figure Description

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

[0117] Figure 1a A schematic diagram illustrating a method for obtaining a table component according to an embodiment of this application;

[0118] Figure 1b A schematic diagram of the triggering table generation component provided in an embodiment of this application;

[0119] Figure 1c A schematic diagram of a table display component provided in an embodiment of this application;

[0120] Figure 2 A flowchart illustrating a method for obtaining a table component according to an embodiment of this application;

[0121] Figure 3a A flowchart illustrating a second embodiment of a method for obtaining a table component provided in this application;

[0122] Figure 3b A schematic diagram of a table header component provided in an embodiment of this application;

[0123] Figure 4aA flowchart illustrating a method for obtaining a table component according to an embodiment of this application, in embodiment three;

[0124] Figure 4b A schematic diagram of a table body component in a table component provided in an embodiment of this application;

[0125] Figure 5 A schematic diagram of a front-end rendering component and a table component acquisition engine provided in an embodiment of this application;

[0126] Figure 6 A schematic diagram of the structure of a form component acquisition device provided in an embodiment of this application;

[0127] Figure 7 A schematic diagram of the structure of another form component acquisition device provided in an embodiment of this application;

[0128] Figure 8 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application;

[0129] Figure 9 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

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

[0131] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0132] This application provides a method for obtaining table components. A computing device can acquire raw business data, including attribute information for multiple table headers and attribute information for multiple table bodies. The computing device can determine the table header structure based on header merging rules and the attribute information of the multiple headers. The header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header. The header display attributes include the number of rows spanned and the number of columns spanned. The computing device can determine the table body structure based on table body merging rules, the header structure, and the attribute information of the multiple table bodies. The table body structure indicates the table body display result of multiple table bodies, the table body display attributes, and the corresponding headers of the table bodies. The table body display attributes include the number of rows spanned or a hidden / show flag. The computing device can perform rendering processing on the header and body structures to obtain the table components.

[0133] The above methods improve the efficiency of obtaining table components.

[0134] The method for obtaining the table component according to the embodiments of this application will be described in detail below.

[0135] Below, to facilitate understanding of the method for obtaining the table component provided in the embodiments of this application, in conjunction with... Figure 1a , Figure 1b , Figure 1c The application scenarios involved in the embodiments of this application will be introduced.

[0136] Figure 1a This is a schematic diagram illustrating a scenario for a method of obtaining a table component provided in an embodiment of this application. For example... Figure 1a As shown, the scenario includes a computing device 10, a terminal device 20, and a database server 30. It should be noted that the computing device 10 can run a table component to retrieve the engine (…). Figure 1a (Not shown).

[0137] The computing device 10 can be a terminal device, a server, or a server cluster. When the computing device 10 is a server, from an architectural perspective, the server can be a rack server, a high-density server, a tower server, or a full rack server; from a functional perspective, the server can be a general-purpose server or an artificial intelligence server (AI server), for example, an artificial intelligence server can be an image processing server (GPU server).

[0138] Terminal device 20 may be, but is not limited to, various personal computers, laptops, smartphones, and tablets.

[0139] It should be noted that when the computing device 10 is a terminal device, the computing device 10 and the terminal device 20 can be integrated into a single terminal device or they can be different terminal devices. This application embodiment does not limit this.

[0140] Database server 30 can be a single server or a server cluster.

[0141] In this scenario:

[0142] The computing device 10 can acquire raw business data. This raw business data may include attribute information for multiple table headers and attribute information for multiple table bodies. In one implementation, the terminal device 20 can send a processing request to the computing device 10. For example, Figure 1b This is a schematic diagram of the triggering table generation component provided in an embodiment of this application. For example... Figure 1b As shown, the terminal device's display interface includes a trigger control. The terminal device 20 can respond to the user's operation on the trigger control, generate a processing request, and send the processing request to the computing device 10. The computing device 10 can respond to the processing request and retrieve the raw business data stored in the database server 30.

[0143] The computing device 10 can determine the header structure based on the header merging rules and the attribute information of multiple headers. The header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header; the header display attributes include the number of rows spanned and the number of columns spanned.

[0144] The computing device 10 can determine the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies. The table body structure indicates the table body display results, table body display attributes, and the corresponding table headers for multiple table bodies; the table body display attributes include the number of rows spanned or a hidden / show flag.

[0145] The computing device 10 can render the table header structure and table body structure to obtain a table component.

[0146] Terminal device 20 can receive the table component sent by computing device 10 and perform display processing on the table component. For example, Figure 1c This is a schematic diagram of a table display component provided in an embodiment of this application. Figure 1c As shown, the terminal device can display a table component.

[0147] It should be noted that, Figure 1a This is a schematic diagram of a scenario provided in an embodiment of this application. This embodiment of the application does not necessarily represent... Figure 1a The document does not limit the actual form of the various devices included, nor does it specify the form of the devices. Figure 1aThe interaction methods between devices are limited, and can be set according to actual needs when applying the solution.

[0148] The technical solution of this application will now be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0149] Figure 2 This is a flowchart illustrating a method for obtaining a table component according to an embodiment of this application. See also... Figure 2 The method specifically includes the following steps:

[0150] S201: Obtain raw business data.

[0151] In this embodiment, the computing device can acquire raw business data.

[0152] The original business data may include attribute information of multiple table headers (also known as table header business data) and attribute information of multiple table bodies (also known as table body business data).

[0153] In one implementation, the attribute information of the table header may include the table header name, table header identifier (also known as code), parent header identifier (parentcode), and level information. It should be noted that the attribute information of the table header may also include other information, but this embodiment does not limit this.

[0154] For example, the attribute information of a table header may include the following: the table header name is "Human Resources Operations Subclass", the table header code is "SC_5", the parent header code is "C_3", and the level information is "2".

[0155] For example, the attribute information of a table header may include the following: the table header name is "Technology Family", the table header identifier is "F_1", the parent header identifier is "null", and the level information is "0".

[0156] For example, the attribute information of a table header may include the following: the table header name is "Hardware Class", the table header code is "C_1", the parent table header code is "F_1", and the level information is "1".

[0157] In one implementation, the table body's attribute information may include the table body name, rank information, prefix information, and grouping attributes. In another implementation, the grouping attribute can be a subclass. Additionally, in yet another implementation, the table body's attribute information may also include a table body identifier (id).

[0158] For example, the attribute information of a table body may include the following: table body name is "Power Hardware Senior Expert", rank information is "12", prefix information is "T", subclass is "SC_1", and table body identifier is "1".

[0159] For example, the attribute information of a table body may include the following: table body name is "Product Testing Specialist", ranking information is "3", prefix information is "T", subclass is "SC_1", and table body identifier is "2".

[0160] For example, the attribute information of a table body may include the following: table body name is "Engineer", ranking information is "1-2", prefix information is "T", subclass is "SC_1", and table body identifier is "3".

[0161] The following section explains the process by which computing devices acquire raw business data.

[0162] In one implementation:

[0163] Terminal devices can send processing requests to computing devices. In one implementation, the terminal device can run a client that calls the engine initialization function (engine.init(config, data)) to send a processing request to the computing device.

[0164] The computing device can respond to processing requests and retrieve raw business data stored on the database server. This raw business data may include attribute information from multiple table headers and attribute information from multiple table bodies. It should be noted that the attribute information from table headers can exist in the form of an array of objects, and the attribute information from table bodies can also exist in the form of an array of objects.

[0165] S202: Determine the header structure based on the header merging rules and the attribute information of multiple headers.

[0166] In this embodiment, the computing device can obtain configuration rules.

[0167] The configuration rules include header merging rules and body merging rules.

[0168] In one implementation, the client code may include configuration rules. That is, the configuration rules are static configuration rules embedded in the client code file. The computing device can access the configuration rules in the client code.

[0169] In one implementation, the computing device can obtain configuration rules sent by the database server. It should be noted that, in another implementation, the terminal device can send an update request to the database server. The database server can respond to the update request and update the configuration rules stored on the database server. This method enables the configuration rules to be updated even if the client code has not been updated, thus improving the efficiency of configuration rule updates.

[0170] The computing device can determine the header structure based on the header merging rules and the attribute information of multiple headers.

[0171] The header structure indicates the hierarchical relationship between multiple headers, the header display result (displayfield) of each header, and the header display attributes of each header.

[0172] It should be noted that the header display attributes can include the number of rows spanned (rowspan) and the number of columns spanned (colspan).

[0173] Additionally, it should be noted that in one implementation, the header merging rule may also include a first mapping relationship. The first mapping relationship indicates the mapping between the field identifiers of various attribute information in the original business data header and the field identifiers of the attribute information in the header that the table component retrieval engine can use. For example, for the field identifier "code" of the header attribute information, the computing device running the table component retrieval engine can determine the corresponding field identifier as "id" based on the first mapping relationship. The computing device can then use this field identifier "id" to determine the field value "Commuting Operations Subclass" corresponding to the field identifier "id" (header name). In other words, the computing device can determine the header name as "Commuting Operations Subclass".

[0174] The following section explains the process by which the computing device determines the header structure based on the header merging rules and the attribute information of multiple headers.

[0175] In one implementation:

[0176] The computing device can determine the hierarchical relationship between multiple headers based on the parent header identifier and the header identifier of the multiple headers.

[0177] The computing device can retrieve multiple merge rules from the header merge rules.

[0178] For any given merge rule, the computing device can determine the target header corresponding to the merge rule from multiple headers based on the merge conditions in the merge rule. The hierarchical information of the target header matches the hierarchical information in the merge conditions.

[0179] The computing device can determine the corresponding header display result based on the header name.

[0180] The computing device can determine the number of columns spanned corresponding to the target header based on the merge action configuration information in the merge rules.

[0181] The computing device can determine the preset number of row spans as the number of row spans corresponding to the target table header. For example, the preset number of row spans can be 1.

[0182] S203: Determine the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies.

[0183] In this embodiment, the computing device can determine the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies.

[0184] The table body structure can indicate the table body display results, table body display attributes, and table headers corresponding to multiple table bodies.

[0185] It should be noted that the table body display attributes can include the number of rows spanned or the option to hide or show tags.

[0186] Additionally, it should be noted that in one implementation, the table body merging rule may also include a second mapping relationship. The second mapping relationship indicates the mapping between the field identifiers of various attribute information of the table body in the original business data and the field identifiers of the table body attribute information that the table component retrieval engine can use. For example, for the field identifier "rank" of the table body attribute information, the computing device running the table component retrieval engine can determine the corresponding field identifier as "rankfield" based on the first mapping relationship. The computing device can then use this field identifier "rank" to determine that the field value "12" corresponding to this attribute information field identifier is the field value corresponding to the field identifier "rankfield" (ranking information). In other words, the computing device can determine that the ranking information is "12".

[0187] The following section explains the process by which the computing device determines the table structure based on the table merging rules, the table header structure, and the attribute information of multiple table bodies.

[0188] In one implementation:

[0189] The table body's attribute information includes the table body name, ranking information, prefix information, and grouping attributes.

[0190] The computing device can group multiple table bodies according to their grouping attributes and header structures, obtain multiple headers corresponding to the groups, and determine the headers as the headers corresponding to the table bodies included in the groups; wherein, the header structure includes the headers; and the grouping attributes of the table bodies included in the groups corresponding to the headers are consistent with the headers.

[0191] The first table body can be any one of multiple table bodies.

[0192] The computing device can determine the display attributes of the first table body based on the ranking information of the first table body.

[0193] The computing device can generate the ranking display result corresponding to the first table body based on the template information, the ranking information of the first table body, and the prefix information of the first table body.

[0194] The computing device can determine the display result of the first table body based on the table body name and the ranking display result corresponding to the first table body.

[0195] S204: Render the table header and body structures to obtain the table component.

[0196] In this embodiment, the computing device can render the table header structure and table body structure to obtain a table component.

[0197] In one implementation, the computing device can send a table component to the terminal device. The terminal device can then display the table component.

[0198] The beneficial effects of this embodiment are as follows: In this embodiment, the computing device can acquire raw business data, which includes attribute information of multiple table headers and attribute information of multiple table bodies. The computing device can determine the table header structure based on the table header merging rules and the attribute information of multiple table headers. The table header structure indicates the hierarchical relationship between multiple table headers, the display result of each table header, and the display attributes of each table header. The table header display attributes include the number of rows spanned and the number of columns spanned. The computing device can determine the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies. The table body structure indicates the display result of multiple table bodies, the display attributes of the table bodies, and the table headers corresponding to the table bodies. The table body display attributes include the number of rows spanned or a hidden / show flag. The computing device can perform rendering processing on the table header structure and the table body structure to obtain table components. By utilizing pre-configured header and body merging rules to process the original business data, the header and body structures are obtained, respectively. These are then rendered to create table components. This eliminates the need for manual analysis of the original business data and writing corresponding conversion code based on individual expertise, lowering the barrier to entry for obtaining table components and improving efficiency. Furthermore, compared to merging data during rendering, which leads to low rendering efficiency, this embodiment of the application merges data before rendering, further improving rendering efficiency.

[0199] The following describes one implementation of "S202: Determine the header structure based on the header merging rules and the attribute information of multiple headers" in Example 1, through Method Example 2.

[0200] Figure 3a This is a flowchart illustrating a second embodiment of a method for obtaining a table component provided in this application. See also... Figure 3a The method specifically includes the following steps:

[0201] S301: Determine the hierarchical relationship between multiple table headers based on the parent header identifier and the header identifier of the multiple table headers.

[0202] In this embodiment, the attribute information of the table header includes the table header name, table header identifier, parent table header identifier, and hierarchy information.

[0203] The computing device can determine the hierarchical relationship between multiple table headers based on the parent header identifier and the header identifiers of the multiple table headers. This hierarchical relationship between the multiple table headers constitutes the table header structure.

[0204] In one implementation:

[0205] The first header can be any one of multiple headers.

[0206] In a computing device, if there is a header identifier for one of the multiple headers that matches the parent header identifier of the first header, then that header is identified as the parent header of the first header.

[0207] The computing device can determine the hierarchical relationship between multiple headers based on the parent header of at least one header.

[0208] S302: Retrieve multiple merge rules from the header merge rules.

[0209] In this embodiment, the header merging rule may include multiple merging rules. In one implementation, the multiple merging rules may include a root-level merging rule, at least one category-level merging rule, and a leaf node non-merging rule.

[0210] The merging rules can include merging conditions. These conditions can include hierarchical information. It should be noted that, in one implementation, the hierarchical information in the merging conditions can include the field identifier of the triggering field and the field value of the triggering field. The field identifier can be a hierarchical identifier (level).

[0211] In addition, merge rules may also include merge action rules. These merge action rules may include the target merge type.

[0212] In addition, merge rules can also include display rules.

[0213] The display rules may include a preset number of rows to span. In one implementation, the display rules may also include the field identifier corresponding to the table header display result—the table header name. In another implementation, the display rules may also include a method for calculating the number of columns to span.

[0214] S303: For any merge rule, determine the target header corresponding to the merge rule from multiple headers based on the merge conditions in the merge rule.

[0215] In this embodiment, for any merge rule, the computing device can determine the target header corresponding to the merge rule from multiple headers based on the merge conditions in the merge rule.

[0216] It should be noted that the hierarchical information in the target table header matches the hierarchical information in the merge conditions.

[0217] For example, for a root-level merge rule, the level information in the merge condition is "level 0". The attribute information of a table header can include the following: header name is "technology family", header code is "F_1", parent code is "null", and level is "0". The computing device can determine that this table header is the target table header corresponding to the root-level merge rule based on whether its level information matches the level information in the merge condition.

[0218] For another example, regarding the rule of not merging leaf nodes, the level information in the merging condition of this rule is "level 2". The attribute information of a table header can include the following: header name is "power subclass", header code is "SC_1", parent header code is "C-1", and level information is "2". The computing device can determine that this table header is the target table header corresponding to the rule of not merging leaf nodes based on whether the level information of this table header matches the level information in the merging condition.

[0219] For another example, consider a category-level merging rule where the merging condition specifies "level 2". A table header's attributes can include: header name "Hardware Class", header code "C_1", parent header code "F-1", and level "1". The computing device can determine that this header is the target header for the leaf node non-merging rule based on whether its level information matches the level information in the merging condition.

[0220] S304: Determine the header display result corresponding to the target header based on the header name.

[0221] In this embodiment, the computing device can obtain the header name of the target header. It should be noted that the display rules may also include the field identifier corresponding to the header display result—the header name field identifier. The computing device can obtain the header name of the target header (the field value corresponding to the header name field identifier) ​​based on the header name field identifier.

[0222] The computing device can determine the header display result corresponding to the target header based on the header name. In one implementation, the computing device can directly determine the header name as the header display result corresponding to the target header.

[0223] S305: Determine the number of columns spanned corresponding to the target header based on the merge action configuration information in the merge rules.

[0224] In this embodiment, the computing device can determine the number of columns spanned corresponding to the target header based on the merge action configuration information in the merge rules.

[0225] The merge action configuration information may include the target merge type.

[0226] It should be noted that the target merge type is either a no-merge type or a spanAllDescendants type. It should also be noted that the spanAllDescendants type can also be called a sub-header merge type or a subset merge type; this application embodiment does not impose such limitations.

[0227] In one implementation:

[0228] The computing device can determine the preset number of column spans as the number of column spans corresponding to the target table header when the target merge type in the merge action configuration information is set to "no merge". For example, the preset number of column spans can be 1.

[0229] In one implementation:

[0230] When the target merge type in the merge action configuration information is a cross-child node merge type, the computing device can determine the set of table headers corresponding to the target table header based on the table header identifiers of multiple table headers and the parent table header identifiers of multiple table headers.

[0231] The header set includes multiple candidate headers.

[0232] It should be noted that the target header is either the direct parent header or the indirect parent header of the candidate header.

[0233] The computing device can determine multiple selected headers from a pool of candidate headers based on their hierarchical information. It should be noted that when the header merging rules include multiple merging rules, which may include a root-level merging rule, a category-level merging rule, and a rule that leaf nodes are not merged, the target header corresponding to the category-level merging rule is the direct parent header of each selected header. In other words, each selected header is a direct child header of the target header.

[0234] The computing device can determine the total number of selected headers as the number of columns spanned by the target header.

[0235] The following describes the process by which the computing device determines multiple selected headers from multiple candidate headers based on the hierarchical information of each candidate header.

[0236] In one implementation:

[0237] For any candidate header, the computing device can determine whether the candidate header is a leaf header based on its hierarchical information. In one implementation, the computing device can determine the highest level information from multiple headers and designate the header corresponding to the highest level information as a leaf header.

[0238] The computing device can determine that a candidate header is a leaf header, and then select the candidate header as the selected header.

[0239] The following describes the process by which a computing device determines the set of headers (including multiple candidate headers) corresponding to a target header based on the header identifiers of multiple headers and the parent header identifiers of multiple headers.

[0240] In one implementation:

[0241] For any given header, the computing device can determine whether its parent header identifier matches the header identifier of the target header. If the computing device determines that the parent header identifier matches the header identifier of the target header, it will select that header as a candidate header. It should be noted that the target header is the direct parent header of the candidate header.

[0242] For any given header, the computing device can determine whether its parent header identifier matches the header identifier of the candidate header. If the computing device determines that the parent header identifier matches the header identifier of the candidate header, it will select that header as a candidate header. It should be noted that the target header is the indirect parent header of the candidate header.

[0243] S306: Set the preset number of row spans to the number of row spans corresponding to the target header.

[0244] In this embodiment, the computing device can determine the preset number of row spans as the number of row spans corresponding to the target table header. For example, the preset number of row spans can be 1.

[0245] In another implementation, the computing device may also determine that the header structure includes duplicate detection information. This duplicate detection information indicates whether duplicate headers are detected.

[0246] In one implementation, the computing device can further determine that the table body structure includes table header sorting information. This header sorting information indicates whether the order of the multiple table headers within the original business data is preserved.

[0247] For example, Figure 3b This is a schematic diagram of a table header component provided in an embodiment of this application. Figure 3bAs shown, in the header component, the order of multiple headers in the original business data is preserved. There are no duplicate headers in the header component.

[0248] The beneficial effects of this embodiment are as follows: The attribute information of the table header includes the table header name, table header identifier, parent table header identifier, and hierarchy information. In determining the table header structure: The computing device can determine the hierarchy relationship between multiple table headers based on the parent table header identifiers and the table header identifiers of multiple table headers. The computing device can obtain multiple merging rules from the table header merging rules. For any merging rule, the computing device can determine the target table header corresponding to the merging rule from multiple table headers based on the merging conditions in the merging rule; the hierarchy information of the target table header matches the hierarchy information in the merging conditions. The computing device can determine the table header display result corresponding to the target table header based on the table header name. The computing device can determine the number of columns spanned by the target table header based on the merging action configuration information in the merging rule. The computing device can determine the number of rows spanned by the preset number of rows spanned as the number of rows spanned by the target table header. By processing the attribute information of multiple table headers using the above-described method of utilizing table header merging rules, the table header structure can be constructed. This improves the efficiency and accuracy of the computing device in obtaining the table header structure.

[0249] The following describes one implementation of "S203: Determine the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies" in Example 1, through Method Example 3.

[0250] Figure 4a This is a flowchart illustrating a method for obtaining a table component according to an embodiment of this application, specifically embodiment three. See also... Figure 4a The method specifically includes the following steps:

[0251] S401: Based on the grouping attributes of multiple table bodies and the table header structure, group multiple table bodies to obtain groups corresponding to multiple table headers.

[0252] In this embodiment, the header structure can indicate the hierarchical relationship between multiple headers. That is, the header belongs to the header structure.

[0253] The computing device can group multiple table bodies according to their grouping attributes and header structures to obtain groups corresponding to multiple headers.

[0254] It should be noted that the grouping attributes of the table body included in the group corresponding to the table header are consistent with the header identifier of the table header. For example, the grouping attribute can be subclass. It should also be noted that this table header is a leaf header.

[0255] S402: For any group corresponding to a header, the header is determined to be the header corresponding to the body of the group.

[0256] In this embodiment, for any group corresponding to a header, the header is determined to be the header corresponding to the table body included in the group.

[0257] S403: Determine the table body display attributes of the first table body based on the ranking information of the first table body.

[0258] In this embodiment, the first table body is any one of a plurality of table bodies.

[0259] The computing device can determine the display attributes of the first table body based on the ranking information of the first table body.

[0260] The following describes the process by which the computing device determines the display attributes of the first table body based on the ranking information of the first table body.

[0261] In one implementation:

[0262] The computing device can determine whether the ranking information of the first table body is within a numerical range. For example, the ranking information of the first table body can be "1-2". If the ranking information of the first table body is "1-2", the computing device can determine that the ranking information of the first table body is within a numerical range. As another example, the ranking information of the first table body can be "5". If the ranking information of the first table body is "5", the computing device can determine that the ranking information of the first table body is not within a numerical range.

[0263] The computing device can expand the first table body based on the ranking information, once it determines that the ranking information is within a numerical range, to obtain at least one expanded table body. For example, the computing device can expand the first table body based on the ranking information "1-2" to obtain one expanded table body.

[0264] The computing device can determine the number of row spans based on at least one extended table body and a first table body. Understandably, the computing device can determine the number of row spans by summing the number of at least one extended table body and the number of the first table body. It should also be noted that, in one implementation, the computing device can determine the number of row spans by the number of values ​​corresponding to the ranking information. For example, the computing device can determine that the number of values ​​corresponding to the ranking information "1-2" is 2. The computing device can then determine 2 as the number of row spans.

[0265] The computing device can determine that the display attributes of the first table body include the number of rows spanned, and determine that the display attributes of the extended table body include hiding the display markers.

[0266] In addition, if the computing device determines that the ranking information of the first table body is not within a numerical range, it can determine whether there is at least one target table body in the group to which the first table body belongs.

[0267] It should be noted that in one implementation, the grouping attribute of the first table body is consistent with the grouping attribute of the target table body, and the displayed ranking result (formattedrank) of the first table body is consistent with the displayed ranking result of the target table body. For example, when the grouping attribute is a subclass, the subclass of the first table body is consistent with the subclass of the target table body, and the displayed ranking result of the first table body is consistent with the displayed ranking result of the target table body.

[0268] In one implementation, the grouping attribute of the first table body is consistent with the grouping attribute of the target table body, and the ranking information of the first table body is consistent with the ranking information of the target table body. For example, when the grouping attribute is a subclass, the subclass of the first table body is consistent with the subclass of the target table body, and the ranking information of the first table body is consistent with the ranking information of the target table body.

[0269] Additionally, it should be noted that the first table body and at least one target table body are table bodies with consecutive sorting numbers. In one implementation, the first table body and at least one target table body are table bodies with consecutive sorting numbers, and the sorting number of the target table body is greater than that of the first table body.

[0270] It should be noted that the sorting sequence number is obtained by sorting the business data of multiple tables included in the group based on the ranking information of the business data of the table body in the group to which the first table body belongs.

[0271] The computing device can determine the number of row spans based on the at least one target table body and the first table body, provided that at least one target table body exists. Understandably, the computing device can determine the number of row spans by summing the number of at least one target table body with the number of the first table body.

[0272] The computing device can determine the display attributes of the first table body, including the number of rows spanned, and determine the display attributes of the target table body, including the hiding of display markers.

[0273] S404: Generate the ranking display result corresponding to the first table body based on the template information, the ranking information of the first table body, and the prefix information of the first table body.

[0274] In this embodiment, the computing device can generate the ranking display result corresponding to the first table body based on the template information, the ranking information of the first table body, and the prefix information of the first table body.

[0275] In one implementation:

[0276] Template information may include first template information and second template information.

[0277] For example, the first template information could be "P{{prefix}}{{start}}-P{{prefix}}{{end}}". As another example, the first template information could be "{{prefix}}{{start}}-{{prefix}}{{end}}".

[0278] For example, the second template information could be "P{{prefix}}{{value}}". As another example, the second template information could be "{{prefix}}{{value}}".

[0279] When the ranking information in the first table body is a numerical range, the computing device can generate the ranking display result corresponding to the first table body based on the first template information, the ranking information of the first table body, and the prefix information. In one implementation, the ranking information may include a starting value and an ending value. The computing device can fill the starting value, the ending value, and the prefix information into the first template information to obtain the ranking display result. For example, if the ranking information of the first table body is "1-3" and the prefix information is "A", the ranking display result corresponding to the first table body can be "PA1-PA3". As another example, if the ranking information of the first table body is "1-3" and the prefix information is "A", the ranking display result corresponding to the first table body can be "A1-A3".

[0280] If the ranking information in the first table body is not within a numerical range, the computing device can generate the ranking display result corresponding to the first table body based on the second template information, the ranking information of the first table body, and the prefix information. In one implementation, the computing device can fill the ranking information and prefix information into the first template information to obtain the ranking display result. For example, if the ranking information of the first table body is "2" and the prefix information is "O", the ranking display result corresponding to the first table body can be "PO2". As another example, if the ranking information of the first table body is "2" and the prefix information is "O", the ranking display result corresponding to the first table body can be "O2".

[0281] S405: Determine the display result of the first table body based on the table body name and the ranking display result corresponding to the first table body.

[0282] In this embodiment, the computing device can determine the display result of the first table body based on the table body name and the ranking display result corresponding to the first table body.

[0283] In another implementation, the computing device may further determine that the table body structure includes a second display mode. This second display mode is a grouped display mode. It should be noted that a grouped display mode refers to the aggregation of table bodies belonging to the same group. In other words, table bodies with the same grouping attributes are aggregated for display.

[0284] In one implementation, the computing device may further determine that the table body structure includes second sorting information. The second sorting information indicates whether the multiple table bodies are sorted based on ranking information. In one implementation, the second sorting information indicates that the multiple table bodies are sorted in ascending order based on ranking information.

[0285] In one implementation, the computing device may further determine that the table body structure includes second visual separation information. This second visual separation information indicates whether visual separation lines exist between groups corresponding to each table header.

[0286] For example, Figure 4b This is a schematic diagram of a table body component in a table component provided in an embodiment of this application. For example... Figure 4b As shown, there are visual dividing lines in the table body component, table bodies in the same group are displayed together, and multiple table bodies are sorted based on ranking information.

[0287] The beneficial effects of this embodiment are as follows: In this embodiment, the attribute information of the table body includes the table body name, ranking information, prefix information, and grouping attributes. The computing device can group multiple table bodies according to their grouping attributes and header structure to obtain multiple groups corresponding to headers; wherein, the header structure includes a header; the grouping attributes of the table bodies included in the group corresponding to the header are consistent with the header identifier of the header. For any group corresponding to a header, the computing device can determine the header as the header corresponding to the table body included in the group. The computing device can determine the table body display attributes of the first table body according to its ranking information; the first table body is any one of multiple table bodies. The computing device can generate the ranking display result corresponding to the first table body according to the template information, the ranking information of the first table body, and the prefix information of the first table body. The computing device can determine the table body display result of the first table body according to its table body name and the ranking display result corresponding to the first table body. By processing the attribute information of multiple table bodies using the above-described table body merging rules, the table body structure can be constructed. This improves the efficiency and accuracy of the computing device in obtaining the table body structure, thereby improving the efficiency of the computing device in obtaining table components.

[0288] The computing device can run a table component retrieval engine. It should be noted that, in one implementation, the computing device can obtain the code files corresponding to the table component retrieval engine by acquiring the Node Package Manager (npm) package. In another implementation, the computing device can obtain the code files corresponding to the table component retrieval engine by acquiring a script.

[0289] Terminal devices can run front-end rendering components.

[0290] The following section explains the functions of the front-end rendering component and the table component's engine.

[0291] Figure 5 This is a schematic diagram of a front-end rendering component and a table component acquisition engine provided in an embodiment of this application.

[0292] like Figure 5 As shown, the table component acquisition engine can include a configuration layer, a core engine layer, an adaptation rendering layer, and a data and integration layer.

[0293] The configuration layer is used to manage header merging rules and body merging rules.

[0294] The core engine layer includes a configuration parser, a structure builder, and a data binder. The configuration parser retrieves the header and body configuration rules. The structure builder determines the header structure based on the header merging rules and attribute information from multiple headers. The data binder determines the body structure based on the body merging rules, the header structure, and attribute information from multiple body sections.

[0295] The rendering layer is adapted, including the view renderer. The view renderer is used to render the table header and body structures to obtain table components. It's important to note that the view renderer includes drivers for different underlying user interface libraries. For any given underlying user interface library, its driver can convert the common table header and body structures into table components (also called table component instances or user interface table component instances). These table components correspond to the underlying user interface library.

[0296] The data and integration layer includes a data interface (software interface) and an integration interface (software interface). The data interface receives raw business data. The integration interface receives processing requests from terminal devices. The integration interface also sends form components to terminal devices.

[0297] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0298] Figure 6 This is a schematic diagram of a device for acquiring a table component, provided in an embodiment of this application. Figure 6 As shown, the table component acquisition device 60 includes an acquisition module 61 and a processing module 62.

[0299] The acquisition module 61 is used to acquire raw business data; wherein, the raw business data includes attribute information of multiple table headers and attribute information of multiple table bodies;

[0300] Processing module 62 is used to determine the header structure based on the header merging rules and the attribute information of multiple headers; wherein, the header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header; the header display attributes include the number of rows spanned and the number of columns spanned.

[0301] The processing module 62 is also used to determine the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies; wherein, the table body structure indicates the table body display results, table body display attributes, and the table header corresponding to the table body of multiple table bodies; the table body display attributes include the number of rows spanned or the hidden display flag;

[0302] The processing module 62 is also used to render the table header structure and table body structure to obtain the table component.

[0303] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0304] In one implementation, the attribute information of the table header includes the table header name, table header identifier, parent table header identifier, and hierarchy information; the processing module 62 is specifically used for:

[0305] Determine the hierarchical relationship between multiple table headers based on the parent header identifier and the header identifier of multiple table headers;

[0306] Retrieve multiple merge rules from the header merge rules;

[0307] For any given merge rule, the target table header corresponding to the merge rule is determined from multiple table headers based on the merge conditions in the merge rule; the hierarchical information of the target table header is matched with the hierarchical information in the merge conditions.

[0308] Based on the header name, determine the header display result corresponding to the target header;

[0309] Based on the merge action configuration information in the merge rules, determine the number of columns spanned corresponding to the target table header;

[0310] Set the preset row span number to the row span number corresponding to the target table header.

[0311] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0312] In one implementation, processing module 62 is specifically used for:

[0313] When the target merge type in the merge action configuration information is cross-child node merge, the header set corresponding to the target header is determined based on the header identifiers of multiple headers and the parent header identifiers of multiple headers; the header set includes multiple candidate headers; the target header is the direct parent header or indirect parent header of the candidate headers;

[0314] Based on the hierarchical information of each candidate header, determine multiple selected headers from the multiple candidate headers;

[0315] The total number of selected headers is set as the number of columns spanned by the target header.

[0316] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0317] In one implementation, processing module 62 is specifically used for:

[0318] For any candidate header, determine whether the candidate header is a leaf header based on the hierarchy information of the candidate header;

[0319] If the candidate header is determined to be a leaf header, then the candidate header is selected.

[0320] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0321] In one implementation, processing module 62 is specifically used for:

[0322] If the target merge type in the merge action configuration information is "no merge", the preset number of columns to be spanned will be set to the number of columns to be spanned corresponding to the target table header.

[0323] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0324] In one implementation, the table body's attribute information includes the table body name, ranking information, prefix information, and grouping attributes; the processing module 62 is specifically used for:

[0325] Based on the grouping attributes of multiple table bodies and the table header structure, multiple table bodies are grouped to obtain multiple groups corresponding to table headers; wherein, the table header structure includes the table header; the grouping attributes of the table bodies included in the group corresponding to the table header are consistent with the table header identifier;

[0326] For any group corresponding to a header, the header is defined as the header corresponding to the table body included in the group;

[0327] Based on the ranking information of the first table body, determine the table body display attributes of the first table body; the first table body can be any one of multiple table bodies;

[0328] Based on the template information, the ranking information of the first table body, and the prefix information of the first table body, generate the ranking display result corresponding to the first table body;

[0329] Based on the table body name of the first table body and the ranking display result corresponding to the first table body, determine the table body display result of the first table body.

[0330] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0331] In one implementation, processing module 62 is specifically used for:

[0332] Determine whether the ranking information in the first table body is within a numerical range;

[0333] If the ranking information of the first table body is determined to be within a numerical range, the first table body is expanded according to the ranking information to obtain at least one expanded table body.

[0334] The number of rows spanned is determined based on at least one extended table body and the first table body;

[0335] The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the extended table body are determined to include the hiding of the display marker.

[0336] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0337] In one implementation, the processing module 62 is further configured to:

[0338] If it is determined that the ranking information of the first table body is not within a numerical range, then it is determined whether there is at least one target table body in the group to which the first table body belongs; wherein, the grouping attribute of the first table body is consistent with the grouping attribute of the target table body, and the ranking information of the first table body is consistent with the ranking information of the target table body; the first table body and at least one target table body are tables with consecutive sorting numbers; the sorting number is obtained by sorting the business data of multiple tables body included in the group according to the ranking information of the business data of the tables body in the group to which the first table body belongs;

[0339] If it is determined that there is at least one target table body, the number of rows spanned is determined based on the at least one target table body and the first table body;

[0340] The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the target table body are determined to include the hiding of display tags.

[0341] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0342] Figure 7 This is a schematic diagram of the structure of another form component acquisition device provided in an embodiment of this application. For example... Figure 7 As shown, the table component acquisition device 70 includes an acquisition module 71 and a control module 72.

[0343] The acquisition module 71 is used to acquire the table component sent by the computing device; the table component is rendered based on the table header structure and table body structure; the table header structure is determined based on the table header merging rules and the attribute information of multiple table headers in the original business data; the table body structure is determined based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies in the original business data; the table header structure indicates the hierarchical relationship between multiple table headers, the table header display result of each table header, and the table header display attributes of each table header; the table header display attributes include the number of rows spanned and the number of columns spanned; the table body structure indicates the table body display result of multiple table bodies, the table body display attributes, and the table header corresponding to the table body; the table body display attributes include the number of rows spanned or a hidden / show flag;

[0344] The control module 72 is used for display processing of the table component.

[0345] The table component acquisition device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0346] Figure 8 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Figure 8 As shown, the computing device 80 includes a processor 81 and a memory 82; wherein the processor 81 is coupled to the memory 82, and the memory 82 is used to store computer instructions; the processor 81 is used to execute the computer instructions to cause the computing device 80 to perform the technical solutions in the aforementioned method embodiments.

[0347] Optionally, the memory 82 can be either independent or integrated with the processor 81. Optionally, when the memory 82 is a device independent of the processor 81, the computing device 80 may further include a bus 83 for connecting the aforementioned devices.

[0348] The processor is used to execute the technical solution in the aforementioned method embodiment, where the execution subject is a computing device. Its implementation principle and technical effect are similar and will not be described again here.

[0349] Figure 9 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Figure 9 As shown, the terminal device 90 includes a processor 91 and a memory 92; wherein the processor 91 is coupled to the memory 92, and the memory 92 is used to store computer instructions; the processor 91 is used to execute the computer instructions to cause the terminal device 90 to perform the technical solutions in the aforementioned method embodiments.

[0350] Optionally, the memory 92 can be either standalone or integrated with the processor 91. Optionally, when the memory 92 is a device independent of the processor 91, the terminal device 90 may further include a bus 93 for connecting the aforementioned devices.

[0351] The processor is used to execute the technical solution in the aforementioned method embodiment, where the execution subject is a terminal device. Its implementation principle and technical effect are similar and will not be described again here.

[0352] This application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the technical solutions provided in the aforementioned method embodiments.

[0353] This application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the technical solutions provided in the aforementioned method embodiments.

[0354] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as volatile memory and non-volatile memory.

[0355] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for obtaining a table component, characterized in that, include: Obtain raw business data; wherein, the raw business data includes attribute information of multiple table headers and attribute information of multiple table bodies; Based on the header merging rules and the attribute information of multiple headers, the header structure is determined; wherein, the header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header; the header display attributes include the number of rows spanned and the number of columns spanned. The table body structure is determined based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies; wherein, the table body structure indicates the table body display results, table body display attributes, and the table header corresponding to the table body of multiple table bodies; the table body display attributes include the number of rows spanned or a hidden / show flag; The table header structure and the table body structure are rendered to obtain a table component.

2. The method according to claim 1, characterized in that, The attribute information of the table header includes the table header name, table header identifier, parent table header identifier, and hierarchy information; The step of determining the header structure based on the header merging rules and the attribute information of multiple headers includes: The hierarchical relationship between the multiple table headers is determined based on the parent header identifier and the header identifier of the multiple table headers. Retrieve multiple merge rules from the header merge rules; For any given merge rule, based on the merge conditions in the merge rule, the target table header corresponding to the merge rule is determined from multiple table headers; the hierarchical information of the target table header is matched with the hierarchical information in the merge conditions. Based on the header name, determine the header display result corresponding to the target header; Based on the merge action configuration information in the merge rules, determine the number of columns spanned corresponding to the target header; The preset number of rows to be spanned is determined to be the number of rows to be spanned corresponding to the target header.

3. The method according to claim 2, characterized in that, The step of determining the number of columns spanned corresponding to the target header based on the merge action configuration information in the merge rule includes: When the target merge type in the merge action configuration information is a cross-child node merge type, the header set corresponding to the target header is determined based on the header identifiers of multiple headers and the parent header identifiers of multiple headers; the header set includes multiple candidate headers; the target header is the direct parent header or indirect parent header of the candidate headers. Based on the hierarchical information of each candidate header, determine multiple selected headers from the multiple candidate headers; The total number of selected headers is determined as the number of columns spanned by the target header.

4. The method according to claim 3, characterized in that, The step of determining multiple selected headers from multiple candidate headers based on the hierarchical information of each candidate header includes: For any candidate header, determine whether the candidate header is a leaf header based on the hierarchy information of the candidate header; If the candidate header is determined to be the leaf header, then the candidate header is determined to be the selected header.

5. The method according to claim 2, characterized in that, The step of determining the number of columns spanned corresponding to the target header based on the merge action configuration information in the merge rule includes: If the target merge type in the merge action configuration information is a non-merge type, the preset number of columns to be spanned will be determined as the number of columns to be spanned corresponding to the target header.

6. The method according to any one of claims 1-5, characterized in that, The attribute information of the table body includes the table body name, ranking information, prefix information, and grouping attributes; The step of determining the table body structure based on the table body merging rules, the table header structure, and the attribute information of multiple table bodies includes: Based on the grouping attributes of multiple table bodies and the table header structure, multiple table bodies are grouped to obtain multiple groups corresponding to table headers; wherein, the table header structure includes the table header; the grouping attributes of the table bodies included in the group corresponding to the table header are consistent with the table header identifier of the table header; For any group corresponding to a header, the header is determined to be the header corresponding to the table body included in the group; Based on the ranking information of the first table body, determine the table body display attributes of the first table body; the first table body is any one of multiple table bodies; Based on the template information, the ranking information of the first table body, and the prefix information of the first table body, generate the ranking display result corresponding to the first table body; Based on the table body name of the first table body and the ranking display result corresponding to the first table body, the table body display result of the first table body is determined.

7. The method according to claim 6, characterized in that, The step of determining the table body display attributes of the first table body based on the ranking information of the first table body includes: Determine whether the ranking information of the first table body is within a numerical range; If the ranking information of the first table body is determined to be within a numerical range, the first table body is expanded according to the ranking information to obtain at least one expanded table body. The number of rows spanned is determined based on at least one of the extended table bodies and the first table body; The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the extended table body are determined to include the hidden display marker.

8. The method according to claim 7, characterized in that, The method further includes: If it is determined that the ranking information of the first table body is not within a numerical range, then it is determined whether there is at least one target table body in the group to which the first table body belongs; wherein, the grouping attribute of the first table body is consistent with the grouping attribute of the target table body, and the ranking information of the first table body is consistent with the ranking information of the target table body; the first table body and at least one target table body are tables with consecutive sorting numbers; the sorting number is obtained by sorting multiple table body business data included in the group according to the ranking information of the table body business data in the group to which the first table body belongs; If it is determined that there is at least one target table body, the number of rows spanned is determined based on the at least one target table body and the first table body; The display attributes of the first table body are determined to include the number of rows spanned, and the display attributes of the target table body are determined to include the hidden display marker.

9. A method for obtaining a table component, characterized in that, Applied to a terminal device, the method includes: The system acquires a table component sent by a computing device. The table component is rendered based on a header structure and a body structure. The header structure is determined based on header merging rules and attribute information of multiple headers in the original business data. The body structure is determined based on body merging rules, the header structure, and attribute information of multiple bodies in the original business data. The header structure indicates the hierarchical relationship between multiple headers, the header display result of each header, and the header display attributes of each header. The header display attributes include the number of rows spanned and the number of columns spanned. The body structure indicates the body display result of multiple bodies, the body display attributes, and the header corresponding to each body. The body display attributes include the number of rows spanned or a hidden / shown flag. The table component is then displayed.

10. A computing device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory is used to store computer-executed instructions; The processor is configured to execute computer execution instructions stored in the memory to implement the method according to any one of claims 1-8.

Images