Data linkage method, device and equipment based on large-screen billboard assembly and medium

Abstract

The invention relates to a data linkage method, device and equipment based on a large-screen Kanban assembly and a storage medium, the method comprises the steps that by configuring dynamic request information of a first assembly, a second assembly and the first assembly are subjected to association operation, the first assembly and the second assembly are movable assemblies of a large-screen Kanban interface, and the first assembly and the second assembly are movable assemblies of the large-screen Kanban interface; and setting the target parameter of the first component as target data corresponding to the second component, and triggering the first component to initiate a data updating request according to the dynamic request information according to the change condition of the target data of the second component so as to update the target parameter of the first component. According to the method and the device, when the first component monitors that the target data of the second component changes, the request for updating the target parameter of the first component is actively triggered, so that linkage between the large-screen billboard components is realized.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a data linkage method, device, equipment, and storage medium based on large-screen dashboard components. Background Art

[0002] Large-screen dashboards can be used for real-time monitoring, reporting, displaying analysis results, etc. Their main scenarios include data monitoring, business analysis, information display, etc. The visual large-screen dashboard can save and avoid the development of a large number of repetitive requirements during the development of the dashboard page. Through simple dragging and arranging, the dashboard page can be configured and presented. However, the configured page can only complete the arrangement of components within the page, and there is no linkage ability between the components within the page. When it is necessary to dynamically query data according to certain conditions and then display it in the chart component, the scenarios that the large-screen dashboard can cover are very limited at this time, and it cannot meet the needs of various business scenarios.

[0003] Therefore, providing a technical solution for linkage between large-screen dashboard components has become an urgent technical problem for those skilled in the art. It should be noted that the information disclosed in the above background art section is only used to strengthen the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to those of ordinary skill in the art. Summary of the Invention

[0004] In view of the above, this application provides a data linkage method, device, equipment, and storage medium based on large-screen dashboard components, aiming to solve the above technical problems.

[0005] In a first aspect, this application provides a data linkage method based on large-screen dashboard components, and the method includes:

[0006] Configure the dynamic request information of the first component;

[0007] Perform an association operation on the second component and the first component, where the first component and the second component are movable components on the large-screen dashboard interface;

[0008] Set the target parameter of the first component to the target data corresponding to the second component;

[0009] According to the change situation of the target data of the second component, trigger the first component to initiate a data update request according to the dynamic request information to update the target parameter of the first component.

[0010] In a second aspect, this application provides a data linkage device based on large-screen dashboard components, and the device includes:

[0011] Configuration module: used to configure the dynamic request information of the first component;

[0012] Association module: used to perform an association operation on the second component and the first component, where the first component and the second component are movable components on a large-screen dashboard interface;

[0013] Setting module: used to set the target parameter of the first component as the target data corresponding to the second component;

[0014] Update module: used to trigger the first component to initiate a data update request according to the dynamic request information based on the change situation of the target data of the second component, so as to update the target parameter of the first component.

[0015] In a third aspect, the present application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete communication with each other through the communication bus;

[0016] Memory: used to store a computer program;

[0017] Processor: when used to execute the program stored on the memory, implement the data linkage method based on large-screen dashboard components described in any embodiment of the first aspect.

[0018] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, it implements the data linkage method based on large-screen dashboard components described in any embodiment of the first aspect.

[0019] The above technical solutions provided by the embodiments of the present application have the following advantages compared with the prior art:

[0020] In the present application, by configuring the dynamic request information of the first component, an association operation is performed between the second component and the first component. Among them, the first component and the second component are movable components on a large-screen dashboard interface. The target parameter of the first component is set as the target data corresponding to the second component. According to the change situation of the target data of the second component, the first component is triggered to initiate a data update request according to the dynamic request information to update the target parameter of the first component. When the first component monitors that the target data of the second component changes, it actively triggers a request to update the target parameter of the first component, thereby realizing the linkage between large-screen dashboard components. Description of the Drawings

[0021] The drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0022] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0023] Figure 1 It is a schematic flowchart of an embodiment of the data linkage method based on a large-screen dashboard component of the present application;

[0024] Figure 2 It is a schematic module diagram of an embodiment of the data linkage device based on a large-screen dashboard component of the present application;

[0025] Figure 3 It is a schematic diagram of an embodiment of an electronic device of the present application;

[0026] The realization of the purpose of the present application, functional characteristics and advantages will be further described with reference to the embodiments and the accompanying drawings. Detailed implementation manners

[0027] To make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0028] The following disclosure provides many different embodiments or examples for implementing different structures of the present application. To simplify the disclosure of the present application, the components and settings of specific examples are described below. Of course, they are only examples and are not intended to limit the present application. In addition, the present application may repeat reference numerals and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0029] The present application provides a data linkage method based on a large-screen dashboard component. Refer to Figure 1 As shown, it is a schematic flowchart of the method of an embodiment of the data linkage method based on a large-screen dashboard component of the present application. This method can be executed by an electronic device, which is implemented by software and / or hardware. The data linkage method based on a large-screen dashboard component includes:

[0030] Step S10: Configure the dynamic request information of the first component;

[0031] Step S20: performing an association operation on the second component and the first component, wherein the first component and the second component are movable components of the large-screen billboard interface;

[0032] Step S30: setting the target parameter of the first component to the target data corresponding to the second component;

[0033] Step S40: According to the change of the target data of the second component, trigger the first component to initiate a data update request according to the dynamic request information to update the target parameters of the first component.

[0034] The visual large-screen dashboard can save and avoid the development of a large number of repetitive requirements during the development of the dashboard page. The dashboard page can be configured and presented through simple dragging and editing.

[0035] However, the configured page can only complete the arrangement of components within the page. The components within the page do not have any linkage capabilities. When it is necessary to dynamically query data based on certain conditions and display it in the chart component, the scenarios that the large-screen dashboard can cover are very limited and cannot meet the needs of various business scenarios.

[0036] To this end, this application proposes a linkage solution between large-screen dashboard components, which allows the components to complete dynamic request re-updates by configuring interaction logic. That is, one component can notify another component in some way to trigger the corresponding request update, thereby completing the update of the displayed data to meet the needs of various business scenarios.

[0037] The first component and the second component are movable components of the large-screen kanban interface, and the user can drag the components. The ordinate value of the first component is a specific value or measurement related to the value of the second component, and the value of the second component may refer to values ​​such as date, season, product type, project stage, age stage, etc. For example, when the value of the second component is a date, the abscissa value of the first component is also a date type value, that is, the abscissa value of the first component is the same type of value as the second component. The target parameter of the first component (i.e., the ordinate value) can be sales, number of users, visit frequency, growth rate, score, etc. Taking the first component as a bar chart component and the second component as a date component as an example to illustrate the scheme of this embodiment, it can be understood that in actual applications, the first component and the second component can also be other components with an associated relationship.

[0038] Since the first component needs to have the ability to make dynamic data requests in order to receive new request parameters and re-request data according to the trigger action of the second component. If the dynamic request information is not configured, the first component will not be able to respond to the linkage request of the second component. Therefore, the dynamic request information of the first component can be configured first to ensure the real-time and dynamic nature of the data. Specifically, the configuration of the dynamic request information of the first component includes:

[0039] Configure the SQL request and / or dataset request of the first component.

[0040] Configuring the dynamic request information of the first component can enable the first component to adapt to different business scenarios and requirements, and flexibly adjust data requests through parameter changes.

[0041] The user can select the date of the second component. After determining the date of the second component, associate and bind the second component with the first component. By binding the second component with the first component, the change of the date of the second component can trigger the data update of the first component, so as to ensure that the data displayed by the first component is consistent with the date selected by the second component.

[0042] After binding the second component with the first component, set the target parameter of the first component to the target data corresponding to the second component, that is, set the request parameter of the first component to the date of the second component.

[0043] According to the change of the target data (such as date data) of the second component, trigger the first component to initiate a data update request according to the dynamic request information to update the target parameter of the first component. When the second component triggers a specific action, the first component can re-trigger a data request according to the change of the date data of the second component, so as to update the ordinate value of the first component, making the interaction logic of the components achieve a linkage effect.

[0044] In one embodiment, before performing the association operation on the second component and the first component, the method further includes:

[0045] Respond to the edit instruction initiated by the user for the second component;

[0046] Configure the target data corresponding to the second component according to the data corresponding to the edit instruction.

[0047] The user can initiate an edit instruction for the second component (such as an instruction to select a date), receive the user's date edit instruction for the second component, and after completing the selection of the date of the second component according to the edit instruction, perform the association operation on the second component and the first component, so that the first component can subsequently select and dynamically request new data according to the date of the second component and update the display content, thereby maintaining the real-time and accuracy of the data.

[0048] Specifically, triggering the first component to initiate a data update request according to the dynamic request information based on the change situation of the target data of the second component includes:

[0049] The first component listens for whether the target data of the second component has changed;

[0050] If so, trigger the first component to initiate a data update request to the server according to the dynamic request information and the changed target data.

[0051] An event can be defined inside the second component (for example, an event when the date selection is completed). After the user triggers the second component to complete the date selection, the second component will trigger the corresponding event to execute. When it is recognized that the second component is configured with a component binding action and a request parameter action, the corresponding binding component (i.e., the first component) is found from the component list inside the event, so as to obtain the data information of the first component. At this time, the second component will dynamically set the configured request parameters into the request parameters of the first component, so that when the first component listens for the change of the target data of the second component, it actively triggers a request to update the target parameters of the first component.

[0052] Further, listening for whether the target data of the second component has changed through the first component includes:

[0053] Through a listener preset by the first component, it continuously listens for whether the target data of the second component has changed.

[0054] The first component is configured with a callback function, and the callback function sets a listener to listen for whether the request parameters of the component have changed. When the request parameters change, the listener is triggered to work, so as to continuously listen for whether the target data of the second component has changed.

[0055] Further, after initiating a data update request to the server, the method further includes:

[0056] Obtain the new target parameters fed back by the server based on the dynamic request information and the changed target data;

[0057] Update the target parameters of the first component with the new target parameters.

[0058] Sending the dynamic request information and the changed target data to the server can obtain new target parameters, so as to realize that after the target data of the second component changes, the first component's data is automatically triggered to be re-requested.

[0059] In one embodiment, before configuring the dynamic request information of the first component, the method further includes:

[0060] In response to the drag instruction of the user's drag component, drag the first component and the second component corresponding to the drag instruction to the large-screen dashboard interface.

[0061] The user can initiate a drag instruction for the component list, drag the corresponding first component and second component from the component list to the large-screen dashboard interface. This enables the user to freely drag components to any position according to requirements and flexibly adjust the layout, thus meeting the display requirements of different business scenarios.

[0062] Refer to Figure 2 As shown, it is a functional module schematic diagram of the data linkage device 100 based on large-screen dashboard components of the present application.

[0063] The data linkage device 100 based on large-screen dashboard components of the present application can be installed in an electronic device. According to the implemented functions, the data linkage device 100 based on large-screen dashboard components can include a configuration module 110, an association module 120, a setting module 130, and an update module 140. The modules in the present application can also be referred to as units, which refer to a series of computer program segments that can be executed by the processor of the electronic device and can complete fixed functions, and are stored in the memory of the electronic device.

[0064] In this embodiment, the functions of each module / unit are as follows:

[0065] Configuration module 110: Used to configure the dynamic request information of the first component;

[0066] Association module 120: Used to perform an association operation on the second component and the first component, where the first component and the second component are movable components on the large-screen dashboard interface;

[0067] Setting module 130: Used to set the target parameter of the first component as the target data corresponding to the second component;

[0068] Update module 140: Used to trigger the first component to initiate a data update request according to the dynamic request information based on the change situation of the target data of the second component, so as to update the target parameter of the first component.

[0069] In one embodiment, configuring the dynamic request information of the first component includes:

[0070] Configuring the SQL request and / or dataset request of the first component.

[0071] In one embodiment, the association module 120 is further used for:

[0072] Responding to the editing instruction initiated by the user for the second component;

[0073] Configure the target data corresponding to the second component according to the data corresponding to the editing instruction.

[0074] In one embodiment, triggering the first component to initiate a data update request according to the dynamic request information according to the change situation of the target data of the second component includes:

[0075] Monitor whether the target data of the second component changes through the first component;

[0076] If so, trigger the first component to initiate a data update request to the server according to the dynamic request information and the changed target data.

[0077] In one embodiment, the update module 140 is further configured to:

[0078] Obtain new target parameters fed back by the server based on the dynamic request information and the changed target data;

[0079] Update the target parameters of the first component by using the new target parameters.

[0080] In one embodiment, the monitoring whether the target data of the second component changes through the first component includes:

[0081] Real-time monitor whether the target data of the second component changes through a listener preset by the first component.

[0082] In one embodiment, the configuration module 110 is further configured to:

[0083] In response to the drag instruction of the user dragging the component, drag the first component and the second component corresponding to the drag instruction to the large screen dashboard interface.

[0084] Refer to Figure 3 As shown, it is a schematic diagram of a preferred embodiment of the electronic device of the present application.

[0085] The electronic device includes a processor 111, a communication interface 112, a memory 113, and a communication bus 114. Among them, the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114;

[0086] The memory 113 is used to store computer programs, for example, a data linkage program based on the large screen dashboard component;

[0087] Among them, the processor 111 can be a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 111 is generally used to control the overall operation of the electronic device, such as performing control and processing related to data interaction or communication. In this embodiment, the processor 111 is used to run the program code stored in the memory 113 or process data, such as running the program code of the data linkage program based on the large-screen dashboard component.

[0088] The communication interface 112 can optionally include a standard wired interface, a wireless interface (such as a WI-FI interface), and the communication interface 112 can also be used to establish a communication connection between the electronic device and other electronic devices.

[0089] The memory 113 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, a hard disk, a multimedia card, a card-type memory (such as an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 113 can be an internal storage unit of the electronic device, such as the hard disk or memory of the electronic device. In other embodiments, the memory 113 can also be an external storage device of the electronic device, such as a plug-in hard disk equipped with the electronic device, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. Of course, the memory 113 can also include both the internal storage unit and the external storage device of the electronic device. In this embodiment, the memory 11 is generally used to store the operating system installed in the electronic device and various computer programs, such as the program code of the data linkage program based on the large-screen dashboard component. In addition, the memory 113 can also be used to temporarily store various types of data that have been output or will be output.

[0090] In an embodiment of the present application, when the processor 111 is used to execute the program stored on the memory 113, it implements the data linkage method based on the large-screen dashboard component provided by any one of the foregoing method embodiments, including:

[0091] Configure the dynamic request information of the first component;

[0092] Perform an association operation on the second component and the first component, where the first component and the second component are movable components on the large-screen dashboard interface;

[0093] Set the target parameter of the first component to the target data corresponding to the second component;

[0094] According to the change of the target data of the second component, trigger the first component to initiate a data update request according to the dynamic request information to update the target parameter of the first component.

[0095] For a detailed introduction to the above steps, please refer to the above Figure 1 Description of the flowchart of the data linkage method embodiment based on the large screen dashboard component.

[0096] In addition, an embodiment of the present application also proposes a computer-readable storage medium, which can be non-volatile or volatile. The computer-readable storage medium includes a storage data area and a storage program area. The storage program area stores a data linkage program based on the large screen dashboard component. When the data linkage program based on the large screen dashboard component is executed by a processor, the following operations are implemented:

[0097] Configure the dynamic request information of the first component;

[0098] Perform an association operation on the second component and the first component, where the first component and the second component are movable components on the large screen dashboard interface;

[0099] Set the target parameter of the first component to the target data corresponding to the second component;

[0100] According to the change of the target data of the second component, trigger the first component to initiate a data update request according to the dynamic request information to update the target parameter of the first component.

[0101] The specific implementation manner of the computer-readable storage medium of the present application is substantially the same as the specific implementation manner of the above data linkage method based on the large screen dashboard component, and will not be repeated here.

[0102] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0103] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence, or the part that contributes to the related technologies can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0104] It should be noted that the descriptions involving "first", "second", etc. in this application are only for descriptive purposes, and cannot be understood as indicating or implying their relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of such features. In addition, the technical solutions between various embodiments can be combined with each other, but it must be based on the fact that those of ordinary skill in the art can implement them. When the combination of technical solutions results in contradictions or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0105] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, as used herein, the singular forms "a", "an", and "the" may also include the plural forms. The terms "comprising", "including", "containing", and "having" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or their combinations. The method steps, processes, and operations described herein are not to be construed as necessarily requiring them to be executed in the particular order described or illustrated, unless the execution order is explicitly stated. It should also be understood that additional or alternative steps can be used.

[0106] The above are only the specific embodiments of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application will not be limited to these embodiments shown herein, but rather will be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A data linkage method based on a large-screen dashboard component, characterized in that The method includes: Configuring the dynamic request information of the first component; Performing an association operation on the second component and the first component, where the first component and the second component are movable components of the large-screen dashboard interface; Setting the target parameter of the first component to the target data corresponding to the second component; According to the change situation of the target data of the second component, triggering the first component to initiate a data update request according to the dynamic request information to update the target parameter of the first component.

2. The data linkage method based on the large-screen dashboard component according to claim 1, wherein The configuring the dynamic request information of the first component includes: Configuring the SQL request and / or dataset request of the first component.

3. The data linkage method based on the large-screen dashboard component according to claim 1, wherein Before performing the association operation on the second component and the first component, the method further includes: Responding to an editing instruction initiated by the user for the second component; Configuring the target data corresponding to the second component according to the data corresponding to the editing instruction.

4. The data linkage method based on the large-screen dashboard component according to claim 1, wherein, The triggering the first component to initiate a data update request according to the dynamic request information according to the change situation of the target data of the second component includes: Listening through the first component whether the target data of the second component changes; If so, triggering the first component to initiate a data update request to the server according to the dynamic request information and the changed target data.

5. The data linkage method based on the large-screen dashboard component according to claim 4, wherein, After initiating a data update request to the server, the method further includes: Obtaining new target parameters fed back by the server based on the dynamic request information and the changed target data; Updating the target parameter of the first component with the new target parameter.

6. The data linkage method based on the large-screen dashboard component according to claim 4, wherein, The listening through the first component whether the target data of the second component changes includes: Real-time listening through a listener preset in the first component whether the target data of the second component changes.

7. The data linkage method based on the large-screen dashboard component according to claim 1, characterized in that Before configuring the dynamic request information of the first component, the method further includes: Responding to a drag instruction for dragging components by the user, and dragging the first component and the second component corresponding to the drag instruction into the large-screen dashboard interface.

8. A data linkage device based on a large-screen dashboard component, characterized in that, The device includes: A configuration module: used to configure the dynamic request information of the first component; An association module: used to perform an association operation on the second component and the first component, where the first component and the second component are movable components of the large-screen dashboard interface; A setting module: used to set the target parameter of the first component to the target data corresponding to the second component; An update module: used to trigger the first component to initiate a data update request according to the dynamic request information according to the change situation of the target data of the second component to update the target parameter of the first component.

9. An electronic device, characterized in that, Including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus; The memory is used to store a computer program; The processor, when executing the program stored on the memory, implements the data linkage method based on large-screen dashboard components according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program, when executed by the processor, implements the data linkage method based on large-screen dashboard components according to any one of claims 1 to 7.

Images