Method, device, electronic device and storage medium for generating a project flow

Abstract

An embodiment of the present disclosure provides a method, an apparatus, an electronic device, and a storage medium for generating a project flow, the method including: determining at least one process node corresponding to a target to-be-deployed project; determining node attribute information of the at least one process node; determining node dependencies of the at least one process node; and determining execution project flow information corresponding to the target to-be-deployed project based on the node dependencies and the node attribute information.

Description

[Technical Field]

[0001] This application claims priority to a Chinese patent application bearing application number 202111422126.4, filed with the State Intellectual Property Office of China on November 26, 2021, the entire contents of which are incorporated herein by reference.

[0002] TECHNICAL FIELD The present disclosure relates to the field of computer technology, for example, to a method, an apparatus, an electronic device, and a storage medium for generating a project flow. [Background technology]

[0003] When a company develops a product or expands its business in response to market and user needs, the relevant internal team must first establish a corresponding project based on the current work content. Project managers must organize and plan the project from the overall and detailed perspectives to promote the work of multiple stages of the project.

[0004] However, as the scale of a project continues to expand and the complexity of the project's multiple stages continues to deepen, the task of organizing and planning the project process becomes increasingly difficult. At the same time, there is a lack of effective means to organize and integrate the work content of the multiple stages of a project, which results in low project implementation efficiency. Summary of the Invention

[0005] The embodiments of the present disclosure provide a method, an apparatus, an electronic device, and a storage medium for generating a project flow that provides a standard and concise means for organizing and planning a project and improves the convenience of building a corresponding project process based on an actual project.

[0006] In a first aspect, an embodiment of the present disclosure comprises: determining at least one process node corresponding to a target placement awaiting project and determining node attribute information of the at least one process node; determining node dependencies of the at least one process node; The target placement is determined based on the node dependency relationship and the node attribute information. Wait and determining execution project flow information corresponding to the project.

[0007] In a second aspect, an embodiment of the present disclosure comprises: a process node determination module configured to determine at least one process node corresponding to a target placement-awaiting project and determine node attribute information of the at least one process node; a node dependency determination module configured to determine node dependencies of the at least one process node; The target placement is determined based on the node dependency relationship and the node attribute information. Wait An apparatus for generating a project flow is further provided, comprising: an execution project flow information determination module configured to determine execution project flow information corresponding to the project.

[0008] In a third aspect, an embodiment of the present disclosure comprises: one or more processors; a storage device configured to store one or more programs; The present invention further provides an electronic device that, when the one or more programs are executed by the one or more processors, causes the one or more processors to implement a method for generating a project flow described in any of the embodiments of the present disclosure.

[0009] In a fourth aspect, an embodiment of the present disclosure further provides a storage medium including computer-executable instructions, the computer-executable instructions being configured, when executed by a processor of a computer, to perform a method for generating a project flow according to any of the embodiments of the present disclosure. [Brief explanation of the drawings]

[0010] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and components are not necessarily drawn to scale.

[0011] [Figure 1] FIG. 1 is a flow diagram of a method for generating a project flow according to an embodiment of the present disclosure. [Figure 2] FIG. 10 is a schematic flow diagram of a method for generating a project flow according to another embodiment of the present disclosure. [Figure 3] FIG. 10 is a schematic diagram of a final generated project flow according to one embodiment of the present disclosure. [Figure 4] 1 is a template for generating a project flow according to one embodiment of the present disclosure. [Figure 5] FIG. 10 is a schematic flow diagram of a method for generating a project flow according to another embodiment of the present disclosure. [Figure 6] 10 illustrates a node information editing page according to an embodiment of the present disclosure. [Figure 7] 1 is a node scheduling page according to one embodiment of the present disclosure. [Figure 8] 10 illustrates a node-associated role selection page according to one embodiment of the present disclosure. [Figure 9] FIG. 2 is a structural block diagram of an apparatus for generating a project flow according to an embodiment of the present disclosure. [Figure 10] 1 is a structural schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] It should be understood that steps recited in method embodiments of the present disclosure may be performed in different orders and / or in parallel. Also, method embodiments may include additional steps and / or omit performance of steps shown. The scope of the present disclosure is not limited in this respect.

[0013] As used herein, the term "comprises" and variations thereof are intended to be open inclusive, i.e., "including, but not limited to." The term "based on" means "based at least in part on." The term "in one embodiment" refers to "at least one embodiment," the term "in another embodiment" refers to "at least one other embodiment," and the term "in some embodiments" refers to "at least some embodiments." Relevant definitions of other terms are provided below.

[0014] It should be noted that the concepts of "first," "second," etc. referred to in this disclosure are merely intended to distinguish between different devices, modules, or units, and are not intended to limit the order or interdependence of the functions performed by these devices, modules, or units.

[0015] It should be understood that the modifications "one" and "multiple" referred to in this disclosure are exemplary and not limiting, and that one of ordinary skill in the art would understand "one or more" unless otherwise specified herein.

[0016] 1 is a schematic diagram of a method for generating a project flow according to an embodiment of the present disclosure. This embodiment is applicable to a situation in which an execution project flow is determined for a plurality of projects to be deployed. The method can be executed by an apparatus for generating a project flow, which can be realized in the form of software and / or hardware, and the hardware can be an electronic device such as a mobile terminal, a PC terminal, or a server.

[0017] Before introducing this technical solution, an application scenario will be described as an example. This technical solution can be applied to any scenario where a project flow needs to be generated for a project. For example, an enterprise may create a project according to market and user needs and want to create a visualized and digitized project flow for the project. In this case, the execution project flow can be determined based on this technical solution.

[0018] As shown in FIG. 1, the method of this embodiment includes:

[0019] In S110, at least one process node corresponding to the target allocation waiting project is determined, and node attribute information of the at least one process node is determined.

[0020] For a project established by an enterprise for a specific product or business, relevant personnel need to establish a project process corresponding to the actual work content of the project, so as to grasp and control multiple stages within the project after it is deployed. For example, personnel need to first clarify the needs and actual work content of the project, then organize and plan the entire project according to the needs of project management, divide the project into multiple stages, determine the main idea corresponding to the executors and work content of each stage of the project, and finally obtain a project process in the form of a document, flowchart, or other specific form corresponding to the project on a computer.

[0021] Based on this, in this embodiment, if a project or product needs to be completed and a corresponding implementation project needs to be deployed, this project or product can be set as a target deployment waiting project, such as a project established by an enterprise to evaluate and develop an Internet product after it has been designed and released in response to user needs.

[0022] In this embodiment, the process node is a carrier of information related to multiple stages of a target deployment project, and there may be one or more, and the specific number is determined according to the actual work content of the project and the needs of project management. At the same time, one process node may correspond to a certain stage in the project, or to a certain step in a single stage of the project. For example, the process nodes of a target deployment project include a review initiation node, a score estimation node, a needs profit analysis node, a development node, a test node, and a release node, among which the review initiation node, the score estimation node, and the needs profit analysis node correspond to the start-up stage of the project, the development node and the test node correspond to the development and testing stage of the project, and the release node corresponds to the online stage of the project.

[0023] For multiple process nodes in the target allocation project, there is also corresponding node attribute information. In this embodiment, the node attribute information may be information reflecting the workers and work content at each stage of the project. For example, the node attribute information of the development node in the above example may include the department developing the product, the developer, and the time period required for development.

[0024] In actual application, for a target project to be allocated, its process nodes and the node attribute information of each process node can be determined by a specific platform or system. For example, after determining a target project to be allocated, an operator can use a specific control in a platform or system for generating a project flow to establish a corresponding process node for each stage or step of the project according to the actual work content of the project and the needs of project process management, and configure corresponding node attribute information for each process node according to the actual work content of the project.

[0025] Continuing with the above example, if the project to be deployed includes a startup stage, a development and testing stage, and an online deployment stage, the project manager can enter the space deployment background in the project flow generation platform and, by clicking, dragging, etc., select from multiple pre-deployed nodes suitable for the project, a review trigger node, a score estimation node, a needs profit analysis node, etc., as process nodes representing the above multiple stages. By selecting or editing the corresponding responsible department, developer, and development time period for each process node according to the actual work content of the project and the needs of project management, the node attribute information of each process node can be obtained.

[0026] At S120, node dependencies of at least one process node are determined.

[0027] In this embodiment, after the process nodes and the node attribute information of each process node are determined for the target deployment project, it is necessary to further determine the node dependency of at least one process node. Among these, node dependency is also called a logical relationship. In project management, when there is only one process node, the node dependency of the node is obtained once the start and end information of the node is determined. When there are multiple process nodes, the node dependency indicates a relationship in which a change in one of the two nodes affects the other. Typically, mandatory node dependencies include (inherent node dependencies between multiple nodes), flexible node dependencies (node ​​dependencies determined by the actual work content of the project and the needs of project management), and external node dependencies (node ​​dependencies between nodes and other external factors). Those skilled in the art should understand that node dependencies between process nodes can at least reflect the execution order of work in multiple stages of a project.

[0028] It should be noted that when generating a project flow for a target deployment project using a specific platform or system, there are multiple ways to determine the node dependencies of process nodes. For example, a user can connect multiple process nodes by clicking, dragging, etc. It is understood that the connection lines between nodes may be directional, and that the relationship between nodes may be determined by setting corresponding indicators for each process node and editing the relationship between the indicators in the deployment interface. Those skilled in the art should understand that the method for determining process node dependencies can be selected depending on the platform or system actually selected by the user, and the embodiments of the present disclosure are not specifically limited thereto.

[0029] Continuing with the above example, based on the platform or system that generates the project flow, it is determined that the process nodes of the target deployment project include a review initiation node, a score estimation node, a needs and profit analysis node, a development node, a test node, and a release node. By using a dragging method to draw connecting lines with arrows between the multiple nodes, the project manager can determine the execution order of the work in the multiple stages of the project as follows: first, initiate a review of the project, then evaluate the project, then analyze the needs and profit of the project, then develop a product related to the project, test the product, and finally put the project product online and release it.

[0030] In S130, a target layout is determined based on the node dependency relationship and the node attribute information. Wait Execution project flow information corresponding to the project is determined.

[0031] In this embodiment, after the node attribute information of the process nodes for the target allocation waiting project is determined, based on the node dependency relationships between the determined process nodes, the association between the node attribute information of multiple nodes can be further established to obtain the execution project flow of the project.

[0032] For example, execution project flow information of the target deployment-awaiting project can be determined based on the determined node dependencies and node attribute information. In this embodiment, the execution project flow can be understood as the project process of the target deployment-awaiting project, i.e., the execution order of the substantive work of multiple stages of the project. The execution project flow information also includes node attribute information of at least one process node, as well as the relationship between the performers of the multiple nodes and the relationship between the substantive work content of the multiple stages. Finally, the determined execution project flow information is displayed in a specific platform or system in the form of a document, a flowchart, or other format.

[0033] Continuing with the above example, after determining the node dependencies of the review trigger node, score estimation node, needs profit analysis node, development node, test node, and release node of a target deployment awaiting project, as well as the responsible department, executor, and task execution period of each node, a platform or system for generating a project flow can determine the handover tasks of the responsible department of each node of the project, the task files that need to be transmitted by the executor of each node, and the time period of each node's task execution period throughout the project.The platform or system displays the project flowchart on a specific page, and project personnel can click on multiple nodes in the flowchart to check the node attribute information of the node and the node dependency relationship between the node and other nodes.

[0034] By determining the execution project flow information of the target deployment project, the work tasks of multiple nodes of the project can be automatically organized and planned in a standardized manner from the overall perspective and in detail. After the project is deployed, the project manager can monitor the progress and completion status of each stage of the project according to the obtained project process, thereby achieving highly efficient management of the project. For example, in a specific platform or system, the project manager can view a dynamic project process diagram on a specific page and understand the progress and completion status of the project based on the different status information of the multiple nodes in the diagram. At the same time, the execution project flow information includes the node dependency of at least one process node of the project. Multiple teams responsible for project evaluation, research and development, and online implementation can determine their respective work content and handover tasks according to the node dependency, thereby achieving integration among multiple departments within the team and executors of multiple stages of the project, which is beneficial to the efficient promotion of the project.

[0035] After obtaining the execution project flow information based on the node attribute information and the node dependency relationships of at least one process node, the obtained execution project flow information and project process diagram may be stored in the template repository of the platform or system in the form of a template, and the template may be labeled according to the description information of the project. If execution project flow information and project process diagrams need to be determined for other projects and have similar work content and project management needs to the project awaiting target deployment, the execution project flow information and project process diagrams for the other projects can be directly determined by selecting the currently saved template from the template repository. Those skilled in the art should understand that in a platform or system for generating project flows, a user may also reasonably modify some of the deployment information in the template (e.g., the node attribute information of each process node and the node dependency relationships between nodes) according to the actual situations of other projects, and the embodiments of the present disclosure will not be repeated here.

[0036] The technical solution of this embodiment determines at least one process node corresponding to the project waiting for target allocation, and determines the node attribute information of each process node to clarify the specific work content of each process of the project, determines the node dependency of at least one process node, and performs target allocation based on the node dependency and node attribute information. Wait The execution project flow information corresponding to the project is determined, thereby providing a standard and concise means for organizing and planning the project and improving the convenience of building the corresponding project process based on the actual project. At the same time, the resulting clear and digitized project process facilitates workers' monitoring and management of the entire project and the work at multiple stages, which is beneficial to promoting the high efficiency of the project.

[0037] 2 is a schematic diagram of a method for generating a project flow according to another embodiment of the present disclosure. Based on the above embodiment, a process node is determined according to the execution process of a project. When a trigger of a process node is detected, a node information editing page is displayed, allowing the user to customize node attribute information with greater flexibility. The node dependency relationships between nodes are determined according to the predecessor node indicators, or the node dependency relationships between nodes are determined based on the execution process of the project. This realizes logical organization of the execution process of the project, determines the execution order of multiple process nodes based on the node dependency relationships, and generates execution project flow information, which is beneficial to the efficient promotion of the project. For example, the technical solution of this embodiment may be referred to. Technical terms similar to or corresponding to those in the above embodiment will not be repeated here.

[0038] As shown in FIG. 2, the method includes the following steps:

[0039] In S210, an execution process corresponding to the target allocation waiting project is determined, and at least one process node is determined according to the execution process.

[0040] The execution process corresponding to the target deployment project includes multiple stages from project launch to completion. The execution process can be understood as a compilation of the project's actual work content, divided according to the project management needs. To obtain project execution flow information for the project, a specific platform or system can select or create corresponding process nodes for multiple stages in the execution process, and at least one of the determined process nodes corresponds to the execution process. The above process will now be described in detail with reference to Figure 3.

[0041] Referring to FIG. 3, after a target project to be deployed is determined, a space deployment option can be selected in a platform or system for generating a project flow, and a task for deploying the project flow can be created on the corresponding space deployment page for the project. Based on the actual work content of the project and the company's project management needs, it can be determined that the project execution process includes multiple stages, such as project review, research and development, and release. Therefore, on the task processing page for deploying the project flow, the project manager can select or create process nodes, such as needs creation, discussion and alignment, product design, inline review, UX design, technical review, research and development completion, dark launch, release note entry, full release, and termination. It can be understood that the above nodes collectively reflect the project execution process and demarcate and summarize the work content of the project's multiple stages.

[0042] For example, the process nodes include a master process node and a slave process node. Among them, for multiple process nodes corresponding to an executing process, the master process node and the slave process node are relative concepts, and the master-slave concept setting for the process nodes can at least reflect the execution order of the multiple process nodes and the association relationship between the nodes.

[0043] Based on this, in the process of determining at least one process node according to the running process, at least one master process node is determined according to the running process, and for each master process node, when it is detected that the current master process node is triggered, a slave process node corresponding to the current master process node is added, and when it is detected that the slave process node is triggered, the slave process node is set as the current master process node. The process will be described below with reference to FIG. 3.

[0044] Referring to Figure 3, the needs creation node and the discussion and alignment node in the execution process require the project team to first clarify the project needs information and then hold discussions with multiple departments to determine the actual work content of the project. Therefore, the needs creation node corresponding to the first stage of the project may be designated as the master process node, and the discussion and alignment node in the next stage may be designated as the slave process node. After the project manager adds the needs creation node on the relevant page of the space layout according to the execution process, he or she can click on the node. After the operation is detected by the platform or system, a discussion and alignment node corresponding to the next stage of the project can be automatically added for the node.

[0045] Similarly, for the discussion matching node and the product design node, when a trigger operation on the matching node is detected, the platform or system can set the matching node as the current master process node and automatically add a product design node corresponding to the next stage of the project. At the same time, it should be noted that the same master process node may have multiple slave process nodes, not just multi-level ones. Taking the project execution process in FIG. 3 as an example, if the needs creation node is set as the master process node, the discussion matching node and the product design node corresponding to multiple stages of the project after this node are multi-level slave process nodes of this node. At the same time, if the research and development completion node is set as the master process node, the dark launch node and the release note entry node are both slave process nodes of this node. It can be understood that when multiple slave process nodes are at the same level, work tasks corresponding to multiple nodes can be executed in parallel.

[0046] Since the execution process and process nodes of the target allocation project are generated by a specific platform or system, before the process nodes are determined, the platform or system may further pre-edit multiple templates that are compatible with multiple types of projects and have a certain degree of versatility, so that the process nodes for the execution process of the project can be directly determined by the templates.

[0047] For example, when it is detected that the template creation control on the target page is triggered, a configuration page corresponding to the creation of the template is popped up, in which the configuration page includes a template type control and a control for whether to reuse the template in the related art. Based on the trigger operation on the configuration page, a waiting-to-use template corresponding to the target waiting-to-be-configured project is determined, and at least one process node corresponding to the target waiting-to-be-configured project is determined based on the waiting-to-use template.

[0048] In actual applications, projects created by enterprises are generally complex. Therefore, multiple process nodes determined for the project execution process may be as shown in FIG. 4. As can be seen from FIG. 4, multi-level process nodes represent multiple stages of a project, and a single project stage may further include multiple work tasks. A project engineer can select a node to set it as a master process node (e.g., the "Data Development" node selected by the project engineer in FIG. 4). At this time, by clicking the plus sign in the upper right corner of the node or the "Add Node" control in the lower left corner, slave process nodes corresponding to subsequent stages of the project (e.g., the "Data Test" node in FIG. 4) can be created for the node. At the same time, since a platform or system for generating project flows can provide template creation and reuse functions, after generating an execution project flow for a project according to the subsequent steps of the embodiments of the present disclosure, the generated project flow can be saved, updated, or deleted as a template for a certain type of project by clicking another control in the lower left corner.

[0049] In S220, when it is detected that the process node has been triggered, a node information editing page corresponding to the process node is displayed, and node attribute information of the process node is edited in at least one editable item of the node information editing page.

[0050] In this embodiment, after multiple process nodes are determined for the execution process of the target project to be allocated, if a trigger operation for the node is detected, a node information editing page may be displayed. For example, after a project manager clicks on a process node on the platform or system space allocation page, the current space allocation page transitions to a node information editing page corresponding to the node. On the node information editing page, multiple editing operations, such as entry, selection, and modification, can be performed on at least the node. It can be understood that the information obtained after the operation is completed is the node attribute information corresponding to the node.

[0051] In addition, the node attribute information includes attribute information of multiple dimensions of the node, and this attribute information can not only reflect the actual work content of multiple stages of the project from multiple dimensions, but also determine the execution logic and execution order of the work corresponding to multiple nodes.

[0052] In S230, determine the node dependency of at least one process node according to the preceding node indicator in the node attribute information, or determine the sequence information of at least one process node according to the execution process of the project waiting for target placement, and determine the node dependency of at least one process node according to the sequence information.

[0053] In this embodiment, there are at least two ways to determine the dependency relationship of at least one process node. The first way is to determine the sequence information of at least one process node in a platform or system that generates a project flow based on the execution process of a project waiting for target allocation, and establish node dependency relationships among multiple process nodes according to the determined sequence information. In this way, it can be understood that the node dependency relationships among nodes are essentially determined according to the actual work content and project management needs in multiple stages of the project.

[0054] The second method determines a predecessor node indicator for each node in the node attribute information and determines the node dependency of at least one process node based on the indicator. A predecessor node can be understood as a node whose execution process does not transition to the current node associated with the node until the project task or project event represented by the predecessor node is completed. A current node can have one or more predecessor nodes. At the same time, the current node itself can be considered as a predecessor node of one or more nodes in the subsequent execution process. In a platform or system for generating a project flow, such node dependency is determined by the predecessor node indicator in the node attribute information of the current node. The following description continues to use FIG. 4 as an example.

[0055] Referring to FIG. 4, when the "Waiting for Release" node is set as the current node, the predecessor node of the node can be determined by editing the node attribute information on the node information editing page. For example, five node indicators, namely "iOS Test," "Android Test," "Service Test," "Front-End Test," and "Data Test," can be selected as predecessor node indicators on the page. Based on these five predecessor node indicators, the platform or system can determine the node dependency between these five nodes and the "Waiting for Release" node. That is, the iOS test task, Android test task, service test task, front-end test task, and data test task must all be completed before the project execution process will flow to the "Waiting for Release" node. At the same time, in the node information editing pages corresponding to the "Online Security Review" node and the "Open Platform File Update" node, the node indicators of the "Waiting for Release" node are set as the predecessor node indicators of the two nodes, thereby determining the node dependency between the online security review task, the open platform file update task, and the waiting for release task. That is, only after the execution of the task or event corresponding to the "Waiting for Release" node is completed, the execution process of the project will flow to the "Online Security Review" node and the "Open Platform File Update" node.

[0056] For example, the preceding node indicator in the node attribute information is adjusted in accordance with the node dependency relationship, and the node attribute information is updated based on the adjusted preceding node indicator.

[0057] In actual application, when the actual work content or project management needs of a target deployment project change, not only will the node attribute information of the related process nodes change, but new node dependencies may also arise between different process nodes. For a platform or system that generates a project flow, when generating a project flow based on new node dependencies between multiple process nodes of a project, it is necessary to modify the preceding node indicators in the related node attribute information according to the node dependencies so as to realize the update to the node attribute information. The following explanation continues to take Figure 4 as an example.

[0058] Referring to Figure 4, if a company decides not to continue developing applications for iOS devices after two reviews of a target deployment project, it needs to delete the iOS-related branches from the project execution process. Based on this, the platform or system that generates the project flow can delete the "iOS score estimation scheduling," "iOS development," and "iOS testing" nodes. At the same time, in the node attribute information corresponding to the "Waiting for release" node, the node indicator corresponding to the "iOS testing" node among its predecessor node indicators can be deleted, thereby updating the node attribute information of the related process nodes of the project.

[0059] In S240, an execution order corresponding to at least one process node is determined based on the node dependency relationship, and execution project flow information of the project awaiting target placement is generated according to the node name and node dependency relationship in the node attribute information of the at least one process node.

[0060] In this embodiment, after the node dependency of at least one process node of the target deployment project is determined, the platform or system for generating a project flow determines the execution order corresponding to at least one node. It can be understood that the trigger conditions, completion conditions, and relationship between the tasks or events of multiple stages of the project are determined. According to the node names in the multiple node attribute information and the node dependency relationships between the multiple nodes, execution project flow information can be generated in the form of a flowchart. At the same time, the project flow information is displayed on a specific page of the platform or system so that relevant workers can monitor and manage the completion status of the entire project and the tasks of multiple stages. The following explanation takes Figure 3 as an example.

[0061] Referring to Figure 3, after the node attribute information of multiple nodes of the project and the node dependencies between the nodes are determined, multiple process nodes can be connected with lines to display the execution process of the project awaiting target deployment in a left-to-right format. At the same time, each node is assigned a symbol representing node status information, such as a circle in the diagram, where different symbols can represent different status information. A circle with a check mark indicates that the execution of the task or event corresponding to the node has been completed and passed the assessment of the relevant authorized user. A black circle indicates that the task or event corresponding to the node has not yet been completed and the pre-assigned deadline for the task or event has passed, requiring special attention. A solid circle indicates that the project is currently executing the task or event corresponding to the node. A gray circle indicates that the project execution process has not yet shifted to the node, i.e., the task or event of the preceding node related to the node has not yet been completed, and the task or event of the node cannot be triggered.

[0062] In actual application, after generating execution project flow information for a project awaiting target deployment, the project personnel can monitor and manage multiple process nodes through a platform or system. At the same time, the personnel corresponding to the multiple process nodes can similarly obtain the node attribute information of the corresponding nodes through the platform or system to clarify their corresponding relationships with other departments in the current project, and at the same time, execute corresponding tasks or events based on the node attribute information.

[0063] The technical solution of this embodiment determines process nodes according to the execution process of the project; when it is detected that a process node is triggered, a node information editing page is displayed, allowing the user to customize node attribute information with greater freedom; and determines node dependencies between nodes according to the preceding node indicators, or determines node dependencies between nodes based on the execution process of the project, thereby realizing logical organization of the execution process of the project, determining the execution order of multiple process nodes based on the node dependencies, and generating execution project flow information, which is beneficial to promoting the project with high efficiency.

[0064] 5 is a schematic diagram of a method for generating a project flow according to another embodiment of the present disclosure. Based on the above embodiment, the node attribute information includes multi-dimensional attribute information of the process node. By editing and configuring this information on the node editing page, a highly customized project execution process for a target allocation is realized in a visualized manner, and at the same time, a means for the user to modify the project execution process is provided. The technical solution of this embodiment can be referred to for an exemplary embodiment. Technical terms similar to or corresponding to those in the above embodiment will not be repeated here.

[0065] As shown in FIG. 5, the method includes the following steps:

[0066] In S310, at least one process node corresponding to the target allocation waiting project is determined, and node attribute information of the at least one process node is determined.

[0067] At S320, node dependencies of at least one process node are determined.

[0068] In step S330, a target layout is determined based on the node dependency relationship and the node attribute information. Wait Execution project flow information corresponding to the project is determined.

[0069] In S340, the node corresponding to the node attribute information is processed based on the edit status of each attribute information in the node attribute information.

[0070] In this embodiment, the node attribute information includes multiple dimensions of attribute information of the node. For example, the node-related information includes at least one of the following: node indicator, node name, node collaborating user, node authorization information, node execution time length, node operation type, node transition type, node restriction type, preceding node indicator, and node event. The editing page can include editable items corresponding to any of the above information. The above information will be described in detail below with reference to FIG. 6.

[0071] Referring to Figure 6, a node indicator is the ID of a process node. A node indicator is unique for any node. Setting a node indicator for each node is beneficial for a platform or system to call these nodes through an application programming interface (API) and further realize node configuration and project flow generation. For the "Data Development" process node, the corresponding node indicator is "waiting_for_data_development." The node name reflects the event that the project needs to complete at that node and may be a key field. For example, "Data Development" indicates the work related to big data development in the project that needs to be completed at that stage. Naming project stages facilitates intuitive display of the project task stages corresponding to the node to users and also benefits the user's interaction with the platform or system that generates the project flow.

[0072] In this embodiment, if the node label of the current process node changes and an upgrade operation is detected for the current process node, the current process node and the process nodes dependent on the current process node are deleted. For example, a project manager can modify the node label of the current node in a platform or system. After the modification operation for the node label is detected in the platform or system, the current node and the node attribute information of the node that was previously edited before the node label was modified are deleted. At the same time, other nodes that have node dependencies with the current node are also deleted according to the node dependencies between multiple process nodes. Similarly, the node attribute information already deployed for other nodes is also deleted. This process can be understood as meaning that after modifying the work content of any one current stage of a project, the work content of other stages that have node dependencies with the project stage are also changed.

[0073] Continuing to refer to FIG. 6, during the actual execution of a project, depending on the needs of project management, some nodes in the execution process may require confirmation by multiple people after completion, and the project task will not be transferred to the next node in the execution process until all confirmations by multiple people are completed. Accordingly, the process of editing node attribute information further includes editing a node restriction type, editing a node transfer type, and editing a node collaborating user. For the node restriction type, the option "Is this a restricted node?" can be set to "Yes" or "No," indicating whether the node is a restricted node or an unrestricted node, respectively. For the node transfer type, the option "Is confirmation by multiple people required?" can be set to "Yes" or "No," indicating whether the task corresponding to the node requires confirmation by multiple people after completion, respectively.

[0074] For example, if the node restriction type in the node attribute information of the current process node is Type 1, when processing of the current process node by a target operation user corresponding to Type 1 is detected, the node state of the current process node is changed. Taking the "Data Development" node in Figure 6 as an example, the current process node is set to the restriction type (Type 1) using the "Restricted Node" option in the node attribute information. In this case, after the work task (Data Development Task) of the node is completed, the project manager (the target operation user corresponding to Type 1) must assess and confirm the related work task before the node status information can be changed from "Under Development" to "Development Completed." At the same time, the project will not be transferred to the next node (the "Data Test" node) in the execution process. Note that if the node restriction type is Type 1 and there are multiple corresponding target operation users, the project task will not be transferred in the execution process unless one of the target operation users confirms the completion status of the task for the node.

[0075] For example, if the node restriction type in the node attribute information of the current process node is Type 2 and the node collaborative users include a collaborative user, the node status of the current process node is updated based on the collaborative user's trigger operation on the current process node. Taking the "Data Development" node in Figure 6 as an example, the current process node is set to the non-restricted type (Type 2) according to the option "Whether is this a restricted node?" in the node attribute information, and User A and User B, who are not the project staff, are selected as the node collaborative users. In this case, after the work task (Data Development Task) of the node is completed, not only the project staff confirms the project, but also after either one of the selected node collaborative users A and B confirms the completion status of the task, the node status information can be changed from "Under Development" to "Development Completed," and at the same time, the project will proceed to the next node (the "Data Test" node) in the execution process.

[0076] Continuing to refer to Figure 6, in the node attribute information, the node authorization information needs to be further edited to clarify the executor of the project task corresponding to the node. To this end, the executor of the node project task can be selected from the pre-defined role set in the "Authorization Operation Role" field. For the task "Data Development," the task executor can be selected as "Data Engineer," i.e., the "Data Engineer" will perform work related to big data development. At the same time, the execution time length for the project work of the node can be further specified by selecting "Yes" in the "Whether Scheduling Information Entry Required" field and entering a specific time period as the execution time length for the "Data Development" work. As shown in Figure 7, on the scheduling page corresponding to the node, the execution time length for the Data Engineer can be set to two days, which corresponds to the time period from July 14, 2021, to July 15, 2021, in the project deadline. At the same time, the executor can be added to the current "Data Development" node by clicking the "Add Person" control on the page. If no task executor is selected for the node, the "authorized operation role" of the node defaults to the project manager who creates the project, and at the same time, the node defaults to "unschedulable," meaning there is no need to specify the task execution time.

[0077] Continuing to refer to FIG. 6 , the node attribute information can further include a node operation type. The “Can be deleted?” option can be selected as “Yes” or “No.” It can be understood that the node operation type attribute determines whether the node can be deleted. Therefore, the two options indicate whether the target project does not need to execute the task corresponding to the node. The node can further include an “associated role.” In this embodiment, the “associated role” can determine at least the deletion operation for the associated node. That is, when a role selected in the associated role is deleted from the platform or system, the nodes associated with the selected role will also be deleted in the execution process corresponding to the project.

[0078] For example, if a related role is set for a current process node, the current process node is deleted when the deletion of the related role is detected. As shown in FIG. 8, "Data Engineer" can be selected as the related role of the "Data Development" node from multiple types of roles provided by a preset set of related roles. When the role is deleted from the platform or system, the "Data Development" node corresponding to the role (and multiple nodes involved in subsequent big data tasks) are also deleted. Those skilled in the art should understand that the platform or system can further provide a restoration function for related roles and their associated nodes, and the embodiments of the present disclosure will not be described again here.

[0079] Furthermore, after a node is edited to "deletable", only users with the corresponding operation authority for the node can perform the deletion operation. At the same time, the "deletable" attribute can be edited for a node only if the associated role of the node in the platform or system is deletable, and in this case, the deletion operation is reversible, that is, even if a project manager or a user with the relevant authority accidentally deletes a node, the node can be restored by re-adding the associated role corresponding to the node.

[0080] Continuing to refer to FIG. 6, in the node attribute information, the predecessor node indicator of the current node can be further edited. For example, a predecessor node indicator can be added to "node arrival event," so that an event corresponding to the predecessor node can trigger an event corresponding to the current node. That is, the task of the current node can be triggered after the task corresponding to the predecessor node is completed. For example, if "Data Development" is the current node, its predecessor node indicator can be edited to an indicator corresponding to the "Data score estimation scheduling" node. That is, the execution process will not flow to the big data development task until the relevant worker has performed score estimation scheduling for the big data task of the project. It can be understood that in addition to the function of adding a predecessor node indicator, the platform or system can also provide a function of deleting a predecessor node indicator.

[0081] While editing the preceding node indicator, the event type and transition status information of the current node when the project execution process reaches the current node can also be edited. As shown in Figure 6, after the execution of the score estimation scheduling event of the big data task is completed, the current "Data Development" node can realize the project promotion according to the "event transition" selected in the event type. At the same time, based on the transition status information selected in "Node Reached and Can Transition Below," the node can be adaptively displayed as "Under Development" on the platform or system display page.

[0082] Continuing to refer to FIG. 6 , the node attribute information can further configure a node form for the current node. The node form is used to edit and configure the deliverable list for the process node. Those skilled in the art should understand that multiple process nodes can configure deliverables according to the actual needs of a project, and that a deliverable may be a physical object, such as the hardware of a product, or a virtual object, such as a package file, program code, or component data platform. After editing the node form for a process node, the attribute information of the deliverable can be configured in the form configuration page. For example, if the deliverable corresponding to a process node is a front-end webpage, the attribute information of the deliverable is a link corresponding to the webpage. Those skilled in the art should understand that the attribute information of the deliverable corresponding to the node form of a process node can be configured according to the actual needs of a project, and the embodiments of the present disclosure are not specifically limited thereto.

[0083] When editing and arranging multiple node attribute information based on the node information editing page of a specific platform or system, the user can inquire about a detailed interpretation of the node attribute information by clicking on a question mark or other indicator after each attribute information.

[0084] In S350, after detecting that the task completion information corresponding to the current process node has been filled, the node state of the current process node is changed.

[0085] Continuing to refer to FIG. 6 , the node attribute information can further include editing of the node task or event of the current node. For example, specific event information can be added to the “node completion event” option to mark the current node as completed. At the same time, after the added event information is completed and entered into the node attribute information, the status information of the process node also adaptively changes. This process can be understood to be similar to the process of the node arrival event. For example, for a “Data Development” node, its node completion information may be “Project-related big data platform construction completed.” After an authorized user of the node practically examines the big data and confirms that the completion information is real and reliable, the execution process can be promoted from the current “Data Development” node to the next node, “Data Testing.” At this time, the node status information of the “Data Development” node changes from “Under Development” to “Development Completed.”

[0086] In the technical solution of this embodiment, the node attribute information includes attribute information of multiple dimensions of the process node, and by editing and arranging this information on the node editing page, a high level of customization for the execution process of the project waiting for target allocation can be realized in a visualized manner, and at the same time, a means for the user to modify the execution process of the project can be provided.

[0087] 9 is a structural block diagram of an apparatus for generating a project flow according to an embodiment of the present disclosure, which can execute the method for generating a project flow according to any embodiment of the present disclosure, and includes functional modules corresponding to the execution of the method and beneficial effects. As shown in FIG. 9, the apparatus includes a process node determination module 410, a node dependency determination module 420, and an execution project flow information determination module 430.

[0088] The process node determination module 410 is configured to determine at least one process node corresponding to the target awaiting deployment project and determine node attribute information for the at least one process node.

[0089] The node dependency determination module 420 is configured to determine node dependencies of the at least one process node.

[0090] The execution project flow information determination module 430 determines the target placement based on the node dependency relationship and the node attribute information. Wait The method is configured to determine execution project flow information corresponding to the project.

[0091] Based on the above-mentioned technical solutions, the process nodes include a master process node and a slave process node, and the process node determination module 410 includes an execution process determination unit, a process node determination unit, and a node attribute information editing unit.

[0092] The execution process determination unit is configured to determine an execution process corresponding to the target deployment-ready project, and determine at least one process node according to the execution process.

[0093] The process node determination unit is configured to determine at least one master process node according to the executing process, and for each master process node, add a slave process node corresponding to the current master process node when it is detected that the current master process node is triggered, and set the slave process node as the current master process node when it is detected that the slave process node is triggered.

[0094] The node attribute information editing unit is configured, when it detects that a process node is triggered, to display a node information editing page corresponding to the process node and edit the node attribute information of the process node in at least one editable item of the node information editing page.

[0095] For example, the node dependency determination module 420 is further configured to determine node dependency of at least one process node according to a preceding node indicator in the node attribute information, or to determine order information of at least one process node according to an execution process of the target deployment awaiting project, and determine node dependency of at least one process node according to the order information.

[0096] For example, the apparatus for generating a project flow further comprises a predecessor node indicator adjustment module.

[0097] The antecedent node module adjustment module is configured to adjust an antecedent node indicator in the node attribute information according to the node dependency relationship, and update the node attribute information based on the adjusted antecedent node indicator.

[0098] Based on the above-mentioned technical solutions, the execution project flow information determination module 430 includes a process node execution order determination unit and an execution project flow information generation unit.

[0099] The process node execution order determination unit is configured to determine an execution order corresponding to at least one process node based on the node dependency relationships.

[0100] The execution project flow information generating unit is configured to generate execution project flow information of the target allocation awaiting project according to a node name in the node attribute information of at least one process node and the node dependency relationship.

[0101] Based on the above-mentioned multiple technical proposals, the node attribute information includes at least one of the following: node indicator, node name, node collaborating user, node authorization information, node execution time length, node operation type, node flow type, node restriction type, preceding node indicator, and node event.

[0102] Based on the above-mentioned technical solutions, the project flow generating apparatus further includes a process node processing module.

[0103] The process node processing module is configured to delete the current process node and process nodes on which the current process node depends if it is detected that a node indicator of the current process node has changed and an upgrade operation has been performed on the current process node.

[0104] For example, the process node processing module is further configured to change the node state of the current process node when a node restriction type in the node attribute information of the current process node is a first type and processing of the current process node by a target operation user corresponding to the first type is detected.

[0105] For example, the process node processing module is further configured to, if the node restriction type in the node attribute information of the current process node is a second type and the node collaborating users include a collaborating user, update the node state of the current process node based on a trigger operation of the collaborating user on the current process node.

[0106] For example, the process node processing module is further configured to, if an association role is set for the current process node, delete the current process node when a deletion of the association role is detected.

[0107] Based on the above-mentioned technical solutions, the project flow generating device further includes a node status change module.

[0108] The node state change module is configured to change the node state of a current process node after detecting that the task completion information corresponding to the current process node has been filled.

[0109] The technical solution of this embodiment determines at least one process node corresponding to a project waiting for target allocation, and determines node attribute information of the at least one process node to clarify the specific work content of multiple processes in the project, determines node dependency of the at least one process node, and performs target allocation according to the node dependency and node attribute information. Wait It determines the execution project flow information corresponding to the project, provides a standard and concise means for organizing and planning the project, and improves the convenience of building the corresponding project process based on the actual project. At the same time, the resulting clear and digitized project process facilitates workers' monitoring and management of the entire project and the work at multiple stages, which is beneficial to promoting high-efficiency projects.

[0110] The project flow generating apparatus according to the embodiments of the present disclosure can execute the project flow generating method according to any embodiment of the present disclosure, and includes functional modules and beneficial effects corresponding to the execution of the method.

[0111] The multiple units and modules provided in the above device are merely divided according to functional logic, but are not limited to the above divisions as long as they can realize the corresponding functions. It should be noted that the specific names of the multiple functional units are merely intended to make it easier to distinguish them from each other and are not intended to limit the scope of protection of the embodiments of the present disclosure.

[0112] FIG. 10 is a structural schematic diagram of an electronic device according to an embodiment of the present disclosure. Reference will now be made to FIG. 10 , which illustrates a structural schematic diagram of an electronic device (e.g., a terminal device or server in FIG. 10 ) 500 suitable for implementing an embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-car terminals (e.g., in-car navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. The electronic device illustrated in FIG. 10 is merely an example and does not impose any limitations on the functionality and scope of use of the embodiment of the present disclosure.

[0113] 10, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 501, which can perform various appropriate operations and processes based on a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 506 into a random access memory (RAM) 503. The RAM 503 further stores various programs and data necessary for the operation of the electronic device 500. The processing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An edit / output (I / O) interface 505 is also connected to the bus 504.

[0114] Typically, the I / O interface 505 can be connected to an editing device 506 including, for example, a touch panel, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; a storage device 506 including, for example, a magnetic tape, hard disk, etc.; and a communication device 509. The communication device 509 enables the electronic device 500 to communicate wirelessly or via a wire with other devices to exchange data. While FIG. 10 illustrates the electronic device 500 having various devices, it should be understood that it is not required to implement or include all of the illustrated devices. Instead, more or fewer devices may be implemented or included.

[0115] According to embodiments of the present disclosure, the processes described with reference to the flowcharts above can be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product including a computer program carried on a non-transitory computer-readable medium, the computer program including program code for performing the methods illustrated in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via the communication device 509, installed from the storage device 506, or installed from the ROM 502. When the computer program is executed by the processing device 501, it performs the functions defined by the methods of the embodiments of the present disclosure.

[0116] The names of messages or information interacted between devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0117] The electronic device according to the embodiment of the present disclosure belongs to the same disclosed concept as the method for generating a project flow according to the above embodiment, and the technical details not described in detail in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0118] An embodiment of the present disclosure provides a computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for generating a project flow according to the embodiment.

[0119] It should be noted that the computer-readable medium described above in the present disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the above. The computer-readable storage medium may be, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to, an electrical connection having one or more leads, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium usable by or that contains or stores a program usable in connection with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code carried therein. Such propagated data signals may take various forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may transmit, propagate, or transmit a program for use in or in connection with an instruction execution system, apparatus, or device. Program code contained in a computer-readable medium may be transmitted over any suitable medium, including, but not limited to, electrical wire, optical cable, RF (radio frequency), etc., or any suitable combination of the above.

[0120] In some embodiments, the clients and servers may communicate using any now known or later developed network protocol, such as HTTP (Hyper Text Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include local area networks ("LANs"), wide area networks ("WANs"), networks off networks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), and any now known or later developed networks.

[0121] The computer-readable medium may be included in the electronic device, or may exist independently and not be attached to the electronic device.

[0122] The computer-readable medium carries one or more programs, and the one or more programs are executed by the electronic device, causing the electronic device to: Determine at least one process node corresponding to the target placement awaiting project; and determine node attribute information for the at least one process node; determining node dependencies for the at least one process node; The target placement is determined based on the node dependency relationship and the node attribute information. Wait Execution project flow information corresponding to the project is determined.

[0123] Computer program code for carrying out the operations of the present disclosure can be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may run entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider).

[0124] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, program segment, or portion of code, which includes one or more executable instructions for implementing a given logical function. It should be noted that in some alternative implementations, the functions depicted in the blocks may occur in a different order than depicted in the figures. For example, two successively shown blocks may actually be executed essentially in parallel, depending on the function, and may be executed in the reverse order. It should be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented in a dedicated hardware-based system that performs a given function or operation, or in a combination of dedicated hardware and computer instructions.

[0125] The units described in the embodiments of the present disclosure may be implemented in a software manner or a hardware manner, and the names of the units may not necessarily be used to limit the units themselves, for example, the first acquiring unit may be described as a "unit for acquiring at least two Internet Protocol addresses."

[0126] The functionality described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard parts (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), etc.

[0127] In the context of the present invention, a machine-readable medium may be a tangible medium that can contain or store a program for use in or in connection with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the above. More specific examples of machine-readable storage media include an electrical connection of one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0128] According to one or more embodiments of the present disclosure, [Example 1] is determining at least one process node corresponding to the target placement awaiting project, and determining node attribute information of the at least one process node; determining node dependencies of the at least one process node; The target placement is determined based on the node dependency relationship and the node attribute information. Wait and determining execution project flow information corresponding to the project.

[0129] According to one or more embodiments of the present disclosure, [Example 2] is For example, a method for generating a project flow is provided, further comprising: determining an execution process corresponding to the target awaiting deployment project; and determining at least one process node according to the execution process.

[0130] According to one or more embodiments of the present disclosure, [Example 3] is For example, the process nodes include a master process node and a slave process node; determining at least one master process node according to the executing process; For each master process node, when it is detected that the current master process node has been triggered, adding a slave process node corresponding to the current master process node, and when it is detected that the slave process node has been triggered, setting the slave process node as the current master process node.

[0131] According to one or more embodiments of the present disclosure, [Example 4] is For example, a method for generating a project flow is provided, further including, when it is detected that a process node has been triggered, displaying a node information editing page corresponding to the process node and editing node attribute information of the process node in at least one editable item on the node information editing page.

[0132] According to one or more embodiments of the present disclosure, [Example 5] is For example, determining node dependencies of at least one process node according to a predecessor node indicator in the node attribute information; or The method for generating a project flow further includes determining order information of at least one process node according to an execution process of the target deployment awaiting project, and determining node dependencies of the at least one process node according to the order information.

[0133] According to one or more embodiments of the present disclosure, [Example 6] is For example, the present invention provides a method for generating a project flow, which further includes adjusting a preceding node indicator in the node attribute information according to the node dependency relationship, and updating the node attribute information based on the adjusted preceding node indicator.

[0134] According to one or more embodiments of the present disclosure, [Example 7] is determining an execution order corresponding to at least one process node, for example, based on the node dependency; generating execution project flow information of the target allocation awaiting project according to a node name in node attribute information of at least one process node and the node dependency relationship.

[0135] According to one or more embodiments of the present disclosure, [Example 8] is For example, the method for generating a project flow further includes the node attribute information including at least one of a node indicator, a node name, a node collaborating user, a node authorization information, a node execution time length, a node operation type, a node transition type, a node restriction type, a preceding node indicator, and a node event.

[0136] According to one or more embodiments of the present disclosure, [Example 9] is For example, the present invention provides a method for generating a project flow, further including deleting a current process node and a process node on which the current process node depends if it is detected that a node indicator of the current process node has changed and an upgrade operation has been performed on the current process node.

[0137] According to one or more embodiments of the present disclosure, [Example 10] is For example, if the node restriction type in the node attribute information of the current process node is a first type, when processing of the current process node by a target operation user corresponding to the first type is detected, the method for generating a project flow further includes changing the node state of the current process node.

[0138] According to one or more embodiments of the present disclosure, [Example 11] is For example, if the node restriction type in the node attribute information of the current process node is a second type and the node collaborating users include a collaborating user, the method for generating a project flow further includes updating the node state of the current process node based on a trigger operation of the collaborating user on the current process node.

[0139] According to one or more embodiments of the present disclosure, [Example 12] is For example, if an associated role is set for a current process node, the method for generating a project flow further includes deleting the current process node when deletion of the associated role is detected.

[0140] According to one or more embodiments of the present disclosure, [Example 13] is For example, a method for generating a project flow may be provided, further comprising changing a node state of a current process node after detecting that task completion information corresponding to the current process node has been filled.

[0141] According to one or more embodiments of the present disclosure, [Example 14] is a process node determination module configured to determine at least one process node corresponding to a target placement awaiting project and determine node attribute information of the at least one process node; a node dependency determination module configured to determine node dependencies of the at least one process node; The target placement is determined based on the node dependency relationship and the node attribute information. Wait An apparatus for generating a project flow is provided, further comprising: an execution project flow information determination module configured to determine execution project flow information corresponding to the project.

[0142] Also, although certain operations have been described in a particular order, it should not be understood that these operations must be performed in the particular order shown, or in any forward order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes some specific implementation details, these should not be understood as limiting the scope of the present disclosure. Any features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented in multiple embodiments alone or in any suitable subcombination.

Claims

1. A method for implementing a system comprising: a server determining at least one process node corresponding to a target placement awaiting project; and determining node attribute information of the at least one process node; the server determining node dependencies of the at least one process node; determining, by the server, execution project flow information corresponding to the target awaiting deployment project based on the node dependency relationships and the node attribute information, The node attribute information further includes a node indicator; The method for generating a project flow further includes, in response to detecting that a node indicator of a current process node has changed and that an upgrade operation has been performed on the current process node, the server deleting the current process node and process nodes on which the current process node depends. How to generate a project flow.

2. The step of determining at least one process node corresponding to the target placement-awaiting project includes: The server determines an execution process corresponding to the target project to be deployed, and determines at least one process node according to the execution process. The method of claim 1.

3. The process nodes include a master process node and a slave process node, and determining at least one process node according to the execution process includes: The server determines at least one master process node according to the executing process; the server, for each master process node, in response to detecting that the current master process node has been triggered, adds a slave process node corresponding to the current master process node, and in response to detecting that the slave process node has been triggered, sets the slave process node as the current master process node; The method of claim 2.

4. The step of determining the node attribute information of the at least one process node includes: and in response to detecting that a process node has been triggered, the server displays a node information edit page corresponding to the process node and edits node attribute information of the corresponding process node in at least one editable item of the node information edit page. The method of claim 1.

5. Determining node dependencies of the at least one process node, The server determines node dependencies of the at least one process node according to a predecessor node indicator in the node attribute information; or The server determines order information of the at least one process node according to an execution process of the target deployment awaiting project, and determines node dependency of the at least one process node according to the order information. The method of claim 1.

6. After determining order information of the at least one process node according to an execution process of the target deployment awaiting project and determining node dependency of the at least one process node according to the order information, The method further includes the server adjusting a preceding node indicator in the node attribute information according to the node dependency relationship, and updating the node attribute information based on the adjusted preceding node indicator. The method of claim 5.

7. The step of determining execution project flow information corresponding to the target allocation waiting project based on the node dependency relationship and the node attribute information includes: determining, by the server, an execution order corresponding to the at least one process node based on the node dependency; generating, by the server, execution project flow information of the target allocation awaiting project according to a node name in the node attribute information of the at least one process node and the node dependency relationship; The method of claim 1.

8. The node attribute information further includes at least one of a node name, a node cooperation user, a node authorization information, a node execution time length, a node operation type, a node flow type, a node restriction type, a preceding node indicator, and a node event. The method of claim 1.

9. The method further includes the server determining that the node restriction type in the node attribute information of the current process node is a first type, and changing the node state of the current process node in response to detecting processing of the current process node by a target operation user corresponding to the first type. The method of claim 8.

10. The method further includes the server determining that the node restriction type in the node attribute information of the current process node is a second type and, in response to the node collaborative users including a collaborative user, updating the node state of the current process node based on a trigger operation of the collaborative user on the current process node. The method of claim 8.

11. The method further includes the server setting an associated role for the current process node, and deleting the current process node in response to detecting deletion of the associated role. The method of claim 8.

12. The method further includes: after detecting that the task completion information corresponding to the current process node has been filled, the server changes the node state of the current process node. The method of claim 1.

13. a process node determination module configured to determine at least one process node corresponding to a target awaiting deployment project and to determine node attribute information for the at least one process node; a node dependency determination module configured to determine node dependencies for the at least one process node; an execution project flow information determination module configured to determine execution project flow information corresponding to the target awaiting placement project based on the node dependency relationship and the node attribute information, The node attribute information further includes a node indicator; The project flow generating apparatus further comprises a process node processing module configured to delete the current process node and process nodes on which the current process node depends in response to detecting that a node indicator of the current process node has changed and that an upgrade operation has been performed on the current process node. A device for generating project flows.

14. one or more processors; a storage device configured to store one or more programs; The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method for generating a project flow according to any one of claims 1 to 12. electronic equipment.

15. A storage medium containing computer-executable instructions, The computer-executable instructions, when executed by a processor of a computer, are configured to perform the method for generating a project flow according to any one of claims 1 to 12. storage medium.

Images