Intelligent question-based dashboard management method and device, medium and product

Abstract

A kind of dashboard management method, device, medium and product based on intelligent question, at least involve intelligent question technical field, method includes: in response to first management operation for first component, display component configuration interface;In response to the input operation executed for component configuration interface, obtain input information, input information includes component basic information and at least one second component in instrument panel interface analysis logic for component, component basic information includes the component relationship of first component and second component;In response to the configuration operation executed for component configuration interface, based on input information, the metadata of first component is generated, metadata is used to generate the analysis result in first component and the management authority for configuring first component, analysis result corresponds with analysis logic, management authority is determined at least by component relationship, realizes the deep integration of automated data analysis and dashboard tool.

Description

Technical Field

[0001] This content relates at least to the field of intelligent data query technology, specifically to a dashboard management method, device, medium, and product based on intelligent data query. Background Technology

[0002] Dashboards are tools for visualizing data and displaying the current status of key business metrics to users. Traditional dashboards lack the ability to provide insights into the data, requiring users to possess professional data analysis skills to extract valuable information from massive amounts of data. Summary of the Invention

[0003] This content section is provided to briefly introduce the concepts, which will be described in detail in the examples section later. This content section is not intended to identify key or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0004] Firstly, a dashboard management method based on intelligent query data is provided, including: In response to the first management operation on the first component, the component configuration interface is displayed; In response to an input operation performed on the component configuration interface, input information is obtained, wherein the input information includes basic component information and analysis logic for at least one second component within the dashboard interface, and the basic component information includes the component relationship between the first component and the at least one second component; In response to a configuration operation performed on the component configuration interface, metadata of the first component is generated based on the input information. The metadata is used to generate analysis results in the first component and to configure management permissions for the first component. The analysis results correspond to the analysis logic, and the management permissions are determined at least through the component relationship.

[0005] Secondly, a dashboard management device based on intelligent data is provided, comprising: The first response module is used to respond to the first management operation for the first component and display the component configuration interface; The second response module is used to respond to an input operation performed on the component configuration interface and obtain input information, wherein the input information includes basic component information and analysis logic for at least one second component in the dashboard interface, and the basic component information includes the component relationship between the first component and the at least one second component; The third response module is used to respond to the configuration operation performed on the component configuration interface, and generate metadata of the first component based on the input information. The metadata is used to generate analysis results in the first component and to configure the management permissions of the first component. The analysis results correspond to the analysis logic, and the management permissions are determined at least through the component relationship.

[0006] Thirdly, a computer-readable medium is provided having a computer program stored thereon, wherein the computer program, when executed by a processing device, implements the steps of the dashboard management method described in the first aspect.

[0007] Fourthly, an electronic device is provided, comprising: A storage device on which computer programs are stored; A processing device is configured to execute the computer program in the storage device to implement the steps of the dashboard management method described in the first aspect.

[0008] Fifthly, a computer program product is provided, comprising a computer program, wherein when executed by a processor, the computer program implements the steps of the dashboard management method described in the first aspect.

[0009] The above technical solution provides a component configuration interface for users to input information, thereby configuring the metadata of the first component. The metadata configured based on the analysis logic is used to support automated analysis of data in the second component, that is, to achieve automated generation of analysis results in the first component. In addition, the metadata configured based on component relationships can realize the configuration of management permissions for the first component, providing a data foundation for seamless collaboration between the first and second components in the dashboard interface and flexible management of the first component, thereby achieving deep integration of automated data analysis and dashboard tools.

[0010] Other features and advantages of the technical solution will be described in detail in the following examples section. Attached Figure Description

[0011] The above and other features, advantages, and aspects of the technical solution will become more apparent when considered in conjunction with the accompanying drawings and the following examples. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale. In the drawings: Figure 1 These are schematic diagrams illustrating application environments under certain circumstances; Figure 2 This is a flowchart illustrating a smart query-based dashboard management method under certain circumstances; Figure 3This is another flowchart illustrating a smart query-based dashboard management method in some scenarios; Figure 4 This is a block diagram of a smart query-based dashboard management device shown in some scenarios; Figure 5 These are schematic diagrams of the structure of electronic devices shown under certain circumstances. Detailed Implementation

[0012] The technical solution will now be described in more detail with reference to the accompanying drawings. Although certain scenarios are shown in the drawings, it should be understood that the technical solution can be implemented in various forms and should not be construed as limited to the scenarios described herein. Rather, these scenarios are provided to provide a more thorough and complete understanding of the technical solution. It should be understood that the accompanying drawings and the scenarios described are for illustrative purposes only and are not intended to limit the scope of protection of the technical solution.

[0013] It should be understood that the steps described in the method implementation may be performed in different orders and / or in parallel. Furthermore, the method implementation may include additional steps and / or omit the steps shown. The scope of the technical solution is not limited in this respect.

[0014] The term "comprising" and its variations as used herein can be open-ended, meaning "including but not limited to". The term "based on" can mean "at least partially based on". The term "one case" means "at least one case"; the term "another case" means "at least one additional case"; the term "some cases" means "at least some cases". Definitions of other terms will be given in the following description.

[0015] It should be noted that the concepts of "first" and "second" mentioned here are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions performed by these devices, modules or units or their interdependencies.

[0016] It should be noted that the terms "one" and "more" used here are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0017] The names of the messages or information exchanged between the multiple devices in the implementation are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0018] It is understandable that before using the technical solutions provided here, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in accordance with relevant laws and regulations, and their authorization should be obtained through appropriate means.

[0019] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations described herein.

[0020] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0021] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of the technical solution. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the technical solution.

[0022] At the same time, it is understood that the data involved in the technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of relevant laws, regulations and related provisions.

[0023] Figure 1 These are schematic diagrams illustrating application environments under certain circumstances, for reference only. Figure 1 The client 101 can provide an interactive interface (such as a component configuration interface) for users to perform a series of interactive operations with the client 101 through these interfaces to realize a dashboard management method based on intelligent data. The client 101 can be a device such as a mobile phone or laptop.

[0024] Figure 2 This is a flowchart illustrating a smart data-based dashboard management method under certain circumstances. This smart data-based dashboard management method can be... Figure 1 The client 101 shown executes as follows: Figure 2 As shown, the dashboard management method based on intelligent data may include steps S210, S220 and S230.

[0025] In step S210, in response to the first management operation for the first component, the component configuration interface is displayed.

[0026] Intelligent query is a data query and analysis tool based on artificial intelligence technology. For example, it can utilize the natural language understanding capabilities of a large language model (i.e., a large model) to understand the intent of a user's question in natural language form, and then convert the intent understanding result into a structured query statement. After that, it combines data sources such as databases or chart data to perform data queries and return the query results to the user.

[0027] This allows for the integration of metadata into the components within the dashboard using intelligent data analysis. For example, the visualization (i.e., analysis results) presented by the first component in the dashboard interface can be generated from metadata obtained through intelligent data analysis. The generation of metadata for the first component can be found in the following related content.

[0028] In step S220, in response to an input operation performed on the component configuration interface, input information is obtained, wherein the input information includes basic component information and analysis logic for at least one second component within the dashboard interface, and the basic component information includes the component relationship between the first component and at least one second component.

[0029] The component configuration interface can provide at least one configuration item for users to perform input operations. This configuration item can include a dialogue system for intelligent data retrieval, which can provide dialog boxes to enable user interaction with the large model. For example, the dialog box can provide input for analysis logic, which includes an analysis approach for data analysis of at least one second component within the dashboard interface. Based on this analysis logic, the content within the second component is interpreted. The second component can be a chart component within the dashboard interface; therefore, the purpose of interpreting data charts (graphs) within the chart component can be achieved. The following example uses a chart component as the second component for illustration. Of course, the second component or its charts can also be described through the input analysis logic; that is, the analysis logic can include the second component to be analyzed or its charts.

[0030] Users can input configuration items corresponding to the component's basic information to obtain this information. Alternatively, users can also input component basic information through the dialog box and the interactive features of the larger model. The component relationships in the basic information can be parent-child or sibling relationships; please refer to the following content for information on parent-child and sibling relationships.

[0031] In step S230, in response to the configuration operation performed on the component configuration interface, metadata of the first component is generated based on the input information. The metadata is used to generate the analysis results in the first component and to configure the management permissions of the first component. The analysis results correspond to the analysis logic, and the management permissions are determined at least through the component relationship.

[0032] Understandably, the metadata generated based on the input information is used to load the first component on the dashboard interface, obtain analysis results, and manage other components (such as lifecycle management).

[0033] The metadata obtained based on the analysis logic configuration is used to characterize the logic for obtaining the analysis results. This logic includes the calculation method of the analysis results and the data that needs to be referenced, etc. The analysis results are generated through this logic. As an example, the logic can be code. When the first component is loaded in the dashboard interface, executing this code generates the corresponding analysis results, which are then displayed in the dashboard interface as the first component carrying the analysis results. It can be understood that the analysis results are obtained by analyzing the data charts in the second component of the dashboard interface.

[0034] As shown above, component relationships can include sibling relationships or parent-child relationships. When loading the first component based on the metadata corresponding to the component relationship, the loaded component can be granted specific management permissions, such as layout management permissions, linkage permissions, or lifecycle management permissions. Detailed explanations and descriptions can be found below. Furthermore, different component relationships can be set according to different analysis scenarios.

[0035] The sibling relationship indicates that the first and second components belong to the same level. For example, both the first and second components are native components within the dashboard interface. By configuring this relationship, the first component can share a unified component registration mechanism, layout coordinate system, drag-and-drop, scaling, and copying operation protocols. The first component can be placed anywhere in the dashboard, and its size and display style can be freely adjusted. It has an independent lifecycle (creation / update / deletion) that does not depend on other components. The first component can be saved, referenced, and configured independently, and supports reuse across dashboards or pages—advantages inherent to native components—making it suitable for scenarios with flexible component layout. Therefore, under such a sibling relationship, the first component can have at least lifecycle management permissions and layout management permissions.

[0036] The parent-child relationship can be used to represent that a first component can be a child component of a second component. That is, the first component can be attached to the second component, forming a hierarchical structure from parent chart to child chart. By configuring this relationship, the position, lifecycle, etc., of the first component can be fully inherited from the second component, forming a strong binding between them. For example, when the second component moves its position, deletes, or updates chart data, the first component can automatically follow. This relationship is suitable for... Figure 1 The analytical scenario for interpretation refers to the scenario where all chart components in the dashboard need to be interpreted. Therefore, under this parent-child relationship, the first component can at least have linkage permissions.

[0037] Parent-child relationships can also be used to represent that a first component can act as the parent component of a second component, forming a report-style structure centered on the first component (i.e., the analysis results). The first component can contain one or more second components; that is, the analysis logic can target multiple second components. In this scenario, such a parent-child relationship can be set so that when loading and displaying the dashboard interface, the analysis conclusion can be determined first, and then the charts can be automatically organized, conforming to the "conclusion first" business reporting logic and suitable for scenarios where multiple charts are interpreted simultaneously. Therefore, similar to the parent-child relationship where the first component can act as a child component of the second component, the first component can at least have linkage permissions. When acting as a parent component, the first component can also be considered a native component, thus possessing lifecycle management permissions and layout management permissions.

[0038] In addition to component relationships, basic component information can also include basic attribute information, such as size attributes, position attributes, and runtime attributes. The metadata generated from this information can be used to configure the visual display of the first component in the dashboard interface or to configure linked permissions. For example, when loading the first component based on the metadata corresponding to its position attribute information, the first component can be loaded into the corresponding position within the dashboard interface according to that metadata.

[0039] The first component is text-based, and the second component is chart-based. Therefore, the above technical solution creates a dashboard interface combining text and graphics. Furthermore, a component configuration interface is provided for users to input information, thereby configuring the metadata of the first component. The metadata configured based on the analysis logic supports automated analysis of data in the second component, enabling automated generation of analysis results. Additionally, the metadata configured based on component relationships allows for the configuration of management permissions for the first component. This provides a data foundation for seamless collaboration between the first and second components within the dashboard interface, as well as flexible management of the first component, thus achieving deep integration of automated data analysis with dashboard tools.

[0040] In some cases, management permissions include linkage permissions. The above-mentioned dashboard management method based on intelligent data may also include the following steps: in response to the first component having linkage permissions and the data chart of the third component in the dashboard interface changing, an analysis result is generated based on the metadata and the changed data chart; based on the analysis result, the first component in the dashboard interface is updated, wherein the third component is any component of at least one second component.

[0041] As can be seen from the above, whether the first component has linkage permissions can be configured based on the component's basic information.

[0042] For example, when the component relationship represents a parent-child relationship, it can indicate that the first component has linkage permission. As another example, when the component relationship represents a sibling relationship, linkage permission can still be configured based on the basic information of other components. Continuing from the above example, this other basic information can include runtime attributes. Users can directly input instructions to the large model in natural language to configure the values ​​of runtime attributes. The large model, based on its understanding of these instructions, configures the values ​​of the runtime attributes. As another example, the component configuration interface can provide configuration items corresponding to runtime attributes. Responding to input operations on these configuration items, the values ​​of the runtime attributes are configured. For example, the value of the runtime attribute can include "yes" or "no." If configured as "yes," the first component is determined to have linkage permission; if configured as "no," the first component is determined not to have linkage permission. Furthermore, the configuration of whether a component has linkage permission can be implemented at a finer granularity. For example, the value of the runtime attribute can be a chart identifier or a component identifier. Thus, the first component only has the corresponding linkage permission when the chart corresponding to the chart identifier or the component corresponding to the component identifier changes, thereby achieving fine-grained customization of linkage between components.

[0043] In the dashboard interface, the content displayed in the first loaded component (including analysis results) is derived from the analysis of the data charts in the third component. The filters associated with the third component can adjust the data in the charts in real time, thus modifying the corresponding charts. Therefore, the data charts of the first and third components can be bound together (through configuring linkage permissions). Then, when the data charts in the third component change, the first component responds to the change, generating analysis results based on metadata and the changed charts. This allows for the regeneration of analysis results based on the new chart data, updating the first component and achieving inter-component linkage. Specifically, the retrieval logic can be executed based on the data in the changed charts to re-retrieve the analysis results.

[0044] In some cases, when updating the first component within the dashboard interface, an incremental update method can be used, that is, only updating the content that has changed, such as only updating the analysis results in the first component, thereby reducing the resources required for the update.

[0045] In some situations, when the first component has linkage permissions and the data chart of the third component in the dashboard interface changes, the first component in the dashboard interface can be automatically or manually refreshed. Of course, the automatic or manual refresh method can be understood as another type of component basic information, namely the refresh method. Therefore, the refresh method can be configured to be either automatic or manual.

[0046] With the automatic refresh method, after the analysis results are reacquired, the first component in the dashboard interface can be automatically updated based on the reacquired analysis results without requiring secondary confirmation from the user.

[0047] For the manual refresh method, the above steps of updating the first component in the dashboard interface based on the reacquired analysis results can be implemented in the following way: in response to the update operation for the first component, update the first component in the dashboard interface based on the reacquired analysis results.

[0048] Of course, the update operation here is triggered by the user. As an example, after re-acquiring the analysis results, a confirmation update control or a cancellation update control can be displayed. If the user clicks the confirmation update control, it is determined that the user has performed an update operation on the first component. Conversely, if the user does not click the confirmation update control or the cancellation update control, it is determined that the user has not performed an update operation on the first component, and therefore there is no need to perform the step of updating the first component in the dashboard interface based on the re-acquired analysis results.

[0049] In some cases, sibling relationships and parent-child relationships (i.e., the first component can be the parent component of the second component) can both indicate that the first component can be used independently of the second component and as the original component in the dashboard interface, thereby enabling the independent management of the first component in the dashboard interface, such as lifecycle management and / or layout management.

[0050] Therefore, the above-mentioned dashboard management method based on intelligent data may further include the following steps: in response to the first component having lifecycle management permissions and performing a second management operation on the first component within the dashboard interface, performing lifecycle management corresponding to the second management operation; or in response to the first component having layout management permissions and performing a third management operation on the first component within the dashboard interface, performing layout management corresponding to the third management operation.

[0051] The second management operation could be, for example, a component deletion operation, used to manage the lifecycle of the first component in the dashboard interface, i.e., deleting the first component. The third management operation could be, for example, a drag-and-drop operation, which allows managing the layout of the first component in the dashboard interface, i.e., changing the position of the first component in the dashboard interface.

[0052] The above solution supports lifecycle management and / or layout management of the first component, improving the flexibility of managing the first component in the dashboard interface.

[0053] In some scenarios, the first management operation can be a component addition operation. When the first component is an empty configuration component, in response to the component addition operation for the first component in the dashboard interface, the component configuration interface is directly displayed, automatically entering edit mode when creating a new empty component and reducing unnecessary clicks. Additionally, the first management operation can also be other operations used to enable configuration of the first component.

[0054] In some cases, the input information is also used to indicate multiple data sources. The step of generating metadata of the first component based on the input information in response to the configuration operation performed on the component configuration interface may include the following steps: in response to the configuration operation performed on the component configuration interface, calling multiple data sources based on the input information; generating metadata based on the analysis logic in the input information and the multiple data sources called, which is used to generate the analysis results in the first component.

[0055] As an example, multiple data sources may include chart data from the second component, metadata (such as fields) in the chart data, and attribution reports. The attribution reports may be generated by the attribution module and are used to characterize the attribution of outliers and the reports generated based on the attribution results. The outliers may include metrics related to the chart data of the second component or metrics related to the analysis logic.

[0056] By using the above methods, it is possible to support the reference of various data sources, thereby improving the accuracy of metadata and, consequently, the reliability of the analysis results generated based on that metadata.

[0057] In some scenarios, when a user performs an input operation, a floating layer can display available data sources after the user enters a preset symbol in the component configuration interface. Where multiple data sources exist, the floating layer can categorize and display different types of data sources, or different preset symbols can be set for different types of data sources. After entering the corresponding preset symbol, the floating layer displays the corresponding type of data source, allowing users to directly select from the displayed content and quickly reference the data source.

[0058] In some cases, the analysis logic can include multiple types, and the input information also includes a preset template. This preset template is configured with placeholders, and each placeholder is associated with the analysis result corresponding to each analysis logic. In other words, a template can be provided to combine different analysis results, so that analysis results for different analysis needs can be displayed in a single component. These different analysis needs can be for different second components, different data charts in the same component, and / or different analysis logics.

[0059] It is understandable that a preset template can be considered a type of metadata for the first component, enabling personalized configuration of the preset template. As an example, the component configuration interface can provide an area for configuring preset templates. In this case, the aforementioned dashboard management method based on intelligent queries can further include the following steps: in response to an adjustment operation on a target placeholder in the component configuration interface, adjusting the position of the target placeholder in the preset template, wherein the target placeholder is any placeholder among all placeholders, and this adjustment operation is used to adjust the content structure of the preset template.

[0060] For example, the adjustment operation can be a drag operation targeting a placeholder. Based on the drag operation, the position of the target placeholder in the preset template can be changed, thereby realizing the adjustment of the content structure of the entire preset template (i.e., the interpretation order of different analysis results in the preset template), so as to support the flexible adjustment of the interpretation order between multiple analysis results when the first component needs to present multiple analysis results.

[0061] In some cases, the content displayed in the first component can be generated in the following way, including the analysis results corresponding to each analysis logic: Based on the metadata generated by the analysis logic, the analysis results are generated; placeholders in the preset template are replaced with the analysis results associated with the placeholders; and the replaced results are used as the content. After generating the analysis results, by directly backfilling the analysis results into the preset template, a data analysis report that meets the user's interpretation needs (i.e., interpretation order) can be quickly obtained.

[0062] In some cases, following the examples of the aforementioned preset template and various analysis logics, the dashboard management method based on intelligent data analysis may further include the following steps: in response to a recommendation request, obtaining dependency information; and generating adjustment suggestions based on the dependency information, wherein the adjustment suggestions are used to describe the recommended position of at least one placeholder in the preset template.

[0063] As shown above, a dialog box can be provided to configure metadata. Therefore, during the metadata configuration process in the component configuration interface, the user can input information for adjusting the content structure of the preset template through the dialog box, and request adjustment suggestions from the large model based on this information. After receiving the recommendation request, the large model obtains the dependency information, and then, through the understanding capabilities of the large model, generates and outputs the corresponding adjustment suggestions based on the dependency information.

[0064] By using the methods described above, we can provide users with adjustment suggestions, thereby improving the accuracy of the content structure in the preset templates.

[0065] In some cases, dependency information can include multiple types of information to improve the accuracy of adjustment suggestions. For example, dependency information may include a first prompt, a second prompt, and chart data from the dashboard interface. The first prompt may represent the content structure information of the adjustment preset template entered by the user through the dialog box; the second prompt is used to represent the default prompt set by the dialog system, which may include a reference interpretation structure.

[0066] In some cases, when providing adjustment suggestions, the reasons for the adjustments can also be provided, so that users can quickly determine whether to accept the adjustment suggestions based on the reasons.

[0067] Figure 3 This is another flowchart illustrating a smart query-based dashboard management method in some scenarios, see reference. Figure 3 After entering the component configuration interface, a dialog box allows users to perform input operations to obtain input information. After the user completes the input operation and submits it (i.e., triggers the configuration operation executed on the component configuration interface), the input information is processed. Figure 3 The dialog (as shown) is initiated by extracting referenced charts, fields, and attribution reports from the input information obtained from the dialog through a large model. Based on multiple data sources (i.e., charts, fields, and attribution reports) and the analysis logic in the input information, the acquisition logic is generated.

[0068] The component configuration interface provides a preview function for the analysis results. (Continue to refer to...) Figure 3 In response to a triggered preview operation, the system can execute acquisition logic, generate and display analysis results for the user to preview, allowing the user to determine if they are satisfied with the current analysis results. If satisfied, it can respond to a user-triggered save operation, persisting the metadata generated by the acquisition logic as the metadata of the first component. This allows the first component to be loaded, displayed, and managed based on this metadata when loaded in the dashboard interface. If the user is not satisfied with the current analysis results, they can continue to interact with the larger model, re-describe the input information, and regenerate the analysis results.

[0069] Based on the same concept, a dashboard management device based on intelligent data is provided. Figure 4 This is a block diagram of a smart query-based dashboard management device shown in some scenarios, with reference to... Figure 4 The smart query-based dashboard management device 400 includes: The first response module 401 is used to respond to the first management operation for the first component and display the component configuration interface. The second response module 402 is used to respond to an input operation performed on the component configuration interface and obtain input information, wherein the input information includes basic component information and analysis logic for at least one second component in the dashboard interface, and the basic component information includes the component relationship between the first component and the at least one second component; The third response module 403 is used to respond to the configuration operation performed on the component configuration interface and generate metadata of the first component based on the input information. The metadata is used to generate analysis results in the first component and to configure management permissions of the first component. The analysis results correspond to the analysis logic, and the management permissions are determined at least through the component relationship.

[0070] In some cases, the management permissions include linkage permissions, and the dashboard management device 400 based on intelligent data queries further includes: The fourth response module is used to respond to the first component having the linkage permission and the data chart of the third component in the dashboard interface changing, and to generate the analysis result based on the metadata and the changed data chart; An update module is used to update the first component in the dashboard interface based on the analysis results, wherein the third component is any one of the at least one second component.

[0071] In some cases, the management permissions include lifecycle management permissions and / or layout management permissions, and the smart data-based dashboard management device 400 further includes: The fifth response module is used to respond to the first component having the lifecycle management permission and to perform lifecycle management corresponding to the second management operation of the first component within the dashboard interface; The sixth response module is used to respond to the first component having the layout management permission and to perform layout management corresponding to the third management operation of the first component within the dashboard interface.

[0072] In some cases, the input information is also used to indicate multiple data sources, and the third response module 403 is further used for: In response to the configuration operation performed by the component configuration interface, the various data sources are invoked based on the input information; Metadata is generated based on the analysis logic in the input information and the various data sources invoked, wherein the metadata is used to generate the analysis results in the first component.

[0073] In some cases, the analysis logic includes multiple types, and the input information also includes a preset template. The preset template is configured with placeholders, and each placeholder is associated with the analysis result corresponding to each of the analysis logics. The dashboard management device 400 based on intelligent query data also includes: An adjustment module is used to respond to an adjustment operation for a target placeholder in the component configuration interface, and to adjust the position of the target placeholder in the preset template, wherein the target placeholder is any one of the placeholders, and the adjustment operation is used to adjust the content structure of the preset template; The content displayed in the first component is generated in the following manner, the content including the analysis results corresponding to each of the analysis logics: the analysis results are generated based on the metadata generated by the analysis logic, the placeholders in the preset template are replaced with the analysis results associated with the placeholders, and the replaced results are used as the content.

[0074] In some cases, the analysis logic includes multiple types, and the input information also includes a preset template. The preset template is configured with placeholders, and each placeholder is associated with the analysis result corresponding to each of the analysis logics. The dashboard management device 400 based on intelligent query data also includes: The acquisition module is used to retrieve dependency information in response to recommendation requests; The recommendation module is used to generate adjustment suggestions based on the dependency information, wherein the adjustment suggestions are used to describe the recommended position of at least one of the placeholders in the preset template.

[0075] The implementation principles of each module in the aforementioned intelligent data-based dashboard management device 400 can be referred to the explanations and descriptions in the aforementioned related methods. Furthermore, the intelligent data-based dashboard management device has the technical effects that can be achieved by the aforementioned related methods, and the technical effects can be referred to the above content.

[0076] Based on the same concept, a computer-readable medium is provided that stores a computer program thereon, wherein when the computer program is executed by a processing device, it implements the steps of the above-described method, and the computer-readable medium has the technical effects that can be achieved by implementing the above-described related methods, and the technical effects can be referred to the above content.

[0077] Based on the same concept, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, it implements the steps of the above-described method, and the computer program product has the technical effects that can be achieved by implementing the above-described related methods, and the technical effects can be referred to the above content.

[0078] Based on the same concept, an electronic device is provided, comprising: A storage device on which computer programs are stored; A processing device is used to execute the computer program in the storage device to implement the steps of the above method, and the electronic device has the technical effects that can be achieved by implementing the above-mentioned related methods, and the technical effects can be referred to the above content.

[0079] The following is for reference. Figure 5 It shows an electronic device 500 suitable for implementing the above-mentioned technical solution (e.g., Figure 1 The diagram shows the structure of the client device. Terminal devices can include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Personal Computers), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs (Televisions), desktop computers, etc. Figure 5 The electronic device shown is merely an example and should not be construed as limiting its functionality or scope of use.

[0080] like Figure 5 As shown, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, the ROM 502, and the RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0081] Typically, the following devices can be connected to the input / output interface 505: input devices 506 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 507 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 508 including, for example, magnetic tape, hard disk, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0082] In particular, depending on certain circumstances, the processes described in the above-referenced flowchart can be implemented as computer software programs. For example, a computer program product is provided, comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. This computer program can be downloaded and installed from a network via communication device 509, or installed from storage device 508, or installed from read-only memory 502. When the computer program is executed by processing device 501, it performs the functions defined in the above-described methods.

[0083] It should be noted that the aforementioned computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are 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, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In one case, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In another case, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (Radio Frequency), etc., or any suitable combination thereof.

[0084] In some implementations, 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 communication (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 peer-to-peer networks (e.g., ad-hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0085] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0086] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: display a component configuration interface in response to a first management operation on a first component; obtain input information in response to an input operation performed on the component configuration interface, wherein the input information includes basic component information and analysis logic for at least one second component within the dashboard interface, the basic component information including the component relationship between the first component and the at least one second component; and generate metadata for the first component based on the input information in response to a configuration operation performed on the component configuration interface, wherein the metadata is used to generate analysis results in the first component and to configure management permissions for the first component, the analysis results corresponding to the analysis logic, and the management permissions being determined at least through the component relationship.

[0087] Computer program code for performing the above operations can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include, but are not limited to, object-oriented programming languages, as well as conventional procedural programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0088] The flowcharts and block diagrams in the accompanying figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products under various scenarios. In this respect, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the figures. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0089] The modules mentioned above can be implemented in software or hardware. In some cases, the name of a module does not constitute a limitation on the module itself. For example, the first response module can also be described as "a module that displays the component configuration interface in response to a first management operation on the first component".

[0090] The functions described above can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Parts (ASSPs), Systems on Chips (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0091] In this context, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. 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, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0092] The above description is merely illustrative and explains the technical principles employed. Those skilled in the art should understand that the scope of the technical solution is not limited to specific combinations of the above-described technical features, but also includes other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features provided herein that have similar functions.

[0093] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Multitasking and parallel processing may be advantageous in certain environments. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the technical solution. Certain features described in the context of a single example can also be implemented in combination in a single example. Conversely, various features described in the context of a single example can also be implemented individually or in any suitable sub-combination in multiple examples.

[0094] Although the technical solution has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims. Regarding the aforementioned apparatus, the specific manner in which each module performs its operation has already been described in detail in the section concerning the method, and will not be elaborated upon here.

Claims

1. A dashboard management method based on intelligent query data, comprising: In response to the first management operation on the first component, the component configuration interface is displayed; In response to an input operation performed on the component configuration interface, input information is obtained, wherein the input information includes basic component information and analysis logic for at least one second component within the dashboard interface. The basic component information includes the component relationship between the first component and the at least one second component. The component relationship includes a parent-child relationship or a sibling relationship. The parent-child relationship is used to indicate that the first component is a child component or a parent component of the second component. The sibling relationship is used to indicate that the first component and the second component belong to the same level. In response to a configuration operation performed on the component configuration interface, metadata of the first component is generated based on the input information. The metadata is used to generate analysis results in the first component and to configure management permissions for the first component. The analysis results correspond to the analysis logic. The management permissions are determined at least through the component relationship. When the component relationship is a parent-child relationship, the management permissions include linkage permissions. When the component relationship is a sibling relationship, the management permissions include at least one of lifecycle management permissions, layout management permissions, and linkage permissions.

2. The dashboard management method according to claim 1, wherein the management permissions include the linkage permissions, and the dashboard management method further includes: In response to the first component having the linkage permission, and the data chart of the third component in the dashboard interface changing, the analysis result is generated based on the metadata and the changed data chart; Based on the analysis results, the first component in the dashboard interface is updated, wherein the third component is any one of the at least one second component.

3. The dashboard management method according to claim 1, wherein the management permissions include the lifecycle management permissions and / or the layout management permissions, and the dashboard management method further includes: In response to the first component having the lifecycle management permission, and the second management operation performed on the first component within the dashboard interface, lifecycle management corresponding to the second management operation is executed; or, In response to the first component having the layout management permission, and within the dashboard interface for the third management operation of the first component, the layout management corresponding to the third management operation is executed.

4. The dashboard management method according to claim 1, wherein the input information is further used to indicate multiple data sources, and the generation of metadata for the first component based on the input information in response to a configuration operation performed on the component configuration interface includes: In response to the configuration operation performed by the component configuration interface, the various data sources are invoked based on the input information; Metadata is generated based on the analysis logic in the input information and the various data sources invoked, wherein the metadata is used to generate the analysis results in the first component.

5. The dashboard management method according to claim 1, wherein the analysis logic includes multiple types, the input information further includes a preset template, the preset template is configured with placeholders, each placeholder is associated with the analysis result corresponding to each of the analysis logics, and the dashboard management method further includes: In response to an adjustment operation on a target placeholder in the component configuration interface, the position of the target placeholder in the preset template is adjusted, wherein the target placeholder is any one of the placeholders, and the adjustment operation is used to adjust the content structure of the preset template; The content displayed in the first component is generated in the following manner, the content including the analysis results corresponding to each of the analysis logics: the analysis results are generated based on the metadata generated by the analysis logic, the placeholders in the preset template are replaced with the analysis results associated with the placeholders, and the replaced results are used as the content.

6. The dashboard management method according to claim 1, wherein the analysis logic includes multiple types, the input information further includes a preset template, the preset template is configured with placeholders, each placeholder is associated with the analysis result corresponding to each of the analysis logics, and the dashboard management method further includes: In response to a recommendation request, retrieve dependency information; Based on the dependency information, adjustment suggestions are generated, wherein the adjustment suggestions are used to describe the recommended position of at least one of the placeholders in the preset template.

7. A dashboard management device based on intelligent data queries, comprising: The first response module is used to respond to the first management operation for the first component and display the component configuration interface; The second response module is used to respond to an input operation performed on the component configuration interface and obtain input information, wherein the input information includes basic component information and analysis logic for at least one second component in the dashboard interface. The basic component information includes the component relationship between the first component and the at least one second component. The component relationship includes a parent-child relationship or a sibling relationship. The parent-child relationship is used to indicate that the first component is a child component or a parent component of the second component. The sibling relationship is used to indicate that the first component and the second component belong to the same level. The third response module is used to respond to the configuration operation performed on the component configuration interface, and generate metadata of the first component based on the input information. The metadata is used to generate analysis results in the first component and to configure the management permissions of the first component. The analysis results correspond to the analysis logic. The management permissions are determined at least through the component relationship. When the component relationship is a parent-child relationship, the management permissions include linkage permissions. When the component relationship is a sibling relationship, the management permissions include at least one of lifecycle management permissions, layout management permissions, and linkage permissions.

8. A computer-readable medium having a computer program stored thereon, wherein, When the computer program is executed by the processing device, it implements the steps of the dashboard management method according to any one of claims 1-6.

9. An electronic device, comprising: A storage device on which computer programs are stored; A processing device for executing the computer program in the storage device to implement the steps of the dashboard management method according to any one of claims 1-6.

10. A computer program product comprising a computer program, wherein, When executed by a processor, the computer program implements the steps of the dashboard management method according to any one of claims 1-6.

Images