Report development method and device based on generic indicators
Through the concept of generic indicators, the report development of the data analysis platform is simplified, and the problems of high cost of customized reports and complex maintenance in the existing technology are solved, achieving efficient indicator management and development efficiency improvement.
Patent Information
- Application Number
- CN202011446058.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-08
- Publication Date
- 2024-12-24
- Estimated Expiration
- 2040-12-08
AI Technical Summary
When existing data analysis platforms deal with complex business logic and diversified needs, they are difficult to be compatible with general indicators, resulting in high cost of development and complex maintenance of customized reports, and a large number of indicators with similar names increase maintenance costs.
Using a report development method based on generic metrics, by creating general query metrics and generic query metrics, defining their corresponding data sources, and partitioning them in the table. Configuring the call method for generic query metrics, and using pre-configured call method Obtain the data, summarize and feedback to the front-end display.
The report development process is simplified, development costs are reduced, development efficiency is improved, and the lightweight management of the indicator cluster is realized, which significantly reduces the number of customized components development.
Smart Images

Figure CN112905631B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of big data technology, and in particular to a report development method and device based on generic indicators. Background Art
[0002] With the continuous development of data management concepts, real-time comparison of industry data, comparison of data flow, and cross-domain data set analysis are becoming more and more important in daily business decisions. General data analysis platforms are increasingly unable to meet the various analysis concepts of data analysts. Currently, general data analysis tools mostly use the following methods to achieve these needs:
[0003] 1. Develop a customized reporting process: In the process of building universal data indicators, there is a part of data that cannot be achieved through universal indicators or the cost of achieving it is high. When the universal data analysis platform cannot be easily compatible, manpower is often arranged to develop a customized reporting process according to demand.
[0004] 2. Continuous iteration of customized components: Even if some data can be defined as indicators, their business logic is too complex or not a popular demand. At this time, the general data analysis platform will convert customized requirements into general requirements for compatibility, and add different components to the analysis platform iteration, which increases user operation costs, reduces user experience, and also increases subsequent maintenance costs.
[0005] 3. There are too many indicators with similar names, which increases maintenance costs: With the expansion of the market data domain, different business departments may have different business understandings of the same indicator, which will result in a large number of indicators with similar names, such as offline sales amount, online sales amount, etc. This results in a large data middle layer with many indicators. Summary of the invention
[0006] The purpose of the present invention is to provide a report development method and device based on generic indicators, which can simplify the report development process and improve development efficiency while reducing development costs.
[0007] In order to achieve the above object, a first aspect of the present invention provides a report development method based on generic indicators, comprising:
[0008] Create common query indicators and generic query indicators;
[0009] Define the data sources corresponding to general query indicators and generic query indicators respectively;
[0010] Create a table and partition the common query indicators and generic query indicators in the table;
[0011] Direct the generic query indicators to configure the calling method of the generic query indicators;
[0012] Data requests are made based on the indicator content in the table, and query data corresponding to general query indicators and generic query indicators are obtained from the data source using a pre-configured calling method;
[0013] The query data corresponding to the general query indicators and generic query indicators are aggregated and integrated, and fed back to the front-end for display.
[0014] Preferably, the method for creating a general query index and a generic query index includes:
[0015] Define general query indicators with normal scope and generic query indicators without actual business technical scope through the indicator definition module;
[0016] The generic query indicator includes a content description of an indicator name and an indicator unit, and the generic query indicator may be a sub-indicator of the general query indicator.
[0017] Preferably, the method of defining the data sources corresponding to the general query index and the generic query index respectively includes:
[0018] Internal data sources for targeting common query indicators and external data sources for targeting generic query indicators are defined through the data source definition module;
[0019] The external data source includes one or more of a database, an API interface, a JAR package, a KV text, and an EXCEL document;
[0020] The data source information of the database includes the service IP, port and database name. The data source information of the API interface includes the interface address, input parameter information and return parameter information. The data source information of the JAR package includes the JAR name, full path of the interface class and method name.
[0021] Preferably, the method of creating a table and partitioning the general query index and the generic query index in the table includes:
[0022] Use the visualization platform to create a table and set the table content order to analysis fields, general query indicators, and generic query indicators.
[0023] Preferably, the method for orienting the generic query indicator to configure the calling mode of the generic query indicator includes:
[0024] The generic targeting module is used to orient the calling method of the generic query indicator to the corresponding generic query indicator, and the generic query indicator and the calling method are in a one-to-one correspondence. At the same time, the general query indicator and the analysis field in the calling method are dimensionally mapped.
[0025] Furthermore, a method for performing a data request based on the indicator content in the table and obtaining query data corresponding to the general query indicator and the generic query indicator from the data source using a pre-configured calling method includes:
[0026] Initiate data request based on generic query indicators in the table, and after indicator screening, use corresponding calling methods to access external data sources from one or more channels including database, API interface, JAR package, KV text, and EXCEL document to obtain query data for generic indicators;
[0027] Initiate a data request based on the general query indicators in the table, and after indicator screening, use the corresponding calling method to obtain the query data of the general indicators from the internal data source.
[0028] Preferably, the method of aggregating and fusing the query data corresponding to the general query index and the generic query index and feeding them back to the front end for display includes:
[0029] According to the analysis fields of dimension mapping, the query data of generic indicators and common indicators in the table are summarized and fused, and the fused summary data is fed back to the front-end page for visual display.
[0030] Compared with the prior art, the report development method based on generic indicators provided by the present invention has the following beneficial effects:
[0031] In the report development method based on generic indicators provided by the present invention, it is first necessary to clarify the general query indicators and generic query indicators required for the report, and define the data sources corresponding to the general query indicators and the generic query indicators respectively, then create a table to partition the general query indicators and the generic query indicators in the table, and at the same time, configure the calling method of the generic query indicators in a targeted manner, then make a data request based on the indicator content in the table, and use a pre-configured calling method to obtain the query data corresponding to the general query indicators and the generic query indicators from the data source respectively, and finally summarize and merge the query data corresponding to the general query indicators and the generic query indicators, and feed them back to the front-end page for display.
[0032] It can be seen that the present invention introduces the concept of generic query indicators. Since one generic query indicator can represent N general query indicators, it can achieve lightweight management of indicator clusters. In addition, compared with the report development process of general query indicators, the introduction of generic query indicators can significantly reduce the number of customized components developed in general query indicators and improve report development efficiency.
[0033] A second aspect of the present invention provides a report development device based on generic indicators, which is applied to the report development method based on generic indicators described in the above technical solution, and the device includes:
[0034] An indicator creation unit, used to create common query indicators and generic query indicators;
[0035] A data source definition unit, used to define data sources corresponding to common query indicators and generic query indicators respectively;
[0036] A table creation unit is used to create a table and partition the common query index and the generic query index in the table;
[0037] A calling configuration unit is used to direct the generic query indicator to configure the calling method of the generic query indicator;
[0038] A data request unit, used to make data requests based on the indicator content in the table, and to obtain query data corresponding to the general query indicator and the generic query indicator from the data source using a pre-configured calling method;
[0039] The data fusion unit is used to aggregate and fuse the query data corresponding to the general query indicators and the generic query indicators, and feed them back to the front-end for display.
[0040] Preferably, the indicator creation unit is further used for:
[0041] Define general query indicators with normal scope and generic query indicators without actual business technical scope through the indicator definition module;
[0042] The generic query indicator includes a content description of an indicator name and an indicator unit, and the generic query indicator may be a sub-indicator of the general query indicator.
[0043] Compared with the prior art, the beneficial effects of the report development device based on generic indicators provided by the present invention are the same as the beneficial effects of the report development method based on generic indicators provided by the above technical solution, which will not be elaborated here.
[0044] A third aspect of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned current limiting method for microservices are executed.
[0045] Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present invention are the same as the beneficial effects of the report development method based on generic indicators provided by the above technical solution, which will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:
[0047] Figure 1A flowchart of a report development method based on generic indicators in an embodiment of the present invention;
[0048] Figure 2 Another flowchart of a report development method based on generic indicators in an embodiment of the present invention;
[0049] Figure 3 This is an example diagram of the use of the Widget component scenario in an embodiment of the present invention;
[0050] Figure 4 This is an example diagram comparing the traditional report development method in the embodiment of the present invention with the report development method in this embodiment;
[0051] Figure 5 This is an example diagram of report data lineage tracing in an embodiment of the present invention. DETAILED DESCRIPTION
[0052] In order to make the above-mentioned purposes, features and advantages of the present invention more obvious and easy to understand, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work belong to the scope of protection of the present invention.
[0053] Embodiment 1
[0054] See also Figure 1 and Figure 2 This embodiment provides a report development method based on generic indicators, including:
[0055] Create general query indicators and generic query indicators; define the data sources corresponding to the general query indicators and generic query indicators respectively; create a table to represent the general query indicators and generic query indicators in the table in partitions; target the generic query indicators to configure the calling method of the generic query indicators; make data requests based on the indicator content in the table, and use the pre-configured calling method to obtain the query data corresponding to the general query indicators and generic query indicators from the data source respectively; summarize and merge the query data corresponding to the general query indicators and generic query indicators, and feed them back to the front-end for display.
[0056] In the report development method based on generic indicators provided in this embodiment, it is first necessary to clarify the general query indicators and generic query indicators required for the report, and define the data sources corresponding to the general query indicators and generic query indicators respectively, and then create a table to partition the general query indicators and generic query indicators in the table, and at the same time, configure the calling method of the generic query indicators in a targeted manner, and then make data requests based on the indicator content in the table, and use the pre-configured calling method to obtain the query data corresponding to the general query indicators and generic query indicators from the data source respectively, and finally summarize and merge the query data corresponding to the general query indicators and generic query indicators, and feed them back to the front-end page for display.
[0057] It can be seen that this embodiment introduces the concept of generic query indicators. Since one generic query indicator can represent N general query indicators, it can achieve lightweight management of indicator clusters. In addition, compared with the report development process of general query indicators, the introduction of generic query indicators can significantly reduce the number of customized components developed in general query indicators and improve report development efficiency.
[0058] It needs to be explained that generic search indicators are defined as a series of indicators that have only the meaning of indicators but are not supported by actual caliber and data source. The caliber and actual data source of the indicators are postponed to the stage of solidified report creation or real-time data analysis. The difference between it and general indicators is that generic indicators do not need to be bound to actual data sources during the definition process. For example, large retail companies create general sales indicators such as online sales amount and offline sales amount, which have clear indicator groups with specific calibers. If you use generic indicators, you only need to create a sales amount indicator.
[0059] In the above embodiment, the method for creating a general query index and a generic query index includes:
[0060] The indicator definition module is used to define general query indicators of normal scope and generic query indicators without actual business technical scope; the generic query indicators include a content description of the indicator name and indicator unit. For example, the generic query indicator can be a sub-indicator of the general query indicator.
[0061] In specific implementation, in addition to defining general query indicators with normal caliber, the indicator definition module also needs to define generic query indicators without actual business technical caliber. Among them, generic query indicators only contain descriptions of external content such as indicator names and indicator units, but have no actual business technical caliber as data support. They generally refer to a collection of indicators with similar meanings, such as the sales amount of small stores, the sales amount of online stores, and the sales amount of cloud stores, collectively referred to as sales amounts. In addition, the derived generic query indicators can also define calculation formulas between generic indicators, such as automatically calculating the sum of the sales amount of small stores and the sales amount of online stores through calculation formulas.
[0062] In the above embodiment, the method of defining the data sources corresponding to the general query index and the generic query index respectively includes:
[0063] The data source definition module directs the internal data source of general query indicators and the external data source of generic query indicators; the sources of external data sources include one or more of databases, API interfaces, JAR packages, KV texts, and EXCEL documents; the data source information of the database includes the service IP, port, and database name, the data source information of the API interface includes the interface address, input parameter information, and return parameter information, and the data source information of the JAR package includes the JAR name, the full path of the interface class, and the method name.
[0064] In specific implementation, the data source definition module is mainly used to define the information of the external data source, such as the service IP, port, database name, etc. under the database type; the interface address, input parameter information, return parameter information, etc. under the API interface; the JAR name, interface class full path, method name, etc. under the imported JAR package.
[0065] As we all know, generic query indicators generally need to obtain indicator data from external data sources, and general query indicators generally need to obtain indicator data from internal data sources. The reason is that the actual caliber and data source support of external data sources are uncertain, while the actual caliber and data source support of internal data sources are generally certain. For example, if a user wants to analyze the online sales data of his company and a competing company, he can define his company as a general query indicator and the competing company as a generic query indicator, and then obtain the query data through the corresponding data source.
[0066] In the above embodiment, the method of creating a table and partitioning the general query index and the generic query index in the table includes:
[0067] Use the visualization platform to create a table, and set the table content order to analysis field, common query index, and generic query index. For example, the analysis field is the query region.
[0068] In the above embodiment, the method for orienting the generic query indicator to configure the calling mode of the generic query indicator includes:
[0069] The generic targeting module is used to target the calling method of the generic query indicator with the corresponding generic query indicator, and the generic query indicator and the calling method are in a one-to-one correspondence. At the same time, dimension mapping is performed on the general query indicator and the analysis fields in the calling method, such as region.
[0070] In the above embodiment, the method for making a data request based on the indicator content in the table and obtaining the query data corresponding to the general query indicator and the generic query indicator from the data source respectively by using a pre-configured calling method includes:
[0071] Initiate a data request based on the generic query indicators in the table. After indicator screening, use the corresponding calling method to access the external data source from one or more channels such as database, API interface, JAR package, KV text, and EXCEL document to obtain the query data of the generic indicators; initiate a data request based on the general query indicators in the table. After indicator screening, use the corresponding calling method to obtain the query data of the general indicators from the internal data source.
[0072] In the above embodiment, the method for making a data request based on the indicator content in the table and obtaining the query data corresponding to the general query indicator and the generic query indicator from the data source respectively by using a pre-configured calling method includes:
[0073] Initiate data request based on generic query indicators in the table, and after indicator screening, use corresponding calling methods to access external data sources from one or more channels including database, API interface, JAR package, KV text, and EXCEL document to obtain query data for generic indicators;
[0074] Initiate a data request based on the general query indicators in the table, and after indicator screening, use the corresponding calling method to obtain the query data of the general indicators from the internal data source.
[0075] In the above embodiment, the method of aggregating and fusing the query data corresponding to the general query index and the generic query index and feeding them back to the front end for display includes:
[0076] According to the analysis fields mapped by the dimension, such as the region field, the query data of the generic indicators and the query data of the general indicators in the table are summarized and fused, and the fused summary data is fed back to the front-end page for visual display.
[0077] It should be noted that the main modules in this embodiment include four modules: data source definition module, indicator definition module, generic directional model and data access module. Figure 2 As shown, the data source definition module and the indicator definition module do not interfere with each other, and the generic orientation module and the data access module depend on the data source definition module and the indicator definition module.
[0078] In the data source definition module, users define one or more implementation methods such as data API interface, embedded JAR package, KV text, database Suning data, etc. to the external data source information; in the indicator definition module, users add their own generic indicators; in specific data analysis scenarios, external data source information is directed to the specified generic indicators, and data is queried through the data routing and implementation logic of the data access module.
[0079] Data source definition module: mainly used to define external data source information, such as service IP, port, database name, etc. under the database type; interface address, input parameter information, return parameter information, etc. under the API interface; JAR name, interface class full path, method name, etc. under the imported JAR package.
[0080] Indicator definition module: In addition to defining general query indicators with normal caliber, generic query indicators also need to be defined.
[0081] Generic directional model: It is the data source for the generic query indicator. At this time, it specifies the business technical caliber content of the generic query indicator. The directional content includes external data source encoding, dimension mapping KV set, and indicator mapping KV combination. It should be noted that it is for generic query indicator columns, not generic indicators, because in the same chart, the same generic query indicator can generate multiple columns, and the data source or logic of each column can be different. For example, the sales amount is refined into the small store sales amount from the small store interface data and the online store sales amount from the online store model data.
[0082] Data access module: mainly used to parse the configuration information of generic indicator columns, and route the data sources configured by generic indicator columns to different data channels, such as external API interfaces, built-in uploaded JAR packages or key-value pair files, etc.
[0083] See also Figure 2 For ease of understanding, the above-mentioned embodiment scheme is now described as an example:
[0084] Step 1: The user creates a common query indicator, such as total sales amount, based on the indicator model layer and the indicator acceleration layer.
[0085] Step 2: The online sales amount (generic query indicator 1) is processed into the database of the data mart through the ETL task, and the external data is defined in the data source definition module to clarify its calling method A.
[0086] Step 3: The offline sales amount (generic query indicator 2) is provided through the API interface of the offline data system, and the external data is defined in the data source definition module to clarify its calling method B.
[0087] Step 4: The user defines the sub-sales amount of the generic indicator in the indicator definition module, which are the online sales amount and the offline sales amount.
[0088] Step 5. The user creates a table in the visualization platform and selects the general total sales amount, offline sales amount, and offline sales amount indicators as the table content. The table content is sales region, total sales amount, online sales amount, and offline sales amount in order.
[0089] Step 6. Use the generic targeting model to perform generic targeting, direct call method A to the online sales amount column, direct call method B to the offline sales amount column, and perform dimension mapping on the region fields in the total sales amount, call method A, and call method B.
[0090] Step 7: Request the indicator data in the table.
[0091] Step 8: Use the data routing module to screen indicators, allocate the total sales amount to the data acceleration module for general indicator data request, and allocate the data access module for online sales amount and offline sales amount.
[0092] Step 9: Use the data access module to request data through the API interface and the built-in JAR method according to the targeted content of the generic query indicator.
[0093] Step 10: Aggregate the query data returned by the data request interface into the data fusion module, and perform data fusion of general query indicators and generic query indicators according to the regional fields of dimension mapping.
[0094] Step 11: Feedback the integrated data to the front-end page for display.
[0095] For example, Figure 3 It is a desktop widget component. The sales amount is a generic query indicator, and the total sales amount is displayed by default. The online sales amount and offline sales amount are generic directional indicators entered in advance. Users can define new directional content through the input button, or drag the currently developed JAR package or EXCEL / CSV file to the display area to generate a temporary generic directional indicator and display the corresponding sales amount.
[0096] Figure 4 It describes how to embed customized reports in the portal. On the left is the customization method used by the traditional solution, which embeds the customized report URL link into the portal iframe; on the right is the method used in this embodiment, which adapts the generic query index to the data caliber, so the user only needs to develop the data caliber to achieve it. Even if the business logic of the solution in this embodiment is complex, as long as the page components support it, the user does not need to perform full customization, and there is no need to use the URL embedding method. Only simple data interaction development for generic query indicators is required. At the same time, please refer to Figure 5 This embodiment also supports the lineage tracing function of report data for general query indicators and generic query indicators.
[0097] It can be seen that this embodiment can achieve the following effects:
[0098] Lightweight indicator management: The introduction of the concept of generic indicators is equivalent to just defining the meaning of the indicator, such as sales amount. The specific and clear types are placed in specific chart scenarios, which greatly reduces the number of indicator groups with similar names.
[0099] The customized development process is simplified and the customized development cost is reduced: the page design and data fusion parts of report development do not need to be repeatedly developed. Users only need to develop and maintain the data orientation part corresponding to the generic query indicators. This part can be an external API interface, an exported JAR package, a customized KV key-value pair or an EXCEL document, etc., which greatly shortens the development cycle and reduces the development and maintenance costs.
[0100] The number of custom components developed is reduced: only a set of generic query index design components and generic index orientation components need to be defined, and the rest can be implemented by the data access module. There is no need to define different components for different business scenarios.
[0101] Embodiment 2
[0102] This embodiment provides a report development device based on generic indicators, including:
[0103] An indicator creation unit, used to create common query indicators and generic query indicators;
[0104] A data source definition unit, used to define data sources corresponding to common query indicators and generic query indicators respectively;
[0105] A table creation unit is used to create a table and partition the common query index and the generic query index in the table;
[0106] A calling configuration unit is used to direct the generic query indicator to configure the calling method of the generic query indicator;
[0107] A data request unit, used to make data requests based on the indicator content in the table, and to obtain query data corresponding to the general query indicator and the generic query indicator from the data source using a pre-configured calling method;
[0108] The data fusion unit is used to aggregate and fuse the query data corresponding to the general query indicators and the generic query indicators, and feed them back to the front-end for display.
[0109] Preferably, the indicator creation unit is further used for:
[0110] Define general query indicators with normal scope and generic query indicators without actual business technical scope through the indicator definition module;
[0111] The generic query indicator includes a content description of an indicator name and an indicator unit, and the generic query indicator is a sub-indicator of the general query indicator.
[0112] Compared with the prior art, the beneficial effects of the report development device based on generic indicators provided by the embodiment of the present invention are the same as the beneficial effects of the report development method based on generic indicators provided by the above-mentioned embodiment 1, which will not be described in detail here.
[0113] Embodiment 3
[0114] This embodiment provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the report development method based on generic indicators are executed.
[0115] Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this embodiment are the same as the beneficial effects of the report development method based on generic indicators provided by the above technical solution, and will not be elaborated here.
[0116] A person skilled in the art can understand that all or part of the steps in the above-mentioned inventive method can be implemented by instructing related hardware through a program, and the above-mentioned program can be stored in a computer-readable storage medium. When the program is executed, it includes the steps of the above-mentioned embodiment method, and the storage medium can be: ROM / RAM, disk, optical disk, memory card, etc.
[0117] The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
Claims
1. A report development method based on generic indicators, characterized in that: include: Create common query indicators and generic query indicators; Define the data sources corresponding to general query indicators and generic query indicators respectively; Create a table and partition the common query indicators and generic query indicators in the table; Direct the generic query indicators to configure the calling method of the generic query indicators; Data requests are made based on the indicator content in the table, and query data corresponding to general query indicators and generic query indicators are obtained from the data source using a pre-configured calling method; Aggregate and merge the query data corresponding to the general query indicators and generic query indicators, and feed them back to the front-end for display and output; The method for directing the generic query indicator to configure the calling mode of the generic query indicator includes: The generic orientation module is used to orient the calling method of the generic query indicator to the corresponding generic query indicator, and the generic query indicator and the calling method are in a one-to-one correspondence. At the same time, the generic query indicator and the analysis field in the calling method are dimensionally mapped; The report development method based on generic indicators includes: Users create common query indicators based on the indicator model layer and indicator acceleration layer; The online sales amount is processed into the data mart database through ETL tasks, and the external data is defined in the data source definition module to clarify its calling method A; The offline sales amount is provided through the API interface of the offline data system, and the external data is defined in the data source definition module to clarify its calling method B; The user defines the sub-sales amount of the generic indicator in the indicator definition module, which are online sales amount and offline sales amount; The user creates a table in the visualization platform and selects the general total sales amount, offline sales amount, and offline sales amount indicators as the table content. The table content is sales region, total sales amount, online sales amount, and offline sales amount in order; Use the generic targeting model to perform generic targeting, direct call method A to the online sales amount column, direct call method B to the offline sales amount column, and perform dimension mapping on the total sales amount, call method A, and the region field in call method B; Perform request operations on indicator data in the table; Use the data routing module to screen indicators, allocate the total sales amount to the data acceleration module to request general indicator data, and allocate the online sales amount and offline sales amount to the data access module; Use the data access module to request data using the API interface and built-in JAR method according to the directional content of the generic query indicator; Aggregate the query data returned by the data request interface to the data fusion module, and perform data fusion of general query indicators and generic query indicators based on the regional fields mapped by the dimension; The integrated data is fed back to the front-end page for display.
2. The method according to claim 1, characterized in that Methods for creating common query indicators and generic query indicators include: Define general query indicators with normal scope and generic query indicators without actual business technical scope through the indicator definition module; The generic query indicator includes a content description of the indicator name and indicator unit.
3. The method according to claim 1, characterized in that The methods for defining the data sources corresponding to general query indicators and generic query indicators include: Internal data sources for targeting common query indicators and external data sources for targeting generic query indicators are defined through the data source definition module; The external data source includes one or more of a database, an API interface, a JAR package, a KV text, and an EXCEL document; The data source information of the database includes the service IP, port and database name. The data source information of the API interface includes the interface address, input parameter information and return parameter information. The data source information of the JAR package includes the JAR name, full path of the interface class and method name.
4. The method according to claim 1, characterized in that The methods for creating a table and partitioning the common query indicators and generic query indicators in the table include: Use the visualization platform to create a table and set the table content order to analysis fields, general query indicators, and generic query indicators.
5. The method according to claim 4, characterized in that The method of making a data request based on the indicator content in the table and obtaining the query data corresponding to the general query indicator and the generic query indicator from the data source by using a pre-configured calling method includes: Initiate data request based on generic query indicators in the table, and after indicator screening, use corresponding calling methods to access external data sources from one or more channels including database, API interface, JAR package, KV text, and EXCEL document to obtain query data for generic indicators; Initiate a data request based on the general query indicators in the table, and after indicator screening, use the corresponding calling method to obtain the query data of the general indicators from the internal data source.
6. The method according to claim 4, characterized in that The method of aggregating and integrating the query data corresponding to the general query indicators and the generic query indicators and feeding them back to the front-end for display includes: According to the analysis fields of dimension mapping, the query data of generic indicators and common indicators in the table are summarized and fused, and the fused summary data is fed back to the front-end page for visual display.
7. A report development device based on generic indicators as claimed in claim 1, characterized in that: include: An indicator creation unit, used to create common query indicators and generic query indicators; A data source definition unit, used to define data sources corresponding to common query indicators and generic query indicators respectively; A table creation unit is used to create a table and partition the common query index and the generic query index in the table; A calling configuration unit is used to direct the generic query indicator to configure the calling method of the generic query indicator; A data request unit, used to make data requests based on the indicator content in the table, and to obtain query data corresponding to the general query indicator and the generic query indicator from the data source using a pre-configured calling method; The data fusion unit is used to aggregate and fuse the query data corresponding to the general query indicators and the generic query indicators, and feed them back to the front-end for display.
8. The device according to claim 7, characterized in that The indicator creation unit is also used for: Define general query indicators with normal scope and generic query indicators without actual business technical scope through the indicator definition module; The generic query indicator includes a content description of the indicator name and indicator unit.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are executed.
