Method, device, equipment, storage medium and program product for generating operation report

Abstract

Embodiments of the present application provide a kind of operation report generation method, device, equipment, storage medium and program product, involve big data field.The method comprises: in response to the configuration operation initiated by user in visual operation interface, the index configuration information corresponding to configuration operation and operation report template are acquired;According to index configuration information, index data is acquired, and at least one target service interface is determined according to index data and operation report template;At least one target service interface is called, to generate operation report based on index data and operation report template.The method proposed in the present application can improve the timeliness, analysis pertinence and flexible adaptation capability of operation report generation in high-frequency, multi-dimensional business scenarios, reduce manual analysis and template adjustment cost.

Description

Technical Field

[0001] This application relates to the field of big data, and in particular to a method, apparatus, device, storage medium, and program product for generating operational reports. Background Technology

[0002] In financial product operation analysis, existing methods typically employ Business Intelligence (BI) reporting tools, rule-driven automated reporting systems, or basic text generation technologies to perform statistical analysis on business metrics and output operation reports.

[0003] However, such solutions often rely on periodic data processing, fixed template configurations, and manual analysis, resulting in delayed metric updates and difficulty in supporting high-frequency, multi-dimensional business scenarios. Summary of the Invention

[0004] This application provides a method, apparatus, device, storage medium, and program product for generating operation reports, which unifies and dynamically coordinates the operation report generation process, thereby improving the generation capability and application effect of operation reports in high-frequency, multi-dimensional business analysis scenarios.

[0005] In a first aspect, embodiments of this application provide a method for generating an operation report, including:

[0006] In response to a configuration operation initiated by a user through a visual operation interface, obtain the corresponding indicator configuration information and operation report template;

[0007] Obtain indicator data based on the indicator configuration information, and determine at least one target service interface based on the indicator data and the operation report template;

[0008] Invoke the at least one target service interface to generate an operation report based on the indicator data and the operation report template.

[0009] In some implementations, the indicator configuration information includes a data source and data processing logic; obtaining indicator data based on the indicator configuration information includes:

[0010] Obtain raw business data from the data source;

[0011] The original business data is processed according to the data processing logic to obtain the indicator data.

[0012] In some implementations, determining at least one target service interface based on the indicator data and the operation report template includes:

[0013] Based on the aforementioned operation report template, determine the components of the operation report;

[0014] Based on each component, the corresponding target indicator data is determined from the indicator data, and the corresponding target service is determined based on each component;

[0015] At least one target service interface is determined based on the target indicator data and the target service.

[0016] In some implementations, determining at least one target service interface based on the target metric data and the target service includes:

[0017] Based on the target indicator data and the pre-defined correspondence between the indicator data and the service interface, the first target service interface is determined;

[0018] Based on the correspondence between the target service and the preset services and service interfaces, determine the second target service interface;

[0019] The first target service interface and the second target service interface are determined as the at least one target service interface.

[0020] In some implementations, the step of invoking the at least one target service interface to generate an operation report based on the metric data and the operation report template includes:

[0021] The at least one target service interface is invoked to process the indicator data based on the operation report template to obtain the report content;

[0022] An operations report is generated based on the report content and the operations report template.

[0023] In some implementations, after generating the operations report, the method further includes:

[0024] In response to a user's modification request initiated through the visual interface, the operation report is modified accordingly.

[0025] Secondly, embodiments of this application provide an apparatus for generating an operation report, comprising:

[0026] The acquisition module is used to respond to the configuration operation initiated by the user through the visual operation interface, and to acquire the indicator configuration information and operation report template corresponding to the configuration operation.

[0027] The determination module is used to obtain indicator data based on the indicator configuration information, and determine at least one target service interface based on the indicator data and the operation report template.

[0028] The generation module is used to call the at least one target service interface to generate an operation report based on the indicator data and the operation report template.

[0029] In some embodiments, the apparatus further includes: a processing module, configured to:

[0030] Obtain raw business data from the data source;

[0031] The original business data is processed according to the data processing logic to obtain the indicator data.

[0032] In some implementations, the determining module is used to:

[0033] Based on the aforementioned operation report template, determine the components of the operation report;

[0034] Based on each component, the corresponding target indicator data is determined from the indicator data, and the corresponding target service is determined based on each component;

[0035] At least one target service interface is determined based on the target indicator data and the target service.

[0036] In some implementations, the determining module is used to:

[0037] Based on the target indicator data and the pre-defined correspondence between the indicator data and the service interface, the first target service interface is determined;

[0038] Based on the correspondence between the target service and the preset services and service interfaces, determine the second target service interface;

[0039] The first target service interface and the second target service interface are determined as the at least one target service interface.

[0040] In some implementations, the generation module is used to:

[0041] The at least one target service interface is invoked to process the indicator data based on the operation report template to obtain the report content;

[0042] An operations report is generated based on the report content and the operations report template.

[0043] In some embodiments, the apparatus further includes: a modification module, configured to:

[0044] In response to a user's modification request initiated through the visual interface, the operation report is modified accordingly.

[0045] Thirdly, embodiments of this application provide an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0046] The memory stores computer-executed instructions;

[0047] The processor executes computer execution instructions stored in the memory to implement the method described in the first aspect.

[0048] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first aspect.

[0049] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0050] The operation report generation method, apparatus, device, storage medium, and program product provided in this application, by responding to configuration operations initiated by users in a visual operation interface, obtains indicator configuration information and operation report templates corresponding to the configuration operations, obtains indicator data based on the indicator configuration information, and then determines at least one target service interface based on the indicator data and operation report template, and calls at least one target service interface to generate operation reports. This can link user configuration, indicator processing, and report generation, improve the timeliness and flexible adaptability of operation report generation, and thus better meet the requirements of high-frequency, multi-dimensional business analysis scenarios for operation report output efficiency, analysis support capabilities, and report adaptability. Attached Figure Description

[0051] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0052] Figure 1 A flowchart illustrating an operation report generation method provided in this application embodiment. Figure 1 ;

[0053] Figure 2 A flowchart illustrating a method for determining at least one target service interface, provided in an embodiment of this application;

[0054] Figure 3 A flowchart illustrating an operation report generation method provided in this application embodiment. Figure 2 ;

[0055] Figure 4 A schematic diagram of the structure of an operation report generation device provided in this application embodiment;

[0056] Figure 5 This is a schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application.

[0057] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0058] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0059] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation access points for users to choose to authorize or refuse.

[0060] Furthermore, the technical solution involved in this application, which involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.) and the use of artificial intelligence technology for automated decision-making, and makes decisions that have a significant impact on personal rights based on the results of automated decision-making, provides users with corresponding operation entry points for users to choose to agree to or reject the results of automated decision-making; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0061] It should be noted that the method, apparatus, equipment, storage medium and product for generating operation reports provided in this application can be used in the field of big data, or in any field other than big data. The application fields of the method, apparatus, equipment, storage medium and product for generating operation reports in this application are not limited.

[0062] In financial product operation analysis, existing methods typically employ BI reporting tools, rule-driven automated reporting systems, or basic text generation technologies to perform statistical analysis on business indicators and output operation reports.

[0063] However, such solutions often rely on periodic data processing, fixed template configurations, and manual analysis, resulting in delayed metric updates and difficulty in supporting high-frequency, multi-dimensional business scenarios.

[0064] To address the aforementioned issues, this application provides a method for generating operational reports. By responding to configuration operations initiated by users in a visual operation interface, the method obtains the corresponding indicator configuration information and operational report template. Based on the indicator configuration information, it acquires indicator data, determines at least one target service interface based on the indicator data and the operational report template, and calls at least one target service interface to generate the operational report. This method can link user configuration, indicator processing, and report generation, improving the timeliness and flexibility of operational report generation. This better meets the requirements for operational report output efficiency, analytical support capabilities, and report adaptability in high-frequency, multi-dimensional business analysis scenarios.

[0065] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0066] The execution subject in this application embodiment can be an electronic device or an operation report generation device installed in an electronic device. The electronic device can be a server, etc. The operation report generation device can be implemented by software or by a combination of software and hardware. For example, the operation report generation device can be a processor in the electronic device. For ease of understanding, the following description will use a server as the execution subject as an example.

[0067] Figure 1 A flowchart illustrating an operation report generation method provided in this application embodiment. Figure 1 ,like Figure 1 As shown, the method includes:

[0068] S101. Responding to configuration operations initiated by users through the visual operation interface, obtain the corresponding indicator configuration information and operation report template.

[0069] In this embodiment, the visual operation interface is used to receive configuration operations initiated by users and thereby obtain indicator configuration information and operation report templates. The visual operation interface can be deployed on a browser, desktop client, or the front-end page of an organization's internal operation analysis platform. The visual operation interface is configured with an indicator selection area, a time range configuration area, a dimension configuration area, a template editing area, and a submission control. Users can perform configuration operations by clicking, dragging, inputting, checking boxes, or selecting from dropdown menus.

[0070] The indicator configuration information describes the configuration content required to obtain indicator data in the future and serves as the input basis for generating subsequent operation reports. Specifically, it may include indicator name, statistical period, time range, business object, filtering conditions, aggregation method, sorting rules, anomaly threshold, and dimension information.

[0071] The operation report template is used to constrain the organization of the operation report content and serves as the basis for determining the target service interface, generating report content, and ultimately generating the operation report. Specifically, it can include the layout structure, field placeholders, chart types, paragraph order, and output format parameters corresponding to the report homepage, summary area, core indicator area, trend chart area, anomaly analysis area, attribution explanation area, strategy suggestion area, and conclusion area.

[0072] In one implementation, after the user enters the configuration page of the visual operation interface, the interface retrieves optional indicator definitions and template structure definitions via an API and renders them as editable components. When the user selects a specific business scenario, such as daily operational analysis of bank retail products, conversion analysis of insurance channels, or detection of securities customer activity, the business scenario identifier is recorded and written into the current session context. Then, the user selects the business indicator to be detected in the indicator configuration area, enters or selects the statistical time interval, such as the current day, the last seven days, the last thirty days, or a custom start and end date, and sets dimension information, such as institutional dimension, channel dimension, product dimension, customer segmentation dimension, geographic dimension, or time segmentation dimension. After receiving the configuration, the backend can also perform syntax validation, field validity validation, and permission validation on the configuration content, uniformly converting the indicator configuration information into an executable configuration.

[0073] In addition, users can select an existing template or create a new one in the operational report template area. When creating a new template, the interface supports drag-and-drop definition of report sections, placing key indicator cards, line charts, bar charts, pie charts, ranking tables, text paragraphs, analysis conclusions, and strategy recommendation containers on the template canvas. Users can also set titles, display order, placeholder fields, whether automatic summaries are needed, and whether editing is allowed for each container. If users adjust an existing template, the version number, modification time, and modifier of the adjusted template can be recorded, and a new template configuration snapshot can be generated upon submission.

[0074] After configuration, the metric configuration information and the operation report template can be submitted to the server in a structured message format. The message can be in JSON (JavaScript Object Notation) format, and the fields include task identifier, user identifier, business scenario identifier, metric configuration list, template structure definition, template version number, and real-time requirements. Upon receiving the message, the server can first perform an integrity check to confirm the correspondence between the metric configuration information and the fields referenced in the operation report template. Then, it writes the validated metric configuration information and operation report template to the task configuration storage area, forming the input objects required for subsequent processing.

[0075] S102. Obtain indicator data based on indicator configuration information, and determine at least one target service interface based on indicator data and operation report template.

[0076] Metric data is used as the basic input for subsequently determining target service interfaces and generating operational reports. Metric data can be a set of data in the form of numerical, categorical, sequential, or structured charts after being processed. It can correspond to the current value of a single indicator, or include trend sequences, comparison results, dimensional breakdown results, and anomaly labels.

[0077] The target service interface is used to undertake processing tasks based on indicator data and operation report templates, and output the intermediate content required to generate operation reports. Specifically, it may include attribution analysis service interface, strategy suggestion service interface, text generation service interface, chart generation service interface, and summary generation service interface.

[0078] Obtaining indicator data based on indicator configuration information essentially means obtaining indicator results that meet the requirements for generating operation reports based on user-defined configuration content; determining at least one target service interface based on indicator data and operation report template essentially means selecting processing capabilities that are compatible with operation report generation based on the current indicator results and the requirements of the operation report template.

[0079] Assuming that the indicator configuration information and operation report template are written to the task configuration storage area, in one implementation, the indicator configuration information formed in step S101 is first read from the task configuration storage area, and the corresponding indicator results are generated according to the configuration content. To ensure that results from different sources can be processed uniformly, the obtained results can also be standardized, including unifying the time format, unifying the monetary unit, unifying the percentage precision, filling in missing dimension values, and adding indicator caliber descriptions. If an indicator fails to be obtained, the error code and the reason for failure can be recorded, and an abnormal status identifier can be generated for the indicator so that it can be adapted when selecting the target service interface in the future.

[0080] After acquiring the metric data, the requirements of the metric data and the operational report template are matched to determine at least one target service interface. One or more target service interfaces can correspond to the same operational report generation process. If the user adjusts the operational report template or the metric results change, the process of determining the target service interface can be re-executed to ensure that the target service interface remains consistent with the currently input metric data and operational report template.

[0081] S103. Call at least one target service interface to generate an operation report based on metric data and an operation report template.

[0082] Operational reports are used to carry the final generated report results. Operational reports can be structured report objects displayed on the page, or editable documents, downloadable files, or pushable message carriers. They contain a report composed of indicator data, analysis content, chart content, and text content.

[0083] Calling at least one target service interface to generate an operation report based on indicator data and an operation report template essentially involves distributing the indicator data formed in S102 to each target service interface according to the operation report template definition, obtaining the corresponding intermediate analysis results and content results, and then assembling, rendering, and outputting the report according to the operation report template structure.

[0084] The service interfaces can be divided into attribution analysis service interfaces, strategy suggestion service interfaces, text generation service interfaces, chart generation service interfaces, and summary generation service interfaces. The attribution analysis service interface takes abnormal indicator values, historical comparison values, and threshold deviation information as input, and returns the main impacts causing the indicator changes and corresponding explanatory text. The strategy suggestion service interface takes attribution results, indicator status, business scenario identifiers, and constraints as input, and returns the execution strategy text, related action items, and applicable objects corresponding to the current business scenario. The text generation service interface takes indicator names, current values, comparison results, trend characteristics, and tone constraints or paragraph templates from the operation report template as input, and outputs natural language content that can be directly written into the report. The chart generation service interface takes time series or grouped aggregation results and the chart type specified in the operation report template as input, and returns a chart configuration object or renderable image data. The summary generation service interface takes core indicator results, main anomalies, attribution conclusions, and strategy highlights as input, and returns a report summary text.

[0085] Each target service interface can be implemented using an HTTP (Hypertext Transfer Protocol) interface, a remote procedure call interface, or a service bus interface. During the call, each interface should be encapsulated with unified input parameters, which should at least include the identifier of the indicator data, the section identifier of the operation report template, a description of the data caliber, and an identifier of the call context.

[0086] After the service interface returns the results, structural validation and content archiving can be performed on the results, and the output of different interfaces can be written to the corresponding module cache. If an interface fails to execute, it can be retried according to the preset fault tolerance rules; if the retry still fails, the module is marked as awaiting manual supplementation, and the content of other successfully generated modules is retained, so that the reporting task can continue to be completed.

[0087] After the calls to each target service interface are completed, the content is assembled according to the operation report template. Specifically, the chart content is filled into the trend chart area and ranking area, the attribution analysis results are filled into the anomaly analysis area and attribution explanation area, the strategy suggestion results are filled into the strategy suggestion area, the text generation results are filled into the explanatory paragraphs and conclusion area, and the summary generation results are written into the summary area. At the same time, the paragraph order, image and text position, font style, table column width, and pagination rules are set according to the layout parameters in the operation report template to generate a complete operation report.

[0088] The method for generating an operation report provided in this application responds to a configuration operation initiated by a user through a visual operation interface, obtains the indicator configuration information and operation report template corresponding to the configuration operation, obtains indicator data based on the indicator configuration information, determines at least one target service interface based on the indicator data and the operation report template, and calls the at least one target service interface to generate an operation report based on the indicator data and the operation report template.

[0089] This method integrates the configuration information of visual configuration indicators, the operation report template, the dynamic determination of service interfaces, and the assembly of reports into the same processing link. Configuration changes can be directly transmitted to the data acquisition and content generation stages, and indicator data can be updated according to the current time range and business dimensions. The analysis and generation tasks corresponding to different contents in the operation report template are automatically undertaken by the target service interface, and finally, an operation report matching the business scenario is generated. This ensures that the report generation process can respond quickly to business changes, has depth of analysis, and adaptability to templates.

[0090] In some embodiments, the configuration information includes a data source and data processing logic. Raw business data can be obtained from the data source, and the raw business data can be processed according to the data processing logic to obtain indicator data.

[0091] In practice, the corresponding data source identifier and data processing logic identifier can be parsed from the indicator configuration information first. Then, the corresponding data source is accessed according to the data source identifier to read the raw business data that meets the time range, business type, or other constraints. The read raw business data can be detailed records or a data set that has been pre-filtered by business dimension. It is then input into the data processing logic to perform calculations, such as summarizing transaction amounts by product dimension, counting active times by customer dimension, or calculating conversion rates according to a specified period. After processing, the output indicator data can be saved in the form of numerical values, arrays, structured records, or key-value pairs for subsequent use in conjunction with operational report templates.

[0092] In this implementation, the data source provides the raw input, the data processing logic unifies business dimensions and calculates metrics, and the metric data is stably output as an intermediate result, enabling subsequent report generation to directly call the already formed metric results. By separating the configuration of raw business data and processing rules, adaptation can be completed by only updating the corresponding relationships and data processing logic when the data source changes or the metric dimensions are adjusted, reducing additional modifications to the operational report generation chain.

[0093] Optionally, at least one target service interface may be identified based on metric data and operational report templates, such as Figure 2 As shown, the method includes:

[0094] S201. Based on the operation report template, determine the components of the operation report.

[0095] The operational report template can be structured and parsed to extract all the necessary components of the report, and the content boundaries, display logic, and output requirements of each component can be standardized.

[0096] S202. Determine the corresponding target indicator data from the indicator data based on each component, and determine the corresponding target service based on each component.

[0097] The target metrics data for each component can be obtained by filtering the metric data pool by field name, time range, business dimension, and caliber label. For example, when the component is transaction trend analysis, metrics such as transaction volume, number of transactions, and month-on-month change rate are extracted; when the component is customer activity analysis, metrics such as number of active customers, retention rate, and conversion rate are extracted. The target services for each component can be determined based on the content generation requirements of that component, such as chart generation service, attribution analysis service, strategy suggestion service, or text generation service, and the service identifiers are written into the component mapping table.

[0098] S203. Determine at least one target service interface based on the target indicator data and target service.

[0099] After completing the pairing of target indicator data and target services, at least one target service interface can be determined based on the correspondence between target indicator data, target services and service interfaces. This target service interface can then be used for subsequent operation report generation, enabling each component of the operation report template to obtain service capabilities that match its content.

[0100] The method for determining at least one target service interface provided in this application first determines the components of an operation report based on an operation report template, then determines the corresponding target indicator data from the indicator data based on each component, and finally determines the corresponding target service based on each component. Finally, at least one target service interface is determined based on the target indicator data and the target service. This method establishes a mapping relationship between the target service interface and the structure of the operation report template, reducing target service interface selection bias and ensuring consistency between indicator data input, service processing, and operation report generation, thereby improving the adaptability and accuracy of the generated operation report.

[0101] Optionally, determining at least one target service interface based on target indicator data and target service includes: determining a first target service interface based on target indicator data and a preset correspondence between indicator data and service interfaces, and determining a second target service interface based on target service and a preset correspondence between service and service interfaces, and then determining the first target service interface and the second target service interface as at least one target service interface.

[0102] The target indicator data can be abnormal indicators, volatile indicators, or indicator values ​​that require special explanation extracted from the operation report template. First, the target indicator data is compared with the indicator configuration in the mapping table to determine the first target service interface that can output the corresponding analysis results. At the same time, the service capabilities that need to be called are determined based on the target service. The target service can be an attribution analysis service, a confidence calculation service, or a report text generation service. Then, the second target service interface is determined based on the correspondence between services and interfaces.

[0103] If the first target service interface and the second target service interface point to the same service interface, they can be directly merged into the same target service interface; if the first target service interface and the second target service interface correspond to different processing units, they are jointly determined as at least one target service interface and executed sequentially according to the calling order.

[0104] This method of determining target service interfaces enables target metric data and target services to drive the selection of target service interfaces separately, reducing mismatches and duplicate calls to target service interfaces, thereby improving the accuracy of operational report content.

[0105] The following is combined with Figure 3The method for generating the operations report will be further explained. Figure 3 A flowchart illustrating an operation report generation method provided in this application embodiment. Figure 2 ,like Figure 3 As shown, the method also includes:

[0106] S301. Call at least one target service interface, process the indicator data based on the operation report template, and obtain the report content.

[0107] After obtaining the indicator data and operational report template by calling at least one target service interface, the system can perform matching, calculation, aggregation, interpretation, or text generation processing on the indicator data, and output report content corresponding to each component of the operational report template. For chart-type components, the system can generate the data sequence or rendering parameters required for the graph based on the indicator data; for analysis paragraph-type components, the system can output text analysis results based on indicator change trends, differences, or abnormal fluctuations; for conclusion paragraph-type components, the system can generate conclusive descriptions based on the processed indicator data, thus forming intermediate content that can be directly used for typesetting and splicing.

[0108] S302. Generate an operations report based on the report content and operations report template.

[0109] After obtaining the report content, it can be assembled, mapped, and populated according to the components of the operations report template to generate the final operations report. The assembly process involves piecing together titles, charts, analysis paragraphs, and conclusion paragraphs in the template order, maintaining consistency in the hierarchical relationships, display styles, and placeholder rules between the components. This ensures the final operations report fully reflects the results of the indicator data processing. If the operations report template contains dynamic binding relationships, the corresponding report content can be filled into designated locations based on the binding information, ensuring that the operations report template remains consistent even after adjustments.

[0110] The method for generating operation reports provided in this application first calls at least one target service interface, processes the indicator data based on the operation report template to obtain report content, and then generates an operation report based on the report content and the operation report template. This method, by inputting indicator data and the operation report template into the target service interface to generate report content, and then assembling the operation report according to the template, can complete indicator processing and report output while maintaining the configurability of report components, enabling the report content to directly correspond to the display requirements of different components.

[0111] In some embodiments, after generating the operation report, the operation report can also be modified in response to a user's modification request initiated through a visual operation interface.

[0112] The "Modify" function triggers further processing of the generated operational report. This operation is initiated by the user within the visual operation interface, which displays the main text, tables, and charts of the operational report and provides corresponding editing entry points. Users can use interactive methods such as mouse clicks, touch selection, keyboard input, or drag-and-drop adjustments to partially edit text descriptions, indicator names, chart titles, annotations, table cells, or chart labels in the operational report. Users can replace, add, delete, or rearrange content according to their needs, and the modified operational report is synchronously updated to the current editing view.

[0113] In one implementation, the object to be modified can be determined first based on the report area selected by the user in the interface, and then the text editing component, table editing component, or chart editing component can be called to process the corresponding content. For text content, new text can be written directly while retaining the original paragraph format; for table content, cell data can be overwritten while maintaining consistent column width, row height, and border styles; for chart content, chart titles, data labels, or legends can be updated, and the chart display results can be re-rendered.

[0114] After modification, the updated operation report can be saved as a downloadable file format that matches the operation report template. The file format can be PDF (Portable Document Format), Word, HTML (Hyper Text Markup Language), DOCX (Office Open XML (Machine Learning) Document), XLSX (Office Open XML (Extensible Markup Language) Spreadsheet), or other formats that are easy to download and archive. In practical applications, other file formats can also be selected, and this application does not limit this.

[0115] By introducing a method for partial modification based on a visual interface after generating the operational report, partial content can be revised without regenerating the entire report, and the revised results can be output in a downloadable format. This ensures that the report content is consistent with the user's real-time analysis needs, while also facilitating subsequent delivery, archiving, and reuse.

[0116] Figure 4 This is a schematic diagram of the structure of an operation report generation device provided in an embodiment of this application. Figure 4 As shown, the operation report generation device 400 includes:

[0117] The acquisition module 401 is used to respond to the configuration operation initiated by the user through the visual operation interface and to acquire the indicator configuration information and operation report template corresponding to the configuration operation.

[0118] The determination module 402 is used to obtain indicator data based on indicator configuration information, and determine at least one target service interface based on the indicator data and the operation report template.

[0119] The generation module 403 is used to call at least one target service interface to generate an operation report based on indicator data and an operation report template.

[0120] In some implementations, the operation report generation apparatus further includes a processing module for:

[0121] Obtain raw business data from the data source;

[0122] The original business data is processed according to the data processing logic to obtain the indicator data.

[0123] In some implementations, the determining module 402 is used for:

[0124] Based on the operations report template, determine the components of the operations report;

[0125] Based on each component, the corresponding target indicator data is determined from the indicator data, and the corresponding target service is determined based on each component;

[0126] Identify at least one target service interface based on the target indicator data and target services.

[0127] In some implementations, the determining module 402 is used for:

[0128] Based on the target indicator data and the pre-defined correspondence between the indicator data and the service interface, determine the first target service interface;

[0129] Based on the correspondence between the target service and the preset services and service interfaces, determine the second target service interface;

[0130] The first target service interface and the second target service interface are determined as at least one target service interface.

[0131] In some implementations, the generation module 403 is used for:

[0132] Call at least one target service interface, process the indicator data based on the operation report template, and obtain the report content;

[0133] Generate an operations report based on the report content and operations report template.

[0134] In some implementations, the operation report generation apparatus further includes: a modification module, used for:

[0135] In response to user-initiated modification requests through the visual interface, the operation report is modified accordingly.

[0136] The operation report generation device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0137] Figure 5 This is a schematic diagram of the structure of an electronic device provided for an exemplary embodiment of this application. Please refer to... Figure 5 The electronic device 500 may include at least one processor 501 for implementing the operation report generation method provided in the embodiments of this application.

[0138] Optionally, the electronic device 500 further includes at least one memory 502 for storing program instructions and / or data. The memory 502 is coupled to the processor 501. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 501 may operate in conjunction with the memory 502. The processor 501 may execute program instructions stored in the memory 502. At least one of the at least one memory may be included in the processor.

[0139] Optionally, the electronic device 500 further includes a communication interface 503 for communicating with other devices via a transmission medium, thereby enabling the electronic device 500 to communicate with other devices. The communication interface 503 may be, for example, a transceiver, interface, bus, circuit, or a device capable of transmitting and receiving functions. The processor 501 can utilize the communication interface 503 to transmit and receive data and / or information, and to implement the methods provided in the embodiments of this application. See the detailed description in the preceding embodiments for further details, which will not be repeated here.

[0140] This application embodiment does not limit the specific connection medium between the processor 501, memory 502, and communication interface 503. This application embodiment... Figure 5 The processor 501, memory 502, and communication interface 503 are connected via bus 504. Bus 504 is... Figure 5 The connections between other components are shown in bold lines only and are not intended to be limiting. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0141] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0142] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0143] Accordingly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the methods described in the above-described method embodiments.

[0144] Accordingly, embodiments of this application may also provide a computer program product, which includes a computer program that, when executed by a processor, can implement the methods shown in the above-described method embodiments.

[0145] The terms “unit”, “module”, etc., used in this specification may be used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution.

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

[0147] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0148] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0149] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0150] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0151] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0152] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0153] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0154] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for generating an operational report, characterized in that, include: In response to a configuration operation initiated by a user through a visual operation interface, obtain the corresponding indicator configuration information and operation report template; Obtain indicator data based on the indicator configuration information, and determine at least one target service interface based on the indicator data and the operation report template; Invoke the at least one target service interface to generate an operation report based on the indicator data and the operation report template.

2. The method according to claim 1, characterized in that, The indicator configuration information includes data sources and data processing logic; the step of obtaining indicator data based on the indicator configuration information includes: Obtain raw business data from the data source; The original business data is processed according to the data processing logic to obtain the indicator data.

3. The method according to claim 1, characterized in that, The step of determining at least one target service interface based on the indicator data and the operation report template includes: Based on the aforementioned operation report template, determine the components of the operation report; Based on each component, the corresponding target indicator data is determined from the indicator data, and the corresponding target service is determined based on each component; At least one target service interface is determined based on the target indicator data and the target service.

4. The method according to claim 3, characterized in that, The step of determining at least one target service interface based on the target metric data and the target service includes: Based on the target indicator data and the pre-defined correspondence between the indicator data and the service interface, the first target service interface is determined; Based on the correspondence between the target service and the preset services and service interfaces, determine the second target service interface; The first target service interface and the second target service interface are determined as the at least one target service interface.

5. The method according to any one of claims 1-4, characterized in that, The step of invoking the at least one target service interface to generate an operation report based on the indicator data and the operation report template includes: The at least one target service interface is invoked to process the indicator data based on the operation report template to obtain the report content; An operations report is generated based on the report content and the operations report template.

6. The method according to any one of claims 1-4, characterized in that, After generating the operation report, the method further includes: In response to a user's modification request initiated through the visual interface, the operation report is modified accordingly.

7. An apparatus for generating an operational report, characterized in that, include: The acquisition module is used to respond to the configuration operation initiated by the user through the visual operation interface, and to acquire the indicator configuration information and operation report template corresponding to the configuration operation. The determination module is used to obtain indicator data based on the indicator configuration information, and determine at least one target service interface based on the indicator data and the operation report template. The generation module is used to call the at least one target service interface to generate an operation report based on the indicator data and the operation report template.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6.

Images