A method and device for custom report configuration and report resource display

Abstract

The application discloses a self-defined report configuration and report resource display method and device. The method comprises the following steps: based on a view label selected by a user, a view corresponding to the view label is acquired from a pre-configured view dictionary, a query statement in the view is executed to acquire view fields from a database, and the view fields are displayed to the user; based on a pre-configured multilingual dictionary, language configuration information is added to the selected view fields, and report configuration parameters are set for the selected view fields; report configuration information including the view fields selected by the user, corresponding language configuration information and report configuration parameters is generated, a version number is set for the view corresponding to the selected view label, and the report configuration information and the version number of the view are stored into a report configuration dictionary. The report style can be flexibly configured according to the actual demand of the user, the user demand is responded, and the diversified demand for report display under different users and business scenarios is met.

Description

Technical Field

[0001] This invention relates to the field of data information processing, and in particular to a method and apparatus for customizing report configuration and displaying report resources. Background Technology

[0002] With the development of the information age, data from various industries is stored through electronic reports. This not only allows for the systematic organization and storage of data but also saves resources and makes data access more convenient and simple. In the petrochemical industry, the oil and gas extraction and production process generates a large amount of complex oil and gas production data. Without effective organization of this data, companies cannot make accurate decisions based on dynamic production information. Therefore, it is necessary to systematically organize and process oil and gas production data. For personnel in different departments, customized reports based on user needs can improve data analysis efficiency, helping users better understand the data and make accurate decisions.

[0003] In existing report customization and display systems, users typically need to select fixed report styles and content when customizing reports. Users cannot customize the report display style according to their actual needs. Furthermore, the creation and display of each report in such systems requires writing a large amount of code on the front-end and back-end, resulting in long development cycles, complex operations, poor flexibility, and a large workload. Therefore, how to enable users to customize data report styles and display content that meet their specific needs in order to quickly obtain key data is a problem that current report customization systems need to solve. Summary of the Invention

[0004] Current report generation systems require users to customize data reports using fixed templates, preventing them from generating reports tailored to their specific needs. This hinders the rapid and flexible customization and display of reports. These shortcomings limit users' ability to customize report styles and content according to actual requirements, reducing system efficiency and resulting in a poor user experience.

[0005] In view of the above problems, the present invention is proposed to provide a custom report configuration method, report resource display method and apparatus that overcome the above problems or at least partially solve the above problems.

[0006] In a first aspect, embodiments of the present invention provide a method for configuring custom reports, including:

[0007] Based on the view tag selected by the user, the view corresponding to the view tag is obtained from the pre-configured view dictionary, the query statement in the view is executed to retrieve the view field from the database, and the view field is displayed to the user;

[0008] Add language configuration information to the selected view fields based on a pre-configured multilingual dictionary, and set report configuration parameters for the selected view fields;

[0009] Generate report configuration information that includes the view fields selected by the user, the corresponding language configuration information, and the report configuration parameters, and set the version number for the view corresponding to the selected view label, and store the report configuration information and the view version number in the report configuration dictionary.

[0010] In some optional embodiments, the above method further includes:

[0011] Based on the report configuration information, the report component is called from the report component library to generate a preview table with the selected view field as the report header, which is then displayed in the specified preview area.

[0012] In some optional embodiments, based on the view tag selected by the user, the view corresponding to the view tag is retrieved from a pre-configured view dictionary, the query statement in the view is executed to retrieve the view fields from the database, and the view fields are displayed to the user, including:

[0013] The SQL parsing general interface is called to receive the view label selected by the user, and the view corresponding to the view label is queried from the pre-configured view dictionary based on the view label;

[0014] Execute the SQL query statement in the view, retrieve all view field data from the database according to the preset query conditions, and pass the view field data to the SQL parsing general interface for parsing and return the parsing result. Display the view fields included in the parsing result through the human-computer interaction interface.

[0015] In some optional embodiments, configuring the view dictionary includes:

[0016] Obtain view configuration information input by the user. The view configuration information includes view key values ​​and corresponding view labels.

[0017] View configuration information and corresponding views are stored in a view dictionary. A view is pre-compiled executable code that includes a query statement. The query conditions in the query statement are determined based on the view key value.

[0018] In some optional embodiments, configuring a multilingual dictionary includes:

[0019] The view label that needs to be configured with language information and the language configuration information of the view field entered by the user are obtained. The language configuration information includes the multilingual key value of the view field and the corresponding multilingual characters.

[0020] The user-inputted language configuration information is associated with the view label containing the language to be configured and stored in a multilingual dictionary.

[0021] In some optional embodiments, language configuration information is added to selected view fields based on a pre-configured multilingual dictionary, including:

[0022] For the selected view field, retrieve the multilingual key-value pair entered by the user;

[0023] Retrieve multilingual characters corresponding to multilingual key values ​​from a pre-configured multilingual dictionary;

[0024] Select the user-selected language from the multilingual characters, and add the language characters of the user-specified language to the selected view field.

[0025] In some optional embodiments, report configuration parameters are set for selected view fields, including:

[0026] For the selected view field, obtain the report configuration parameters entered by the user. The report configuration parameters include report header configuration parameters, report content configuration parameters, and query condition configuration parameters.

[0027] The report header configuration parameters include the table attribute information of the table occupied by the view field in the report header, and the report content configuration parameters include the content attribute information of the view field in the report header;

[0028] The query condition configuration parameters include the content of the query conditions and the corresponding display style.

[0029] In some optional embodiments, after storing the report configuration information and the view version number in the report configuration dictionary, the method further includes:

[0030] If new report configuration information corresponding to the selected view label is obtained, update the corresponding report configuration information in the report configuration, and store the updated report configuration information in the report configuration dictionary.

[0031] In some optional embodiments, based on report configuration information, a report component is called from the report component library to generate a preview table with the selected view field as the report header, which is then displayed in a specified preview area, including:

[0032] Get the version number of the corresponding view based on the selected view label;

[0033] Retrieve the report configuration information corresponding to the view label and view version number from the report configuration dictionary;

[0034] The report's display style is parsed based on the report configuration information, and the corresponding components in the report component library are obtained by calling the report component interface;

[0035] The parsed report is rendered according to the corresponding components, generating a preview table with the selected view field as the report header, which is then displayed in the specified preview area.

[0036] In some optional embodiments, the table attribute information includes the header width, header unit, and whether the view field is set as a fixed column;

[0037] Content attribute information includes view field data sorting, view field merge display options, and report sorting sequence number;

[0038] The display styles of query conditions include: fuzzy input box, exact input box, drop-down selection box, date picker, month selection period, year picker, year-week picker, date range picker, month range picker, year range picker, year-week range picker, and one of the following: organizational tree query.

[0039] Secondly, embodiments of the present invention provide a method for displaying report resources, wherein the report is configured based on the aforementioned custom report configuration method, including:

[0040] Receive a report access request and obtain the access path from the access request;

[0041] Get the view tag and view version number in the access path, and get the corresponding report configuration information in the report configuration dictionary based on the view tag and view version number;

[0042] The report's display style is parsed based on the report configuration information, and the corresponding components in the report component library are obtained by calling the report component interface;

[0043] The parsed report is rendered according to the corresponding components, and the rendered report is displayed through the human-computer interaction interface.

[0044] In some optional embodiments, before receiving a report access request, the system further includes configuring a report resource menu, which includes resource names corresponding to multiple levels of resources.

[0045] In some optional embodiments, the report resource menu is configured, including:

[0046] For the lowest-level resource in the report resource menu, retrieve the input resource configuration parameters, associate them with the corresponding resource name, and store them. The resource configuration parameters include view label, resource access permissions, resource type, and resource access path.

[0047] Thirdly, embodiments of the present invention provide a custom report configuration device, including:

[0048] The view field retrieval module retrieves the view corresponding to the view tag selected by the user from a pre-configured view dictionary, executes the query statement in the view to retrieve the view field from the database, and displays the view field to the user.

[0049] The language configuration module is used to add language configuration information to selected view fields based on a pre-configured multilingual dictionary;

[0050] The report configuration module sets report configuration parameters for the selected view fields; generates report configuration information including the user-selected view fields, corresponding language configuration information, and report configuration parameters; sets the version number for the view corresponding to the selected view label; and stores the report configuration information and the view version number in the report configuration dictionary.

[0051] Fourthly, embodiments of the present invention provide a report resource display device, characterized in that it includes:

[0052] The data access module is used to receive report access requests, obtain the access path from the access request, obtain the view name and version number in the access path, and query the report configuration parameters in the report configuration dictionary based on the view name and version number to obtain the corresponding report configuration parameters.

[0053] The report display module is used to call the corresponding data interfaces and component libraries based on the report configuration parameters to render the display page and then display the rendered page.

[0054] This invention also provides a computer storage medium storing computer-executable instructions, which, when executed by a processor, implement the aforementioned custom report configuration method and / or the aforementioned report resource display method.

[0055] This invention also provides a terminal device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the above-described custom report configuration method and / or the above-described report resource display method.

[0056] The beneficial effects of the above-described technical solutions provided in the embodiments of the present invention include at least the following:

[0057] The custom report configuration method provided in this embodiment of the invention is based on the view tag selected by the user. It obtains the view corresponding to the view tag from the pre-configured view dictionary, executes the query statement in the view to obtain the view fields from the database, and displays the view fields to the user. Not all fields in a view are necessarily needed by the user. By presenting all fields of the view to the user, the user can select the view fields they need to customize the report header items to adapt to different business scenarios and data requirements. This approach is more flexible and can improve the efficiency and satisfaction of responding to user needs. Based on a pre-configured multilingual dictionary, language configuration information is added to the selected view fields. This allows users to choose the appropriate language to edit and display reports, meeting international reporting requirements. Report configuration parameters are also set for the selected view fields. Users can customize report configuration parameters for the selected view fields according to business needs to obtain a suitable report display style. After obtaining the user-defined report configuration parameters, corresponding report configuration parameters are set for the selected fields, generating report configuration information that includes the user-selected view fields, corresponding language configuration information, and report configuration parameters. A version number is also set for the view corresponding to the selected view label. This report configuration information and the view version number are stored in the report configuration dictionary for later retrieval during report display. The method of this invention is not limited to fixed report display style templates. By configuring the view dictionary and multilingual dictionary, users can configure the reports they need and store the configured reports for later use. This enables users to customize report configuration information according to their actual needs, so that reports can be displayed in different styles, improving the flexibility of report customization, improving data analysis efficiency, and reducing maintenance costs. Moreover, this method can be implemented without writing code, and is also applicable to users without programming skills, making it universally applicable.

[0058] The report resource display method provided in this embodiment of the invention receives a report access request and obtains the access path from the access request; obtains the view tag and view version number in the access path, and obtains the corresponding report configuration information in the report configuration dictionary based on the view tag and view version number; the report configuration is implemented through the report custom configuration method. When a user makes a report access request, the report configuration information in the report configuration dictionary is obtained based on the access path, the report display style is parsed based on the report configuration information, and the corresponding component in the report component library is obtained by calling the report component interface; the report component interface is a public report processing interface. Directly calling the report component interface can simplify the amount of code and quickly realize the rendering of the report style, reducing the workload of developers, compared to writing lengthy report style rendering code. The parsed report display style is rendered according to the corresponding component, and the rendered report display style is displayed through the human-computer interaction interface.

[0059] Other features and advantages of the invention will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings.

[0060] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0061] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings:

[0062] Figure 1 This is a flowchart of the custom report configuration method in Embodiment 1 of the present invention;

[0063] Figure 2 This is the multilingual configuration user interface in Embodiment 1 of the present invention;

[0064] Figure 3 This is the query condition configuration interface in Embodiment 1 of the present invention;

[0065] Figure 4 This is the report content configuration interface in Embodiment 1 of the present invention;

[0066] Figure 5 This is the user interface for report preview in Embodiment 1 of the present invention;

[0067] Figure 6 This is a schematic diagram of the custom report configuration method in Embodiment 1 of the present invention;

[0068] Figure 7 This is a schematic diagram of the custom report configuration device in Embodiment 1 of the present invention;

[0069] Figure 8 This is a flowchart of the report resource display method in Embodiment 2 of the present invention;

[0070] Figure 9 This is the report display interface in Embodiment 2 of the present invention;

[0071] Figure 10 This is the page for configuring the report resource menu in Embodiment 2 of the present invention;

[0072] Figure 11 This is a schematic diagram of the report resource display device in Embodiment 2 of the present invention. Detailed Implementation

[0073] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0074] In existing report editing and display systems, users typically need to select fixed report styles and content when customizing reports. This fixed style makes it impossible to adjust and change the report's display style according to the user's actual needs. This deficiency limits the user's ability to customize report styles and content according to actual needs, reducing system efficiency and user satisfaction. Therefore, a flexible report customization method is needed to enable users to customize reports as needed and improve work efficiency.

[0075] To address the problem of fixed report styles in existing technologies, which prevent users from customizing reports according to their needs, this invention provides a method and apparatus for customizing report configuration and displaying report resources.

[0076] This invention provides a method for configuring custom reports, the process of which is as follows: Figure 1 As shown, it includes the following steps:

[0077] Step S101: Based on the view label selected by the user, retrieve the view corresponding to the view label from the pre-configured view dictionary, execute the query statement in the view to retrieve the view fields from the database, and display the view fields to the user;

[0078] Step S102: Add language configuration information to the selected view fields based on the pre-configured multilingual dictionary, and set report configuration parameters for the selected view fields;

[0079] Step S103: Generate report configuration information including the view fields selected by the user, the corresponding language configuration information and report configuration parameters, and set the version number for the view corresponding to the selected view label, and store the report configuration information and the view version number in the report configuration dictionary.

[0080] In steps S101-S103 above, report configuration information is set for the selected view fields in the view corresponding to the view label selected by the user, based on the view label selected by the user. This report configuration information is stored in the report configuration dictionary so that the user-selected view fields can be displayed later according to the set report configuration information. Here, a view is a virtual data table built based on one or more data tables in the database to meet the user's report usage needs. By calling the view, the fields of the data table can be queried; these fields can be considered as the view fields. The view contains a collection of SQL query statements. At the code level, when a query statement needs to be executed multiple times, writing a SELECT query statement each time would complicate the code and increase runtime. Using a view simplifies the code; the query function can be implemented by directly calling the view, greatly reducing the workload of developers. The view dictionary, multilingual dictionary, and report configuration dictionary can be linked for queries. Based on the relationships between the three, when configuring a report, the corresponding view can be retrieved from the view dictionary based on the view tag selected by the user. The query statement in the view is then executed to retrieve all view fields so that the user can select the required view field. When configuring the language of the selected view field, the language configuration information of the view field is obtained from the multilingual dictionary corresponding to the view tag, allowing the user to add language configuration information to the selected view field.

[0081] Optionally, in step S101 above, based on the view label selected by the user, the view corresponding to the view label is obtained from the pre-configured view dictionary, the query statement in the view is executed to retrieve the view fields from the database, and the view fields are displayed to the user, including:

[0082] The SQL parsing general interface is called to receive the view label selected by the user, and the view corresponding to the view label is queried from the pre-configured view dictionary based on the view label;

[0083] Execute the SQL query statement in the view, retrieve all view field data from the database according to the preset query conditions, and pass the view field data to the SQL parsing general interface for parsing and return the parsing result. Display the view fields included in the parsing result through the human-computer interaction interface.

[0084] View tags serve as indexes for views, enabling the retrieval of corresponding views from the configured view dictionary based on these tags. Upon receiving a view tag, the SQL parsing interface searches for the corresponding view in the view dictionary, invokes the view, executes the query statement within it, examines the field information in the data table, and passes the retrieved field information as view field data to the SQL parsing interface. This view field data is then parsed, its format converted, and the parsing result returned. Finally, the view fields included in the parsing result are displayed through a user interface. Users will see all views at this point, but not all view fields may be what they need. Users can select view fields that meet their requirements and configure these selected fields. Compared to traditional fixed-style report customization methods, this method allows users to customize according to their actual needs, offering greater flexibility and higher user satisfaction.

[0085] Optionally, in step S101 above, configuring the view dictionary includes:

[0086] Obtain the view configuration information input by the user. The view configuration information includes view key values ​​and corresponding view labels. Store the view configuration information and the corresponding view in the view dictionary. The view is pre-compiled executable code that includes query statements. The query conditions in the query statements are determined based on the view key values.

[0087] The view dictionary is a data table that manages views. It contains multiple views and allows for view management, such as adding, deleting, and modifying views. View keys and corresponding view tags are added to views for subsequent indexing. After operations are performed on a view in the view dictionary, the resulting information is stored in the database's view dictionary. The view dictionary table must contain at least the following fields: view dictionary ID, view tag, view key, dictionary code, dictionary sorting, dictionary type, creation notes, creator, creation time, updater, and update time. View tags are added through the view dictionary interface. The specific steps are: retrieve the view key entered by the user and its corresponding view tag; associate and match the view tag and view key and store them in the view dictionary. This establishes a one-to-one relationship between view tags and view keys. Later, during report configuration, the view tag can be used to quickly retrieve the corresponding view and view fields.

[0088] Optionally, in step S102 above, configuring the multilingual dictionary includes:

[0089] The view label that needs to be configured with language information and the language configuration information of the view field entered by the user are obtained. The language configuration information includes the multilingual key value of the view field and the corresponding multilingual characters.

[0090] The user-inputted language configuration information is associated with the view label containing the language to be configured and stored in a multilingual dictionary.

[0091] A multilingual dictionary, as an auxiliary item in report configuration, manages the language configuration information used by the view fields required by the report, thus meeting the internationalization and diversification needs of the report. The multilingual dictionary data table must include at least: a multilingual dictionary ID, a view dictionary ID, a view label, multilingual key values, and corresponding multilingual characters, creator, creation time, updater, and update time. The multilingual characters can be Chinese, English, French, Russian, German, etc. Each field must include at least Chinese and English representations; representations of other languages ​​can be set according to user needs. Figure 2 This is the user interface for configuring multilingual languages. When configuring a multilingual dictionary, multilingual key-value pairs need to be added to the view fields corresponding to the view labels for the language information to be configured, along with the Chinese and English representations of the view fields corresponding to the multilingual key-value pairs. Representations for other languages ​​can be added as needed by the user, for example... Figure 2 In the view field labeled "Basic_Well Information Maintenance" to be configured with language information, after the user clicks "Add", a pop-up window will appear showing the multilingual key-value pairs and multilingual expressions. The user fills in the language configuration information for one field according to the information fields in the pop-up window, and then clicks "Save" to store the language configuration information in the multilingual dictionary. The same method is used to configure the multilingual information for all fields in the view corresponding to the view label, and the multilingual configuration information is stored in the multilingual dictionary.

[0092] Optionally, in step S103 above, language configuration information is added to the selected view field based on a pre-configured multilingual dictionary, including:

[0093] For the selected view field, retrieve the multilingual key value entered by the user; retrieve the multilingual characters corresponding to the multilingual key value from the pre-configured multilingual dictionary; select the language type selected by the user from the multilingual characters, and add the language characters of the user-specified language type to the selected view field.

[0094] Based on a pre-configured multilingual dictionary, when a user configures the multilingual language of a view field selected in the current view tab, they need to add multilingual key-value pairs for the selected view field. The system matches the user-inputted multilingual key-value pairs with the corresponding characters in multiple languages, mapping the view field to its language representation (e.g., Chinese, English, etc.) to meet the requirements of internationalized report display.

[0095] Optionally, in step S102 above, report configuration parameters are set for the selected view fields, including:

[0096] For the selected view field, obtain the report configuration parameters input by the user. The report configuration parameters include report header configuration parameters, report content configuration parameters, and query condition configuration parameters. The report header configuration parameters include the table attribute information of the table occupied by the view field in the report header. The report content configuration parameters include the content attribute information of the view field in the report header. The query condition configuration parameters include the content of the query conditions and the corresponding display style.

[0097] Optionally, table attribute information includes header width, header unit, and whether to set view fields as fixed columns; content attribute information includes view field data sorting, view field merge display options, and report sorting sequence number; the display style of query conditions includes: fuzzy input box, precise input box, drop-down selection box, date picker, month selection period, year picker, year-week picker, date range picker, month range picker, year range picker, year-week range picker, and one of the following: organizational tree query.

[0098] The system retrieves the header width and unit from the header configuration parameters and sets the corresponding width and unit for the selected view field. It also determines whether to set the selected field as a fixed column or not, depending on whether the view field is set as a fixed column. Furthermore, it retrieves the data sorting information for the view field from the table content and sets the corresponding data sorting for that view field. For example, if the view field is ranked 3rd, it means that the data field is the third item in the report header. Finally, it retrieves the data items from the view field merging display option, i.e., the view field itself, and merges and displays the selected data items. In some cases, several reports may be displayed on the same screen. In such cases, users can set the report sorting sequence number, which indicates which report on the display page the configured report will be displayed in.

[0099] Setting query conditions facilitates quick searches on the report display page, allowing users to quickly query according to the conditions set for view fields. However, not all view fields require query conditions. When configuring query conditions for view fields, you configure the content of the query conditions and the corresponding display style. During preview, view fields with configured query conditions are displayed according to the configured display style. When the user enters the content of the query conditions, the query is performed according to the content of the query conditions. For example, if the user selects a year, the data for that year will be searched; if a time range is entered, the data will be searched according to the time range.

[0100] After completing steps S101-S102, report configuration information is generated, including the view fields selected by the user, the corresponding language configuration information, and report configuration parameters. Based on the version number entered by the user, a version number is set for the view corresponding to the selected view label. The version number and report configuration information are stored in the report configuration dictionary for later display and retrieval of the report. See the page display of report configuration for details. Figure 3 and Figure 4 As shown, Figure 3 Configure the query criteria interface. Figure 4 Configure the interface for report content. Figure 3 and Figure 4 The report header and fields are already configured for multilingual support. View fields without a "+" sign are selected and used as an item in the report header. Users can configure query conditions for a specific field by clicking... Figure 3 The small icon at ① will pop up a query condition configuration window, allowing you to set query condition parameters, obtain the query condition configuration parameters corresponding to the view field selected by the user, and configure the query conditions for the corresponding view field. Figure 4 In the report content configuration interface, after the user configures the query conditions for the view fields, they click... Figure 4 Upon receiving the submission command, the "Submit" button on the page redirects to a pop-up window displaying the report content configuration parameters, allowing the user to configure these parameters. Figure 4 In the table, the table name key value represents the view key value corresponding to the selected view label. The view key value belongs to a data field in the view dictionary data table. Users can sort the table, set the sort order, and sort the selected view fields according to their needs. They can also customize the style of the table header items, select the view fields to be merged in the merge field item, and display the merged view fields. After configuring the report content parameters, add the version number, and click "Save". At this time, the report configuration information will be saved in the report configuration dictionary for use when displaying the report.

[0101] The custom report configuration method provided in this invention allows users to configure reports according to their needs. Unnecessary report items can be unselected. During report configuration, users can customize report configuration information to achieve diverse report displays. Compared to traditional fixed-style configuration methods, this method improves the flexibility of report display, allowing users to adjust the report display style, content, and query conditions at any time according to actual needs to adapt to different business scenarios and data requirements. This flexibility greatly improves the practicality and applicability of reports. It also optimizes report display effects, supporting multiple display methods for various reports, such as displaying data sequence columns, merging fields, and data sorting, making report displays more intuitive, clear, and easy to understand.

[0102] Optionally, in step S103 above, after storing the report configuration information and the view version number in the report configuration dictionary, the method further includes:

[0103] If new report configuration information corresponding to the selected view label is obtained, update the corresponding report configuration information in the report configuration, and store the updated report configuration information in the report configuration dictionary.

[0104] If a user needs to adjust or change the report configuration information, they can reset the report configuration information. When the new report configuration information corresponding to the view label is received, the report configuration information stored in the report configuration dictionary will be updated. After receiving the "save" command, the updated report configuration information will be stored in the report configuration dictionary.

[0105] Optionally, the above-mentioned custom report configuration methods also include:

[0106] Based on the report configuration information, the report component is called from the report component library to generate a preview table with the selected view field as the report header, which is then displayed in the specified preview area. Each view field is included as an item in the report header.

[0107] Optionally, based on the report configuration information, a report component is called from the report component library to generate a preview table with the selected view fields as report headers, which is then displayed in a specified preview area, including:

[0108] Get the version number of the corresponding view based on the selected view label;

[0109] Retrieve the report configuration information corresponding to the view label and view version number from the report configuration dictionary;

[0110] Based on the report configuration information, the report display style is parsed, and the corresponding components in the report component library are obtained by calling the report component interface;

[0111] The parsed report is rendered according to the corresponding components, generating a preview table with the selected view field as the report header, which is then displayed in the specified preview area.

[0112] The report component interface can be used as a public report processing interface to access the report component library. Once the report configuration information is stored in the report configuration dictionary, the corresponding report configuration parameters are retrieved from the dictionary based on the view tag and version number. The report processing interface is then called, and the corresponding report header component, report content component, and query condition component are retrieved from the report component library. Based on the report configuration settings, the report display style is rendered, generating a preview table with the selected view field as the report header, which is then previewed in the preview area. Figure 5This is the user interface for report preview. Figures 3-4 The user has already configured the report and stored the report configuration information in the report configuration dictionary. Based on the report configuration information in the report configuration dictionary, the corresponding component in the report component library is called to generate a report header consisting of the view fields selected from the view named "Downhole Operations_Well Repair Record". When the user needs to change the report configuration parameters, they only need to store the changed report configuration parameters in the report configuration dictionary. Based on the report configuration parameters, the corresponding report display style is parsed, the corresponding component in the report component library is called to render the report style, and the rendered report style is displayed in the preview area. The report style is determined by the report configuration information. If the report configuration information changes, the report display style will also change randomly. Traditional methods rely heavily on the changed information, requiring developers to repeatedly write code to re-render the report style based on the report configuration parameters. This results in a large amount of code, poor readability, and consumes a lot of developer time, extending the development cycle. In contrast, this method uses a report component interface to address user-defined report requirements. Whether the report configuration information is pre-configured or updated, users only need to save the report configuration information and call the report component interface to re-render the report style. This simplifies the code, enhances readability, and allows for quick and flexible implementation of new user requirements.

[0113] The schematic diagram of the custom report configuration method provided in this embodiment of the invention can be found in [reference needed]. Figure 6As shown, the view dictionary, multilingual dictionary, and report configuration dictionary serve as the data source for report configuration and need to be pre-established in the database. The view is created in the database, but the view itself does not store data; it is merely a collection of SELECT query statements. The view accesses the data tables existing in the database based on the SELECT query statements. When modifying the statements in the SELECT statement collection in the view, the operation also needs to be performed in the database. When users customize reports, the report configuration function page developed by the developers manages the view dictionary, multilingual dictionary, and report configuration dictionary. View dictionary management includes setting view tags for view key values ​​for later retrieval and indexing, modifying and deleting view tags, and finally interacting with the database to save the data manipulated in the view dictionary. Language configuration dictionary management includes adding, modifying, and deleting language configuration information for view fields corresponding to view tags, interacting with the database, and storing the language configuration information in the multilingual dictionary for later retrieval. Report configuration management includes adding, modifying, and deleting report configuration information, interacting with the database, storing the report configuration information in the report configuration dictionary in the database, and after storing the report configuration information, calling the report component interface. The report component interface retrieves the corresponding report configuration information from the data source, processes the report configuration information, parses the corresponding report display style, renders the parsed display style, and previews the report style in the preview area.

[0114] Based on the same inventive concept, embodiments of the present invention provide a custom report configuration device, which can be installed in devices with calculation and processing functions. See the schematic diagram below. Figure 7 As shown, it includes:

[0115] The view field acquisition module 11 is used to retrieve the view corresponding to the view tag selected by the user from a pre-configured view dictionary, execute the query statement in the view to retrieve the view field from the database, and display the view field to the user.

[0116] Language configuration module 12 is used to add language configuration information to selected view fields based on a pre-configured multilingual dictionary;

[0117] The report configuration module 13 sets report configuration parameters for the selected view fields; generates report configuration information including the view fields selected by the user, the corresponding language configuration information and report configuration parameters, and sets the version number for the view corresponding to the selected view label, and stores the report configuration information and the view version number in the report configuration dictionary.

[0118] The above-described custom report configuration device implements a custom report configuration method. The descriptions of each functional module have been described in detail in the embodiments of the method, and will not be repeated here.

[0119] Example 2

[0120] Embodiment 2 of the present invention provides a method for displaying report resources. This report is configured based on a custom report configuration method provided in Embodiment 1, the process of which is described in [link to embodiment 1]. Figure 8 As shown, it includes the following steps:

[0121] S201: Receive a report access request and obtain the access path from the access request;

[0122] S202: Obtain the view label and view version number in the access path, and obtain the corresponding report configuration information in the report configuration dictionary based on the view label and view version number;

[0123] S203: Parse the report display style based on the report configuration information, and call the report component interface to obtain the corresponding components in the report component library;

[0124] Step S204: Render the style of the parsed report according to the corresponding components, and display the rendered report through the human-computer interaction interface.

[0125] Optionally, in step S201 above, the report resource menu is configured, and the menu includes the resource names corresponding to multi-level resources.

[0126] Optionally, the report resource menu can be configured, including:

[0127] For the lowest-level resource in the report resource menu, retrieve the input resource configuration parameters, associate them with the corresponding resource name, and store them. The resource configuration parameters include view label, resource access permissions, resource type, and resource access path.

[0128] In step S201 above, the user accesses the report resources with the access permissions according to the report access permissions. When the access request sent by the user is received, the access path in the access request is received according to the user's access request, the view tag and view version number in the access path are parsed, and the report configuration information in the corresponding report configuration dictionary is searched based on the view tag and view version number. After obtaining the report configuration information, the report component interface is called to render the report display style corresponding to the report configuration information. After the rendering is completed, the report is displayed to the user through the human-computer interaction interface according to the display style.

[0129] Figure 9 For the report display interface, Figure 9Accessing the daily production report of the first-level sub-resources, the daily comprehensive information report of the oil wells in the second-level sub-resources will display to the user the daily comprehensive production data report of the oil wells in the daily comprehensive information report of the oil wells.

[0130] Figure 10 This is the page where users configure the report resource menu. Figure 10 The data collection and production information displayed in the figure belongs to the reporting resource. The production information resource includes four primary sub-resources: Comprehensive Information, Comprehensive Information Con…, Comprehensive Information PSA, and Daily Production Report. The primary sub-resource Daily Production Report includes four secondary sub-resources: Daily Comprehensive Information of Oil Wells from Two Different Wells, Daily Comprehensive Information of Oil Wells with PSA, and Daily Standard Condition Report to the Chadian Government. Other sub-resources are not included under the secondary sub-resources in the figure. Figure 10 The second-level sub-resources in the report resource menu are the lowest-level resources. Users can set resource configuration parameters for the lowest-level resources in the report resource menu. The system obtains the resource configuration parameters entered by the user, associates them with the corresponding resource name, and then stores them. Figure 10 The resource configuration parameters of the four lowest-level resources are associated with the storage of first-level sub-resources. The resource name of the first-level sub-resource is "Production Daily Report". The resource configuration parameters include view label, resource access permission, resource type, and resource access path. The access view label can be used as the title of the report in the report display interface. Access permissions are set for the resource. Public report resources can be accessed by multiple users, while private report resources are only accessible to users with access permissions, thereby improving the security of report access. The resource access path is bound to the view label and view version number. The view label and view version number can determine the uniqueness of the report configuration parameters, so that data can be quickly retrieved from the report configuration dictionary when a user access request is received.

[0131] Based on the same inventive concept, embodiments of the present invention also provide a report resource display device, which can be installed in a device with computing processing capabilities, and the structure of the device is as follows. Figure 11 As shown, it includes:

[0132] Data access module 21 is used to receive report access requests, obtain access paths from the access requests, obtain view names and version numbers in the access paths, query report configuration parameters in the report configuration dictionary based on the view names and version numbers, and obtain the corresponding report configuration parameters.

[0133] The report display module 22 is used to call the corresponding data interface and component library based on the report configuration parameters to render the display page and display the rendered page.

[0134] The specific functions of each module in the aforementioned report resource display device have been described in detail in the relevant report resource display methods, and will not be repeated here.

[0135] This invention also provides a computer storage medium storing computer-executable instructions, which, when executed by a processor, implement the aforementioned custom report configuration method and / or report resource display method.

[0136] This invention also provides a terminal device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the above-mentioned custom report configuration method and / or report resource display method.

[0137] Unless otherwise specifically stated, terms such as processing, calculation, operation, determination, display, etc., may refer to the actions and / or processes of one or more processing or computing systems or similar devices that represent the manipulation and conversion of data representing physical (e.g., electronic) quantities within the registers or memory of the processing system into other data similarly representing physical quantities within the memory, registers, or other such information storage, transmission, or display devices of the processing system. Information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0138] It should be understood that the specific order or hierarchy of steps in the disclosed process is an example of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process may be rearranged without departing from the scope of this disclosure. The appended method claims provide elements of various steps in an exemplary order and are not intended to limit the scope to the specific order or hierarchy described.

[0139] In the detailed description above, various features are combined together in a single embodiment to simplify this disclosure. This approach to disclosure should not be construed as reflecting an intention that embodiments of the claimed subject matter require more features than are explicitly stated in each claim. Rather, as reflected in the appended claims, the invention is presented with fewer features than all of the features in a single disclosed embodiment. Therefore, the appended claims are hereby explicitly incorporated into the detailed description, with each claim representing a separate preferred embodiment of the invention.

[0140] Those skilled in the art will also understand that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments herein can be implemented as electronic hardware, computer software, or a combination thereof. To clearly illustrate the interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps described above are generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in alternative ways for each specific application; however, such implementation decisions should not be construed as departing from the scope of this disclosure.

[0141] The steps of the methods or algorithms described in conjunction with the embodiments herein can be directly embodied in hardware, software modules executed by a processor, or a combination thereof. The software modules can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is connected to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user terminal. Alternatively, the processor and storage medium can exist as discrete components in the user terminal.

[0142] For software implementation, the techniques described in this application can be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described in this application. This software code can be stored in memory units and executed by a processor. The memory units can be implemented within the processor or outside the processor; in the latter case, they are communicatively coupled to the processor via various means, as is well known in the art.

[0143] The foregoing description includes examples of one or more embodiments. It is certainly impossible to describe all possible combinations of components or methods in order to describe the above embodiments, but those skilled in the art will recognize that further combinations and arrangements of the various embodiments are possible. Therefore, the embodiments described herein are intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims. Furthermore, the term "comprising" as used in the specification or claims is interpreted in a manner similar to the term "including," as interpreted when used as a conjunction in the claims. Additionally, the use of any term "or" in the specification of the claims is intended to mean "non-exclusive or."

Claims

1. A method for configuring custom reports, characterized in that, include: Based on the view tag selected by the user, the view corresponding to the view tag is obtained from the pre-configured view dictionary, the query statement in the view is executed to retrieve the view field from the database, and the view field is displayed to the user; Add language configuration information to the selected view fields based on a pre-configured multilingual dictionary, and set report configuration parameters for the selected view fields; Generate report configuration information that includes the view fields selected by the user, the corresponding language configuration information, and the report configuration parameters, and set the version number for the view corresponding to the selected view label, and store the report configuration information and the view version number in the report configuration dictionary.

2. The method as described in claim 1, characterized in that, Also includes: Based on the report configuration information, the report component is called from the report component library to generate a preview table with the selected view field as the report header, which is then displayed in the specified preview area.

3. The method as described in claim 1, characterized in that, The process of retrieving the view corresponding to the user-selected view tag from a pre-configured view dictionary, executing the query statement in the view to retrieve view fields from the database, and displaying the view fields to the user includes: The SQL parsing general interface is called to receive the view label selected by the user, and the view corresponding to the view label is queried from the pre-configured view dictionary based on the view label; Execute the SQL query statement in the view, retrieve all view field data from the database according to the preset query conditions, and pass the view field data to the SQL parsing general interface for parsing and return the parsing result. Display the view fields included in the parsing result through the human-computer interaction interface.

4. The method as described in claim 1, characterized in that, Configure the view dictionary, including: Obtain view configuration information input by the user, the view configuration information including view key values ​​and corresponding view labels; The view configuration information and the corresponding view are stored in the view dictionary. The view is pre-compiled executable code that includes a query statement. The query conditions in the query statement are determined based on the view key value.

5. The method as described in claim 1, characterized in that, Configure a multilingual dictionary, including: Obtain the view label whose language information is to be configured and the language configuration information of the view field input by the user. The language configuration information includes the multilingual key value of the view field and the corresponding multilingual characters. The user-inputted language configuration information is associated with the view label containing the language to be configured and stored in a multilingual dictionary.

6. The method as described in claim 1, characterized in that, The process of adding language configuration information to selected view fields based on a pre-configured multilingual dictionary includes: For the selected view field, retrieve the multilingual key-value pair entered by the user; Obtain the multilingual characters corresponding to the multilingual key values ​​from the pre-configured multilingual dictionary; Select the user-selected language from the multilingual characters, and add the language characters of the user-specified language to the selected view field.

7. The method as described in claim 1, characterized in that, Set report configuration parameters for the selected view fields, including: For the selected view field, obtain the report configuration parameters input by the user. The report configuration parameters include report header configuration parameters, report content configuration parameters, and query condition configuration parameters. The report header configuration parameters include the table attribute information of the table occupied by the view field in the report header, and the report content configuration parameters include the content attribute information of the view field in the report header; The query condition configuration parameters include the content of the query conditions and the corresponding display style.

8. The method as described in claim 1, characterized in that, After storing the report configuration information and view version number in the report configuration dictionary, it also includes: If new report configuration information corresponding to the selected view label is obtained, update the corresponding report configuration information in the report configuration, and store the updated report configuration information in the report configuration dictionary.

9. The method as described in claim 2, characterized in that, The process of calling report components from the report component library based on report configuration information to generate a preview table with the selected view fields as report headers, and displaying it in a specified preview area, includes: Get the version number of the corresponding view based on the selected view label; Retrieve the report configuration information corresponding to the view label and view version number from the report configuration dictionary; Based on the report configuration information, the report display style is parsed, and the corresponding components in the report component library are obtained by calling the report component interface; The parsed report is rendered according to the corresponding components, generating a preview table with the selected view field as the report header, which is then displayed in the specified preview area.

10. The method as described in claim 7, characterized in that, The table attribute information includes the header width, header unit, and whether the view field is set as a fixed column; The content attribute information includes view field data sorting, view field merge display options, and report sorting sequence number; The display styles of the query conditions include: fuzzy input box, precise input box, drop-down selection box, date selector, month selection period, year selector, year-week selector, date range selector, month range selector, year range selector, year-week range selector, and one of the following: organizational tree query.

11. A method for displaying report resources, characterized in that, The report is configured based on a custom report configuration method according to any one of claims 1-10, including: Receive a report access request and obtain the access path from the access request; Obtain the view label and view version number in the access path, and obtain the corresponding report configuration information in the report configuration dictionary based on the view label and view version number; Based on the report configuration information, the report display style is parsed, and the corresponding components in the report component library are obtained by calling the report component interface; The parsed report is rendered according to the corresponding components, and the rendered report is displayed through the human-computer interaction interface.

12. The method as described in claim 11, characterized in that, Before receiving a report access request, the system also includes configuring the report resource menu, which includes resource names corresponding to multiple levels of resources.

13. The method as described in claim 12, characterized in that, The configuration of the report resource menu includes: For the lowest-level resource in the report resource menu, the input resource configuration parameters are obtained and stored after being associated with the corresponding resource name; the resource configuration parameters include view label, resource access permission, resource type, and resource access path.

14. A custom report configuration device, characterized in that, include: The view field retrieval module retrieves the view corresponding to the view tag selected by the user from a pre-configured view dictionary, executes the query statement in the view to retrieve the view field from the database, and displays the view field to the user. The language configuration module is used to add language configuration information to selected view fields based on a pre-configured multilingual dictionary; The report configuration module sets report configuration parameters for the selected view fields; generates report configuration information including the user-selected view fields, corresponding language configuration information, and report configuration parameters; sets the version number for the view corresponding to the selected view label; and stores the report configuration information and the view version number in the report configuration dictionary.

15. A report resource display device, characterized in that, include: The data access module is used to receive report access requests and obtain the access path from the access requests; Obtain the view name and version number in the access path, and query the report configuration parameters in the report configuration dictionary based on the view name and version number to obtain the corresponding report configuration parameters; The report display module is used to call the corresponding data interfaces and component libraries based on the report configuration parameters to render the display page and then display the rendered page.

16. A computer storage medium, characterized in that, The computer storage medium stores computer-executable instructions, which, when executed by a processor, implement the custom report configuration method according to any one of claims 1-10 and / or the report resource display method according to claims 11-13.

17. A terminal device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the custom report configuration method according to any one of claims 1-10 and / or the report resource display method according to claims 11-13.

Images