Task generation method and device, equipment, medium and program product

Abstract

The invention provides a task generation method which can be applied to the technical field of cloud computing. The method comprises the steps that a received task generation request is responded, a task date information table is determined according to a request date in the task generation request, and the task date information table comprises a plurality of dates for task execution of a task execution object; matching the obtained task generation periods of the plurality of task execution objects with a task date information table to determine a target execution object matched with the request date from the plurality of task execution objects; determining a data filling deadline of the data item according to the request date and a preset filling duration of the data item in the target execution object, so as to generate a to-be-filled data item according to the data filling deadline; and marking the to-be-filled data item by using the data collection frequency corresponding to the target execution object to generate a target execution task. The invention further provides a task generation device and equipment, a storage medium and a program product.

Description

Technical Field

[0001] The present disclosure relates to the field of cloud computing, and in particular to a task generation method, apparatus, device, medium and program product. Background Art

[0002] At present, in enterprise operation scenarios, it is necessary to periodically collect and process various indicator data, such as the regular collection of attendance data and project operation data. In the process of data collection, it is necessary to send corresponding data collection monitoring tasks to relevant departments. In related technologies, data items in the monitoring tasks are configured one by one according to department indicators to generate monitoring tasks, and the generated monitoring tasks are sent to the corresponding departments for processing.

[0003] In the process of realizing the concept of the present disclosure, the inventors found that there are at least the following problems in the related technology: since there are multiple indicators in a department, each time a monitoring task is generated, the data items in each indicator need to be configured one by one, the amount of data to be processed is large, and the configuration efficiency is low, resulting in low task generation efficiency. Summary of the invention

[0004] In view of the above problems, the present disclosure provides a task generation method, apparatus, device, medium and program product.

[0005] According to a first aspect of the present disclosure, a task generation method is provided, comprising: in response to a received task generation request, determining a task date information table according to a request date in the task generation request, wherein the task date information table includes multiple dates for the task execution object to execute the task; matching the task generation cycles of the multiple task execution objects obtained with the task date information table, so as to determine a target execution object matching the request date from the multiple task execution objects, wherein the task generation cycle includes a preset cycle variable associated with the date; determining a data reporting period for the data item according to the request date and a preset reporting period of the data item in the target execution object, so as to generate a data item to be reported according to the data reporting period; marking the data item to be reported using a data collection frequency corresponding to the target execution object, and generating a target execution task. .

[0006] According to an embodiment of the present disclosure, the task generation cycles of the multiple task execution objects acquired are matched with the task date information table to determine the target execution object matching the request date from the multiple task execution objects, including: determining the starting date corresponding to the starting point of the period in the task generation cycle in the task date information table; subtracting and summing the starting date with the preset period variable respectively to determine the first initiation date and the second initiation date in the task date information table; comparing the first initiation date and the second initiation date of each task execution object with the request date respectively to generate a comparison result; in the case where the comparison result indicates that the first initiation date or the second initiation date of the task execution object is the request date, the task execution object is determined as the target execution object.

[0007] According to an embodiment of the present disclosure, the above-mentioned starting date is subtracted and summed respectively with the above-mentioned preset periodic variable to determine the first initiation date and the second initiation date in the above-mentioned task date information table, including: when it is determined that the attribute information of the above-mentioned preset periodic variable is a natural duration, the dates obtained by subtracting and summing the above-mentioned starting date and the above-mentioned preset periodic variable in the above-mentioned task date information table are determined as the above-mentioned first initiation date and the above-mentioned second initiation date; when it is determined that the attribute information of the above-mentioned preset periodic variable is a task execution duration, multiple task execution dates are determined in the above-mentioned task date information table to generate an execution date information table; in the above-mentioned execution date information table, the above-mentioned starting date is subtracted and summed with the above-mentioned preset periodic variable to determine the above-mentioned first initiation date and the above-mentioned second initiation date.

[0008] According to an embodiment of the present disclosure, the data reporting deadline of the above-mentioned data item is determined based on the above-mentioned request date and the preset reporting duration of the data item in the above-mentioned target execution object, including: when it is determined that the attribute information of the above-mentioned preset reporting duration is the above-mentioned natural duration, the above-mentioned request date is summed with the above-mentioned preset reporting duration to obtain the data reporting deadline of the above-mentioned data item; when it is determined that the attribute information of the above-mentioned preset reporting duration is the above-mentioned task execution duration, the above-mentioned request date and the above-mentioned preset reporting duration are summed in the above-mentioned execution date information table to determine the data reporting deadline of the above-mentioned data item.

[0009] According to an embodiment of the present disclosure, the method further includes: sending the target execution task to the target execution object according to the data collection frequency, so as to obtain the data returned by the target execution object corresponding to the data item to be reported.

[0010] According to an embodiment of the present disclosure, the above method also includes: when it is determined that the above data collection frequency is greater than the monthly collection frequency, traversing each of the above data items of the above target execution object to determine the collection attribute of each of the above data items; when the above collection attribute is a cumulative attribute, determining the data corresponding to the above data item to be reported based on the historical data returned by the above target execution object; when the above collection attribute is an update attribute, sending the data item to be reported with the above update attribute to the above target execution object to obtain the data corresponding to the above data item to be reported returned by the above target execution object.

[0011] According to an embodiment of the present disclosure, the task date information table is determined based on the request date in the task generation request, including: determining multiple target months associated with the request month in the request date, wherein the target months include a first month that is earlier than a preset time period of the request month, and a second month that is later than a preset time period of the request month; concatenating the date information tables of the first month, the second month and the request month to obtain the task date information table, wherein the task date information table includes multiple starting dates corresponding to the starting points of the cycles in the task generation cycle.

[0012] The second aspect of the present disclosure provides a task generation device, including: an information determination module, for responding to a received task generation request, and determining a task date information table according to a request date in the task generation request, wherein the task date information table includes multiple dates for the task execution object to execute the task; a cycle matching module, for matching the acquired task generation cycles of the multiple task execution objects with the task date information table, so as to determine a target execution object matching the request date from the multiple task execution objects, wherein the task generation cycle includes a preset cycle variable associated with the date; a deadline determination module, for determining a data reporting deadline for the data item according to the request date and a preset reporting duration of the data item in the target execution object, so as to generate a data item to be reported according to the data reporting deadline; a frequency marking module, for marking the data item to be reported using the data collection frequency corresponding to the target execution object, and generating a target execution task.

[0013] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0014] The fourth aspect of the present disclosure further provides a computer-readable storage medium having a computer program or instructions stored thereon, which implements the steps of the above method when the above computer program or instructions are executed by a processor.

[0015] The fifth aspect of the present disclosure further provides a computer program product, including a computer program or instructions, which implement the steps of the above method when the above computer program or instructions are executed by a processor.

[0016] According to an embodiment of the present disclosure, a task for data collection is automatically generated based on a received task generation request. In the process of generating tasks, the generated tasks are made highly executable by matching the task generation cycle with the task date information table. Data items to be reported are generated based on the data reporting period of the data items, and the data items to be reported are marked using the data collection frequency, so that the target execution object can process the generated target execution tasks. By automatically generating a target execution task for data collection based on the configured task generation cycle and the preset reporting duration, the problem of having to configure the data items each time data collection is performed is at least partially overcome, and the task generation efficiency is effectively improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0018] Figure 1 The application scenario diagram of the task generation method, apparatus, device, medium and program product according to the embodiment of the present disclosure is schematically shown;

[0019] Figure 2 A flowchart of a task generation method according to an embodiment of the present disclosure is schematically shown;

[0020] Figure 3 A schematic diagram schematically shows the matching of a task generation cycle and a task date information table according to an embodiment of the present disclosure;

[0021] Figure 4 A schematic diagram schematically shows a scenario of task delivery according to an embodiment of the present disclosure;

[0022] Figure 5 A flowchart of a task generation method according to another embodiment of the present disclosure is schematically shown;

[0023] Figure 6 A structural block diagram of a task generation device according to an embodiment of the present disclosure is schematically shown; and

[0024] Figure 7 A block diagram of an electronic device suitable for implementing a task generation method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0025] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0026] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "include", "comprising", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0027] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0028] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0029] It should be noted that in the embodiments of the present application, 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 application, but it does not mean that the applicant has or will necessarily use the solution.

[0030] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0031] Indicator management includes indicator management and data item management. An indicator contains multiple data items. The indicator has a calculation formula for these data items and specifies different risk areas for the calculation results. Each indicator has a defined data collection frequency (monthly, quarterly, half-yearly, annual) and reporting department. Monitoring tasks need to be sent to the reporting department regularly based on the collection frequency. The reporting department reports the data of each data item, and the system calculates the indicator results based on the collected data.

[0032] Every month, the staff of each department needs to manually initiate monitoring tasks. Since there are many indicators, the monitoring cycle of each indicator is different (monthly, quarterly, semi-annual, and annual), and the indicators initiated each time are different, it is easy to miss or send the wrong indicators when initiating. In addition, the reporting period for each indicator is also different. When initiating a monitoring task, it needs to be filled in manually, and it has to be manually checked every time it is initiated, which is easy to make mistakes. The labor cost of manually initiating monitoring tasks is high. Since each institution has its own indicators to initiate, they must be handled by a dedicated person. There are many indicators, and they must be initiated one by one, which is inefficient.

[0033] An embodiment of the present disclosure provides a task generation method, the method comprising: in response to a received task generation request, determining a task date information table according to a request date in the task generation request, wherein the task date information table includes multiple dates for the task execution object to execute the task; matching the task generation cycles of the acquired multiple task execution objects with the task date information table to determine a target execution object that matches the request date from the multiple task execution objects, wherein the task generation cycle includes a preset cycle variable associated with the date; determining a data reporting deadline for the data item according to the request date and a preset reporting duration of the data item in the target execution object, to generate a data item to be reported according to the data reporting deadline; marking the data item to be reported using the data collection frequency corresponding to the target execution object, and generating a target execution task.

[0034] Figure 1 The application scenario diagram of the task generation method, apparatus, device, medium and program product according to the embodiments of the present disclosure is schematically shown.

[0035] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104 and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0036] The user can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0037] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0038] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0039] It should be noted that the task generation method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the task generation device provided in the embodiment of the present disclosure can generally be set in the server 105. The task generation method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105. Accordingly, the task generation device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105.

[0040] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0041] The following will be based on Figure 1 The scene described by Figure 2~Figure 6 The task generation method of the disclosed embodiment is described in detail.

[0042] Figure 2 The flowchart of the task generation method according to the embodiment of the present disclosure is schematically shown.

[0043] like Figure 2 As shown, the task generation method of this embodiment includes operations S210 to S240.

[0044] In operation S210 , in response to the received task generation request, a task date information table is determined according to a request date in the task generation request, wherein the task date information table includes a plurality of dates on which the task execution object executes the task.

[0045] In operation S220, the acquired task generation cycles of the plurality of task execution objects are matched with the task date information table to determine a target execution object matching the request date from the plurality of task execution objects, wherein the task generation cycle includes a preset cycle variable associated with the date.

[0046] In operation S230, a data reporting deadline for the data item is determined according to the request date and a preset reporting duration of the data item in the target execution object, so as to generate a data item to be reported according to the data reporting deadline.

[0047] In operation S240, the data items to be reported are marked using the data collection frequency corresponding to the target execution object, and a target execution task is generated.

[0048] According to the embodiments of the present disclosure, in many scenarios, it is often necessary to periodically collect and process indicator data. Among them, one indicator includes multiple data items, and each indicator is defined with a corresponding reporting department, that is, a task execution object. In the process of data collection, it is necessary to regularly send the task of collecting indicator data to the task execution object according to the frequency of data collection, and the task execution object reports the data of each data item.

[0049] According to an embodiment of the present disclosure, in response to a received task generation request, a request date in the task generation request is determined, wherein the request date includes information such as year, month, and day. A task date information table is determined based on the request date, wherein the task date information table includes multiple dates when the task execution object executes the task, and may also include multiple dates when the task execution object does not execute the task.

[0050] According to an embodiment of the present disclosure, the task generation cycle of each task execution object that has been configured is obtained. The task generation cycle can be configured according to the importance of the indicator. A shorter cycle is configured for important indicators, and a longer cycle is configured for unimportant indicators. The task generation cycles of multiple task execution objects are matched with the task date information table respectively to determine the target execution object that matches the request date. Among them, the target execution object is an execution object that can generate a task on the request date.

[0051] According to an embodiment of the present disclosure, the preset reporting time configured for each data item in the indicator is obtained, and the data reporting period is calculated according to the request date and the preset reporting time. After the calculation is completed, each data item is marked according to the mapping relationship between the data reporting period and the data item, and a plurality of data items to be reported are obtained. Among them, the data items to be reported can be presented in a table.

[0052] According to the embodiments of the present disclosure, the data collection frequency (monthly, quarterly, half-year, annual) of the target execution object is determined, and the data items to be reported are marked using the data collection frequency to obtain multiple data collection items. For example: data items with data collection frequencies such as June of ××××, the second quarter of ××××, and the first half of ××××. Aggregate multiple data collection items to generate a target execution task. The target execution task includes the name of the target execution object, that is, the department name, and the name of the indicator corresponding to the target execution object.

[0053] According to an embodiment of the present disclosure, a task for data collection is automatically generated based on a received task generation request. In the process of generating tasks, the generated tasks are made highly executable by matching the task generation cycle with the task date information table. Data items to be reported are generated based on the data reporting period of the data items, and the data items to be reported are marked using the data collection frequency, so that the target execution object can process the generated target execution tasks. By automatically generating a target execution task for data collection based on the configured task generation cycle and the preset reporting duration, the problem of having to configure the data items each time data collection is performed is at least partially overcome, and the task generation efficiency is effectively improved.

[0054] According to an embodiment of the present disclosure, the task generation cycles of the acquired multiple task execution objects are matched with the task date information table to determine the target execution object that matches the request date from the multiple task execution objects, including: determining the starting date corresponding to the starting point of the period in the task generation cycle in the task date information table; subtracting and summing the starting date with the preset period variable respectively to determine the first initiation date and the second initiation date in the task date information table; comparing the first initiation date and the second initiation date of each task execution object with the request date respectively to generate a comparison result; when the comparison result indicates that the first initiation date or the second initiation date of the task execution object is the request date, determining the task execution object as the target execution object.

[0055] According to an embodiment of the present disclosure, the task generation cycle configured for each task execution object is obtained. Specifically, the task generation cycle is T±N natural days or working days, and the ± sign and N days need to be configured, where T corresponds to the last day of each month. N is a preset cycle variable associated with the execution date of the task.

[0056] According to an embodiment of the present disclosure, a starting date corresponding to the starting point of the cycle is determined in the task date information table according to the configured task generation cycle, that is, a date corresponding to the last day of each month T. The starting date is subtracted and summed from the preset cycle variable to obtain the first initiation date and the second initiation date.

[0057] According to an embodiment of the present disclosure, the first initiation date and the second initiation date of each task execution object are compared with the request date respectively to determine whether there is a date that is the same as the request date, so as to generate a comparison result. Specifically, the comparison result can be to compare the second initiation date and the second initiation date corresponding to each task execution with the request date by table traversal.

[0058] According to an embodiment of the present disclosure, when the comparison result indicates that the first initiation date or the second initiation date of the task execution object is the request date, the task execution object is determined as the target execution object. In another embodiment, a table including multiple task initiation cycles can be directly matched with the task date information table to query the target execution object of the review request date, and if there are multiple target execution objects, a corresponding list is generated.

[0059] According to the embodiment of the present disclosure, by matching the configured task generation cycle with the task date information table, the generated task is highly executable, and the target execution object is determined by calculating the first initiation date and the second initiation date, making the determination process more convenient.

[0060] According to an embodiment of the present disclosure, a task date information table is determined based on a request date in a task generation request, including: determining multiple target months associated with a request month in the request date, wherein the target months include a first month that is earlier than a preset time period of the request month, and a second month that is later than a preset time period of the request month; concatenating the date information tables of the first month, the second month, and the request month to obtain a task date information table, wherein the task date information table includes multiple starting dates corresponding to the starting points of the cycles in the task generation cycle.

[0061] According to an embodiment of the present disclosure, since there are multiple initiation dates in the process of configuring a task generation cycle, when determining the task date information table, all date information tables that meet the task generation cycle need to be determined to avoid omission of the initiation date.

[0062] According to the embodiment of the present disclosure, the month before the request month, that is, the first month, and the month after the request month, that is, the second month, are determined. The date information tables of the first month, the request month, and the second month are spliced ​​respectively, so that when determining the first initiation date and the second initiation date, the starting date can be determined as the last day of the first month and the last day of the request month, so that the possibility of the first initiation date and the second initiation date is maximized.

[0063] Figure 3 The diagram schematically shows the matching of the task generation cycle and the task date information table according to an embodiment of the present disclosure.

[0064] like Figure 3 As shown, the task generation cycles of multiple task execution objects 310 are matched with the task date information table 320. Specifically, the task date information table includes a date information table 321 of the first month, a date information table 322 of the request month, and a date information table 323 of the second month. The last day of the first month is taken as the starting date 330, and the first initiation date 331 and the second initiation date 332 are determined respectively.

[0065] According to an embodiment of the present disclosure, by determining multiple date information tables according to the request date and concatenating the multiple date information tables to obtain a task date information table, the judgment on whether to initiate a task currently is more accurate and the omission of periodic situations is reduced.

[0066] According to an embodiment of the present disclosure, the starting date is respectively subtracted and summed from the preset periodic variable to determine the first initiation date and the second initiation date in the task date information table, including: when it is determined that the attribute information of the preset periodic variable is a natural duration, the dates obtained by subtracting and summing the starting date from the preset periodic variable in the task date information table are determined as the first initiation date and the second initiation date; when it is determined that the attribute information of the preset periodic variable is the task execution duration, multiple task execution dates are determined in the task date information table to generate an execution date information table; in the execution date information table, the starting date is subtracted and summed from the preset periodic variable to determine the first initiation date and the second initiation date.

[0067] According to an embodiment of the present disclosure, the task generation cycle includes a preset period variable N of a natural day or a working day. Wherein, when N is a natural day, the attribute information of the preset period variable is determined to be a natural duration. When N is a working day, the attribute information of the preset period variable is determined to be the task execution duration. All configuration tasks only need to be configured once, and they will be executed according to the current configuration every subsequent month.

[0068] According to an embodiment of the present disclosure, when determining that the attribute information of the preset periodic variable is a natural duration, when determining the first initiation date and the second initiation date, the corresponding preset periodic variable can be directly shifted in the task date information table according to the calculation result to obtain the corresponding initiation date.

[0069] According to an embodiment of the present disclosure, when the attribute information of the preset periodic variable is determined to be the task execution duration, multiple task execution dates are determined in the task date information table, that is, working days are selected to obtain the execution date information table. In the selection process, the determination can be made according to the identification of each date in the task date information table.

[0070] According to an embodiment of the present disclosure, the starting date and the preset period variable are subtracted and summed in the execution date information table. When determining the first launch date and the second launch date, the corresponding preset period variable can be directly translated in the execution date information table according to the calculation result to obtain the corresponding launch date.

[0071] In another embodiment, when it is determined that the attribute information of the preset periodic variable is the task execution duration, the first initiation date and the second initiation date can be determined directly in the task date information table according to the preset periodic variable. Specifically, after determining the starting date, the task date information table is traversed from two opposite time directions respectively to determine the attribute identifier of each date. Among them, the attribute identifier includes a working day identifier and a holiday identifier. In the process of traversing the task date information table according to the preset periodic variable, if the attribute identifier of the date is determined to be a holiday identifier, the current date is determined to be invalid, and the traversal continues backward until it is determined that the initiation date whose attribute identifier is not a holiday identifier is obtained.

[0072] According to an embodiment of the present disclosure, when querying a target execution object that meets the request date, a distinction is made between working days and holidays, thereby ensuring the executability of the task finally generated, thereby avoiding the situation where the generated task cannot be processed.

[0073] According to an embodiment of the present disclosure, the data reporting deadline of the data item is determined based on the request date and the preset reporting duration of the data item in the target execution object, including: when the attribute information of the preset reporting duration is determined to be a natural duration, the request date and the preset reporting duration are summed to obtain the data reporting deadline of the data item; when the attribute information of the preset reporting duration is determined to be the task execution duration, the request date and the preset reporting duration are summed in the execution date information table to determine the data reporting deadline of the data item.

[0074] According to the embodiments of the present disclosure, the preset reporting period for each data item in the indicator is configured, specifically T+P natural days or working days, P days need to be configured, T corresponds to the initiation date of the task, and the data reporting period is used to generate the deadline of the task. All configuration tasks only need to be configured once, and will be executed according to the current configuration every month thereafter.

[0075] According to an embodiment of the present disclosure, in the data configuration stage, since two different initiation dates are configured in the task generation cycle, namely T+N and TN, the corresponding data reporting deadline also includes two corresponding deadlines, namely T+N+P and T-N+P. If it is determined that the current request date is consistent with the T+N initiation date in the task generation week, the corresponding data reporting deadline can be determined to be T+N+P. If it is determined that the current request date is consistent with the TN initiation date in the task generation week, the corresponding data reporting deadline can be determined to be T-N+P, or T-N+P can be determined as an intermediate deadline and T+N+P can be determined as the final data reporting deadline. It can be reasonably allocated according to the data collection situation of the data item or the importance of the attributes of the data item.

[0076] According to an embodiment of the present disclosure, when it is determined that the attribute information of the preset reporting duration is a natural duration, the corresponding preset reporting duration can be directly shifted from the request date in the task date information table to obtain the data reporting deadline.

[0077] According to an embodiment of the present disclosure, when the attribute information of the preset reporting time is determined to be the task execution time, the request date and the preset reporting time are summed in the execution date information table to shift the corresponding preset reporting time in the execution date information table to obtain the data reporting period.

[0078] In another embodiment, when the attribute information of the preset reporting duration is determined to be the task execution duration, the data reporting deadline can be determined in the task date information table directly according to the preset reporting duration. Specifically, after determining the request date, the task date information table is traversed. In the process of traversing the task date information table according to the preset reporting duration, if the attribute identifier of the date is determined to be a holiday identifier, the current date is determined to be invalid, and the traversal is continued backward until it is determined that the data reporting deadline whose attribute identifier is not a holiday identifier is obtained.

[0079] According to the embodiments of the present disclosure, holidays and working days are distinguished when determining the data reporting deadline, so that the data reporting deadline is more reasonable and the timeliness of task completion is ensured.

[0080] Figure 4 A schematic diagram of a scenario for issuing tasks according to an embodiment of the present disclosure is schematically shown.

[0081] According to an embodiment of the present disclosure, the method further includes: sending the target execution task to the target execution object according to the data collection frequency, so as to obtain the data returned by the target execution object and corresponding to the data item to be reported.

[0082] According to the embodiment of the present disclosure, the target execution task is sent to the target execution object according to the data collection frequency, and the target execution object collects and summarizes the data in the data items to be reported and submits them. After the submission is completed, the collected data is sent to the task-assigning department of the target execution object for review, and after the review is completed, it is saved. The system automatically calculates the indicator results and the risk area to which the indicators belong based on the results of each data item and the indicator formula.

[0083] like Figure 4 As shown, after the task generation cycle 410 and the preset reporting time 420 of each data item of the task execution object are configured, multiple user data collection tasks 430 are automatically initiated according to the configured information. The initiated tasks are sent to multiple task execution objects 440. Among them, the task execution objects may include attendance management systems, financial management systems, and project operation systems.

[0084] According to the embodiments of the present disclosure, the configuration information of the task is automatically generated according to the indicator, which facilitates the configuration of the data reporting period of each indicator. According to the task initiation cycle and the monitoring data reporting period, a data collection task that meets the conditions will be generated at a specified time every month, and the task will be sent to the corresponding task execution object, which is convenient for data collection.

[0085] According to an embodiment of the present disclosure, the method also includes: when it is determined that the data collection frequency is greater than the monthly collection frequency, traversing each data item of the target execution object to determine the collection attribute of each data item; when the collection attribute is a cumulative attribute, determining the data corresponding to the data item to be reported based on the historical data returned by the acquired target execution object; when the collection attribute is an update attribute, sending the data item to be reported with the update attribute to the target execution object to obtain the data returned by the target execution object corresponding to the data item to be reported.

[0086] According to the embodiments of the present disclosure, since the data collection frequencies include monthly, quarterly, semi-annual and annual, when quarterly collection is performed after the monthly data collection is completed, statistics can be performed on the data of multiple months, thereby reducing the interaction with the task execution objects and reducing the consumption of communication resources.

[0087] According to an embodiment of the present disclosure, when it is determined that the data collection frequency is greater than the monthly collection frequency, each data item of the target execution object is traversed to determine the collection attribute of each data item. For data items whose collection attributes are cumulative attributes, data collection can be performed using a multi-monthly statistical method. However, for data items whose collection attributes are update attributes, it is necessary to initiate a task to the task execution object to collect the latest data.

[0088] According to the embodiments of the present disclosure, since there are multiple data items in an indicator, not all collection attributes of each data item are update attributes. Therefore, in the process of generating tasks, data items to be collected can be generated for data items with update attributes only based on the collection attributes of the data items, thereby generating tasks for data collection. Targeted generation of tasks reduces the amount of data processed by the task execution object and effectively improves the user experience without repeatedly filling in duplicate data.

[0089] Figure 5 The flowchart of a task generation method according to another embodiment of the present disclosure is schematically shown.

[0090] like Figure 5 As shown, the task generation method of this embodiment includes operations S510 to S540.

[0091] In operation S510, a detection task configuration is generated, including a task initiation period and a preset reporting time of a data item.

[0092] In operation S520, the task configuration is monitored, and the task initiation date determined according to the task initiation cycle and the data reporting period of the data item generated according to the preset reporting time are configured.

[0093] In operation S530, tasks are automatically generated according to the configured task generation date and data reporting deadline, and the tasks are sent to the task execution object.

[0094] In operation S540, the data returned by the task execution object is collected, and the index formula is used to calculate the results of the audited data.

[0095] According to the embodiments of the present disclosure, all tasks are automatically initiated according to the configuration information, which reduces the situation of missed or wrong tasks. In the process of generating tasks, the indicators and data item information are automatically associated, and the indicators and data item information to be initiated and the monitoring period are automatically filled in, making the generated tasks more accurate. In the process of generating tasks, only one configuration is required, which effectively reduces labor costs and improves the efficiency of task generation.

[0096] Based on the above task generation method, the present disclosure also provides a task generation device. Figure 6 The device is described in detail.

[0097] Figure 6 The structural block diagram of the task generation device according to an embodiment of the present disclosure is schematically shown.

[0098] like Figure 6 As shown, the task generation device 600 of this embodiment includes an information determination module 610 , a cycle matching module 620 , a deadline determination module 630 and a frequency marking module 640 .

[0099] The information determination module 610 is used to respond to the received task generation request and determine a task date information table according to the request date in the task generation request, wherein the task date information table includes multiple dates for the task execution object to execute the task. In one embodiment, the information determination module 610 can be used to execute the operation S210 described above, which will not be repeated here.

[0100] The period matching module 620 is used to match the task generation period of the acquired multiple task execution objects with the task date information table to determine the target execution object that matches the request date from the multiple task execution objects, wherein the task generation period includes a preset period variable associated with the date. In one embodiment, the period matching module 620 can be used to perform the operation S220 described above, which will not be repeated here.

[0101] The deadline determination module 630 is used to determine the data reporting deadline of the data item according to the request date and the preset reporting time of the data item in the target execution object, so as to generate the data item to be reported according to the data reporting deadline. In one embodiment, the deadline determination module 630 can be used to perform the operation S230 described above, which will not be repeated here.

[0102] The frequency marking module 640 is used to mark the data items to be reported using the data collection frequency corresponding to the target execution object to generate the target execution task. In one embodiment, the frequency marking module 640 can be used to perform the operation S240 described above, which will not be repeated here.

[0103] According to an embodiment of the present disclosure, the period matching module 620 includes a starting point determination submodule, a date calculation submodule, a date comparison submodule and a target determination submodule.

[0104] The starting point determination submodule is used to determine the starting point date corresponding to the starting point of the period in the task generation cycle in the task date information table.

[0105] The date calculation submodule is used to perform subtraction and summation of the starting date and the preset period variable respectively, so as to determine the first initiation date and the second initiation date in the task date information table.

[0106] The date comparison submodule is used to compare the first initiation date and the second initiation date of each task execution object with the request date respectively to generate a comparison result.

[0107] The target determination submodule is used to determine the task execution object as the target execution object when the comparison result indicates that the first initiation date or the second initiation date of the task execution object is the request date.

[0108] According to an embodiment of the present disclosure, the date calculation submodule includes a first date calculation unit, an information determination unit and a second date calculation unit.

[0109] The first date calculation unit is used to determine the first initiation date and the second initiation date by subtracting and summing the start date and the preset period variable in the task date information table when it is determined that the attribute information of the preset period variable is a natural duration.

[0110] The information determination unit is used to determine multiple task execution dates in the task date information table and generate the execution date information table when the attribute information of the preset period variable is determined to be the task execution duration.

[0111] The second date calculation unit is used to perform subtraction and summation between the starting date and the preset period variable in the execution date information table to determine the first initiation date and the second initiation date.

[0112] According to an embodiment of the present disclosure, the deadline determination module 630 includes a first deadline determination submodule and a second deadline determination submodule.

[0113] The first deadline determination submodule is used to sum the request date and the preset reporting time period to obtain the data reporting deadline of the data item when it is determined that the attribute information of the preset reporting time period is a natural time period.

[0114] The second deadline determination submodule is used to sum the request date and the preset reporting time in the execution date information table to determine the data reporting deadline of the data item when the attribute information of the preset reporting time is determined to be the task execution time.

[0115] According to an embodiment of the present disclosure, the task generating device 600 further includes a task sending module.

[0116] The task sending module is used to send the target execution task to the target execution object according to the data collection frequency, so as to obtain the data returned by the target execution object corresponding to the data item to be reported.

[0117] According to an embodiment of the present disclosure, the task generation device 600 further includes a property determination module, a data determination module and a data acquisition module.

[0118] The attribute determination module is used to traverse each data item of the target execution object and determine the collection attribute of each data item when it is determined that the data collection frequency is greater than the monthly collection frequency.

[0119] The data determination module is used to determine the data corresponding to the data item to be reported based on the historical data returned by the acquired target execution object when the collection attribute is a cumulative attribute.

[0120] The data acquisition module is used to send the data item to be reported of the update attribute to the target execution object when the collection attribute is an update attribute, so as to obtain the data corresponding to the data item to be reported returned by the target execution object.

[0121] According to an embodiment of the present disclosure, the information determination module 610 includes a month determination submodule and an information determination submodule.

[0122] A month determination submodule, used to determine a plurality of target months associated with the request month in the request date, wherein the target months include a first month that is earlier than a preset time period of the request month, and a second month that is later than a preset time period of the request month;

[0123] The information determination submodule is used to splice the date information tables of the first month, the second month and the requested month to obtain a task date information table, wherein the task date information table includes multiple starting dates corresponding to the starting points of the cycles in the task generation cycle.

[0124] According to an embodiment of the present disclosure, any multiple modules of the information determination module 610, the period matching module 620, the deadline determination module 630 and the frequency marking module 640 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the information determination module 610, the period matching module 620, the deadline determination module 630 and the frequency marking module 640 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in a suitable combination of any of them. Alternatively, at least one of the information determination module 610, the period matching module 620, the deadline determination module 630 and the frequency marking module 640 may be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function may be performed.

[0125] Figure 7 A block diagram of an electronic device suitable for implementing a task generation method according to an embodiment of the present disclosure is schematically shown.

[0126] like Figure 7 As shown, the electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 to a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include an onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0127] In RAM 703, various programs and data required for the operation of electronic device 700 are stored. Processor 701, ROM 702 and RAM 703 are connected to each other via bus 704. Processor 701 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 702 and / or RAM 703. It should be noted that the program can also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.

[0128] According to an embodiment of the present disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to the bus 704. The electronic device 700 may further include one or more of the following components connected to the input / output (I / O) interface 705: an input portion 706 including a keyboard, a mouse, etc.; an output portion 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 708 including a hard disk, etc.; and a communication portion 709 including a network interface card such as a LAN card, a modem, etc. The communication portion 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the input / output (I / O) interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage portion 708 as needed.

[0129] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0130] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 702 and / or RAM 703 described above and / or one or more memories other than ROM 702 and RAM 703.

[0131] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the task generation method provided by the embodiment of the present disclosure.

[0132] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 701. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0133] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 709, and / or installed from the removable medium 711. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0134] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0135] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0136] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0137] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0138] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A task generation method, characterized in that: The method comprises: In response to the received task generation request, determining a task date information table according to a request date in the task generation request, wherein the task date information table includes multiple dates on which the task execution object executes the task; Matching the acquired task generation cycles of the plurality of task execution objects with the task date information table to determine a target execution object that matches the request date from the plurality of task execution objects, wherein the task generation cycle includes a preset cycle variable associated with the date; Determine the data reporting deadline of the data item according to the request date and the preset reporting duration of the data item in the target execution object, so as to generate the data item to be reported according to the data reporting deadline; The data items to be reported are marked using the data collection frequency corresponding to the target execution object to generate a target execution task.

2. The method according to claim 1, characterized in that The step of matching the acquired task generation periods of the plurality of task execution objects with the task date information table to determine a target execution object that matches the request date from the plurality of task execution objects includes: Determining in the task date information table a starting date corresponding to a period starting point in the task generation period; Subtracting and summing the starting date and the preset period variable respectively to determine a first initiation date and a second initiation date in the task date information table; Compare the first initiation date and the second initiation date of each of the task execution objects with the request date respectively to generate a comparison result; In a case where the comparison result indicates that the first initiation date or the second initiation date of the task execution object is the request date, the task execution object is determined as the target execution object.

3. The method according to claim 2, characterized in that The step of respectively subtracting and summing the starting date and the preset period variable to determine the first initiation date and the second initiation date in the task date information table includes: In the case where it is determined that the attribute information of the preset period variable is a natural duration, the dates obtained by subtracting and summing the starting date and the preset period variable in the task date information table are determined as the first initiation date and the second initiation date; In the case where the attribute information of the preset periodic variable is determined to be the task execution duration, a plurality of task execution dates are determined in the task date information table to generate an execution date information table; In the execution date information table, the starting date and the preset period variable are subtracted and summed to determine the first initiation date and the second initiation date.

4. The method according to claim 3, characterized in that: Determining the data reporting period of the data item according to the request date and the preset reporting period of the data item in the target execution object includes: In the case where it is determined that the attribute information of the preset reporting time is the natural time, the request date is summed with the preset reporting time to obtain the data reporting deadline of the data item; In the case where the attribute information of the preset reporting duration is determined to be the task execution duration, the request date and the preset reporting duration are summed in the execution date information table to determine the data reporting deadline for the data item.

5. The method according to claim 1, characterized in that The method further comprises: According to the data collection frequency, the target execution task is sent to the target execution object to obtain the data returned by the target execution object and corresponding to the data item to be reported.

6. The method according to claim 5, characterized in that The method further comprises: In the case where it is determined that the data collection frequency is greater than the monthly collection frequency, traversing each of the data items of the target execution object to determine a collection attribute of each of the data items; In the case where the collection attribute is a cumulative attribute, determining data corresponding to the data item to be reported according to the acquired historical data returned by the target execution object; In the case where the collection attribute is an update attribute, the data item to be reported of the update attribute is sent to the target execution object to obtain data returned by the target execution object and corresponding to the data item to be reported.

7. The method according to claim 1, characterized in that The step of determining the task date information table according to the request date in the task generation request includes: Determine a plurality of target months associated with the request month in the request date, wherein the target months include a first month that is earlier than the request month by a preset time period, and a second month that is later than the request month by a preset time period; The date information tables of the first month, the second month and the requested month are concatenated to obtain the task date information table, wherein the task date information table includes a plurality of starting dates corresponding to the starting points of the cycles in the task generation cycle.

8. A task generation device, characterized in that: The device comprises: An information determination module, configured to determine a task date information table in response to a received task generation request and according to a request date in the task generation request, wherein the task date information table includes a plurality of dates on which the task execution object executes the task; A cycle matching module, used for matching the acquired task generation cycles of the plurality of task execution objects with the task date information table, so as to determine a target execution object matching the request date from the plurality of task execution objects, wherein the task generation cycle includes a preset cycle variable associated with the date; A deadline determination module, used to determine the data reporting deadline of the data item according to the request date and the preset reporting duration of the data item in the target execution object, so as to generate the data item to be reported according to the data reporting deadline; The frequency marking module is used to mark the data items to be reported using the data collection frequency corresponding to the target execution object to generate a target execution task.

9. An electronic device, comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images