Data submission method and device, electronic equipment and storage medium

Abstract

The invention relates to a data submission method and device, electronic equipment and a storage medium, and belongs to the technical field of financial science and technology, information technology industry and data processing. The method comprises the following steps: abstracting a submission action to obtain a candidate code, and binding the submission action with the candidate code, so that a user does not need to compile the submission code when arranging the submission workflow, the user operation is simplified, the arrangement difficulty of the submission workflow is reduced, and the arrangement efficiency of the submission workflow is improved; determining a submission action contained in the candidate workflow based on the type of the arrangement operation and the operation information of the arrangement operation to generate the candidate workflow, determining a target workflow from a workflow library, and configuring the target workflow based on the configuration information of a target submission event to generate a submission instance, therefore, the submission workflow and the submission instance can be automatically generated, and the submission instance is executed by scheduling the application program to process the target submission event, so that the data submission efficiency is improved.

Description

Technical Field

[0001] The present disclosure relates to the fields of financial technology, information technology industry, and data processing technology, and in particular to a data reporting method, device, electronic device, computer-readable storage medium, and computer program product. Background Art

[0002] At present, with the continuous development of Internet technology, workflow has the advantages of high office automation and high office efficiency, and has been widely used. However, in the related technologies, most of the data are submitted manually, especially in the data submission scenario with large data volume, there are many repetitive operations, long time consumption and low data submission efficiency. Summary of the invention

[0003] The present disclosure provides a data reporting method, device, electronic device, computer-readable storage medium and computer program product to at least solve the problem of low data reporting efficiency in related technologies. The technical solution of the present disclosure is as follows:

[0004] According to a first aspect of an embodiment of the present disclosure, a data reporting method is provided, comprising: abstracting a reporting action to obtain a candidate code, and binding the reporting action to the candidate code; in response to detecting an orchestration operation for a candidate workflow, determining the reporting action included in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation to generate the candidate workflow, and adding the candidate workflow to a workflow library; determining a target workflow of a target reporting event from the workflow library, and configuring the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event; importing the reporting instance into a scheduling application, and parsing the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed; executing the target code through the scheduling application to execute the reporting instance to process the target reporting event.

[0005] According to a second aspect of an embodiment of the present disclosure, a data reporting device is provided, comprising: an abstraction module configured to abstract a reporting action, obtain a candidate code, and bind the reporting action to the candidate code; an orchestration module configured to determine, in response to detecting an orchestration operation for a candidate workflow, the reporting action contained in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation, so as to generate the candidate workflow, and add the candidate workflow to a workflow library; a configuration module configured to determine a target workflow of a target reporting event from the workflow library, and configure the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event; a parsing module configured to import the reporting instance into a scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed; and an execution module configured to execute the target code through the scheduling application to execute the reporting instance to process the target reporting event.

[0006] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the data reporting method as described in the first aspect.

[0007] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the data reporting method as described in the first aspect.

[0008] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the data reporting method as described in the first aspect is implemented.

[0009] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects: abstracting the submission action to obtain the candidate code, and binding the submission action with the candidate code, so that the user does not need to write the submission code when arranging the submission workflow, which simplifies the user operation, reduces the difficulty of arranging the submission workflow, and improves the arranging efficiency of the submission workflow. In addition, considering the type of the arranging operation and the operation information of the arranging operation, the submission action included in the candidate workflow can be determined to generate the candidate workflow, and the candidate workflow can be added to the workflow library, so that the automatic submission workflow can be realized. Generate, in addition, determine the target workflow of the target reporting event from the workflow library, and take into account the configuration information of the target reporting event, automatically configure the target workflow, generate the reporting instance of the target reporting event, and realize the automatic generation of the reporting instance. Import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed. Execute the target code through the scheduling application to execute the reporting instance, which can realize the automation of data reporting and improve the efficiency of data reporting.

[0010] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0012] Figure 1 It is a flowchart of the data reporting method according to the first embodiment of the present disclosure.

[0013] Figure 2 It is a flowchart of a data reporting method according to the second embodiment of the present disclosure.

[0014] Figure 3 It is a flowchart of a data reporting method according to the third embodiment of the present disclosure.

[0015] Figure 4 It is a flowchart of a data reporting method according to the fourth embodiment of the present disclosure.

[0016] Figure 5 is a block diagram of a data reporting device according to the first embodiment of the present disclosure.

[0017] Figure 6 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0018] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0019] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0020] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards.

[0021] It should be noted that the acquisition, transmission, storage, use, and processing of data in the technical solution of the present disclosure are in compliance with the relevant provisions of relevant laws and regulations. In the embodiments of the present disclosure, certain software, components, models, and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present disclosure, but it does not mean that the applicant has or will necessarily use the solution.

[0022] Figure 1 It is a flowchart of the data reporting method according to the first embodiment of the present disclosure.

[0023] like Figure 1 As shown, the data reporting method of the first embodiment of the present disclosure includes the following steps:

[0024] S101, abstract the reporting action, obtain the candidate code, and bind the reporting action with the candidate code.

[0025] It should be noted that the execution subject of the data reporting method of the present disclosure is an electronic device, wherein the electronic device may include a mobile phone, a notebook, a vehicle-mounted device, a smart home appliance, etc. The data reporting method of the embodiment of the present disclosure may be executed by the data reporting device of the embodiment of the present disclosure, and the data reporting device of the embodiment of the present disclosure may be configured in any electronic device to execute the data reporting method of the embodiment of the present disclosure.

[0026] It should be noted that there are no excessive restrictions on reporting actions, for example, it may include data collection, data analysis, data processing, data encryption, data review, data packaging, data compression, data transmission, etc. Among them, data analysis may include data analysis through delimiters, extraction of labels or key-value pairs, text analysis based on NLP (Natural Language Processing), structured processing, etc., and data processing may include data cleaning, data conversion, feature engineering, data aggregation, data segmentation, quality inspection, etc.

[0027] It should be noted that abstracting the reporting action to obtain the candidate code means converting the reporting action into an executable script, which can be implemented by using any step abstraction method in the relevant technology, and no excessive restrictions are made here. For example, the name, execution method, formal parameters, code type, etc. of the candidate code can be configured.

[0028] It can be understood that binding a reporting action with a candidate code refers to binding a reporting action with a candidate code abstracted from the reporting action. Different reporting actions may be bound to different candidate codes.

[0029] In one implementation, after obtaining the candidate code, the process further includes deploying the candidate code to a local storage space.

[0030] For example, the reporting action 1 may be abstracted to obtain the candidate code 1, and the reporting action 1 may be bound to the candidate code 1, and the candidate code 1 may be deployed to the local storage space.

[0031] For example, the reporting action 2 may be abstracted to obtain the candidate code 2, and the reporting action 2 may be bound to the candidate code 2, and the candidate code 2 may be deployed to the local storage space.

[0032] S102, in response to detecting an orchestration operation for a candidate workflow, determining a reporting action included in the candidate workflow based on the type of the orchestration operation and operation information of the orchestration operation to generate a candidate workflow, and adding the candidate workflow to a workflow library.

[0033] It should be noted that the candidate workflow is a workflow for data reporting (hereinafter referred to as a reporting workflow), and the terms workflow, work process, etc. are interchangeable. A candidate workflow contains at least one reporting action. There are no excessive restrictions on the types of orchestration operations, such as selection operations, input operations, etc. Among them, the selection operation may include a click operation, a drag operation, etc. The workflow library includes multiple candidate workflows.

[0034] In one embodiment, the method further includes controlling the display of multiple candidate selection items on an interactive page during the arrangement of the candidate workflow, wherein the candidate selection items are used to represent the reporting action.

[0035] Based on the type of the orchestration operation and the operation information of the orchestration operation, the submission action included in the candidate workflow is determined, including responding to the type of the orchestration operation being a selection operation, taking the candidate selection item selected by the selection operation as the target selection item, and adding the submission action corresponding to the target selection item to the submission action included in the candidate workflow. In this way, the submission action selected by the user can be added to the submission action included in the submission workflow, and the visualization and personalized orchestration of the submission workflow can be realized.

[0036] It is understandable that the user can perform selection operations on the interactive page for the candidate selection items, and there is no excessive restriction on the shape and other information of the candidate selection items. For example, different types of reporting actions may correspond to different shapes of candidate selection items. There is no excessive restriction on the display mode of the candidate selection items, for example, it may include pop-up window display, notification bar display, floating window display, etc. The multiple candidate selection items include the target selection item.

[0037] Exemplarily, the start action component, the end action component, the arrow component, etc. can be controlled to be displayed on the interactive page. The start action component is used to represent the start of execution of the candidate workflow, the end action component is used to represent the end of execution of the candidate workflow, and the arrow component is used to represent whether the reporting action is successfully executed. Among them, the start action component and the end action component are both ovals, the candidate selection items are rectangles, the arrow component used to represent the successful execution of the reporting action is a solid arrow, and the arrow component used to represent the failure of the reporting action is a dotted arrow.

[0038] For example, during the arrangement of candidate workflow A, candidate options 1 to 10 may be controlled to be displayed on the interactive interface, wherein candidate option k is used to represent reporting action k, and k is a positive integer not greater than 10.

[0039] In response to detecting a selection operation for candidate workflow A, candidate selection items 1 and 3 selected by the selection operation are used as target selection items, and reporting action 1 corresponding to candidate selection item 1 and reporting action 3 corresponding to candidate selection item 3 are added to the reporting actions included in candidate workflow A.

[0040] In one embodiment, the method further comprises generating a candidate workflow based on the reporting actions included in the candidate workflow, the dependency relationships between the reporting actions included in the candidate workflow, and the name of the candidate workflow, wherein the dependency relationships may include serial relationships, parallel relationships, and the like.

[0041] S103, determining a target workflow of a target reporting event from a workflow library, and configuring the target workflow based on configuration information of the target reporting event to generate a reporting instance of the target reporting event.

[0042] It should be noted that the workflow library includes the target workflow.

[0043] In one embodiment, determining the target workflow of the target reporting event from the workflow library includes, in response to detecting a selection operation for the candidate workflow, using the candidate workflow selected by the selection operation as the target workflow. Thus, the candidate workflow selected by the user can be used as the target workflow of a reporting event, and personalized selection of the reporting workflow can be achieved.

[0044] In one embodiment, determining a target workflow of a target reporting event from a workflow library includes obtaining a target reporting scenario of the target reporting event and candidate reporting scenarios of each of a plurality of candidate workflows in the workflow library, obtaining the similarity between the target reporting scenario and the candidate reporting scenario, and determining the target workflow from the workflow library based on the similarity. Thus, the similarity between the target reporting scenario and the candidate reporting scenario can be considered to determine the target workflow from the workflow library, which helps to obtain a target workflow that matches the target reporting scenario and improves the success rate of data reporting.

[0045] It should be noted that there are no excessive restrictions on the reporting scenarios, for example, they may include the reporting content, the field to which the data to be reported belongs, the type of reporting agency (such as the reporting initiator, the reporting responder), etc. The terms such as reporting initiator and data sender can be interchangeable, and the terms such as reporting responder and data receiver can be interchangeable.

[0046] In some examples, based on the similarity, a target workflow is determined from a workflow library, including taking a candidate workflow corresponding to the greatest similarity as the target workflow.

[0047] In some examples, a target workflow is determined from a workflow library based on similarity, including obtaining a target score of a candidate workflow based on similarity, and selecting a candidate workflow corresponding to a maximum target score as the target workflow.

[0048] Exemplarily, based on the similarity, a target score of the candidate workflow is obtained, including obtaining the target score of the candidate workflow based on the similarity and the initial score of the candidate workflow. For example, the candidate workflows may be scored in advance to obtain the initial scores of the plurality of candidate workflows. For example, the similarity and the initial score may be weighted and summed to obtain the target score.

[0049] It should be noted that there are no excessive restrictions on the configuration information of the reporting event, for example, it may include the reporting content, reporting agency (such as reporting initiator, reporting responder), reporting node, strategy for identifying whether to re-report, strategy for identifying whether the reporting action is successfully executed, etc. The configuration information of different reporting events may be different.

[0050] Exemplarily, the reported content may include the type, format, reporting method, data source, etc. of the data to be reported.

[0051] Exemplarily, the strategy for identifying whether to resubmit may include determining to resubmit in response to receiving first indication information (such as a resubmission flag) for indicating resubmission, and determining not to resubmit in response to not receiving the first indication information.

[0052] Exemplarily, a strategy for identifying whether a reporting action is successfully executed may include determining that the reporting action is successfully executed in response to receiving second indication information (such as a success return code) indicating that the reporting action is successfully executed, and determining that the reporting action fails in response to not receiving the second indication information.

[0053] Exemplarily, a strategy for identifying whether a reporting action is successfully executed may include determining that the reporting action has failed in response to receiving third indication information (such as a failure return code) indicating that the reporting action has failed to execute, and determining that the reporting action has been successfully executed in response to not receiving the third indication information.

[0054] In the embodiments of the present disclosure, based on the configuration information of the target reporting event, the target workflow is configured to generate a reporting instance of the target reporting event, including the following possible implementations:

[0055] Method 1: Identify whether there is overlapping information between the configuration information of N target reporting events, where N is a positive integer greater than 1. In response to the existence of overlapping information between the configuration information of the N target reporting events, batch configure the target workflows of the N target reporting events based on the overlapping information to generate reporting instances for the N target reporting events.

[0056] Therefore, when there is overlapping information between the configuration information of multiple reporting events, the reporting workflows of the multiple reporting events can be batch configured based on the overlapping information to generate multiple reporting instances, thereby improving the configuration efficiency of the reporting workflows and further improving the generation efficiency of the reporting instances.

[0057] For example, identify whether there is overlapping information between the configuration information of the target reporting events 1 to 10. In response to the consistency of the reporting content and reporting agency of the target reporting events 1 to 10, batch configure the target workflows of the target reporting events 1 to 10 based on the above reporting content and reporting agency, and generate reporting instances for the target reporting events 1 to 10.

[0058] Method 2: Determine the reporting content and reporting organization of the target reporting event from the configuration information of the target reporting event, bind the target workflow to the reporting content and reporting organization of the target reporting event respectively, and generate a reporting instance.

[0059] Therefore, the reporting workflow can be bound to the reporting content and reporting organization of the reporting event respectively to generate a reporting instance.

[0060] It is understandable that the reporting content and reporting agencies bound to different reporting workflows may be different.

[0061] Method 3: Obtain the candidate code bound to the reporting action contained in the target workflow as the target code to be executed, configure the actual parameters of the target code based on the configuration information of the target reporting event, and generate a reporting instance.

[0062] Thus, the actual parameters of the reporting code may be configured taking into account the configuration information of the reporting event to generate a reporting instance.

[0063] S104, importing the reporting instance into the scheduling application, and parsing the reporting instance through the scheduling application to obtain candidate codes bound to the reporting actions contained in the reporting instance as target codes to be executed.

[0064] S105, executing the target code by scheduling the application to execute the reporting instance to process the target reporting event.

[0065] It should be noted that the multiple candidate codes include a target code, and the number of the target code is at least one. The scheduling application refers to an application for scheduling workflows, and there are no excessive restrictions on the scheduling application, for example, it may include a batch processing program.

[0066] For example, there is a binding relationship between the reporting action p and the candidate code p, where p is a positive integer not greater than 10.

[0067] The target workflow of the target reporting event 1 is determined from the workflow library as the candidate workflow A. Based on the configuration information of the target reporting event 1, the candidate workflow A is configured to generate a reporting instance B of the target reporting event 1.

[0068] Import reporting instance B into the scheduling application, and parse reporting instance B through the scheduling application to obtain reporting actions 1 and 3 contained in reporting instance B, obtain candidate code 1 bound to reporting action 1, and candidate code 3 bound to reporting action 3 as target codes to be executed.

[0069] The candidate codes 1 and 3 are executed by scheduling the application to execute the reporting instance B to process the target reporting event 1.

[0070] In summary, according to the data submission method provided by the embodiment of the present disclosure, the submission action is abstracted to obtain the candidate code, and the submission action is bound to the candidate code, so that the user does not need to write the submission code when arranging the submission workflow, which simplifies the user operation, reduces the difficulty of arranging the submission workflow, and improves the efficiency of arranging the submission workflow. In addition, the submission action included in the candidate workflow can be determined by considering the type of the arranging operation and the operation information of the arranging operation to generate the candidate workflow, and the candidate workflow is added to the workflow library, so that the automatic generation of the submission workflow can be realized. In addition, the target workflow of the target reporting event is determined from the workflow library, and the configuration information of the target reporting event is taken into consideration to automatically configure the target workflow and generate a reporting instance of the target reporting event. This can realize the automatic generation of the reporting instance, import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed. The target code is executed through the scheduling application to execute the reporting instance, which can realize the automation of data reporting and improve the efficiency of data reporting.

[0071] Figure 2 It is a flowchart of a data reporting method according to the second embodiment of the present disclosure.

[0072] like Figure 2 As shown, the data reporting method of the second embodiment of the present disclosure includes the following steps:

[0073] S201, abstracting the reporting action to obtain a candidate code, and binding the reporting action to the candidate code.

[0074] For the relevant contents of step S201, please refer to the above embodiment, which will not be repeated here.

[0075] S202: In response to detecting an orchestration operation for a candidate workflow, and in response to the type of the orchestration operation being a first entry operation for a reporting action, obtaining a reporting action entered by the first entry operation.

[0076] S203, adding the entered submission action to the submission actions included in the candidate workflow to generate a candidate workflow, and adding the candidate workflow to the workflow library.

[0077] S204, abstracting the entered reporting action to obtain a newly added candidate code, and binding the entered reporting action with the newly added candidate code.

[0078] The relevant contents of step S204 may refer to the relevant contents of step S101 and will not be repeated here.

[0079] S205, obtaining the candidate code entered by the first entry operation, and binding the entered reporting action with the entered candidate code.

[0080] It is understandable that the user can perform the first input operation for the reporting action on the interactive page. Exemplarily, when the user enters the reporting action, he can also enter the candidate code.

[0081] For example, during the arrangement of candidate workflow A, an input box can be controlled to be displayed on the interactive interface. In response to detecting a first input operation for a reporting action, reporting actions 11 and 12 entered by the first input operation are obtained, and reporting actions 11 and 12 are added to the reporting actions included in candidate workflow A.

[0082] The reporting action 11 may be abstracted to obtain the candidate code 11, and the reporting action 11 may be bound to the candidate code 11, and the candidate code 11 may be deployed to the local storage space.

[0083] The candidate code 12 entered by the first entry operation may be obtained, and the candidate code 12 may be bound to the candidate code 12, and the candidate code 12 may be deployed to the local storage space.

[0084] S206, determining a target workflow of the target reporting event from the workflow library, and configuring the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event.

[0085] S207, importing the reporting instance into the scheduling application, and parsing the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed.

[0086] S208, executing the target code by scheduling the application to execute the reporting instance to process the target reporting event.

[0087] For the relevant contents of steps S206-S208, please refer to the above embodiment and will not be repeated here.

[0088] In summary, according to the data reporting method provided by the embodiment of the present disclosure, in response to the type of orchestration operation being a first entry operation for a reporting action, the reporting action entered by the first entry operation is obtained, and the entered reporting action is added to the reporting actions included in the candidate workflow, so that the reporting action entered by the user can be added to the reporting actions included in the reporting workflow, and personalized orchestration of the reporting workflow can be achieved. In addition, the entered reporting action is abstracted to obtain a newly added candidate code, and the entered reporting action is bound to the newly added candidate code, and / or the candidate code entered by the first entry operation is obtained, and the entered reporting action is bound to the entered candidate code, so that the candidate code bound to the entered reporting action can be automatically obtained through step abstraction, and / or the candidate code entered by the user can be used as the candidate code bound to the entered reporting action, and personalized configuration of the candidate code can be achieved.

[0089] Figure 3 It is a flowchart of a data reporting method according to the third embodiment of the present disclosure.

[0090] like Figure 3 As shown, the data reporting method of the third embodiment of the present disclosure includes the following steps:

[0091] S301, abstract the reporting action, obtain the candidate code, and bind the reporting action with the candidate code.

[0092] For the relevant contents of step S301, please refer to the above embodiment, which will not be repeated here.

[0093] S302: In response to detecting an orchestration operation for a candidate workflow, and in response to the type of the orchestration operation being a second input operation for an orchestration requirement, obtaining an orchestration requirement for the candidate workflow input by the second input operation.

[0094] It is understandable that the user can perform a second input operation for the arrangement requirements on the interactive page. There are no excessive restrictions on the arrangement requirements, for example, they may include the reporting content, reporting frequency, scheduled reporting, the field to which the data to be reported belongs, the type of reporting agency (such as the reporting initiator, the reporting responder), etc. The arrangement requirements of different candidate workflows may be different.

[0095] S303: Input the orchestration requirements into the target model, and the target model outputs text description information of the candidate workflow.

[0096] S304: Determine the reporting action included in the candidate workflow from the text description information to generate the candidate workflow, and add the candidate workflow to the workflow library.

[0097] It should be noted that there are no excessive restrictions on the target model, for example, it may include a language model, a large model (such as a large language model), etc. The text description information includes the reporting actions included in the candidate workflow. Exemplarily, the text description information also includes the dependency relationship between the reporting actions included in the candidate workflow, the name of the candidate workflow, etc. The training content of the target model can be found in the following embodiments, which will not be repeated here.

[0098] S305, determining a target workflow of a target reporting event from a workflow library, and configuring the target workflow based on configuration information of the target reporting event to generate a reporting instance of the target reporting event.

[0099] S306, importing the reporting instance into the scheduling application, and parsing the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed.

[0100] S307, executing the target code by scheduling the application to execute the reporting instance to process the target reporting event.

[0101] For the relevant contents of steps S305-S307, please refer to the above embodiment and will not be repeated here.

[0102] In summary, according to the data reporting method provided by the embodiment of the present disclosure, in response to the type of the orchestration operation being a second input operation for an orchestration requirement, the orchestration requirement of the candidate workflow input by the second input operation is obtained, the orchestration requirement is input into the target model, the target model outputs the text description information of the candidate workflow, and the reporting action included in the candidate workflow is determined from the text description information. Thus, the orchestration requirement of the reporting workflow input by the user can be input into the target model, the orchestration requirement is processed by the target model, and the text description information of the reporting workflow is obtained to determine the reporting action included in the reporting workflow, so that the user only needs to input the orchestration requirement of the reporting workflow, and does not need to orchestrate the reporting action, and the automatic orchestration of the reporting workflow is realized through the target model, which simplifies the user operation, reduces the difficulty of the orchestration of the reporting workflow, and improves the orchestration efficiency of the reporting workflow.

[0103] Figure 4 It is a flowchart of a data reporting method according to the fourth embodiment of the present disclosure.

[0104] like Figure 4 As shown, the data reporting method of the fourth embodiment of the present disclosure includes the following steps:

[0105] S401, abstracting the reporting action to obtain a candidate code, and binding the reporting action to the candidate code.

[0106] S402: In response to detecting an orchestration operation for a candidate workflow, and in response to the type of the orchestration operation being a second input operation for an orchestration requirement, obtaining an orchestration requirement for the candidate workflow input by the second input operation.

[0107] For the relevant contents of steps S401 - S402 , please refer to the above embodiment and will not be described again here.

[0108] S403, based on the orchestration requirements, the orchestration knowledge base and the orchestration rule base, determining the reporting actions included in the candidate workflow to generate the candidate workflow, and adding the candidate workflow to the workflow library.

[0109] It should be noted that the orchestration knowledge base includes multiple orchestration knowledge of reporting workflows, and the orchestration rule base includes multiple orchestration rules of reporting workflows. There are no excessive restrictions on orchestration knowledge, such as modularization (i.e., decomposing workflows into multiple independent modules), reusability (each module can be reused by multiple workflows), dependencies between reporting actions, conditional branches (such as conditional judgment, branch merging), exception handling, etc. There are no excessive restrictions on orchestration rules, such as standardization (such as adopting unified naming standards and coding standards), scalability (such as designing a plug-in architecture and using configuration files to manage parameters), security (such as data encryption, identity authentication, and permission management), etc.

[0110] In one embodiment, based on the orchestration requirements, the orchestration knowledge base and the orchestration rule base, determining the reporting actions included in the candidate workflow includes obtaining the orchestration knowledge matching the orchestration requirements from the orchestration knowledge base, obtaining the orchestration rules matching the orchestration requirements from the orchestration rule base, and determining the reporting actions included in the candidate workflow based on the matching orchestration knowledge and the matching orchestration rules. Thus, the reporting actions included in the reporting workflow can be determined by taking into account the orchestration knowledge and the orchestration rules matching the orchestration requirements of the reporting workflow, and automatic orchestration of the reporting actions can be achieved.

[0111] In some examples, the method further includes obtaining a first correlation parameter between the orchestration requirement and the orchestration knowledge, and obtaining, based on the first correlation parameter, orchestration knowledge matching the orchestration requirement from a orchestration knowledge base.

[0112] Exemplarily, based on the first correlation parameter, obtaining orchestration knowledge that matches the orchestration requirement from the orchestration knowledge base includes sorting multiple orchestration knowledge from large to small according to the first correlation parameter, taking the first Q orchestration knowledge as the matching orchestration knowledge, where Q is a positive integer, and / or taking the orchestration knowledge corresponding to the first correlation parameter greater than a set threshold as the matching orchestration knowledge.

[0113] In some examples, the method further includes obtaining a second correlation parameter between the orchestration requirement and the orchestration rule, and obtaining an orchestration rule that matches the orchestration requirement from an orchestration rule library based on the second correlation parameter.

[0114] Exemplarily, based on the second correlation parameter, obtaining an orchestration rule that matches the orchestration requirement from an orchestration rule library includes sorting multiple orchestration rules from large to small according to the second correlation parameter, taking the first Q orchestration rules as the matching orchestration rules, where Q is a positive integer, and / or taking the orchestration rule corresponding to the second correlation parameter greater than a set threshold as the matching orchestration rule.

[0115] It should be noted that the first correlation parameter is used to characterize the correlation (also called correlation relationship) between the orchestration requirement and the orchestration knowledge, and the second correlation parameter is used to characterize the correlation between the orchestration requirement and the orchestration rule. The correlation may include the degree of correlation, positive correlation, negative correlation, no correlation, etc. There are no excessive restrictions on the correlation parameters, for example, they may include the F value of linear regression, correlation coefficient, nonlinear correlation coefficient, complex correlation coefficient, etc. The relevant content of the correlation parameter can be obtained by using any correlation analysis method in the relevant technology, and no excessive restrictions are made here.

[0116] S404, determining a target workflow of a target reporting event from a workflow library, and configuring the target workflow based on configuration information of the target reporting event to generate a reporting instance of the target reporting event.

[0117] S405, importing the reporting instance into the scheduling application, and parsing the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed.

[0118] S406, executing the target code by scheduling the application to execute the reporting instance to process the target reporting event.

[0119] For the relevant contents of steps S404-S406, please refer to the above embodiment and will not be repeated here.

[0120] In summary, according to the data reporting method provided by the embodiment of the present disclosure, in response to the type of the orchestration operation being the second input operation for the orchestration requirement, the orchestration requirement of the candidate workflow entered by the second input operation is obtained, and based on the orchestration requirement, the orchestration knowledge base and the orchestration rule base, the reporting action included in the candidate workflow is determined. Thus, the orchestration requirement, the orchestration knowledge base and the orchestration rule base of the reporting workflow entered by the user can be comprehensively considered to determine the reporting action included in the reporting workflow, so that the user only needs to enter the orchestration requirement of the reporting workflow, and does not need to arrange the reporting action, which simplifies the user operation, reduces the difficulty of the reporting workflow, and improves the efficiency of the reporting workflow.

[0121] On the basis of any of the above embodiments, the method further includes obtaining a sample workflow, a sample orchestration requirement of the sample workflow, and sample execution information of a sample reporting instance corresponding to the sample workflow, and training the target model based on the sample workflow, the sample orchestration requirement, and the sample execution information, and / or updating the orchestration knowledge base and the orchestration rule base. Thus, during the training process, the target model can learn the relationship between the sample orchestration requirement, the sample workflow, and the sample execution information, so that the trained target model can obtain the text description information of the reporting workflow based on the orchestration requirement of the reporting workflow. In addition, the orchestration knowledge base and the orchestration rule base can be updated based on the sample workflow, the sample orchestration requirement, and the sample execution information, thereby improving the accuracy of the orchestration knowledge base and the orchestration rule base.

[0122] It should be noted that there are not too many restrictions on the execution information. For example, it may include the execution result of the candidate code bound to the reporting action contained in the sample instance (such as successful execution, failed execution), the processing status of the sample reporting event corresponding to the sample instance (such as unprocessed, processing, processing completed) and the processing result (such as successful processing, failed processing), etc.

[0123] It should be noted that the target model can be trained based on the sample workflow, sample orchestration requirements and sample execution information, and any model training method in the relevant technology can be used to achieve this, and no excessive restrictions are made here.

[0124] Exemplarily, based on the sample workflow, sample arrangement requirements and sample execution information, the target model is trained, including determining the label of the sample workflow based on the sample execution information, wherein the label includes a positive sample or a negative sample, inputting the sample arrangement requirements into the target model, and the target model outputs the predicted text description information of the sample workflow, and based on the predicted text description information, the actual text description information of the sample workflow, and the label of the sample workflow, the loss function of the target model is obtained, and the target model is trained based on the loss function. It should be noted that the loss function is not too limited, for example, it can include CE (Cross Entropy), MSE (Mean-Square Error), KL (Kullback-Leibler) divergence, contrast loss function, etc.

[0125] Exemplarily, determining the label of the sample workflow based on the sample execution information includes determining that the label of the sample workflow is a positive sample in response to the sample execution information indicating that the sample reporting event corresponding to the sample workflow is successfully processed, and determining that the label of the sample workflow is a negative sample in response to the sample execution information indicating that the sample reporting event corresponding to the sample workflow is failed to be processed.

[0126] On the basis of any of the above embodiments, the method further includes, in response to the consistency of the target workflows of the M target reporting events and the consistency of the reporting contents of the M target reporting events, dividing the reporting agencies bound to the M target reporting events into the same reporting group, wherein M is a positive integer greater than 1, and generating statistical reports based on the execution information of the reporting instances of the multiple reporting agencies in the same reporting group. Thus, when the target workflows and reporting contents of the multiple reporting events are consistent, the reporting agencies bound to the multiple reporting events can be divided into the same reporting group, and the statistical reports can be generated taking into account the execution information of the reporting instances of the multiple reporting agencies in the same reporting group, so as to realize the coordinated statistics of the execution information of the reporting instances of different reporting agencies, and improve the statistical efficiency of the execution information of the reporting instances.

[0127] It is understandable that different reporting events may be bound to different reporting agencies.

[0128] Figure 5 4 is a block diagram of a data reporting device according to the first embodiment of the present disclosure.

[0129] like Figure 5 As shown, the data reporting device 100 of the embodiment of the present disclosure includes: an abstract module 110 , an orchestration module 120 , a configuration module 130 , a parsing module 140 and an execution module 150 .

[0130] The abstraction module 110 is configured to abstract the reporting action, obtain a candidate code, and bind the reporting action with the candidate code;

[0131] The orchestration module 120 is configured to, in response to detecting an orchestration operation for a candidate workflow, determine a reporting action included in the candidate workflow based on a type of the orchestration operation and operation information of the orchestration operation to generate the candidate workflow, and add the candidate workflow to a workflow library;

[0132] The configuration module 130 is configured to determine a target workflow of a target reporting event from the workflow library, and configure the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event;

[0133] The parsing module 140 is configured to import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed;

[0134] The execution module 150 is configured to execute the target code through the scheduling application to execute the reporting instance to process the target reporting event.

[0135] In one embodiment of the present disclosure, the orchestration module 120 is further configured to: during the orchestration process of the candidate workflow, control the display of multiple candidate selection items on the interactive page, wherein the candidate selection items are used to represent the submission action; in response to the type of the orchestration operation being a selection operation, use the candidate selection item selected by the selection operation as the target selection item; and add the submission action corresponding to the target selection item to the submission actions included in the candidate workflow.

[0136] In one embodiment of the present disclosure, the orchestration module 120 is further configured to: in response to the type of the orchestration operation being a first entry operation for a reporting action, obtain the reporting action entered by the first entry operation; and add the entered reporting action to the reporting actions included in the candidate workflow.

[0137] In one embodiment of the present disclosure, the orchestration module 120 is further configured to: abstract the entered reporting action to obtain a newly added candidate code, and bind the entered reporting action with the newly added candidate code; and / or obtain the candidate code entered by the first entry operation, and bind the entered reporting action with the entered candidate code.

[0138] In one embodiment of the present disclosure, the orchestration module 120 is further configured to: in response to a second input operation in which the type of the orchestration operation is for an orchestration requirement, obtain the orchestration requirement of the candidate workflow entered by the second input operation; input the orchestration requirement into a target model, and output text description information of the candidate workflow by the target model; and determine the reporting action included in the candidate workflow from the text description information.

[0139] In one embodiment of the present disclosure, the orchestration module 120 is further configured to: in response to a second entry operation in which the type of the orchestration operation is for an orchestration requirement, obtain the orchestration requirement of the candidate workflow entered by the second entry operation; and determine the reporting action included in the candidate workflow based on the orchestration requirement, an orchestration knowledge base, and an orchestration rule base.

[0140] In one embodiment of the present disclosure, the orchestration module 120 is further configured to: obtain orchestration knowledge matching the orchestration requirement from the orchestration knowledge base; obtain orchestration rules matching the orchestration requirement from the orchestration rule base; and determine the reporting action included in the candidate workflow based on the matched orchestration knowledge and the matched orchestration rules.

[0141] In one embodiment of the present disclosure, the orchestration module 120 is further configured to: obtain a sample workflow, a sample orchestration requirement of the sample workflow, and sample execution information of a sample reporting instance corresponding to the sample workflow; train a target model based on the sample workflow, the sample orchestration requirement, and the sample execution information, and / or update an orchestration knowledge base and an orchestration rule base.

[0142] In one embodiment of the present disclosure, the configuration module 130 is further configured to: identify whether there is overlapping information between the configuration information of each of the N target reporting events, where N is a positive integer greater than 1; in response to the existence of overlapping information between the configuration information of each of the N target reporting events, batch configure the target workflows of each of the N target reporting events based on the overlapping information, and generate reporting instances for each of the N target reporting events.

[0143] In one embodiment of the present disclosure, the device 100 also includes: a statistical module, configured to: in response to the target workflows of the M target reporting events being consistent and the reporting contents of the M target reporting events being consistent, divide the reporting agencies bound to the M target reporting events into the same reporting group, wherein M is a positive integer greater than 1; and generate statistical reports based on the execution information of the reporting instances of the multiple reporting agencies in the same reporting group.

[0144] In one embodiment of the present disclosure, the configuration module 130 is further configured to: obtain a target reporting scenario of the target reporting event and a candidate reporting scenario of each of a plurality of candidate workflows in the workflow library; obtain a similarity between the target reporting scenario and the candidate reporting scenarios; and determine the target workflow from the workflow library based on the similarity.

[0145] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0146] In summary, the data reporting device provided by the embodiment of the present disclosure abstracts the reporting action to obtain the candidate code, and binds the reporting action to the candidate code, so that the user does not need to write the reporting code when arranging the reporting workflow, which simplifies the user operation, reduces the difficulty of arranging the reporting workflow, and improves the arranging efficiency of the reporting workflow. In addition, the reporting action included in the candidate workflow can be determined by considering the type of the orchestration operation and the operation information of the orchestration operation to generate the candidate workflow, and the candidate workflow is added to the workflow library, so that the automatic generation of the reporting workflow can be realized. In addition, the target workflow of the target reporting event is determined from the workflow library, and the configuration information of the target reporting event is taken into consideration to automatically configure the target workflow and generate a reporting instance of the target reporting event. This can realize the automatic generation of the reporting instance, import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed. The target code is executed through the scheduling application to execute the reporting instance, which can realize the automation of data reporting and improve the efficiency of data reporting.

[0147] Figure 6 It is a block diagram of an electronic device according to an exemplary embodiment.

[0148] like Figure 6 As shown, the electronic device 200 includes:

[0149] The memory 210 and the processor 220, a bus 230 connecting different components (including the memory 210 and the processor 220), the memory 210 stores a computer program, and when the processor 220 executes the program, the data reporting method described in the embodiment of the present disclosure is implemented.

[0150] Bus 230 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0151] The electronic device 200 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 200, including volatile and non-volatile media, removable and non-removable media.

[0152] The memory 210 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 240 and / or cache memory 250. The electronic device 200 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 260 may be used to read and write non-removable, non-volatile magnetic media ( Figure 6 not shown, usually called a "hard drive"). Although Figure 6 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 230 via one or more data medium interfaces. The memory 210 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0153] A program / utility 280 having a set (at least one) of program modules 270 may be stored, for example, in the memory 210, such program modules 270 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 270 generally perform the functions and / or methods of the embodiments described in the present disclosure.

[0154] The electronic device 200 may also communicate with one or more external devices 290 (e.g., keyboards, pointing devices, displays 291, etc.), one or more devices that enable a user to interact with the electronic device 200, and / or any device that enables the electronic device 200 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed through an input / output (I / O) interface 292. Furthermore, the electronic device 200 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) through a network adapter 293. Figure 6 As shown, the network adapter 293 communicates with other modules of the electronic device 200 via the bus 230. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0155] The processor 220 executes various functional applications and data processing by running the programs stored in the memory 210 .

[0156] It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of the data reporting method of the embodiment of the present disclosure, and will not be repeated here.

[0157] In summary, the electronic device provided by the embodiment of the present disclosure can execute the data reporting method as described above, abstract the reporting action, obtain the candidate code, and bind the reporting action to the candidate code, so that the user does not need to write the reporting code when arranging the reporting workflow, which simplifies the user operation, reduces the difficulty of arranging the reporting workflow, and improves the arranging efficiency of the reporting workflow. In addition, the type of the arranging operation and the operation information of the arranging operation can be considered to determine the reporting action included in the candidate workflow to generate the candidate workflow, and the candidate workflow is added to the workflow library, so that the reporting workflow can be realized. Automatic generation of flow. In addition, the target workflow of the target reporting event is determined from the workflow library, and the configuration information of the target reporting event is taken into consideration to automatically configure the target workflow and generate a reporting instance of the target reporting event. The reporting instance can be automatically generated, and the reporting instance is imported into the scheduling application. The reporting instance is parsed through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance as the target code to be executed. The target code is executed through the scheduling application to execute the reporting instance, which can realize the automation of data reporting and improve the efficiency of data reporting.

[0158] In order to implement the above embodiments, the present disclosure also proposes a computer-readable storage medium.

[0159] When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device can perform the above-mentioned, or perform the above-mentioned data reporting method. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0160] In order to implement the above embodiments, the present disclosure further provides a computer program product, including a computer program, characterized in that when the computer program is executed by a processor, the data reporting method as described above is implemented.

[0161] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0162] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A data reporting method, characterized in that: include: Abstracting the reporting action to obtain a candidate code, and binding the reporting action to the candidate code; In response to detecting an orchestration operation for a candidate workflow, determining a reporting action included in the candidate workflow based on a type of the orchestration operation and operation information of the orchestration operation to generate the candidate workflow, and adding the candidate workflow to a workflow library; Determine a target workflow of a target reporting event from the workflow library, and configure the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event; Importing the reporting instance into the scheduling application, and parsing the reporting instance through the scheduling application to obtain candidate codes bound to the reporting actions contained in the reporting instance as target codes to be executed; The target code is executed by the scheduling application to execute the reporting instance to process the target reporting event.

2. The method according to claim 1, characterized in that The method further comprises: In the process of arranging the candidate workflow, controlling to display a plurality of candidate selection items on the interactive page, wherein the candidate selection items are used to represent the reporting action; The determining, based on the type of the orchestration operation and the operation information of the orchestration operation, the reporting action included in the candidate workflow includes: In response to the type of the arrangement operation being a selection operation, taking the candidate selection item selected by the selection operation as a target selection item; The reporting action corresponding to the target selection item is added to the reporting actions included in the candidate workflow.

3. The method according to claim 1, characterized in that The determining, based on the type of the orchestration operation and the operation information of the orchestration operation, the reporting action included in the candidate workflow includes: In response to the type of the arrangement operation being a first input operation for a reporting action, obtaining the reporting action input by the first input operation; The entered reporting action is added to the reporting actions included in the candidate workflow.

4. The method according to claim 3, characterized in that: The method further comprises: Abstracting the inputted submission action to obtain a newly added candidate code, and binding the inputted submission action with the newly added candidate code; and / or, The candidate code entered by the first entry operation is obtained, and the entered reporting action is bound to the entered candidate code.

5. The method according to claim 1, characterized in that The determining, based on the type of the orchestration operation and the operation information of the orchestration operation, the reporting action included in the candidate workflow includes: In response to the type of the orchestration operation being a second input operation for an orchestration requirement, obtaining the orchestration requirement of the candidate workflow input by the second input operation; Inputting the arrangement requirement into a target model, and outputting text description information of the candidate workflow by the target model; The reporting actions included in the candidate workflow are determined from the text description information.

6. The method according to claim 1, characterized in that The determining, based on the type of the orchestration operation and the operation information of the orchestration operation, the reporting action included in the candidate workflow includes: In response to the type of the orchestration operation being a second input operation for an orchestration requirement, obtaining the orchestration requirement of the candidate workflow input by the second input operation; Based on the orchestration requirement, the orchestration knowledge base and the orchestration rule base, a reporting action included in the candidate workflow is determined.

7. The method according to claim 6, characterized in that The determining, based on the orchestration requirement, the orchestration knowledge base, and the orchestration rule base, the reporting action included in the candidate workflow includes: Acquire the orchestration knowledge matching the orchestration requirement from the orchestration knowledge base; Acquire an orchestration rule matching the orchestration requirement from the orchestration rule library; Based on the matched orchestration knowledge and the matched orchestration rule, a reporting action included in the candidate workflow is determined.

8. The method according to any one of claims 5 to 7, characterized in that: The method further comprises: Acquire a sample workflow, a sample arrangement requirement of the sample workflow, and sample execution information of a sample reporting instance corresponding to the sample workflow; Based on the sample workflow, the sample orchestration requirement and the sample execution information, a target model is trained, and / or an orchestration knowledge base and an orchestration rule base are updated.

9. The method according to any one of claims 1 to 7, characterized in that: The configuring the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event includes: Identify whether there is overlapping information between the configuration information of the N target reporting events, where N is a positive integer greater than 1; In response to overlapping information between the configuration information of the N target reporting events, the target workflows of the N target reporting events are batch configured based on the overlapping information to generate reporting instances of the N target reporting events.

10. The method according to any one of claims 1 to 7, characterized in that The method further comprises: In response to the M target reporting events having consistent target workflows and consistent reporting contents, the reporting agencies bound to the M target reporting events are divided into the same reporting group, where M is a positive integer greater than 1; Generate statistical reports based on the execution information of the reporting instances of multiple reporting agencies within the same reporting group.

11. The method according to any one of claims 1 to 7, characterized in that: The step of determining a target workflow of a target reporting event from the workflow library includes: Acquire a target reporting scenario of the target reporting event and candidate reporting scenarios of each of a plurality of candidate workflows in the workflow library; Obtaining the similarity between the target reporting scenario and the candidate reporting scenario; Based on the similarity, the target workflow is determined from the workflow library.

12. A data reporting device, characterized in that: include: An abstraction module is configured to abstract the reporting action, obtain a candidate code, and bind the reporting action to the candidate code; an orchestration module configured to, in response to detecting an orchestration operation for a candidate workflow, determine a reporting action included in the candidate workflow based on a type of the orchestration operation and operation information of the orchestration operation to generate the candidate workflow, and add the candidate workflow to a workflow library; A configuration module, configured to determine a target workflow of a target reporting event from the workflow library, and configure the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event; A parsing module is configured to import the reporting instance into a scheduling application, and parse the reporting instance through the scheduling application to obtain candidate codes bound to the reporting actions contained in the reporting instance as target codes to be executed; The execution module is configured to execute the target code through the scheduling application to execute the reporting instance to process the target reporting event.

13. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instruction to implement the data reporting method as described in any one of claims 1-11.

14. A computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the data reporting method according to any one of claims 1 to 11.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the data reporting method according to any one of claims 1 to 11 is implemented.

Images