Kanban linkage method, system and equipment and storage medium

Abstract

According to the billboard linkage method, system and device and the storage medium, the source table, the linkage table, the linkage conditions and the interaction options are integrated in the billboard interface, a traditional mode depending on manual field input is replaced, the configuration process is simplified, and the error rate is reduced. And the linkage configuration information is analyzed to construct the linkage rule, so that standardization and automatic generation of the rule can be realized, and the accuracy and efficiency of data linkage are improved. And after the user interaction event is detected, the screening logic can be automatically triggered and the updated linkage table display data can be generated, so that interactive display is realized, and tedious operation of manual query is avoided. Compared with a traditional manual configuration mode, according to the embodiment of the invention, through visual configuration, automatic screening and rapid rendering, the response speed and accuracy of billboard linkage are remarkably improved, and the method is suitable for data visualization requirements of multiple scenes such as hotel operation data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data visualization, in particular to a look board linkage method, system, device and storage medium. BACKGROUND

[0002] With the rapid development of data visualization technology, look board as an intuitive data display tool is widely used in enterprise data analysis and business monitoring. The traditional look board scheme usually only supports static data display. When a user selects a source table data, the user needs to manually query the associated data in the corresponding other linkage table based on the corresponding field data in the source table, which is tedious and inefficient.

[0003] It should be noted that the information disclosed in the above background section is only used to strengthen the understanding of the background of the present application, and therefore can include information that does not constitute prior art known to those of ordinary skill in the art. SUMMARY

[0004] In view of the problems in the prior art, the object of the present application is to provide a look board linkage method, system, device and storage medium, which overcomes the difficulties of the prior art and solves the technical problem of low look board linkage efficiency in the prior art.

[0005] The first aspect of the present application provides a look board linkage method, comprising:

[0006] Obtaining linkage configuration information set by a user in a look board interface, the linkage configuration information comprising at least one source table, a linkage table associated with the source table, a table linkage condition and an interaction option;

[0007] Analyzing the linkage configuration information, and constructing a structured linkage rule based on the analysis result;

[0008] Detecting a user interaction event of the source table, and executing a table trigger logic on the user interaction event according to the linkage rule to obtain a trigger instruction;

[0009] In response to the trigger instruction, triggering a linkage data filtering in the linkage table based on the linkage rule as updated linkage table display data;

[0010] Rendering the updated linkage table display data to the look board interface.

[0011] Optionally, the obtaining of the linkage configuration information set by the user in the look board interface comprises:

[0012] displaying an interactive control for table selection on a dashboard interface, determining at least one source table and a linkage table associated with the source table in response to a user selection of the interactive control, the linkage table being associated with the source table based on a preset data mapping relationship, and generating the linkage condition based on the data mapping relationship;

[0013] receiving an interaction option set by the user through the dashboard interface, the interaction option being one of a multiple selection mode, a non-cancellable mode, and a default selection mode;

[0014] packaging the source table, the linkage table of the source table, the linkage condition, and the interaction option into a configuration data structure as the linkage configuration information.

[0015] Optionally, the structured linkage rule is constructed based on the analysis result, including:

[0016] determining a trigger type based on the source table and the linkage table, the trigger type being a single table trigger or a multi-table combination trigger;

[0017] converting the linkage condition into a data mapping relationship and an executable SQL query statement;

[0018] storing the trigger type, the data mapping relationship, and the interaction option as a structured linkage rule.

[0019] Optionally, the user interaction event of the source table is detected, including:

[0020] listening to a user action on the source table, determining the user interaction event, and obtaining a field selected by the user action and a field value thereof;

[0021] executing a table trigger logic on the user interaction event according to the linkage rule to obtain a trigger instruction, including:

[0022] generating the trigger instruction based on the trigger type in the linkage rule and the field value.

[0023] Optionally, in response to the trigger instruction, triggering a filtering of linkage data in the linkage table based on the linkage rule to obtain updated linkage table display data, including:

[0024] generating a corresponding SQL query statement based on the field value in the trigger instruction and the data mapping relationship in the linkage rule;

[0025] executing the SQL query statement to filter or aggregate the data in the linkage table to obtain the updated linkage table display data.

[0026] Optionally, the SQL query statement is executed to filter or aggregate the data in the linkage table, including:

[0027] construct a multi-table joint SQL query statement based on the data mapping relationship defined in the linkage rule, the multi-table joint including the inter-table linkage condition established between the source table and the linkage table based on the data mapping relationship;

[0028] access the database based on the multi-table joint SQL query statement, and extract linkage data meeting the inter-table linkage condition;

[0029] perform field filtering, grouping aggregation or sorting processing on the extracted linkage data to obtain updated linkage table display data.

[0030] Optionally, the board linkage method further includes:

[0031] when no linkage data is obtained in the linkage table by executing the SQL query statement, the following steps are performed:

[0032] generate a prompt information based on the field value and display the prompt information on the board interface.

[0033] A second aspect of the present disclosure provides a board linkage system, which includes:

[0034] a linkage configuration module configured to obtain linkage configuration information set by a user on a board interface, the linkage configuration information including at least one source table, a linkage table associated with the source table, an inter-table linkage condition and an interaction option;

[0035] a rule construction module configured to parse the linkage configuration information and construct a structured linkage rule based on a parsing result;

[0036] a detection module configured to detect a user interaction event of the source table, execute a table trigger logic on the user interaction event according to the linkage rule, and obtain a trigger instruction;

[0037] a data filtering module configured to trigger, in response to the trigger instruction, filtering of linkage data in the linkage table based on the linkage rule as updated linkage table display data;

[0038] a rendering module configured to render the updated linkage table display data to the board interface.

[0039] A third aspect of the present disclosure provides an electronic device, which includes:

[0040] a processor;

[0041] a memory having executable instructions of the processor stored therein;

[0042] The processor is configured to execute the steps of the board linkage method described in any of the above embodiments by executing the executable instructions.

[0043] The fourth aspect of the present disclosure provides a computer-readable storage medium for storing a program, which, when executed, implements the steps of the kanban linkage method according to any of the embodiments.

[0044] The kanban linkage method, system, device and storage medium provided by the embodiments of the present disclosure have the following advantages:

[0045] The embodiments of the present disclosure integrate the source table, linkage table, linkage condition and interaction option in the kanban interface, replace the traditional manual field input mode, simplify the configuration process and reduce the error rate. Analyzing the linkage configuration information to construct the linkage rule can realize the standardization and automatic generation of the rule, improve the accuracy and efficiency of data linkage. When detecting the user interaction event, the filtering logic can be automatically triggered and the updated linkage table display data can be generated to realize the interactive display and avoid the tedious manual query operation.

[0046] Compared with the traditional manual configuration mode, the embodiments of the present disclosure significantly improve the response speed and accuracy of the kanban linkage through the visual configuration, automatic filtering and rapid rendering, and are suitable for the data visualization needs in multiple scenarios such as hotel operation data.

[0047] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0048] Other features, objects and advantages of the present application will become more apparent from the following detailed description of non-limiting embodiments with reference to the drawings.

[0049] Figure 1 A flowchart of a kanban linkage method provided by an embodiment of the present disclosure is shown;

[0050] Figure 2 An implementation of the kanban linkage method is shown; Figure 1 An architecture diagram of a kanban linkage system of the kanban linkage method is shown;

[0051] Figure 3 A module structure schematic diagram of a kanban linkage system provided by an embodiment of the present disclosure is shown;

[0052] Figure 4 A structure schematic diagram of an electronic device provided by an embodiment of the present disclosure is shown;

[0053] Figure 5 A structure schematic diagram of a computer program product of an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0054] In order to make the technical solutions of the present application clearer and more specific, the exemplary embodiments of the present application will be described in detail in conjunction with the drawings. It should be understood that the following embodiments are only used to illustrate the technical implementation path of the present application, and do not limit the protection scope of the present application. Those skilled in the art can make various modifications and adjustments on the basis of the basic idea disclosed in the present application, and these modifications should also be considered to be included in the protection scope of the present application.

[0055] It should be noted that the specific embodiments provided in the specification can be implemented in various forms, and the examples should not be understood as constituting any limitation on the present application. The structural features, module division and processing steps in the embodiments can be flexibly combined and adjusted according to the system architecture, deployment platform and running environment, in order to better adapt to the needs of the target application scenario.

[0056] In addition, the drawings are used to illustrate the principle structure and implementation steps of the present application, and are not necessarily drawn to scale. In order to simplify the description of the drawings, the same reference numerals in the drawings represent the same or functionally similar components or modules, and therefore the same elements are not described repeatedly in multiple drawings. The functional entities or processing flows shown in the drawings can be implemented in various ways, and are not limited to a specific hardware structure or logical division. The specific implementation can adopt software functions, API interfaces, script logic, micro-service processes or hardware modules, and can also be completed in a single computing node or a distributed system.

[0057] In the related art, there is also a KPI board linkage function based on a data visualization tool, but the user needs to input the data mapping relationship one by one, manually set the inter-table linkage rules, and the linkage configuration is complicated, the operation steps are many, the configuration process is complex and prone to field or logical errors, resulting in low efficiency of KPI board linkage. There is a lack of intuitive configuration method.

[0058] To solve the above problems, the present disclosure provides an efficient KPI board linkage method, system, device and storage medium, which significantly improves the efficiency of KPI board linkage.

[0059] In order to facilitate understanding of the technical solutions, the key terms of the embodiments of the present disclosure are explained in detail as follows:

[0060] Source table: a data table on which the user performs user interaction operations in the visual KPI board interface, serving as the trigger source of inter-table linkage, that is, the user's operation on the source table will trigger the filtering and display of data of other linkage tables;

[0061] Linkage table: a data table triggered by the interaction event of the source table, and the display data of which will change according to the linkage rules;

[0062] Linkage: refers to the association between the source table and the linkage table triggered by the user interaction event, filtering the linkage data that meets the linkage rules, and dynamically generating and updating the display data of the linkage table.

[0063] Linkage state: refers to the display state of linkage table display data on the dashboard interface.

[0064] JSON configuration: refers to the JSON format data structure generated after the user sets the linkage configuration information on the dashboard interface, which includes the source table, the linkage table, the linkage conditions of the field matching between the tables, and the interaction options, as the input of the linkage process, for parsing and generating structured linkage rules.

[0065] Linkage configuration information: refers to the source table, linkage table, linkage conditions of field matching between tables, and interaction options set by the user on the dashboard interface, which defines the linkage logic.

[0066] Linkage condition: refers to the field matching relationship between the source table and the linkage table.

[0067] Interaction options: refers to the interaction type, operation object, and parameter configuration set supported by the user when interacting with the source table on the visual dashboard interface, which triggers the linkage or behavioral response.

[0068] As shown in Figure 1 , the dashboard linkage method provided by the embodiment of the present disclosure includes but is not limited to the following steps:

[0069] Step 110: obtaining the linkage configuration information set by the user on the dashboard interface, the linkage configuration information including at least one source table, a linkage table associated with the source table, a linkage condition between the tables, and interaction options;

[0070] Step 120: parsing the linkage configuration information, and constructing a structured linkage rule based on the parsing result;

[0071] Step 130: detecting a user interaction event of the source table, and executing a table triggering logic on the user interaction event according to the linkage rule to obtain a triggering instruction;

[0072] Step 140: in response to the triggering instruction, triggering a filtering logic based on the linkage rule in the linkage table to filter linkage data as updated linkage table display data.

[0073] Step 150: rendering the updated linkage table display data to the dashboard interface.

[0074] In this way, the embodiment integrates the source table, the linkage table, the linkage condition, and the interaction options in the dashboard interface, replacing the traditional manual field input method, simplifying the configuration process and reducing the error rate. Parsing the linkage configuration information to construct the linkage rule can realize the standardization and automatic generation of the rule, improve the accuracy and efficiency of data linkage. When detecting the user interaction event, the filtering logic can be automatically triggered to generate the updated linkage table display data, realizing interactive display and avoiding manual query cumbersome operation.

[0075] Compared with the traditional manual configuration mode, the embodiment of the disclosure significantly improves the response speed and accuracy of the dashboard linkage by visualizing the configuration, automatically screening and quickly rendering, and is suitable for data visualization needs in multiple scenarios such as hotel operation data.

[0076] In the embodiment of the disclosure, when step 110 is performed, the user terminal displays a visualized dashboard interface, and the user can intuitively configure one or more source tables, linkage tables associated with the source tables, linkage conditions and interaction options through dragging fields or a drop-down menu, and then generate configuration data in JSON format according to the information input or selected by the user as linkage configuration information. Specifically, step 110 can specifically include the following sub-steps:

[0077] The dashboard interface displays an interactive control for table selection, and in response to user selection of the control, at least one source table and a linkage table associated therewith are determined, the linkage table being associated with the source table based on a preset data mapping relationship and generating a linkage condition based on the mapping relationship;

[0078] The interaction options set by the user through the dashboard interface are received, and the interaction options include one of a multiple selection mode, a non-cancellable mode and a default selected mode;

[0079] The source table, the linkage table of the source table, the linkage condition and the interaction option are encapsulated into a configuration data structure as the linkage configuration information.

[0080] In an implementable manner, the interactive control includes input type controls (such as buttons, drop-down menus, text boxes) and composite controls (such as multiple selection drop-down boxes, drag-and-drop chart components, etc.), which realize human-computer interaction functions.

[0081] In the embodiment, the multiple selection mode allows the user to select multiple field values (such as multiple categories, labels, time periods, etc.) in the source table or allows the user to select multiple source tables to trigger the linkage table data display at the same time. For example, the selected multiple source table field values are used as linkage conditions in the subsequent, and the linkage table will be aggregated, filtered or displayed in a union set according to these values. For example, in sales data analysis, the user can check multiple provinces, and the linkage table will synchronously display the sales data corresponding to all the checked provinces.

[0082] The non-cancellable mode means that once the user selects a field value, the field value cannot be unselected, and the "at least one" of the field value is kept active to prevent the linkage condition from being empty or causing the dashboard state to reset, so as to ensure the validity of the linkage logic. It is used to prevent the key field from being null. For example, in the KPI indicator dashboard, a certain dimension (such as "current quarter") must always be selected to prevent the user from mistakenly unselecting all options and causing the linkage chart to fail.

[0083] And the default selected mode (Default Selected Mode) refers to the system default selection of one or more field values as the initial value of the trigger condition before the interactive operation is performed, ensuring that the dashboard displays meaningful field values when it is initially loaded. Improve user experience. For example, when the user opens the dashboard interface, the system default field value is "the latest month" to trigger the dynamic display of this field value.

[0084] Compared with the traditional manual input rule, this step reduces the probability of configuration errors by providing interactive controls or field preview and verification functions through the dashboard interface. In terms of implementation, the dashboard interface is rendered through the front-end framework (such as React), the back-end database stores the table structure, and the JSON format linkage configuration information is stored.

[0085] In the embodiments of the present disclosure, the linkage configuration information is obtained through step 110, and the next step is to execute step 120 to obtain structured linkage rules using the information.

[0086] Optionally, the structured linkage rules are automatically generated by parsing the JSON format linkage configuration information obtained in step 110, including:

[0087] Determine the trigger type according to the source table and the linkage table, the trigger type includes single table trigger and multi-table combination trigger;

[0088] Convert the linkage condition into a data mapping relationship and an executable SQL query statement;

[0089] Store the trigger type, data mapping relationship, and interaction options as structured linkage rules.

[0090] Among them, the single table trigger corresponds to a single source table, and the multi-table combination trigger corresponds to multiple source tables (such as order volume table and passenger flow table multi-source data joint trigger).

[0091] This automatic parsing process eliminates the complex steps of manually defining rules, ensures the accuracy of the rules, and guides the logic of subsequent triggering and filtering.

[0092] Among them, if the parsing result contains only one source table, it is a single table trigger, and if the parsing result contains multiple source tables (such as order volume table and passenger flow), it is a multi-table combination trigger. The automatic parsing process eliminates the complex steps of manually defining rules, the linkage rules are based on standardized JSON format, ensuring the accuracy of the logic, and providing guidance for subsequent triggering and filtering. In terms of implementation, the JSON parser is used to extract the linkage configuration information, the trigger logic is determined to be a single table trigger or a multi-table combination trigger, the SQL generator converts the linkage condition, and the linkage rules are stored in memory or database for subsequent calls.

[0093] In the embodiment of the present disclosure, the step 130 can include the following specific steps:

[0094] The user action is listened as a user interaction event, and the field value selected by the user action is obtained;

[0095] According to the trigger type in the linkage rule and the field value selected by the user action, a corresponding trigger instruction is generated.

[0096] In the embodiment, listening to the "user action" can refer to listening to operations such as "click, check, switch, etc.", and the "field value" refers to the field value selected by the user operation. The "trigger instruction" contains the user-selected field value and specifies the linkage table.

[0097] The user action and the trigger type are part of the interaction options, and the user action is used as a trigger parameter to ensure the accuracy of the trigger instruction. In an implementation, the user click is captured through a JavaScript event listener, and the trigger instruction is generated in combination with the linkage rule.

[0098] In the embodiment of the present disclosure, the step 140 specifically includes the following steps:

[0099] Based on the field value in the trigger instruction and the data mapping relationship in the linkage rule, a corresponding SQL query statement is generated;

[0100] The SQL query statement is executed to filter or aggregate the data in the linkage table to obtain updated linkage table display data.

[0101] In an implementation, executing the SQL query statement to filter or aggregate the data in the linkage table includes:

[0102] Based on the data mapping relationship defined in the linkage rule, a multi-table joint SQL query statement is constructed, and the multi-table joint includes a linkage condition between tables established based on the data mapping relationship;

[0103] Based on the multi-table joint SQL query statement execution, the database is accessed to extract linkage data that meets the linkage condition;

[0104] The extracted linkage data is subjected to field filtering, grouping aggregation, or sorting processing to obtain updated linkage table display data.

[0105] In a further implementation, the board linkage method further includes the following steps:

[0106] Based on the field value, a prompt information is generated, and the user is prompted in the prompt information that the current linkage configuration information does not match any linkage data.

[0107] In real time, the updated linkage table display data is displayed in real time as a chart (such as a line chart) or a table on the dashboard interface. Optionally, during the display process, the display state is dynamically controlled according to the interaction control parameters in the linkage rule.

[0108] The embodiment provides a dashboard linkage system for implementing the above-mentioned dashboard linkage method, as shown in the figure. Figure 2 The system architecture shown includes a configuration module 210, a rule engine module 220, an event listening module 230, a data processing module 240, a display module 250, and a database 260, which cooperatively implement a closed loop from configuration to rendering.

[0109] First, the configuration module 210 supports users to enter a setting portal through the dashboard interface, configure source tables, linkage tables, linkage conditions, and interaction options (including interaction types, operation objects, and their trigger parameters), and generate configuration data structures in JSON format. Compared with manual rule input, the configuration module 210 simplifies the operation process, ensures accurate configuration, and reduces errors. The generated configuration information provides efficient input for the rule engine module 220.

[0110] Based on the above-mentioned linkage configuration information, the rule engine module 220 parses the JSON format data to generate structured linkage rules, including trigger types and field matching relationships. Automatic parsing eliminates the complex steps of manual rule definition, and the linkage rules based on the formatted data of the configuration information ensure accurate logic. The generated linkage rules guide subsequent triggering and data filtering, improving data processing efficiency.

[0111] Subsequently, the event listening module 230 detects user interaction events on the source table, such as clicking to select a specific row, and judges whether to enable the multi-selection mode. Based on the trigger parameters of the linkage rule and the interaction option, a trigger instruction is generated, containing the field values selected by the user. This fast triggering process ensures efficient connection from interaction to filtering, and the linkage rule and the interaction option ensure accurate instructions and reduce invalid triggering.

[0112] The data processing module 240 responds to the trigger instruction, filters linkage data from the linkage table in the database 260 based on the linkage rule, generates updated linkage table display data, which may involve filtering or aggregation, and displays it on the dashboard interface. Automatic filtering replaces manual queries, reducing steps and errors, and the linkage rule ensures accurate filtering.

[0113] Finally, the display module 250 renders the updated linkage table display data into a chart or a table, and controls the display state according to the interaction options (interaction types, operation objects, and their trigger parameters), such as highlighting the selected row, default selection, or non-cancellable mode. This fast rendering and intuitive feedback reduces user verification time, and the interaction option supports flexible display control.

[0114] An embodiment of a dashboard linkage method is provided below in the context of a hotel scenario. In the context of hotel operation data monitoring, users need to analyze the correlation between order volume and performance trends.

[0115] The user first enters the dashboard interface and selects the order volume source table (containing fields: store ID, date, order amount) and the performance trend linkage table (containing fields: date, sales) through the interactive controls of the "analysis function" entry. Configure the linkage condition "order volume source table. Date = performance trend linkage table. Date" (supporting field value equality or regular matching) and the interaction options (interaction type: click; operation object: source table row; interaction control parameters: highlight display, default selection, non-cancelable mode, multi-selection mode).

[0116] The dashboard linkage system generates linkage configuration information based on user settings, integrates source tables, linkage tables, linkage conditions, and interaction options, and generates JSON format data structures. The dashboard interface provides field preview and verification functions to ensure accurate configuration, simplifies the operation process, and reduces the probability of data mapping errors through dashboard interface configuration and automated parsing and filtering.

[0117] Based on the above linkage configuration information, the JSON format data is parsed to generate structured linkage rules, including trigger types (such as single table-based triggers), data mapping relationships (such as date field associations), and interaction control parameters (such as highlight display, default automatic triggering, and non-cancelable mode). Linkage rules are based on standardized formats to ensure accuracy and guide subsequent triggering and data filtering.

[0118] Subsequently, the dashboard linkage system detects user interaction events, such as clicking on a specific date row (e.g., date = 2025-07-23), and determines whether to enable multi-selection mode. If it is a single selection mode, the dashboard linkage system extracts the single source table click row field value and filters according to a single condition; if it is a multi-selection mode, it aggregates multiple source table field values and filters according to a combined condition. Based on the linkage rules, the dashboard linkage system generates a trigger instruction containing the user-selected field value (e.g., date). The trigger instruction is based on the interaction control parameters (e.g., click row) to ensure accuracy and shorten the operation-to-filtering time.

[0119] Through the above trigger instruction, the dashboard linkage system responds and filters data from the performance trend linkage table based on the linkage rules to generate updated linkage table display data and obtain matching field data (e.g., sales records for date = 2025-07-23), which may involve filtering (e.g., filtering specific dates) or aggregation (e.g., aggregating sales by date). Efficient filtering provides accurate support for rendering.

[0120] Finally, the board linkage system renders the updated linkage table display data into a line chart to show performance trends and controls the linkage state according to the interactive control parameters, highlighting the selected source table row and the corresponding linkage table row (such as the sales data of date = 2025-07-23). If the default automatic trigger is enabled, the board interface automatically triggers the first linkage when loaded. If the non-cancellable mode is enabled, the linkage state is restricted from being cancelled. Fast rendering and intuitive feedback ensure that users can obtain analysis results in a timely manner.

[0121] This embodiment forms an efficient linkage process by obtaining linkage configuration information, parsing linkage rules, triggering automatic filtering and rendering feedback, which is overall superior to the cumbersome manual query and inefficient response of traditional systems.

[0122] Taking the average single price analysis based on the order volume source table and customer flow source table as an example, the board linkage method of the embodiment is described.

[0123] Referring to the above embodiment, the user enters the "batch linkage" entry of the board interface through the interactive control, configures the order volume source table (fields: store ID, order amount), the customer flow source table (fields: store ID, customer flow), and the average single price analysis linkage table (fields: store ID, average single price), sets the linkage conditions (such as "order volume source table. store ID = average single price analysis linkage table. store ID" and "customer flow source table. store ID = average single price analysis linkage table. store ID", supporting field value equality or regular matching), and the interactive options (interaction type: click; operation object: source table row; interaction control parameters: highlight display, multi-selection mode, default selection, and allow cancellation). The board interface verifies the data mapping relationship to ensure that the multi-table combination trigger configuration is accurate, simplifies the operation, and reduces the risk of errors.

[0124] Referring to the above embodiment, the board linkage system parses the linkage configuration information, generates structured linkage rules, defines multi-table combination triggers and data mapping relationships (such as store ID association), and ensures that the data mapping relationship is logically correct to guide multi-table data filtering.

[0125] Referring to the above embodiment, the user clicks to select rows (such as store ID = 1, 2) on the order volume source table or the customer flow source table. The board linkage system detects the user interaction event, aggregates multi-source table field values based on the multi-selection mode, and generates a trigger instruction containing the selected field values (such as store ID).

[0126] Referring to the above embodiment, through the trigger instruction, the board linkage system filters data from the average single price analysis linkage table based on the linkage rules, generates updated linkage table display data, and involves filtering (such as filtering records of a specific store ID) or aggregation (such as calculating the ratio of order amount to customer flow).

[0127] Referring to the above embodiments, the dashboard linkage system renders the updated linkage table display data into a table, displays the single price analysis results of each store, and controls the linkage state according to the interaction control parameters, highlights the selected source table row and linkage table row, and if the default automatic triggering is enabled, the first linkage is automatically triggered when the dashboard interface is loaded, and if the cancel permission is enabled, the linkage state can be canceled.

[0128] Figure 3 is a module schematic diagram of an embodiment of the dashboard linkage system provided by the embodiments of the present disclosure. As shown in Figure 3 the dashboard linkage system 300 of the present disclosure includes but is not limited to:

[0129] The linkage configuration module 310 obtains the linkage configuration information set by the user on the dashboard interface, and the linkage configuration information includes at least one source table, a linkage table associated with the source table, a linkage condition between the tables, and an interaction option.

[0130] The rule construction module 320 parses the linkage configuration information and constructs a structured linkage rule based on the parsing result.

[0131] The detection module 330 detects the user interaction event of the source table, executes the table triggering logic on the user interaction event according to the linkage rule, and obtains a triggering instruction.

[0132] The data filtering module 340 triggers the linkage data filtering in the linkage table based on the linkage rule as the updated linkage table display data in response to the triggering instruction.

[0133] The rendering module 350 renders the updated linkage table display data to the dashboard interface.

[0134] Optionally, the linkage configuration module 310 is specifically configured to:

[0135] display an interaction control for table selection on the dashboard interface, and determine at least one source table and a linkage table associated with the source table in response to the user's selection of the interaction control, the linkage table being associated with the source table based on a preset data mapping relationship, and the linkage condition being generated based on the data mapping relationship;

[0136] receive the interaction option set by the user through the dashboard interface, the interaction option being one of a multiple selection mode, an uncancelable mode, and a default selected mode;

[0137] encapsulate the source table, the linkage table of the source table, the linkage condition, and the interaction option into a configuration data structure as the linkage configuration information.

[0138] Optionally, the rule construction module 320 is specifically configured to:

[0139] determine a trigger type according to the source table and the linkage table, the trigger type being a single-table trigger or a multi-table combination trigger;

[0140] convert the linkage condition into a data mapping relationship and an executable SQL query statement;

[0141] store the trigger type, the data mapping relationship and the interaction option as a structured linkage rule.

[0142] Optionally, the detection module 330 is specifically configured to:

[0143] listen to a user action on the source table, determine the user interaction event, and obtain a field selected by the user action and a field value of the field;

[0144] generate the trigger instruction based on the trigger type in the linkage rule and the field value.

[0145] Optionally, the data filtering module 340 is specifically configured to:

[0146] generate a corresponding SQL query statement based on the field value in the trigger instruction and the data mapping relationship in the linkage rule;

[0147] execute the SQL query statement to filter or aggregate the data in the linkage table, and obtain updated linkage table display data.

[0148] Optionally, the data filtering module 340 is specifically configured to:

[0149] construct a multi-table joint SQL query statement based on the data mapping relationship defined in the linkage rule, the multi-table joint including the inter-table linkage condition between the source table and the linkage table based on the data mapping relationship;

[0150] access the database based on the multi-table joint SQL query statement, and extract linkage data meeting the inter-table linkage condition;

[0151] perform field filtering, grouping aggregation or sorting processing on the extracted linkage data, and obtain updated linkage table display data.

[0152] Optionally, the data processing module 340 is specifically configured to:

[0153] generate a prompt information based on the field value, and display the prompt information on the board interface.

[0154] The board linkage system integrates the source table, linkage table, linkage condition and interactive option in the board interface, replaces the traditional manual field input mode, simplifies the configuration process and reduces the error rate. The linkage configuration information is parsed to construct the linkage rule, the standardization and automatic generation of the rule can be realized, and the accuracy and efficiency of data linkage are improved. When the user interaction event is detected, the filtering logic can be automatically triggered and the updated linkage table display data is generated, the interactive display is realized, and the manual query cumbersome operation is avoided.

[0155] Compared with the traditional manual configuration mode, the visual configuration, automatic filtering and rapid rendering of the embodiment of the disclosure significantly improve the response speed and accuracy of the board linkage, and are suitable for data visualization needs in multiple scenes such as hotel operation data.

[0156] The modules of the system can be connected to each other through a data interface, and the board linkage system can be embedded into a front-end development tool as an independent software module, or can provide an interface as a cloud service for remote calling by developers.

[0157] The embodiment of the application also provides a board linkage device, including a processor and a memory, wherein the memory stores executable instructions of the processor. The processor is configured to execute the steps of the board linkage method by executing the executable instructions.

[0158] As shown above, the board linkage device of the application can integrate the source table, linkage table, linkage condition and interactive option in the board interface, replace the traditional manual field input mode, simplify the configuration process and reduce the error rate. The linkage configuration information is parsed to construct the linkage rule, the standardization and automatic generation of the rule can be realized, and the accuracy and efficiency of data linkage are improved. When the user interaction event is detected, the filtering logic can be automatically triggered and the updated linkage table display data is generated, the interactive display is realized, and the manual query cumbersome operation is avoided. Compared with the traditional manual configuration mode, the visual configuration, automatic filtering and rapid rendering of the embodiment of the disclosure significantly improve the response speed and accuracy of the board linkage, and are suitable for data visualization needs in multiple scenes such as hotel operation data.

[0159] Those skilled in the art can understand that each aspect of the application can be implemented as a system, a method or a program product. Therefore, each aspect of the application can be embodied in the form of a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, which can be collectively referred to as "circuitry", "module" or "platform" here.

[0160] Figure 4 is a structural schematic diagram of an electronic device of the application. The following refers to Figure 4The electronic device 400 according to this embodiment of the present application will be described. Figure 4 The electronic device 400 shown is merely one example and should not be taken as limiting the scope of the present application embodiments.

[0161] As shown in Figure 4 FIG. 4, the electronic device 400 is in the form of a general computing device. The components of the electronic device 400 can include, but are not limited to, at least one processing unit 410, at least one memory unit 420, a bus 430 that connects the various platform components including the memory unit 420 and the processing unit 410, a display unit 440, etc.

[0162] The memory unit stores program code that can be executed by the processing unit 410 such that the processing unit 410 performs the steps described in the above watch linkage method section according to various exemplary embodiments of the present application. For example, the processing unit 410 can perform the steps as shown in Figure 1

[0163] The memory unit 420 can include a readable medium in the form of volatile memory units such as a random access memory (RAM) 421 and / or a cache memory unit 422, and can further include a read-only memory (ROM) 423.

[0164] The memory unit 420 can further include program / utility 424 having a set of at least one program modules 425, including but not limited to an operating system, one or more applications, other program modules, and program data, and can include implementation of a network environment, each or a combination of these examples.

[0165] The bus 430 can be representative of one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration bus, a processing bus, or a local bus using any of a variety of bus structures.

[0166] ​The electronic device 400 can also communicate with one or more external devices 401 such as a keyboard or a pointing device, a Bluetooth device, etc.; other devices that enable a user to interact with the electronic device 400; and / or any devices (e.g., a router, a modem, a peer device etc.) that enable the electronic device 400 to communicate with one or more other computing devices. Such communication can occur via an input / output (I / O) interface 450. Still yet, the electronic device 400 can communicate with one or more networks, such as a local area network (LAN), a wide area network (WAN), and / or the Internet, through a network adapter 460. The network adapter 460 can communicate with the other components of the electronic device 400 via the bus 430. It should be understood that, although not shown explicitly, other hardware and / or software components could be used in conjunction with the electronic device 400. These include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

[0167] The embodiments of the present disclosure also provide a computer readable storage medium for storing a program, which, when executed, implements the steps of the Kanban linkage method. In some possible implementation manners, various aspects of the present disclosure can also be implemented in the form of a program product, which includes program codes for causing a terminal device to perform the steps of the Kanban linkage method described in the foregoing description of the present disclosure when the program product is run on the terminal device.

[0168] As shown in Figure 5 The computer program product 500 for implementing the method described above according to the embodiments of the present disclosure can take the form of a portable compact disc read-only memory (CD-ROM) and include program codes, and can be run on a terminal device, such as a personal computer. However, the computer program product of the present disclosure is not limited to this, and in the present document, the readable storage medium can be any tangible medium containing or storing a program, which can be used by or in conjunction with an instruction execution system, apparatus or device.

[0169] The computer program product can take any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium, for example, can be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any combination of the above. More specific examples (a non-exhaustive list) of the readable storage medium include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0170] The computer readable storage medium can include a computer-readable medium in baseband or propagated as a carrier wave in a propagated signal, wherein the latter embodiment includes a computer-readable medium. The propagated signal can take a variety of forms including, but not limited to, electromagnetic, optical, or any suitable combination thereof. Computer readable medium can be any medium that can be read by a machine (e.g., a computer). The computer-readable medium can include, but is not limited to, volatile memory, non-volatile memory, volatile memory, non-volatile memory, magnetic storage, and optical storage.

[0171] The program code can be implemented in any of a variety of programming languages, including object-oriented programming languages such as Java, C++, and the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider (ISP).

[0172] In summary, the present disclosure aims to provide a dashboard linkage method, system, device and storage medium, which integrates source table, linkage table, linkage condition and interaction option in the dashboard interface, replaces the traditional manual field input method, simplifies the configuration process and reduces the error rate. Analyzing the linkage configuration information to construct the linkage rule can realize the standardization and automatic generation of the rule, improve the accuracy and efficiency of data linkage. When detecting the user interaction event, the filtering logic can be automatically triggered and the updated linkage table display data can be generated to realize the interactive display and avoid the tedious manual query operation.

[0173] Compared with the traditional manual configuration method, the present disclosure significantly improves the response speed and accuracy of the dashboard linkage through visual configuration, automatic filtering and fast rendering, and is suitable for data visualization requirements in multiple scenarios such as hotel operation data.

[0174] The above is further detailed description of the present application in combination with specific preferred embodiments, and cannot be deemed as limitation of the specific implementation of the present application to these descriptions. For those skilled in the art to which the present application belongs, without departing from the concept of the present application, a number of simple deductions or substitutions can be made, and all of them shall be deemed as falling within the protection scope of the present application.

Claims

1. A Kanban linkage method, characterized in that, include: Obtain the linkage configuration information set by the user on the dashboard interface. The linkage configuration information includes at least one source table, a linkage table associated with the source table, inter-table linkage conditions, and interaction options. The linkage configuration information is parsed, and structured linkage rules are constructed based on the parsing results; Detect user interaction events in the source table, and execute table triggering logic on the user interaction events according to the linkage rules to obtain triggering instructions; In response to the trigger command, the linkage data in the linkage table is selected based on the linkage rules and displayed as the updated linkage table data. The updated linked table data is rendered and displayed on the dashboard interface.

2. The Kanban linkage method according to claim 1, characterized in that, The step of obtaining the linkage configuration information set by the user on the dashboard interface includes: The dashboard interface displays interactive controls for table selection. In response to the user's selection of the interactive controls, at least one source table and a linked table associated with the source table are determined. The linked table is associated with the source table based on a preset data mapping relationship, and the linkage conditions are generated based on the data mapping relationship. The system receives interactive options set by the user through the dashboard interface, where the interactive options are one of a multi-select mode, a non-cancelable mode, and a default selected mode. The source table, the linked table of the source table, the linkage conditions, and the interaction options are encapsulated into a configuration data structure as the linkage configuration information.

3. The Kanban linkage method according to claim 2, characterized in that, The structured linkage rules constructed based on the parsing results include: The trigger type is determined based on the source table and the linked table, and the trigger type is either a single table trigger or a multi-table combined trigger. The linkage conditions are converted into data mapping relationships and executable SQL query statements; The trigger type, data mapping relationship, and interaction options are stored as structured linkage rules.

4. The Kanban linkage method according to claim 1, characterized in that, The detection of user interaction events in the source table includes: Listen to user actions on the source table, determine the user interaction event, and obtain the field selected by the user action and its field value; The step of executing the table triggering logic for the user interaction event according to the linkage rule to obtain the triggering instruction includes: The trigger instruction is generated based on the trigger type and the field value in the linkage rule.

5. The Kanban linkage method according to claim 4, characterized in that, The response to the trigger command, triggering the filtering of linked data in the linked table based on the linked rules as the updated linked table display data, includes: Based on the field values ​​in the triggering instruction and the data mapping relationship in the linkage rule, a corresponding SQL query statement is generated; Execute the SQL query statement to filter or aggregate the data in the linked table and obtain the updated linked table display data.

6. The Kanban linkage method as described in claim 5, characterized in that, The execution of the SQL query statement to filter or aggregate data in the linked table includes: Based on the data mapping relationship defined in the linkage rules, construct a SQL query statement for multi-table union, wherein the multi-table union includes the inter-table linkage conditions established between the source table and the linkage table based on the data mapping relationship; Access the database based on the multi-table combined SQL query statement and extract linked data that meets the inter-table linkage conditions; The extracted linked data is processed by field filtering, grouping aggregation, or sorting to obtain the updated linked table display data.

7. The Kanban linkage method according to claim 5, characterized in that, The Kanban linkage method also includes: If the SQL query fails to retrieve linked data from the linked table, the following steps are performed: A prompt message is generated based on the field value and displayed on the dashboard interface.

8. A signboard linkage system, characterized in that, include: The linkage configuration module obtains the linkage configuration information set by the user on the dashboard interface. The linkage configuration information includes at least one source table, a linkage table associated with the source table, inter-table linkage conditions, and interaction options. The rule construction module parses the linkage configuration information and constructs structured linkage rules based on the parsing results; The detection module detects user interaction events in the source table, executes table triggering logic on the user interaction events according to the linkage rules, and obtains triggering instructions. The data filtering module, in response to the triggering command, triggers the filtering of linked data in the linked table based on the linked rules as the updated linked table display data; The rendering module renders the updated linked table display data to the dashboard interface.

9. An electronic device, characterized in that, include: processor; A memory in which executable instructions of the processor are stored; The processor is configured to execute the steps of the Kanban linkage method according to any one of claims 1 to 7 by executing the executable instructions.

10. A computer-readable storage medium for storing a program, characterized in that, When the program is executed, it implements the steps of the Kanban linkage method as described in any one of claims 1 to 7.

Images