Methods, devices, equipment, media, and products for processing table data.

Abstract

We provide methods, devices, equipment, media, and products for processing tabular data that can efficiently and flexibly adjust the content presented on a dashboard according to the needs of different scenarios. [Solution] The method involves pre-configuring authorization information for a second terminal of a data table, and using this authorization information to indicate the access rights of each first terminal to the data in the data table. When the second terminal detects that the authorization information is valid, it presents a dashboard for describing the data analysis results for the data table, and further presents a switch component. This allows the administrator to flexibly configure whether or not to restrict the dashboards presented by each first terminal using the authorization information via the switch component.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and particularly to a method, apparatus, device, medium, and product for processing table data.

Background Art

[0002] For some scenarios, for example, for a data analysis result presentation scenario, in these scenarios, there is a need to present the data analysis result for a data table through a dashboard so that each visitor can check the data analysis result through the dashboard. Here, the dashboard includes a plurality of components, and for any one component, the component is for presenting a result obtained by performing some analysis on the data table, such as results like ranking, histogram, etc.

Summary of the Invention

[0003] To solve the above technical problems, this application provides a method, apparatus, device, medium, and product for processing table data, which is advantageous for improving the user experience.

[0004] To achieve the above object, the technical solution according to this application is as follows.

[0005] This application provides a method for processing table data, including presenting a dashboard for describing a data analysis result for the data table for which permission information indicating the access permission of a first terminal to the data in the data table is pre-configured, presenting a switch component for restricting the dashboard presented to the first terminal with the permission information in response to the permission information being in an effective state, and presenting first prompt information for indicating restricting the dashboard presented to the first terminal with the permission information in response to the switch component being in an on state.

[0006] In one possible embodiment, the method further includes, in response to the switch component being in an off state, presenting a second prompt to indicate that the authorization information does not restrict the dashboard presented to the first terminal.

[0007] In one possible embodiment, the process of presenting the switch component includes presenting the switch component on the dashboard in response to the authorization information being in an active state.

[0008] In one possible embodiment, the dashboard displays an entry indicator for an administration page, and the process of presenting the switch component includes presenting the administration page in response to a trigger operation on the entry indicator, and additionally presenting the switch component on the administration page in response to the authorization information being in an active state.

[0009] In one possible embodiment, after presenting the switch component on the dashboard as described above, the method further includes canceling the presentation of the switch component on the dashboard in response to the authorization information being switched from an enabled state to a disabled state.

[0010] In one possible embodiment, after presenting the switch component on the management page as described above, the method further includes canceling the presentation of the switch component on the management page in response to the authorization information being switched from an enabled state to a disabled state.

[0011] In one possible embodiment, after presenting the switch component as described above, the method further includes saving the state of the switch component and canceling the presentation of the switch component in response to the authorization information being switched from an enabled state to an disabled state, and presenting the switch component in its saved state in response to the authorization information being switched from an disabled state to an enabled state.

[0012] In one possible embodiment, the method further includes, when a state switching request triggered on the switch component and a first request for switching the authorization information from an enabled state to an disabled state are detected simultaneously, executing the first request and presenting a third prompt information, the third prompt information being for indicating that the execution of the state switching request failed because the authorization information is in an disabled state, and the state switching request is for switching the switch component from an off state to an on state, or from an on state to an off state.

[0013] In one possible embodiment, the method is applied to a second terminal, and the method further includes, when a state switching request triggered to the switch component and a second request for canceling the second terminal's administrative rights to the data table are detected simultaneously, executing the second request and presenting a fourth prompt information, the fourth prompt information being for indicating that the execution of the state switching request failed because the second terminal does not have administrative rights to the data table, and the state switching request is for switching the switch component from an off state to an on state, or from an on state to an off state.

[0014] In one possible embodiment, different requests are triggered by different terminals, and the state switching request is triggered by the second terminal.

[0015] In one possible embodiment, a plurality of first terminals are pre-configured in the data table, the method further comprises presenting a preview page in response to a preview operation triggered on the dashboard, the preview page by default presenting the presentation effect on a third terminal of the dashboard, the plurality of first terminals including the third terminal, and updating the preview page in response to a preview target switching operation triggered on the preview page, the preview target switching operation being for instructing a switch from the third terminal to a fourth terminal, the plurality of first terminals including the fourth terminal, and the updated preview page presenting the presentation effect on the fourth terminal of the dashboard.

[0016] The present invention provides a method for processing table data, the method being applied to a first terminal and presenting a dashboard determined based on a data table in which permission information for indicating the first terminal's access rights to data in the data table is pre-configured; presenting a prompt page to indicate that the data permissions for the dashboard have changed in response to a state switching operation triggered on a switch component at a second terminal; and updating the dashboard in response to a trigger operation on an update component on the prompt page, wherein the updated dashboard is constrained by the permission information if the dashboard before the update is not constrained by the permission information and the state switching operation is for instructing the switch component to switch from an off state to an on state, or the updated dashboard is not constrained by the permission information if the dashboard before the update is constrained by the permission information and the state switching operation is for instructing the switch component to switch from an on state to an off state.

[0017] In one possible embodiment, the dashboard comprises a plurality of components, each component for presenting different data analysis results for the data table, and if the dashboard is constrained by the authorization information, the authorization information indicates that the first terminal does not have permission to access a first dataset in the data table, and if the first dataset includes any column or any row in the data table, the presentation process for any component in the dashboard includes, if the key information on which to render the component includes the first dataset, presenting the component using pre-configured content instead of the component, wherein the key information constitutes the data analysis results presented by the component, and the pre-configured content indicates that the first terminal does not have permission to check the data analysis results presented by the component, and if the key information on which to render the component does not include the first dataset, rendering and presenting the component using the data table.

[0018] In one possible embodiment, the dashboard comprises a plurality of components, each component for presenting different data analysis results for the data table, and if the dashboard is constrained by the authorization information, the authorization information indicates that the first terminal does not have permission to access some data in a second dataset in the data table, and if the second dataset includes any one column or any one row in the data table, then for any one component in the dashboard, the presentation process for the component includes rendering and presenting the component by relying on other data in the second dataset, except for the aforementioned data, if the key information on which to render the component includes the second dataset, wherein the key information constitutes the data analysis results presented by the component, and rendering and presenting the component by relying on other data in the second dataset, except for the aforementioned data, if the key information on which to render the component does not include the second dataset, but the second dataset is used in the rendering process for the component.

[0019] The present invention provides a table data processing device comprising: a first presentation unit for presenting a dashboard for describing data analysis results for a data table, which is pre-configured with permission information indicating the access rights of a first terminal to data in the data table; a second presentation unit for presenting a switch component for determining whether or not the permission information restricts the dashboard presented to the first terminal in response to the permission information being in an active state; and a third presentation unit for presenting a first prompt information indicating that the permission information restricts the dashboard presented by the first terminal in response to the switch component being switched from an off state to an on state, or a second prompt information indicating that the permission information does not restrict the dashboard presented by the first terminal in response to the switch component being switched from an on state to an off state.

[0020] The present invention provides a table data processing device, which includes: a fourth presentation unit for presenting a dashboard determined based on a data table in which permission information for indicating the access rights of the first terminal to data in the data table is pre-configured; a fifth presentation unit for presenting a prompt page to indicate that the data permissions of the dashboard have changed in response to a state switching operation triggered on a switch component by a second terminal; and an update unit for updating the dashboard in response to a trigger operation on an update component on the prompt page, wherein if the dashboard before the update is not constrained by the permission information and the state switching operation is for instructing the switch component to switch from an off state to an on state, the updated dashboard is constrained by the permission information, or if the dashboard before the update is constrained by the permission information and the state switching operation is for instructing the switch component to switch from an on state to an off state, the updated dashboard is not constrained by the permission information.

[0021] This application provides an electronic device including a memory for storing instructions or computer programs, and a processor for executing the instructions or computer programs in the memory to perform the table data processing method according to this application.

[0022] The present invention provides a computer-readable medium that, when operated by a device, stores instructions or a computer program that causes the device to execute the table data processing method according to the present invention.

[0023] This application provides a computer program product that includes a computer program containing program code for executing the method of processing table data according to this application, which is mounted on a non-temporary computer-readable medium.

[0024] This invention has at least the following advantages compared to related technologies.

[0025] In the proposed technology, if a second terminal for managing a data table is pre-configured with permission information for the data table, and this permission information is used to indicate the access rights of each first terminal to the data in the data table, then when the second terminal detects that the permission information is valid, it not only presents a dashboard for describing the data analysis results for the data table, but also presents a switch component, thereby allowing the administrator to flexibly configure, via the switch component, whether or not to restrict the dashboard presented by each first terminal with the permission information. In this way, it is possible to flexibly configure, from the dimensions of the dashboard, whether the data used for its statistics is all the data in the data table or only the data to which the visitor has permission. As a result, it is possible to efficiently and flexibly adjust the content presented on the dashboard according to the needs of different scenarios (e.g., an all-public scenario or a scenario that considers role attributes), and furthermore, it is possible to effectively improve the user experience. [Brief explanation of the drawing]

[0026] To more clearly explain the technical solutions in the embodiments of this application or related technologies, the following briefly introduces the drawings that need to be used in the description of the embodiments or related technologies. It is self-evident that the drawings in the following description are only some of the embodiments described in this application. For those skilled in the art, based on these drawings and without creative efforts, other drawings can also be obtained. [Figure 1] It is a flowchart of a method for processing table data applied to a second terminal according to an embodiment of this application. [Figure 2] It is a schematic diagram of a presentation flow of a switch component according to an embodiment of this application. [Figure 3] It is a schematic diagram of a state switching flow of a switch component according to an embodiment of this application. [Figure 4] It is a schematic diagram of a preview page according to an embodiment of this application. [Figure 5] It is a flowchart of a method for processing table data applied to a first terminal according to an embodiment of this application. [Figure 6] It is a schematic diagram of the configuration of a table data processing device according to an embodiment of this application. [Figure 7] It is a schematic diagram of the configuration of a table data processing device according to an embodiment of this application. [Figure 8] It is a schematic diagram of the configuration of an electronic device according to an embodiment of this application.

Embodiments for Implementing the Invention

[0027] Research has revealed that some dashboard implementation solutions, by default, only use dashboards to aggregate data that visitors are authorized to access, and therefore have at least the following drawbacks: Because these solutions only support aggregating data that visitors are authorized to access and not all data, they can only meet the needs of a single scenario (e.g., a scenario that considers role attributes) and fail to meet the needs of other scenarios (e.g., an all-public scenario), impacting the user experience.

[0028] Further research has shown that, to overcome the aforementioned shortcomings, it is possible to manually configure whether the data used by each component in the dashboard for statistical analysis is all data or data to which the visitor has permission.

[0029] Further research revealed that the above solution has the following drawbacks: (1) It has relatively high deployment costs, impacting the user experience. (2) Because an entire dashboard corresponds to one specific scenario, when switching scenarios, all components in the dashboard must be manually reconfigured to determine whether the data used for statistical analysis is all data or data to which the visitor has permission, resulting in relatively high scenario switching costs and impacting the user experience.

[0030] Based on the above research, in order to further improve the user experience, the present invention provides a method for processing table data, wherein permission information is pre-configured for a second terminal of a data table, and said permission information is used to indicate the access rights of each first terminal to the data in the data table, and when the second terminal detects that said permission information is valid, the second terminal not only presents a dashboard for describing the data analysis results for said data table, but also further presents a switch component, thereby allowing the administrator to flexibly configure whether or not to restrict the dashboard presented by each first terminal with said permission information via the switch component, and thus it is possible to flexibly configure from the dimensions of the dashboard whether the data used for its statistics is all the data in said data table or only the data to which the visitor has permission, and as a result it is possible to efficiently and flexibly adjust the content presented on the dashboard according to the needs of different scenarios (e.g., an all-public scenario or a scenario that considers role attributes), and furthermore it is possible to effectively overcome the above-mentioned shortcomings, and in this way the user experience can be effectively improved.

[0031] Furthermore, this application does not limit the entity that implements the method for processing table data according to this application. For example, the method may be applied to terminal equipment. Alternatively, for example, the method may be implemented by a data table data processing process between terminal equipment and a server. Here, the terminal equipment may be a smartphone, computer, personal digital assistant (PDA), tablet, etc. The server may be a standalone server, a cluster server, or a cloud server.

[0032] To enable those skilled in the art to better understand the solutions of this application, the following clearly and fully describes the technical solutions in the embodiments of this application, linking them to the drawings of the embodiments. Clearly, the embodiments described are only a selection of the embodiments of this application, not all of them. All other embodiments derived from the embodiments of this application without the creative effort of those skilled in the art are all within the scope of protection of this application.

[0033] To better understand the technical proposal of this application, the following will describe the proposal with reference to several drawings. As shown in Figure 1, an embodiment of the present application provides a method for processing table data applied to a second terminal, and includes the following steps S101 to S103.

[0034] S101: The second terminal presents a dashboard, which describes the results of data analysis on a data table, and the data table is pre-configured with permission information, which indicates the first terminal's access rights to the data in the data table.

[0035] Here, the second terminal (also called the management terminal) refers to a terminal that has administrative privileges over a data table (for example, the data table shown in Table 1 below), thereby enabling the administrator to perform several administrative tasks over the data table via that terminal. Furthermore, this application does not limit the second terminal, and may be implemented by, for example, a terminal for creating the data table or a terminal to which administrative privileges have been granted. [Table 1]

[0036] A dashboard is obtained by performing statistical analysis on at least one data table so that the dashboard can represent the results of data analysis on that data table. A single dashboard may be used to describe the results of data analysis on one data table, or it may be used to describe the results of data analysis on several data tables; the present invention is not specifically limited to this.

[0037] Furthermore, the dashboard may include multiple components (for example, text component 1, text component 2, bar graph, and ranking shown in Figure 2), and different components may be used to present different data analysis results for the data table (for example, summation, mean, ranking results according to a certain metric) so that the dashboard can present multiple types of data analysis results for the data table.

[0038] Furthermore, this application does not limit the embodiments of the components in the dashboard, and may include, for example, coordinate axis components (e.g., bar graphs, line graphs, bar graphs, area graphs, scattergrams, assembly diagrams, radar charts), pie charts, ring charts, funnel charts, word clouds, metric cards, rankings, Net Promoter Score (NPS) charts, view class components (e.g., components for directly presenting some data in data tables such as Gantt charts, Kanban, and catalogs), text components, or button components.

[0039] Furthermore, to improve data security, permission information may be pre-configured for the data table so that it describes the access rights of each first terminal to the data in the data table (for example, that XXX does not have permission to access the "Region" column in Table 1). This allows for restricting the data that each first terminal can later check based on the permission information. Here, the first terminal (also called an access terminal) refers to a terminal that has been granted permission to access the data table. As a result, the first terminal can check the data for which it has permission from the data table and check the dashboard generated based on the data table.

[0040] Furthermore, this application does not limit the first terminal. For example, in some scenarios, multiple first terminals may be pre-configured for a data table such that each first terminal has the authority to check the data table. As a result, the authority information configured for the data table indicates the access rights of each first terminal to the data in the data table. Also, this application does not limit the embodiments of the multiple first terminals. For example, in some scenarios, the multiple first terminals may include at least one terminal (referred to as a non-second terminal or ordinary terminal) that has only check authority over the data table. In other scenarios, for example, the multiple first terminals may further include at least one terminal (referred to as a second terminal) that has administrative authority over the data table.

[0041] Furthermore, to further improve flexibility, after pre-configuring authorization information for the data table, it may be flexibly configured whether or not to restrict the access rights of different first terminals with said authorization information, depending on several operations on the second terminal. In this way, data access needs in different scenarios can be better met. Note that this application is not limited to the operations described above, and may be implemented by, for example, employing on or off operations triggered on higher-level authorizations as shown in Figure 2. In this way, the authorization information can be enabled by setting it to restrict the access rights of different first terminals with said authorization information so that an on operation is triggered on said higher-level authorization later, and the authorization information can be disabled by setting it not to restrict the access rights of different first terminals with said authorization information so that an off operation is triggered on said higher-level authorization. In this way, it is possible to flexibly control whether or not to enable the authorization information.

[0042] S102: The second terminal, in response to the authorization information being in an active state, presents a switch component, which is used to restrict the dashboard presented to the first terminal with the authorization information.

[0043] In this application, when a terminal (e.g., a second terminal) that presents a dashboard obtained by performing statistical analysis on a data table is detected to have administrative privileges for the data table, and when it is detected that pre-configured permission information for the data table is valid, it can be determined that the user of the terminal may have an administrative need to "configure the dashboard to be used to statistically analyze all data, or to configure the dashboard to be used to statistically analyze data for which the visitor has check privileges." Therefore, in order to better satisfy this need, a switch component (e.g., a switch entry labeled "Statistical Tracking Higher Permissions" as shown in Figure 2) may be presented through the dashboard. This allows the user to flexibly choose whether or not the dashboard performs statistical analysis based on the permission information via the switch component.

[0044] Therefore, the conditions for presenting the switch component are that the terminal for presenting the dashboard rendered based on the data table (e.g., a second terminal) has administrative privileges for the data table, and that the pre-configured permission information for the data table is active (e.g., higher privileges are enabled for the data table). Here, the switch component is for setting whether or not the permission information restricts the dashboard presented by the first terminal. Furthermore, the present application does not limit the embodiment of the switch component, and may be implemented using any component that can be flexibly switched between an on state and an off state (e.g., the switch entry "Statistical Tracking Higher Privileges" shown in Figure 2).

[0045] Furthermore, this application does not limit the method of presenting the switch component. For example, the switch component may be presented directly on the dashboard as a single operable component. This allows the user to flexibly and efficiently configure the dashboard's statistics directly through the switch component without leaving the dashboard. Thus, in one possible embodiment, S102 above may specifically mean that a second terminal additionally presents the switch component on the dashboard in response to the authorization information being in an active state. This is advantageous for simplifying management operations.

[0046] Furthermore, for example, to better conserve space, the above-mentioned switch component may be presented as a single operable component on a subpage of the dashboard (e.g., the administration page 202 shown in Figure 2). This reduces the spatial load on the dashboard. Thus, in one possible embodiment, when an entry indicator for an administration page (e.g., entry indicator 201 shown in Figure 2) is presented on the dashboard, S102 above may specifically present the administration page (e.g., page 202 shown in Figure 2) in response to a trigger operation (e.g., a click operation) on the entry indicator by the second terminal, and may also present an additional switch component (e.g., a switch entry labeled "Statistical Tracking Higher Permissions" shown in Figure 2) on the administration page in response to the permission information being in an active state. This makes it possible to add new components without increasing the spatial load on the dashboard, which is advantageous in improving the presentation effectiveness of the dashboard. Here, the entry indicator is for uniquely identifying the entry on the administration page, and the administration page is for presenting several components that can assist in the management of the dashboard, such as the switch component.

[0047] Furthermore, this application does not limit the default state of the switch component. For example, in some scenarios, such as those where data security is a priority, the switch component is on by default. This allows the dashboard to use statistics for data that visitors have permission to check by default. This is advantageous in better improving data security. Also, in some scenarios, such as those where the user experience of existing users is a priority, the switch component is off by default. This allows the dashboard to use statistics for all data by default. This allows the user to continue using the statistics method they previously used when using the dashboard, avoiding interference with the user.

[0048] Furthermore, in order to further improve the user experience, the above-mentioned switch component satisfies the constraint that, at a minimum, when the control cursor on the second terminal moves above the switch component, it will display a page introducing the functionality of the switch component (for example, page 203 shown in Figure 2). This allows the user to better understand the functionality of the switch component through the page.

[0049] S103: The second terminal, in response to the switch component being in the ON state, presents first prompt information, which indicates that the dashboard presented to the first terminal is constrained by authorization information.

[0050] In this application, when a switch component presented by a second terminal is detected to be in an ON state, the first prompt information (for example, prompt information 204 shown in Figure 3) may be presented to the administrator so that the first prompt information can later restrict the dashboard presented by each first terminal with authorization information.

[0051] Furthermore, this application is not limited to the embodiment of S103 described above. For example, the second terminal may specifically present the first prompt information in such a way that it is used to indicate that the first prompt information restricts the dashboard presented to the first terminal with authorization information in response to the switch component being switched from an off state to an on state.

[0052] Therefore, when it is detected that a switch component presented via the dashboard has been switched from an off state to an on state, it can be determined that the switch component has been turned on. Accordingly, the first prompt information (for example, prompt information 204 shown in Figure 3) may be presented so that the administrator can be informed that the first prompt information will later restrict the dashboard presented by each first terminal with permission information. As a result, the administrator can know from the first prompt information that the statistical data on the current dashboard has been switched from all data to data to which the visitor has permission.

[0053] As can be seen from the contents of S101 to S103 above, the method for processing table data according to the present invention includes, when permission information is pre-configured for a second terminal of a data table and said permission information is used to indicate the access rights of each first terminal to the data in the data table, when the second terminal detects that said permission information is in an effective state, the second terminal not only presents a dashboard for describing the data analysis results for the data table, but also further presents a switch component, thereby allowing the administrator to flexibly configure whether or not to restrict the dashboard presented by each first terminal with said permission information via the switch component. In this way, it is possible to flexibly configure from the dimensions of the dashboard whether the data used for its statistics is all the data in the data table or data to which the visitor has permission, and as a result, it is possible to efficiently and flexibly adjust the content presented on the dashboard according to the needs of different scenarios (e.g., an all-public scenario or a scenario that considers role attributes), and furthermore, it is possible to effectively improve the user experience.

[0054] Furthermore, to improve flexibility, the above method for processing table data may further include step 1 below.

[0055] Step 1: The second terminal, in response to the switch component being in an off state, presents second prompt information to indicate that the dashboard presented to the first terminal is not constrained by authorization information.

[0056] In this application, when a switch component presented by a second terminal is detected to be in an off state, the second prompt information (for example, prompt information 205 shown in Figure 3) may be presented to inform the administrator that the second prompt information will not later restrict the dashboards presented by each first terminal with authorization information.

[0057] Furthermore, the present application does not limit the embodiments of step 1 described above. For example, in response to the switch component being switched from an on state to an off state, a second prompt information may be presented to indicate that the dashboard presented to the first terminal is not restricted by authorization information.

[0058] Therefore, when it is detected that a switch component presented via the dashboard has been switched from an on state to an off state, it can be determined that the switch component has been turned off. Accordingly, a second prompt (for example, prompt information 205 shown in Figure 3) may be presented so that the administrator can be informed that the second prompt information will not later restrict the dashboard presented by each first terminal with permission information. As a result, the administrator can know from the second prompt information that the statistical data on the current dashboard has been switched from data to which the visitor has permission to access to all data.

[0059] Furthermore, in some scenarios, to further enhance the user experience, both the first and second prompt information described above include an entry indicator on the same page (for example, the "See More" entry indicator shown in Figure 3). This allows the user to access the appropriate page, such as a page displaying help center documentation, via the indicator. This application does not limit the embodiments of the indicator. For example, it can be implemented by employing an access link to the help center documentation. The link must also support at least multiple languages.

[0060] Furthermore, when statistical analysis is performed on a data table and a dashboard is obtained, if it is detected that the terminal displaying the dashboard has administrative privileges for the data table, and that the pre-configured permission information for the data table is invalid, it can be determined that there is no need to restrict the visitor's access rights with permission information. As a result, it can be determined that the visitor can access all the data in the data table, and furthermore, that the dashboard can be used to statistically analyze all the data. Therefore, it is not necessary to present a switch component. This avoids confusing the user and is advantageous in improving the user experience.

[0061] As can be seen from this, in one possible embodiment, the method for processing the table data described above may include at least steps S101 to S102 and step 11 below. Here, the execution time of step 11 is slower than the execution time of S102.

[0062] Step 11: The second terminal cancels the presentation of the switch component in response to the authorization information being switched from an enabled state to an disabled state.

[0063] Example 1: If the above switch component is deployed directly to the dashboard, step 11 above may specifically involve the second terminal canceling the presentation of the switch component on the dashboard in response to the authorization information being switched from an enabled state to an disabled state.

[0064] Example 2: If the above switch component is deployed on an administration page (for example, page 202 shown in Figure 2), step 11 above may specifically involve the second terminal canceling the presentation of the switch component on the administration page in response to the authorization information being switched from an enabled state to an disabled state.

[0065] As can be seen from the content of step 11 above, when it is detected that the pre-configured permission information for a data table has been switched from enabled to disabled for a dashboard presented by the second terminal to describe the data analysis results of the data table, it can be determined that there is no need to restrict the visitor's data access rights with that permission information, and as a result, it can be determined that the dashboard will be used to statistically analyze all the data, and furthermore, it can be determined that there is no need for the administrator to manually select the statistical mode for the dashboard. Therefore, the presentation of the switch component, which has directly lost its usefulness, can be canceled. In this way, interference by the switch component can be effectively avoided. As a result, it is advantageous for improving the user experience.

[0066] Research has shown that in some scenarios, administrators may re-enable higher privileges. Therefore, to better improve the user experience, we found that the state of the above switch component from when higher privileges were previously turned off can be reused.

[0067] Therefore, in one possible embodiment, the method for processing the table data described above may include at least steps S101 to S102 and the following steps 21 to 22.

[0068] Step 21: In response to the authorization information being switched from an enabled state to an disabled state, the second terminal saves the state of the switch component so that the saved state represents the state of the switch component when the presentation of the switch component is canceled, for example, an on state or an off state, and cancels the presentation of the switch component.

[0069] Step 22: In response to the authorization information being switched from an invalid state to an enabled state, the second terminal presents the switch component in its saved state so that the newly presented switch component can be restored to the state it was in when the higher-level authorization was last turned off.

[0070] As can be seen from the content of steps 21 to 22 above, when it is detected that the pre-configured permission information for the data table has been switched from enabled to disabled for the dashboard presented by the second terminal to describe the data analysis results of the data table, it is not only necessary to cancel the presentation of the switch component, but also to save the state of the switch component so that the saved state represents the state of the switch component when the higher-level permission was turned off. Then, when it is detected that the permission information has been switched back from disabled to enabled, the presentation of the switch component can be restored directly to the saved state so that the newly presented switch component retains the state of the switch component when the higher-level permission was turned off last time. In this way, the drawbacks of reusing and deploying the switch component can be effectively avoided, and as a result, it is advantageous to improve the user experience.

[0071] Research has shown that in some scenarios, such as those where multiple administrators exist or where multiple requests can be triggered simultaneously on the same device, a phenomenon that can easily lead to confusion can occur when multiple conflicting requests are triggered simultaneously (for example, two requests, "turn off higher privileges" and "turn on a switch component," are triggered simultaneously, or two requests, "cancel administrative privileges on a device" and "the device whose administrative privileges were canceled turns on a switch component," are triggered simultaneously).

[0072] Based on the above research, in order to overcome the above-mentioned shortcomings, the method for processing table data according to the present application may include at least the following steps 31 and / or 32. Here, there is no relationship between the execution time of step 31 and the execution time of step 32; for example, they may be the same, the former may precede the latter, or the latter may precede the former, and the present application is not limited thereto.

[0073] Step 31: When a state switch request triggered on a switch component and a first request to switch authorization information from an enabled state to an disabled state are detected simultaneously, the first request is executed, and a third prompt is presented, the third prompt indicating that the execution of the state switch request failed because the authorization information is in an disabled state, and the state switch request is to switch the switch component from an off state to an on state, or from an on state to an off state.

[0074] Furthermore, this application does not limit the embodiments of step 31, and for the sake of easier understanding, it will be explained below in conjunction with two cases.

[0075] Case 1: In some scenarios, for example, in scenarios that allow multiple requests to be triggered simultaneously on the same terminal, step 31 above specifically involves the second terminal 1 presenting a switch component. If, at the same time that the second terminal 1 triggers a state switching request (e.g., a request to switch from the off state to the on state, or from the on state to the off state) to the switch component, the second terminal 1 also triggers a first request to switch the authorization information from the enabled state to the disabled state, then a conflict in the execution processes of these two requests will be detected. Therefore, the first request, which has a relatively higher priority, may be executed first to switch the authorization information from the enabled state to the disabled state, thereby preventing the switch component from meeting the presentation conditions. As a result, the state switching request triggered on the switch component loses its value, and the second terminal 1 can be directly presented with the prompt "Operation failed. Higher privileges are not enabled in the current data table." The second terminal 1 can then learn from this prompt that the state of the authorization information in the data table has changed.

[0076] Case 2: In some scenarios, for example, in a scenario with multiple administrators, step 31 above specifically involves a first request being triggered by another second terminal (e.g., second terminal 2) to request that the authorization information be switched from enabled to disabled at the same time that the second terminal 1, which is presenting the switch component, triggers a state switch request for the switch component. At this time, a conflict is detected between the execution processes of these two requests. Therefore, the first request, which has a relatively higher priority, may be executed first to switch the authorization information from enabled to disabled, so that the switch component does not meet the presentation conditions. As a result, the state switch request triggered for the switch component loses its value, and the second terminal 1 can be directly prompted with "Operation failed. Higher privileges are not enabled in the current data table." The second terminal 1 can then learn from this prompt that the state of the authorization information in the data table has changed.

[0077] Step 32: When a state switch request triggered on a switch component and a second request to cancel the second terminal's administrative privileges over the data table are detected simultaneously, the second request is executed and a fourth prompt is presented, which indicates that the execution of the state switch request failed because the second terminal does not have administrative privileges over the data table, and the state switch request is to switch the switch component from the off state to the on state, or from the on state to the off state.

[0078] Furthermore, this application does not limit the embodiments of step 32, and for the sake of easier understanding, it will be explained below in conjunction with two cases.

[0079] Case 1: In some scenarios, for example, in scenarios that allow multiple requests to be triggered simultaneously on the same terminal, step 32 above specifically involves a second request being triggered by the second terminal 1, which is presenting the switch component, at the same time that the second terminal 1 triggers a state switch request to the switch component, and at this time, a conflict is detected between the execution processes of these two requests. Therefore, the second request, which has a relatively higher priority, may be executed first to cancel the second terminal 1's management rights to the data table, so that the second terminal 1 no longer has management rights to the data table. As a result, the state switch request triggered by the second terminal 1 is not permitted by its own authority, and furthermore, the state switch request loses its value, and the second terminal 1 can be directly prompted with "Operation failed. You do not have permission to operate." As a result, the second terminal 1 can learn from the prompt that it will no longer have administrative privileges over the data table.

[0080] Case 2: In some scenarios, for example, in a scenario where there are multiple administrators, step 32 above may be interpreted as follows: At the same time that a state switch request is triggered by the second terminal 1 presenting the switch component, another second terminal (e.g., second terminal 2) triggers a second request to revoke the second terminal 1's administrative privileges over the data table, and at this time, a conflict is detected in the execution processes of these two requests. Therefore, the second request, which has a relatively higher priority, may be executed first to revoke the second terminal 1's administrative privileges over the data table, so that the second terminal 1 no longer has administrative privileges over the data table. As a result, the state switch request triggered by the second terminal 1 is not permitted by its own authority, and furthermore, the state switch request loses its value, and the second terminal 1 can be directly presented with the prompt "Operation failed. You do not have permission to operate." As a result, the second terminal 1 can learn from the prompt that it will no longer have administrative privileges over the data table.

[0081] As can be seen from the contents of steps 31 to 32 above, if a conflict is detected between multiple requests triggered simultaneously by the same second terminal or different requests triggered simultaneously by different terminal devices, these requests may be processed sequentially according to priority to avoid the drawbacks of processing these requests simultaneously, such as confusion or insecurity.

[0082] Research has shown that in some scenarios, there may be a need for administrators to preview whether the dashboards that different users will see meet their expectations.

[0083] Based on the above research, in order to better meet the above needs, the present application provides a possible embodiment of a method for processing table data, in which, if a data table is pre-configured with a plurality of first terminals, the method for processing table data may include at least the following steps 41 to 42.

[0084] Step 41: The second terminal, in response to a preview operation triggered on the dashboard, presents a preview page, which by default displays the dashboard's presentation effect on the third terminal, and the above-mentioned multiple first terminals include the third terminal.

[0085] Here, the preview operation is intended to trigger the flow of presenting the preview page. Furthermore, this application does not limit the preview operation. For example, one may first click the "Superior Permissions" button shown in Figure 2 to open the options aggregation page, and then click the preview option presented on the options aggregation page to enter the preview page, for example, page 206 shown in Figure 4.

[0086] Furthermore, the third terminal refers to the first terminal to which the dashboard presented by default (or initially) on the preview page belongs when entering that page, for example, the second terminal mentioned above, or any one of the multiple first terminals mentioned above, or a terminal configured by the user.

[0087] Step 42: The second terminal updates the preview page in response to a preview target switching operation triggered on the preview page, the preview target switching operation being intended to instruct the switching from the third terminal to the fourth terminal, the multiple first terminals including the fourth terminal, and the updated preview page is intended to show the presentation effect of the dashboard on the fourth terminal.

[0088] Here, the preview target switching operation is intended to instruct a switch from the third terminal to the fourth terminal, and this operation is used to change the content presented on the preview page, for example, to request a switch from the dashboard presented by the third terminal (e.g., User A shown in Figure 4) to the dashboard presented by the fourth terminal (e.g., User 1 shown in Figure 4).

[0089] The fourth terminal refers to the preview target specified by the preview target switching operation, for example, User 1 shown in Figure 4.

[0090] As can be seen from the content of steps 41 to 42 above, a second terminal may be configured to enter preview mode, and in that mode, the dashboard that each visitor sees may be configured to check whether it meets their expectations. This is advantageous in improving the management experience.

[0091] Furthermore, this application does not limit the application scenarios of the preview flow described in steps 41 to 42 above. For example, a second terminal presenting a switch component may, upon detecting that the switch component is ON, cause the terminal to add a new component (e.g., the preview option described above) to the dashboard it presents. This allows the user to enter the preview flow by later using the component to trigger a preview operation. In this way, the administrator can verify through the preview mode whether the dashboard viewed by any one visitor matches the access permissions set for that visitor, thereby ensuring that the preview service is provided only in scenarios where the dashboard is generated based on data for which the visitor has permissions, and is also advantageous in avoiding interference with scenarios where the content of the component interferes with scenarios where the dashboard is generated based on all data.

[0092] The research revealed that when a second device is adjusting the statistical methodology for the dashboard, if other devices are accessing the dashboard, the dashboard may not be updated in a timely manner. To overcome this drawback, such as insecurity, it is necessary to update the dashboard presented to other devices in a timely manner.

[0093] Based on the above research, the present invention further provides a method for processing table data applicable to a first terminal, including the following S501 to S503.

[0094] S501: The first terminal presents a dashboard, which is determined based on a data table, which has pre-configured authorization information, and which authorization information indicates the first terminal's access rights to the data in the data table.

[0095] S502: The first terminal, in response to a state switching operation triggered on a switch component by the second terminal, presents a prompt page indicating that the data permissions for the dashboard have changed.

[0096] Here, a state switching operation refers to an operation triggered on the second terminal to adjust the state of a switch component while the first terminal is displaying the dashboard.

[0097] Therefore, if the dashboard presented by the first terminal is not constrained by authorization information, it can be determined that the switch component has already been turned off by the second terminal in the past, and as a result, it can be determined that the state switching operation is used to instruct the switch component presented by the second terminal to switch from the off state to the on state. However, if the dashboard presented by the first terminal is constrained by authorization information, it can be determined that the switch component has already been turned on by the second terminal in the past, and as a result, it can be determined that the state switching operation is used to instruct the switch component presented by the second terminal to switch from the on state to the off state.

[0098] Furthermore, the present invention does not limit the embodiments of the prompt page, and it may be implemented, for example, by employing a popup window method. Here, the copy of the popup window may be the copy, "Dashboard data permissions have been changed. Please refresh and check." The popup window may further include a refresh button, so that the user can refresh the dashboard later by clicking the button.

[0099] S503: The first terminal, in response to a trigger operation on the update component on the prompt page, updates the dashboard, where the dashboard before the update is not constrained by permission information, the state switching operation instructs the switch component to switch from the off state to the on state, and the updated dashboard is constrained by permission information, or the dashboard before the update is constrained by permission information, the state switching operation instructs the switch component to switch from the on state to the off state, and the updated dashboard is not constrained by permission information.

[0100] Here, the update component refers to the component present on the prompt page that triggers the dashboard update flow, such as the refresh button shown above.

[0101] Furthermore, this application does not limit the embodiments of the "updating the dashboard" step described above. For example, the following constraints may be met: If the dashboard before the update is not constrained by permission information and the state switching operation described above is for instructing the switch component to switch from the off state to the on state, then the updated dashboard is constrained by permission information. Or, if the dashboard before the update is constrained by permission information and the state switching operation described above is for instructing the switch component to switch from the on state to the off state, then the updated dashboard is not constrained by permission information.

[0102] As can be seen from the contents of S501 to S503 above, if a second terminal triggers a state switching operation on a switch component presented by any one of the first terminals while the first terminal is viewing the dashboard, it can be determined that the second terminal has adjusted the statistical method of the dashboard. Therefore, a pop-up window may be presented to the first terminal to prompt the user to refresh. The visitor can then trigger the dashboard update flow by clicking the refresh button in the pop-up window. As a result, the visitor can continue to view the updated dashboard. In this way, it is possible to update the dashboard on each first terminal in a timely manner, which is advantageous in improving the user experience.

[0103] Furthermore, this application does not limit the implementation form of restricting the dashboard with permission information. For example, if it is detected that any one component in the dashboard contains data related to the process of determining the data analysis results presented by that component (e.g., intermediate data or the final data presented) that the visitor does not have permission to access, the component cannot be presented, and a pre-configured fallback image that does not have the necessary check permissions is displayed directly at the component's presentation location to inform the visitor that they do not have permission to access the component.

[0104] The study further showed that if data that the visitor does not have permission to access is used in the intermediate data of a component's rendering process (e.g., the process of determining the data analysis results presented by the component), but the final rendering result of the component does not use data that the visitor does not have permission to access, then there is no risk of disclosing unauthorized data to the visitor when presenting the component. This means that the component should be presented to the visitor and not replaced with a pre-configured fallback image that the visitor does not have permission to access, thus improving the user experience.

[0105] Based on the above research, in order to further improve the user experience, the present application provides an implementation solution that constrains each component in a dashboard with permission information, wherein the permission information indicates that a first terminal does not have permission to access a first dataset in a data table (e.g., any one invisible column or any one invisible row), and the first dataset contains any one column or any one row in the data table, the process for determining what to present in any component in the dashboard includes the following:

[0106] If the key information on which the component is rendered is used to construct the data analysis results presented by the component so that the user can directly see the key information within the component, and the key information includes a first dataset, then it can be determined that there is data in the component's presentation that the visitor does not have permission to check. Therefore, instead of the component, pre-configured content (for example, content such as a fallback image that the user does not have permission to check) may be used to present the data, and this pre-configured content may be used to indicate that the first terminal does not have permission to check the data analysis results. As a result, the visitor can avoid seeing data they do not have permission to see from the component. However, if the key information does not include the first dataset, then it can be determined that there is no data in the component's presentation that the visitor does not have permission to check, and even if the first dataset is used in the process of obtaining the content presented by the component, the visitor still cannot see the first dataset through the component because the component does not directly expose it. Therefore, the component can be rendered and presented based on the data table. In this way, under the premise of avoiding the exposure of data that visitors do not have permission to access, it is possible to present as many data analysis results as possible. To facilitate understanding, this will be explained below in relation to three cases.

[0107] Case 1: If any component in the dashboard presented by the first terminal has invisible columns (or invisible rows) in the key information on which rendering that component is based (e.g., a component of the data analysis results presented by that component), then it can be determined that there is a risk that data that the visitor does not have permission to access may be exposed in that component. Therefore, the component should not be presented, and a fallback image that does not have direct checking authority should be presented at the component's presentation location.

[0108] Furthermore, as shown in (1) to (3) below, different components have different characteristics, so by making the key information of different components different, differences are created in the processing criteria of different components.

[0109] (1) For a first type of component (e.g., a coordinate axis component, a pie chart, or a ring chart), if the content presented by the component consists of key information of the component and the user can directly see the key information through the component, then if it is detected that an invisible column is used in the key information, it can be determined that the component cannot be presented properly and it can be replaced with a fallback image for which the system does not have checking authority. Here, the key information may include the type of the coordinate axis component (e.g., X-axis), the series of the coordinate axis component (e.g., Y-axis), the basis for grouping the coordinate axis component, the sector group of the pie chart (or ring chart), the sector values ​​of the pie chart (or ring chart), etc.

[0110] (2) With respect to the second type of component (e.g., funnel chart, word cloud, metric card, ranking, NPS chart), if the content presented by the component is obtained by processing the key information of the component so that the user can directly see the processing results of the key information through the component, then if it is detected that an invisible column has been used in the key information, it can be determined that the component cannot be presented properly and may be replaced with a fallback image that does not have checking privileges. Here, the key information may include funnel layers or data statistics of a funnel chart, keyword fields of a word cloud, statistical methods of metric cards, ranking fields or ranking basis of a ranking, NPS basis of an NPS chart, etc.

[0111] (3) For a third type of component (e.g., a text component or a button component), the key information used to render the component is not related to an invisible column, since the content presented by the component is unlikely to relate to any data column in the data table (e.g., an invisible column) and is unlikely to relate to the processing results of that data column. As a result, the component is not affected by the invisible column.

[0112] Furthermore, for any one component, the key information used to render that component may be set manually in advance, or it may be determined based on the component's own attributes, and this application does not specifically limit this.

[0113] Case 2: If, for any one component in the dashboard presented by the first terminal, there are no invisible columns (or invisible rows) in the key information on which to render the component, but invisible columns (or invisible rows) are used in the rendering process of the component, it can be determined that these invisible columns (or invisible rows) will not be exposed when the component is presented. Therefore, the component can be presented directly and successfully. For example, if the column "Region" shown in Table 1 above belongs to the invisible column, and the filtering condition corresponding to the component is Region = Region 1, the type corresponding to the component is Sales Date, and the series corresponding to the component is Sales Amount, then the filtering is enabled, the component is rendered successfully, and the rendered component satisfies the constraint that the type is Sales Date for Region 1, the series is Sales Amount for Region 1, the drill-down data of the component is used only to present rows 2 through 6 in Table 1, but the column "Region" needs to be hidden.

[0114] Furthermore, if, for any one component, the intermediate process involved in rendering that component includes global filtering, component filtering, or component data ordering, and an invisible column is used for filtering or ordering, it is sufficient to return the filtering and ordering results correctly and continue the subsequent rendering process based on those results, ensuring that the data in the invisible column and the processing results for that invisible column do not appear in the finally rendered component.

[0115] Furthermore, if a drill-down popup window exists for any one component, and filtered and ordered graph calculation data is presented in that popup window, then invisible columns in the data source will be hidden, and rows for which the filtering or ordering conditions have been activated will be displayed.

[0116] Case 3: If, for any one component in the dashboard presented by the first terminal, the key information on which the component is rendered does not contain any invisible columns (or rows), and no invisible columns (or rows) are used in the rendering process of the component, then it can be determined that the component does not involve invisible columns (or rows). Therefore, the component can be presented normally directly.

[0117] Research has shown that in some scenarios, for example, when a single user has multiple role attributes, the user's data access permissions to a data table are the union of the data access permissions for all role attributes, which can result in extracted columns (or extracted rows) in the user's data access permissions to the data table. For example, the user may have permission to check some data in a certain column (for example, the top 6 data in the "Profit" column in Table 1 above). As a result, it was found that how to use these extracted columns when generating dashboards becomes a challenge. Here, extracted columns, also called partially visible columns, refer to data columns where some data is visible and some data is not. As a result, extracted columns seen by visitors will appear as a state where some cells have data and some cells do not.

[0118] Based on the above research, in order to solve the above problems, the present application further provides the above-mentioned solution for processing extracted columns. In this solution, when each component in the dashboard is constrained by permission information, if the permission information indicates that a first terminal does not have permission to access some data in a second dataset (e.g., extracted columns or extracted rows) in a data table, and the second dataset contains any one column or any one row in the data table, then for any one component in the dashboard, the process for determining what to present in that component includes the following:

[0119] If the key information on which the component is rendered is used to construct the data analysis results presented by the component so that the user can directly see the key information in the component, and the key information includes a second dataset, then the component is rendered and presented in such a way that the content presented by the component does not include the aforementioned data, relying on data other than the aforementioned data in the second dataset. If the key information does not include a second dataset, but the second dataset is used in the rendering process of the component, then the component is rendered and presented in such a way that the content presented by the component does not include the aforementioned data, relying on data other than the aforementioned data in the second dataset. If the key information does not include a second dataset, and the second dataset is not used in the rendering process of the component, then the component may be rendered and presented in such a way that it does not include the aforementioned data. To facilitate understanding, three cases are explained below.

[0120] Case 1: If, for any one component in the dashboard presented by the first terminal, there is an extracted column (or extracted row) in the key information on which the component is rendered, it can be determined that some of the content presented by the component can be presented, but some cannot. Therefore, the component may be obtained by having the visitor participate in statistical processing using the data for which they have permission in the extracted column (or extracted row). In this way, the component is used only to present content related to data for which the visitor has permission (also called visible data), and does not present content related to data for which the visitor does not have permission (also called invisible data). For example, if the column labeled "Profit" in Table 1 above belongs to the extracted column, and the top six data points in that extracted column belong to data that the visitor has permission to access, and the other data belong to data that the visitor does not have permission to access, then the extracted column is used as the key information on which to render the component, and the type corresponding to the component is "Sales Date", and the series corresponding to the component is "Profit", then the component is rendered based on the statistical analysis results of rows 2 to 7 in Table 1, and the rendered component satisfies the constraint that the type is used to describe the sales dates related to rows 2 to 7, and the series is used to describe the profits related to rows 2 to 7. As a result, the drill-down data of the component is used only to present rows 2 to 7 in Table 1.

[0121] Since different components have different characteristics, different key information for different components can create differences in the processing criteria for those components. Specifically, if a sampled column is used for the key information of the first type of component or the second type of component described above, that component will be used to render based on the visible data in the sampled column, and the third type of component described above will not be affected by the sampled column. Furthermore, if a sampled column is used for grouping in a fourth type of component, such as a view class component, the content presented in that component will be grouped based on the data row where the visible data in the sampled column is located. If a sampled column is placed in the parent record of a table, that component will be used to present data whose parent record is the data row where the visible data in the sampled column is located. If a sampled column is used when placing the date and time in a Gantt chart, that component will be used to present the data row where the visible data in the sampled column is located. If a sampled column is used in a visible field, that component will be used to present the data row where the visible data in the sampled column is located. If a sample column is used on a Kanban or catalog cover, the component is used to present the cover of the data row in which the visible data in the sample column is located, and rows for which the user is not authorized are considered not to be present.

[0122] Case 2: If, for any one component in the dashboard presented by the first terminal, there are no extracted columns (or extracted rows) in the key information on which the component is rendered, but the extracted columns (or extracted rows) are used in the rendering process of the component, the visible data in the extracted columns (or extracted rows) may be used to participate in the rendering process and obtain and present the component. In this way, the component is used solely to present data analysis results determined based on the visible data. For example, if the column labeled "Profit" in Table 1 above belongs to the extracted column, and the top 6 data points in that extracted column are visible while the other data points are invisible, and the filtering condition for the component is Profit > 200, the type for the component is Sales Date, and the series for the component is Sales Amount, then the filtering is enabled and the component is rendered by filtering only rows 2 through 7 of Table 1, so that the rendered component satisfies the constraints that the type includes 2024 / 11 / 02, 2024 / 11 / 04, and 2024 / 11 / 06, and the series includes 203, 500, and 300. As a result, the drill-down data for the component is used only for rows 2 through 7 of Table 1.

[0123] Furthermore, if the intermediate process rendering any one component includes global filtering, component filtering, or component data ordering, and if a sampled column is used for filtering or ordering, the data rows where the visible data in the sampled column is located should be included in the filtering and ordering, and the subsequent rendering process should be performed based on the returned results.

[0124] Furthermore, if a drill-down popup window exists for any one component, and the graph displayed for that component includes a extracted column, then only the visible data in the filtered column will be displayed.

[0125] As can be seen from the above, the proposed technology of this application has the following advantages: (1) This application places the statistical data either all data or data to which the visitor has permission from the dashboard dimensions. This allows users to flexibly choose whether to perform statistics using all data or data to which the visitor has permission, depending on different usage scenarios of the dashboard (e.g., all public scenario or multi-role attribute scenario). In this way, it is advantageous to improve the flexibility of scenario switching. (2) When rendering any one component in the dashboard, if an invisible column is used in the intermediate process related to that component (e.g., filtering or ordering), this application ensures that the intermediate process is executed successfully so that the visitor only sees the final rendering result and is unaware of the intermediate process, and that the finally rendered component does not present the invisible column. In this way, it is advantageous to improve the user experience. (3) The present invention further provides a processing method for extracted columns or extracted rows that can meet the needs in scenarios where the permission allocation of data to which a visitor has authority is refined down to the cell level, and as a result the present invention is applicable to scenarios where roles intersect, such as extracted columns, resulting from the same user having multiple role attributes.

[0126] Based on the method for processing table data according to the embodiment of the present application, the embodiment of the present application further provides a table data processing device. The following will be interpreted and explained in conjunction with Figure 6. Figure 6 is a schematic diagram of the configuration of the table data processing device according to the embodiment of the present application. Technical details of the table data processing device according to the embodiment of the present application should be referred to in the description of the table data processing method above.

[0127] As shown in Figure 6, the table data processing device 600 according to the embodiment of the present invention is A first presentation unit 601 for presenting a dashboard for describing data analysis results for a data table, which is pre-configured with permission information indicating the first terminal's access rights to the data in the data table, In response to the fact that the authorization information is in an effective state, a second presentation unit 602 presents a switch component for restricting the dashboard presented to the first terminal with the authorization information, The system includes a third presentation unit 603 for presenting first prompt information to indicate that the dashboard presented to the first terminal is restricted by the authorization information in response to the switch component being in an ON state.

[0128] In one possible embodiment, the third presentation unit 603 is further used to present a second prompt information indicating that the dashboard presented to the first terminal is not restricted by the authorization information, in response to the switch component being in an off state.

[0129] In one possible embodiment, the second presentation unit 602 is specifically used to additionally present the switch component on the dashboard in response to the authorization information being in an active state.

[0130] In one possible embodiment, the dashboard displays an entry indicator for an administration page, and the second display unit 602 is used specifically to display the administration page in response to a trigger operation on the entry indicator, and to display the switch component on the administration page in response to the authorization information being in an active state.

[0131] In one possible embodiment, the table data processing device 600 further includes a first cancellation unit for canceling the presentation of the switch component on the dashboard in response to the authorization information being switched from an enabled state to an disabled state, after having presented the switch component on the dashboard.

[0132] In one possible embodiment, the table data processing device 600 further includes a second cancellation unit for canceling the presentation of the switch component on the management page in response to the authorization information being switched from an enabled state to an disabled state, after the switch component has been presented on the management page.

[0133] In one possible embodiment, the table data processing device 600 further includes a third cancellation unit for saving the state of the switch component and canceling the presentation of the switch component in response to the authorization information being switched from an enabled state to an disabled state, and a presentation recovery unit for presenting the switch component in the saved state in response to the authorization information being switched from an disabled state to an enabled state.

[0134] In one possible embodiment, the table data processing device 600 further includes a first processing unit for executing the first request and presenting a third prompt information when it detects simultaneously a state switching request triggered on the switch component and a first request for switching the authorization information from an enabled state to an disabled state, the third prompt information for indicating that the execution of the state switching request failed because the authorization information is in an disabled state, and the state switching request for switching the switch component from an off state to an on state, or from an on state to an off state.

[0135] In one possible embodiment, the table data processing device 600 further includes a second processing unit for executing the second request and presenting a fourth prompt information when it detects simultaneously a state switching request triggered on the switch component and a second request for canceling the second terminal's administrative rights over the data table, the fourth prompt information for indicating that the execution of the state switching request failed because the second terminal does not have administrative rights over the data table, and the state switching request for switching the switch component from an off state to an on state, or from an on state to an off state.

[0136] In one possible embodiment, different requests are triggered by different terminals, and the state switching request is triggered by the second terminal.

[0137] In one possible embodiment, a plurality of first terminals are pre-configured in the data table, and the processing device 600 for the table data includes a preview trigger unit for presenting a preview page in response to a preview operation triggered on the dashboard, wherein the preview page, by default, presents the presentation effect on the third terminal of the dashboard, and the plurality of first terminals further includes a preview trigger unit including the third terminal, and a target switching unit for updating the preview page in response to a preview target switching operation triggered on the preview page, wherein the preview target switching operation is for instructing a switch from the third terminal to a fourth terminal, wherein the plurality of first terminals include the fourth terminal, and the updated preview page presents the presentation effect on the fourth terminal of the dashboard.

[0138] As can be seen from the above description of the table data processing device 600, the operating principle of the device 600 is that when permission information is pre-configured for a data table and said permission information is used to indicate the access rights of each first terminal to the data in the data table, when the second terminal detects that said permission information is valid, the second terminal not only presents a dashboard for describing the data analysis results for said data table, but also further presents a switch component. This allows the administrator to flexibly configure, via the switch component, whether or not to restrict the dashboard presented by each first terminal with said permission information, and thus flexibly configure from the dashboard dimensions whether the data used for its statistics is all the data in said data table or only the data to which the visitor has permission. As a result, it is possible to efficiently and flexibly adjust the content presented on the dashboard according to the needs of different scenarios (e.g., an all-public scenario or a scenario that considers role attributes), and furthermore, the user experience can be effectively improved.

[0139] Based on the method for processing table data according to the embodiment of the present application, the embodiment of the present application further provides a table data processing device. The following will be interpreted and explained in conjunction with Figure 7. Figure 7 is a schematic diagram of the configuration of the table data processing device according to the embodiment of the present application. Technical details of the table data processing device according to the embodiment of the present application should be referred to in the description of the table data processing method above.

[0140] As shown in Figure 7, the table data processing device 700 according to the embodiment of the present invention is A fourth display unit 701 for displaying a dashboard determined based on the data table in which permission information indicating the access rights of the first terminal to the data in the data table is pre-configured, A fifth presentation unit 702 for presenting a prompt page to indicate that the data permissions for the dashboard have changed in response to a state switching operation triggered on the switch component at the second terminal, Update unit 703 for updating the dashboard in response to a trigger operation on the update component on the prompt page, wherein the dashboard before the update is not restricted by the permission information, the state switching operation instructs the switch component to switch from the off state to the on state, and the updated dashboard is restricted by the permission information, or the dashboard before the update is restricted by the permission information, the state switching operation instructs the switch component to switch from the on state to the off state, and the updated dashboard is not restricted by the permission information.

[0141] In one possible embodiment, the dashboard comprises a plurality of components, each component for presenting different data analysis results for the data table, and if the dashboard is constrained by the authorization information, the authorization information indicates that the first terminal does not have permission to access a first dataset in the data table, and if the first dataset includes any column or any row in the data table, the presentation process for any component in the dashboard includes, if the key information on which to render the component includes the first dataset, presenting instead the component using pre-configured content, wherein the key information constitutes the data analysis results presented by the component, and the pre-configured content indicates that the first terminal does not have permission to check the data analysis results presented by the component, and if the key information on which to render the component does not include the first dataset, rendering and presenting the component using the data table.

[0142] In one possible embodiment, the dashboard comprises several components, each component for presenting different data analysis results for the data table, and if the dashboard is constrained by permission information, the permission information indicates that the first terminal does not have permission to access some data in a second dataset in the data table, and if the second dataset includes any one column or any one row in the data table, then for any one component in the dashboard, the presentation process for the component includes rendering and presenting the component by relying on other data in the second dataset, except for the aforementioned data, if the key information on which to render the component includes the second dataset, wherein the key information constitutes the data analysis results presented by the component, and rendering and presenting the component by relying on other data in the second dataset, except for the aforementioned data, if the key information on which to render the component does not include the second dataset, but the second dataset is used in the rendering process for the component.

[0143] As can be seen from the above description of the table data processing device 700, the operating principle of the device 700 is such that when a visitor is viewing the dashboard via the device 700, the second terminal can determine that the second terminal has adjusted the statistical method of the dashboard when the second terminal triggers a state switching operation on a switch component. Therefore, the device 700 may be presented with a pop-up window to prompt the user to refresh. The visitor can then trigger the dashboard update flow by clicking the refresh button in the pop-up window. As a result, the visitor can continue to view the updated dashboard. In this way, it is possible to update the dashboard on terminals other than the second terminal in a timely manner, which is advantageous in improving the user experience.

[0144] Furthermore, embodiments of the present application provide an electronic device comprising a memory for storing instructions or computer programs, and a processor for executing the instructions or computer programs in the memory to perform any one embodiment of the table data processing method according to embodiments of the present application.

[0145] Referring to Figure 8, a schematic diagram of the configuration of an electronic device 800 suitable for realizing an embodiment of the present disclosure is shown. The terminal devices in the embodiment of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablets), PMPs (portable multimedia players), and in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in Figure 8 is merely an example and does not impose any limitations on the functions and scope of use of the embodiment of the present disclosure.

[0146] As shown in Figure 8, the electronic device 800 may include a processing unit (e.g., a central processing unit, graphics processor, etc.) 801, which can perform various appropriate operations and processes by programs stored in read-only memory (ROM) 802 or programs loaded from storage device 808 into random access memory (RAM) 803. RAM 803 further stores various programs and data necessary for the operation of the electronic device 800. The processing unit 801, ROM 802, and RAM 803 are interconnected via bus 804. An input / output (I / O) interface 805 is also connected to bus 804.

[0147] Generally, an input device 806, including, for example, a touchscreen, touch panel, keyboard, mouse, camera head, microphone, accelerometer, and gyroscope; an output device 807, including, for example, a liquid crystal display (LCD), speaker, and oscillator; a storage device 808, including, for example, magnetic tape and hard disk; and a communication device 809 may be connected to the I / O interface 805. The communication device 809 enables the electronic device 800 to exchange data with other devices via wireless or wired communication. Figure 8 shows an electronic device 800 with various devices, but it should be understood that there is no intention to require that all of the shown devices be implemented or equipped. More or less of the devices may be implemented or equipped instead.

[0148] In particular, according to embodiments of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product which includes a computer program containing program code for performing the method shown in the flowchart, which is mounted on a non-temporary computer-readable medium. In such embodiments, the computer program may be downloaded and installed from a network by a communication device 809, or installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by the processing unit 801, it performs the above-described functions as limited in the manner of embodiments of the present disclosure.

[0149] The electronic devices according to the embodiments of this disclosure belong to the same inventive concept as the methods according to the embodiments described above, and technical details not described in detail in these embodiments can be found in the embodiments described above, and these embodiments achieve the same beneficial effects as the embodiments described above.

[0150] The embodiment of the present invention further provides a computer-readable medium that, when operated by the device, stores instructions or a computer program that causes the device to execute any one embodiment of the table data processing method according to the embodiment of the present invention.

[0151] The computer-readable medium described above in this disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. The computer-readable storage medium may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specifically, the computer-readable storage medium may include, but is not limited to, an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program, which can be used in or in combination with an instruction execution system, apparatus, or device. In this disclosure, the computer-readable signal medium may include a data signal propagated in the baseband or a data signal partially propagated in the carrier wave, which contains computer-readable program code. The data signals propagated in this manner may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium may further be any computer-readable medium other than a computer-readable storage medium, and such computer-readable medium can transmit, propagate, or transmit programs used in or in combination with instruction execution systems, apparatus, or devices. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to electric wires, optical cables, RF (radio frequency), or any suitable combination thereof.

[0152] In some embodiments, clients and servers can communicate using any currently known or future-developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communications (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed networks.

[0153] The computer-readable media described above may be included in the electronic device described above, or it may be a standalone entity not implemented in the electronic device.

[0154] The computer-readable medium described above contains one or more programs, and when these one or more programs are executed by the electronic device, the electronic device is made to perform the method described above.

[0155] Computer program code for performing the operations disclosed herein can be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java®, Smalltalk, and C++, and general procedural programming languages ​​such as C or similar languages. The program code may run entirely on a user computer, partially on a user computer, as a standalone software package, partially on a user computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user computer by any network, including a local area network (LAN) or wide area network (WAN), or to an external computer (for example, via the Internet using an Internet service provider).

[0156] The flowcharts and block diagrams in the drawings illustrate the implementable system architectures, functions, and operations of systems, methods, and computer program products relating to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or part of code, which includes one or more executable instructions for implementing a specified logic function. In some alternative implementations, the functions represented in a block may occur in a different order than those shown in the drawings. For example, two consecutively shown blocks may be executed substantially in parallel, or, depending on the function, they may be executed in reverse order. Each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, may be implemented by a dedicated system based on hardware that performs a specified function or operation, or by a combination of dedicated hardware and computer instructions.

[0157] The means relating to the embodiments of this disclosure may be implemented in software or in hardware. Herein, the name of the means / module may not be limited to the means itself.

[0158] The functions described herein may be performed by at least partially one or more hardware logic units. For example, exemplary hardware logic units that can be used may include, but are not limited to, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SOCs), and complex-programmable logic devices (CPLDs).

[0159] In the context of this disclosure, a machine-readable medium may be a tangible medium that contains or stores a program used by or in combination with an instruction execution system, device, or apparatus. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatus, or any suitable combination thereof. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0160] In this specification, each example is described progressively, with emphasis on the differences between each example and the others. Identical or similar parts between examples should be referenced to one another. The descriptions of systems or apparatus disclosed in the examples are relatively simplified to correspond to the methods disclosed in the examples; relevant parts should be referred to in the description of the methods.

[0161] In this application, "at least one (item 1)" means one or more, and "multiple" means two or more. "And / or" is used to describe the relationship between related objects and indicates that there may be three relationships. For example, "A and / or B" may represent three cases: A exists only, B exists only, and A and B exist simultaneously. A and B may be singular or plural. The letter " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c may represent a, b, c, "a and b", "a and c", "b and c", or "a, b and c", where a, b, and c may be singular or plural.

[0162] In this specification, relational terms such as “First” and “Second” are used solely for the purpose of distinguishing one entity or operation from another entity or operation, and do not require or imply that such an actual relationship or order exists between these entities or operations. Furthermore, the terms “include,” “contain,” or any other variant thereof, by indicating non-exclusive inclusion, mean that a process, method, article, or apparatus containing a series of elements includes not only those elements but also other elements not explicitly stated, or elements specific to such process, method, article, or apparatus. Unless further restrictions are imposed, an element limited by “include one…” does not exclude other identical elements from being included in a process, method, article, or apparatus containing the aforementioned element.

[0163] Steps of methods or algorithms described in relation to the embodiments disclosed herein may be carried out directly by hardware, by software modules executed by a processor, or by a combination thereof. The software modules may be located in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art.

[0164] The above description of the disclosed embodiments will enable those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Accordingly, the present invention is not limited to these embodiments herein and has the broadest scope that conforms to the principles and novel features disclosed herein.

Claims

1. A method for processing table data, To present a dashboard for describing the data analysis results for the data table, in which permission information for indicating the access rights of the first terminal to the data in the data table is pre-configured, In response to the fact that the aforementioned authorization information is in an effective state, a switch component for restricting the dashboard presented to the first terminal with the aforementioned authorization information is presented, A method characterized by including, in response to the switch component being in an ON state, presenting first prompt information to indicate that the authorization information restricts the dashboard presented to the first terminal.

2. The method according to claim 1, further comprising presenting a second prompt information to indicate that the authorization information does not restrict the dashboard presented to the first terminal in response to the switch component being in an off state.

3. The process for presenting the switch component is as follows: In response to the fact that the aforementioned permission information is in an active state, the switch component is added to the dashboard. Or, The dashboard displays an entry indicator for the management page, and the process for displaying the switch component is as follows: The method according to claim 1, characterized in that it includes presenting the management page in response to a trigger operation on the entry indicator, and additionally presenting the switch component on the management page in response to the authorization information being in a valid state.

4. After adding the switch component to the dashboard, the method, The further includes canceling the presentation of the switch component on the dashboard in response to the permission information being switched from an enabled state to an disabled state, Or, After adding the switch component to the management page, the method is as follows: The method according to claim 3, further comprising canceling the presentation of the switch component on the management page in response to the authorization information being switched from an enabled state to an disabled state.

5. After presenting the aforementioned switch component, the method is as follows: In response to the authorization information being switched from an enabled state to an disabled state, the state of the switch component is saved and the presentation of the switch component is canceled. The method according to claim 1, further comprising presenting the switch component in a saved state in response to the authorization information being switched from an invalid state to an enabled state.

6. The method according to claim 1, further comprising: when a state switching request triggered on the switch component and a first request for switching the authorization information from an enabled state to an disabled state are detected simultaneously, the first request is executed and a third prompt information is presented, wherein the third prompt information indicates that the execution of the state switching request failed because the authorization information is in an disabled state, and the state switching request is for switching the switch component from an off state to an on state, or switching the switch component from an on state to an off state.

7. This method is applied to the second terminal, The method according to claim 1, further comprising: when a state switching request triggered on the switch component and a second request for canceling the second terminal's administrative privileges over the data table are detected simultaneously, the second request is executed and a fourth prompt information is presented, the fourth prompt information being for indicating that the execution of the state switching request failed because the second terminal does not have administrative privileges over the data table, and the state switching request is for switching the switch component from an off state to an on state, or from an on state to an off state.

8. The method according to claim 7, characterized in that different requests are triggered by different terminals, and the state switching request is triggered by the second terminal.

9. Multiple first terminals are pre-configured in the aforementioned data table. This method is In response to a preview operation triggered on the dashboard, a preview page is presented, wherein the preview page, by default, displays the presentation effect of the dashboard on a third terminal, and the plurality of first terminals include the third terminal. The method according to claim 1, further comprising updating the preview page in response to a preview target switching operation triggered on the preview page, wherein the preview target switching operation is for instructing a switch from the third terminal to the fourth terminal, the plurality of first terminals include the fourth terminal, and the updated preview page is for presenting the dashboard's display effect on the fourth terminal.

10. A method for processing table data, the method being applied to a first terminal, This method is To present a dashboard determined based on the data table in which permission information indicating the access rights of the first terminal to the data in the data table is pre-configured, In response to a state switching operation triggered on the switch component at the second terminal, a prompt page is presented to indicate that the data permissions for the dashboard have changed. A method characterized by updating the dashboard in response to a trigger operation on the update component on the prompt page, wherein the dashboard before the update is not constrained by the permission information, the state switching operation is for instructing the switch component to switch from the off state to the on state, and the updated dashboard is constrained by the permission information, or the dashboard before the update is constrained by the permission information, the state switching operation is for instructing the switch component to switch from the on state to the off state, and the updated dashboard is not constrained by the permission information.

11. The dashboard includes multiple components, each of which is used to present different data analysis results for the data table. If the dashboard is restricted by the permission information, and the permission information indicates that the first terminal does not have permission to access the first dataset in the data table, and the first dataset includes any column or any row in the data table, then for any one component in the dashboard, the presentation process for that component is: If the key information on which the component is rendered includes the first dataset, the presentation is made using pre-configured content instead of the component, wherein the key information constitutes the data analysis results presented by the component, and the pre-configured content indicates that the first terminal does not have the authority to check the data analysis results presented by the component. The method according to claim 10, characterized in that, if the key information on which to render the component does not include the first dataset, the method further comprises rendering and presenting the component based on the data table.

12. The dashboard includes multiple components, each of which is used to present different data analysis results for the data table. If the dashboard is restricted by the permission information, and the permission information indicates that the first terminal does not have permission to access some of the data in the second dataset in the data table, and the second dataset includes any one column or any one row in the data table, then for any one component in the dashboard, the presentation process for that component is: If the key information on which to render the component includes the second dataset, the component is rendered and presented by relying on data other than the aforementioned data in the second dataset, wherein the key information constitutes the data analysis results presented by the component. The method according to claim 10, characterized in that, although the key information on which to render the component does not include the second dataset, if the second dataset is used in the rendering process of the component, the component is rendered and presented by relying on data other than the aforementioned data in the second dataset.

13. A processing device for table data, A first presentation unit for presenting a dashboard for describing data analysis results for a data table, which is pre-configured with permission information indicating the access rights of a first terminal to the data in the data table, A second presentation unit for presenting a switch component for restricting the dashboard presented to the first terminal with the permission information in response to the permission information being in an effective state, A table data processing device comprising: a third presentation unit for presenting first prompt information to indicate that the dashboard presented to the first terminal is restricted by the authorization information in response to the switch component being in an ON state.

14. A processing device for table data, A fourth display unit for displaying a dashboard determined based on the data table, in which permission information indicating the first terminal's access rights to the data in the data table is pre-configured; A fifth presentation unit for displaying a prompt page indicating that the data permissions for the dashboard have changed in response to a state switching operation triggered on the switch component at the second terminal, A table data processing device comprising: an update unit for updating the dashboard in response to a trigger operation on the update component on the prompt page, wherein the dashboard before the update is not constrained by the permission information, the state switching operation instructs the switch component to switch from the off state to the on state, and the updated dashboard is constrained by the permission information; or the dashboard before the update is constrained by the permission information, the state switching operation instructs the switch component to switch from the on state to the off state, and the updated dashboard is not constrained by the permission information.

15. Memory for storing instructions or computer programs, An electronic device comprising a processor for executing the instructions or computer programs in the memory to perform the method according to any one of claims 1 to 12.

16. A computer-readable medium characterized in that, when operated by a device, it stores instructions or a computer program that causes the device to perform the method described in any one of claims 1 to 12.

17. A computer program product characterized by including a computer program containing program code for performing the method described in any one of claims 1 to 12, which is mounted on a non-temporary computer-readable medium.

Images