Intelligent tabular collaborative management method and device

Abstract

The application discloses an intelligent tabular collaborative management method and device, and a server method comprises the following steps: obtaining original business data to be displayed and pre-stored custom style data according to a page processing request sent by a client; the original business data and the pre-stored custom style data are stored separately; the pre-stored custom style data comprises a mapping relationship between each business data identifier, column identifier and specific style; obtaining a current data identifier of the original business data, a current column identifier of a column where the original business data is located, reading data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; and rendering the original business data according to the data style and the column style, and sending the rendered original business data to the client. According to the application, while supporting operation on massive data, it is ensured that the custom style defined by a user is consistent across views, and the data visualization efficiency and operation experience in the big data scene of a manufacturing enterprise are significantly improved.

Description

Technical Field

[0001] This application relates to the fields of computer and manufacturing digitalization technology, and in particular to an intelligent tabular collaborative management method and device. Background Technology

[0002] In the process of digital management in manufacturing enterprises, especially in scenarios involving high concurrency and large data volumes in production reporting and piece-rate wage calculation, users need to quickly identify key information from massive amounts of production data. Existing management systems generally have pre-defined data display styles, making it impossible for users to customize data styles, such as bolding, underlining, color switching, and font size adjustment.

[0003] In related technologies, the management system currently used based on traditional Web technology architecture has a fixed table rendering style pre-written on the front-end page, and the back-end database is only responsible for storing and returning pure business data content; the front-end components perform a unified visual presentation of the returned data according to the preset template.

[0004] However, table rendering relies heavily on preset styles, making it impossible to provide differentiated visual displays for different data based on user needs, leading to significant discomfort among frontline staff. Secondly, existing table components lack flexible, personalized configuration interfaces, making it difficult to apply special styles to different cells within the same table, thus limiting the granularity of data visualization. Finally, the backend database only records the data content itself, failing to establish a mechanism for associating data with style attributes. Summary of the Invention

[0005] This application provides an intelligent tabular collaborative management method and apparatus. To provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. This summary is not intended as a general commentary, nor is it intended to identify key / important components or describe the scope of protection of these embodiments. Its sole purpose is to present some concepts in a simple form as a prelude to the detailed description that follows.

[0006] In a first aspect, embodiments of this application provide an intelligent tabular collaborative management method, applied to a server, the method comprising: Based on the page processing request sent by the client, the original business data to be displayed in the table and the pre-stored custom style data are obtained. The original business data and the pre-stored custom style data are stored separately. The pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier and specific style. Obtain the current data identifier and the current column identifier of the original business data, and read the data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; Based on the data style and column style, render the original business data and send the rendered original business data to the client.

[0007] Optionally, render the original business data according to the data style and column style, including: When a page processing request is used to request the server to perform pagination switching, data filtering, or sorting operations, check whether the data style and column style are empty values. If neither the data style nor the column style is null, the data style will be applied to the original business data for style rendering first; or, If the data style is null and the column style is not null, then the column style will be applied to the original business data for style rendering; or, If both the data style and column style are empty, the preset default style will be applied to the original business data for style rendering.

[0008] Optionally, the mapping relationship can be generated by following these steps: Receive a style setting request sent by the client. The style setting request includes the target business data identifier, the target column identifier, and the target custom style corresponding to the target business data identifier and / or the target column identifier. Construct a target mapping key based on the target business data identifier and / or target column identifier; In the storage structure of custom style data, establish and store the mapping relationship between the target mapping key and the target custom style; When the target custom style is the target column style, it will take effect in the same column of each page of the table.

[0009] Optionally, data styles can be applied to the original business data for style rendering first, including: Parse the data style to obtain the business data validation rules and data style attributes of each cell containing the original business data; The original business data is verified using the business data verification rules for each cell, and the data verification results are obtained. If the data validation result indicates that the original business data has passed validation, the data style attributes of each cell are applied to the original business data; specifically, after switching pagination, data filtering, or sorting operations, the data style attributes of each cell take effect along with the business data associated with it; or, If the data validation result indicates that the original business data validation failed, check whether the column style corresponding to each cell exists. If a column style exists, it will be applied to the original business data that fails validation; if a column style does not exist, the default style will be applied to the original business data that fails validation.

[0010] Optionally, column styles can be applied to the original business data for style rendering, including: Parse the column style to obtain visual formatting attributes applicable to the entire column; Retrieve the table identifier, pagination parameters, and filter conditions carried in the page processing request; Determine the range of the data view to be rendered based on the table identifier, pagination parameters, and filtering conditions; Locate all target data cells within the data view range corresponding to the current column identifier to obtain the first target cell set; Determine if the first target cell set contains any cells that are pre-marked and forced to be rendered as data styles; If they exist, remove the cells that are forcibly rendered as data styles from the first target cell set to form the second target cell set; apply the visual formatting attributes applicable to the entire column to the original business data of each cell in the second target cell set; If it does not exist, the visual formatting attributes applicable to the entire column will be applied to the raw business data of each cell in the first target cell set.

[0011] Optionally, establish and store the mapping relationship between the target mapping key and the target custom style, including: Load the node tree data structure used to store the mapping relationship as the storage structure for the custom style data; Resolve the target mapping key into the target node path; The node tree data structure used to store mapping relationships is traversed and searched to determine whether a corresponding historical style storage node exists at the end of the target node path, and the judgment result is obtained. The node tree data structure takes the data table identifier as the root node and the column identifier and / or business data identifier as the child node path, forming a hierarchical index structure. Based on the judgment result and the target custom style, update the node tree data structure to establish and store the mapping relationship between the target mapping key and the target custom style.

[0012] Optionally, based on the judgment result and the target custom style, update the node tree data structure, including: If the judgment result indicates that there is no corresponding historical style storage node, then in the node tree data structure, a new style storage node is created along the target node path, and the target custom style is stored as the attribute value of the new node; or, If the judgment result indicates that a corresponding historical style storage node exists, then the original historical attribute values ​​of the historical style storage node are overwritten and updated with the target custom style; Generate an updated node tree data structure.

[0013] Optionally, based on the page processing request sent by the client, obtain the original business data to be displayed in the table and the pre-stored custom style data, including: Parse the page processing request to obtain the table's data table identifier, the pagination information of the current request, data filtering conditions, and sorting rules; Based on the data table identifier, pagination information, data filtering conditions and sorting rules, execute a query from the business database to obtain the original business data corresponding to the currently requested page view; Extract the unique business data identifier from each line of business data record in the original business data; Based on the data table identifier, locate the target root node of the node tree data structure that stores the mapping relationship of the table; Obtain all column identifiers involved in the page processing request to obtain the set of column identifiers to be processed; Based on the unique business data identifier, the target root node, and the set of column identifiers to be processed, pre-stored custom style data is generated.

[0014] Optionally, based on the unique business data identifier, the target root node, and the set of column identifiers to be processed, pre-stored custom-style data is generated, including: Based on the target root node, the column styles corresponding to all columns in the column identifier set to be processed are read in batches from the node tree data structure to form the style base layer; Combine the unique business data identifier with each column identifier in the set of column identifiers to be processed to obtain the query key for all cells on the current page; Based on the query key, the corresponding data style is queried and obtained from the node tree data structure to form an overlay layer; Use the data style in the overlay layer and the column style in the style base layer as the current specific style; The unique business data identifier, the set of column identifiers to be processed, and the current specific style are mapped and combined and cached to obtain pre-stored custom style data.

[0015] Secondly, embodiments of this application provide an intelligent tabular collaborative management device, the device comprising: The parameter acquisition module is used to obtain the original business data to be displayed in the table and the pre-stored custom style data based on the page processing request sent by the client. The original business data and the pre-stored custom style data are stored separately. The pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier and specific style. The style query module is used to obtain the current data identifier and the current column identifier of the original business data, and read the data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; The style rendering module is used to render the original business data according to the data style and column style, and then send the rendered original business data to the client.

[0016] The technical solutions provided in this application embodiment may include the following beneficial effects: In this embodiment, on the one hand, the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier, and specific style. The corresponding data style or column style can be retrieved in real time based on the current data identifier and column identifier for rendering. This mapping relationship is customized by the user based on their own needs, enabling differentiated visual displays for different table data. Secondly, by establishing the mapping relationship, it becomes technically possible to set special styles for any specific cell, thus breaking through the limitations of traditional one-size-fits-all rendering and achieving a higher level of precision in data visualization.

[0017] On the other hand, a node tree data structure is used to store style mapping relationships. This structure, rooted at the table identifier and using column and business data identifiers as paths, forms a global style index. This establishes a relational storage mechanism between data and style attributes, accurately expressing the complex relationships between specific columns, rows, and styles in a specific data table. When rendering data, the node tree can be efficiently traversed based on all combinations of business data identifiers and column identifiers for the current page, allowing for batch retrieval and rendering of the corresponding styles, thus improving rendering accuracy and efficiency.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] Figure 1 This is a schematic diagram of the method flow of an intelligent tabular collaborative management method provided in an embodiment of this application; Figure 2 This is a schematic diagram illustrating a mapping relationship generation process provided in an embodiment of this application; Figure 3 This is a structural diagram of a node tree of this style provided in an embodiment of this application; Figure 4 This is a schematic diagram illustrating the process of acquiring raw business data and pre-stored custom style data according to an embodiment of this application. Figure 5 This is a UI interface diagram for an application scenario provided in an embodiment of this application; Figure 6 This is a structural diagram of a tree structure in an application scenario provided by an embodiment of this application; Figure 7 This is a schematic diagram illustrating the rendering process of raw business data provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of an intelligent tabular collaborative management device provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0021] The following description and accompanying drawings fully illustrate specific embodiments of this application to enable those skilled in the art to practice them.

[0022] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0023] In the following description, when referring to the accompanying drawings, the same numbers in different drawings denote the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0024] In the description of this application, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0025] Currently, in management systems based on traditional Web technology architecture, the front-end pages have pre-written fixed table rendering styles, and the back-end database is only responsible for storing and returning pure business data content; the front-end components perform a unified visual presentation of the returned data based on preset templates.

[0026] The table rendering relies heavily on preset styles, making it impossible to provide differentiated visual displays for different data based on user needs, leading to significant difficulties for frontline staff. Secondly, the existing table components lack flexible, personalized configuration interfaces, making it difficult to apply special styles to different cells within the same table, thus limiting the granularity of data visualization. Finally, the backend database only records the data content itself, failing to establish a mechanism for associating data with style attributes.

[0027] To address the aforementioned issues, this application provides an intelligent tabular collaborative management method and apparatus to resolve the problems existing in the related technologies. In the embodiments of this application, on one hand, pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier, and specific style. The corresponding data style or column style can be retrieved in real time based on the current data identifier and column identifier for rendering. This mapping relationship is customized by the user based on their own needs, enabling differentiated visual displays for different tabular data. Secondly, by establishing the mapping relationship, it becomes technically possible to set special styles for any specific cell, thereby breaking through the limitations of traditional one-size-fits-all rendering and achieving a higher level of precision in data visualization.

[0028] On the other hand, a node tree data structure is used to store style mapping relationships. This structure, rooted at the data table identifier and using column and business data identifiers as paths, forms a global style index, thus establishing an associative storage mechanism between data and style attributes. This mechanism can accurately express the complex relationships between specific columns, rows, and styles in a specific data table. When data needs to be rendered, the node tree can be efficiently traversed based on all combinations of business data identifiers and column identifiers on the current page, and the corresponding styles can be retrieved in batches for rendering, thereby improving rendering accuracy and efficiency. A detailed explanation using an exemplary embodiment follows.

[0029] The following will be combined with the appendix Figure 1 - Appendix Figure 7 This application provides a detailed description of the intelligent tabular collaborative management method provided in its embodiments. This method can be implemented using a computer program and can run on an intelligent tabular collaborative management device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application.

[0030] Please see Figure 1 This is a flowchart illustrating an intelligent tabular collaborative management method provided in this application embodiment, applied to the server side. For example... Figure 1 As shown, the method in this application embodiment includes the following steps: S101, based on the page processing request sent by the client, obtain the original business data to be displayed in the table and the pre-stored custom style data; wherein, the original business data and the pre-stored custom style data are stored separately; the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier and specific style; In this context, the client is a software application or browser running on the user's terminal device, used for data interaction with the server and presenting the user interface. Page processing requests are generated by the client and sent to the server. These requests must contain at least the necessary parameters to identify the target data view, such as the identifier of the target table, the requested data pagination information, data filtering conditions, and sorting rules. A table is a logical view container used to organize, display, and manage massive amounts of structured business data in rows and columns. Raw business data is a collection of pure data records obtained from the business database without any style rendering. Each record contains values ​​for several business fields and is the core information entity that the table needs to display, and it is physically separated from visual style information. A business data identifier is a string, number, or code that uniquely and stably identifies a specific business data record within the system. A column identifier is a string or code that uniquely identifies a specific data column (field) within the table. A specific style is a set of formatting instructions that defines the visual presentation characteristics of data cells. Its specific content may include, but is not limited to, CSS properties such as background color, font style, border style, and text color, or their equivalent representations.

[0031] In some embodiments of this application, the specific process of generating the mapping relationship includes: receiving a style setting request sent by a client, the style setting request including a target business data identifier, a target column identifier, and a target custom style corresponding to the target business data identifier and / or the target column identifier; constructing a target mapping key based on the target business data identifier and / or the target column identifier; establishing and storing the mapping relationship between the target mapping key and the target custom style in the storage structure of the custom style data; wherein, when the target custom style is a target column style, it is effective in the same column of each page of the table.

[0032] Specifically, the process of establishing and storing the mapping relationship between the target mapping key and the target custom style includes: loading a node tree data structure for storing the mapping relationship as the storage structure for the custom style data; parsing the target mapping key into a target node path; traversing and searching the node tree data structure for storing the mapping relationship to determine whether a corresponding historical style storage node exists at the end of the target node path, and obtaining the determination result; wherein, the node tree data structure uses the data table identifier as the root node and the column identifier and / or business data identifier as the child node path to form a hierarchical index structure; and updating the node tree data structure according to the determination result and the target custom style to establish and store the mapping relationship between the target mapping key and the target custom style.

[0033] Specifically, the process of updating the node tree data structure based on the judgment result and the target custom style includes: if the judgment result indicates that there is no corresponding historical style storage node, then a new style storage node is created along the target node path in the node tree data structure, and the target custom style is stored as the attribute value of the new node; or, if the judgment result indicates that there is a corresponding historical style storage node, then the original historical attribute value of the historical style storage node is overwritten and updated with the target custom style; and an updated node tree data structure is generated.

[0034] In this embodiment, a node tree data structure is used to store style mapping relationships. The node tree data structure uses the data table identifier as the root and column identifiers and business data identifiers as paths to form a global style index, thus establishing an associative storage mechanism between data and style attributes. This mechanism can accurately express the complex relationship between a specific column, specific row, and specific style in a specific data table. When data needs to be rendered, the node tree can be efficiently traversed based on all combinations of business data identifiers and column identifiers on the current page, and the corresponding styles can be retrieved in batches for rendering, thereby improving rendering accuracy and efficiency.

[0035] For example Figure 2 As shown, Figure 2This is a schematic diagram illustrating the mapping relationship generation process provided in this application. The system receives a style setting request containing a target business data identifier, a target column identifier, and a target custom style, and constructs a target mapping key based on this information. Subsequently, the system loads a node tree data structure for storing the mapping relationship, parses the target mapping key into a target node path, and traverses the node tree to determine whether a corresponding historical style storage node exists at the end of the target node path. Then, different update operations are performed based on the determination result: if no historical style storage node is found, a new style storage node is created along the target node path, and the target custom style is stored as the attribute value of the new node; if a historical style storage node is found, the target custom style is used to overwrite and update the original attribute value of the historical node. Finally, the system generates an updated node tree data structure, completes the establishment and storage of the mapping relationship, and makes the style setting effective.

[0036] In one possible implementation, the user performs any of the following operations in the web front-end interface: Setting Column Styles (Operation A): The user wants to highlight the entire "Quantity of Defective Products" column with a light red background to draw attention. He right-clicks the "Quantity of Defective Products" column header in the front-end table, selects "Set Column Style," chooses "#FFE6E6" (light red) from the color picker, and then clicks Apply. Setting Data Styles (Operation B): While browsing the report, the user notices that the product with ID P20240520007 has a "Production Progress" of only 65%, far below the standard. He selects the cell, clicks the "Highlight" button in the toolbar, and chooses the "Yellow Background + Bold" style to mark it.

[0037] At this point, regardless of whether operation A or B is performed, the front-end JavaScript code will capture the user's intent and construct a style setting request (HTTP POST request), sending it to the server-side style management interface (e.g., POST / api / style / set). The server-side StyleController receives the request, parses it, and constructs the target mapping key based on the request parameters. For column style requests: the mapping key construction rule is {tableId}:{columnId}. After substituting the parameters, the target mapping key is generated: press_workshop_daily:defect_count. For data style requests: the mapping key construction rule is {tableId}:{columnId}:{dataId}. After substituting the parameters, the target mapping key is generated: press_workshop_daily:progress_rate:P20240520007.

[0038] At this point, the server calls the style service to load the style node tree identified as `press_workshop_daily` from memory cache or persistent storage (such as Redis or a database). The structure of this style node tree is as follows: Figure 3 As shown. For the column style key `press_workshop_daily:defect_count`, the path is: root -> `defect_count` column node. For the data style key `press_workshop_daily:progress_rate:P20240520007`, the path is: root -> `progress_rate` column node -> `P20240520007` data node. The server searches the tree along this path.

[0039] For example, when creating a new node: When processing a data style request, the system finds that the data node P20240520007 at the end of the path does not exist. The system creates a new child node named P20240520007 under the `progress_rate` column node. Then, it stores the `targetStyle({backgroundColor:“#FFFFCC”,fontWeight:“bold”})` from the request as the attribute value (`node.style`) of this new node.

[0040] For example, when updating an existing node: Suppose a user later sets a new style (e.g., changes the border to red) for the `progress_rate` column of the same data record (P20240520007). When the system searches, it finds that the data node already exists. The system then updates the node's original `style` attribute value with the new style object.

[0041] Finally, after updating the node tree, the system serializes the latest node tree structure and saves it back to the cache or database. Then, it returns a success response to the client.

[0042] In some embodiments of this application, the specific process of obtaining the original business data to be displayed in a table and the pre-stored custom style data according to the page processing request sent by the client includes: parsing the page processing request to obtain the table's data table identifier, the pagination information of the current request, data filtering conditions, and sorting rules; performing a query from the business database based on the data table identifier, pagination information, data filtering conditions, and sorting rules to obtain the original business data corresponding to the currently requested page view; extracting the unique business data identifier of each row of business data records in the original business data; locating the target root node of the node tree data structure storing the table's mapping relationship based on the data table identifier; obtaining all column identifiers involved in the page processing request to obtain a set of column identifiers to be processed; and generating pre-stored custom style data based on the unique business data identifier, the target root node, and the set of column identifiers to be processed.

[0043] Specifically, the process of generating pre-stored custom style data based on a unique business data identifier, a target root node, and a set of column identifiers to be processed includes: based on the target root node, batch reading the column styles corresponding to all columns in the set of column identifiers to be processed from the node tree data structure to form a style base layer; combining the unique business data identifier with each column identifier to be processed in the set of column identifiers to be processed to obtain the query key for all cells on the current page; based on the query key, querying and obtaining the corresponding data style from the node tree data structure to form an overlay layer; using the data style in the overlay layer and the column style in the style base layer as the current specific style; and mapping and caching the unique business data identifier, the set of column identifiers to be processed, and the current specific style to obtain the pre-stored custom style data.

[0044] In this embodiment, the process ensures that in any paginated, filtered, or sorted data view, the user-preset global column style and the data style following the specific data can be accurately and efficiently obtained and applied. This not only ensures style consistency across views, but also optimizes the retrieval performance of massive style data through the node tree structure, thereby maintaining the system's response speed and rendering accuracy in complex interactive scenarios.

[0045] For example Figure 4 As shown, Figure 4This is a schematic diagram illustrating the process of acquiring raw business data and pre-stored custom style data provided in this application. First, the system receives a page processing request and parses out the data table identifier, pagination information, filtering conditions, and sorting rules. Then, based on these parameters, it queries the business database to retrieve the raw business data corresponding to the current page view and extracts the unique business data identifier for each business record. Simultaneously, based on the data table identifier, the system locates the target root node of the node tree data structure storing the table mapping relationship and obtains all column identifiers involved in the current request. Next, based on the target root node, the system batch reads the column styles corresponding to these columns to form a style base layer. At the same time, it combines the unique business data identifier and column identifier to generate a cell query key and retrieves the corresponding data style to form an overlay layer. Finally, the system merges the overlay layer and the style base layer into the current specific style, maps and combines it with the business data identifier and column identifier, and caches it to obtain the pre-stored custom style data.

[0046] In one possible implementation, the administrator clicks... Figure 5 After the second page or application filtering and sorting, the front end automatically initiates an AJAX request. The request is sent to the server-side interface (such as GET / api / table / data), carrying the following parameters: {"tableId": "wo_live_progress", "page": 2, "pageSize": 5, "filters": [ {"field": "status", "op": "=", "value": "Executing"} ], "sortBy": "planned_end_time", "sortOrder": "asc At this point, the TableDataService on the server side receives the request and extracts tableId(wo_live_progress), page(2), pageSize(5), filters, and sortBy / sortOrder. Based on the above parameters, it assembles the SQL query, and the SQL statement is as follows: SELECT id, work_order_no, product_name, quantity, progress, status, operator, planned_end_time FROM wo_live_progress WHERE status = 'Executing' ORDER BY planned_end_time ASC LIMIT 5 OFFSET 5; Page 2, skip the first 5 records. Execute the query to obtain the 5 original business data records for the current page, as shown in Table 1.

[0047] Table 1

[0048] At this point, the `id` column is extracted from the result set to obtain the unique set of business data identifiers for the current page: [10025, 10028, ...]. Based on `tableId(wo_live_progress)`, the target root node of the style node tree corresponding to this table is loaded (or located) from the style service's memory or cache. Assume this tree structure in memory is as follows... Figure 6 As shown. Parse the request to determine which columns the front-end table needs to render. For example, it might use the default setting of all columns, assuming they are ['work_order_no', 'product_name', 'quantity', 'progress', 'status', 'operator']. This yields a set of column identifiers to be processed.

[0049] At this point, the server now has the following parameters: `uniqueDataIds: [10025, 10028, ...]` (IDs of all rows on the current page), `styleRootNode:` (a pointer to the `wo_live_progress` style tree), and `columnIds: ['work_order_no', 'product_name', 'quantity', 'progress', 'status', 'operator'].` It iterates through `columnIds`, and for each column identifier, finds the corresponding column node under `styleRootNode` and reads its stored column style attributes. For example, from the `progress` column node, it reads `{backgroundColor:'#f0f9ff'}` (global light blue background). From the `status` column node, it reads `{fontWeight:'bold'}` (global bold). Column nodes such as `quantity` and `work_order_no` have no column style attributes and are empty. A column style mapping (style base layer) is generated.

[0050] At this point, perform a Cartesian product between `uniqueDataIds` and `columnIds` to generate the lookup keys for all cells on the current page. For example, for the first row (id=10025): ['wo_live_progress:progress:10025', 'wo_live_progress:status:10025', 'wo_live_progress:quantity:10025', ...]. Using these query keys as paths, perform efficient batch searches in the node tree. For example, if the node pointed to by the path wo_live_progress:progress:10025 exists, its style attribute is {backgroundColor:'#52c41a', color: 'white'} (green background, white text). The node with the path wo_live_progress:status:10025 has no style. The node with the path wo_live_progress:quantity:10025 also has no style. Generate a data style mapping (overlay).

[0051] Finally, the system uses columnStyleBase as a baseline, overlays the styles in dataStyleOverlay onto it, and generates a flat style mapping table that completely corresponds to the current page's data structure, serving as a pre-stored custom style data: { "preStyledData": { "10025": { "progress": {"backgroundColor": "#52c41a", "color": "white"}, "status": {"fontWeight": "bold"} / / From column style }, "10028": { "progress": {"backgroundColor": "#f0f9ff"}, / / From column styles only "status": {"fontWeight": "bold"} / / From column style }, / / ... other lines }}.

[0052] S102, obtain the current data identifier and the current column identifier of the original business data, and read the data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; The current data identifier is a string, value, or code that uniquely and stably identifies a specific business data record within the original business data. The current column identifier is a string or code that uniquely identifies a specific data field (column) within the current view of the table. A data style is a set of visual formatting instructions bound to specific business data identifiers and column identifiers, applied to a single cell or a group of cells. Its effectiveness depends on the specific data instance; when the view position changes due to pagination, filtering, sorting, or other operations, the style moves and takes effect along with its associated data. A column style is a set of visual formatting instructions bound to a specific column identifier, applicable to all data cells in the column corresponding to that identifier. Its effectiveness is independent of the specific data row; the style is consistently applied to the column across all paginations and filtered views of the table.

[0053] In one possible implementation, the server retrieves 10 inventory records from the "Shelf A-01" area based on the user request, serving as the raw business data. Each record contains the following fields: stock_id (primary key), item_code (item code), item_name (item name), quantity (quantity), and alert_level (alert level). The system extracts the stock_id of each record (e.g., STK-1001, STK-1002, ...) as the current data identifier. Simultaneously, it determines the column currently displayed in the view, and its corresponding field name (e.g., quantity, alert_level) serves as the current column identifier. The system already has the following mapping relationship: Column style mapping: alert_level->{"backgroundColor":"#FFF7E6"} (Global: The background of the alert level column is light orange).

[0054] Data style mapping: stock_id:STK-1005, column:quantity->{"color": "#CF1322", "fontWeight": "bold"} (Data style: For the item with inventory ID STK-1005, the "Quantity" cell is marked in bold red). stock_id:STK-1008, column:alert_level->{"backgroundColor": "#FFCCC7"} (Data style: For the item with inventory ID STK-1008, the "Alert Level" cell has a warning red background).

[0055] At this point, when rendering the second row of data (stock_id: STK-1005), the system performs the following read operation: 1. For the quantity column: Combine the current data identifier (STK-1005) with the current column identifier (quantity) to form the query key. Read the data style {"color": "#CF1322", "fontWeight": "bold"} from the mapping relationship.

[0056] 2. For the alert_level column: the same combination of identifiers was used for the query. No special data style was found for STK-1005, but the column style {"backgroundColor": "#FFF7E6"} was found.

[0057] S103 renders the original business data according to the data style and column style, and sends the rendered original business data to the client.

[0058] In some embodiments of this application, the specific process of rendering original business data according to data style and column style includes: when the page processing request is used to request the server to perform page switching, data filtering or sorting operations, determining whether the data style and column style are null values; if the data style and column style are not null values, then the data style is applied to the original business data for style rendering first; or, if the data style is null value and the column style is not null value, then the column style is applied to the original business data for style rendering; or, if both the data style and column style are null values, then the preset default style is applied to the original business data for style rendering.

[0059] Specifically, the process of prioritizing the application of data styles to the original business data for style rendering includes: parsing the data style to obtain the business data validation rules and data style attributes for each cell containing the original business data; validating the original business data using the business data validation rules for each cell to obtain the data validation result; if the data validation result indicates that the original business data has passed validation, applying the data style attributes of each cell to the original business data; wherein, after switching pagination, data filtering, or sorting operations, the data style attributes of each cell take effect along with the business data associated with it; or, if the data validation result indicates that the original business data has failed validation, determining whether the column style corresponding to each cell exists; if the column style exists, applying the column style to the original business data that failed validation; if the column style does not exist, applying the preset default style to the original business data that failed validation.

[0060] Specifically, the process of applying column styles to the original business data for style rendering includes: parsing the column style to obtain visual formatting attributes applicable to the entire column; obtaining the table identifier, pagination parameters, and filtering conditions carried in the page processing request; determining the range of the data view to be rendered based on the table identifier, pagination parameters, and filtering conditions; locating all target data cells within the data view range corresponding to the current column identifier to obtain a first target cell set; determining whether there are pre-marked cells in the first target cell set that are forced to be rendered as data styles; if so, removing the cells that are forced to be rendered as data styles from the first target cell set to form a second target cell set; applying the visual formatting attributes applicable to the entire column to the original business data of each cell in the second target cell set; if not, applying the visual formatting attributes applicable to the entire column to the original business data of each cell in the first target cell set.

[0061] It's important to note that when both a user-defined, finely styled data style and a global column style exist within the same cell, the system automatically prioritizes the data style, ensuring that personalized visual markers for specific data accurately cover the more general column-level format. This maintains the accuracy of visual cues and the clear expression of business meaning in complex data operations. When no special data style exists, the system automatically reverts to the column style to maintain visual consistency across the entire column, or applies the default style to ensure basic readability when neither exists. This mechanism fundamentally solves the problems of style confusion, conflicting coverage, or complete loss in traditional tables after view changes. It enables user-defined style rules to intelligently and stably follow the data and correctly synchronize with the view state, significantly improving data visualization efficiency and user experience in scenarios involving large amounts of data.

[0062] For example Figure 7 As shown, Figure 7 This is a schematic diagram illustrating the rendering process of raw business data provided in this application. First, the system receives a page processing request and determines whether the request involves view change operations such as switching pagination, filtering, or sorting. If no such change occurs, the process terminates or skips style calculation. If the view changes, the system further determines whether all data styles and column styles in the current context are empty values. If both are not empty, the system first verifies the raw business data; if the verification passes, the data style attributes are applied. If the data style is empty but the column style exists, the system parses the column style, determines the data view range, and locates the target cell set. If there are cells that are forcibly rendered as data styles, they are removed to form a second set, and the column style is applied; otherwise, the column style is directly applied to the first set. If both the data style and column style are empty, the preset default style is directly applied. Finally, the processed raw business data is rendered and sent to the client.

[0063] In one possible implementation, the server retrieves the corresponding data style and column style for each cell on the current page. For cells in the status column: the system finds that they only have a column style (gray background) and no data style specific to a particular row. For cells in the output column: the system finds that some cells have both a data style and a column style (for example, a row with an output of 600 may have both the data style "output > 500" and the possible column style), while other cells have only a column style or neither.

[0064] At this point, the system iterates through each row of data on the current page, focusing on processing the output column: Scenario A (Data Style Validation Passed): A row of data is encountered: Production = 650. The system parses the validation rule (Production > 500) in the data style, validates the data (650), and the result is successful. The system prioritizes applying the data style (green background + bold) to this cell. At this time, even if a column style exists in this column, it will be overridden by the data style. Regardless of which page the user flips to, as long as the production value in a row exceeds 500, that number will automatically become green and bold, and this style will move with that row of data (ID=123), without being affected by pagination or sorting.

[0065] Scenario B (Data Style Validation Failed): Another row of data was encountered: Production = 420. The validation rule (Production > 500) failed. The system checks if the cell has a column style. If it does, the column style is applied (e.g., if the column has a style set, it is applied); otherwise, the default style (such as a plain white background) is applied. For data that does not meet the highlighting criteria, the system automatically reverts to the normal column style or the default style, ensuring the visual consistency of the table.

[0066] Finally, the system processes the status column: The system parses the column style to obtain the visual formatting attribute (gray background). Based on the pagination parameters, the system determines the status cells of all rows on the current page, obtaining the first target cell set. The system checks if there are any cells in this set that have been forcibly rendered with the data style (i.e., those cells that were specially marked in the previous step, such as "abnormal status highlighted in red"). If they exist: these special cells are removed, and the gray background is applied to the remaining cells. If they do not exist: the gray background is directly applied to all status cells. The gray background of the entire column remains consistent across every page. Furthermore, if the status of a row is individually set to a red data style for a special reason (such as "work stoppage"), then the status cells in that row will be displayed in red, instead of incorrectly displaying in gray, demonstrating the precise overriding of the column style by the data style.

[0067] In this embodiment, on the one hand, the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier, and specific style. The corresponding data style or column style can be retrieved in real time based on the current data identifier and column identifier for rendering. This mapping relationship is customized by the user based on their own needs, enabling differentiated visual displays for different table data. Secondly, by establishing the mapping relationship, it becomes technically possible to set special styles for any specific cell, thus breaking through the limitations of traditional one-size-fits-all rendering and achieving a higher level of precision in data visualization.

[0068] On the other hand, a node tree data structure is used to store style mapping relationships. This structure, rooted at the table identifier and using column and business data identifiers as paths, forms a global style index. This establishes a relational storage mechanism between data and style attributes, accurately expressing the complex relationships between specific columns, rows, and styles in a specific data table. When rendering data, the node tree can be efficiently traversed based on all combinations of business data identifiers and column identifiers for the current page, allowing for batch retrieval and rendering of the corresponding styles, thus improving rendering accuracy and efficiency.

[0069] 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.

[0070] Please see Figure 8 This illustration shows a schematic diagram of the structure of an intelligent tabular collaborative management device provided in an exemplary embodiment of this application. This intelligent tabular collaborative management device can be implemented as all or part of an electronic device through software, hardware, or a combination of both. The device 1 includes a parameter acquisition module 10, a style query module 20, and a style rendering module 30.

[0071] The parameter acquisition module 10 is used to acquire the original business data to be displayed in the table and the pre-stored custom style data according to the page processing request sent by the client; wherein the original business data and the pre-stored custom style data are stored separately; the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier and specific style; The style query module 20 is used to obtain the current data identifier and the current column identifier of the original business data, and to read the data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; The style rendering module 30 is used to render the original business data according to the data style and column style, and send the rendered original business data to the client.

[0072] It should be noted that the intelligent tabular collaborative management device provided in the above embodiments is only illustrated by the division of the above functional modules when executing the intelligent tabular collaborative management method. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the intelligent tabular collaborative management device and the intelligent tabular collaborative management method embodiments provided in the above embodiments belong to the same concept, and the implementation process is detailed in the method embodiments, which will not be repeated here.

[0073] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0074] In this embodiment, on the one hand, the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier, and specific style. The corresponding data style or column style can be retrieved in real time based on the current data identifier and column identifier for rendering. This mapping relationship is customized by the user based on their own needs, enabling differentiated visual displays for different table data. Secondly, by establishing the mapping relationship, it becomes technically possible to set special styles for any specific cell, thus breaking through the limitations of traditional one-size-fits-all rendering and achieving a higher level of precision in data visualization.

[0075] On the other hand, a node tree data structure is used to store style mapping relationships. This structure, rooted at the table identifier and using column and business data identifiers as paths, forms a global style index. This establishes a relational storage mechanism between data and style attributes, accurately expressing the complex relationships between specific columns, rows, and styles in a specific data table. When rendering data, the node tree can be efficiently traversed based on all combinations of business data identifiers and column identifiers for the current page, allowing for batch retrieval and rendering of the corresponding styles, thus improving rendering accuracy and efficiency.

[0076] This application also provides a computer-readable medium having program instructions stored thereon, which, when executed by a processor, implement the intelligent tabular collaborative management method provided in the above-described method embodiments.

[0077] This application also provides a computer program product containing instructions that, when run on a computer, causes the computer to execute the intelligent tabular collaborative management method of the various method embodiments described above.

[0078] Please see Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 9As shown, the electronic device 1000 may include: at least one processor 1001, at least one network interface 1004, a user interface 1003, a memory 1005, and at least one communication bus 1002.

[0079] The communication bus 1002 is used to realize the connection and communication between these components.

[0080] The user interface 1003 may include a display screen and a camera. Optionally, the user interface 1003 may also include a standard wired interface and a wireless interface.

[0081] The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).

[0082] The processor 1001 may include one or more processing cores. The processor 1001 connects to various parts within the electronic device 1000 using various interfaces and lines. It executes various functions and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 1005, and by calling data stored in the memory 1005. Optionally, the processor 1001 may be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 1001 may integrate one or more of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content to be displayed on the screen; and the modem handles wireless communication. It is understood that the modem may also be implemented as a separate chip, without being integrated into the processor 1001.

[0083] The memory 1005 may include random access memory (RAM) or read-only memory. Optionally, the memory 1005 may include a non-transitory computer-readable storage medium. The memory 1005 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 1005 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 1005 may also be at least one storage system located remotely from the aforementioned processor 1001. Figure 9 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an intelligent spreadsheet collaborative management application.

[0084] exist Figure 9 In the illustrated electronic device 1000, the user interface 1003 is mainly used to provide an input interface for the user and to acquire user input data; while the processor 1001 can be used to call the intelligent spreadsheet collaborative management application stored in the memory 1005 and specifically perform the following operations: Based on the page processing request sent by the client, the original business data to be displayed in the table and the pre-stored custom style data are obtained. The original business data and the pre-stored custom style data are stored separately. The pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier and specific style. Obtain the current data identifier and the current column identifier of the original business data, and read the data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; Based on the data style and column style, render the original business data and send the rendered original business data to the client.

[0085] In one embodiment, when the processor 1001 renders the original business data according to the data style and column style, it specifically performs the following operations: When a page processing request is used to request the server to perform pagination switching, data filtering, or sorting operations, check whether the data style and column style are empty values. If neither the data style nor the column style is null, the data style will be applied to the original business data for style rendering first; or, If the data style is null and the column style is not null, then the column style will be applied to the original business data for style rendering; or, If both the data style and column style are empty, the preset default style will be applied to the original business data for style rendering.

[0086] In one embodiment, when the processor 1001 generates the mapping relationship, it performs the following operations: Receive a style setting request sent by the client. The style setting request includes the target business data identifier, the target column identifier, and the target custom style corresponding to the target business data identifier and / or the target column identifier. Construct a target mapping key based on the target business data identifier and / or target column identifier; In the storage structure of custom style data, establish and store the mapping relationship between the target mapping key and the target custom style; When the target custom style is the target column style, it will take effect in the same column of each page of the table.

[0087] In one embodiment, when the processor 1001 performs style rendering by prioritizing the application of data styles to the original business data, it specifically performs the following operations: Parse the data style to obtain the business data validation rules and data style attributes of each cell containing the original business data; The original business data is verified using the business data verification rules for each cell, and the data verification results are obtained. If the data validation result indicates that the original business data has passed validation, the data style attributes of each cell are applied to the original business data; specifically, after switching pagination, data filtering, or sorting operations, the data style attributes of each cell take effect along with the business data associated with it; or, If the data validation result indicates that the original business data validation failed, check whether the column style corresponding to each cell exists. If a column style exists, it will be applied to the original business data that fails validation; if a column style does not exist, the default style will be applied to the original business data that fails validation.

[0088] In one embodiment, when the processor 1001 performs style rendering by applying column styles to the original business data, it specifically performs the following operations: Parse the column style to obtain visual formatting attributes applicable to the entire column; Retrieve the table identifier, pagination parameters, and filter conditions carried in the page processing request; Determine the range of the data view to be rendered based on the table identifier, pagination parameters, and filtering conditions; Locate all target data cells within the data view range corresponding to the current column identifier to obtain the first target cell set; Determine if the first target cell set contains any cells that are pre-marked and forced to be rendered as data styles; If they exist, remove the cells that are forcibly rendered as data styles from the first target cell set to form the second target cell set; apply the visual formatting attributes applicable to the entire column to the original business data of each cell in the second target cell set; If it does not exist, the visual formatting attributes applicable to the entire column will be applied to the raw business data of each cell in the first target cell set.

[0089] In one embodiment, when the processor 1001 performs the operation of establishing and storing the mapping relationship between the target mapping key and the target custom style, the following specific operations are performed: Load the node tree data structure used to store the mapping relationship as the storage structure for the custom style data; Resolve the target mapping key into the target node path; The node tree data structure used to store mapping relationships is traversed and searched to determine whether a corresponding historical style storage node exists at the end of the target node path, and the judgment result is obtained. The node tree data structure takes the data table identifier as the root node and the column identifier and / or business data identifier as the child node path, forming a hierarchical index structure. Based on the judgment result and the target custom style, update the node tree data structure to establish and store the mapping relationship between the target mapping key and the target custom style.

[0090] In one embodiment, when the processor 1001 updates the node tree data structure based on the judgment result and the target custom style, it specifically performs the following operations: If the judgment result indicates that there is no corresponding historical style storage node, then in the node tree data structure, a new style storage node is created along the target node path, and the target custom style is stored as the attribute value of the new node; or, If the judgment result indicates that a corresponding historical style storage node exists, then the original historical attribute values ​​of the historical style storage node are overwritten and updated with the target custom style; Generate an updated node tree data structure.

[0091] In one embodiment, when the processor 1001 executes a page processing request sent by the client to obtain the original business data to be displayed in the table and the pre-stored custom style data, it specifically performs the following operations: Parse the page processing request to obtain the table's data table identifier, the pagination information of the current request, data filtering conditions, and sorting rules; Based on the data table identifier, pagination information, data filtering conditions and sorting rules, execute a query from the business database to obtain the original business data corresponding to the currently requested page view; Extract the unique business data identifier from each line of business data record in the original business data; Based on the data table identifier, locate the target root node of the node tree data structure that stores the mapping relationship of the table; Obtain all column identifiers involved in the page processing request to obtain the set of column identifiers to be processed; Based on the unique business data identifier, the target root node, and the set of column identifiers to be processed, pre-stored custom style data is generated.

[0092] In one embodiment, when processor 1001 generates pre-stored custom-style data based on a unique business data identifier, the target root node, and a set of column identifiers to be processed, it specifically performs the following operations: Based on the target root node, the column styles corresponding to all columns in the column identifier set to be processed are read in batches from the node tree data structure to form the style base layer; Combine the unique business data identifier with each column identifier in the set of column identifiers to be processed to obtain the query key for all cells on the current page; Based on the query key, the corresponding data style is queried and obtained from the node tree data structure to form an overlay layer; Use the data style in the overlay layer and the column style in the style base layer as the current specific style; The unique business data identifier, the set of column identifiers to be processed, and the current specific style are mapped and combined and cached to obtain pre-stored custom style data.

[0093] In this embodiment, on the one hand, the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier, and specific style. The corresponding data style or column style can be retrieved in real time based on the current data identifier and column identifier for rendering. This mapping relationship is customized by the user based on their own needs, enabling differentiated visual displays for different table data. Secondly, by establishing the mapping relationship, it becomes technically possible to set special styles for any specific cell, thus breaking through the limitations of traditional one-size-fits-all rendering and achieving a higher level of precision in data visualization.

[0094] On the other hand, a node tree data structure is used to store style mapping relationships. This structure, rooted at the table identifier and using column and business data identifiers as paths, forms a global style index. This establishes a relational storage mechanism between data and style attributes, accurately expressing the complex relationships between specific columns, rows, and styles in a specific data table. When rendering data, the node tree can be efficiently traversed based on all combinations of business data identifiers and column identifiers for the current page, allowing for batch retrieval and rendering of the corresponding styles, thus improving rendering accuracy and efficiency.

[0095] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The intelligent spreadsheet collaborative management program can be stored in a computer-readable storage medium. When executed, the program can include the processes of the embodiments of the above methods. The storage medium for the intelligent spreadsheet collaborative management program can be a magnetic disk, optical disk, read-only memory, or random access memory, etc.

[0096] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. An intelligent tabular collaborative management method, characterized in that, Applied to the server side, the method includes: Based on the page processing request sent by the client, the original business data to be displayed in the table and the pre-stored custom style data are obtained; wherein, the original business data and the pre-stored custom style data are stored separately; the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier and specific style; Obtain the current data identifier and the current column identifier of the original business data, and read the data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; Based on the data style and column style, the original business data is rendered, and the rendered original business data is sent to the client.

2. The method according to claim 1, characterized in that, The step of rendering the original business data according to the data style and column style includes: When the page processing request is used to request the server to perform pagination switching, data filtering, or sorting operations, determine whether the data style and column style are empty values. If neither the data style nor the column style is empty, then the data style is preferentially applied to the original business data for style rendering; or, If the data style is null and the column style is not null, then the column style is applied to the original business data for style rendering; or, If both the data style and the column style are empty, the preset default style will be applied to the original business data for style rendering.

3. The method according to claim 1, characterized in that, The mapping relationship is generated according to the following steps: Receive a style setting request sent by the client, the style setting request including a target business data identifier, a target column identifier, and a target custom style corresponding to the target business data identifier and / or the target column identifier; Construct a target mapping key based on the target business data identifier and / or target column identifier; In the storage structure of the custom style data, a mapping relationship between the target mapping key and the target custom style is established and stored; When the target custom style is the target column style, it applies to the same column on each page of the table.

4. The method according to claim 2, characterized in that, The step of preferentially applying the data style to the original business data for style rendering includes: Parse the data style to obtain the business data validation rules and data style attributes of each cell where the original business data is located; The original business data is verified using the business data verification rules for each cell to obtain the data verification result; If the data verification result indicates that the original business data has passed verification, the data style attributes of each cell are applied to the original business data; wherein, after switching pagination, data filtering, or sorting operations, the data style attributes of each cell take effect following the business data associated with it; or, If the data verification result indicates that the original business data verification fails, determine whether the column style corresponding to each cell exists; If the column style exists, the column style is applied to the original business data that fails validation; if the column style does not exist, the preset default style is applied to the original business data that fails validation.

5. The method according to claim 2, characterized in that, The step of applying the column style to the original business data for style rendering includes: Parse the column style to obtain visual formatting attributes applicable to the entire column; Obtain the table identifier, pagination parameters, and filtering conditions carried in the page processing request; The range of data view to be rendered is determined based on the table identifier, pagination parameters, and filtering conditions. Locate all target data cells within the data view range corresponding to the current column identifier to obtain a first target cell set; Determine whether there are any pre-marked cells in the first target cell set that are forced to be rendered as data styles; If they exist, remove the cells that are forcibly rendered as data styles from the first target cell set to form a second target cell set; apply the visual formatting attributes applicable to the entire column to the original business data of each cell in the second target cell set; If it does not exist, the visual formatting attribute applicable to the entire column is applied to the raw business data of each cell in the first target cell set.

6. The method according to claim 3, characterized in that, The process of establishing and storing the mapping relationship between the target mapping key and the target custom style includes: Load the node tree data structure used to store the mapping relationship as the storage structure for the custom style data; The target mapping key is parsed into a target node path; A traversal search is performed in the node tree data structure used to store the mapping relationship to determine whether there is a corresponding historical style storage node at the end of the target node path, and a determination result is obtained; wherein, the node tree data structure takes the data table identifier as the root node and the column identifier and / or business data identifier as the child node path to form a hierarchical index structure. Based on the judgment result and the target custom style, update the node tree data structure to establish and store the mapping relationship between the target mapping key and the target custom style.

7. The method according to claim 6, characterized in that, The step of updating the node tree data structure based on the judgment result and the target custom style includes: If the judgment result indicates that there is no corresponding historical style storage node, then in the node tree data structure, a new style storage node is created along the path of the target node, and the target custom style is stored as the attribute value of the new node; or, If the judgment result indicates that there is a corresponding historical style storage node, then the original historical attribute value of the historical style storage node is overwritten and updated with the target custom style; Generate the updated node tree data structure.

8. The method according to claim 1, characterized in that, The step of obtaining the original business data to be displayed in the table and the pre-stored custom style data according to the page processing request sent by the client includes: Parse the page processing request to obtain the table's data table identifier, the pagination information of the current request, the data filtering conditions, and the sorting rules; Based on the data table identifier, pagination information, data filtering conditions and sorting rules, a query is executed from the business database to obtain the original business data corresponding to the currently requested page view. Extract the unique business data identifier from each line of business data record in the original business data; Based on the data table identifier, the target root node of the node tree data structure that stores the mapping relationship of the table is located; Obtain all column identifiers involved in the page processing request to obtain a set of column identifiers to be processed; Based on the unique business data identifier, the target root node, and the set of column identifiers to be processed, pre-stored custom style data is generated.

9. The method according to claim 8, characterized in that, The process of generating pre-stored custom-style data based on the unique business data identifier, the target root node, and the set of column identifiers to be processed includes: Based on the target root node, the column styles corresponding to all columns in the column identifier set to be processed are read in batches from the node tree data structure to form a style base layer; By combining the unique business data identifier with each column identifier in the set of column identifiers to be processed, the query key for all cells on the current page is obtained; Based on the query key, the corresponding data style is queried and obtained from the node tree data structure to form an overlay layer; The data style in the overlay layer and the column style in the style base layer are used as the current specific style; The unique business data identifier, the set of column identifiers to be processed, and the current specific style are mapped and combined and cached to obtain pre-stored custom style data.

10. An intelligent tabular collaborative management device, characterized in that, The device includes: The parameter acquisition module is used to acquire the original business data to be displayed in the table and the pre-stored custom style data according to the page processing request sent by the client; wherein the original business data and the pre-stored custom style data are stored separately; the pre-stored custom style data includes the mapping relationship between each business data identifier, column identifier and specific style; The style query module is used to obtain the current data identifier and the current column identifier of the original business data, and to read the data style and column style corresponding to the current data identifier and the current column identifier from the mapping relationship; The style rendering module is used to render the original business data according to the data style and column style, and send the rendered original business data to the client.

Images