Task risk management methods and equipment

Abstract

The present application provides a task risk processing method and device, which relates to the field of computer processing technology. The method includes: obtaining a target task number; generating a query statement for a target data table, wherein the query condition is determined by the target task number and a number generation rule; obtaining a query result corresponding to the query statement from the target data table, wherein the query result includes risk information of at least one level of target tasks, and the target data table stores task numbers and risk information of tasks of multiple levels. The task numbers in the target data table are generated according to the number generation rule and are used to represent the hierarchical relationship between tasks. The present application can implement a risk identification process for descendant tasks based on a data table through the number generation rule. Since only one query statement is needed to query a data table, only one connection to the database can be established, which reduces the time required for the connection and thereby improves the efficiency of risk identification.

Description

Technical Field

[0001] The present application relates to the field of computer processing technology, and in particular to a method and device for handling task risks. Background Art

[0002] The concept of tasks exists in various technical fields. These tasks can be performed manually or by machines. For example, in software technology, tasks can include software development and testing. To ensure the successful completion of these tasks, it is necessary to monitor their status to identify any tasks that pose execution risks. For example, a task's actual start time may be later than its planned start time, or its actual end time may be later than its planned end time.

[0003] In the above-mentioned risk determination process, how to improve the efficiency of risk identification is an urgent problem to be solved. Summary of the Invention

[0004] The present application provides a task risk management method and device, which can improve the efficiency of risk identification.

[0005] In a first aspect, the present application provides a method for handling risk of a task, the method comprising:

[0006] Get the target task number;

[0007] Generate a query statement for the target data table, wherein the query condition of the query statement is determined by the target task number and a preset number generation rule;

[0008] Obtain a query result corresponding to the query statement from the target data table, wherein the query result includes risk information of target tasks of at least one level, wherein the target data table stores task numbers of tasks of multiple levels and risk information corresponding to the tasks, wherein the tasks of the multiple levels form a tree structure, and the task numbers in the target data table are generated according to the number generation rule, and the number generation rule is used to represent the hierarchical relationship between the tasks of the multiple levels.

[0009] Optionally, when the number generation rule includes: the task number of the parent-level task is the target segment of the task number of the child-level task, the query condition includes the target segment of the task number in the target data table being the target task number.

[0010] Optionally, the target fragment is a starting fragment.

[0011] Optionally, the risk information includes at least one of the following information: risk description, risk type.

[0012] Optionally, the query condition also includes that the risk type in the target data table is a target risk type.

[0013] Optionally, the target data table also includes at least one of the following task information: the task identifier of the task, the task description of the task, the planned start time of the task, the actual start time of the task, the planned completion time of the task, the actual completion time of the task, and the task status of the task. The query result also includes the task information of the target task.

[0014] Optionally, each of the levels corresponds to a user, and the user is used to manage the tasks of the level and the tasks of the descendant levels. The query condition of the query statement also includes: the level corresponding to the task number in the target data table is lower than the level corresponding to the current user.

[0015] In a second aspect, the present application provides a task risk management device, the device comprising:

[0016] Target task number acquisition module, used to obtain the target task number;

[0017] A query statement generating module, configured to generate a query statement for a target data table, wherein a query condition of the query statement is determined by the target task number and a preset number generating rule;

[0018] A risk information acquisition module is used to obtain the query results corresponding to the query statement from the target data table, the query results including risk information of target tasks at least one level, the target data table stores task numbers of tasks at multiple levels and risk information corresponding to the tasks, the tasks at the multiple levels constitute a tree structure, the task numbers in the target data table are generated according to the number generation rules, and the number generation rules are used to represent the hierarchical relationship between the tasks at the multiple levels.

[0019] Optionally, when the number generation rule includes: the task number of the parent-level task is the target segment of the task number of the child-level task, the query condition includes the target segment of the task number in the target data table being the target task number.

[0020] Optionally, the target fragment is a starting fragment.

[0021] Optionally, the risk information includes at least one of the following information: risk description, risk type.

[0022] Optionally, the query condition also includes that the risk type in the target data table is a target risk type.

[0023] Optionally, the target data table also includes at least one of the following task information: the task identifier of the task, the task description of the task, the planned start time of the task, the actual start time of the task, the planned completion time of the task, the actual completion time of the task, and the task status of the task. The query result also includes the task information of the target task.

[0024] Optionally, each of the levels corresponds to a user, and the user is used to manage the tasks of the level and the tasks of the descendant levels. The query condition of the query statement also includes: the level corresponding to the task number in the target data table is lower than the level corresponding to the current user.

[0025] In a third aspect, the present application provides an electronic device, comprising: at least one processor and a memory;

[0026] The memory stores computer-executable instructions;

[0027] The at least one processor executes the computer-executable instructions stored in the memory, so that the electronic device implements the method according to the first aspect.

[0028] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions. When a processor executes the computer-executable instructions, the computing device implements the method described in the first aspect.

[0029] In a fifth aspect, the present application provides a computer program, which is used to implement the method described in the first aspect.

[0030] The present application provides a method and device for handling the risk of a task, the method comprising: obtaining a target task number; generating a query statement for a target data table, wherein the query condition of the query statement is determined by the target task number and a preset number generation rule; obtaining a query result corresponding to the query statement from the target data table, wherein the query result includes risk information of at least one level of target tasks, wherein the target data table stores task numbers of tasks of multiple levels and risk information corresponding to the tasks, wherein the tasks of multiple levels form a tree structure, and the task numbers in the target data table are generated according to the number generation rule, and the number generation rule is used to represent the hierarchical relationship between tasks of multiple levels. The embodiment of the present application can realize the risk identification process of descendant tasks based on a data table through the number generation rule of the task numbers of tasks of multiple levels. Since only one query statement is required to query a data table, only one connection to the database can be established, which reduces the time required for the connection and thereby improves the efficiency of risk identification. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0032] Figure 1 It is a schematic diagram of the risk identification process based on the risk data table and the task data table provided by the existing technology;

[0033] Figure 2 It is a schematic diagram of the relationship between multiple levels of tasks in the prior art;

[0034] Figure 3 This is a flowchart of a risk management method for a task provided in an embodiment of the present application;

[0035] Figure 4 The embodiment of this application provides Figure 2 A task numbering diagram of multiple levels of tasks;

[0036] Figure 5 This is a structural block diagram of a risk processing device for tasks provided in an embodiment of the present application;

[0037] Figure 6 This is a structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0039] The embodiments of the present application can be applied to the risk identification scenario of tasks. The risk identification of tasks relies on the storage of risk information. In the prior art, risk information can be stored in a risk data table in a database, and task information can be stored in a task data table in a database. Figure 1 This is a schematic diagram of a risk identification process based on a risk data table and a task data table provided by the prior art. The risk identification process of the prior art includes two strategies.

[0040] Reference Figure 1As shown, in the first strategy, after the user inputs the target task identifier, the risk information of the task corresponding to the target task identifier is queried from the risk data table according to the target task identifier.

[0041] Reference Figure 1 As shown, in the second strategy, after the user inputs the target task identifier, first, the descendant task identifier of the task corresponding to the target task identifier is obtained from the task data table according to the target task identifier; then, the risk information of the task corresponding to the target task identifier and the risk information of the task corresponding to the descendant task identifier are queried from the risk data table.

[0042] The tasks in the above task data table constitute multiple levels of tasks. A parent-level task can consist of one or more child-level tasks. Figure 2 This is a diagram showing the relationship between multiple levels of tasks in the prior art. Figure 2 As shown, there are multiple levels of tasks, TSK1 through TSK8. TSK1 is the first-level task, TSK2 and TSK3 are the second-level tasks, TSK4, TSK5, and TSK6 are the third-level tasks, and TSK7 and TSK8 are the fourth-level tasks. TSK1's sub-tasks include TSK2 and TSK3, and TSK1 is the parent task of TSK2 and TSK3. Similarly, TSK2's sub-tasks include TSK4 and TSK5, TSK3's sub-task is TSK6, TSK5's sub-task is TSK7, and TSK6's sub-task is TSK8.

[0043] according to Figure 2 As shown in the above relationship, if TSK1 is the task corresponding to the target task identifier, then the remaining tasks outside TSK1 are all descendant tasks of TSK1, so they can be identified by the second strategy mentioned above. Figure 2 Of course, we can also use the first strategy above to identify only the risk information of TSK1.

[0044] It can be seen that the query process of the second strategy mentioned above needs to traverse two data tables, which requires establishing two connections with the database, which takes a long time and results in low risk identification efficiency.

[0045] In order to solve the above problems, the embodiment of the present application can store risk information through a data table and remove the above task data table. However, how to implement the risk identification process of the above second strategy based on a data table is a problem that needs to be considered. In order to implement the risk identification process of the second strategy, it is necessary to identify the descendant tasks of the target task number through the data table. The embodiment of the present application can use multiple levels of task numbers that comply with the number generation rules in the data table to determine the risk information of the descendant level tasks corresponding to the target task number according to the number generation rules, so as to implement the risk identification of the above second strategy.

[0046] It can be seen that the embodiment of the present application can realize the risk identification process of descendant-level tasks based on a data table through the numbering generation rules of multiple levels of task numbers. Since only one data table needs to be queried, only one connection to the database can be established, which reduces the time required for the connection and thereby improves the risk identification efficiency.

[0047] The following specific embodiments describe in detail the technical solutions of the embodiments of the present application and how the technical solutions of the present application solve the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0048] The methods and devices involved in the embodiments of the present application can be applicable to traditional industries, software industries, Internet industries, etc., and the embodiments of the present application do not limit their applicable fields.

[0049] Figure 3 This is a step flow chart of the risk management method for tasks provided in an embodiment of the present application. Figure 3 The method shown can be applied in electronic devices. Figure 3 As shown, the risk management approach for this task includes:

[0050] S101: Obtain the target task number.

[0051] The target task number is any task number entered by the user.

[0052] In practical applications, an interface can be provided to allow users to input the target task number, which helps to improve the human-computer interaction friendliness of risk identification and thus improve the user experience.

[0053] S102: Generate a query statement for the target data table, where the query condition of the query statement is determined by the target task number and a preset number generation rule.

[0054] It is understandable that the process of generating a query statement may include: determining a data table to be queried by the query statement, determining a query result to be output by the query statement, and determining a query condition of the query statement.

[0055] Among them, the queried data table is the target data table in the embodiment of the present application, the query results may include risk information, and the query conditions are determined by the target task number and the coding generation rules.

[0056] In an embodiment of the present application, the query condition is used to limit which tasks are to be queried, which can include two strategies: the first strategy is to only query the risk information of tasks with the target task number; the second strategy is to query the risk information of tasks with the target task number and the risk information of descendant tasks.

[0057] In the first strategy, the query condition is that the task number in the target data table is the target task number.

[0058] In the second strategy, the query condition is used to limit the task numbers in the target data table to include not only the target task number, but also the task numbers of descendant tasks determined according to the encoding generation rules. Different encoding generation rules result in different query conditions. For example, if the encoding generation rule states that the task number of descendant tasks is the task number of the parent task derived according to a preset algorithm, then the query condition could be "Task numbers in the target data table include: the target task number, and the number derived by inputting the target task number into the preset algorithm."

[0059] S103: Obtain the query result corresponding to the query statement from the target data table, the query result including the risk information of the target task of at least one level. The target data table stores the task numbers of tasks of multiple levels and the risk information corresponding to each task. The tasks of multiple levels form a tree structure. The task numbers in the target data table are generated according to the numbering generation rules, and the numbering generation rules are used to represent the hierarchical relationship between tasks of multiple levels.

[0060] Among them, the relationship between tasks at multiple levels can be as follows Figure 2 As shown in the embodiment of the present application, Figure 2 The task numbers of multiple levels of tasks in the can conform to a number generation rule. The number generation rule can be any rule indicating that two tasks are a parent-level task and a child-level task. For example, the task number of the child-level task is the task number of the parent-level task obtained according to a preset algorithm, or the task number of the parent-level task is the target segment of the task number of the child-level task. The target segment can be the starting segment, the ending segment, or an intermediate segment. The embodiments of the present application do not impose any restrictions on this.

[0061] Figure 4 The embodiment of this application provides Figure 2 A task numbering diagram for multiple levels of tasks. Figure 4 As shown, TSK1's task number is 01, and TSK1's subtasks TSK2 and TSK3 have task numbers 011 and 012, respectively. It can be seen that TSK1's task number is the starting segment of the task numbers of its subtasks TSK2 and TSK3. Similarly, TSK2's task number 011 is the starting segment of its subtasks TSK4, which has task numbers 0111, and TSK5, which has task number 0112. TSK3's task number 012 is the starting segment of its subtask TSK6, which has task number 0121. TSK5's task number 0112 is the starting segment of its subtask TSK7, which has task number 01121. TSK7's task number 0121 is the starting segment of its subtask TSK8, which has task number 01211.

[0062] In the embodiment of the present application, it can be based on Figure 4 The number generation rule shown can be used to query the risk information of tasks at one level, or to query the risk information of tasks at multiple levels.

[0063] When querying risk information of tasks at a level, the query condition in the query statement can be set to the target task number in the target data table being the target task number input by the user.

[0064] When querying risk information of tasks at multiple levels, the query condition in the query statement can be set to the target segment of the task number in the target data table as the target task number entered by the user, essentially achieving fuzzy matching between the task number in the target data table and the target task number.

[0065] It is understandable that in order to improve the efficiency of obtaining risk information, it is necessary to use a simpler number generation rule to represent the relationship between the task numbers of multiple levels of tasks. In this way, the time required to determine the task number of the child task based on the task number of the parent task can be shortened, thereby improving the efficiency of risk identification. Based on this consideration, we can use the task number of the parent task as the target fragment of the task number of the child task as the number generation rule to maximize the efficiency of risk identification. Therefore, when identifying risk information, the risk information corresponding to the task number whose target fragment is the target task number can be obtained from the target data table as the risk information of the target task.

[0066] Regarding the second strategy of querying risk information of tasks at multiple levels, the query conditions in the embodiment of the present application are different from those in the prior art.

[0067] In the prior art, the task data table is first searched for the descendant task IDs of the target task ID. To achieve this query, the task data table needs to be traversed multiple times, each traversal requiring a query statement with different query conditions for the query statements used in different traversals.

[0068] In the first traversal, the query condition of the query statement is that the parent task ID in the task data table is the target task ID. If the task corresponding to the target task ID is Figure 4 For a level-one task TSK1, after the first traversal, the task identifiers of the second-level tasks TSK2 and TSK3, that is, the subtask identifiers of TSK1, can be obtained.

[0069] In the second traversal, the query statement's query condition is that the parent-level task ID in the task data table is the subtask ID obtained in the first traversal. After the second traversal, the task IDs of the third-level tasks TSK4, TSK5, and TSK6 are obtained, which are the subtask IDs of TSK2 and TSK3.

[0070] In the third traversal, the query statement's query condition is that the parent-level task ID in the task data table is the subtask ID obtained in the second traversal. After the third traversal, the task IDs of the fourth-level tasks TSK7 and TSK8 are obtained, which are the subtask IDs of TSK4, TSK5, and TSK6.

[0071] The subtask identifiers obtained by the above three traversals can be collectively referred to as descendant task identifiers of TSK1.

[0072] Then, another query statement is used to query the risk data table, where the query condition is that the task identifier in the risk data table exists in at least one descendant task identifier obtained above.

[0073] It can be seen that since the embodiment of the present application only needs to query a data table through one query statement, only one connection to the database needs to be established, while the prior art needs to use two query statements to achieve this, thus requiring two connections to the database.

[0074] When the target segment is the starting segment, the risk information corresponding to the task with the starting segment as the target task number can be used as the risk information of the target task. Since the starting segment is obtained more quickly, it can help improve the matching efficiency and thus improve the efficiency of risk information identification.

[0075] When the target segment is the last segment, the risk information corresponding to the task whose last segment is the target task number may be used as the risk information of the target task.

[0076] When the target segment is a designated intermediate segment, the risk information corresponding to the task with the target task number in the intermediate segment may be used as the risk information of the target task.

[0077] The risk information in the embodiment of the present application may include at least one of the following information: risk description and risk type.

[0078] The risk description is used to describe the risk through simple statements, for example, the actual start time of the task is later than the planned start time of the task, or the actual execution duration of the task is longer than the planned execution duration of the task, or the actual end time of the task is later than the planned end time of the task.

[0079] The above risk types can be represented by enumeration values, for example, 0 represents no risk, 1 represents actual start delay risk, and 2 represents actual completion delay risk.

[0080] In actual applications, users can focus on all types of risks. In this case, users can enter the target task number instead of the target risk type to obtain all types of risk information corresponding to the target task number. For example, refer to Figure 4 As shown, if the risk types corresponding to TSK1 to TSK8 are actual start delay risk, actual start delay risk, no risk, no risk, actual start delay risk, no risk, actual delayed start risk, no risk. If the user only enters the target task number 011, refer to Figure 4 As shown, target task number 011 corresponds to task TSK2. Therefore, the risk information for TSK2, TSK4, TSK5, and TSK7 can be retrieved. The risk information for TSK2, TSK4, TSK5, and TSK7 is: actual delayed start risk, no risk, actual delayed start risk, and actual delayed start risk, respectively. This allows the user to query the risk information for all tasks, both those with and without risk, allowing them to fully monitor various risk information.

[0081] Of course, users can also focus on the target risk type of risk. In this case, users need to enter not only the target task number but also the target risk type. For example, Figure 4 As shown, if the risk types corresponding to TSK1 to TSK8 are actual start delay risk, actual start delay risk, no risk, no risk, actual start delay risk, no risk, actual delayed start risk, no risk. If the user enters the target task number 011 and the target risk type 1, refer to Figure 4As shown, target task number 011 corresponds to task TSK2. TSK2's descendant tasks include risk information for TSK2, TSK4, TSK5, and TSK7. The risk information for TSK2, TSK4, TSK5, and TSK7 is, respectively, actual delayed start risk, no risk, actual delayed start risk, and actual delayed start risk. The actual risk information obtained is the following risk information for TSK2, TSK5, and TSK7, with target risk type 1 (representing actual delayed start risk), allowing users to focus on monitoring actual delayed start risk.

[0082] The aforementioned risk information may also include a risk status to indicate whether the risk has been addressed, including but not limited to: pending risk and resolved risk. Thus, when identifying risk information, users can display risk information with a pending risk status, helping to prioritize and monitor pending risks.

[0083] In an embodiment of the present application, the target data table may include not only the task number and risk information, but also at least one of the following task information: the task identifier, the task description, the planned start time, the actual start time, the planned completion time, the actual completion time, and the task status. Thus, in addition to obtaining risk information from the target data table, the task information of the target task can also be obtained. This allows users to not only understand the risk information of the target task, but also the task information of the target task, which helps users comprehensively monitor tasks.

[0084] As mentioned above, the task identifier can be generated in ascending order, the task description can be used to simply describe the task content, and the task status is used to describe the execution status of the task at the current time. For example, the task status can include: task not started, task being executed, and task completed.

[0085] Of course, in actual applications, the task information may further include a task name, which is used to briefly describe the task content and is usually for display.

[0086] The embodiment of the present application can query the risk information and task information of a task through the above-mentioned target data table, without the need to associate two data tables. In this way, the time required to associate the data tables can be saved, further improving the efficiency of risk identification.

[0087] In an embodiment of the present application, each level of tasks can correspond to a user with risk information for managing tasks at that level. That is, each level corresponds to a user, and the user can manage tasks at that level and tasks at its descendant levels, but users at its descendant levels cannot manage tasks at its parent level. Therefore, when querying risk information, the level corresponding to the current user who inputs the target task number is first determined; then, a query statement is generated, the query condition of which includes not only that the target segment of the task number in the target data table is the target task number, but also that the level corresponding to the task number in the target data table is lower than the level corresponding to the current user.

[0088] The above levels can limit the unauthorized viewing of risk information by users. For example, refer to Figure 4 As shown in the figure, if user USR1 enters the target task number 011 for the third-level task, user USR1 can only query the risk information of TSK4, TSK5, and TSK7, but cannot query the risk information of TSK2. However, if user USR2 enters the target task number 011 for the second-level task, user USR2 can query the risk information of TSK2, TSK4, TSK5, and TSK7.

[0089] The embodiment of the present application can accurately control the viewing authority of risk information and avoid the leakage of risk information through the correspondence between the above-mentioned levels and users.

[0090] In summary, the risk identification method provided in the embodiments of the present application can identify the risk information of a task, so as to monitor, warn and pre-process risky tasks to ensure the smooth execution of the task.

[0091] Corresponding to the risk handling method of the tasks in the above embodiment, Figure 5 This is a structural block diagram of a risk processing device for tasks provided by an embodiment of the present application. For ease of explanation, only the parts related to the embodiment of the present application are shown. Figure 5 The risk processing device 200 for the above-mentioned task includes: a target task number acquisition module 201, a query statement generation module 202 and a risk information acquisition module 203.

[0092] The target task number acquisition module 201 is used to acquire the target task number.

[0093] The query statement generating module 202 is used to generate a query statement for the target data table, wherein the query condition of the query statement is determined by the target task number and a preset number generating rule.

[0094] The risk information acquisition module 203 is used to obtain the query results corresponding to the query statement from the target data table, and the query results include risk information of target tasks of at least one level. The target data table stores task numbers of tasks of multiple levels and risk information corresponding to the tasks. The tasks of the multiple levels constitute a tree structure. The task numbers in the target data table are generated according to the number generation rules, and the number generation rules are used to represent the hierarchical relationship between the tasks of the multiple levels.

[0095] Optionally, when the number generation rule includes: the task number of the parent-level task is the target segment of the task number of the child-level task, the query condition includes the target segment of the task number in the target data table being the target task number.

[0096] Optionally, the target fragment is a starting fragment.

[0097] Optionally, the risk information includes at least one of the following information: risk description, risk type.

[0098] Optionally, the query condition also includes that the risk type in the target data table is a target risk type.

[0099] Optionally, the target data table also includes at least one of the following task information: the task identifier of the task, the task description of the task, the planned start time of the task, the actual start time of the task, the planned completion time of the task, the actual completion time of the task, and the task status of the task. The query result also includes the task information of the target task.

[0100] Optionally, each of the levels corresponds to a user, and the user is used to manage the tasks of the level and the tasks of the descendant levels. The query condition of the query statement also includes: the level corresponding to the task number in the target data table is lower than the level corresponding to the current user.

[0101] The risk management device for tasks provided in this embodiment can be used to perform the above Figure 3 The technical solution of the method embodiment shown has similar implementation principles and technical effects, and will not be repeated here in this embodiment.

[0102] Figure 6 6 is a structural block diagram of an electronic device 600 provided in an embodiment of the present application. The electronic device 600 includes a memory 602 and at least one processor 601.

[0103] The memory 602 stores computer-executable instructions.

[0104] At least one processor 601 executes the computer execution instructions stored in the memory 602, so that the electronic device 601 implements the aforementioned Figure 3 The method in .

[0105] In addition, the electronic device may further include a receiver 603 and a transmitter 604. The receiver 603 is configured to receive information from other devices or equipment and forward it to the processor 601. The transmitter 604 is configured to send the information to the other devices or equipment.

[0106] The above description is merely a preferred embodiment of the present application and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of application involved in this application is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but also encompasses other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned application concept. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions applied for in this application.

[0107] In addition, although adopting specific order to describe each operation, this should not be interpreted as requiring these operations to be executed in the specific order shown or in sequential order.Under certain environment, multitasking and parallel processing may be advantageous.Similarly, although comprising some specific implementation details in the above discussion, these should not be interpreted as limiting the scope of the application.Some features described in the context of separate embodiment can also be implemented in a single embodiment in combination.On the contrary, the various features described in the context of a single embodiment also can be implemented in multiple embodiments individually or in the mode of any suitable subcombination.

[0108] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A method for handling risk of a task, characterized in that: The method comprises: Get the target task number; Generate a query statement for the target data table, wherein the query condition of the query statement is determined by the target task number and a preset number generation rule, and different code generation rules correspond to different query conditions; Obtaining a query result corresponding to the query statement from the target data table, the query result including risk information of at least one level of target tasks, the target data table storing task numbers and risk information corresponding to tasks at multiple levels, the tasks at multiple levels forming a tree structure, the task numbers in the target data table being generated according to the number generation rule, the number generation rule being used to represent a hierarchical relationship between the tasks at the multiple levels; When the number generation rule includes: the task number of the parent-level task is the target segment of the task number of the child-level task, the query condition includes the target segment of the task number in the target data table being the target task number; Each of the levels corresponds to a user, and the user is used to manage tasks of the level and tasks of its descendant levels; Before generating the query statement for the target data table, the method further includes: Determine the level corresponding to the current user who inputs the target task number, and the query condition further includes: the level corresponding to the task number in the target data table is lower than the level corresponding to the current user.

2. The method according to claim 1, characterized in that The target fragment is the starting fragment.

3. The method according to claim 1, characterized in that The risk information includes at least one of the following information: risk description and risk type.

4. The method according to claim 3, characterized in that The query condition also includes that the risk type in the target data table is a target risk type.

5. The method according to any one of claims 1 to 4, characterized in that The target data table also includes at least one of the following task information: the task identifier of the task, the task description of the task, the planned start time of the task, the actual start time of the task, the planned completion time of the task, the actual completion time of the task, and the task status of the task. The query result also includes the task information of the target task.

6. A task risk management device, characterized in that: The device comprises: Target task number acquisition module, used to obtain the target task number; A query statement generation module is used to generate a query statement for the target data table, wherein the query condition of the query statement is determined by the target task number and a preset number generation rule, and different code generation rules correspond to different query conditions; a risk information acquisition module, configured to acquire a query result corresponding to the query statement from the target data table, the query result including risk information of target tasks at at least one level, the target data table storing task numbers and risk information corresponding to tasks at multiple levels, the tasks at the multiple levels forming a tree structure, the task numbers in the target data table being generated according to a number generation rule, the number generation rule being used to represent a hierarchical relationship between the tasks at the multiple levels; When the number generation rule includes: the task number of the parent-level task is the target segment of the task number of the child-level task, the query condition includes the target segment of the task number in the target data table being the target task number; Each of the levels corresponds to a user, and the user is used to manage tasks of the level and tasks of its descendant levels; The query statement generation module is further used to determine the level corresponding to the current user who inputs the target task number before generating the query statement for the target data table. The query condition also includes: the level corresponding to the task number in the target data table is lower than the level corresponding to the current user.

7. An electronic device, characterized in that: include: at least one processor and memory; The memory stores computer-executable instructions; The at least one processor executes the computer-executable instructions stored in the memory, so that the electronic device implements the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, and when a processor executes the computer-executable instructions, the computing device implements the method according to any one of claims 1 to 5.

9. A computer program, characterized in that The computer program is used to implement the method according to any one of claims 1 to 5.

Images