Task management method and device, electronic equipment and medium

Abstract

The embodiment of the invention provides a task management method and device, electronic equipment and a medium, and belongs to the field of network operation and maintenance. The method comprises the steps of obtaining task information of a target service, wherein the task information is used for indicating at least one task group associated with the target service; based on the task information, constructing a task nesting relationship architecture associated with the target service, the task nesting relationship architecture comprising at least one task chain, each task chain being associated with each task group, each task chain comprising task nodes of multiple levels, and each task node of the previous level comprising at least one task node of the next level, the task nodes of the same level are arranged in parallel and / or in series; and managing the task execution process of the target service based on the task nesting relation architecture. In this way, the electronic device can systematically organize and manage the complex task chain in a unified and standardized mode, and the overall cooperation and data interaction efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of network operation and maintenance, and in particular to a task management method, device, electronic device and medium. Background Art

[0002] In the business management systems of many industries, there are processes of task issuance, collection, analysis and reporting. For example, a business management system is used to manage the tasks of multiple salesmen visiting multiple customers, and "visiting Company A" is one of the tasks. Specifically, this task requires multiple processes such as "visiting manager 1 via email", "visiting manager 2 via SMS", etc., and each process includes multiple different specific execution steps. It can be seen that the task management system needs to carry out complex and numerous task management processes.

[0003] However, in related technologies, the data management methods for different tasks are not unified, resulting in inefficient overall collaboration and data interaction of the system. Summary of the invention

[0004] The main purpose of the embodiments of the present application is to propose a task management method, device, electronic device and medium, aiming to improve the efficiency of overall collaboration and data interaction of a business management system.

[0005] To achieve the above object, a first aspect of an embodiment of the present application provides a task management method, the method comprising:

[0006] Acquire task information of a target business, where the task information is used to indicate at least one task group associated with the target business;

[0007] Based on the task information, a task nesting relationship architecture associated with the target business is constructed, wherein the task nesting relationship architecture includes at least one task chain, each of the task chains is associated with each of the task groups, the task chain includes task nodes of multiple levels, and each task node of the upper level includes at least one task node of the lower level, and the task nodes of the same level are arranged in parallel and / or serially;

[0008] Based on the task nesting relationship architecture, the task execution process of the target business is managed.

[0009] In some embodiments, the multiple levels include a first level, a second level, and a third level, the first level is the level above the second level, the second level is the level above the third level, the task nodes of the first level include the task group; the task nodes of the second level include at least one task associated with the task group; and the task nodes of the third level include at least one execution event associated with the task.

[0010] In some implementations, the task chain further includes completion status information of each task node, and the task execution process of the target business is managed based on the task nesting relationship architecture, including:

[0011] Obtaining user behavior data for each of the execution events;

[0012] According to the user behavior data of each of the execution events, the completion status information of the execution event is updated.

[0013] In some implementations, after acquiring the behavior data of the executing user of the executing node, the method further includes:

[0014] Comparing the behavior data with trigger conditions of other task groups to obtain a comparison result, wherein the other task groups are task groups associated with the target business and not indicated by the task information;

[0015] When the comparison result indicates that the behavior data meets the trigger condition, the task nesting relationship architecture is updated for the other task groups.

[0016] In some implementations, the task chain further includes completion status information of each task node, the multiple levels include a first target level and a second target level, the first target level is an upper level of the second target level, and the task execution process of the target business is managed based on the task nesting relationship architecture, including:

[0017] When the completion status information of the target task node of the first target level indicates that the target task node is not completed, the traversed target task nodes include the completion status information of the task nodes of the second target level;

[0018] When the completion status information of the task nodes of the second target level included in each of the target task nodes indicates that the corresponding task nodes have been completed, the completion status information of the target task nodes is changed to "the target task nodes have been completed".

[0019] In some implementations, the task nodes of the first target level are arranged in series based on the execution order of the task nodes of the first target level, and before changing the completion status information of the target task node to the target task node being completed, the method further includes:

[0020] Determine a previous task node of the target task node according to the execution order, the previous task node being a task node whose execution order is before the target task node;

[0021] Traversing the completion status information of the previous task node;

[0022] The step of changing the completion status information of the target task node to indicate that the target task node has been completed includes:

[0023] When the completion status information of the previous task node indicates that the previous task node has been completed, the completion status information of the target task node is changed to indicate that the target task node has been completed.

[0024] In some implementations, managing the task execution process of the target business based on the task nesting relationship architecture includes:

[0025] generating a task execution instruction using the task chain;

[0026] The task execution instruction is sent to an execution user associated with the task group corresponding to the task chain.

[0027] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application provides a task management device, the device comprising:

[0028] An acquisition module, used to acquire task information of a target business, where the task information is used to indicate at least one task group associated with the target business;

[0029] A construction module, configured to construct a task nesting relationship architecture associated with the target business based on the task information, wherein the task nesting relationship architecture includes at least one task chain, each of the task chains is associated with each of the task groups, the task chain includes task nodes of multiple levels, and each task node of the upper level includes at least one task node of the lower level, and the task nodes of the same level are arranged in parallel and / or in series;

[0030] A management module is used to manage the task execution process of the target business based on the task nesting relationship architecture.

[0031] To achieve the above-mentioned purpose, the third aspect of an embodiment of the present application proposes an electronic device, which includes a memory and a processor, the memory stores a computer program, and the processor implements the task management method described in the first aspect when executing the computer program.

[0032] To achieve the above objectives, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the task management method described in the first aspect.

[0033] The task management method, device, electronic device and medium proposed in the present application, the electronic device constructs a task nesting relationship architecture, and the task nesting relationship architecture manages each task in a hierarchical manner according to the task chain associated with the target business, so that the electronic device can systematically organize and manage complex task chains in a unified and standardized manner, thereby improving the overall collaboration and data interaction efficiency, and at the same time realizing serial or parallel scheduling of task nodes at different levels during the business execution process, so that the electronic device performing business management can efficiently handle the dependencies between tasks at each level. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 It is a flowchart of the task management method provided in the embodiment of the present application;

[0035] Figure 2 It is a structural diagram of the task nesting relationship architecture provided in an embodiment of the present application;

[0036] Figure 3 It is a flowchart of a task group triggering process provided by an embodiment of the present application;

[0037] Figure 4 It is a flowchart of a task management process provided by an embodiment of the present application;

[0038] Figure 5 is a structural diagram of a task management device provided in an embodiment of the present application;

[0039] Figure 6 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0041] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0042] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0043] First, some nouns involved in this application are analyzed:

[0044] Business Management System (BMS): A business management system refers to an integrated software system used to assist enterprises or organizations in planning, managing and supervising their various business processes and tasks. Business management systems usually include multiple modules and functions, such as task assignment, data collection, analysis, report generation, etc., to ensure the smooth connection and efficient operation of various business links. In a business management system, all tasks, processes and related data will be processed according to predetermined rules or logic. The system uses automation to reduce manual intervention, improve efficiency and reduce error rates. Typical application scenarios include sales management, customer relationship management (CRM), project management, etc. Especially in complex tasks involving multi-department collaboration, the business management system can provide managers with real-time data and analysis to help them make more accurate decisions, thereby effectively improving the overall execution of the business and the operational efficiency of the enterprise.

[0045] In the business management systems of many industries, there are processes of task issuance, collection, analysis and reporting. For example, a business management system is used to manage the tasks of multiple salesmen visiting multiple customers, and "visiting Company A" is one of the tasks. Specifically, this task requires multiple processes such as "visiting manager 1 via email", "visiting manager 2 via SMS", etc., and each process includes multiple different specific execution steps. It can be seen that the task management system needs to carry out complex and numerous task management processes.

[0046] However, in related technologies, the data management methods for different tasks are not unified, resulting in inefficient overall collaboration and data interaction of the system.

[0047] Based on this, the embodiments of the present application provide a task management method, device, electronic device and medium, aiming to improve the efficiency of overall collaboration and data interaction of a business management system.

[0048] The task management method, device, electronic device and medium provided in the embodiments of the present application are specifically described through the following embodiments. First, the task management method in the embodiments of the present application is described.

[0049] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0050] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0051] The task management method provided in the embodiment of the present application relates to the field of artificial intelligence technology. The task management method provided in the embodiment of the present application can be applied to the terminal, can also be applied to the server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or it can be configured as a server cluster or distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the task management method, etc., but is not limited to the above forms.

[0052] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0053] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0054] See also Figure 1 , Figure 1 It is a flowchart of a task management method provided by an embodiment of the present application. In a first aspect, an embodiment of the present application provides a task management method, including steps S110 to S130.

[0055] Step S110: Acquire task information of the target business, where the task information is used to indicate at least one task group associated with the target business.

[0056] First, the electronic device obtains task information related to the target business. The task information here includes all tasks that need to be completed by the business and the relationship between these tasks to form at least one "task group". This task group can be regarded as a series of logically related task sets.

[0057] For example, in the task of managing a salesperson's visit to a customer, the electronic device first obtains relevant information about the target business of "visiting Company A", which indicates the specific task groups associated with the task, such as "visiting manager 1's task group" and "visiting manager 2's task group".

[0058] Step S120: Based on the task information, construct a task nesting relationship architecture associated with the target business, the task nesting relationship architecture includes at least one task chain, each task chain is associated with each task group, the task chain includes multiple levels of task nodes, and each task node of the previous level includes at least one task node of the next level, and the task nodes of the same level are set in parallel and / or serially.

[0059] Based on the task information obtained in step S110, the electronic device constructs a task nesting relationship architecture related to the target business. In this architecture, tasks are associated with each task group through one or more task chains, and are further divided into task nodes of different levels. Each task node of the previous level can contain one or more task nodes of the next level, and the task nodes of the same level can be executed in parallel or serially, so that the execution order and dependencies of tasks can be better managed.

[0060] For example, in the business of "visiting Company A", the electronic device constructs a task chain based on the task information, with "visiting manager 1's task group" as the first-level node, and the next-level task nodes include "email visit" and "telephone visit" tasks. These tasks can be performed in parallel or serially.

[0061] Step S130: managing the task execution process of the target business based on the task nesting relationship architecture.

[0062] After the electronic device completes the task nesting relationship architecture, the electronic device manages the task execution process based on the architecture. The management process may include real-time monitoring of the task execution status, ensuring that the tasks are executed in the set order, and adjusting the execution mode of the task nodes (parallel or serial) when necessary, so as to ensure the smooth completion of the target business tasks.

[0063] For example, in the execution of the "visit company A" business, the electronic device first executes the first-level "visit manager 1's task group" according to the requirements of the task chain. After the second-level "email visit" is completed, the next step of the second level, "telephone visit", is automatically triggered to ensure the order of the tasks. If an abnormal situation is encountered during the execution, the electronic device will also dynamically adjust the execution progress of the task node to ensure the complete execution of the task and the smooth completion of the target business.

[0064] Through the above steps S110-S130, the electronic device constructs a task nesting relationship architecture, and the task nesting relationship architecture manages each task in layers according to the task chain associated with the target business, so that the electronic device can systematically organize and manage complex task chains in a unified and standardized manner, thereby improving the overall collaboration and data interaction efficiency, and at the same time realizing serial or parallel scheduling of task nodes at different levels during business execution, so that the electronic device performing business management can efficiently handle the dependencies between tasks at each level.

[0065] See also Figure 2 , Figure 2 This is a structural diagram of the task nested relationship architecture provided in an embodiment of the present application. In some embodiments, multiple levels include a first level, a second level, and a third level. The first level is the level above the second level, and the second level is the level above the third level. The task nodes of the first level include a task group; the task nodes of the second level include at least one task associated with the task group; and the task nodes of the third level include at least one execution event associated with the task.

[0066] In this embodiment, the task nesting relationship architecture is divided into multiple levels to accurately manage the different stages of task execution. These levels include the first level, the second level and the third level. The first level, as the highest level, mainly includes task groups, which are used to represent the overall task set associated with the target business. The second level is the next level of the first level, which is used to include each specific task associated with the task group, further refining the execution content of the task group. The third level is the next level of the second level, which includes execution events associated with each task. These events represent the specific operation steps of the task to ensure the integrity and accurate execution of the task.

[0067] Thus, through this multi-level structure, the electronic device can implement hierarchical task management and effectively control the dependencies between task groups, tasks and execution events, thereby improving the accuracy of the task execution process and the overall efficiency of the electronic device.

[0068] For example, in a salesperson's customer visit task, the electronic device divides the task group of "visiting Company A" into three levels. The first level is the "visiting Company A" task group, which is used to manage the entire visit process. The second level contains the specific tasks of the task group, such as the tasks of "visiting manager 1" and "visiting manager 2". The third level further refines the execution steps of these tasks, among which the task of "visiting manager 1" contains two execution events: "contacting manager 1 by email" and "contacting manager 1 by SMS", while "visiting manager 2" contains "contacting manager 2 by email" and "contacting manager 2 by phone". Through this three-level architecture, the electronic device can ensure the execution order of each task and the orderly progress of the specific operation steps, and realize the precise management of complex tasks.

[0069] In some implementations, the task chain also includes completion status information of each task node, and manages the task execution process of the target business based on the task nesting relationship architecture, including:

[0070] Obtain user behavior data for each execution event;

[0071] Update the completion status information of the execution event based on the user behavior data of each execution event.

[0072] In this embodiment, the task chain not only constructs the task relationship at each level, but also includes the completion status information of the task node, so as to fully grasp the progress of task execution. Based on this task nested relationship architecture, the electronic device can effectively manage the task execution process of the target business. Specifically, the electronic device will obtain user behavior data related to each execution event to monitor the actual execution of the task. These user behavior data provide important information about whether the execution event has been completed. Subsequently, the electronic device will update the completion status information of each execution event in real time based on the collected user behavior data, thereby ensuring that the execution status of the task is kept up to date.

[0073] This not only improves the transparency of task management, but also reflects the progress of tasks in a timely manner, facilitating the scheduling and decision-making of subsequent tasks.

[0074] For example, in a sales team's customer visit task, the electronic device sets two execution events for the "Visit Manager 1" task in the "Visit Company A" task chain: "Email Contact Manager 1" and "SMS Contact Manager 1". During the task execution process, the electronic device will obtain user behavior data, such as recording whether the salesperson has successfully sent emails and text messages. If the salesperson sends an email, the electronic device will obtain the behavior data and update the completion status of "Email Contact Manager 1" to completed (change the 0 representing unfinished in the relevant code of "Email Contact Manager 1" to 1 representing completed). If the salesperson has not sent a text message, the electronic device will keep the status of the event as unfinished. This real-time data monitoring and status update mechanism enables managers to clearly understand the progress of each task, so as to better coordinate subsequent customer visit activities.

[0075] See also Figure 3 , Figure 3 is a flowchart of a task group triggering process provided by an embodiment of the present application. In some implementations, after obtaining the behavior data of the executing user of the executing node, the method further includes:

[0076] Step S310: comparing the behavior data with the triggering conditions of other task groups to obtain a comparison result, where the other task groups are task groups associated with the target business and not indicated by the task information;

[0077] Step S320: When the comparison result indicates that the behavior data meets the trigger condition, the task nesting relationship structure is updated for other task groups.

[0078] In this embodiment, after the electronic device obtains the behavior data of the executing user of the execution node, it will also compare the behavior data with the trigger conditions of other task groups to obtain a comparison result. These "other task groups" are task groups that are associated with the target business but do not belong to the task groups indicated by the current task information. Through this comparison mechanism, the electronic device can update the task nesting relationship architecture when the comparison result shows that the behavior data meets the trigger conditions of other task groups.

[0079] In this way, the electronic device can dynamically trigger other task groups related to the target business according to the current task execution status, thereby realizing adaptive task chain expansion during task progress and ensuring the flexibility and timeliness of the task flow.

[0080] For example, in a sales management system, suppose a salesperson is executing the task chain of "visiting Company A" and has completed the execution event of "contacting manager 1 via email." After the electronic device obtains the behavior data, it compares it with the trigger condition of another task group, "product update notification task group." The trigger condition of this task group is "completing the first contact with Company A." When the comparison result of the electronic device shows that the behavior data of "contacting manager 1 via email" meets the trigger condition, the electronic device will automatically add the "product update notification task group" to the task nesting relationship architecture. In this way, the electronic device can dynamically update the task chain according to the actual execution situation, ensuring that after visiting Company A, the salesperson automatically enters the subsequent tasks related to the company, thereby improving the consistency and flexibility of business processing.

[0081] See also Figure 4 , Figure 4 The present application provides a flowchart of a task management process. In some implementations, the task chain further includes completion status information of each task node. The multiple levels include a first target level and a second target level. The first target level is the upper level of the second target level. Based on the task nesting relationship architecture, the task execution process of the target business is managed, including:

[0082] Step S410: when the completion status information of the target task node of the first target level indicates that the target task node is not completed, the completion status information of the task node of the second target level included in the traversed target task nodes;

[0083] Step S420: When the completion status information of the task nodes of the second target level included in each target task node indicates that the corresponding task node has been completed, the completion status information of the target task node is changed to the target task node has been completed.

[0084] In this embodiment, the task chain contains the completion status information of each task node, and realizes the effective management of the task execution process of the target business through multi-level management. Specifically, the task chain is divided into a first target level and a second target level, wherein the first target level is above the second target level. When managing the task execution process, the electronic device first checks the completion status information of the target task node in the first target level. If the status information indicates that the target task node is not completed, the electronic device will further traverse the completion status information of the task nodes in the second target level contained in the node to check the execution status of its subtasks. When the completion status information of all the task nodes of the second target level included indicates that these task nodes have been completed, the electronic device will update the completion status information of the target task node of the first target level to completed.

[0085] In this way, the logical consistency of the task hierarchy is ensured, so that the completion status of the high-level task node can be dynamically updated according to the completion status of the low-level task nodes it contains.

[0086] For example, in a customer visit business, assume that the target task node of the first target level is "Visit Company A", and the task nodes of the second target level it contains include two tasks: "Email Contact Manager 1" and "SMS Contact Manager 2". When the electronic device checks the completion status of the "Visit Company A" task, it finds that its status shows as unfinished, so the electronic device traverses the completion status of the subtasks of the task node - "Email Contact Manager 1" and "SMS Contact Manager 2". If the electronic device confirms that both tasks have been completed, the electronic device will automatically update the completion status of "Visit Company A" to completed. This mechanism ensures that the status of "Visit Company A" can change dynamically according to the actual completion status of the subtasks, avoiding false reports of unfinished or completed situations, thereby ensuring accurate management of tasks.

[0087] In some implementations, the task nodes of the first target level are arranged in series based on the execution order of the task nodes of the first target level. Before changing the completion status information of the target task node to the target task node being completed, the method further includes:

[0088] Determine a previous task node of the target task node according to the execution order, where the previous task node is a task node that is before the target task node in the execution order;

[0089] Traverse the completion status information of previous task nodes;

[0090] Change the completion status information of the target task node to target task node completed, including:

[0091] When the completion status information of the previous task node indicates that the previous task node has been completed, the completion status information of the target task node is changed to indicate that the target task node has been completed.

[0092] In this embodiment, the task nodes of the first target level are serially arranged according to the execution order to ensure that the tasks are executed in sequence according to the predetermined order. Before changing the completion status information of the target task node to completed, the electronic device first needs to determine the previous task node related to the target task node, and the previous task node is the task node that is located before the target task node in the execution order. Next, the electronic device will traverse the completion status information of these previous task nodes to confirm their execution status. When it is confirmed that all previous task nodes have been completed, the electronic device updates the completion status information of the target task node to completed.

[0093] In this way, the logic and completeness of task execution are ensured, avoiding incorrectly marking tasks as completed due to unsatisfied task sequence.

[0094] For example, in the customer visit task of the sales team, it is assumed that "Visit Company A" is the target task node of the first target level, and its previous task nodes are "Confirm the visit time" and "Send the visit notification". Before the electronic device is ready to update the status of "Visit Company A" to completed, it first determines that "Confirm the visit time" and "Send the visit notification" are its previous task nodes. The electronic device will check the completion status of these two tasks. If both "Confirm the visit time" and "Send the visit notification" are completed, the electronic device will update the completion status of "Visit Company A" to completed. This ensures that the completion status of the "Visit Company A" task is based on the completion of all related previous tasks, thereby maintaining the order and accuracy of task execution.

[0095] In some implementations, the task execution process of the target business is managed based on the task nesting relationship architecture, including:

[0096] Use task chains to generate task execution instructions;

[0097] The task execution instruction is sent to an execution user associated with the task group corresponding to the task chain.

[0098] In this embodiment, the electronic device effectively manages the task execution process of the target business based on the task nesting relationship architecture. Specifically, the electronic device first uses the task chain to generate corresponding task execution instructions, which describe in detail the tasks to be executed and their order. Then, the electronic device sends these task execution instructions to the execution user associated with the task group corresponding to the task chain. This process ensures that the execution user can receive accurate task instructions, so as to carry out the corresponding work efficiently and ensure that the task is smoothly executed according to the predetermined plan.

[0099] For example, in a sales management electronic device, assume that the "visit company A" task chain has been constructed and contains multiple subtasks, such as "confirm the visit time", "send the visit notice" and "actual visit". The task execution instructions generated by the electronic device using the task chain may include "first confirm the visit time, then send the notice, and finally make the actual visit". These instructions will be sent to the salesperson in charge of the "visit company A" task group to ensure that they clearly understand the execution order and specific requirements. In this way, the salesperson can efficiently complete the customer visit task according to the instructions provided by the electronic device, thereby improving the efficiency and accuracy of task execution.

[0100] Based on the above multiple implementations, the task management method provided in the embodiment of the present application can be described as follows:

[0101] Electronic devices manage the task execution process of the target business by building a task nesting relationship architecture to ensure that tasks can be completed in a predetermined logical order, and the relationships between tasks at different levels are clear and executed efficiently. The task nesting relationship architecture includes multiple levels, in which the hierarchical division and status information of different task nodes constitute the core of the entire task chain. Generally speaking, the multiple levels in the task chain can be divided into the first target level and the second target level. The task nodes of the first target level are higher-level management nodes, which include task groups associated with the business, while the task nodes of the second target level are refined to specific tasks. This hierarchical structure ensures that the management of tasks at different granularities can adapt to complex business needs.

[0102] On this basis, the task chain further integrates the completion status information of the task nodes, and the electronic device can track the execution status of each task node in real time. For each task node of the first target level, the electronic device will first check its completion status information. If the status indicates unfinished, the electronic device will traverse all the task nodes of the second target level contained in the node and check the completion status of each subtask. When it is confirmed that all the task nodes of the second target level have been completed, the electronic device will update the status of the task nodes of the first target level to completed. This inter-level linkage mechanism ensures that the status of the high-level task node is always consistent with the execution status of the low-level task nodes it contains, avoiding false reports of completion or incompleteness, thereby effectively improving the management accuracy of the task process.

[0103] During the execution of the task, the completion status information of the task chain plays an important role in serial control. The task nodes of the first target level are set serially in the execution order to ensure that the task nodes are completed in sequence. The electronic device first determines the previous task node of the current target task node and traverses its completion status information. If the previous task node has been completed, the status of the current task node can be updated to completed. This mechanism builds a clear serial path in the task chain, avoids the early triggering of subsequent tasks before the completion of previous tasks, and ensures the sequentiality and logic of the task chain.

[0104] In addition, the solution introduces real-time collection and management of user behavior data, so that the task chain can be dynamically adjusted according to the execution progress. After obtaining the behavior data of the executing user, the electronic device compares the data with the trigger conditions of other task groups. Other task groups refer to those task groups that are associated with the current target business but are not directly indicated by the current task information. When the comparison results show that the behavior data meets the trigger conditions of other task groups, the electronic device will automatically add the task group to the task nesting relationship architecture and update the task chain. This mechanism enables the task chain to be flexibly expanded according to business needs during the execution process, ensuring that the task management of the electronic device can adaptively respond to changes in task execution.

[0105] The task chain also includes a mechanism for implementing task control using task execution instructions. The electronic device generates task execution instructions based on the task chain, which contain the specific operation content and execution order of each task node. These instructions will be sent to the execution users of the corresponding task group to ensure the accurate communication of the task instructions. Through this instruction sending mechanism, the electronic device can clearly convey the execution logic of the task chain at the execution user end, ensuring that each task can be strictly executed according to the predetermined steps.

[0106] For example, in a sales management system, suppose a salesperson needs to perform the task of "visiting Company A". The electronic device first builds a task chain and divides the task of "visiting Company A" into multiple levels and nodes, such as "confirming the visit time", "sending a visit notice" and "actual visit". During the execution process, the electronic device will update the task chain in real time according to the behavioral data of the executing user. If the salesperson completes "confirming the visit time", the electronic device will update the completion status of the task and notify the salesperson to enter the next task node "sending a visit notice" in a preset order. If the behavioral data meets the triggering conditions of another task group (such as "product update notification task group"), the electronic device will automatically include the task group in the task chain to ensure that the relevant tasks are triggered on demand. In the entire execution chain, the electronic device will also send specific task execution instructions to the salesperson, such as "contact manager 1 after sending the visit notice", so as to ensure that the task is executed efficiently as planned. Finally, through the multi-level architecture and task chain status monitoring, the electronic device can dynamically manage complex task processes and improve the accuracy and execution efficiency of business management.

[0107] In general, the design of this solution realizes the functions of hierarchical management, real-time monitoring and dynamic expansion through the task nesting relationship architecture. It can not only effectively manage the multi-layer task process in complex business, but also adjust the task chain according to real-time data to enhance the flexibility of electronic equipment. At the same time, the transmission mechanism of task execution instructions ensures the accurate issuance of instructions and the consistency of task execution. This solution enables the business management system to complete various business tasks more efficiently and accurately when facing complex tasks and multi-user collaboration.

[0108] See also Figure 5 , Figure 5 is a structural diagram of a task management device provided in an embodiment of the present application. The embodiment of the present application also provides a task management device 500, which can implement the above-mentioned task management method. The device 500 includes:

[0109] An acquisition module 510 is used to acquire task information of a target business, where the task information is used to indicate at least one task group associated with the target business;

[0110] A construction module 520 is used to construct a task nesting relationship architecture associated with the target business based on the task information, wherein the task nesting relationship architecture includes at least one task chain, each task chain is associated with each task group, the task chain includes multiple levels of task nodes, and each task node of the previous level includes at least one task node of the next level, and the task nodes of the same level are arranged in parallel and / or serially;

[0111] The management module 530 is used to manage the task execution process of the target business based on the task nesting relationship architecture.

[0112] In some implementations, the task chain also includes completion status information of each task node. The management module 530 includes:

[0113] An acquisition unit, used to acquire user behavior data for each execution event;

[0114] The updating unit is used to update the completion status information of the execution event according to the user behavior data of each execution event.

[0115] In some embodiments, the apparatus 500 further comprises:

[0116] A comparison module, used to compare the behavior data with the trigger conditions of other task groups to obtain a comparison result, where the other task groups are task groups associated with the target business and not indicated by the task information;

[0117] The updating module is used to update the task nesting relationship architecture for other task groups when the comparison result indicates that the behavior data meets the triggering condition.

[0118] In some implementations, the task chain further includes completion status information of each task node, the multiple levels include a first target level and a second target level, the first target level is an upper level of the second target level, and the management module 530 includes:

[0119] A traversal unit, configured to, when the completion status information of the target task node of the first target level indicates that the target task node is not completed, traverse the target task nodes including the completion status information of the task nodes of the second target level;

[0120] The changing unit is used to change the completion status information of the target task node to the target task node being completed when the completion status information of the task nodes of the second target level included in each target task node all indicate that the corresponding task nodes have been completed.

[0121] In some implementations, the task nodes of the first target level are arranged in series based on the execution order of the task nodes of the first target level, and the management module 530 further includes:

[0122] A previous node determination unit, used to determine a previous task node of the target task node according to the execution order, the previous task node being a task node whose execution order is before the target task node;

[0123] A second traversal unit, used for traversing the completion status information of the previous task node;

[0124] Change unit, including:

[0125] The changing subunit changes the completion status information of the target task node to indicate that the target task node has been completed when the completion status information of the previous task node indicates that the previous task node has been completed.

[0126] In some embodiments, the management module 530 includes:

[0127] A generating unit, used for generating a task execution instruction by using the task chain;

[0128] The sending unit is used to send the task execution instruction to the execution user associated with the task group corresponding to the task chain.

[0129] The specific implementation of the task management device is basically the same as the specific implementation of the above-mentioned task management method, and will not be repeated here.

[0130] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned task management method when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a car computer, etc.

[0131] See also Figure 6 , Figure 6 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0132] The processor 601 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0133] The memory 602 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 602 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 602, and the processor 601 calls and executes the task management method of the embodiment of this application;

[0134] Input / output interface 603, used to implement information input and output;

[0135] Communication interface 604, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0136] Bus 605 , which transmits information between various components of the device (e.g., processor 601 , memory 602 , input / output interface 603 , and communication interface 604 );

[0137] The processor 601 , the memory 602 , the input / output interface 603 and the communication interface 604 are connected to each other in communication within the device via a bus 605 .

[0138] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the above-mentioned task management method is implemented.

[0139] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0140] The task management method, device, electronic device and medium provided in the embodiments of the present application, the electronic device constructs a task nesting relationship architecture, and the task nesting relationship architecture manages each task in a hierarchical manner according to the task chain associated with the target business, so that the electronic device can systematically organize and manage complex task chains in a unified and standardized manner, thereby improving the overall collaboration and data interaction efficiency, and at the same time realizing serial or parallel scheduling of task nodes at different levels during the business execution process, so that the electronic device performing business management can efficiently handle the dependencies between tasks at each level.

[0141] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0142] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0143] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0144] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0145] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0146] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0147] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0148] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0149] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0150] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0151] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A task management method, characterized in that: The method comprises: Acquire task information of a target business, where the task information is used to indicate at least one task group associated with the target business; Based on the task information, a task nesting relationship architecture associated with the target business is constructed, wherein the task nesting relationship architecture includes at least one task chain, each of the task chains is associated with each of the task groups, the task chain includes task nodes of multiple levels, and each task node of the upper level includes at least one task node of the lower level, and the task nodes of the same level are arranged in parallel and / or serially; Based on the task nesting relationship architecture, the task execution process of the target business is managed.

2. The method according to claim 1, characterized in that The multiple levels include a first level, a second level and a third level, the first level is the level above the second level, the second level is the level above the third level, the task nodes of the first level include the task group; the task nodes of the second level include at least one task associated with the task group; the task nodes of the third level include at least one execution event associated with the task.

3. The method according to claim 2, characterized in that The task chain also includes completion status information of each task node. The task execution process of the target business is managed based on the task nesting relationship architecture, including: Obtaining user behavior data for each of the execution events; According to the user behavior data of each of the execution events, the completion status information of the execution event is updated.

4. The method according to claim 3, characterized in that After acquiring the behavior data of the executing user of the executing node, the method further includes: Comparing the behavior data with trigger conditions of other task groups to obtain a comparison result, wherein the other task groups are task groups associated with the target business and not indicated by the task information; When the comparison result indicates that the behavior data meets the trigger condition, the task nesting relationship architecture is updated for the other task groups.

5. The method according to claim 1, characterized in that: The task chain also includes completion status information of each task node, the multiple levels include a first target level and a second target level, the first target level is an upper level of the second target level, and the task execution process of the target business is managed based on the task nesting relationship architecture, including: When the completion status information of the target task node of the first target level indicates that the target task node is not completed, the traversed target task nodes include the completion status information of the task nodes of the second target level; When the completion status information of the task nodes of the second target level included in each of the target task nodes indicates that the corresponding task nodes have been completed, the completion status information of the target task nodes is changed to "the target task nodes have been completed".

6. The method according to claim 5, characterized in that The task nodes of the first target level are arranged in series based on the execution order of the task nodes of the first target level. Before changing the completion status information of the target task node to the target task node being completed, the method further includes: Determine a previous task node of the target task node according to the execution order, the previous task node being a task node whose execution order is before the target task node; Traversing the completion status information of the previous task node; The step of changing the completion status information of the target task node to indicate that the target task node has been completed includes: When the completion status information of the previous task node indicates that the previous task node has been completed, the completion status information of the target task node is changed to indicate that the target task node has been completed.

7. The method according to claim 1, characterized in that The managing the task execution process of the target business based on the task nesting relationship architecture includes: generating a task execution instruction using the task chain; The task execution instruction is sent to an execution user associated with the task group corresponding to the task chain.

8. A task management device, characterized in that: The device comprises: An acquisition module, used to acquire task information of a target business, where the task information is used to indicate at least one task group associated with the target business; A construction module, configured to construct a task nesting relationship architecture associated with the target business based on the task information, wherein the task nesting relationship architecture includes at least one task chain, each of the task chains is associated with each of the task groups, the task chain includes task nodes of multiple levels, and each task node of the upper level includes at least one task node of the lower level, and the task nodes of the same level are arranged in parallel and / or in series; A management module is used to manage the task execution process of the target business based on the task nesting relationship architecture.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the task management method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the task management method according to any one of claims 1 to 7 is implemented.

Images