CN111598428A

CN111598428A - Method and device for managing process nodes, storage medium and server

Info

Publication number: CN111598428A
Application number: CN202010398787.7A
Authority: CN
Inventors: 周俊; 宋坤
Original assignee: Yuanguang Software Co Ltd
Current assignee: Yuanguang Software Co Ltd
Priority date: 2020-05-12
Filing date: 2020-05-12
Publication date: 2020-08-28
Anticipated expiration: 2040-05-12
Also published as: CN111598428B

Abstract

The embodiment of the application discloses a method and a device for managing a process node, a storage medium and a server. The method comprises the steps of determining a current process node in a target project according to a cooperation request of a user terminal on the target project, executing related operations on one or more target pages related to the current process node, updating the current process node according to a process node switching request of the user terminal after the related operations on the target pages are completed, realizing that a plurality of users simultaneously carry out cooperative design on different pages of the same project, and finally merging all edited pages to obtain a final development result of the project, so that the project development efficiency can be improved.

Description

Method and device for managing process nodes, storage medium and server

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for managing a process node, a storage medium, and a server.

Background

A project designed by a prototype tool developed by a user often has a plurality of pages, and needs many persons to collaborate and complete by demand personnel, UI personnel and developers. The existing prototype design tool cannot meet the requirement that multiple roles or multiple persons design a project at the same time, the development progress of the project is seriously influenced, and the problem of how to improve the efficiency of project development is to be solved urgently at present.

Disclosure of Invention

The embodiment of the application provides a method and a device for managing process nodes, a storage medium and a server, which can realize multi-user collaborative development projects and improve the efficiency of project development. The technical scheme is as follows:

in a first aspect, an embodiment of the present application provides a method for managing a flow node, where the method includes:

receiving a cooperation request aiming at a target project from a user terminal; wherein the collaboration request includes operation type information;

determining a current process node in the target project;

executing relevant operation on the target page associated with the current process node according to the operation type information;

receiving a flow node switching request from the user terminal when the related operation on the target page is completed;

and updating the current process node according to the process node switching request.

In a second aspect, an embodiment of the present application provides a management apparatus for a flow node, where the management apparatus includes:

the system comprises a transceiving unit, a processing unit and a processing unit, wherein the transceiving unit is used for receiving a cooperation request aiming at a target project from a user terminal; wherein the collaboration request includes: operation type information;

the determining unit is used for determining the current process node in the target project;

the execution unit is used for executing related operations on the target page associated with the current process node according to the operation type information;

the receiving and sending unit is further configured to receive a flow node switching request from the user terminal after completing the relevant operation on the target page;

and the updating unit is used for updating the current process node according to the process node switching request.

In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-mentioned method steps.

In a fourth aspect, an embodiment of the present application provides a server, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.

The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:

the method comprises the steps of determining a current process node in a target project according to a cooperation request of a user terminal on the target project, executing related operations on one or more target pages related to the current process node, updating the current process node according to a process node switching request of the user terminal after the related operations on the target pages are completed, realizing that a plurality of users simultaneously carry out cooperative design on different pages of the same project, and finally merging all edited pages to obtain a final development result of the project, so that the project development efficiency can be improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a network structure diagram provided in an embodiment of the present application;

fig. 2 is a schematic flowchart of a method for managing a flow node according to an embodiment of the present application;

FIG. 3 is a schematic diagram of each flow node in a project provided by an embodiment of the present application;

fig. 4 is a schematic structural diagram of a management apparatus for a flow node according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application, as detailed in the appended claims.

In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art. Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

Referring to fig. 1, a network architecture diagram provided for an embodiment of the present application includes a server 10 and a plurality of user terminals, for example: the plurality of user terminals include: user terminal 11, user terminal 12 and user terminal 13, each of which may log on to one or more users, for example: user a logs in to the server 10 through the user terminal 11, user B logs in to the server 10 through the user terminal 12, and user C logs in to the server 10 together with the user terminal 13. The user terminal may communicate with the server 10 wirelessly or by wire, for example: the user terminals communicate with the server 10 via a wireless local area network, a cellular network, an optical fiber, a coaxial line or a network line. The user terminal of the present application includes, but is not limited to, a smart phone, a personal computer, a tablet computer, a handheld device, a vehicle-mounted device, a wearable device, a computing device, or other processing device connected to a wireless modem.

The following describes in detail a method for managing a flow node according to an embodiment of the present application with reference to fig. 2 and fig. 3. The method may be implemented in dependence on a computer program, operable on a management device based on a flow node of the von neumann architecture. The computer program may be integrated into the application or may run as a separate tool-like application.

Please refer to fig. 2, which is a flowchart illustrating a method for managing a flow node according to an embodiment of the present application. As shown in fig. 1, the method of the embodiment of the present application may include the steps of:

s101, receiving a cooperation request aiming at a target project from a user terminal.

The method comprises the steps that a user logs in a server through a user terminal, when the user needs to develop a target project, the user operates the user terminal, then the user terminal sends a cooperation request aiming at the target project to the server, the cooperation request is used for developing the target project, and the cooperation request carries an identifier of the target project; the server receives a cooperation request from the user terminal, wherein the message type of the cooperation request comprises but is not limited to HTTP message, TCP message or UDP message. The type of the target project can be a webpage design project, a program development project, a video editing project or other projects and the like. The target project includes a plurality of process nodes, the plurality of process nodes have a certain execution sequence, and the development of the target project can be completed only after the related operations of the plurality of process nodes are completed, for example: for the webpage design project, the flow nodes included in the webpage design project are as follows: UI design, page layout design, page content design and background code design, wherein the total number of the process nodes is 4, and the execution sequence sequentially comprises the following steps: UI design, page layout design, page content design and background code design. The cooperation request carries identification and operation type information of a target project, the identification of the target project is used for uniquely representing the identity of the target project, the operation type information represents a mode of operating a page associated with the process node and is divided into reading operation and writing operation, and the writing operation can also comprise deleting operation, inserting operation, changing operation and the like.

And S102, determining the current flow node in the target project.

When the target project is not completed, the current process node is an ongoing process node in the target project, and the server records and updates the current process node in the target project. When the target project is started for the first time, the target project is the first process node in the plurality of process nodes.

For example: referring to fig. 3, for item P, item P includes flow node a, flow node b, and flow node c. At a certain time, the target process node in the project P is a process node a; at another time, the target process node in project P is process node b.

S103, executing relevant operation on the target page associated with the current process node according to the operation type information.

The number of the target pages associated with the current flow node may be one or more, and according to the indication of the operation type information, the read operation or the write operation is performed on the one or more target pages.

It should be noted that, at the same time, there may be multiple users performing related operations on the same page, and in order to avoid conflicts among the multiple users, in this embodiment of the present application, the performing related operations on the page associated with the current process node according to the operation type information includes:

when the operation type information is used for executing write operation, inquiring the state of the target page;

when the target page is in a locking state, sending a reading operation notification message to the first user terminal; or

When the target page is in an unlocked state, executing write operation on the target interface;

and after the write operation on the target page is finished, updating the target page to be in a locked state.

The method and the device for processing the page conflict solve the conflict problem by adopting a lock mechanism when a plurality of users perform related operations on the same page at the same time. When a page is cooperatively processed by multiple users, a server records the state of the page, the state of the page is divided into a locked state and an unlocked state, the locked state indicates that a user executing write operation exists in the page, and other users can only execute read operation on the page at the moment. The unlocked state indicates that the page does not have a user who executes the write operation, and at the moment, other users select one user to execute the read operation on the page in a competitive mode.

For example: when the user A enters a page of a project, the locking state of the page is firstly obtained to see whether other users are editing (writing operation) or not, and if the user B is editing, the user A only has the permission to check (writing operation). The server sends a prompt message to the user terminal of the user A to prompt the user B that the user B is editing the page (in addition, the user A can apply for editing authority to the user B, when the user B agrees, the user B is switched to the editing authority, the user A is switched to the editing authority, and the prompt message of the page is modified to be that the user A is editing). If no other user edits the page, the user A has editing authority, modifies the prompt message of the page to be that the user A is editing, and resets the state of the page to be an unlocked state when the user A exits the page.

In this embodiment, the server may store the state of the page by using a redis database, and set the validity period to be X (X > -2) minutes, and the server may update the state of the page every X-1 minutes to ensure the validity of the page state.

Io technology can be adopted in the embodiment, and a user applies for a function of editing (writing) permission. Io is a webSocket library that includes js on the client side and nodejs on the server side, and aims to build real-time applications that can be used on different browsers and mobile devices. The method realizes the automatic selection of the best mode from various modes such as webSocket, AJAX long polling, Iframe stream and the like according to the browser to realize the network real-time communication and chat.

In one possible implementation, the management method further includes: and creating a chat room, and adding the users in the online state associated with the target project into the chat room.

For example: all online users of a target project are added into a chat room, when a user A can send an application message to a user B with an editing right in the chat room, the user B can send a confirmation message to the user A and send a modification request to a server to modify the state of a page in the redis.

And S104, receiving a flow node switching request from the user terminal after the related operation on the target page is completed.

When the write operation of the target interface in the current process node is completed, the user terminal sends a process node switching request to the server for switching the current process node, and the current process node can be switched to be the previous process node or the next process node.

And S105, updating the current process node according to the process node switching request.

In a possible implementation manner, the updating the current process node according to the process node switching request includes:

when the flow node switching request is used for executing a transfer flow and when a next flow node exists in the current flow node, switching the current flow node to the next flow node; or

When the flow node switching request is used for executing a rollback flow and the current flow node is stored in the previous flow node, switching the current flow node to the previous flow node;

further, when the flow node switching request is used to execute an end flow, the state of the target item is updated to the ended state.

When the current process node is not started, the state of the current process node is a non-started state; or

And when any page of the current process node is executing relevant operation, the state of the current process node is an ongoing state.

For example: referring to fig. 3, the project P includes a route flow node a, a flow node b, and a flow node c, and after the creation of the project P is completed, the execution sequence of each flow node, the head node, and each flow node of the project P may be set. The server stores the information of the project P and the respective process nodes as follows:

information of item P: unique identification ID, item name, creator, item status (enabled, ended, disabled).

Flow node information: unique identification ID, process, name, processing role, authority type (editing, viewing), next process node ID, previous process node ID, whether the first process node is present.

Current flow node information: flow node ID, flow state (not started, in progress, finished)

Historical track information of the process: flow node ID, status, handler.

After the user selects to start the process, the server modifies the current process node information (the process node ID is the ID of the first node of the process, and the process state is in progress).

The user selects transfer (that is, when the current flow node a flows to the next flow node b) or rollback flow (that is, when the current flow node a flows to the previous flow node c), if the current flow node a is the first node, the flow can only be transferred, and if the current flow node a does not have the next flow node, the flow can only be ended or the rollback flow can only be rolled back.

And (3) a transfer process: the server modifies the current flow node information (the flow node ID is the ID of the flow node b).

And (3) rollback flow: the server modifies the current flow node information (the flow node ID is the ID of flow node c).

And (4) ending the flow: the server modifies the current process node information (the process state is finished).

The current process information is inquired, the current role is found, users belonging to the current process role are found, the users can inquire the project P, and when the users open the project P. And inquiring the current process authority. If the authority is viewing authority, only the item can be viewed, and if the authority is editing authority, the processing is carried out according to a multi-user cooperative processing mode.

The collaboration request further includes user role information; in one possible embodiment, the method further comprises:

and verifying whether the role associated with the current process node is matched with the role indicated by the user role information.

In one possible embodiment, the method further comprises:

acquiring historical track information of a process, and displaying the historical track information of the process through a display unit; wherein the historical track information of the process comprises: user identification, project status and

the method for managing a flow node of the present application is described below with reference to a specific embodiment,

in the present embodiment, the roles of the user are divided into a demand role, a UI role, and a development role. The flow nodes are simply referred to as flows.

The users in the demand role are u1 and u 2; users in the UI role u3, u 4; users in the development role u5, u 6; the project P comprises 3 process nodes including a requirement process a1, a UI process a2 and a development process a3, wherein the 3 process nodes are respectively associated with 3 pages: page1, page2, page 3. The development process for project P is as follows:

step a, a user u1 creates a project P, and 3 pages 1, 2 and 3 correspond to the project P; at initialization, the three page states are all empty.

Step b, setting flow information by a user u 1: ID, Liucheng; name: example flow; the creator: u 1; the state is as follows: and (4) starting. Project P has three process nodes:

a requirement flow a1, a UI flow a2, and a development flow a 3. Wherein, the requirement flow a 1; ID: a1 procedure ID: ligation; name: a demand; and (4) processing roles: a demand person; the permission types are as follows: editing; the next node: a 2; the last node is 'none'; and if the node is the first node, the node is yes.

UI flow a 2: ID a 2; the process ID is Liuche; name: a UI; and (4) processing roles: a UI person; the permission types are as follows: editing; the next node: a 3; the previous node a 1; and if the node is the first node, judging whether the node is the first node.

Development flow a 3: ID a 3; the process ID is Liuche; name: development; and (4) processing roles: a developer; the permission types are as follows: editing; the next node: "none"; the previous node a 2; and if the node is the first node, judging whether the node is the first node. Initializing the node information of the current process: flow node ID: "; the flow state is as follows: is not started

Step c, starting the process by the user u1, and setting the node information of the process: flow node ID: a 1; the flow state is as follows: carrying out the following steps; historical track information of the process: [ { a1, u1, in progress } ].

And d, at the moment, only the users u1 and u2 can enter the project, when the user u1 opens the project to enter the page1, the server inquires that the state of the page1 is empty, the user u1 can edit the page, and at the moment, the server updates the state of the page1 to be the page1: u 1.

And e, when u2 enters a page1 of the project, the server inquires that the state of the page1 is u1, judges that u2 only has viewing permission, u2 clicks the editing permission of applying the page1, u1 becomes the viewing permission after u1 clicks the consent, u2 becomes the editing permission, and the server updates the state of the page1 to be page1: u 2.

And step f, when u2 leaves the page1, the server updates the state of the page1 to be page 1:'.

Step g, u1 transmits the flow to a2, and the information of the flow node is set as follows: flow node ID: a 2; the flow state is as follows: carrying out the following steps; historical track information of the process: [ { a1, u1, in progress }, { a2, u2, in progress } ]; at this time, u1, u2, u3 and u4 can all see items, u1 and u2 only have viewing authority, u3 and u4 authority is judged according to the page state, and the steps are repeated from d to f.

Step h, u3 returns the process to a1, and the process node information is set as follows: flow node ID: a 1; the flow state is as follows: carrying out the following steps; historical track information of the process: [ { a1, u1, in progress }, { a2, u2, in progress }, { a1, u1, in progress } ]; at this time, u1 and u2 can see items, the authority of u1 and u2 is judged according to the page state, and the steps are repeated from d to f.

In the step i, u1 transmits the flow to a2, and the information of the flow node is set as follows: flow node ID: a 2; the flow state is as follows: carrying out the following steps; historical track information of the process: [ { a1, u1, in progress }, { a2, u2, in progress }, { a1, u1, in progress }, { a2, u2, in progress } ]. u2 transmits the flow to a3, sets the flow node information: flow node ID: a 3; the flow state is as follows: carrying out the following steps; historical track information of the process: { a1, u1, in progress }, { a2, u2, in progress }, { a1, u1, in progress }, { a2, u2, in progress }, and { a3, u3, in progress } ]. At the moment, u1, u2, u3, u4, u5 and u6 can all see items, u1, u2, u3 and u4 only have viewing authority, the authority of u5 and u6 is judged according to the page state, and the steps are repeated from d to f.

Step j, the user u5 ends the process, and the server sets the process node information: flow node ID: a 3; the flow state is as follows: the process is finished; historical track information of the process: { a1, u1, in progress }, { a2, u2, in progress }, { a1, u1, in progress }, { a2, u2, in progress }, { a3, u3, in progress }, { a3, u3, finished } ].

According to the embodiment of the application, in a multi-role collaborative scene, a requirement can be created in a prototype design tool, one or more requirement pages are designed in a canvas, then the requirement pages can be transferred to UI personnel through a flow system, the UI personnel generate a to-be-handled condition, the UI personnel check UI specifications and beautify the pages, then the UI personnel transfer the UI specifications to developers and generate the to-be-handled condition, the developers can obtain real pages after exporting the codes (js, css and html) and other settings (setting page element IDs and the like) of the pages. And the communication cost under the multi-role line is reduced by smoothly circulating and informing the backlog.

In the multi-user collaboration of the same role, a plurality of demand (UI, development) personnel can simultaneously log in an original design tool and design the same project, and for each page of the project, only the first user entering the page editing has editing permission, and other users only have viewing permission. Only the user B with the viewing authority can initiate an editing authority application to the user A with the editing authority, after the user A passes the application, the user B is used for editing authority, and the user A becomes the viewing authority. When a user with the editing right leaves the page, other personnel can switch to the page or refresh the page to acquire the editing right of the page. And multiple users can be supported to simultaneously carry out collaborative design on different pages of the same project. Each user can work in a cooperative mode and automatically combine results, and project development efficiency is greatly improved.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 4, a schematic structural diagram of a management apparatus of a flow node according to an exemplary embodiment of the present application is shown. The management means may be implemented as all or part of the server in software, hardware or a combination of both. The management device 4 includes: a transceiving unit 40, a determining unit 41, an executing unit 42 and an updating unit 43.

A transceiving unit 40 for receiving a cooperation request for a target project from a user terminal; wherein the collaboration request includes: operation type information and identification of the target item;

a determining unit 41, configured to determine a current flow node in the target project;

an executing unit 42, configured to execute a relevant operation on the target page associated with the current process node according to the operation type information;

the transceiving unit 40 is further configured to receive a flow node switching request from the user terminal after completing the relevant operation on the target page;

an updating unit 43, configured to update the current process node according to the process node switching request.

and updating the state of the target item to be the finished state when the flow node switching request is used for executing the finished flow.

In a possible implementation manner, when the current process node is not started, the state of the current process node is a non-started state; or

In a possible implementation manner, the performing, according to the operation type information, a related operation on a page associated with the current flow node includes:

In a possible embodiment, the management device 4 further comprises:

and the communication unit is used for creating a chat room and adding the users in the online state associated with the target project into the chat room.

In one possible embodiment, the collaboration request further includes user role information;

the management apparatus 4 further includes:

and the verification unit is used for verifying whether the role associated with the current process node is matched with the role indicated by the user role information.

In one possible embodiment, the method further comprises:

the acquisition unit is used for acquiring historical track information of the process and displaying the historical track information of the process through the display unit; wherein the historical track information of the process comprises: user identification, project status and process node identification

It should be noted that, when the management apparatus for a flow node provided in the foregoing embodiment executes the management method for a flow node, the division of each functional module is merely used as an example, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules, so as to complete all or part of the functions described above. In addition, the management apparatus for a process node and the management method for a process node provided in the foregoing embodiments belong to the same concept, and details of implementation processes thereof are referred to in the method embodiments and are not described herein again.

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

An embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are suitable for being loaded by a processor and executing the method steps in the embodiment shown in fig. 2, and a specific execution process may refer to a specific description of the embodiment shown in fig. 2, which is not described herein again.

Please refer to fig. 5, which provides a schematic structural diagram of a server according to an embodiment of the present application. As shown in fig. 5, the server 1000 may include: at least one processor 1001, at least one network interface 1004, a user interface 1003, memory 1005, at least one communication bus 1002.

Wherein a communication bus 1002 is used to enable connective communication between these components.

The user interface 1003 may include a Display screen (Display), a physical keyboard, and a touch screen, and the optional user interface 1003 may also include a standard wired interface and a wireless interface.

The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.

Processor 1001 may include one or more processing cores, among other things. The processor 1001, which is connected to various parts throughout the server 1000 using various interfaces and lines, performs various functions of the server 1000 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 1005 and calling data stored in the memory 1005. Alternatively, the processor 1001 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 1001 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 1001, but may be implemented by a single chip.

The Memory 1005 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 1005 includes a non-transitory computer-readable medium. The memory 1005 may be used to store an instruction, a program, code, a set of codes, or a set of instructions. The memory 1005 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 1005 may optionally be at least one memory device located remotely from the processor 1001. As shown in fig. 5, the memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and an identification application program.

In the server 1000 shown in fig. 5, the user interface 1003 is mainly used as an interface for providing input for a user, and acquiring data input by the user; the processor 1001 may be configured to invoke an application program of the management method of the flow node stored in the memory 1005, and specifically execute the management method of the flow node shown in fig. 2, where specific principles and processes are shown in the method embodiment shown in fig. 2, and are not described herein again.

In the embodiment of the application, the current process node in the target project is determined according to the cooperation request of the user terminal on the target project, the related operation is executed on one or more target pages related to the current process node, after the related operation on the target pages is completed, the current process node is updated according to the process node switching request of the user terminal, a plurality of users can simultaneously carry out collaborative design on different pages of the same project, finally, all edited pages are combined to obtain the final development result of the project, and the project development efficiency can be improved.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory or a random access memory.

The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.

Claims

1. A method for managing a process node, the method comprising:

receiving a cooperation request aiming at a target project from a user terminal; wherein the collaboration request includes: operation type information and identification of the target item;

determining a current process node in the target project;

after the relevant operation on the target page is completed, receiving a flow node switching request from the user terminal;

2. The method for managing according to claim 1, wherein the updating the current flow node according to the flow node switching request includes:

3. The management method according to claim 2,

4. The method for managing according to claim 1, wherein the performing related operations on the page associated with the current process node according to the operation type information includes:

5. The method of managing according to claim 4, further comprising:

and creating a chat room, and adding the users in the online state associated with the target project into the chat room.

6. The method of claim 1, wherein the collaboration request further includes user role information;

the method further comprises the following steps:

7. The management method according to claim 1, further comprising:

acquiring historical track information of a process, and displaying the historical track information of the process through a display unit; wherein the historical track information of the process comprises: user identification, project status and process node identification.

8. A management apparatus for a process node, the management apparatus comprising:

the system comprises a transceiving unit, a processing unit and a processing unit, wherein the transceiving unit is used for receiving a cooperation request aiming at a target project from a user terminal; wherein the collaboration request includes: operation type information and identification of the target item;

9. A computer storage medium, characterized in that it stores a plurality of instructions adapted to be loaded by a processor and to carry out the method steps according to any one of claims 1 to 7.

10. A terminal, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1 to 7.