Spreadsheet multi-tab data processing method and system

Abstract

The application discloses an electronic form multi-tab data processing method and system. The method comprises the following steps: rendering a data worksheet view of a system default tab page in an electronic form main area, wherein the electronic form main area comprises a pre-rendered tab control bar, and the tab control bar provides an operable tab page; in response to a selection operation of a target tab page other than the system default tab page in the tab control bar, determining a target data model and target configuration information corresponding to the target tab page; switching a current data model and a current view configuration of the system default tab page associated with the form main area into the target data model and the target configuration information; and rendering a data worksheet view of the target tab page in the main area according to the target data model and the target configuration information. The application improves the continuity and efficiency of operation, effectively avoids operation interruption and context loss caused by page jumping, and improves the pertinence and flexibility of the interface.

Description

Technical Field

[0001] This application relates to the field of manufacturing execution systems technology, and in particular to a method and system for processing multi-tab data in spreadsheets. Background Technology

[0002] In the warehouse management scenario of traditional Manufacturing Execution System (MES) and Enterprise Information Management System, warehouse staff need to pay attention to multiple dimensions of business data when performing daily business. For example, when operating inbound and outbound operations, they need to simultaneously view real-time inventory ledgers, trace historical inbound and outbound records, and process currently online inbound and outbound operation tasks.

[0003] Currently, a fixed single-page structure is used. When managing data, users need to navigate between different module pages by clicking on functional modules to access different data lists or forms. In addition, the system adopts a globally unified interface configuration strategy, which centrally manages the view configurations such as field display rules and column sorting logic of data tables, and applies the configuration results to all pages.

[0004] However, the fixed single-page structure prevents users from dynamically creating multiple independent data views as needed. When cross-referencing data from different dimensions is required, users have to repeatedly jump between functional modules, resulting in lengthy operation paths, frequent loss of context, and severely impacting operational consistency. Secondly, interface configurations such as field display rules and column sorting logic typically adopt a globally uniform strategy, preventing users from customizing differentiated views for different business scenarios, thus affecting the relevance and flexibility of business scenarios. Summary of the Invention

[0005] This application provides a method and system for processing multi-tab data in a spreadsheet. 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 a method for processing multi-tab data in a spreadsheet, the method comprising:

[0007] The spreadsheet body area renders the data worksheet view of the system's default tabs. The spreadsheet body area includes a pre-rendered tab control bar, which provides at least two user-configured operable tabs, each tab corresponding to a data worksheet view.

[0008] In response to the user's selection of a target tab in the tab control bar other than the system default tab, determine the target data model and target configuration information corresponding to the target tab;

[0009] Switch the current data model and current view configuration of the system default tab associated with the main table area to the target data model and target configuration information;

[0010] Based on the target data model and target configuration information, render the data worksheet view of the target tab within the main area of ​​the spreadsheet.

[0011] Optionally, determine the target data model and target configuration information corresponding to the target tab, including:

[0012] Retrieve the pre-stored ternary mapping relationship, which includes the mapping relationship between user identifier, tab ID identifier, data model corresponding to tab ID identifier, and configuration information;

[0013] From the pre-stored ternary mapping relationship, obtain the binary mapping relationship between each first tab ID corresponding to the user's current user ID, the first data model corresponding to each first tab ID, and the first configuration information;

[0014] From the binary mapping relationship, obtain the target data model and target configuration information corresponding to the target tab.

[0015] Optionally, the pre-stored ternary mapping relationship is generated by following these steps:

[0016] Render a tab control bar within the currently displayed single table body area;

[0017] In response to a user instruction to create a new tab for the main body area of ​​the table, a tab ID is generated;

[0018] Determine the data model and configuration information corresponding to the tab ID; the configuration information is the user's global preference configuration or the configuration parameters of the system default template, which are read automatically.

[0019] Integrate the tab ID into the tab control bar to create an operable tab;

[0020] Stores a three-element mapping relationship between the user identifier of the currently operating user, the tab ID identifier, the data model corresponding to the tab ID identifier, and the configuration information.

[0021] Optionally, the current data model and current view configuration of the system default tab associated with the table body area can be switched to the target data model and target configuration information, including:

[0022] Capture the current view state of the data worksheet view of the system default tab and obtain the historical view state records of the system default tab; the current view state includes at least the cached historical scroll bar position, row selection state, and input box content;

[0023] In local memory, the association between the user's current user identifier, the tab ID of the system default tab, and the historical view status records of the system default tab is stored.

[0024] Remove the main area of ​​the spreadsheet from the current data model and current configuration information, and bind it to the target data model and target configuration information corresponding to the target tab.

[0025] Optionally, based on the target data model and target configuration information, render a data worksheet view of the target tab within the main area of ​​the spreadsheet, including:

[0026] Determine if the data worksheet view of the target tab is being rendered for the first time;

[0027] If not, restore the cached history view state record of the target tab from memory; the history view state record includes at least the historical scroll bar position, row selection state and input box content cached in the content when the target tab was previously accessed, in order to maintain the continuity of user operation;

[0028] If so, according to the query logic of the target data model, obtain the initial data set from the server, or according to the recovery logic of the target data model, restore the cached data stored in the local device to the initial data set; based on the column configuration, sorting rules and filtering conditions defined in the target configuration information, process the initial data set to generate a formatted dataset for rendering;

[0029] Render the data sheet view of the target tab within the main area of ​​the spreadsheet, based on the cached historical view state records of the target tab or the formatted dataset used for rendering.

[0030] Optionally, the user's user identifier, the tab ID identifier, and the association between the tab's historical view status records are stored locally in memory;

[0031] Determine if the data worksheet view of the target tab is being rendered for the first time, including:

[0032] From the association relationships, query whether there are any historical view status records associated with the user's current user ID and the tab ID of the target tab page;

[0033] If so, determine that the data worksheet view of the target tab is not being rendered for the first time;

[0034] If not, determine that the data worksheet view of the target tab is being rendered for the first time.

[0035] Optionally, based on the cached historical view state records of the target tab or the formatted dataset used for rendering, render the data worksheet view of the target tab within the main area of ​​the spreadsheet, including:

[0036] Retrieve the field-level access permission policies configured for the user from the target configuration information;

[0037] Based on the field-level access permission policy, the cached historical view state records or the formatted dataset used for rendering of the target tab are filtered to hide or remove sensitive data fields that the user is not authorized to view, resulting in a filtered formatted dataset.

[0038] Draw and display the filtered, formatted dataset within the main area of ​​the spreadsheet to obtain the data worksheet view for the target tab.

[0039] Optionally, before rendering the data sheet view of the system's default tab in the main area of ​​the spreadsheet, the following also applies:

[0040] Initialize and render a tab control bar above or below the main area of ​​the spreadsheet;

[0041] In response to a user's command to enter the main area of ​​the spreadsheet, retrieve a list of identifiers for at least two pre-configured tabs from the persistent storage configuration associated with the user;

[0042] Based on the list of identifiers, render the operable tabs in the tab control bar;

[0043] From at least two tabs, determine the first tab as the system default tab.

[0044] Optionally, render the data worksheet view of the system default tab in the main area of ​​the spreadsheet, including:

[0045] Retrieve default configuration information associated with the user for the system default tab;

[0046] Retrieve the default data model corresponding to the system's default tab and the field-level access permission policy configured for the user;

[0047] Based on the permission policy, the original data set corresponding to the default data model is filtered to remove sensitive data fields that users do not have permission to access, thus obtaining the final data set after permission filtering.

[0048] Based on the column configuration, sorting rules, and filtering conditions defined in the default configuration information, the final data set is formatted to generate the final dataset to be rendered.

[0049] Within the main area of ​​the spreadsheet, a data worksheet view of the system's default tab is drawn and presented based on the dataset to be rendered and the default configuration information.

[0050] Secondly, embodiments of this application provide a multi-tab data processing system for spreadsheets, the system comprising:

[0051] The initialization module is used to render the data worksheet view of the system default tab in the main area of ​​the spreadsheet. The main area of ​​the spreadsheet includes a pre-rendered tab control bar, which provides at least two operable tabs pre-configured by the user, each tab corresponding to a data worksheet view.

[0052] The parameter determination module is used to determine the target data model and target configuration information corresponding to the target tab in response to the user's selection operation of other target tabs in the tab control bar besides the system default tabs;

[0053] The parameter switching module is used to switch the current data model and current view configuration of the system default tab associated with the main table area to the target data model and target configuration information;

[0054] The data worksheet view rendering module is used to render the data worksheet view of the target tab within the main area of ​​the spreadsheet, based on the target data model and target configuration information.

[0055] The technical solutions provided in this application embodiment may include the following beneficial effects:

[0056] In this embodiment, on the one hand, by introducing pre-rendered tab control bars, users can access different data worksheet views within the same spreadsheet main area through multiple pre-configured operable tabs. Users can quickly switch between different data views within the same interface simply by clicking a tab. Since tab switching is completed within the same container, view states can be independently cached and restored, eliminating the need for users to jump back and forth between different pages when comparing data of different dimensions. This improves the continuity and efficiency of the operation and effectively avoids operation interruptions and context loss caused by page jumps. On the other hand, each tab is independently associated with its own data model and configuration information. When a user selects a new target tab, the system determines the target data model and target configuration information corresponding to the target tab and switches the model and configuration bound to the entire spreadsheet main area. This ensures that each tab's corresponding data worksheet view has an independent and personalized configuration, significantly improving the interface's relevance and flexibility.

[0057] 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

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

[0059] Figure 1 This is a flowchart illustrating a method for processing multi-tab data in an electronic spreadsheet, as provided in an embodiment of this application.

[0060] Figure 2 This is an interface diagram of the main area of ​​a spreadsheet provided in an embodiment of this application;

[0061] Figure 3 This is a diagram of a new tab interface provided in an embodiment of this application;

[0062] Figure 4 This is a screenshot of the result interface after creating a new tab, provided in an embodiment of this application.

[0063] Figure 5 This is a schematic diagram illustrating the rendering process of a data worksheet view of a target tab page according to an embodiment of this application;

[0064] Figure 6 This is a schematic diagram illustrating a multi-tab data processing procedure for an electronic spreadsheet provided in an embodiment of this application;

[0065] Figure 7 This is a schematic diagram of the structure of a multi-tab data processing system for spreadsheets provided in an embodiment of this application;

[0066] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

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

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

[0069] 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 systems and methods consistent with some aspects of this application as detailed in the appended claims.

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

[0071] Currently, a fixed single-page structure is used. When managing data, users need to navigate between different module pages by clicking on functional modules to access different data lists or forms. In addition, the system adopts a globally unified interface configuration strategy, which centrally manages the view configurations such as field display rules and column sorting logic of data tables, and applies the configuration results to all pages.

[0072] The inventors realized that the fixed single-page structure prevented users from dynamically creating multiple independent data views as needed. When cross-referencing data from different dimensions was required, users had to repeatedly jump between functional modules, resulting in lengthy operation paths, frequent loss of context, and severely impacting operational continuity. Secondly, interface configurations such as field display rules and column sorting logic typically adopted a globally uniform strategy, preventing users from customizing differentiated views for different business scenarios, thus affecting the relevance and flexibility of business scenarios.

[0073] To address the aforementioned issues, this application provides a multi-tab data processing method and system for spreadsheets, resolving the problems existing in the related technologies. In this application's embodiments, on one hand, by introducing pre-rendered tab control bars, users can access different data worksheet views within the same main spreadsheet area through multiple pre-configured operable tabs. Users can quickly switch between different data views within the same interface simply by clicking a tab. Since tab switching is completed within the same container, view states can be independently cached and restored, eliminating the need for users to jump back and forth between different pages when comparing data of different dimensions. This improves the continuity and efficiency of operations and effectively avoids operation interruptions and context loss caused by page jumps. On the other hand, each tab is independently associated with its own data model and configuration information. When a user selects a new target tab, the system determines the target data model and target configuration information corresponding to the target tab and switches the model and configuration bound to the entire main spreadsheet area. This ensures that each tab's corresponding data worksheet view has an independent and personalized configuration, significantly improving the interface's relevance and flexibility. Exemplary embodiments are described in detail below.

[0074] The following will be combined with the appendix Figure 1 - Appendix Figure 6 This application provides a detailed description of the spreadsheet multi-tab data processing method provided in its embodiments. This method can be implemented using a computer program and can run on a spreadsheet multi-tab data processing system based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application.

[0075] Please see Figure 1 This is a flowchart illustrating a multi-tab data processing method for spreadsheets, as provided in this application embodiment. Figure 1 As shown, the method in this application embodiment includes the following steps:

[0076] S101, Render the data worksheet view of the system default tab in the main area of ​​the spreadsheet. The main area of ​​the spreadsheet includes a pre-rendered tab control bar. The tab control bar provides at least two operable tabs pre-configured by the user, and each tab corresponds to a data worksheet view.

[0077] The main body area of ​​the spreadsheet is a component area within the user interface display area used for rendering, presenting, and manipulating tabular data. This component area serves as the visual and logical container for the main content of the spreadsheet. For example, the main body area of ​​the spreadsheet... Figure 2As shown. The system default tab is a specific tab that is pre-set to be active when the user enters the system or during system initialization, among a set of multiple toggleable view tabs. This tab is displayed first without the user having to actively select it. Figure 2 In the system settings, sales data can be displayed on the system default tab, with the first tab being the default. Users can also customize this setting. The data worksheet view is an interactive view based on spreadsheet controls, used to display, edit, and manage structured data records, such as... Figure 2 The spreadsheet form. A tab control bar is a user interface control component located at the top or bottom of the main spreadsheet area. It hosts and manages a group of tabs, providing interfaces for creating, selecting, closing, and renaming tabs. Interactive tabs are independent tab-style controls embedded in the tab control bar. Users can interact with them by clicking, touching, etc., to trigger the activation and switching of the corresponding view for that tab. Figure 2 The top tab displays sales data, and the top tab displays user information.

[0078] In some embodiments of this application, before rendering the data worksheet view of the system default tab in the main area of ​​the spreadsheet, the system needs to initialize and render a tab control bar above or below the main area of ​​the spreadsheet; in response to the user's operation command to enter the main area of ​​the spreadsheet, the system obtains a list of identifiers of at least two pre-configured tabs from the persistent storage configuration associated with the user; based on the identifier list, the system renders operable tabs in the tab control bar; and from the at least two tabs, the system determines the first tab as the system default tab.

[0079] In one possible implementation, create a component instance (e.g., TabsContainer) representing the tab control bar. Configure its basic styles (e.g., placing it above or below the table body area) and bind it to a DOM container element to hold the tab list. Call the framework's rendering method (e.g., React's render or virtual DOM mounting) to draw the component's UI structure (HTML / CSS) onto the browser's specified DOM node. Send an asynchronous request to the server or local storage. The request carries a unique identifier for the currently logged-in user (e.g., userID). The server, based on the user identifier, queries the tab configuration field from its associated configuration file or user configuration data table. This field stores serialized data in JSON or other format containing an ordered list of tab identifiers. For example: ["tab_inventory", "tab_logs", "tab_alerts"]. Return the retrieved identifier list to the front end. The front end application receives and parses this list. The front end application (e.g., a Sheet Manager) iterates through the identifier list retrieved from persistent storage. For each identifier in the list, the system maps it to a specific tab component definition. For each tab corresponding to an identifier, create an instance of an operable UI component. Render the tab header of this instance into the created tab control bar container. Each tab component is initially inactive upon rendering. Determine the system default tab from at least two rendered tabs according to predefined logic.

[0080] In some embodiments of this application, rendering the data worksheet view of the system default tab in the main area of ​​a spreadsheet specifically includes: obtaining default configuration information associated with the user for the system default tab; obtaining the default data model corresponding to the system default tab and the field-level access permission policy configured for the user; performing field filtering on the original data set corresponding to the default data model based on the permission policy to remove sensitive data fields that the user is not authorized to access, thereby obtaining the final data set after permission filtering; formatting the final data set according to the column configuration, sorting rules, and filtering conditions defined in the default configuration information to generate the final dataset to be rendered; and drawing and presenting the data worksheet view of the system default tab within the main area of ​​the spreadsheet based on the dataset to be rendered and the default configuration information.

[0081] The default configuration information is a set of predefined view presentation rules bound to the system default tab, including but not limited to: column configuration (including column order, show / hide status, column width, column header alias), sorting rules (specifying one or more fields and their ascending / descending sorting), filtering conditions (conditional expressions used to filter data on the server or client side), and identifiers for data query logic (such as API endpoints, SQL query statement IDs), etc.

[0082] The default data model, located in the application's data layer, is a logical object used to describe, encapsulate, and process the data structure required by the system's default tabs. It defines the types and relationships of data fields (attributes) and contains the business logic for retrieving and manipulating data.

[0083] In one possible implementation, during initialization, a request is sent to the configuration management service. The request parameters include the current user identifier and the tab identifier of the system's default tab. The server queries the user-tab configuration table in the database based on these two parameters. If the user has personalized configurations for that tab, they are returned; otherwise, a predefined default configuration template is returned. The system instantiates a corresponding data model object on the client side or via a request, based on the data source identifier specified in the default configuration information. This object encapsulates methods for communicating with the backend service to obtain the raw data set. A request is sent to the permission center service, with the current user identifier and data model identifier as parameters. The permission center returns a permission policy object. The `fetch()` or `query()` method of the default data model is called to retrieve the raw data set from the server. Each record in the raw data is iterated through, and a new data object containing only allowed access fields is created according to the policy. The fields of the final data set are rearranged or filtered according to the column configurations in the default configuration information. Data formatting is performed, outputting the dataset to be rendered. The dataset to be rendered and the default configuration information are passed to the front-end table rendering component. The table rendering component draws and renders the view.

[0084] S102, in response to the user's selection of a target tab in the tab control bar other than the system default tab, determine the target data model and target configuration information corresponding to the target tab;

[0085] The tab control bar can hold multiple interface control bars that allow switching between tabs, for example... Figure 2The system's default tab is the one that is automatically activated and displayed in the initial state. A selection action is an interactive event initiated by the user to activate a specific interface element. This can take the form of a left mouse click or a finger touch click; its programmatic essence is triggering the onClick, onTap, and other event listeners bound to the tab control. The target data model is a data layer object uniquely bound to the target tab, used to manage and provide the required business data. It encapsulates the data query and update logic and data format definitions for the specific business scenario of that tab. The target configuration information is the view configuration metadata uniquely associated with the target tab. It defines the specific presentation of the data worksheet view under that tab, and is the rule for how the data in the target data model is processed into the view.

[0086] In some embodiments of this application, the specific process of determining the target data model and target configuration information corresponding to the target tab includes: obtaining a pre-stored ternary mapping relationship, which includes a mapping relationship between user identifier, tab ID identifier, data model corresponding to the tab ID identifier, and configuration information; obtaining a binary mapping relationship between each first tab ID identifier corresponding to the user's current user identifier, the first data model corresponding to each first tab ID identifier, and the first configuration information from the pre-stored ternary mapping relationship; and obtaining the target data model and target configuration information corresponding to the target tab from the binary mapping relationship.

[0087] The ternary mapping relationship is a mapping table or database record that links a user identifier, a tab ID, and the data model and configuration information bound to that tab ID. Its core function is to establish a global, persistent index, enabling the system to uniquely locate the data and view rules that a user should use under that tab using the user and tab ID. An example of a ternary mapping relationship data table is shown in Table 1.

[0088] Table 1

[0089]

[0090] In one possible implementation, a user selects a tab that is not currently active on the tab control bar, for example, by clicking its header. The system retrieves the currently logged-in user's `user_id` (e.g., `u001`). Then, a filter operation is performed on the aforementioned loaded ternary mapping dataset, with the condition `user_id == 'u001'`. After filtering, all records belonging exclusively to user `u001` are obtained. These records together constitute a tab resource mapping table belonging to that user. Internally, this result is typically transformed into a binary mapping with `tab_id` as the key and objects containing `data_model_definition` and `config_json` as values. The `tab_id` (e.g., `transaction_log`) bound to the clicked tab UI component is retrieved. Using this `tab_id` (`transaction_log`) as the key, a lookup is performed in the binary mapping (i.e., `userTabMap['transaction_log']` is executed). A successful query returns the associated value object { dataModel:'TransactionLogModel', config: { …}}. The dataModel field (definition) and config field (data) in this object represent the final target data model and target configuration information.

[0091] In some embodiments of this application, the specific process of generating a pre-stored ternary mapping relationship includes: rendering a tab control bar within the currently displayed single table body area; generating a tab ID identifier in response to a user instruction to create a new tab for the table body area; determining the data model and configuration information corresponding to the tab ID identifier; the configuration information being automatically read user global preference configuration or configuration parameters of the system default template; integrating the tab ID identifier into the tab control bar to obtain an operable tab; and storing the ternary mapping relationship between the user identifier of the currently operating user, the tab ID identifier, the data model corresponding to the tab ID identifier, and the configuration information.

[0092] The user command to create a new tab is an interactive action triggered by the user to add a new tab, such as clicking [a button]. Figure 2 The "+" button in the menu allows you to select "New Tab". Global preference configurations are personalized view settings templates bound to the currently logged-in user account and applicable across tabs, containing commonly used rules for column display, sorting, and filtering. The system default template is a standardized view configuration template predefined by the system administrator and applicable to all users when the user has no personal preference configuration.

[0093] In one possible implementation, within the displayed spreadsheet workbench, the system first renders a tab control bar. Simultaneously, it listens for user commands to "create a new tab" in this area, such as clicking the "+ New Tab" icon next to the control bar. Upon capturing the creation command, the system immediately generates a globally unique tab ID (e.g., sheet_new_abc123). This ID uniquely represents the new tab in all subsequent logic. Based on the context of the creation command or the user's selection, the system determines the data type to be displayed on the new tab, thus associating it with a specific data model definition. The system automatically attempts to read the currently logged-in user's global preference configuration. If the user has never set it, it reverts to using the system's default template configuration parameters. This ensures that the new tab's view style is consistent with user habits or team standards, eliminating the need for the user to set it up from scratch. The system dynamically adds the generated tab ID as a new, clickable tab control to the tab control bar. The user can then see this new tab on the interface. Finally, the system associates and stores key information, forming a ternary mapping record. This record includes user identifier, tab ID, data model, and configuration information.

[0094] For example, when the user clicks Figure 2 After clicking the "+ New Tab", the results displayed to the user are as follows: Figure 3 As shown, users can configure the page signature name, data model, and configuration template. For example, if the configured page signature is named "Sales Data Table," the selected data model is "Inventory Data Model," and the configuration template is the system default, the final result after the user clicks "Create" is as follows: Figure 4 As shown, Figure 4 A new tab named "Sales Data Table" has appeared on the tab control bar.

[0095] S103, switch the current data model and current view configuration of the system default tab associated with the main table area to the target data model and target configuration information;

[0096] In some embodiments of this application, the specific process of switching the current data model and current view configuration of the system default tab associated with the main body area of ​​the table to the target data model and target configuration information includes: capturing the current view state of the data worksheet view of the system default tab and obtaining the historical view state record of the system default tab; the current view state includes at least the cached historical scroll bar position, row selection state, and input box content; storing the association between the user's current user identifier, the tab ID identifier of the system default tab, and the historical view state record of the system default tab in local memory; unbinding the main body area of ​​the spreadsheet from the current data model and current configuration information, and binding the target data model and target configuration information corresponding to the target tab.

[0097] The current view state is a snapshot of the information presented by the interface elements at a specific moment when the user interacts with the data worksheet view of the system's default tab. It includes temporary information generated by user interaction. The historical view state record is a data snapshot obtained by serializing the current view state, used to restore the state at a specific point in the past.

[0098] In one possible implementation, the system first locks the currently active system default tab the moment the user clicks the target tab. The system calls the state capture method of the table component corresponding to that tab, reading its current scroll bar position, the ID array of the selected row, and the temporary values ​​of all cells in edit mode. This information is assembled into a view state object (i.e., a history view state record). For example: { scrollTop: 250, selectedRowIds:[101, 103], editingCells: {'B5': 'Pending Review'}}. In the front-end application's memory, the system combines the current user ID and the tab ID of the system default tab into a unique key (e.g., user_001:tab_default). The generated view state object is stored as the value using this unique key to establish a relationship, allowing for quick restoration when the user switches back to this tab. The system instructs the rendering engine of the spreadsheet's main area to stop listening to changes in the current data model and clears all control over the table style from the current configuration information. The table's dataSource property is set to point to an instance of the target data model, and the system subscribes to the model's data change events. Based on the column definitions, sorting rules, and other information in the target configuration, the table headers and columns are reconfigured and rendered. At this point, the main area of ​​the spreadsheet has been completely switched to the new target tab in terms of logic and resource dependencies.

[0099] S104, Render the data worksheet view of the target tab in the main area of ​​the spreadsheet based on the target data model and target configuration information.

[0100] In some embodiments of this application, the specific process of rendering the data worksheet view of a target tab within the main area of ​​a spreadsheet, based on the target data model and target configuration information, includes: determining whether the data worksheet view of the target tab is being rendered for the first time; if not, restoring the historical view state record cached by the target tab from memory; the historical view state record includes at least the historical scroll bar position, row selection state, and input box content cached in the content when the target tab was previously accessed, to maintain the continuity of user operations; if yes, obtaining the initial data set from the server according to the query logic of the target data model, or restoring the cached data stored in the local device to the initial data set according to the restoration logic of the target data model; processing the initial data set based on the column configuration, sorting rules, and filtering conditions defined in the target configuration information to generate a formatted dataset for rendering; and rendering the data worksheet view of the target tab within the main area of ​​the spreadsheet based on the historical view state record cached by the target tab or the formatted dataset for rendering.

[0101] The local memory stores the association between the user's user identifier, the tab ID, and the tab's historical view status records.

[0102] Specifically, the process of determining whether the data worksheet view of the target tab is being rendered for the first time includes: querying the relationships to see if there are any historical view status records associated with the user's current user ID and the target tab's tab ID; if so, determining that the data worksheet view of the target tab is not being rendered for the first time; if not, determining that the data worksheet view of the target tab is being rendered for the first time.

[0103] Specifically, the process of rendering the data worksheet view of the target tab within the main body of the spreadsheet, based on the cached historical view state records or the formatted dataset used for rendering, includes: obtaining the field-level access permission policy configured for the user from the target configuration information; filtering the cached historical view state records or the formatted dataset used for rendering based on the field-level access permission policy to hide or remove sensitive data fields that the user is not authorized to view, resulting in a filtered formatted dataset; and drawing and presenting the filtered formatted dataset within the main body of the spreadsheet to obtain the data worksheet view of the target tab.

[0104] For example Figure 5 As shown, Figure 5This is a schematic diagram illustrating the rendering process of a data worksheet view of a target tab provided in this application. To begin rendering the data worksheet view of the target tab, the process first queries the local memory for the association relationship: user identifier - tab ID - historical view state record. Then, it checks if an associated historical view state record exists. If it's not the first rendering, the historical view state record of the target tab is restored from memory, and the cached historical view state, including historical scroll bar position, row selection state, and input box content, is extracted. If it's the first rendering, the initial data set is obtained from the server or restored from the local device cache. Data is processed based on the target configuration information to generate a formatted dataset for rendering. Finally, the field-level access permission policy in the target configuration information is used to filter the historical view state and the formatted dataset, generating a filtered formatted dataset. The data is then drawn within the main area of ​​the spreadsheet, ultimately presenting the data worksheet view of the target tab.

[0105] In this embodiment, by intelligently determining whether the target tab is being accessed for the first time, accurate restoration of view state and efficient data loading are achieved. For non-first-time accesses, the system directly restores the complete context of the user's previous interactions (such as scroll position, selected row, and unsaved input) from memory, ensuring absolute continuity and a seamless experience when switching between multiple views. For first-time accesses, data is retrieved on demand from the server or local cache and formatted using personalized configurations, achieving rapid data initialization and standardized presentation. This effectively solves the problems of context loss, lengthy operation paths, and low data loading efficiency caused by repeated jumps in traditional systems, significantly improving the overall efficiency and smoothness of users' cross-processing between multiple data views.

[0106] For example Figure 6 As shown, Figure 6This is a schematic diagram illustrating a multi-tab data processing procedure for a spreadsheet provided in this application. During system initialization, a tab control bar is initialized above / below the main body area of ​​the spreadsheet. Responding to user commands to enter the spreadsheet, a list of pre-configured tab identifiers is retrieved from persistent storage. Operable tabs are rendered on the tab control bar, and the first tab is identified as the system default tab. The data model and configuration information of the system default tab are obtained, and a data worksheet view of the system default tab is rendered in the main body area of ​​the spreadsheet. During user operation, the user's operation type is first determined. If it is a command to create a new tab, the tab control bar is rendered within the current single main body area of ​​the spreadsheet, a new tab ID is generated, the data model and configuration information corresponding to the tab ID are determined, and the tab ID is integrated into the tab control bar to form an operable tab. A three-element mapping relationship—user identifier—tab ID—data model—configuration information—is stored. If another target tab is selected, extract the binary mapping relationship corresponding to the current user identifier from the ternary mapping relationship, obtain the target data model and target configuration information of the target tab from the binary mapping relationship, switch the current data model and view configuration of the table body area to the target data model and configuration, and re-render the data worksheet view based on the target data model and configuration information.

[0107] In this embodiment, on the one hand, by introducing pre-rendered tab control bars, users can access different data worksheet views within the same spreadsheet main area through multiple pre-configured operable tabs. Users can quickly switch between different data views within the same interface simply by clicking a tab. Since tab switching is completed within the same container, view states can be independently cached and restored, eliminating the need for users to jump back and forth between different pages when comparing data of different dimensions. This improves the continuity and efficiency of the operation and effectively avoids operation interruptions and context loss caused by page jumps. On the other hand, each tab is independently associated with its own data model and configuration information. When a user selects a new target tab, the system determines the target data model and target configuration information corresponding to the target tab and switches the model and configuration bound to the entire spreadsheet main area. This ensures that each tab's corresponding data worksheet view has an independent and personalized configuration, significantly improving the interface's relevance and flexibility.

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

[0109] Please see Figure 7This illustration shows a schematic diagram of the structure of a multi-tab spreadsheet data processing system provided in an exemplary embodiment of this application. This multi-tab spreadsheet data processing system can be implemented as all or part of an electronic device through software, hardware, or a combination of both. System 1 includes an initialization module 10, a parameter determination module 20, a parameter switching module 30, and a data worksheet view rendering module 40.

[0110] Initialization module 10 is used to render the data worksheet view of the system default tab in the main area of ​​the spreadsheet. The main area of ​​the spreadsheet includes a pre-rendered tab control bar, which provides at least two operable tabs pre-configured by the user, each tab corresponding to a data worksheet view.

[0111] The parameter determination module 20 is used to determine the target data model and target configuration information corresponding to the target tab in response to the user's selection operation of other target tabs in the tab control bar besides the system default tabs;

[0112] The parameter switching module 30 is used to switch the current data model and current view configuration of the system default tab associated with the main body area of ​​the table to the target data model and target configuration information;

[0113] The data worksheet view rendering module 40 is used to render the data worksheet view of the target tab within the main area of ​​the spreadsheet based on the target data model and target configuration information.

[0114] It should be noted that the spreadsheet multi-tab data processing system provided in the above embodiments is only illustrated by the division of the functional modules described above when executing the spreadsheet multi-tab data processing 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 spreadsheet multi-tab data processing system and the spreadsheet multi-tab data processing 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.

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

[0116] In this embodiment, on the one hand, by introducing pre-rendered tab control bars, users can access different data worksheet views within the same spreadsheet main area through multiple pre-configured operable tabs. Users can quickly switch between different data views within the same interface simply by clicking a tab. Since tab switching is completed within the same container, view states can be independently cached and restored, eliminating the need for users to jump back and forth between different pages when comparing data of different dimensions. This improves the continuity and efficiency of the operation and effectively avoids operation interruptions and context loss caused by page jumps. On the other hand, each tab is independently associated with its own data model and configuration information. When a user selects a new target tab, the system determines the target data model and target configuration information corresponding to the target tab and switches the model and configuration bound to the entire spreadsheet main area. This ensures that each tab's corresponding data worksheet view has an independent and personalized configuration, significantly improving the interface's relevance and flexibility.

[0117] This application also provides a computer-readable medium having program instructions stored thereon, which, when executed by a processor, implement the spreadsheet multi-tab data processing method provided in the above-described method embodiments.

[0118] This application also provides a computer program product containing instructions that, when run on a computer, causes the computer to execute the spreadsheet multi-tab data processing method of the various method embodiments described above.

[0119] Please see Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 8 As 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.

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

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

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

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

[0124] 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 8 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 a spreadsheet multi-tab data processing application.

[0125] exist Figure 8In the illustrated electronic device 1000, the user interface 1003 is mainly used to provide an input interface for the user and to obtain the user's input data; while the processor 1001 can be used to call the spreadsheet multi-tab data processing application stored in the memory 1005 and specifically perform the following operations:

[0126] The spreadsheet body area renders the data worksheet view of the system's default tabs. The spreadsheet body area includes a pre-rendered tab control bar, which provides at least two user-configured operable tabs, each tab corresponding to a data worksheet view.

[0127] In response to the user's selection of a target tab in the tab control bar other than the system default tab, determine the target data model and target configuration information corresponding to the target tab;

[0128] Switch the current data model and current view configuration of the system default tab associated with the main table area to the target data model and target configuration information;

[0129] Based on the target data model and target configuration information, render the data worksheet view of the target tab within the main area of ​​the spreadsheet.

[0130] In one embodiment, when the processor 1001 executes the operation to determine the target data model and target configuration information corresponding to the target tab, it specifically performs the following operations:

[0131] Retrieve the pre-stored ternary mapping relationship, which includes the mapping relationship between user identifier, tab ID identifier, data model corresponding to tab ID identifier, and configuration information;

[0132] From the pre-stored ternary mapping relationship, obtain the binary mapping relationship between each first tab ID corresponding to the user's current user ID, the first data model corresponding to each first tab ID, and the first configuration information;

[0133] From the binary mapping relationship, obtain the target data model and target configuration information corresponding to the target tab.

[0134] In one embodiment, when the processor 1001 generates a pre-stored ternary mapping relationship, it specifically performs the following operations:

[0135] Render a tab control bar within the currently displayed single table body area;

[0136] In response to a user instruction to create a new tab for the main body area of ​​the table, a tab ID is generated;

[0137] Determine the data model and configuration information corresponding to the tab ID; the configuration information is the user's global preference configuration or the configuration parameters of the system default template, which are read automatically.

[0138] Integrate the tab ID into the tab control bar to create an operable tab;

[0139] Stores a three-element mapping relationship between the user identifier of the currently operating user, the tab ID identifier, the data model corresponding to the tab ID identifier, and the configuration information.

[0140] In one embodiment, when processor 1001 executes the operation of switching the current data model and current view configuration of the system default tab associated with the table body area to the target data model and target configuration information, it specifically performs the following operations:

[0141] Capture the current view state of the data worksheet view of the system default tab and obtain the historical view state records of the system default tab; the current view state includes at least the cached historical scroll bar position, row selection state, and input box content;

[0142] In local memory, the association between the user's current user identifier, the tab ID of the system default tab, and the historical view status records of the system default tab is stored.

[0143] Remove the main area of ​​the spreadsheet from the current data model and current configuration information, and bind it to the target data model and target configuration information corresponding to the target tab.

[0144] In one embodiment, when the processor 1001 renders a data worksheet view of a target tab within the main area of ​​a spreadsheet based on the target data model and target configuration information, it specifically performs the following operations:

[0145] Determine if the data worksheet view of the target tab is being rendered for the first time;

[0146] If not, restore the cached history view state record of the target tab from memory; the history view state record includes at least the historical scroll bar position, row selection state and input box content cached in the content when the target tab was previously accessed, in order to maintain the continuity of user operation;

[0147] If so, according to the query logic of the target data model, obtain the initial data set from the server, or according to the recovery logic of the target data model, restore the cached data stored in the local device to the initial data set; based on the column configuration, sorting rules and filtering conditions defined in the target configuration information, process the initial data set to generate a formatted dataset for rendering;

[0148] Render the data sheet view of the target tab within the main area of ​​the spreadsheet, based on the cached historical view state records of the target tab or the formatted dataset used for rendering.

[0149] In one embodiment, when the processor 1001 performs the operation of determining whether the data worksheet view of the target tab is being rendered for the first time, the following specific operations are performed:

[0150] From the association relationships, query whether there are any historical view status records associated with the user's current user ID and the tab ID of the target tab page;

[0151] If so, determine that the data worksheet view of the target tab is not being rendered for the first time;

[0152] If not, determine that the data worksheet view of the target tab is being rendered for the first time.

[0153] In one embodiment, when the processor 1001 renders a data worksheet view of the target tab within the main area of ​​the spreadsheet based on the cached historical view state records or a formatted dataset used for rendering, the processor 1001 specifically performs the following operations:

[0154] Retrieve the field-level access permission policies configured for the user from the target configuration information;

[0155] Based on the field-level access permission policy, the cached historical view state records or the formatted dataset used for rendering of the target tab are filtered to hide or remove sensitive data fields that the user is not authorized to view, resulting in a filtered formatted dataset.

[0156] Draw and display the filtered, formatted dataset within the main area of ​​the spreadsheet to obtain the data worksheet view for the target tab.

[0157] In one embodiment, the processor 1001 also performs the following operations:

[0158] Initialize and render a tab control bar above or below the main area of ​​the spreadsheet;

[0159] In response to a user's command to enter the main area of ​​the spreadsheet, retrieve a list of identifiers for at least two pre-configured tabs from the persistent storage configuration associated with the user;

[0160] Based on the list of identifiers, render the operable tabs in the tab control bar;

[0161] From at least two tabs, determine the first tab as the system default tab.

[0162] In one embodiment, when the processor 1001 renders the data worksheet view of the system default tab in the main area of ​​the spreadsheet, it specifically performs the following operations:

[0163] Retrieve default configuration information associated with the user for the system default tab;

[0164] Retrieve the default data model corresponding to the system's default tab and the field-level access permission policy configured for the user;

[0165] Based on the permission policy, the original data set corresponding to the default data model is filtered to remove sensitive data fields that users do not have permission to access, thus obtaining the final data set after permission filtering.

[0166] Based on the column configuration, sorting rules, and filtering conditions defined in the default configuration information, the final data set is formatted to generate the final dataset to be rendered.

[0167] Within the main area of ​​the spreadsheet, a data worksheet view of the system's default tab is drawn and presented based on the dataset to be rendered and the default configuration information.

[0168] In this embodiment, on the one hand, by introducing pre-rendered tab control bars, users can access different data worksheet views within the same spreadsheet main area through multiple pre-configured operable tabs. Users can quickly switch between different data views within the same interface simply by clicking a tab. Since tab switching is completed within the same container, view states can be independently cached and restored, eliminating the need for users to jump back and forth between different pages when comparing data of different dimensions. This improves the continuity and efficiency of the operation and effectively avoids operation interruptions and context loss caused by page jumps. On the other hand, each tab is independently associated with its own data model and configuration information. When a user selects a new target tab, the system determines the target data model and target configuration information corresponding to the target tab and switches the model and configuration bound to the entire spreadsheet main area. This ensures that each tab's corresponding data worksheet view has an independent and personalized configuration, significantly improving the interface's relevance and flexibility.

[0169] 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 program for processing multi-tab data in a spreadsheet 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 program can be a magnetic disk, optical disk, read-only memory, or random access memory, etc.

[0170] 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. A method for processing multi-tab data in a spreadsheet, characterized in that, The method includes: The spreadsheet body area renders the data worksheet view of the system's default tabs. The spreadsheet body area includes a pre-rendered tab control bar, which provides at least two operable tabs pre-configured by the user, each tab corresponding to a data worksheet view. In response to the user's selection of a target tab in the tab control bar other than the system default tab, the target data model and target configuration information corresponding to the target tab are determined; Switching the current data model and current view configuration of the system default tab associated with the main body area of ​​the table to the target data model and target configuration information includes: capturing the current view state of the data worksheet view of the system default tab, and obtaining the historical view state record of the system default tab; the current view state includes at least the cached historical scroll bar position, row selection state, and input box content; storing the association between the user's current user identifier, the tab ID of the system default tab, and the historical view state record of the system default tab in local memory; unbinding the main body area of ​​the spreadsheet from the current data model and current configuration information, and binding the target data model and target configuration information corresponding to the target tab; Based on the target data model and target configuration information, render the data worksheet view of the target tab within the main area of ​​the spreadsheet.

2. The method according to claim 1, characterized in that, Determining the target data model and target configuration information corresponding to the target tab includes: Obtain the pre-stored ternary mapping relationship, which includes the mapping relationship between user identifier, tab ID identifier, data model corresponding to the tab ID identifier, and configuration information; From the pre-stored ternary mapping relationship, obtain the binary mapping relationship between each first tab ID corresponding to the user's current user identifier, the first data model corresponding to each first tab ID, and the first configuration information; From the binary mapping relationship, obtain the target data model and target configuration information corresponding to the target tab.

3. The method according to claim 2, characterized in that, Generate a pre-stored ternary mapping relationship by following these steps: Render a tab control bar within the currently displayed single table body area; In response to a user instruction to create a new tab for the main body area of ​​the table, a tab ID is generated; Determine the data model and configuration information corresponding to the tab ID; the configuration information is the user's global preference configuration or the configuration parameters of the system default template, which are automatically read. The tab ID is integrated into the tab control bar to obtain an operable tab page; The system stores a ternary mapping relationship between the user identifier of the currently operating user, the tab ID identifier, the data model corresponding to the tab ID identifier, and the configuration information.

4. The method according to claim 1, characterized in that, The step of rendering the data worksheet view of the target tab within the main area of ​​the spreadsheet based on the target data model and target configuration information includes: Determine whether the data worksheet view of the target tab is being rendered for the first time; If not, restore the cached history view state record of the target tab from memory; the history view state record includes at least the historical scroll bar position, row selection state and input box content cached in the content when the target tab was previously accessed, in order to maintain the continuity of user operation; If so, according to the query logic of the target data model, the initial data set is obtained from the server, or according to the recovery logic of the target data model, the cached data stored in the local device is restored to the initial data set; based on the column configuration, sorting rules and filtering conditions defined in the target configuration information, the initial data set is processed to generate a formatted dataset for rendering; Render the data worksheet view of the target tab within the main area of ​​the spreadsheet, based on the cached historical view state records of the target tab or the formatted dataset used for rendering.

5. The method according to claim 4, characterized in that, The local memory stores the user's user identifier, the tab ID identifier, and the association between the tab's historical view status records; The step of determining whether the data worksheet view of the target tab is being rendered for the first time includes: From the association relationships, query whether there are any historical view status records associated with the user's current user ID and the tab ID of the target tab page; If so, it is determined that the data worksheet view of the target tab is not being rendered for the first time; If not, the data worksheet view of the target tab is determined to be rendered for the first time.

6. The method according to claim 4, characterized in that, The step of rendering the data worksheet view of the target tab within the main area of ​​the spreadsheet, based on the cached historical view state record of the target tab or the formatted dataset used for rendering, includes: Obtain the field-level access permission policy configured for the user from the target configuration information; According to the field-level access permission policy, the cached historical view state records of the target tab or the formatted dataset used for rendering are filtered to hide or remove sensitive data fields that the user is not authorized to view, and the filtered formatted dataset is obtained. The filtered, formatted dataset is drawn and presented within the main area of ​​the spreadsheet to obtain the data worksheet view of the target tab.

7. The method according to any one of claims 1-6, characterized in that, Before rendering the data worksheet view of the system's default tab in the main area of ​​the spreadsheet, the following is also included: Initialize and render a tab control bar above or below the main area of ​​the spreadsheet; In response to the user's operation command to enter the main area of ​​the spreadsheet, a list of identifiers for at least two pre-configured tabs is obtained from the persistent storage configuration associated with the user; Based on the list of identifiers, render operable tabs in the tab control bar; From the at least two tabs, the first tab is determined to be the system default tab.

8. The method according to any one of claims 1-6, characterized in that, The rendering of the system's default tab data worksheet view in the main area of ​​the spreadsheet includes: Obtain the default configuration information associated with the user for the system default tab; Obtain the default data model corresponding to the system's default tab and the field-level access permission policy configured for the user; Based on the permission policy, the original data set corresponding to the default data model is subjected to field filtering to remove sensitive data fields that the user does not have permission to access, thereby obtaining the final data set after permission filtering. Based on the column configuration, sorting rules, and filtering conditions defined in the default configuration information, the final data set is formatted to generate the final dataset to be rendered. Within the main area of ​​the spreadsheet, based on the dataset to be rendered and the default configuration information, a data worksheet view of the system default tab is drawn and presented.

9. A multi-tab data processing system for spreadsheets, characterized in that, The system includes: An initialization module is used to render the data worksheet view of the system default tab in the main area of ​​the spreadsheet. The main area of ​​the spreadsheet includes a pre-rendered tab control bar, which provides at least two operable tabs pre-configured by the user, each tab corresponding to a data worksheet view. The parameter determination module is used to determine the target data model and target configuration information corresponding to the target tab in response to the user's selection operation of other target tabs in the tab control bar besides the system default tabs; The parameter switching module is used to switch the current data model and current view configuration of the system default tab associated with the main body area of ​​the table to the target data model and target configuration information. This includes: capturing the current view state of the data worksheet view of the system default tab, obtaining historical view state records of the system default tab; the current view state includes at least the cached historical scroll bar position, row selection state, and input box content; storing the association between the user's current user identifier, the tab ID of the system default tab, and the historical view state records of the system default tab in local memory; and unbinding the main body area of ​​the spreadsheet from the current data model and current configuration information, and binding the target data model and target configuration information corresponding to the target tab. The data worksheet view rendering module is used to render the data worksheet view of the target tab within the main area of ​​the spreadsheet, based on the target data model and target configuration information.

Images