Task flow processing method and device, equipment, medium and program product
By enabling bidirectional synchronization between the operation and maintenance layer and the management operation layer, and displaying data in different formats, the problems of high cost and long cycle of task flow updates are solved, achieving efficient task flow updates and data synchronization.
Patent Information
- Application Number
- CN202511758533.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-26
- Publication Date
- 2026-02-24
AI Technical Summary
The creation and configuration of task flows need to be customized based on the organizational structure and specific business needs, resulting in insufficient versatility, high update costs, and long cycles.
The task flow is updated through two operation entry points: the operation and maintenance layer and the management operation layer. Synchronization is achieved with the help of the task database. The operation and maintenance layer displays the task flow in a list format, while the management operation layer displays it in a view format, adapting to the operation habits of different operation layers.
It improves the efficiency of task flow updates and data synchronization, reduces operational burden and learning costs, and supports flexible configuration and real-time viewing of task processes.
Smart Images
Figure CN121560903A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a task flow processing method, apparatus, device, medium, and program product. Background Technology
[0002] Currently, the creation and configuration of task flows need to be customized based on the organizational structure and specific business requirements. This results in insufficient versatility of task flows, which often requires adaptive adjustments based on the organizational structure and specific business requirements, leading to high update costs and long update cycles.
[0003] Therefore, how to improve the update efficiency of task flow is a problem that needs to be solved by those skilled in the art. Summary of the Invention
[0004] In view of this, the purpose of this application is to provide a task flow processing method, apparatus, device, medium and program product to improve the update efficiency of task flow.
[0005] Firstly, this application provides a task flow processing method, including:
[0006] In response to the update request for the target task flow from the operation and maintenance layer, the target task flow is updated to obtain a first task flow, and the first task flow is recorded in the task database;
[0007] The first task flow in the task database is synchronized to the management operation layer, and the first task flow is displayed in the management operation layer in view format.
[0008] In response to the update request from the management operation layer for the first task flow, the first task flow is updated to obtain a second task flow, and the second task flow is recorded in the task database;
[0009] The second task flow in the task database is synchronized to the operation and maintenance layer, and the second task flow is displayed in the operation and maintenance layer in a list format.
[0010] Optionally, in response to an update request from the operations and maintenance layer for the target task flow, the target task flow is updated, including:
[0011] Based on the update request for the target task flow from the operation and maintenance layer, the corresponding target update item is determined; the target update item includes at least one of: node addition, node deletion, and node modification;
[0012] Execute the target update item for the target task flow.
[0013] Optionally, in response to the update request from the management operation layer for the first task flow, the first task flow is updated, including:
[0014] Based on the update request from the management operation layer for the first task flow, a corresponding first update item is determined; the first update item includes at least one of task initiation and node approval.
[0015] The first update item is executed for the first task flow.
[0016] Optionally, it also includes:
[0017] In response to a query request from the operation and maintenance layer for any task flow, the corresponding task flow is displayed in a list format in the operation and maintenance layer.
[0018] In response to a query request from the management operation layer for any task flow, the corresponding task flow is displayed in the management operation layer in a view format.
[0019] Optionally, it also includes:
[0020] Each task flow in the task database is labeled with a corresponding update timestamp.
[0021] Optionally, it also includes:
[0022] The task database records the correspondence between the target task flow, the first task flow, and the second task flow, and sorts the target task flow, the first task flow, and the second task flow according to their respective update timestamps.
[0023] Secondly, this application provides a task flow processing apparatus, comprising:
[0024] The first update module is used to respond to the update request of the operation and maintenance layer for the target task flow, update the target task flow to obtain the first task flow, and record the first task flow to the task database.
[0025] The first synchronization module is used to synchronize the first task flow in the task database to the management operation layer, and display the first task flow in the management operation layer in a view format.
[0026] The second update module is used to update the first task flow in response to the update request from the management operation layer to the first task flow, obtain the second task flow, and record the second task flow in the task database.
[0027] The second synchronization module is used to synchronize the second task flow in the task database to the operation and maintenance layer, and display the second task flow in the operation and maintenance layer in a list format.
[0028] Optionally, the first update module is specifically used for:
[0029] Based on the update request for the target task flow from the operation and maintenance layer, the corresponding target update item is determined; the target update item includes at least one of: node addition, node deletion, and node modification;
[0030] Execute the target update item for the target task flow.
[0031] Optionally, the second update module is specifically used for:
[0032] Based on the update request from the management operation layer for the first task flow, a corresponding first update item is determined; the first update item includes at least one of task initiation and node approval.
[0033] The first update item is executed for the first task flow.
[0034] Optionally, it also includes:
[0035] The query module is used to respond to the query request of the operation and maintenance layer for any task flow, and to display the corresponding task flow in the operation and maintenance layer in a list format; and to respond to the query request of the management operation layer for any task flow, to display the corresponding task flow in the management operation layer in a view format.
[0036] Optionally, it also includes:
[0037] The annotation module is used to annotate each task flow in the task database with a corresponding update timestamp.
[0038] Optionally, it also includes:
[0039] The management module is used to record the correspondence between the target task flow, the first task flow, and the second task flow in the task database, and to sort the target task flow, the first task flow, and the second task flow according to their respective update timestamps.
[0040] Thirdly, this application provides an electronic device, comprising:
[0041] Memory, used to store computer programs;
[0042] A processor is used to execute the computer program to implement the aforementioned disclosed task flow processing method.
[0043] Fourthly, this application provides a non-volatile storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned task flow processing method.
[0044] Fifthly, this application provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the aforementioned disclosed task flow processing method.
[0045] As can be seen from the above scheme, this application provides a task flow processing method, including: responding to an update request from the operation and maintenance layer for a target task flow, updating the target task flow to obtain a first task flow, and recording the first task flow in a task database; synchronizing the first task flow in the task database to the management operation layer, and displaying the first task flow in the management operation layer in a view format; responding to an update request from the management operation layer for the first task flow, updating the first task flow to obtain a second task flow, and recording the second task flow in the task database; synchronizing the second task flow in the task database to the operation and maintenance layer, and displaying the second task flow in the operation and maintenance layer in a list format.
[0046] As can be seen, the beneficial effects of this application are as follows: Through two operation entry points—the operation and maintenance layer and the management operation layer—the same task flow can be updated, and the update operations performed by the two operation entry points can be synchronized with each other. That is, updates to any task flow by the operation and maintenance layer and the management operation layer are recorded in the task database accordingly. Thus, the task database enables the synchronization of updates to the same task flow across different operation entry points. Furthermore, displaying the task flow in different formats in the operation and maintenance layer and the management operation layer better suits the habits of operators in both operation layers, which is beneficial for improving work efficiency. For example, managers may prefer visual, WYSIWYG flowcharts, so the task flow can be displayed in a view format in the management operation layer; operation and maintenance personnel may be more sensitive to tabular data, so the task flow can be displayed in a list format in the operation and maintenance layer, which facilitates batch updates of nodes in the task flow and improves the update efficiency and data synchronization efficiency of the task flow.
[0047] Correspondingly, the task flow processing device, equipment, medium, and program product provided in this application also have the above-mentioned technical effects. Attached Figure Description
[0048] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0049] Figure 1 This is a flowchart of a task flow processing method disclosed in this application;
[0050] Figure 2 This is a schematic diagram of a task flow processing scheme disclosed in this application;
[0051] Figure 3 This is a schematic diagram of a task flow processing device disclosed in this application;
[0052] Figure 4 This is a schematic diagram of an electronic device disclosed in this application;
[0053] Figure 5 A server architecture diagram provided for this application;
[0054] Figure 6 A terminal structure diagram provided for this application. Detailed Implementation
[0055] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.
[0056] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.
[0057] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0058] Currently, task flow creation and configuration require customization based on organizational structure and specific business needs. This results in insufficient versatility, frequently necessitating adaptive adjustments based on organizational structure and business requirements, leading to high update costs and long update cycles. To address this, this application provides a task flow processing solution that enables updates to the same task flow through two operation entry points: an operations layer and a management layer. The update operations performed by these two entry points can be synchronized using a task database. Furthermore, this solution displays the task flow in different formats at the operations layer and the management layer, better adapting to the habits of operators at both layers and improving both work efficiency and task flow update efficiency.
[0059] See Figure 1 As shown in the figure, this application discloses a task flow processing method, including:
[0060] S101. In response to the update request for the target task flow from the operation and maintenance layer, update the target task flow to obtain the first task flow, and record the first task flow in the task database.
[0061] This embodiment provides two operation entry points: the operation and maintenance operation layer and the management operation layer. This embodiment allows updates to the same task flow through both the operation and maintenance operation layer and the management operation layer, and the update operations performed by the two entry points can be synchronized using the task database. The operation and maintenance operation layer is used to create and configure task flows.
[0062] In one implementation, in response to an update request from the operations and maintenance layer for the target task flow, the target task flow is updated, including: determining corresponding target update items based on the update request from the operations and maintenance layer; the target update items include at least one of: node addition, node deletion, and node modification; and executing the target update items for the target task flow. Node modifications include: changes to node names, changes to node permissions, etc.
[0063] S102. Synchronize the first task flow in the task database to the management operation layer, and display the first task flow in the management operation layer in view format.
[0064] S103. In response to the update request from the management operation layer for the first task flow, update the first task flow to obtain the second task flow, and record the second task flow in the task database.
[0065] In one example, the management operation layer is used to implement the use of task flows, such as initiating task flows and approving task flow nodes. In one implementation, in response to an update request from the management operation layer for a first task flow, the first task flow is updated, including: determining a corresponding first update item based on the update request from the management operation layer for the first task flow; the first update item includes at least one of task initiation and node approval; and executing the first update item for the first task flow.
[0066] S104. Synchronize the second task flow from the task database to the operation and maintenance layer, and display the second task flow in the operation and maintenance layer in a list format.
[0067] Since the operations and maintenance layer and the management operations layer are bound to the same data source (i.e., the task database), both the operations and maintenance layer and the management operations layer can query the task database. Therefore, in response to a query request from the operations and maintenance layer for any task flow, the corresponding task flow is displayed in a list format in the operations and maintenance layer; in response to a query request from the management operations layer for any task flow, the corresponding task flow is displayed in a view format in the management operations layer.
[0068] It's worth noting that displaying task flows in different formats at the operations and maintenance (O&M) and management (MAG) levels better suits the habits of operators at both levels, thus improving work efficiency. For example, if administrators prefer visual, WYSIWYG flowcharts, then displaying task flows in a view format at the MAG level; if O&M personnel are more sensitive to tabular data, then displaying task flows in a list format at the O&M level facilitates batch updates of nodes within the task flow, improving update and data synchronization efficiency.
[0069] To achieve effective management of various task flows in the task database, this embodiment also supports: marking each task flow in the task database with a corresponding update timestamp. In the task database, the correspondence between the target task flow, the first task flow, and the second task flow is recorded, and the target task flow, the first task flow, and the second task flow are sorted according to their respective update timestamps.
[0070] As can be seen, this embodiment, through two operation entry points—the operation and maintenance layer and the management operation layer—allows for updates to the same task flow. Furthermore, the update operations performed by the two entry points are synchronized. Specifically, updates to any task flow by the operation and maintenance layer and the management operation layer are recorded in the task database. This leverages the task database to achieve synchronized updates of the same task flow across different operation entry points. Moreover, the different display formats of the task flow in the operation and maintenance layer and the management operation layer better suit the habits of operators at both layers, thus improving work efficiency. For example, managers may prefer visual, WYSIWYG flowcharts, so the task flow is displayed in a view format in the management operation layer; operation and maintenance personnel may be more sensitive to tabular data, so the task flow is displayed in a list format in the operation and maintenance layer. This facilitates batch updates of nodes within the task flow, improving update efficiency and data synchronization efficiency.
[0071] Please see Figure 2 , Figure 2 This example demonstrates the specific operations supported by the operation and maintenance layer and the management operation layer, respectively. Specifically, Figure 2 The business layer is the operation and maintenance layer, and the visualization layer is the management and operation layer. The business layer allows for flexible configuration of each task node in the task flow, such as changing node names, roles, and permissions, to adapt the task flow to the organizational structure and specific business needs. The visualization layer provides a streamlined view of the task flow configured in the business layer and supports business operations such as node querying, task initiation, node approval, node rollback, and node annotation.
[0072] It's important to note that the business layer and the visualization layer are bidirectionally bound, accessing the same database. The business layer displays the task flow as a list, while the visualization layer displays it as a view. In other words, the business layer and visualization layer use different formats to display the same task flow, which better suits the habits of operators at both operational layers, thus improving work efficiency. For example, administrators might prefer visual, WYSIWYG flowcharts, so the task flow is displayed as a view in the management operational layer; operations and maintenance personnel might be more sensitive to tabular data, so the task flow is displayed as a list in the operations and maintenance operational layer. This facilitates batch updates of nodes within the task flow, improving update and data synchronization efficiency.
[0073] The task flow visualization interface and related browser-level operations can be implemented based on WebGL technology. At the same time, the underlying code will bind each business process to the visualization interface in two ways to achieve different forms of display of the same data source.
[0074] As can be seen, this embodiment unifies business logic with visualization, reducing operational burden and learning costs. It also supports flexible configuration of business processes, real-time viewing of task flow and processing time. The business layer and visualization layer are bidirectionally data-bound and synchronized, eliminating the need for secondary coding. Network interaction and data synchronization require fewer resources, resulting in higher efficiency.
[0075] The following describes a task flow processing apparatus provided by an embodiment of this application. The task flow processing apparatus described below can be referred to in conjunction with other embodiments described herein.
[0076] See Figure 3 As shown in the figure, this application discloses a task flow processing apparatus, including:
[0077] The first update module 301 is used to respond to the update request of the operation and maintenance layer for the target task flow, update the target task flow, obtain the first task flow, and record the first task flow to the task database;
[0078] The first synchronization module 302 is used to synchronize the first task flow in the task database to the management operation layer and display the first task flow in the management operation layer in a view format.
[0079] The second update module 303 is used to respond to the update request of the management operation layer for the first task flow, update the first task flow to obtain the second task flow, and record the second task flow to the task database.
[0080] The second synchronization module 304 is used to synchronize the second task flow in the task database to the operation and maintenance layer, and display the second task flow in the operation and maintenance layer in a list format.
[0081] In one implementation, the first update module is specifically used for:
[0082] Based on the update request for the target task flow from the operation and maintenance layer, determine the corresponding target update items; the target update items include at least one of the following: node addition, node deletion, and node modification;
[0083] Execute target update items for the target task flow.
[0084] In one implementation, the second update module is specifically used for:
[0085] Based on the update request from the management operation layer for the first task flow, determine the corresponding first update item; the first update item includes at least one of task initiation and node approval;
[0086] Execute the first update item for the first task flow.
[0087] In one implementation, it further includes:
[0088] The query module is used to respond to query requests from the operations and maintenance layer for any task flow and display the corresponding task flow in a list format in the operations and maintenance layer; and to respond to query requests from the management layer for any task flow and display the corresponding task flow in a view format in the management layer.
[0089] In one implementation, it further includes:
[0090] The annotation module is used to annotate each task flow in the task database with the corresponding update timestamp.
[0091] In one implementation, it further includes:
[0092] The management module is used to record the correspondence between the target task flow, the first task flow, and the second task flow in the task database, and to sort the target task flow, the first task flow, and the second task flow according to their respective update timestamps.
[0093] For more detailed information on the working process of each module and unit in this embodiment, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.
[0094] As can be seen, this embodiment provides a task flow processing device that can update the same task flow through two operation entry points: the operation and maintenance operation layer and the management operation layer. The update operations performed by the two operation entry points can be synchronized with the task database. This solution also displays the task flow in different formats in the operation and maintenance operation layer and the management operation layer, which is more adaptable to the habits of operators in the two operation layers and helps to improve work efficiency and task flow update efficiency.
[0095] The following describes an electronic device provided by an embodiment of this application. The electronic device described below can be referred to in conjunction with other embodiments described herein.
[0096] See Figure 4 As shown in the figure, an embodiment of this application discloses an electronic device, including:
[0097] Memory 401 is used to store computer programs;
[0098] Processor 402 is configured to execute the computer program to implement the method disclosed in any of the above embodiments.
[0099] In this embodiment, when the processor executes the computer program stored in the memory, it can specifically implement the following steps: in response to the update request of the operation and maintenance layer for the target task flow, the target task flow is updated to obtain a first task flow, and the first task flow is recorded in the task database; the first task flow in the task database is synchronized to the management operation layer, and the first task flow is displayed in the management operation layer in a view format; in response to the update request of the management operation layer for the first task flow, the first task flow is updated to obtain a second task flow, and the second task flow is recorded in the task database; the second task flow in the task database is synchronized to the operation and maintenance layer, and the second task flow is displayed in the operation and maintenance layer in a list format.
[0100] In this embodiment, when the processor executes the computer program stored in the memory, it can specifically implement the following steps: determine the corresponding target update item according to the update request of the operation and maintenance layer for the target task flow; the target update item includes at least one of node addition, node deletion and node modification; execute the target update item for the target task flow.
[0101] In this embodiment, when the processor executes the computer program stored in the memory, it can specifically implement the following steps: determining the corresponding first update item according to the update request of the management operation layer for the first task flow; the first update item includes at least one of task initiation and node approval; and executing the first update item for the first task flow.
[0102] In this embodiment, when the processor executes the computer program stored in the memory, it can specifically implement the following steps: in response to a query request from the operation and maintenance layer for any task flow, display the corresponding task flow in the operation and maintenance layer in a list format; in response to a query request from the management operation layer for any task flow, display the corresponding task flow in the management operation layer in a view format.
[0103] In this embodiment, when the processor executes the computer program stored in the memory, it can specifically implement the following steps: marking each task flow in the task database with a corresponding update timestamp.
[0104] In this embodiment, when the processor executes the computer program stored in the memory, it can specifically implement the following steps: in the task database, record the correspondence between the target task flow, the first task flow, and the second task flow, and sort the target task flow, the first task flow, and the second task flow according to the update timestamps corresponding to the target task flow, the first task flow, and the second task flow respectively.
[0105] Furthermore, embodiments of this application also provide an electronic device. The aforementioned electronic device can be, for example,... Figure 5 The server shown can also be as follows: Figure 6 The terminal shown. Figure 5 and Figure 6 These are all diagrams illustrating the structure of an electronic device according to an exemplary embodiment. The content in the diagrams should not be considered as any limitation on the scope of this application.
[0106] Figure 5 This is a schematic diagram of a server structure provided in an embodiment of this application. The server may specifically include: at least one processor, at least one memory, a power supply, a communication interface, an input / output interface, and a communication bus. The memory stores a computer program, which is loaded and executed by the processor to implement the relevant steps in the task flow processing disclosed in any of the foregoing embodiments.
[0107] In this embodiment, the power supply is used to provide operating voltage for each hardware device on the server; the communication interface can create a data transmission channel between the server and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.
[0108] In addition, the memory, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored on it include operating system, computer programs and data, etc., and the storage method can be temporary storage or permanent storage.
[0109] The operating system is used to manage and control the various hardware devices and computer programs on the server, enabling the processor to perform operations and processes on the data in the memory. It can be Windows Server, Netware, Unix, Linux, etc. In addition to computer programs capable of performing the task flow processing methods disclosed in any of the foregoing embodiments, the computer programs may further include computer programs capable of performing other specific tasks. The data may include application update information and application developer information.
[0110] Figure 6 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal may include, but is not limited to, a smartphone, tablet computer, laptop computer, or desktop computer.
[0111] Typically, the terminal in this embodiment includes a processor and a memory.
[0112] The processor may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor can be implemented using at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), or PLA (Programmable Logic Array). The processor may also include a main processor and coprocessors. The main processor, also known as the CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor may also include an AI (Artificial Intelligence) processor, which handles computational operations related to machine learning.
[0113] The memory may include one or more computer non-volatile storage media, which may be non-transitory. The memory may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory is used to store at least the following computer programs, which, after being loaded and executed by the processor, are capable of implementing the relevant steps in the task flow processing method executed by the terminal side as disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory may also include operating systems and data, and the storage method may be temporary or permanent storage. The operating system may include Windows, Unix, Linux, etc. The data may include, but is not limited to, application update information.
[0114] In some embodiments, the terminal may further include a display screen, an input / output interface, a communication interface, a sensor, a power supply, and a communication bus.
[0115] Those skilled in the art will understand that Figure 6 The structure shown does not constitute a limitation on the terminal and may include more or fewer components than illustrated.
[0116] The following describes a non-volatile storage medium provided in an embodiment of this application. The non-volatile storage medium described below can be referred to in conjunction with other embodiments described herein.
[0117] A non-volatile storage medium is provided for storing a computer program, wherein the computer program, when executed by a processor, implements the task flow processing method disclosed in the foregoing embodiments. The non-volatile storage medium is a computer-readable non-volatile storage medium, which, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored thereon include an operating system, computer programs, and data, and the storage method can be temporary storage or permanent storage.
[0118] The following describes a computer program product provided by an embodiment of this application. The computer program product described below can be referred to in conjunction with other embodiments described herein.
[0119] A computer program product includes a computer program / instructions that, when executed by a processor, implement the steps of the aforementioned disclosed task flow processing method.
[0120] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the steps in any of the above embodiments.
[0121] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.
[0122] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of non-volatile storage medium known in the art.
[0123] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only intended to help understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A task flow processing method, characterized in that, include: In response to the update request for the target task flow from the operation and maintenance layer, the target task flow is updated to obtain a first task flow, and the first task flow is recorded in the task database; The first task flow in the task database is synchronized to the management operation layer, and the first task flow is displayed in the management operation layer in view format. In response to the update request from the management operation layer for the first task flow, the first task flow is updated to obtain a second task flow, and the second task flow is recorded in the task database; The second task flow in the task database is synchronized to the operation and maintenance layer, and the second task flow is displayed in the operation and maintenance layer in a list format.
2. The method according to claim 1, characterized in that, In response to an update request from the operations and maintenance layer for the target task flow, the target task flow is updated, including: Based on the update request for the target task flow from the operation and maintenance layer, the corresponding target update item is determined; the target update item includes at least one of: node addition, node deletion, and node modification; Execute the target update item for the target task flow.
3. The method according to claim 1, characterized in that, In response to the update request from the management operation layer for the first task flow, the first task flow is updated, including: Based on the update request from the management operation layer for the first task flow, a corresponding first update item is determined; the first update item includes at least one of task initiation and node approval. The first update item is executed for the first task flow.
4. The method according to claim 1, characterized in that, Also includes: In response to a query request from the operation and maintenance layer for any task flow, the corresponding task flow is displayed in a list format in the operation and maintenance layer. In response to a query request from the management operation layer for any task flow, the corresponding task flow is displayed in the management operation layer in a view format.
5. The method according to claim 1, characterized in that, Also includes: Each task flow in the task database is labeled with a corresponding update timestamp.
6. The method according to any one of claims 1-5, characterized in that, Also includes: The task database records the correspondence between the target task flow, the first task flow, and the second task flow, and sorts the target task flow, the first task flow, and the second task flow according to their respective update timestamps.
7. A task flow processing apparatus, characterized in that, include: The first update module is used to respond to the update request of the operation and maintenance layer for the target task flow, update the target task flow to obtain the first task flow, and record the first task flow to the task database. The first synchronization module is used to synchronize the first task flow in the task database to the management operation layer, and display the first task flow in the management operation layer in a view format. The second update module is used to update the first task flow in response to the update request from the management operation layer to the first task flow, obtain the second task flow, and record the second task flow in the task database. The second synchronization module is used to synchronize the second task flow in the task database to the operation and maintenance layer, and display the second task flow in the operation and maintenance layer in a list format.
8. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the method as claimed in any one of claims 1 to 6.
9. A non-volatile storage medium, characterized in that, Used to store a computer program, wherein the computer program, when executed by a processor, implements the method as described in any one of claims 1 to 6.
10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the method described in any one of claims 1 to 6.