Publishing process processing method and device, computer device and storage medium

Abstract

The application relates to a publishing process processing method and device, computer equipment and a storage medium. The method comprises the following steps: receiving an editing request for a flowchart of a target publishing plan sent by at least one terminal in a plurality of terminals; the plurality of terminals respectively display a flowchart of the target publishing plan and a publishing plan state of the target publishing plan; based on the editing request, the flowchart of the target publishing plan displayed by the plurality of terminals is synchronously updated; a historical task connection relationship set is used to check a connection relationship between task nodes in the flowchart of the target publishing plan; in the case that the connection relationship is found to be abnormal, connection relationship abnormality prompt information is sent to the plurality of terminals; and in response to a plan state change request for the target publishing plan, the publishing plan state of the target publishing plan displayed by the plurality of terminals is updated. The method can improve the processing efficiency of the publishing plan.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a publishing process processing method, apparatus, computer equipment, and storage medium. Background Technology

[0002] With the development of computer and internet technologies, applications are finding increasingly wider applications and are becoming more diverse. For example, applications include, but are not limited to, social networking, shopping, and entertainment applications. Applications typically undergo multiple modifications after release, such as when problems are discovered or new features need to be added.

[0003] In traditional technologies, release schedules are typically orchestrated, and new data is released to modify the application by executing the release schedule.

[0004] However, in traditional methods, the release plan is usually arranged by the release manager, which leads to low efficiency in processing the release plan. Summary of the Invention

[0005] Therefore, it is necessary to provide a release process processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the processing efficiency of release plans in response to the above-mentioned technical problems.

[0006] On one hand, this application provides a method for processing a release process. The method includes: receiving an editing request for a flowchart of a target release plan sent by at least one of a plurality of terminals based on a release process processing page; the plurality of terminals respectively displaying the flowchart of the target release plan and the release plan status of the target release plan on the release process processing page; synchronously updating the flowcharts of the target release plan displayed by the plurality of terminals based on the editing request; checking the connection relationships between task nodes in the flowchart of the target release plan using a historical task connection relationship set; the historical task connection relationship set including the connection relationships between task nodes in flowcharts of multiple historical release plans; if an anomaly is detected in the connection relationships between task nodes in the flowchart of the target release plan, sending an anomaly message to the plurality of terminals, so that the plurality of terminals display the anomaly message on the release process processing page; and updating the release plan status of the target release plan displayed by the plurality of terminals in response to a plan status change request triggered on the release process processing page.

[0007] On the other hand, this application also provides a release process processing apparatus. The apparatus includes: an edit request receiving module, configured to receive edit requests for a flowchart of a target release plan sent by multiple terminals based on at least one terminal in a release process processing page; the multiple terminals respectively display the flowchart of the target release plan and the release plan status of the target release plan on the release process processing page; a flowchart update module, configured to synchronously update the flowcharts of the target release plan displayed by the multiple terminals based on the edit requests; a checking module, configured to check the connection relationships between task nodes in the flowchart of the target release plan using a historical task connection relationship set; the historical task connection relationship set includes the connection relationships between task nodes in flowcharts of multiple historical release plans; an information sending module, configured to send connection relationship abnormality prompt information to the multiple terminals when an abnormality is detected in the connection relationships between task nodes in the flowchart of the target release plan, so that the multiple terminals display the connection relationship abnormality prompt information on the release process processing page; and a status update module, configured to update the release plan status of the target release plan displayed by the multiple terminals in response to a plan status change request for the target release plan triggered on the release process processing page.

[0008] In some embodiments, the apparatus is further configured to, in response to a copy request for a created first release plan sent by one of the plurality of terminals, generate the target release plan based on a flowchart of the first release plan; and send plan generation confirmation information for the target release plan to each of the plurality of terminals, so that the plurality of terminals respectively display an editing entry for the target release plan; the editing entry is used to trigger the display of the flowchart of the target release plan.

[0009] In some embodiments, the flowchart of the target release plan includes a task card for a first task node; the flowchart update module is further configured to update the display of the task card of the first task node displayed on the plurality of terminals based on the edit request, provided that the edit request is triggered based on the task card of the first task node and the information requested to be edited by the edit request is related to the task card of the first task node.

[0010] In some embodiments, the flowchart update module is further configured to, when the edit request is for requesting the addition of a second task node, determine a third task node that is adjacent to the second task node in the flowchart of the target release plan; and send a connection relationship establishment request to the plurality of terminals to establish a connection relationship between the second task node and the third task node, so that the connection relationship between the second task node and the third task node is displayed in the flowchart.

[0011] In some embodiments, the second task node belongs to each of the recommended task nodes of the third task node; the apparatus further includes: a recommended task node determination module, configured to determine each of the recommended task nodes corresponding to the third task node in response to a recommended task viewing request sent by the terminal for the third task node; a task information return module, configured to return the task information of each of the recommended task nodes corresponding to the third task node to the terminal; the task information of the recommended task nodes is used to trigger an edit request to be sent to the server to request the addition of the recommended task nodes.

[0012] In some embodiments, the recommended task node determination module is further configured to search for the historical task connection relationship corresponding to the third task node from the historical task connection relationship set based on the task node name of the third task node; the historical task connection relationship set includes the connection relationship between task nodes in the flowcharts of multiple historical release plans; and determine each recommended task node corresponding to the third task node based on the historical task connection relationship corresponding to the third task node.

[0013] In some embodiments, the inspection module is further configured to inspect the connection relationship between the third task node and the second task node using a set of historical task connection relationships; the information sending module is further configured to send a connection relationship abnormality prompt message to the plurality of terminals when an abnormality is detected in the connection relationship between the third task node and the second task node.

[0014] In some embodiments, the status update module is further configured to, in response to a completion request for editing the flowchart of the target release plan triggered on the release process processing page, update the status of the target release plan to an executable state; and send a first status update instruction for the target release plan to the plurality of terminals respectively, so that the plurality of terminals display the status update of the target release plan as an executable state.

[0015] In some embodiments, the flowchart of the target release plan displays the task status of a first task node; the apparatus further includes: an execution instruction sending module, configured to, in response to a plan execution request for the target release plan, send a release task execution instruction for the first task node to a task processing device corresponding to the first task node, so that the task processing device executes the release task corresponding to the first task node; and an update instruction sending module, configured to, when it is determined that the release task of the first task node has been completed, send a task status update instruction for the first task node to the plurality of terminals, so that the plurality of terminals update the task status of the first task node to show as executed.

[0016] In some embodiments, the apparatus is further configured to update the status of the target release plan to the executed state when the task status of each task node in the flowchart of the target release plan is determined to be in the executed state; and to send a second status update instruction for the target release plan to the plurality of terminals respectively, so that the plurality of terminals respectively update the status of the target release plan to the executed state.

[0017] In some embodiments, the execution instruction sending module is further configured to send a data preparation request to the data preparation device corresponding to the first task node; the data preparation device submits the data to be published corresponding to the first task node to the task processing device corresponding to the first task node based on the data preparation request; and upon receiving data preparation success information from the task processing device corresponding to the first task node, sends a task execution instruction for the first task node to the task processing device corresponding to the first task node.

[0018] In some embodiments, the execution instruction sending module is further configured to, upon receiving data preparation success information from the task processing devices corresponding to each task node, send a data review request for the data to be published for each task node to the review device; and, upon determining that the data to be published for each task node has been reviewed and approved, send a task execution instruction for the corresponding task node to the task processing devices corresponding to each task node.

[0019] On the other hand, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps in the above-described publishing process method.

[0020] On the other hand, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps in the above-described publishing process method.

[0021] On the other hand, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps in the above-described publishing process method.

[0022] The aforementioned release process processing method, apparatus, computer equipment, storage medium, and computer program product receive editing requests for flowcharts of a target release plan from multiple terminals based on at least one terminal in a release process processing page. The multiple terminals respectively display the flowcharts and release plan status of the target release plan on the release process processing page. Based on the editing requests, the flowcharts displayed by the multiple terminals are updated synchronously. A historical task connection relationship set is used to check the connection relationships between task nodes in the target release plan's flowchart. This historical task connection relationship set includes connection relationships between task nodes in flowcharts of multiple historical release plans. If an anomaly is detected in the connection relationships between task nodes in the target release plan's flowchart, an anomaly message is sent to the multiple terminals, causing them to display the anomaly message on the release process processing page. In response to a request to change the plan status of the target release plan, the release plan status displayed by the multiple terminals is updated. This approach, employing a graphical interface and multi-terminal collaborative processing of the release plan, improves the processing efficiency of the release plan. Attached Figure Description

[0023] Figure 1 This is an application environment diagram of the publishing process processing method in some embodiments;

[0024] Figure 2 This is a flowchart illustrating the publishing process processing method in some embodiments;

[0025] Figure 3 A schematic diagram illustrating the creation of an entry point for the release plan in some embodiments;

[0026] Figure 4 This is a schematic diagram of the publishing process processing page in some embodiments;

[0027] Figure 5 This is a schematic diagram of the publishing process processing page in some embodiments;

[0028] Figure 6 This is a schematic diagram of the publishing process processing page in some embodiments;

[0029] Figure 7 This is a schematic diagram of the publishing process processing page in some embodiments;

[0030] Figure 8 This is a schematic diagram illustrating the plan to save the window in some embodiments;

[0031] Figure 9 This is a schematic diagram of the release plan execution control in some embodiments;

[0032] Figure 10 This is a schematic diagram illustrating communication between the front-end client and the back-end service in some embodiments;

[0033] Figure 11 Here is a framework diagram of the front-end client in some embodiments;

[0034] Figure 12 This is a sequence diagram of the release process handling method in some embodiments;

[0035] Figure 13 This is a sequence diagram of the release process handling method in some embodiments;

[0036] Figure 14 Here are state change diagrams corresponding to the state machine of the release plan in some embodiments;

[0037] Figure 15 This is a state change diagram of the state machine of the task node in some embodiments;

[0038] Figure 16 This is a flowchart illustrating the publishing process processing method in some embodiments;

[0039] Figure 17 These are comparison images of the effects of SVG technology compared to canvas technology in some embodiments;

[0040] Figure 18 This is a structural block diagram of the publishing process processing apparatus in some embodiments;

[0041] Figure 19 These are internal structural diagrams of the computer device in some embodiments;

[0042] Figure 20 This is a diagram showing the internal structure of a computer device in some embodiments. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0044] The publishing process method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104, or it can be located in the cloud or on another server. Multiple terminals can communicate with server 104, meaning at least two, with terminal 102 being one of them.

[0045] Specifically, multiple terminals communicating with server 104 can each display a flowchart of the target release plan and its release plan status. For example, terminal 102 can display the flowchart and release plan status of the target release plan on the release process processing page. Server 104 can receive an editing request for the flowchart of the target release plan from at least one of the multiple terminals, such as terminal 102. The editing request can be triggered through the release process processing page. Based on the editing request, server 104 can synchronously update the flowcharts displayed by the multiple terminals. Server 104 can use a historical task connection relationship set to check the connection relationships between task nodes in the flowchart of the target release plan. The historical task connection relationship set includes the connection relationships between task nodes in the flowcharts of multiple historical release plans. If an anomaly is detected in the connection relationships between task nodes in the flowchart of the target release plan, an anomaly message is sent to the multiple terminals, causing the multiple terminals to display the anomaly message on the release process processing page. Server 104 can also update the release plan status of the target release plan displayed by the multiple terminals in response to a plan status change request for the target release plan. The target release plan can be any release plan related to the application. A release plan is a plan for releasing data, which allows for updates to the current application. For example, if the current application has a problem, data such as code can be generated to solve it. By releasing the generated data, the problem in the application is resolved. Therefore, the process of releasing data can be understood as the process of updating the application. The application can be of any type, including but not limited to at least one of social or entertainment applications.

[0046] The terminal 102 can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle systems. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. The server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0047] The publishing process processing method provided in this application can be based on artificial intelligence. For example, in the publishing process processing method provided in this application, the server can use artificial intelligence technology to determine the task nodes to be recommended from the created task nodes, and recommend the task nodes to be recommended to the terminal. The terminal can then respond to the task addition operation triggered by the recommended task nodes and add new task nodes generated based on the recommended task nodes to the flowchart. 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 optimal results. In other words, artificial intelligence is a comprehensive technology in computer science that attempts to understand the essence of intelligence and produce a new kind of intelligent machine that can react in a way similar to human intelligence. Artificial intelligence studies the design principles and implementation methods of various intelligent machines, enabling machines to have the functions of perception, reasoning, and decision-making. Artificial intelligence technology is a comprehensive discipline involving a wide range of fields, including both hardware and software technologies. Basic artificial intelligence technologies generally include sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operating / interactive systems, mechatronics, and other technologies. Artificial intelligence software technology mainly includes several major areas such as computer vision technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0048] In some embodiments, such as Figure 2 As shown, a release process processing method is provided, which is applied to... Figure 1 Taking server 104 as an example, the following steps are included:

[0049] Step 202: Receive an editing request for the flowchart of the target release plan from at least one of the multiple terminals based on the release process processing page; the multiple terminals respectively display the flowchart of the target release plan and the release plan status of the target release plan on the release process processing page.

[0050] The release plan is a plan for releasing data. The target release plan can be any release plan. The release plan flowchart refers to a graphical representation of the release plan. The target release plan flowchart can change as it is edited. The target release plan can be created directly or generated based on an existing release plan.

[0051] A release plan may include at least one release task. The flowchart of the release plan may include task nodes corresponding to each release task. Each release task may have an execution order. The execution order between release tasks can be represented by directional connecting lines in the flowchart of the release plan. For example, if release task A is executed and then release task B is executed, then there is a connecting line between the task nodes of release task A and the task nodes of release task B in the flowchart, and the connecting line points from the task node of release task A to the task node of release task B.

[0052] An edit request is a request to edit the flowchart of a target release plan. Edit requests include, but are not limited to, requests to add, delete, or modify task nodes. Release plan status refers to the current state of the release plan, which can be categorized as created, submitted, started, released, rolled back, pending approval, or rolled back.

[0053] Multiple terminals refer to at least two terminals. The server can be the server hosting the graphical publishing flowchart management system. Terminals can access the graphical publishing flowchart management system's pages through a browser or through a client application. Each of these multiple terminals is a terminal for the target object. The target object refers to an object with access rights to the target publishing plan. The object can be identified using its identity information within the graphical publishing flowchart management system. An object can represent a developer, who may include, but is not limited to, a tester or developer. Identity information includes, but is not limited to, at least one of avatar, account, or nickname. When an object logs into the graphical publishing flowchart management system, the terminal can display a publishing plan list page. The publishing plans in the publishing plan list page are those that the object has viewing permissions for. The publishing plan list page may also include a search box. By entering search information into the search box, the corresponding publishing plan can be retrieved from the publishing plan list. Search information includes, but is not limited to, at least one of the following: the creator's identity information, the person in charge's identity information, the publishing plan status, or the plan execution period. The release plan list page can also include separate functional controls for each release plan in the release plan list. These functional controls include, but are not limited to, at least one of the following: a plan copy control, a plan cancellation control, or a task settlement control. The plan copy control is used to trigger the copying of the release plan, the plan cancellation control is used to trigger the cancellation of the release plan, and the task settlement control is used to trigger the settlement of the task.

[0054] Specifically, for each target object's terminal, the terminal can display a flowchart of the target release plan and its release plan status. The target release plan can be created by any target object. For example, any terminal among the multiple terminals can display a release plan creation entry point. In response to a trigger operation targeting the release plan creation entry point, the terminal sends a release plan creation request to the server. The server, in response to the release plan creation request, generates a release plan number corresponding to the target release plan. Each release plan has a unique release plan number, and each release plan's release plan number is different. The server can send the generated release plan number to the terminal. The terminal can display a release process processing page, showing the initial flowchart of the target release plan. If the terminal receives an edit operation targeting this initial flowchart, it can send an edit request to the server, i.e., an edit request for the target release plan's flowchart, which can be an edit request for the initial flowchart of the target release plan. The initial flowchart is preset and may include an initial node and an empty task node. The trigger operation targeting the release plan creation entry point includes, but is not limited to, at least one of a click operation or a double-click operation.

[0055] In some embodiments, the release process page includes a header operation bar, a plan editing panel, a log panel, and a task panel. The header operation bar can display at least one of the following: the name and status of the release plan, the identity information of objects to be confirmed, the identity information of confirmed objects, or the identity information of the currently edited object. Objects to be confirmed refer to those for which the release plan needs confirmation, and confirmed objects refer to those for which the release plan has already been confirmed. When all objects requiring confirmation have been confirmed, the release plan's status can be updated to executable. The header operation bar can also provide function buttons for confirming the plan, saving the plan, editing the plan, executing the plan, canceling the plan, and reverting to the plan. The plan editing panel is the editing area for the release plan. Upon first entry, the plan editing panel displays an initial node and an empty task node. The plan editing panel has a function to guide object operations and also provides basic functions such as copying, deleting, and selecting keyboard shortcuts. In response to a right-click operation on a task node, the terminal can display a shortcut menu for the task node. This shortcut menu can provide recommended upstream and downstream dependencies for the task node and a quick task creation entry. The task node card contains information such as the task node type, the identity information of the person in charge, the creation time, and the task type. Clicking a task node triggers the process of editing task details. Clicking the left or right arrows on a task node card adds pre- or post-task dependencies. The server can recommend and check the correctness of pre- and post-task dependencies in the flowchart. When a task node card is dragged to another task node card, the terminal automatically creates a relationship and draws a connection between the two nodes. The log panel displays currently edited or executed log information, assisting users in editing release plans and viewing execution results and processes. The task panel provides task search capabilities, helping users quickly find relevant tasks by task type, task name, or responsible person's identity information, and can display automatically recommended related tasks. When an empty task is selected in the plan editing panel, or when the add button for a task node is clicked in the task panel, the selected task node can be added and bound to that empty task. For example, the release plan creation entry point is... Figure 3 The "Create Plan" control. When the terminal receives a click operation on the "Create Plan" control, it can display something like this: Figure 4 The release process processing page is shown, and the initial flowchart is displayed on this page. From Figure 4 As can be seen from the diagram, the initial flowchart includes an initial node and an empty task node. Figure 4 The interface displays the header control panel, plan editing panel, log panel, and task panel. A quick task creation entry is provided, for example... Figure 5The entry points for "Add Empty Task" and "Add New Task" in the 502 error message are as follows. In some embodiments, the server can send the release plan number and creation time of the generated target release plan to the terminal, and the terminal can display the release plan number and creation time of the target release plan. The creation time of the target release plan can be the time when the release plan number was generated. Specifically, the terminal can display the release plan number of the target release plan in the release plan list. The release plan number can also be called the plan identifier (ID, Identity document). The release plan list can also display at least one of the following: creation time, approval type, status, name, plan description information, responsible person's identity information, creator's identity information, and update time.

[0056] In some embodiments, the terminal can display an editing entry for the target release plan in the release plan list. Upon receiving a trigger operation on the editing entry, the terminal displays a flowchart of the target release plan and its release plan status. The flowchart refers to the latest flowchart. The terminal can display a release plan creation entry while displaying the release plan list, such as... Figure 3 As shown, the "Create Plan" control is the entry point for creating a release plan. Figure 3 The table shows information about 10 release plans, numbered from 1 to 10.

[0057] Step 204: Based on the editing request, synchronize and update the flowcharts of the target release plan displayed on multiple terminals.

[0058] Specifically, the server can store the latest flowchart of the target release plan. The server can obtain editing requests for the flowchart of the target release plan sent by the terminals of each target object, and edit the latest flowchart based on the editing requests to update the flowchart. After updating the flowchart, the server can send flowchart update requests to the multiple terminals respectively, and the multiple terminals will update the displayed flowchart based on the flowchart update requests.

[0059] In some embodiments, when the edit request is a task addition request, the terminal can send a task addition request to the server. The server can forward the task addition request to other terminals among the plurality of terminals. The terminal responds to the forwarded task addition request from the server, determines the task node to be added based on the task addition request, and adds the task node to the flowchart of the target release plan. The task addition request is used to add a task node, and the task addition request may carry the type of the task node. The type of the task node includes, but is not limited to, at least one of an empty task, a module task, or a general task. For example, if the task addition request is used to request the addition of an empty task node, then the task node to be added is the task node corresponding to the empty task; if the task addition request is used to request the addition of a module task's task node, then the task node to be added is the module task's task node. One task node represents one task; therefore, adding a task node can be understood as adding a task. In this application, "task node" can be replaced with "task".

[0060] In some embodiments, the terminal can display a task addition entry on the publishing process page. This task addition entry is used to trigger the addition of a task node. In response to a trigger operation on the task addition entry, the terminal adds a task node of the task type corresponding to the task addition entry at the corresponding position in the flowchart. Specifically, upon receiving a task addition window display operation for a task node in the flowchart, the terminal can display the task addition window corresponding to that task node. The task addition window display operation is used to trigger the display of the task addition window. The task addition window can display the task addition entry, or display an entry used to trigger the display of the task addition entry, such as... Figure 5 As shown, the task addition window 502 corresponding to the initial node is displayed. The "Add Empty Task" control in the task addition window 502 is the task addition entry point corresponding to the empty task node. Figure 5 The "Add New Task" control is used to trigger the display of task addition entries for task types other than empty tasks. In response to the "Add New Task" trigger, the terminal can display task addition entries for multiple task types.

[0061] In some embodiments, the terminal may display a task search area on the publishing process page. The task search area may be, for example, a... Figure 5In area 504, when the terminal receives a task search operation, it generates a task search request based on the search information entered in the task search area and sends the request, carrying the search information, to the server. The server can then search for candidate task nodes matching the search information from the candidate task node set to obtain the target task node. The server returns the task card information of the target task node to the terminal. The task card information refers to the information included in the task card of the target task node. The task card information may include at least one of the following: task node type, responsible person's identity information, creation time, or task type. The terminal can display the task card of the target task node based on its task card information. The search information includes, but is not limited to, at least one of task name or task type. The terminal can display the add control corresponding to the target task node on the task card of the target task node. When the terminal receives a trigger operation for adding the control to the target task node, it can generate task card information for a new task node based on the target task node and add the generated task card to the flowchart. The task card information of the new task node can be the same as or different from the task card information of the target task node. For example, the name of the task node in the task card information of the new task node may be the same as the name of the task node in the task card information of the target task node, and the type of the task node in the task card information of the new task node may be the same as the type of the task node in the task card information of the target task node. The task card can also be called a task node card.

[0062] In the flowchart, the connections between task nodes are represented by the connections between task cards. The connections between a new task node added to the flowchart and existing task nodes can be automatically determined. For example, the terminal can identify the task nodes associated with the new task node from the flowchart's task nodes, add the new task node to the flowchart, and establish connections between the new task node and its associated task nodes. Alternatively, the terminal can randomly establish connections between a new task node and existing task nodes in the flowchart. The target task node is, for example,... Figure 5 In the task node 506A, the "Add" control 508 is the add control corresponding to the target task node. In response to the click operation of the "Add" control 508, the terminal can add a new task node 506B based on the target task node in the flowchart.

[0063] In some embodiments, the terminal can display a task creation control on the publishing process page. Upon receiving the task creation control, the terminal can display a task editing area, which can be used to edit at least one of the following: task type, task name, or the identity information of the person in charge of the task. The task creation control is, for example, a... Figure 5 The "New" button (510) is used. The task type refers to the type of task node. The terminal can also display a schedule log on the release process page. The schedule log can be, for example, […]. Figure 6 The information in the "Log Panel" 602.

[0064] In some embodiments, the flowchart includes task cards corresponding to task nodes. Each task card represents a task node, and the task card may also include a task editing entry for that task node. Specifically, the terminal may display the corresponding task editing area in response to a trigger operation on the task editing entry, such as a click operation on the task editing entry. Alternatively, the terminal may display the task editing area corresponding to the task node in response to a trigger operation on the task node card. A feature switch may also be set in the task editing area. The feature switch is used to determine the sending method or timing of notifications related to the task node, including but not limited to at least one of social applications, email, or SMS. The timing of sending notifications includes, but is not limited to, when the status of the task node changes. The task editing area is, for example,... Figure 7 Area 702 in the middle, Figure 7 In the target release plan release process page, four task cards are displayed for each task node. Each task card includes a task editing entry, namely the "Edit" control. For example, task card 704 includes an "Edit" control 706. Area 702 is displayed when the terminal receives a click operation on the "Edit" control 706.

[0065] In some embodiments, after the release plan is orchestrated (edited), the terminal receives a trigger operation from the plan execution control for the release plan, updating the displayed release plan status, execution progress, and the status of each task. For example, different colors can be used to distinguish different task statuses and different execution progresses. The server can provide general tasks, which are tasks whose state changes are driven by the behavior of objects. The person in charge of a general task receives a notification from a social application, email, or SMS during the execution of the general task. The person in charge of the task enters the corresponding plan according to the notification content, processes the task under their responsibility, and clicks the "Executed" button after processing to drive the workflow (i.e., flowchart) to continue execution.

[0066] Step 206: Use the historical task connection relationship set to check the connection relationship between task nodes in the flowchart of the target release plan; the historical task connection relationship set includes the connection relationship between task nodes in the flowcharts of multiple historical release plans.

[0067] The historical task connection set includes the connections between task nodes in the flowcharts of multiple historical release plans. "Multiple" means at least two historical task connections. A historical task connection represents the connection between two task nodes in the flowchart of a historical release plan. For example, the historical task connection between task node A and task node B in historical release plan number 001 is: "Name and type of task node A, Name and type of task node B, Positive dependency, Release plan number". "Positive dependency" means that the connection between task node A and task node B points from A to B.

[0068] Specifically, the server can use the historical task connection relationship set to check the connection relationship between task nodes in the flowchart of the target release plan. If an anomaly is found in the connection relationship between task nodes in the flowchart of the target release plan, the server can send connection relationship anomaly prompts to multiple terminals respectively. These multiple terminals can display the connection relationship anomaly prompts on the release process processing page respectively.

[0069] In some embodiments, a task node is a task related to a functional module, such as a task for modifying a functional module. A functional module can be a code block, and different code blocks may or may not have a calling relationship. The server can pre-store preset calling relationships, which include calling relationships between multiple code blocks. The server can use these preset calling relationships to check the connection relationships between task nodes in the flowchart of the target release plan. If two connected task nodes are both related to functional modules, for example, to functional module 1 and functional module 2 respectively, the server determines whether a calling relationship exists between functional module 1 and functional module 2 based on the preset calling relationships. If not, a connection relationship error message is sent to multiple terminals. If a connection relationship exists, the server determines the calling direction between functional module 1 and functional module 2 based on the preset calling relationships. The calling direction includes either functional module 1 calling functional module 2 or functional module 2 calling functional module 1. If the direction of the connection line between the two task nodes does not match the calling direction between functional module 1 and functional module 2, a connection relationship error message is sent to multiple terminals. The two task nodes are task node 1 and task node 2. Task node 1 is related to functional module 1, and task node 2 is related to functional module 2. If the direction of the connecting line between task node 1 and task node 2 is from task node 1 to task node 2, and functional module 1 calls functional module 2, then the direction of pointing and calling are mismatched. Alternatively, if the direction of the connecting line between task node 1 and task node 2 is from task node 2 to task node 1, and functional module 1 calls functional module 2, then the direction of pointing and calling are mismatched.

[0070] In some embodiments, the server may first use a preset call relationship to check the connection relationships between task nodes in the flowchart of the target release plan, and then use a historical task connection relationship set to check the connection relationships between task nodes in the flowchart of the target release plan. Both checks can send connection relationship error messages to multiple terminals.

[0071] Step 208: If an anomaly is detected in the connection relationship between task nodes in the flowchart of the target release plan, send an anomaly message to the multiple terminals so that the multiple terminals display the anomaly message on the release process processing page.

[0072] The connection relationship error message is used to indicate that there may be incorrect connection relationships between task nodes in the flowchart.

[0073] Specifically, the server can use the historical task connection relationship set and the connection relationship between each task node in the flowchart of the target release plan to detect the connection relationship. If an anomaly is detected in the connection relationship between the task nodes in the flowchart of the target release plan, the server can send a connection relationship anomaly prompt message to the multiple terminals.

[0074] In some embodiments, when the server determines that a new connection has been added to the flowchart, it triggers a check of the connection relationships between task nodes in the flowchart of the target release plan. For example, if a connection relationship is added between a third task node and a second task node in the flowchart, the server can check the connection relationship between the third task node and the second task node. If the connection relationship between the third task node and the second task node is determined to be correct, no connection relationship error message is sent to multiple terminals. If the connection relationship between the third task node and the second task node is determined to be incorrect, connection relationship error messages are sent to multiple terminals respectively.

[0075] In some embodiments, the server can also specify connection relationships and use these specified relationships to check the connection relationships between task nodes. The server can use preset call relationships, a set of historical task connection relationships, and the specified connection relationships to check the connection relationships between task nodes. If an anomaly is detected in the connection relationships between task nodes, connection relationship anomaly prompts are sent to each of the multiple terminals respectively.

[0076] Step 210: In response to the plan status change request for the target release plan triggered on the release process processing page, update the release plan status of the target release plan displayed on multiple terminals respectively.

[0077] The release plan status can be categorized as created, saved, in progress, released, canceled, and closed. A plan status change request is used to request a change to the release plan status of the target release plan.

[0078] Specifically, the terminal can display a release plan save control on the release process page of the target release plan. When the terminal receives a trigger operation (such as a click) on the release plan save control, it displays a plan save window for the target release plan. The plan save window can include at least one of the following areas: an area for editing the plan name, an area for editing the responsible person, an area for editing the plan description information, and an area for editing the approval method. The plan save window may also display a submit control. In response to a trigger operation (such as a click) on the submit control, the terminal sends a request to the server to update the release plan status of the target release plan to "submitted." After receiving the plan status change request, the server can send status change indication information to multiple terminals respectively, indicating that the release plan status of the target release plan be changed to "saved." The plan save window is as follows: Figure 8 As shown, Figure 8 "Unified Approval" is an approval method. When "Unified Approval" is selected, the approval method for the target release plan will be "Unified Approval". The "Unified Approval" method means that one plan is approved once, which saves the approval time of each system individually and improves the release efficiency compared to the approval method of N tasks and N approvals.

[0079] In some embodiments, a terminal can access a release plan execution control on the release process handling page of the target release plan. When the terminal receives a trigger operation, such as a click operation, on the release plan execution control, it sends a request to the server to update the release plan status of the target release plan to a "release in progress" status change request. After receiving the status change request, the server can send status change indication information to the multiple terminals respectively. The status change indication information is used to indicate that the release plan status of the target release plan be changed to "release in progress." Figure 9 As shown, the release plan execution control 902 is displayed. Figure 9 The "Publishing" status is displayed after receiving a status change indication message.

[0080] In some embodiments, the server can be the server corresponding to the backend service of the graphical flowchart publishing management system. Terminals can access the graphical flowchart publishing management system's pages through a browser or through the system's frontend client. The backend service of the graphical flowchart publishing management system can provide a standardized API (Application Programming Interface). This standardized API enables communication between the frontend client and the backend service, as well as communication between the access system and the backend service. The standardized API can also be called a standardized interface. Figure 10The diagram illustrates the communication between the front-end client, back-end service, and access system via standardized APIs. Figure 10 In this context, the first client refers to a WebSocket client, and the second client refers to an HTTP client. The backend service provides functionality for synchronizing information. Based on this synchronization function, the server can synchronously update and display information across multiple terminals. For example, the backend service can include a WebSocket service, a full-duplex communication service implemented using the Socket.io framework, used to synchronize messages between the client and server. For instance, when an object enters the publishing process processing page of a publishing plan to edit the flowchart, the frontend client sends an "enter room" message. The room can be understood as the publishing process processing page of the publishing plan. All terminals in the current room receive the "enter room" message and update the identity information of the object currently editing in the room. When an object triggers an editing operation on the publishing plan's flowchart, such as adding a task, the server can use the WebSocket service to notify all users in the room to update the current flowchart, thus achieving real-time multi-user collaborative editing. Any system that meets the access standard API can serve as an access system. Access systems can include the actual running systems corresponding to tasks in the publishing plan. The access system executes the corresponding response based on the task's state machine using the standardized API.

[0081] In some embodiments, the backend service can be a Node.js server-side application developed using the AdonisJS framework on the Node.js platform, providing HTTP and WebSocket services. Node.js can be understood as JavaScript running on the server-side. Figure 10As shown, the HTTP service can include a user module, a publishing plan module, a publishing task module, a template service module, a log service module, a relationship service module, and an execution engine module. These modules uniformly provide a standardized RESTful API. The user module manages user information and performs CRUD operations on user identities or roles. The publishing plan, publishing task, and template service modules provide metadata operation services, such as services for creating, deleting, querying, and modifying plans, tasks, and templates. By calling the execution engine service, plans and tasks can be executed, and the relationship service module can be invoked to check relationships and recommend related tasks. Checking relationships can, for example, verify the correctness of connections between task nodes in a flowchart. The log module records user operation logs, system execution logs, relationship check logs, and data statistics logs. The relationship service module contains a recommendation algorithm engine. Based on known data such as inter-module call data from third-party systems and relationship data within the system, the recommendation algorithm recommends potentially related upstream and downstream modules for content-related tasks, assisting users in orchestrating publishing tasks, reducing the possibility of errors, and indicating necessary upstream and downstream dependencies when modules change. The execution engine module is a workflow-driven engine module based on a Directed Acyclic Graph (DAG), comprising a finite state machine service, a worker service, and a notification service. The finite state machine service drives the state machines of the release plan and tasks. The worker service executes tasks from the queue of tasks in the executable state. The notification service connects to third-party notification services such as social media, email, or SMS. When the execution engine receives a release plan execution or rollback command, it can adjust the state of the release plan and the included tasks according to the state machines of the release plan or tasks. Tasks to be executed are placed in the worker's execution queue. The worker consumes the execution queue, adjusts the task state according to the task state machine, and calls the notification service to send notifications as needed.

[0082] In some embodiments, the backend services also include an HTTP service, a WebSocket service, and a workflow execution engine. The HTTP service provides CRUD (Create, Read, Update, Delete) capabilities for metadata related to release plans, release tasks, release plan logs, plan templates, and relationships, as well as task recommendation capabilities based on relationships stored in the system using a recommendation engine. The workflow engine enables the ordered execution of tasks. It also provides a standardized RESTful API to frontend clients and access systems. REST stands for Representational State Transfer. Figure 10 The first service in the list refers to the WebSocket service, the second service refers to the HTTP service, and the third service refers to the worker service.

[0083] In some embodiments, the front-end client can be a modern web application built on technologies such as Vue, VueRouter, or Vuex. For example, the front-end client can be a Vue single-page application web client developed based on TypeScript, using VueRouter for routing management and Vuex for state management. Element-ui serves as the UI (User Interface) component, interacting with the graphical editor component through events to respond to user input, synchronizing multi-user collaborative information via WebSockets, and updating the plan and graph status in real-time, including the current editor's information. An optimistic locking algorithm is used to enable multi-user collaborative editing of the plan. The front-end and back-end are separated, interacting with the service via an HTTP client to obtain and update data related to the release plan. This data is managed by Vuex and used to notify the UI layer for rendering. The SVG graphical editor renders SVG vector graphics to display the release plan flow based on user input and back-end data, and a relationship checking engine checks the correctness of relationships on the front-end. Figure 11 The diagram shown illustrates the framework of the front-end client. Figure 11 The "single-page client application" in this context refers to the front-end client, from... Figure 11 As can be seen, the front-end client mainly includes the front-end UI presentation layer. This layer includes a standard form list module based on Element-UI and a graphical editor module for editing the release plan workflow. The graphical editor includes an SVG rendering engine and a DAG (Directed Acyclic Graph) relationship checking engine. The front-end client also includes two clients that interact with the back-end service: an HTTP client and a WebSocket client. SVG is a language that uses XML to describe 2D graphics. Vue is a progressive JavaScript framework for building user interfaces. VueRouter is a routing plugin. Vuex is a state management pattern for application development. Element-UI (user interface elements) is used to provide components. TypeScript is an open-source programming language.

[0084] In the above-described release process handling method, multiple terminals receive editing requests for the flowchart of the target release plan sent by at least one terminal on the release process handling page. Each terminal displays the flowchart and release plan status of the target release plan on its respective release process handling page. Based on the editing requests, the flowcharts displayed by the multiple terminals are updated synchronously. A historical task connection relationship set is used to check the connection relationships between task nodes in the target release plan's flowchart. This historical task connection relationship set includes the connection relationships between task nodes in flowcharts of multiple historical release plans. If an anomaly is detected in the connection relationships between task nodes in the target release plan's flowchart, an anomaly message is sent to the multiple terminals, causing them to display the anomaly message on their release process handling pages. In response to a request to change the plan status of the target release plan, the release plan status displayed by the multiple terminals is updated. This approach, employing a graphical interface and multi-terminal collaborative processing of the release plan, improves the processing efficiency of the release plan. In addition, by utilizing the historical task connection relationship set, the connection relationships between task nodes in the flowchart of the target release plan are checked. If any abnormality is found in the connection relationship between task nodes in the flowchart of the target release plan, connection relationship abnormality prompts are sent to multiple terminals. This allows for timely feedback on the update of the flowchart of the target release plan, timely detection of problems in the flowchart for timely correction, and speeds up the efficiency and accuracy of flowchart editing.

[0085] The traditional method for creating release plans is to use tables to arrange them. This method has many problems. Compared with the table-based method, the graphical method of arranging release plans has many advantages. As shown in Table 1, the effect of arranging release plans using tables and using the graphical method is compared.

[0086] Table 1

[0087]

[0088] In some embodiments, the method further includes: in response to a copy request for a created first release plan sent by a terminal among a plurality of terminals, generating a target release plan based on a flowchart of the first release plan; sending plan generation confirmation information for the target release plan to each terminal among the plurality of terminals, so that each terminal displays an editing entry for the target release plan; the editing entry is used to trigger the display of the flowchart of the target release plan.

[0089] There can be multiple created release plans, with the first release plan being one of the existing release plans. The server can store all the created release plans.

[0090] Specifically, the terminal displays a copy entry for at least one created release plan, such as the copy entry for the first release plan. When the terminal receives a trigger operation for the copy entry of the first release plan, it sends a copy request for the first release plan to the server. The server can generate a release plan number for the target release plan and generate a flowchart for the target release plan based on the flowchart of the first release plan. For example, the flowchart of the first release plan can be used as the flowchart of the target release plan. After the server generates the target release plan, it can send a plan generation confirmation message for the target release plan to each of the multiple terminals. The plan generation confirmation message may carry the release plan number of the target release plan. Based on the plan generation confirmation message for the target release plan, the terminal displays the release plan number of the target release plan and the editing entry for the target release plan. When the terminal receives a trigger operation for the editing entry of the target release plan, it displays the release process processing page for the target release plan and displays the flowchart of the target release plan on the release process processing page.

[0091] In this embodiment, in response to a copy request for a first release plan sent by one of the multiple terminals, a target release plan is generated based on the flowchart of the first release plan. This allows the target release plan to be generated based on the flowchart of the created release plan, improving the efficiency of generating the target release plan and the efficiency of generating the flowchart of the target release plan.

[0092] In some embodiments, the flowchart of the target release plan includes a task card of a first task node; synchronously updating the flowchart of the target release plan displayed on multiple terminals based on an edit request includes: when the edit request is triggered based on the task card of the first task node and the information requested to be edited by the edit request is related to the task card of the first task node, updating the display of the task card of the first task node displayed on multiple terminals based on the edit request.

[0093] The task card may include at least one of the following: the task node's name, task node type, the identity information of the person in charge of the task node, and the task node's creation time. The task card for the first task node may also include an editing entry point corresponding to the first task node, using the task card of the first task node as... Figure 7 Taking 704 as an example, the editing entry point for the first task node is the "Edit" control 706.

[0094] Specifically, when a terminal receives a trigger operation for the editing entry on the task card of the first task node, it can display the task editing area corresponding to the first task node. Upon receiving the editing completion operation, the terminal obtains the information input into the task editing area, thus acquiring the editing information for the first task node. If this editing information is related to the information in the task card of the first task node, the terminal sends the editing information of the first task node to the server. The server can then send this editing information to other terminals among the multiple terminals, enabling each terminal to update the display of the task card for the first task node. For example, if the node card of the first task node displays the identity information of the person in charge, and the editing information includes the identity information of the person in charge, then the identity information of the person in charge in the task card of the first task node can be updated and displayed.

[0095] In this embodiment, when the editing request is triggered based on the task card of the first task node and the information requested to be edited is related to the task card of the first task node, the task cards of the first task node displayed on multiple terminals are updated based on the editing request, thereby enabling each terminal to update the information displayed on the task card in a timely manner and improving collaboration efficiency.

[0096] In some embodiments, synchronously updating the flowcharts of the target release plan displayed on multiple terminals based on an edit request includes: when the edit request is to add a second task node, determining a third task node that is adjacent to the second task node from the flowchart of the target release plan; and sending a connection establishment request to at least one of the multiple terminals to establish a connection between the second task node and the third task node, so that the connection between the second task node and the third task node is displayed in the flowchart.

[0097] In this context, the second task node is a task node added to the flowchart of the plan to be released to the target. There can be one or more second task nodes that are adjacent to the first task node; multiple means at least two. The closer two task nodes are, the greater the probability that there is a connection between them.

[0098] Specifically, the third task node that is adjacent to the second task node can be determined by either the terminal or the server. The terminal or server can determine the third task node that is adjacent to the second task node based on a set of historical task connection relationships. This set of historical task connection relationships includes the connection relationships between task nodes in the flowcharts of multiple historical release plans. For example, the terminal or server can query the historical task connection relationships of family members of the second task node from the set of historical task connection relationships based on the name or type of the second task node, thus obtaining the target task connection relationship corresponding to the second task node. For a task node in the flowchart of the target release plan, if a family member of that task node is recorded in the target task connection relationship, that task node can be determined as the third task node that is adjacent to the second task node. Family members of the same task node refer to task nodes with the same name and type.

[0099] In some embodiments, the second task node is a searched task, such as a task node displayed in the task list as shown in 5. The terminal can display an add control corresponding to the second task node. When the terminal receives a trigger operation for the add control of the second task node, for example, on... Figure 5 When the control 508 in the middle is triggered, an edit request can be sent to the server to request the addition of a second task node.

[0100] In some embodiments, when the server determines that the relationship between the second task node and the third task node is adjacent, it may send a connection establishment request to each of the plurality of terminals. The connection establishment request is used to request the addition of the second task node in the flowchart and the establishment of a connection relationship between the second task node and the third task node.

[0101] In this embodiment, when the edit request is used to request the addition of a second task node, a third task node that is adjacent to the second task node is determined from the flowchart of the target release plan. A connection establishment request is sent to multiple terminals to establish a connection between the second task node and the third task node. This allows for the rapid addition of task nodes to the flowchart and the rapid establishment of connections between task nodes, thereby improving the efficiency of the flowchart of the biochemical target release plan.

[0102] In some embodiments, the second task node belongs to each of the recommended task nodes of the third task node; the method further includes: in response to a recommended task viewing request sent by the terminal for the third task node, determining each of the recommended task nodes corresponding to the third task node; returning the task information of each of the recommended task nodes corresponding to the third task node to the terminal; the task information of the recommended task nodes is used to trigger an edit request to be sent to the server to request the addition of recommended task nodes.

[0103] The task information of the recommended task node includes, but is not limited to, at least one of the following: the name of the recommended task node, its type, and the plan ID (identifier) ​​of the historical release plan to which it belongs.

[0104] Specifically, when the terminal receives an operation to display a task add window for the third task node in the flowchart, it sends a request to the server to view recommended tasks for the third task node. The server retrieves the recommended task nodes corresponding to the third task node, returns the task information of each recommended task node to the terminal, and can display the task add window for that task node. Within the task add window, the recommended task view entry is displayed, which is used to view the task information of each recommended task node corresponding to the third task node. The recommended task view entry could be, for example,... Figure 5 512 in the middle.

[0105] In this embodiment, in response to the terminal's request to view recommended tasks for the third task node, the recommended task nodes corresponding to the third task node are determined, and the task information of each recommended task node corresponding to the third task node is returned to the terminal. The task information of the recommended task nodes is used to trigger an edit request to be sent to the server to request the addition of recommended task nodes. Thus, when adding task nodes that are connected to the third task node, task nodes can be selected from the recommended task nodes. After adding a recommended task node, it can be modified based on the recommended task node to obtain the required task node, thereby improving the efficiency of generating task nodes.

[0106] In some embodiments, determining the recommended task nodes corresponding to the third task node includes: searching for the historical task connection relationship corresponding to the third task node from the historical task connection relationship set based on the task node name of the third task node; the historical task connection relationship set includes the connection relationship between task nodes in the flowcharts of multiple historical release plans; and determining the recommended task nodes corresponding to the third task node based on the historical task connection relationship corresponding to the third task node.

[0107] The historical task connection set includes the connections between task nodes in the flowcharts of multiple historical release plans. "Multiple" means at least two historical task connections. A historical task connection represents the connection between two task nodes in the flowchart of a historical release plan. For example, the historical task connection between task node A and task node B in historical release plan number 001 is: "Name and type of task node A, Name and type of task node B, Positive dependency, Release plan number". "Positive dependency" means that the connection between task node A and task node B points from A to B.

[0108] Specifically, the server can search the historical task connection relationship set for historical task connection relationships that record the name of the third task node, thus obtaining the historical task connection relationship corresponding to the third task node. Alternatively, the server can search the historical task connection relationship set for the third task node based on its name and type. For example, for each historical task connection relationship in the historical task connection relationship set, the server can determine whether there exists a task node among the two task nodes recorded in the historical task connection relationship that has the same name and type as the third task node. If so, the server identifies that historical task connection relationship as the historical task connection relationship corresponding to the third task node.

[0109] In some embodiments, the historical task connection relationship corresponding to the third task node includes family task nodes of the third task node. Family task nodes refer to task nodes with the same name and type. For example, if task node A has the same name as task node B and task node A has the same type as task node B, then task node A and task node B are said to be family task nodes. The server can determine the recommended task nodes corresponding to the third task node based on the historical task connection relationship corresponding to the third task node. Specifically, the server can determine the task nodes other than family task nodes of the third task node recorded in the historical task connection relationship corresponding to the third task node as recommended task nodes of the third task node, thus obtaining the recommended task nodes corresponding to the third task node.

[0110] In this embodiment, based on the task node name of the third task node, the historical task connection relationship corresponding to the third task node is searched from the historical task connection relationship set. Based on the historical task connection relationship corresponding to the third task node, each recommended task node corresponding to the third task node is determined, which improves the efficiency of determining recommended task nodes.

[0111] In some embodiments, checking the connection relationships between task nodes in the flowchart of the target release plan using the historical task connection relationship set further includes: checking the connection relationship between the third task node and the second task node using the historical task connection relationship set; and sending connection relationship abnormality prompt information to multiple terminals when an abnormality is found in the connection relationship between the task nodes in the flowchart of the target release plan includes: sending connection relationship abnormality prompt information to multiple terminals when an abnormality is found in the connection relationship between the third task node and the second task node.

[0112] The inspection results include either an incorrect connection between the third task node and the second task node, or a correct connection between the third task node and the second task node.

[0113] Specifically, the server can use the historical task connection relationship set to check the connection relationship between the third task node and the second task node. If the connection relationship between the third task node and the second task node is determined to be correct, no connection relationship error message will be sent to multiple terminals. If the connection relationship between the third task node and the second task node is determined to be incorrect, connection relationship error messages will be sent to multiple terminals respectively. For example, the connection relationship error message might be... Figure 5 Error 514 means "Module mmpaychangetes... Incorrect dependency. Required dependency is XXXX. Please check and reset."

[0114] In some embodiments, the correctness of the connection between two task nodes can be determined based on historical task connection relationships. If there are historical task connection relationships that record the same family task nodes of the third task node and the same family task nodes of the second task node, the server can determine that the connection between the third task node and the second task node is correct; otherwise, the connection between the third task node and the second task node is incorrect.

[0115] In this embodiment, the connection relationship between the third task node and the second task node is checked using the historical task connection relationship set. If an anomaly is found in the connection relationship between the third task node and the second task node, connection relationship anomaly prompt information is sent to multiple terminals. This allows for timely feedback on the update of the flowchart of the target release plan, timely detection of problems in the flowchart for timely correction, and speeds up the efficiency and accuracy of flowchart editing.

[0116] In some embodiments, in response to a plan status change request for a target release plan triggered on the release process processing page, updating the release plan status of the target release plan displayed on multiple terminals includes: in response to a flowchart editing completion request for the target release plan triggered on the release process processing page, updating the status of the target release plan to an executable state; and sending a first status update instruction for the target release plan to multiple terminals respectively, so that the multiple terminals update the status of the target release plan to an executable state.

[0117] The first status update instruction instructs the target release plan to be updated to an executable state. The edit completion request requests that the target release plan be updated to an executable state.

[0118] Specifically, in response to a request for completion of editing the flowchart of the target release plan triggered on the release process handling page, the server determines that the editing of the flowchart of the target release plan is complete. The server can update the stored status of the target release plan to an executable state and send a first status update instruction for the target release plan to at least one of multiple terminals. The terminal can then update the status of the displayed target release plan to an executable state based on the first status update instruction. The status of the target release plan can be, for example,... Figure 5 516 "Initialization" in the middle.

[0119] In this embodiment, in response to the completion request for editing the flowchart of the target release plan triggered on the release process processing page, the status of the target release plan is updated to the executable state, and a first status update instruction for the target release plan is sent to multiple terminals respectively, so that each terminal can update the status of the target release plan in a timely manner.

[0120] In some embodiments, the flowchart of the target release plan shows the task status of the first task node; the method further includes: in response to a plan execution request for the target release plan, sending a release task execution instruction for the first task node to the task processing device corresponding to the first task node, so that the task processing device executes the release task corresponding to the first task node; and when it is determined that the release task of the first task node has been completed, sending a task status update instruction for the first task node to multiple terminals, so that the multiple terminals update the task status of the first task node to show as executed.

[0121] In the flowchart of the target release plan, at least one task node can correspond to a task processing device. For example, each task node can have its own task processing device. The task processing devices corresponding to different task nodes can be the same or different. The task processing device is used to execute the release task of the task node.

[0122] Specifically, the terminal can display the execution control corresponding to the target release plan. When the terminal receives a trigger operation for the execution control and the target release plan is in an executable state, the terminal sends a plan execution request for the target release plan to the server.

[0123] In some embodiments, when the flowchart of the target release plan is determined to be in an executable state, the server can determine the task processing device corresponding to each task node in the flowchart of the target release plan, for example, determine the task processing device corresponding to the first task node. In response to the plan execution request for the target release plan, the server can send a data preparation request for the first task node to the task processing device corresponding to the first task node. The data preparation request is used to request the data to be released for the first task node. When the server determines that the data to be released for the first task node has been successfully prepared, it can send a release task execution instruction for the first task node to the task processing device of the first task node.

[0124] In this embodiment, in response to a plan execution request for a target release plan, a release task execution instruction for the first task node is sent to the task processing device corresponding to the first task node. The task processing device can execute the release task corresponding to the first task node based on the release task execution instruction. When it is determined that the release task of the first task node has been completed, a task status update instruction for the first task node is sent to multiple terminals so that the multiple terminals can update the task status of the first task node to the executed status. Thus, the server can communicate with the task processing device used to implement the release task, update the task status of the task node according to the execution status of the release task, and update it in real time on the terminal, so that the task status of the task node is displayed in a visual form, so as to quickly grasp the status of the task node.

[0125] In some embodiments, the method further includes: updating the status of the target release plan to an executed status when the release task of each task node in the flowchart for determining the target release plan has been completed; and sending a second status update instruction for the target release plan to multiple terminals respectively, so that the multiple terminals respectively display the status update of the target release plan as executed.

[0126] The second status update instruction is used to instruct the terminal to display the status update of the target release plan as executed.

[0127] Specifically, when the task status of each task node in the flowchart of the target release plan is in the executed state, the server can update the status of the stored target release plan to the executed state, and the server can send a second status update instruction for the target release plan to the terminal so that the terminal can update the status of the displayed target release plan to the executed state.

[0128] In this embodiment, a second status update instruction for the target release plan is sent to multiple terminals respectively, so that the multiple terminals respectively display the status update of the target release plan as executed, thereby enabling timely updates to the status of the target release plan displayed on the terminals, so as to keep track of the execution status of the target release plan in a timely manner.

[0129] In some embodiments, sending a task execution instruction for the first task node to the task processing device corresponding to the first task node includes: sending a data preparation request to the data preparation device corresponding to the first task node; the data preparation device submitting the data to be published corresponding to the first task node to the task processing device corresponding to the first task node based on the data preparation request; and, upon receiving data preparation success information from the task processing device corresponding to the first task node, sending a task execution instruction for the first task node to the task processing device corresponding to the first task node.

[0130] The data preparation device is used to submit data to be published to the task processing device; for example, it could be a device used by developers. A data preparation request is used to request the submission of data to be published to the task processing device.

[0131] Specifically, in response to a planned execution request for a target release plan, the server can send a release order creation request to the task processing device corresponding to the first task node. The task processing device corresponding to the first task node creates a release order for the first task node and returns the release order identifier to the server. The server then determines that the first task node should send a data preparation request carrying the release order identifier to the corresponding data preparation device.

[0132] In some embodiments, the data preparation device can display a data submission page, which can be the page of the task processing system corresponding to the task processing device. The data preparation device obtains the data to be published for the first task node input to the data submission page and submits the data to be published for the first task node to the task processing device corresponding to the first task node. Taking the task processing device corresponding to the first task node as an example... Figure 12 This will be illustrated using the device where the data model management system is located as an example. Figure 12 In section 1.3, "Preparing for Release Task" refers to sending a data preparation request to the device within the data model management system. Based on this request, the device creates an empty release order and returns its identifier (ID) to the server. The server then sends information carrying the release order identifier to the developer's device, instructing the developer to submit the data to be released for the first task node (i.e., the data for the preparation task in section 1.8) to the application service (the backend service of the data model management system) through the data model management system's web interface. The data model management system could be, for example, XModel. Figure 12 The release plan can include the front-end client and back-end services of the graphical release process management system.

[0133] In some embodiments, if the task processing device of the first task node determines that the data to be published by the first task node has been successfully submitted, it may return a data preparation success message for the first task node to the server. The server then determines that the data to be published by the first task node has been successfully prepared based on the data preparation success message for the first task node.

[0134] In some embodiments, the first task node is a task node that requires review. If the data to be published by the first task node has been successfully submitted, the task processing device of the first task node can send a request to the review system to create a review order for the first task node. Once the review order is created, the task processing device of the first task node can request the publishing system to associate the review order with the publishing order and update the publishing order status to "ready". The server can send a publishing order status query request to the task processing device of the first task node based on the publishing order identifier of the first task node. The task processing device of the first task node returns the publishing order status to the server. If the server determines that the publishing order status is "ready", it can send a publishing task execution instruction to the task processing device of the first task node. Whether a task node needs to be reviewed and the corresponding review system can be set when the task node is created.

[0135] In some embodiments, when the task processing device of the first task node receives a task execution instruction for publishing the task, it can update the status of the publishing order to "Publishing" and the status of the review order to "Reviewing". When the task processing device of the first task node receives the review result for the review order from the reviewer's device, if the review result is "Approved", it updates the status of the review order to "Completed" and the status of the publishing order to "Published". The task status of the first task node can be the status of the publishing order of the first task node. If the review result is "Rejected", the task processing device of the first task node can return the rejection information to the server, and the server can notify the developer to prepare new data to be published and resubmit it to the task processing device of the first task node. Alternatively, the task processing device of the first task node can directly notify the developer to prepare new data to be published and resubmit it to the task processing device of the first task node.

[0136] In this embodiment, upon receiving data preparation success information from the task processing device corresponding to the first task node, a task execution instruction for the first task node is sent to the task processing device corresponding to the first task node. This allows the task to be executed while ensuring that the data to be published already exists, reducing invalid executions.

[0137] In some embodiments, upon receiving data preparation success information from the task processing device corresponding to the first task node, sending a task execution instruction for the first task node to the task processing device corresponding to the first task node includes: upon receiving data preparation success information from the task processing devices corresponding to each task node respectively, sending a data review request for the data to be published for each task node to the review device; and upon determining that the data to be published for each task node has been reviewed and approved, sending a task execution instruction for the corresponding task node to the task processing device corresponding to each task node.

[0138] The auditing equipment refers to the equipment where the designated auditing system is located.

[0139] Specifically, upon receiving successful data preparation information from the task processing devices corresponding to each task node, the server can send a data review request for the data to be published for each task node to the review device. Once it is determined that the data to be published for each task node has passed review, the server sends a task execution instruction for the corresponding task node to the task processing device for that task node. For example... Figure 13 As shown, when the release plan is set to unified review, the release plan is reviewed in a unified manner. The data to be released for each task node is reviewed in a unified manner. When the data to be released for each task node is approved, the release task execution instruction for the corresponding task node is sent to the task processing device corresponding to each task node, so that the task processing device can upload the approved data to be released for each task node. Figure 13 The non-regional change system in the application is an internal change system for social applications and has a publishing function.

[0140] In some embodiments, the server may store the state machine of the target release plan and the state machines corresponding to the task nodes. The terminal may display at least one of a release plan cancellation control or a release plan rollback control on the release process processing page of the target release plan. When the target release plan is being executed or has been completed, the terminal may send a plan cancellation request to the server in response to a trigger operation on the release plan cancellation control, or the terminal may send a plan rollback request to the server in response to a trigger operation on the release plan rollback control. The server may reverse the state of the target release plan and the state of the task nodes based on the state machine of the target release plan and the state machines of the task nodes. Figure 14 As shown, the state transition diagram corresponding to the state machine of the release plan is illustrated. Figure 15 As shown, the state transition diagram of the task node's state machine is displayed.

[0141] In this embodiment, upon receiving data preparation success information from the task processing devices corresponding to each task node, a data review request for the data to be published for each task node is sent to the review device. This enables one-time approval for each plan, improving approval efficiency and thus publishing efficiency.

[0142] In some embodiments, such as Figure 16 As shown, a publishing process method is provided. Taking the application of this method to a server as an example, it includes the following steps:

[0143] Step 1602: Receive an editing request for a flowchart of the target release plan from at least one of the multiple terminals.

[0144] The flowchart can be a DAG drawn using SVG technology. For release schedules that require large drawing areas but small data volumes, SVG technology offers better performance than canvas technology, providing superior visual appeal and easier manipulation. Canvas technology is a technique for drawing 2D graphics using JavaScript. Figure 17 The image shows the effect of generating flowcharts using SVG technology and canvas technology. Figure 17 In (a) and (b), the dashed lines represent the curves corresponding to canvas, and the solid lines represent the curves corresponding to SVG.

[0145] Step 1604: In response to the terminal's request to view recommended tasks for the first task node, determine the recommended task nodes corresponding to the first task node and return the task information of the recommended task nodes corresponding to the first task node to the terminal.

[0146] Step 1606: In the case of an edit request for requesting the addition of a recommended task node to the first task node, a connection relationship establishment request is sent to multiple terminals to establish a connection relationship between the first task node and the recommended task node, so that the connection relationship between the first task node and the recommended task node is displayed in the flowchart.

[0147] Step 1608: Use the historical task connection relationship set to check the connection relationship between task nodes in the flowchart of the target release plan; the historical task connection relationship set includes the connection relationship between task nodes in the flowcharts of multiple historical release plans.

[0148] Step 1610: If an anomaly is detected in the connection relationship between task nodes in the flowchart of the target release plan, send connection relationship anomaly prompts to multiple terminals so that the connection relationship anomaly prompts are displayed on the release process processing page of multiple terminals.

[0149] Step 1612: Once the flowchart for the target release plan has been edited, update the status of the target release plan to the executable state.

[0150] Step 1614: Send a first status update instruction for the target release plan to multiple terminals respectively, so that the multiple terminals display the status update of the target release plan as executable.

[0151] Step 1616: In response to the plan execution request for the target release plan, send data preparation requests for each task node to the data preparation device corresponding to each task node.

[0152] Step 1618: Upon receiving data preparation success information from the task processing devices corresponding to each task node, send a data review request for the data to be published for each task node to the review device.

[0153] Step 1620: After confirming that the data to be published for each task node has been approved, send the task execution instruction for the corresponding task node to the task processing device corresponding to each task node.

[0154] In the above embodiments, a graphical interface and multiple terminals are used to collaboratively process the release plan, and a unified review method is adopted for review, which improves the processing efficiency of the release plan.

[0155] Traditional technologies lack web-based online graphical systems that provide the ability for multiple users to simultaneously edit and publish workflows. This results in complex workflows, inconvenient user operation, and low orchestration efficiency. Furthermore, existing technologies do not utilize existing data to assist in workflow orchestration, such as inter-module call relationships and accumulated system experience, limiting the system's ability to provide sufficient auxiliary orchestration capabilities. Traditional technologies also lack web-based SVG technology for graphical rendering, hindering image vectorization and the ability to support image modules of arbitrary sizes, leading to poor performance and rendering quality. They also lack integration methods with external systems, making them difficult to apply to task systems dependent on WeChat Pay's publishing features, thus limiting their applicability. Traditional technologies cannot provide a universal task system to represent workflows for any scenario, requiring manual intervention and exhibiting weak scalability. Finally, they cannot leverage social applications or email systems to remind and assist developers in performing publishing tasks, demonstrating poor localization capabilities.

[0156] The release process processing method provided in this application embodiment uses a graphical multi-user collaborative web interface to display dependencies in the form of a DAG graph workflow, describe the task execution process, and present a task execution flow that is easy for users to understand. The system performs security checks on the release process through user-defined dependencies, inter-module call relationships, and accumulated experience relationships in the system, ensuring the correctness, accuracy, and orderliness of the process execution. The state transition of system tasks is described by a finite state machine, and external system access capabilities are provided through standardized APIs. Unified management and approval are implemented to manage the release and dependencies of any system that meets the requirements. A general task module is provided for manually advancing the state of any non-standard system.

[0157] This application provides a graphical release workflow management system. The web-based system is user-friendly for distributing, viewing, and collaboratively publishing releases, providing the ability to orchestrate release workflows. It leverages existing system module call relationships and accumulated experience data to offer a release plan module and dependency task recommendation and checking functions, assisting in the orchestration of the release workflow and the correctness checking of the release process. Using HTML5 SVG technology, it provides a vectorized image representation of the release workflow workflow, resulting in better rendering performance and visual presentation. A standardized API allows access from any system, including WeChat Pay's internal system. A general task concept is provided for systems that cannot be integrated, allowing for manual handling. It integrates with common software such as social applications and email, and standardizes the API to remind developers of the execution status of the release plan and guide their actions. A unified approval scheme is provided; after unified approval by this system, the task system can directly execute based on the system's approval result without further approval. The system can also record detailed steps such as system execution time and manual response time, and output corresponding reports for the team to optimize the release execution workflow and identify process defects.

[0158] The release process processing method provided in this application can be applied to the release plan of any application, including but not limited to the release plans of social applications or financial applications. Taking the release plan of a social application as an example, based on the release process processing method provided in this application, a flowchart for the release plan of the social application can be generated in a collaborative manner. Once the flowchart is completed, the release plan can be executed to perform the release tasks of each task node in the flowchart. The status of each task node and the status of the release plan can be updated in real time and displayed in the flowchart for timely understanding of the release plan's progress. The release process processing method provided in this application can improve the processing efficiency of release plans.

[0159] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0160] Based on the same inventive concept, this application also provides a release process processing apparatus for implementing the release process processing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more release process processing apparatus embodiments provided below can be found in the limitations of the release process processing method described above, and will not be repeated here.

[0161] In some embodiments, such as Figure 18 As shown, a publishing process processing device is provided, including: an edit request receiving module 1802, a flowchart updating module 1804, an inspection module 1806, an information sending module 1808, and a status updating module 1810, wherein:

[0162] The edit request receiving module 1802 is used to receive edit requests for the flowchart of the target release plan sent by multiple terminals based on at least one terminal in the release process processing page; the multiple terminals respectively display the flowchart of the target release plan and the release plan status of the target release plan in the release process processing page.

[0163] The flowchart update module 1804 is used to synchronously update the flowcharts of the target release plan displayed on multiple terminals based on editing requests.

[0164] The inspection module 1806 is used to inspect the connection relationships between task nodes in the flowchart of the target release plan using a set of historical task connection relationships; the set of historical task connection relationships includes the connection relationships between task nodes in the flowcharts of multiple historical release plans.

[0165] The information sending module 1808 is used to send connection relationship abnormality prompt information to the multiple terminals when it is found that there is an abnormality in the connection relationship between the task nodes in the flowchart of the target release plan, so that the multiple terminals display the connection relationship abnormality prompt information on the release process processing page.

[0166] The status update module 1810 is used to update the release plan status of the target release plan displayed on multiple terminals in response to a plan status change request for the target release plan.

[0167] In some embodiments, the apparatus is further configured to, in response to a copy request for a created first release plan sent by a terminal among a plurality of terminals, generate a target release plan based on a flowchart of the first release plan; send plan generation confirmation information for the target release plan to each terminal among the plurality of terminals, so that each terminal displays an editing entry for the target release plan; the editing entry is used to trigger the display of the flowchart of the target release plan.

[0168] In some embodiments, the flowchart of the target release plan includes a task card for a first task node; the flowchart update module is further configured to update the display of the task card of the first task node displayed on multiple terminals based on the edit request, when the edit request is triggered based on the task card of the first task node and the information requested to be edited by the edit request is related to the task card of the first task node.

[0169] In some embodiments, the flowchart update module is further configured to, when an edit request is used to request the addition of a second task node, determine a third task node that is adjacent to the second task node from the flowchart of the target release plan; and send a connection relationship establishment request to multiple terminals to establish a connection relationship between the second task node and the third task node, so that the connection relationship between the second task node and the third task node is displayed in the flowchart.

[0170] In some embodiments, the second task node belongs to each of the recommended task nodes of the third task node; the apparatus further includes: a recommended task node determination module, configured to determine each of the recommended task nodes corresponding to the third task node in response to a recommended task viewing request sent by the terminal for the third task node; a task information return module, configured to return the task information of each of the recommended task nodes corresponding to the third task node to the terminal; the task information of the recommended task nodes is used to trigger an edit request to be sent to the server to request the addition of recommended task nodes.

[0171] In some embodiments, the recommended task node determination module is further configured to search for the historical task connection relationship corresponding to the third task node from the historical task connection relationship set based on the task node name of the third task node; the historical task connection relationship set includes the connection relationship between task nodes in the flowcharts of multiple historical release plans; and determine each recommended task node corresponding to the third task node based on the historical task connection relationship corresponding to the third task node.

[0172] In some embodiments, the inspection module is further configured to inspect the connection relationship between the third task node and the second task node using a set of historical task connection relationships; the information sending module is further configured to send a connection relationship abnormality prompt message to the plurality of terminals when an abnormality is detected in the connection relationship between the third task node and the second task node.

[0173] In some embodiments, the status update module is further configured to, in response to a completion request for editing the flowchart of the target release plan triggered on the release process processing page, update the status of the target release plan to an executable state; and send a first status update instruction for the target release plan to the plurality of terminals respectively, so that the plurality of terminals display the status update of the target release plan as an executable state.

[0174] In some embodiments, the flowchart of the target release plan shows the task status of the first task node; the apparatus further includes: an execution instruction sending module, configured to, in response to a plan execution request for the target release plan, send a release task execution instruction for the first task node to the task processing device corresponding to the first task node, so that the task processing device executes the release task corresponding to the first task node; and an update instruction sending module, configured to, when it is determined that the release task of the first task node has been completed, send a task status update instruction for the first task node to multiple terminals, so that the multiple terminals update the task status of the first task node to show as executed.

[0175] In some embodiments, the apparatus is further configured to update the status of the target release plan to the executed state when the task status of each task node in the flowchart of the target release plan is in the executed state; and to send a second status update instruction for the target release plan to multiple terminals respectively, so that the multiple terminals respectively display the status update of the target release plan as the executed state.

[0176] In some embodiments, the execution instruction sending module is further configured to send a data preparation request to the data preparation device corresponding to the first task node; the data preparation device submits the data to be published corresponding to the first task node to the task processing device corresponding to the first task node based on the data preparation request; and upon receiving data preparation success information from the task processing device corresponding to the first task node, sends a task execution instruction for the first task node to the task processing device corresponding to the first task node.

[0177] In some embodiments, the execution instruction sending module is further configured to, upon receiving data preparation success information from the task processing devices corresponding to each task node, send a data review request for the data to be published for each task node to the review device; and, upon determining that the data to be published for each task node has been reviewed and approved, send a task execution instruction for the corresponding task node to the task processing devices corresponding to each task node.

[0178] Each module in the aforementioned publishing process processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0179] In some embodiments, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 19 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data involved in the publishing process method. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a publishing process method.

[0180] In some embodiments, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 20As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a publishing process method. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0181] Those skilled in the art will understand that Figure 19 and Figure 20 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0182] In some embodiments, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described publishing process method.

[0183] In some embodiments, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described publishing process method.

[0184] In some embodiments, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described release process method.

[0185] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0186] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0187] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0188] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for processing a release workflow, characterized in that, The method includes: The system receives an editing request for a flowchart of a target release plan from at least one of a plurality of terminals, sent via a release process processing page. The plurality of terminals respectively display the flowchart of the target release plan and the release plan status of the target release plan on the release process processing page. Based on the edit request, the flowcharts of the target release plan displayed on the multiple terminals are updated synchronously. The connection relationships between task nodes in the flowchart of the target release plan are checked using a set of historical task connection relationships; the set of historical task connection relationships includes the connection relationships between task nodes in the flowcharts of multiple historical release plans. If an anomaly is detected in the connection relationship between task nodes in the flowchart of the target release plan, an anomaly message is sent to the multiple terminals so that the multiple terminals display the anomaly message on the release process processing page. In response to a plan status change request for the target release plan triggered on the release process processing page, the release plan status of the target release plan displayed on the multiple terminals is updated.

2. The method according to claim 1, characterized in that, The method further includes: In response to a copy request for a first release plan sent by one of the plurality of terminals, the target release plan is generated based on a flowchart of the first release plan; A plan generation confirmation message for the target release plan is sent to each of the plurality of terminals, so that each of the plurality of terminals displays the editing entry of the target release plan; the editing entry is used to trigger the display of the flowchart of the target release plan.

3. The method according to claim 1, characterized in that, The flowchart of the target release plan includes a task card for a first task node; the step of synchronously updating the flowchart of the target release plan displayed on the multiple terminals based on the editing request includes: When the edit request is triggered based on the task card of the first task node, and the information requested to be edited by the edit request is related to the task card of the first task node, the task cards of the first task node displayed on the multiple terminals are updated based on the edit request.

4. The method according to claim 1, characterized in that, The step of synchronously updating the flowchart of the target release plan displayed on the multiple terminals based on the editing request includes: In the case where the edit request is for requesting the addition of a second task node, a third task node that is adjacent to the second task node is determined from the flowchart of the target release plan; A connection establishment request is sent to the plurality of terminals to establish a connection between the second task node and the third task node, so that the connection between the second task node and the third task node is displayed in the flowchart.

5. The method according to claim 4, characterized in that, The second task node belongs to each of the recommended task nodes of the third task node; the method further includes: In response to a recommended task viewing request sent by the terminal for the third task node, determine each recommended task node corresponding to the third task node; The task information of each recommended task node corresponding to the third task node is returned to the terminal; the task information of the recommended task nodes is used to trigger an edit request to be sent to the server to request the addition of the recommended task node.

6. The method according to claim 5, characterized in that, The process of determining the recommended task nodes corresponding to the third task node includes: Based on the task node name of the third task node, the historical task connection relationship corresponding to the third task node is searched from the historical task connection relationship set; the historical task connection relationship set includes the connection relationship between task nodes in the flowcharts of multiple historical release plans; Based on the historical task connection relationship corresponding to the third task node, each recommended task node corresponding to the third task node is determined.

7. The method according to claim 4, characterized in that, The step of checking the connection relationships between task nodes in the flowchart of the target release plan using the historical task connection relationship set includes: The connection relationship between the third task node and the second task node is checked using the historical task connection relationship set; When an anomaly is detected in the connection relationship between task nodes in the flowchart of the target release plan, sending an anomaly message to the multiple terminals includes: If an anomaly is detected in the connection relationship between the third task node and the second task node, an anomaly message is sent to the multiple terminals.

8. The method according to claim 1, characterized in that, The step of updating the release plan status of the target release plan displayed on the multiple terminals in response to a plan status change request for the target release plan triggered on the release process processing page includes: In response to a completion request for editing the flowchart of the target release plan triggered on the release process processing page, the status of the target release plan is updated to the executable status; A first status update instruction for the target release plan is sent to each of the plurality of terminals, so that the plurality of terminals display the status update of the target release plan as executable.

9. The method according to claim 8, characterized in that, The flowchart of the target release plan displays the task status of the first task node; the method further includes: In response to a plan execution request for the target release plan, a release task execution instruction for the first task node is sent to the task processing device corresponding to the first task node, so that the task processing device executes the release task corresponding to the first task node. If it is determined that the task to be published by the first task node has been completed, a task status update instruction for the first task node is sent to the plurality of terminals, so that the plurality of terminals display the task status of the first task node as executed.

10. The method according to claim 9, characterized in that, The method further includes: If the task status of each task node in the flowchart of the target release plan is determined to be in the executed state, the status of the target release plan is updated to the executed state. A second status update instruction for the target release plan is sent to each of the plurality of terminals, so that the plurality of terminals respectively display the status update of the target release plan as executed.

11. The method according to claim 9, characterized in that, Sending the task execution command to the task processing device corresponding to the first task node includes: A data preparation request is sent to the data preparation device corresponding to the first task node; based on the data preparation request, the data preparation device submits the data to be published corresponding to the first task node to the task processing device corresponding to the first task node. Upon receiving a data preparation success message from the task processing device corresponding to the first task node, a task execution command is sent to the task processing device corresponding to the first task node.

12. The method according to claim 11, characterized in that, Upon receiving successful data preparation information from the task processing device corresponding to the first task node, sending a task execution command to the task processing device corresponding to the first task node includes: Upon receiving successful data preparation information from the task processing devices corresponding to each task node, a data review request for the data to be published for each task node is sent to the review device. Once it is confirmed that all data to be published at each task node has been approved, a task execution instruction for the corresponding task node is sent to the task processing device for each task node.

13. A publishing process processing device, characterized in that, The device includes: The edit request receiving module is used to receive an edit request for the flowchart of the target release plan sent by at least one of multiple terminals based on the release process processing page; the multiple terminals respectively display the flowchart of the target release plan and the release plan status of the target release plan on the release process processing page; The flowchart update module is used to synchronously update the flowcharts of the target release plan displayed on the multiple terminals respectively based on the edit request; The inspection module is used to inspect the connection relationships between task nodes in the flowchart of the target release plan using a set of historical task connection relationships; the set of historical task connection relationships includes the connection relationships between task nodes in the flowcharts of multiple historical release plans. The information sending module is used to send connection relationship abnormality prompt information to the multiple terminals when it is found that there is an abnormality in the connection relationship between the task nodes in the flowchart of the target release plan, so that the multiple terminals display the connection relationship abnormality prompt information on the release process processing page; The status update module is used to update the release plan status of the target release plan displayed on the multiple terminals in response to a plan status change request for the target release plan triggered on the release process processing page.

14. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 12.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 12.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 12.

Images