Task management method, routing distribution device, equipment and readable storage medium

Abstract

The present invention relates to the field of network communication technology, and in particular to a task management method, route allocation device, equipment, and readable storage medium, wherein the method comprises: when creating a task on a page, assigning a task identifier to the task; wherein the page is pre-configured with a parent route; generating a sub-route corresponding to the task based on the task identifier, wherein the sub-route is connected to a data set associated with the task; and performing management operations on the task through a component instance in the page based on the task identifier and the sub-route. By assigning a dedicated sub-route to each task through the task identifier, data independence between multiple component instances of the same component is achieved, and each task does not need to separately declare and create its own data state in the component's data management state to achieve independent management of data corresponding to each component instance associated with the task, thereby solving the problem of how to avoid affecting other tasks associated with the data of the task within the same component.

Description

Technical Field

[0001] The present invention relates to the field of network communication technology, and in particular to a task management method, a routing distribution device, equipment, and a readable storage medium. Background Art

[0002] Task management typically involves data connection and task scheduling. Data connection is primarily achieved through visualization (i.e., web pages) to save or connect to different data collection sources based on different instances. Task scheduling primarily involves scripting code to call different data connections for data cleansing and obtain the required data. It also supports scheduled scheduling, record saving, and full script execution for data collection and upload.

[0003] In traditional task management solutions, each web page usually includes multiple components, one component is associated with one or more tasks, and one or more tasks are managed through one component.

[0004] However, due to the inherent characteristics of the component, a component has only one data management state (a dataset object used to store the data used by the component). When multiple tasks exist within a component, the data between tasks within the component is not independent. When adding, deleting, or modifying a task within a component, it may affect other tasks within the same component that are associated with that task's data. For example, when Task A is modified within a component, the data associated with Task A will be modified accordingly. At this time, Task B, which has the same data as Task A, will also be passively modified, causing changes to Task B's scheduling content, or even causing it to fail to process normally.

[0005] The above content is only used to assist in understanding the technical solution of the present invention and does not constitute an admission that the above content is prior art. Summary of the Invention

[0006] The main purpose of the present invention is to provide a task management method, which aims to solve the problem of how to avoid affecting other tasks associated with the data of the task in the same component when adding, deleting or modifying a task in the component.

[0007] To achieve the above objectives, the present invention provides a task management method, which includes:

[0008] When creating a task on a page, assigning a task identifier to the task; wherein the page is pre-configured with a parent route;

[0009] Generating a sub-route corresponding to the task according to the task identifier, wherein the sub-route is connected to the data set associated with the task;

[0010] Based on the task identifier and the sub-route, a management operation is performed on the task through a component instance in the page.

[0011] Optionally, when creating a task on a page, before assigning a task identifier to the task, the process further includes:

[0012] Get the routing format generated by dynamic routing protocols;

[0013] A task identifier corresponding to the task is generated according to the routing format.

[0014] Optionally, the step of generating a sub-route corresponding to the task according to the task identifier includes:

[0015] After adding the task identifier to the parent route, the child route is obtained.

[0016] Optionally, before the step of performing a management operation on the task through a component instance in the page based on the task identifier and the sub-route, the method further includes:

[0017] Creating the component instance and putting the component instance into a cache for caching;

[0018] The component instance is associated with the task, so that the user can call the task corresponding to the component instance in the cache when performing a management operation.

[0019] Optionally, the management operation includes a task deletion operation, and the step of performing the management operation on the task through the component instance in the page based on the task identifier and the sub-route includes:

[0020] According to the task identifier, obtain the component instance and the sub-route corresponding to the task;

[0021] Delete the component instance in the page and delete the sub-route.

[0022] Optionally, after deleting the component instance in the page and deleting the sub-route, the method further includes:

[0023] Determine whether there are other tasks in the page, and if not, end the task deletion operation, wherein the other tasks are tasks in the page for which the task deletion operation has not been performed;

[0024] Otherwise, at least one of the other tasks is displayed on the page according to the task identifier.

[0025] Optionally, the management operation includes a task switching operation, and the step of performing the management operation on the task through a component instance in the page based on the task identifier and the sub-route includes:

[0026] Obtaining a target task identifier of a target switching task in the switching task instruction and a target rendering page of the component instance;

[0027] Determine the target sub-route corresponding to the target switching task according to the target task identifier;

[0028] Based on the target sub-route, the task in the component instance is switched to the target switching task, and the rendering page of the component instance is switched to the target rendering page.

[0029] In addition, to achieve the above-mentioned object, the present invention further provides a route distribution device, the route distribution device comprising:

[0030] Parent route creation module, used to create the parent route corresponding to the page;

[0031] A sub-route allocation module, configured to allocate sub-routes to tasks in the page according to a dynamic routing protocol;

[0032] A connection module is used to connect the parent route and the child route.

[0033] In addition, to achieve the above-mentioned purpose, the present invention also provides a task management device, the task management device comprising: a memory, a processor, and a task management program stored in the memory and executable on the processor, wherein the task management program, when executed by the processor, implements the various steps of the task management method described above.

[0034] In addition, to achieve the above-mentioned purpose, the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a task management program, and when the task management program is executed by a processor, the task management program implements the various steps of the task management method described in the above embodiment.

[0035] An embodiment of the present invention provides a task management method, device, route allocation device and readable storage medium. When creating a task on a page, a task identifier is assigned to the task, a sub-route of the task is generated according to the task identifier, and task management operations are performed on the task based on the task identifier and the sub-route. An exclusive sub-route is allocated to each task, thereby achieving data independence between multiple instances of the same component. Each task does not need to declare and create its own data state in the data management state of the component separately, so as to achieve independent management of the data corresponding to the component instance associated with each task. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A schematic diagram of the hardware architecture of a task management device according to an embodiment of the present invention;

[0037] Figure 2 This is a schematic diagram of a data set configuration page of a cloud platform in one embodiment of the present invention;

[0038] Figure 3 This is a schematic diagram of a task scheduling page of a cloud platform in one embodiment of the present invention;

[0039] Figure 4 A schematic diagram illustrating the relationship between pages and components of a Web application according to an embodiment of the present invention;

[0040] Figure 5 A schematic diagram of the structural relationship between conventional tasks and components of the present invention;

[0041] Figure 6 A schematic diagram of the structural relationship among tasks, page components, component instances, and data management status involved in an embodiment of the present invention;

[0042] Figure 7 A schematic diagram of the structural relationship between a multi-task component instance and a sub-route involved in an embodiment of the present invention;

[0043] Figure 8 This is a flowchart of a first embodiment of a task management method according to the present invention;

[0044] Figure 9 Schematic diagram of the flow of the second embodiment of the task management method of the present invention;

[0045] Figure 10 1 is a flow chart of a third embodiment of the task management method of the present invention;

[0046] Figure 11 FIG. 1 is a schematic diagram of the architecture of the routing distribution device of the present invention.

[0047] The purpose, features and advantages of the present invention will be further described with reference to the accompanying drawings and in conjunction with the embodiments. DETAILED DESCRIPTION

[0048] In this application, the task editing page uses the same component and implements a component instance caching mechanism. For all tasks created in this component, each task corresponds to an instance, which can contain task information and each instance has its own independent data management state.

[0049] In addition, the present application combines dynamic routing to manage each task under the same component. Since all tasks share a component and belong to the same page, they are associated with a common page route. When a new task is added, a unique ID is assigned to the task, and a new sub-route is automatically generated based on the task ID, so the sub-route is unique. Each task corresponds to a sub-route, which is used to associate the task with the corresponding component instance (including the data management status of the instance), and each sub-route is also associated with the same page, but different task component instances are associated with different task component instances through sub-routes under the page, and different instances have their own different data management status. Subsequently, when deleting or switching tasks, the instance is destroyed or switched according to the route to achieve independent management of the data corresponding to the component instance associated with each task.

[0050] In addition, when creating a new task, in addition to concatenating the parent route with the task ID, any other identifier that can uniquely match the task can be used to generate the route, including but not limited to the task name, the timestamp when the task was created, and other functions.

[0051] In addition, the data management state used by each component instance can be maintained by the instance itself or maintained globally or in other public places, and can be associated and used through unique identifiers that can be associated with tasks, such as task IDs and instance IDs.

[0052] It should be understood that the drawings of the present invention show exemplary embodiments of the present invention, and that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0053] As an implementation solution, the task management device can be as follows Figure 1 shown.

[0054] The embodiment of the present invention relates to a task management device, which includes a processor 101, such as a CPU, a memory 102, and a communication bus 103. The communication bus 103 is used to implement connection and communication between these components.

[0055] The memory 102 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory. Figure 1 As shown, the memory 102 as a computer-readable storage medium may include a task management program; and the processor 101 may be used to call the task management program stored in the memory 102 and perform the following operations:

[0056] When creating a task on a page, assigning a task identifier to the task; wherein the page is pre-configured with a parent route;

[0057] Generating a sub-route corresponding to the task according to the task identifier, wherein the sub-route is connected to the data set associated with the task;

[0058] Based on the task identifier and the sub-route, a management operation is performed on the task through a component instance in the page.

[0059] In one embodiment, the processor 101 may be configured to call a task management program stored in the memory 102 and perform the following operations:

[0060] Get the routing format generated by dynamic routing protocols;

[0061] A task identifier corresponding to the task is generated according to the routing format.

[0062] In one embodiment, the processor 101 may be configured to call a task management program stored in the memory 102 and perform the following operations:

[0063] After adding the task identifier to the parent route, the child route is obtained.

[0064] In one embodiment, the processor 101 may be configured to call a task management program stored in the memory 102 and perform the following operations:

[0065] Creating the component instance and putting the component instance into a cache for caching;

[0066] The component instance is associated with the task, so that the user can call the task corresponding to the component instance in the cache when performing a management operation.

[0067] In one embodiment, the processor 101 may be configured to call a task management program stored in the memory 102 and perform the following operations:

[0068] According to the task identifier, obtain the component instance and the sub-route corresponding to the task;

[0069] Delete the component instance in the page and delete the sub-route.

[0070] In one embodiment, the processor 101 may be configured to call a task management program stored in the memory 102 and perform the following operations:

[0071] Determine whether other tasks exist in the page, and if not, terminate the task deletion operation, wherein the other tasks are tasks in the page for which the task deletion operation has not been performed;

[0072] Otherwise, at least one of the other tasks is displayed on the page according to the task identifier.

[0073] In one embodiment, the processor 101 may be configured to call a task management program stored in the memory 102 and perform the following operations:

[0074] Obtaining a target task identifier of a target switching task in the switching task instruction and a target rendering page of the component instance;

[0075] Determine the target sub-route corresponding to the target switching task according to the target task identifier;

[0076] Based on the target sub-route, the task in the component instance is switched to the target switching task, and the rendering page of the component instance is switched to the target rendering page.

[0077] Based on the hardware architecture of the task management device based on the network communication technology, an embodiment of the task management method of the present invention is proposed.

[0078] With the gradual deepening of manufacturing automation and industrial Internet, industrial equipment is connected to the cloud platform, which can integrate various working condition data of industrial equipment and monitor and analyze the operating conditions of industrial equipment. Figure 2 and Figure 3 , Figure 2 This is a schematic diagram of a data set configuration page of a cloud platform in one embodiment of the present invention. Figure 3 This is a schematic diagram of the task scheduling page of the cloud platform in one embodiment of the present invention. Both are part of the data integration module in the cloud platform of this application, have data connection and task scheduling functions, and support adding, deleting, modifying and checking different data set configurations and scheduling tasks. Among them, the data connection mainly configures the relationship between the data acquisition source (i.e., the database) in a visual way, and saves records or connects to different data acquisition sources according to different configuration options. Task scheduling mainly uses script code to call different data connections for data cleaning to obtain the data required by the cloud platform. It also supports timed scheduling, record saving, and full execution of scripts to collect and upload data.

[0079] It should be noted that a web application contains multiple pages, each page has its own route, one route matches one page, and one page can contain multiple components. Specifically, the relationship between pages and components of a general web application is as follows: Figure 4As shown, a page is divided into multiple components based on similarities in internal display structure, style, etc. A component can be associated with one or more tasks. Since a component has only one data management state, the data called by each task is not independent but related. The traditional structural relationship between tasks and components is as follows: Figure 5 The drawback of this structure is that if a task A in the component is added, deleted, or modified, it will affect other tasks in the component that share common data with task A, and may cause the other tasks to fail to process normally.

[0080] In the implementation scheme involved in this application, the structural relationship between tasks and components, component instances and data management states is as follows: Figure 6 As shown in the figure, after the component is introduced, it is instantiated so that each component contains multiple component instances. Each component instance contains an independent data management state, and each data management state corresponds to a task. In this way, when performing operations on tasks, the data management of each task is independent of each other. Even if tasks share common data, they will not interfere with each other.

[0081] On the other hand, refer to Figure 7 This application dynamically assigns routes to tasks by dynamically generating routes, and then creates and associates different component instances. Different component instances each have their own data management status.

[0082] Reference Figure 8 In a first embodiment, the task management method includes the following steps:

[0083] Step S10, when creating a task on a page, assigning a task identifier to the task; wherein the page is pre-configured with a parent route;

[0084] In this embodiment, when a task is created, a unique task identifier is assigned to it. Optionally, the task identifier can be a coded ID containing numbers and / or letters. Using the task identifier, the routing device can quickly identify the task's corresponding dynamic routing. In subsequent data management operations, the task identifier serves as the task's unique "name," enabling operations to be performed on the task based on this "name."

[0085] Optionally, the task identifier may be generated by generating a routing format through a dynamic routing protocol, and determining the task identifier based on the routing format. A dynamic routing protocol is a protocol in which a router can establish its own routing table, generate and maintain the routing table required by the forwarding engine through the exchange of routing information. When the network topology changes, the dynamic routing protocol can automatically update the routing table and is responsible for determining the best path for data transmission. It has the advantages of not requiring manual maintenance by the administrator, thus reducing the administrator's workload; automatically determining the best route; and running a routing protocol on the router so that the router can automatically adjust routing entries according to changes in the network topology. The dynamic routing protocol can be a distance vector routing (DV) protocol or a link state routing (LS) protocol, or an interior gateway protocol (IGP) or an exterior gateway protocol (EGP), which is not limited in this embodiment.

[0086] Step S20, generating a sub-route corresponding to the task according to the task identifier, wherein the sub-route is connected to the data set associated with the task;

[0087] After assigning a task identifier to a task, the route assignment device identifies the task corresponding to the identifier based on the task identifier and dynamically generates a sub-route corresponding to the task. In this embodiment, each page contains multiple tasks. Since each page also needs to be assigned a route, this route is called a parent route. Based on this, the routes assigned to tasks on the same page are collectively referred to as sub-routes. Since the task identifier is unique, the corresponding generated route is also unique. The sub-routes corresponding to different tasks are also different. Of course, the sub-routes are also different from the parent route.

[0088] Tasks and their associated data sets are connected through subroutes. Because each task is assigned a different subroute, meaning each task's data channels are independent, data interactions between tasks will not interfere with each other when performing task-related management operations through subroutes. Therefore, executing a management operation on one task will not affect other tasks that share the same data, thus enabling independent management of the data associated with each task's component instance.

[0089] Optionally, in this embodiment, the sub-route is also connected to the parent route of the page where the task corresponding to the sub-route is located, that is, the parent route is nested with multiple sub-routes. When performing management operations on the tasks in the page, the data in the page also needs to be updated accordingly. For example, in a data set configuration page, the back-end data set is configured through components. At this time, not only the components need to be connected to the data set, but the page also needs to be connected to the components. When the user configures the data set, he needs to perform operations on multiple components in the data set configuration page. The parent route of the page acts as a general data channel, sending data for all operations of the data set configuration to the data set back-end, and the sub-route of each component acts as a sub-channel, allocating the content entered by the user in each component to the data subset corresponding to each component, thereby realizing data processing of the back-end at the front end.

[0090] Step S30: Based on the task identifier and the sub-route, a management operation is performed on the task through a component instance in the page.

[0091] After the sub-route corresponding to the task is generated according to the task identifier, relevant operations of task management can be performed on the tasks corresponding to the task identifier and the sub-route based on the task identifier and the sub-route.

[0092] Optionally, in order to be able to call component instances quickly and conveniently when performing management operations on tasks, a component instance caching mechanism is added before this step, the component instance is created in advance, and the component instance is cached in the cache allocated in the page. When it is necessary to perform management operations on the task, the component instance stored in the cache can be directly called, and the component instance can be associated with the task, so that the user can manage the task through the component instance.

[0093] In the technical solution provided in this embodiment, when creating a task on a page, a task identifier is assigned to the task, a sub-route of the task is generated according to the task identifier, and task management operations are performed on the task based on the task identifier and the sub-route. An exclusive sub-route is assigned to each task to achieve data independence between multiple instances of the same component. Each task does not need to declare and create its own data state in the component's data management state separately, so as to achieve independent management of the data corresponding to each component instance associated with each task.

[0094] Reference Figure 9 In the second embodiment, based on the first embodiment, step S30 includes:

[0095] Step S31, obtaining the component instance and the sub-route corresponding to the task according to the task identifier;

[0096] Step S32: Delete the component instance in the page and delete the sub-route.

[0097] Optionally, this embodiment provides a method for deleting tasks. The user selects the task to be deleted on the front-end page and clicks the Delete button for the task. A deletion confirmation pop-up window appears on the front-end. After the user clicks Confirm Delete, the front-end matches the task ID with the component instance and route corresponding to the task, destroys the instance, and deregisters the route.

[0098] After step S32, the method further includes:

[0099] Step S40, determining whether there are other tasks in the page, and if not, ending the task deletion operation, wherein the other tasks are tasks in the page that have not been subjected to the task deletion operation;

[0100] Step S50: otherwise, display at least one of the other tasks on the page.

[0101] Optionally, after executing the deletion operation, this embodiment can also rearrange the page based on the remaining tasks. First, the front end detects the task identifier in the page and determines whether there are other tasks based on whether the task identifier exists. If not, the operation ends, and the area on the page used to display tasks is displayed as blank; otherwise, after deleting the task, the sequence number of the deleted task is first determined. If it is the first task, the next task is retrieved and replaced with the next task in the display area where the deleted task is located for display; otherwise, the previous task is retrieved and replaced with the previous task in the display area where the deleted task is located for display; the front end obtains the task ID based on the retrieved task, matches and obtains the corresponding cached component instance and route; switches and initializes the instance (including data management status), thereby automatically displaying other tasks on the page.

[0102] In the technical solution provided by this embodiment, the sub-route and component instance corresponding to a task are determined by the task identifier. Therefore, when deleting a task, the component instance associated with the task is accurately matched, and the instance and its associated data are destroyed without affecting the sub-routes and task instances of other tasks. This avoids deleting other tasks that share common data with the deleted task when a component instance on a page is associated with multiple tasks. Furthermore, after deleting a task, the remaining tasks on the page are automatically typeset, improving the efficiency of task management.

[0103] Reference Figure 10 In the third embodiment, based on the first embodiment, step S30 includes:

[0104] Step S33, obtaining the target task identifier of the target switching task in the switching task instruction and the target rendering page of the component instance;

[0105] Step S34, determining the target sub-route corresponding to the target switching task according to the target task identifier;

[0106] Step S35: Based on the target sub-route, the task in the component instance is switched to the target switching task, and the rendering page of the component instance is switched to the target rendering page.

[0107] Optionally, this embodiment provides a method for switching tasks. After the user clicks on the task to be switched on the page, a switching task instruction is generated. The front end of the page obtains the target task identifier of the target switching task in the switching task instruction and the target rendering page of the component instance; the front end matches and obtains the target sub-route of the corresponding cached target component instance based on the target task identifier; then switches and initializes the component instance (including the data management status of the instance), and renders the page to display the corresponding task content, thereby switching the task and task data corresponding to the component instance.

[0108] In the technical solution provided by this embodiment, the target task identifier of the target switching task and the target rendering page to which the component instance corresponding to the instruction needs to be switched are obtained through the switching task instruction. The target sub-route corresponding to the target switching task is determined based on the target task identifier, and the task and the component instance of the task are switched through the target sub-route. Therefore, when switching tasks, the component instance associated with the task is accurately matched, and then the instance and its associated data are switched, without affecting the sub-routes and task instances of other tasks. This avoids the situation where other tasks that have common data with the switched task are also switched when the component instance in the page is associated with multiple tasks.

[0109] In addition, refer to Figure 11 This embodiment further provides a route distribution device, the route distribution device comprising:

[0110] The parent route creation module 100 is used to create the parent route corresponding to the page;

[0111] The sub-route allocation module 200 is used to allocate sub-routes to tasks in the page according to a dynamic routing protocol;

[0112] The connection module 300 is used to connect the parent route and the child route.

[0113] Those skilled in the art will appreciate that all or part of the steps in the method of the above-described embodiment can be implemented by instructing the relevant hardware through a computer program. The computer program includes program instructions, which can be stored in a storage medium that is computer-readable. The program instructions are executed by at least one processor in the task management device to implement the steps of the above-described method embodiment.

[0114] Therefore, the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a task management program, and when the task management program is executed by a processor, the task management program implements the various steps of the task management method described in the above embodiment.

[0115] The computer-readable storage medium may be any computer-readable storage medium that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk.

[0116] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0117] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a computer-readable storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0118] The above are only preferred embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention description and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A task management method, characterized in that: The method comprises: When creating a task on a page, assigning a task identifier to the task, wherein the page is pre-configured with a parent route; Generating a sub-route corresponding to the task according to the task identifier, wherein the sub-route is connected to the data set associated with the task; Based on the task identifier and the sub-route, a management operation is performed on the task through a component instance in the page; each component instance includes an independent data management state, and each data management state corresponds to a task; The management operation includes a task switching operation, and the step of performing the management operation on the task through the component instance in the page based on the task identifier and the sub-route includes: Obtaining a target task identifier of a target switching task in the switching task operation and a target rendering page of the component instance; Determine the target sub-route corresponding to the target switching task according to the target task identifier; Based on the target sub-route, the task in the component instance is switched to the target switching task, and the rendering page of the component instance is switched to the target rendering page.

2. The task management method according to claim 1, wherein: When creating a task on a page, before the step of assigning a task identifier to the task, the step further includes: Get the routing format generated by dynamic routing protocols; A task identifier corresponding to the task is generated according to the routing format.

3. The task management method according to claim 1, wherein: The step of generating a sub-route corresponding to the task according to the task identifier includes: After adding the task identifier to the parent route, the child route is obtained.

4. The task management method according to claim 1, wherein: Before the step of performing a management operation on the task through a component instance in the page based on the task identifier and the sub-route, the step further includes: Creating the component instance and putting the component instance into a cache for caching; The component instance is associated with the task, so that the user can call the task corresponding to the component instance in the cache when performing a management operation.

5. The task management method according to claim 1, wherein: The management operation includes a task deletion operation, and the step of performing the management operation on the task through the component instance in the page based on the task identifier and the sub-route includes: According to the task identifier, obtain the component instance and the sub-route corresponding to the task; Delete the component instance in the page and delete the sub-route.

6. The task management method according to claim 5, wherein: After the steps of deleting the component instance in the page and deleting the sub-route, the method further includes: Determine whether there are other tasks in the page, and if not, end the task deletion operation, wherein the other tasks are tasks in the page for which the task deletion operation has not been performed; Otherwise, at least one of the other tasks is displayed on the page according to the task identifier.

7. A routing distribution device, characterized in that: The routing distribution device is configured to perform the steps of the task management method according to any one of claims 1 to 6, and the routing distribution device includes: Parent route creation module, used to create the parent route corresponding to the page; A sub-route allocation module, configured to allocate sub-routes to tasks in the page according to a dynamic routing protocol; A connection module is used to connect the parent route and the child route.

8. A task management device, characterized in that: The task management device includes: a memory, a processor, and a task management program stored in the memory and executable on the processor. When the task management program is executed by the processor, the steps of the task management method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a task management program, which, when executed by a processor, implements the steps of the task management method according to any one of claims 1 to 6.

Images