Methods, devices, and electronic equipment for drag-and-drop customized data dashboards

Abstract

This application provides a method, apparatus, and electronic device for customizing data dashboards based on drag-and-drop functionality. The method includes: obtaining a data dashboard customization request, wherein the data dashboard customization request is a request sent by a target account corresponding to data to be displayed; dragging multiple data processing components from a first component library to a first visualization interface according to the data dashboard customization request, wherein the first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request; determining multiple target display components from multiple second components included in a second component library according to the multiple data processing components and the data dashboard customization request, and dragging the multiple target display components from the second component library to the second visualization interface to obtain a customized data dashboard. This improves the efficiency and accuracy of customizing data dashboards.

Description

Technical Field

[0001] This application relates to the field of data resource analysis and visualization technology, specifically to a method, device, and electronic device for customizing a data dashboard based on drag-and-drop functionality. Background Technology

[0002] A data dashboard is a data visualization tool specifically designed to display various types of data. Data visualization on a dashboard is an expression of data analysis results and a crucial step in data-driven decision-making. It not only displays data but also allows users to see the entire process of data change. With the popularity of big data analytics, the need for data analysis and dashboard visualization in industry applications to provide decision support is becoming increasingly urgent.

[0003] Currently, visualizing data dashboards requires developers with professional technical skills, involves long development cycles and high costs, and often fails to truly achieve the desired display effect. Therefore, developing a method for customizing data dashboards, allowing users to quickly and accurately customize them independently, has become a pressing technical challenge. Summary of the Invention

[0004] In view of the above-mentioned technical problems existing in the prior art, the embodiments of this application provide a method, apparatus and electronic device for customizing a data screen based on drag and drop, so as to solve at least one of the above-mentioned technical problems.

[0005] According to one aspect of the embodiments of this application, a method for customizing a data dashboard based on drag and drop is provided, comprising: obtaining a data dashboard customization request, wherein the data dashboard customization request is a request sent by a target account corresponding to data to be displayed; dragging multiple data processing components from a first component library to a first visualization interface according to the data dashboard customization request, wherein the first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request; determining multiple target display components from multiple second components included in a second component library according to the multiple data processing components and the data dashboard customization request, and dragging the multiple target display components from the second component library to the second visualization interface to obtain a customized data dashboard.

[0006] According to another aspect of the embodiments of this application, an apparatus for customizing a data dashboard based on drag and drop is also provided, comprising: an acquisition unit, configured to acquire a data dashboard customization request, wherein the data dashboard customization request is a request sent by a target account corresponding to data to be displayed; a first drag and drop unit, configured to drag multiple data processing components from a first component library to a first visualization interface according to the data dashboard customization request, wherein the first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request; a determination unit, configured to determine multiple target display components from multiple second components included in a second component library according to the multiple data processing components and the data dashboard customization request; and a second drag and drop unit, configured to drag multiple target display components from the second component library to a second visualization interface to obtain a customized data dashboard.

[0007] Optionally, the aforementioned determining unit includes a setting subunit, used to set connection relationships between multiple data processing components according to a data dashboard customization request, the connection relationships indicating the data flow direction between the multiple data processing components; a first determining subunit, used to determine a correspondence between at least one data processing component and at least one data display component in a second component library according to the connection relationships and the data dashboard customization request; and a second determining subunit, used to determine multiple target display components according to the correspondence relationships; the correspondence relationships include at least one of the following: at least two data processing components among the multiple data processing components correspond to the same target display component; multiple data processing components correspond to different target display components; or any data processing component corresponds to multiple different target display components.

[0008] Optionally, the above-mentioned device for customizing a data dashboard based on drag and drop further includes: a second determining unit, configured to determine at least one target data source from multiple reference data sources according to the data dashboard customization request after setting the connection relationship between multiple data processing components according to the data dashboard customization request; a first setting unit, configured to set at least one target data source for at least one data processing component, and set specific component attributes for at least one data processing component according to the data dashboard customization request; and a second setting unit, configured to set a target display component corresponding to at least one data processing component in the specific component attributes of at least one data processing component according to the correspondence after determining the correspondence.

[0009] Optionally, the above-mentioned device for customizing a data dashboard based on drag and drop further includes: a third setting unit, used to set the name of the reference customized data dashboard corresponding to the first visualization interface according to the data dashboard customization request after obtaining the data dashboard customization request; a first triggering unit, used to trigger the interface state of the interface corresponding to the data dashboard customization request in the first visualization interface to change from an invalid state to an effective state after the name is set; and a third determining unit, used to determine multiple data processing components from multiple first components included in the first component library according to the data dashboard customization request.

[0010] Optionally, the above-mentioned device for customizing a data dashboard based on drag and drop further includes: a fourth setting unit, used to set a first component library for the first visualization interface using a language compatible with the first visualization interface before obtaining the data dashboard customization request, and to set a first common component attribute for each of the multiple first components in the first component library, wherein the first common component attribute is a component attribute common to the multiple first components; and a fifth setting unit, used to set a second component library for the second visualization interface using a language compatible with the second visualization interface, and to set a second common component attribute for each of the multiple second components in the second component library, wherein the second common component attribute is a component attribute common to the multiple second components.

[0011] Optionally, the above-mentioned device for customizing a data dashboard based on drag and drop further includes: a sixth setting unit, used to set first common component attributes for multiple first components in the first component library, and then set at least one log printing sub-interface for at least one data processing component in the first visualization interface, with each data processing component corresponding to one log printing sub-interface, and the at least one log printing sub-interface connected to each other via tabs; and a second triggering unit, used to trigger at least one log printing sub-interface to print the data processed by the corresponding data processing component after setting specific component attributes for at least one data processing component.

[0012] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, which stores computer instructions for causing a computer to perform the above-described method for customizing a data dashboard based on drag and drop.

[0013] According to another aspect of the embodiments of this application, an electronic device is also provided, the electronic device including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform the above-described method for customizing a data dashboard based on drag and drop.

[0014] By obtaining a data dashboard customization request (a request sent by the target account corresponding to the data to be displayed), multiple data processing components are dragged from a first component library (corresponding to the first visualization interface) to the first visualization interface based on the customization request. The multiple data processing components are draggable components corresponding to both the first visualization interface and the data dashboard customization request. Based on these components and the customization request, multiple target display components are determined from multiple second components included in a second component library, and these target display components are dragged from the second component library to the second visualization interface, resulting in a customized data dashboard. This method not only improves the efficiency but also the accuracy of customized data dashboards. Attached Figure Description

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

[0016] Figure 1 This is a schematic diagram of the hardware environment for an optional method of customizing a data dashboard based on drag and drop, according to an embodiment of the present invention.

[0017] Figure 2 This is a flowchart of an optional method for customizing a data dashboard based on drag and drop, according to an embodiment of the present invention;

[0018] Figure 3 This is a flowchart of another optional method for customizing a data dashboard based on drag and drop, according to an embodiment of the present invention;

[0019] Figure 4 This is a schematic diagram of the structure of an optional drag-and-drop customized data screen according to an embodiment of the present invention;

[0020] Figure 5 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present invention. Detailed Implementation

[0021] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

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

[0023] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0024] To address the problems existing in the prior art, this application provides a method for quickly building a customized data dashboard, namely, a drag-and-drop customized data dashboard method. As an optional implementation, the above-mentioned drag-and-drop customized data dashboard method can be applied to, but is not limited to, [examples of other methods]. Figure 1 The system shown is a drag-and-drop customized data dashboard system consisting of terminal device 102 and server 104. Figure 1 As shown, terminal device 102 is connected to server 104 via network 110. Network 110 may include, but is not limited to, wired networks and wireless networks. The wired network includes local area networks (LANs), metropolitan area networks (MANs), and wide area networks (WANs). The wireless network includes Bluetooth, Wi-Fi, and other networks that enable wireless communication. Terminal device 102 may include, but is not limited to, at least one of the following: mobile phones (such as Android phones, iOS phones, etc.), laptops, tablets, handheld computers, MIDs (Mobile Internet Devices), tablets, desktop computers, smart TVs, etc.

[0025] The aforementioned terminal device 102 is also equipped with a display 106, a processor 108, and a memory 112. The display 106 can be used to display customized data screens, etc. The processor 108 can be used to identify, judge, and process received data screen customization requests, etc. The memory 112 can be used to store data screen customization requests, or to store the data obtained after processing the data screen customization requests, etc.

[0026] The aforementioned server 104 can be a single server, a server cluster consisting of multiple servers, or a cloud server. The aforementioned server 104 includes a database 114 and a processing engine 116. The database 114 can be used to store data dashboard customization requests and customized data dashboards, etc., while the processing engine 116 is used to process the aforementioned data dashboard customization requests and data processing components.

[0027] According to one aspect of the present invention, the system for customizing a data dashboard based on drag and drop can further perform the following steps: First, the terminal device 102 executes S102, sending a data dashboard customization request to the server 104 via the network 110; then, the server 104 executes S104 to S108: obtaining the data dashboard customization request, wherein the data dashboard customization request is a request sent by the target account corresponding to the data to be displayed; dragging multiple data processing components from the first component library to the first visualization interface according to the data dashboard customization request, wherein the first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request; determining multiple target display components from the multiple second components included in the second component library according to the multiple data processing components and the data dashboard customization request, and dragging multiple target display components from the second component library to the second visualization interface to obtain a customized data dashboard.

[0028] In the above embodiments of the present invention, a data dashboard customization request is obtained, which is a request sent by the target account corresponding to the data to be displayed; multiple data processing components are dragged from a first component library to a first visualization interface according to the data dashboard customization request, where the first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request; multiple target display components are determined from multiple second components included in a second component library according to the multiple data processing components and the data dashboard customization request, and multiple target display components are dragged from the second component library to the second visualization interface to obtain a customized data dashboard, thereby improving the efficiency and accuracy of customized data dashboards and achieving the technical effect of quickly and accurately building customized dashboards.

[0029] The above is merely an example, and no limitations are made in this embodiment.

[0030] As an alternative implementation method, please refer to Figure 2This document illustrates a flowchart of a method for customizing a data dashboard based on drag-and-drop functionality, according to an embodiment of this application. The execution entity for each step of this method can be the terminal device or server described above. In the following method embodiments, for ease of description, the execution entity for each step will only be described as a "computer device." This method may include at least one of the following steps (S202 to S206):

[0031] S202, Get Data Dashboard Customization Request. The data dashboard customization request is a request sent by the target account that corresponds to the data to be displayed.

[0032] S204, according to the data dashboard customization request, drag and drop multiple data processing components from the first component library to the first visualization interface. The first component library is the component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request.

[0033] S206. Based on multiple data processing components and data dashboard customization requests, determine multiple target display components from multiple second components included in the second component library, and drag and drop multiple target display components from the second component library to the second visualization interface to obtain a customized data dashboard.

[0034] It should be noted that the data dashboard customization request in S202 can be understood, but is not limited to, as a request sent by a target user through a terminal device after logging into the data dashboard visualization system containing the first and second visualization interfaces using the target account. The data dashboard customization request carries the target display task corresponding to the target account, as well as the target account's specific display requirements for the target display task (e.g., specific display effects). These specific display requirements can be textual or graphical (e.g., simple display diagrams drawn by the user). The target account is the account used by the target user to log into the data dashboard visualization system. When the target user logs into the data dashboard visualization system using the target account, the target account can be verified to confirm the identity of the target user. Only after successful verification can the target user be allowed to send the data dashboard customization request through the target account. The components in this application (i.e., the first component, the second component, the data processing component, the target display component, etc.) can be understood, but are not limited to, as a data engine, and the dragging and dropping of components can be understood, but is not limited to, as dragging and dropping of the data engine.

[0035] The first component library in S204 is a pre-configured component library for the first visualization interface. This library includes multiple first components, which can be understood, but are not limited to, as components used for data processing. These first components can be pre-configured by developers or user-defined. Each first component includes multiple data processing components, and each first component corresponds to a subtask. The target display task corresponds to at least one subtask, meaning the target display task corresponds to at least one first component. It is understood that dragging and dropping multiple data processing components from the first component library can be a manual operation or a triggered operation. This triggered operation occurs after receiving a data dashboard customization request; the system automatically determines multiple data processing components based on the request and then automatically triggers the drag-and-drop operation from the first component library to the first visualization interface.

[0036] The aforementioned multiple first components, such as triggering components (including timed triggering components, manual triggering components, node end triggering components, node exception triggering components, register triggering components, initialization triggering components, etc.), functional components, algorithm components, notification components, industrial control protocol components, CNC data acquisition components, cloud connection components, network components, database components, file processing components, HMI / BI reporting components, equipment management components, alarm management components, fault prediction components, equipment utilization rate components, data management components, production work order components, and energy management components, etc., can be configured according to their specific needs, and this application does not limit them.

[0037] The second component library in S206 is a component library pre-set for the second visualization interface. This library includes multiple second components, which can be pre-set by developers or user-defined. These second components can be understood, but are not limited to, as display components used to display data, and include multiple target display components. Similarly, the operation of dragging and dropping multiple target display components from the second component library to the second visualization interface can be a manual operation or a triggered operation. This triggered operation is automatically triggered after multiple target display components have been identified and their corresponding target display components have been set for each data processing component.

[0038] It should be noted that whether the above-mentioned operations of dragging and dropping multiple data processing components from the first component library to the first visualization interface, and dragging and dropping multiple target display components from the second component library to the second visualization interface are deliberate operations or automatically triggered operations can be determined based on the target account and operation requirements carried in the data dashboard customization request. Specifically, this includes: when the target account is not an account stored in the preset account table (i.e., a regular user account), and the operation requirement carried in the data dashboard customization request is empty, determining that the drag-and-drop operation (for ease of explanation, the drag-and-drop operation mentioned below includes the drag-and-drop in S204 and S206 above) is an automatically triggered drag-and-drop operation; when the target account is not an account stored in the preset account table (i.e., a regular user account), and the operation requirement carried in the data dashboard customization request is "autonomous drag-and-drop", determining that the drag-and-drop operation is a manual drag-and-drop operation; when the target account is an account existing in the preset account table, and the operation requirement carried in the data dashboard customization request is empty, determining that the drag-and-drop operation is a manual drag-and-drop operation; and when the target account is an account existing in the preset account table, and the operation requirement carried in the data dashboard customization request is "automatically triggered drag-and-drop", determining that the drag-and-drop operation is an automatically triggered drag-and-drop operation.

[0039] It should be noted that, in the case of "automatic drag-and-drop" as described above, after obtaining the customized data dashboard, the system will automatically trigger the packaged and sent data dashboard to the third display interface for display; in the case of "autonomous drag-and-drop" as described above, after obtaining the customized data dashboard and receiving a target display request, the customized data dashboard will be packaged and sent to the third display interface for display.

[0040] Through the above-described embodiments of this application, a customized data dashboard is obtained by acquiring a data dashboard customization request, which is a request sent by a target account corresponding to the data to be displayed; multiple data processing components are dragged from a first component library to a first visualization interface according to the data dashboard customization request, where the first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request; multiple target display components are determined from multiple second components included in a second component library according to the multiple data processing components and the data dashboard customization request, and multiple target display components are dragged from the second component library to the second visualization interface to obtain a customized data dashboard; thus improving the efficiency and accuracy of customized data dashboards.

[0041] As an optional implementation, the above-described method determines multiple target display components based on multiple data processing components and data dashboard customization requests, including:

[0042] S1, set the connection relationship between multiple data processing components according to the data dashboard customization request. The connection relationship is used to indicate the direction of data flow between multiple data processing components.

[0043] S2, determine the correspondence between at least one data processing component and at least one data display component in the second component library based on the connection relationship and the data dashboard customization request;

[0044] S3, determine multiple target display components based on the correspondence.

[0045] It should be noted that the multiple data processing components in S1 above, such as Figure 3 The components shown are: timed trigger component 302, data reading component 304 (reading data from machine 1), dataset query component 306, data reading component 308 (reading data from machine 2), time format adjustment component 310, data cleaning component 312, decimal to binary conversion component 314, product number parsing component 316, and log printing component 318. The operations in S1 can be understood, but are not limited to, determining the processing flow of the data to be displayed (data obtained from various data sources) based on the data dashboard customization request. Based on the processing flow, the connection relationships between multiple data processing components can be determined, and then the connection relationships can be set. The connection relationships can be understood, but are not limited to, the flow direction of the data obtained after processing by multiple data processing components (e.g., ...). Figure 3 (The arrow shown).

[0046] The operation in S2 above can be understood, but is not limited to, that after the data processing component processes the data, it needs to be displayed through the data display component in the second visualization interface. Therefore, it is necessary to set the correspondence between the data processing component and the data display component. However, not every data processing component needs to set a corresponding data display component. Each data processing component may not set a data display component, may set one data display component, or may set multiple data display components. However, at least one of the multiple data processing components needs to set a data display component. The data display component is used to display the data through the set component display format. That is, the operation in S2 above can be understood, but is not limited to, as setting the display method of the data processed by the data processing component. Before setting, it is necessary to determine the specific display method (i.e., the target display component in S3 above). This determination process needs to be based not only on the connection relationship but also on the display requirements of the customized data dashboard in the data dashboard customization request.

[0047] The above correspondence includes at least one of the following: at least two data processing components among multiple data processing components correspond to the same target display component (this can be understood, but is not limited to, two identical or different data processing components among multiple data processing components corresponding to the same (or of the same type), but not the same target display component); multiple data processing components correspond to different target display components (this can be understood, but is not limited to, each data processing component corresponding to a different type of target display component, for example...). Figure 3 The nine different types of data processing components shown correspond to different data display components, thus these nine different types of data processing components correspond to nine different types of data display components; any data processing component corresponds to different target display components (this can be understood, but is not limited to, that any one of the multiple data processing components corresponds to multiple different types of target display components, for example...). Figure 3 The data cleaning component 312 shown corresponds not only to the pie chart display component, but also to the bar chart display component, etc.

[0048] After determining the correspondence, multiple target display components can be determined from multiple second components based on the correspondence (i.e., the operation in S3).

[0049] The above-described implementation method of this application, by first determining the connection relationships between multiple data processing components and then determining the target display component based on the connection relationships and the data dashboard customization request, not only can the target display component corresponding to the data dashboard customization request be accurately customized, but it can also take into account the user's personalized display requirements for the customized data dashboard. Furthermore, this application introduces a visual drag-and-drop interface, enabling users to quickly define and configure data sources, data processing nodes, and data flow logic through a graphical interface, thereby improving the flexibility and ease of use of data acquisition and processing. Moreover, the data engine in this application is based on a component-based design, with each data processing function encapsulated as an independent drag-and-drop component. Users can construct data processing links through drag-and-drop, realizing dynamic data acquisition and multi-step data processing.

[0050] As an optional implementation, after setting the connection relationship between multiple data processing components according to the data dashboard customization request, the method further includes:

[0051] S1, determine at least one target data source from multiple reference data sources based on the data dashboard customization request;

[0052] S2, set at least one target data source for at least one data processing component, and set specific component properties for at least one data processing component according to the data dashboard customization request;

[0053] S3, after determining the correspondence, set the target display component corresponding to at least one data processing component in the specific component attribute of at least one data processing component according to the correspondence.

[0054] The multiple reference data sources in S1 mentioned above can be of the same or different types. These multiple reference data sources can be various types of data sources pre-connected to the first visualization interface. These data sources can include multiple types of data sources under one task scenario (e.g., equipment monitoring scenario), or multiple types of data sources under multiple task scenarios (e.g., equipment monitoring scenario, data development scenario, batch data processing scenario). The aforementioned multiple types of data sources include: data stored in various types of databases, data stored in various types of files (e.g., Excel files, Word files), data from offline data sources, and real-time data generated by the equipment (data collected in real-time without storage; for example, some PLC devices do not have storage capabilities, and even those with storage capabilities only store a small amount of data. However, this application allows configuring real-time data generated by the equipment as a data source, enabling the retention of this data and subsequent predictive maintenance of the equipment based on it).

[0055] The operation in S2 above can be understood, but is not limited to, that not every data processing component needs to set a data source, but at least one of the data processing components must set a data source. This at least one data processing component can set one target data source or multiple target data sources, for example... Figure 3 Of the nine data processing components shown, at least one needs to have a target data source set, and multiple target data sources can be set for that one data processing component when setting a target data source, for example... Figure 3 The dataset query component 306 shown can be configured to display data stored in a database, data collected in real-time from devices, and data from various types of files. For example... Figure 3 As can be seen from the component names shown, such as Figure 3 Of the nine data processing components shown, at least three—data reading component 304 (reading data from machine number one), dataset query component 306, and data reading component 308 (reading data from machine number two)—require setting corresponding target data sources. Other components, however, do not require specific data source settings. Figure 3 The data for the time format adjustment component 310 shown is derived from the data reading component 304 that reads data from the No. 1 machine.

[0056] It's important to note that after setting the target data source, you also need to configure the corresponding data source information, such as the database URL, username, password, device IP address, port, and any special configurations. Afterward, the data engine (i.e., the component) will automatically connect to the data source and perform read or write operations. Understandably, after setting the target data source and configuring the corresponding information, a connection verification process is required. If the connection fails, an error message is returned; if the connection is successful, subsequent real-time data acquisition and / or data processing operations are executed.

[0057] The aforementioned specific component attributes can be understood, but are not limited to, as attributes unique to each data processing component (or configurable) and different from other data processing components. These attributes can be set according to the specific display requirements carried in the data dashboard customization request (such as the specific time stamp set in the timed trigger component 302, the specific time format to be adjusted in the time format adjustment component 310, etc.), or they can be added independently to better customize the display effect of the data dashboard (such as adding what to display when parsing an empty product number according to the product parsing product number component 316, and how to display or prompt when parsing obvious errors, such as product numbers that are too long or too short).

[0058] It should be noted that the specific component attributes and specific display component attributes mentioned above, as well as the first and second common component attributes described below, can be customized as needed. For example, component attributes may include IP address, port number, connection name, reading strategy, etc.

[0059] The operation in S3 above can be understood, but is not limited to, binding the data processing component to its corresponding target display component after determining the correspondence. This binding process (i.e., the setting in S3 above) requires not only setting the target display component corresponding to the data processing component in the data processing component, but also setting the second visualization interface corresponding to the data processing component beforehand. Then, after setting the second visualization interface, the specific target display component corresponding to the data processing component is set. Setting the corresponding second visualization interface and the corresponding target display component can be done based on the interface name of the second visualization interface and the name of the target display component (i.e., setting the interface name of the second visualization interface and the component name of the target display component in the specific component properties of the data processing component), or it can be done in other custom ways, such as setting the interface ID of the second visualization interface and the component ID of the target display component in the specific component properties of the data processing component. It is understood that, similar to how a data processing component can have multiple target display components, each data processing component can also have multiple second visualization interfaces. In other words, multiple customized data dashboards with different visualization interfaces can be built using the same multiple data processing components.

[0060] It should be noted that after dragging and dropping multiple target display components to the second visualization interface, it is also necessary to set specific display component properties for each target display component in the second visualization interface. Specific display component properties can be understood as, but are not limited to, unique properties that can be set for each target display component. When setting specific display properties, it is also necessary to set the corresponding first visualization interface and corresponding data processing component for each target display component. Similarly, when setting the corresponding first visualization interface and corresponding data processing component, it can be done based on the interface name of the first visualization interface and the name of the data processing component (i.e., setting the interface name of the first visualization interface and the component name of the corresponding data processing component in the specific component properties of the target display component), or it can be done in other custom ways, such as setting the interface ID of the first visualization interface and the component ID of the corresponding data processing component in the specific component properties of the target display component.

[0061] Through the above-described embodiments of this application, not only is it possible to flexibly set one or more corresponding data sources for different data processing components, but it also enables the setting of one or more corresponding second visualization interfaces and target display components for different data processing components, thereby achieving the rapid construction of multiple and diversified customized data dashboards. Furthermore, this application supports automatic identification and adaptation of multiple data sources, including structured data, semi-structured data, and unstructured data, improving the compatibility and adaptability of data acquisition.

[0062] As an optional implementation, after obtaining the data dashboard customization request, the following steps are also included:

[0063] S1, set the name of the reference customized data dashboard corresponding to the first visualization interface according to the data dashboard customization request;

[0064] S2, after setting the name, the interface state of the interface corresponding to the data dashboard customization request in the first visualization interface changes from invalid to valid.

[0065] S3, based on the data dashboard customization request, determines multiple data processing components from the multiple first components included in the first component library.

[0066] The operation in S2 above can be understood, but is not limited to, naming the first visualization interface. Only after naming the first visualization interface will its validity be triggered. That is, the subsequent drag-and-drop operation of multiple data processing components can only be executed if the first visualization interface is valid. Similarly, after determining multiple target display components, before dragging multiple target display components from the second component library to the second visualization interface, it is also necessary to name the second visualization interface (i.e., perform the same operation as in S1 to S2 above) to change the interface state of the second visualization interface from invalid to valid. Only then can the drag-and-drop operation of multiple target display components be performed. It is understood that there can be one or multiple second visualization interfaces, depending on the data dashboard customization request. When there are multiple second visualization interfaces, the process of determining multiple target display components from the multiple second components corresponding to each second visualization interface and dragging multiple target display components corresponding to each second visualization interface from the second component library corresponding to each second visualization interface is executed in parallel using multi-threading. This results in multiple customized data dashboards being obtained simultaneously.

[0067] The operation in S3 above specifically includes: determining the target customized screen task based on the data screen customization request; determining multiple data processing sub-tasks based on the target customized screen task; and determining multiple data processing components from multiple first components included in the first component library based on the multiple data processing sub-tasks, with each data processing sub-task corresponding to one data processing component.

[0068] The above-described embodiments of this application not only avoid the chaos and resource waste caused by arbitrarily triggering and dragging data processing components and target display components, but also enable accurate identification of multiple data processing components, thereby improving the accuracy of customized data dashboards.

[0069] As an optional implementation, before obtaining the data dashboard customization request, the following steps are also included:

[0070] S1, use a language compatible with the first visual interface to set up a first component library for the first visual interface, and set a first common component property for each of the multiple first components in the first component library. The first common component property is a component property shared by multiple first components.

[0071] S2, using a language compatible with the second visual interface, sets up a second component library for the second visual interface, and sets second common component properties for multiple second components in the second component library. The second common component properties are component properties shared by multiple second components.

[0072] The languages ​​in S1 and S2 above can be understood as, but are not limited to, development languages, and there can be multiple development languages, such as JAVA, C++, Python, etc. The languages ​​in S1 that are compatible with the first visual interface can be understood as, but are not limited to, languages ​​compatible with the first visual interface and the system on which the first visual interface resides. The first common component attributes mentioned above can be understood as component attributes shared by multiple first components. The languages ​​in S2 that are compatible with the second visual interface can be understood as, but are not limited to, languages ​​compatible with the second visual interface and the system on which the second visual interface resides (i.e., the systems on which the first and second visual interfaces (and the third visual interface) reside can be the same system, such as both being Android, or they can be different systems, such as some visual interfaces being Android and some being iOS). The second common component attributes mentioned above can be understood as component attributes shared by multiple second components.

[0073] The first and second common component properties mentioned above can be configured uniformly when configuring the component library, or they can be customized separately after dragging and dropping the corresponding components.

[0074] The above-described embodiments of this application allow for less restriction on language and visual interfaces (first visual interface, second visual interface, and third visual interface), thereby improving flexibility in the process of implementing customized data dashboards.

[0075] As an optional implementation, after setting the first common component properties for each of the multiple first components in the first component library, the method further includes:

[0076] S1, In the first visualization interface, at least one log printing sub-interface is set for at least one data processing component in the first visualization interface, each data processing component corresponds to one log printing sub-interface, and at least one log printing sub-interface is connected to each other through tabs.

[0077] S2, after setting specific component properties for at least one data processing component, trigger at least one log printing sub-interface to print the data processed by the corresponding data processing component.

[0078] It should be noted that each of the above data processing components can be dragged and dropped with a corresponding log printing component (such as...). Figure 3 The log printing component 318 shown can be configured with a log printing sub-interface to print the corresponding data content. When there are multiple log printing components, a log printing sub-interface can be configured for each log printing component, resulting in multiple log printing sub-interfaces. These multiple log printing sub-interfaces are connected by tabs.

[0079] It is understandable that these multiple log printing sub-interfaces are set in the first visualization interface. However, after setting multiple log printing sub-interfaces, they will not be directly displayed in the first visualization interface. Instead, the log printing sub-interfaces will be displayed only after setting specific component properties for at least one data processing component, and the printing operation in the log printing sub-interfaces will be triggered at the same time. The size of the log printing sub-interfaces can be adapted to the size of the first visualization interface, or it can be the size that the user sets as needed.

[0080] Through the above-described embodiments of this application, a log printing sub-interface can be flexibly set for the data processing component, thereby facilitating the verification of the processed data through the logs printed in the log printing sub-interface after the data processing component processes the data. This allows for timely reminders to staff to adjust the corresponding data processing component when errors are detected in the data.

[0081] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0082] According to another aspect of the present invention, an apparatus for implementing the above-described method for customizing a data dashboard based on drag and drop is also provided, such as... Figure 4 As shown, the device includes:

[0083] The acquisition unit 402 is used to acquire the data dashboard customization request, which is a request sent by the target account corresponding to the data to be displayed;

[0084] The first drag-and-drop unit 404 is used to drag and drop multiple data processing components from the first component library to the first visualization interface according to the data dashboard customization request. The first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request.

[0085] The determining unit 406 is used to determine multiple target display components from multiple second components included in the second component library based on multiple data processing components and data screen customization requests;

[0086] The second drag-and-drop unit 408 is used to drag and drop multiple target display components from the second component library to the second visualization interface to obtain a customized data dashboard.

[0087] The specific methods of execution of each unit in the above device embodiments have been described in detail in the embodiments related to the method, and will not be elaborated further here.

[0088] According to another aspect of the present invention, an electronic device for implementing the above-described method for customizing a data dashboard based on drag and drop is also provided. This electronic device may be as follows: Figure 5 The terminal device or server shown. This embodiment uses this electronic device as an example for illustration. Figure 5 As shown, the electronic device includes: at least one processor 504; and a memory 502 communicatively connected to at least one processor 504; wherein the memory 502 stores a computer program executable by at least one processor 504, the computer program being executed by at least one processor 504 to cause at least one processor 504 to perform the steps in any of the above method embodiments.

[0089] Optionally, in this embodiment, the aforementioned electronic device may be located in at least one of a plurality of network devices in a computer network.

[0090] Optionally, in this embodiment, the processor can be configured to execute the steps of the above-described method for customizing a data dashboard based on drag and drop via a computer program.

[0091] Alternatively, as those skilled in the art will understand, Figure 5 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones (such as Android phones, iOS phones, etc.), tablets, PDAs, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 5 This does not limit the structure of the aforementioned electronic devices. For example, the electronic device may also include components that are more... Figure 5 The more or fewer components shown (such as network interfaces, etc.), or having the same Figure 5 The different configurations shown.

[0092] The memory 502 can be used to store software programs and modules, such as the program instructions / modules corresponding to the drag-and-drop customized data screen method and device in this embodiment of the invention. The processor 504 executes various functional applications and data processing by running the software programs and modules stored in the memory 502, thereby realizing the above-mentioned drag-and-drop customized data screen method. The memory 502 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 502 may further include memory remotely located relative to the processor 504, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Specifically, the memory 502 may be used, but is not limited to, to store information such as customized data screens. As an example, such as Figure 5 As shown, the memory 502 may include, but is not limited to, the acquisition unit 402, the first drag-and-drop unit 404, the determination unit 406, and the second drag-and-drop unit 408 in the aforementioned device for customizing a data screen based on drag-and-drop functionality. Furthermore, it may include, but is not limited to, other module units in the aforementioned device for customizing a data screen based on drag-and-drop functionality, which will not be elaborated upon in this example.

[0093] Optionally, the transmission device 506 described above is used to receive or send data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission device 506 includes a Network Interface Controller (NIC), which can be connected to other network devices and a router via a network cable to communicate with the Internet or a local area network. In another example, the transmission device 506 is a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0094] In addition, the above-mentioned electronic device also includes a display 508 and a connection bus 510 for connecting the various module components in the above-mentioned electronic device.

[0095] In other embodiments, the aforementioned terminal device or server can be a node in a distributed system, wherein the distributed system can be a blockchain system, which is a distributed system formed by connecting multiple nodes through network communication. The nodes can form a peer-to-peer (P2P) network, and any form of computing device, such as a server, terminal, or other electronic device, can become a node in the blockchain system by joining this peer-to-peer network.

[0096] According to one aspect of this application, a computer program product is provided, comprising a computer program / instructions containing program code for performing the methods shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it performs various functions provided in embodiments of this application.

[0097] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0098] According to one aspect of this application, a computer-readable storage medium is provided, wherein a processor of a computer device reads computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the above-described method for creating a drag-and-drop customized data dashboard.

[0099] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the above-described method for customizing a data dashboard based on drag and drop.

[0100] Those skilled in the art will understand that all or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes as described in the above method embodiments. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), random access memory (RAM), flash memory (FM), hard disk drive (HDD), or solid-state drive (SSD), etc.; the storage medium can also include combinations of the above types of memory.

[0101] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0102] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0103] In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between units or modules, and may be electrical or other forms.

[0104] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0105] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0106] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for customizing a data dashboard based on drag-and-drop, characterized in that, include: Obtain a data dashboard customization request, wherein the data dashboard customization request is a request sent by the target account corresponding to the data to be displayed; According to the data dashboard customization request, set the names of the reference customized data dashboards corresponding to the first and second visualization interfaces, respectively. After the name is set, the interface state of the interface corresponding to the data screen customization request in the first visualization interface is triggered to change from an invalid state to an effective state, and the interface state of the interface corresponding to the data screen customization request in the second visualization interface is triggered to change from an invalid state to an effective state. According to the data dashboard customization request, multiple data processing components are dragged from the first component library to the first visualization interface. The first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request. The process includes determining multiple target display components from multiple second components included in a second component library based on multiple data processing components and the data dashboard customization request, including: setting connection relationships between multiple data processing components according to the data dashboard customization request, the connection relationships indicating the data flow direction between multiple data processing components; determining a correspondence between at least one data processing component and at least one data display component in the second component library based on the connection relationships and the data dashboard customization request; determining multiple target display components based on the correspondence; determining at least one target data source from multiple reference data sources according to the data dashboard customization request; setting at least one target data source for at least one data processing component, and setting specific component attributes for at least one data processing component according to the data dashboard customization request; and after determining the correspondence, setting a target display component corresponding to at least one data processing component in the specific component attributes of at least one data processing component according to the correspondence, the name corresponding to the second visualization interface, and the name of the target display component; and setting at least one data processing component corresponding to the target display component in the specific component attributes of the target display component according to the correspondence, the name corresponding to the first visualization interface, and the name corresponding to at least one data processing component. Drag and drop multiple target display components from the second component library onto the second visualization interface to obtain a customized data dashboard.

2. The method according to claim 1, characterized in that, The correspondence includes at least one of the following: At least two of the plurality of data processing components correspond to the same target display component; Each of the multiple data processing components corresponds to a different target display component; Each of the data processing components corresponds to multiple different target display components.

3. The method according to claim 1, characterized in that, After the interface state of the interface corresponding to the data dashboard customization request in the first visualization interface changes from an invalid state to an active state, it also includes: Based on the data dashboard customization request, multiple data processing components are determined from the multiple first components included in the first component library.

4. The method according to claim 3, characterized in that, Before obtaining the data dashboard customization request, the following steps are also included: The first component library is set up for the first visual interface using a language compatible with the first visual interface, and a first common component attribute is set for each of the multiple first components in the first component library. The first common component attribute is a component attribute that is common to the multiple first components. The second component library is set up for the second visualization interface using a language compatible with the second visualization interface, and a second common component property is set for each of the multiple second components in the second component library. The second common component property is a component property shared by the multiple second components.

5. The method according to claim 1, characterized in that, After setting the first common component property for each of the multiple first components in the first component library, the method further includes: In the first visualization interface, at least one log printing sub-interface is set for at least one of the data processing components in the first visualization interface, each data processing component corresponds to one log printing sub-interface, and at least one log printing sub-interface is connected to each other through tabs. After setting specific component properties for at least one of the data processing components, at least one log printing sub-interface is triggered to print the data processed by the corresponding data processing component.

6. A device for customizing a large data screen based on drag-and-drop functionality, characterized in that: include: The acquisition unit is used to acquire a data dashboard customization request, wherein the data dashboard customization request is a request sent by the target account that corresponds to the data to be displayed; The first drag-and-drop unit is used to drag and drop multiple data processing components from the first component library to the first visualization interface according to the data dashboard customization request. The first component library is a component library corresponding to the first visualization interface, and the multiple data processing components are draggable components corresponding to the first visualization interface and the data dashboard customization request. A determining unit is configured to determine multiple target display components from multiple second components included in a second component library based on multiple data processing components and a data dashboard customization request. The determination includes: setting connection relationships between the multiple data processing components according to the data dashboard customization request, wherein the connection relationships indicate the data flow direction between the multiple data processing components; determining a correspondence between at least one data processing component and at least one data display component in the second component library based on the connection relationships and the data dashboard customization request; determining multiple target display components based on the correspondence; determining at least one target data source from multiple reference data sources according to the data dashboard customization request; setting at least one target data source for at least one data processing component, and setting specific component attributes for at least one data processing component according to the data dashboard customization request; and after determining the correspondence, setting a target display component corresponding to at least one data processing component in the specific component attributes of at least one data processing component based on the correspondence, the name corresponding to the second visualization interface, and the name of the target display component; and setting at least one data processing component corresponding to the target display component in the specific component attributes of the target display component based on the correspondence, the name corresponding to the first visualization interface, and the name corresponding to at least one data processing component. The second drag-and-drop unit is used to drag and drop multiple target display components from the second component library to the second visualization interface to obtain a customized data dashboard; The device for customizing a data dashboard based on drag and drop is further configured to, after obtaining a data dashboard customization request, set the names of the reference customized data dashboards corresponding to the first visualization interface and the second visualization interface according to the data dashboard customization request; after setting the names, trigger the interface state of the interface corresponding to the data dashboard customization request in the first visualization interface to change from an invalid state to an effective state, and trigger the interface state of the interface corresponding to the data dashboard customization request in the second visualization interface to change from an invalid state to an effective state.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the drag-and-drop customized data dashboard method according to any one of claims 1-5.

8. An electronic device, characterized in that, The electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform the drag-and-drop customized data screen method according to any one of claims 1-5.

Images