CN111598428B - Management method and device of flow node, storage medium and server - Google Patents
Management method and device of flow node, storage medium and server Download PDFInfo
- Publication number
- CN111598428B CN111598428B CN202010398787.7A CN202010398787A CN111598428B CN 111598428 B CN111598428 B CN 111598428B CN 202010398787 A CN202010398787 A CN 202010398787A CN 111598428 B CN111598428 B CN 111598428B
- Authority
- CN
- China
- Prior art keywords
- flow node
- flow
- node
- current flow
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063118—Staff planning in a project environment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Game Theory and Decision Science (AREA)
- Operations Research (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application discloses a method and a device for managing flow nodes, a storage medium and a server. Determining a current flow node in a target project according to a collaboration request of a user terminal to the target project, executing related operations on one or more target pages related to the current flow node, updating the current flow node according to a flow 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 collaborative 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
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for managing a flow node, a storage medium, and a server.
Background
Users develop a project of prototype tool design, often have many pages, and require multiple people to finish the collaboration of the required personnel, UI personnel and developers. The existing prototype design tool cannot meet the requirement that multiple roles or multiple people design a project at the same time, the development progress of the project is seriously influenced, and how to improve the development efficiency of the project is a problem to be solved urgently at present.
Disclosure of Invention
The embodiment of the application provides a method, a device, a storage medium and a server for managing flow nodes, which can realize multi-user collaborative development project 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 collaboration request for a target item from a user terminal; wherein the collaboration request includes operation type information;
determining a current flow node in the target item;
performing related operations on the target page associated with the current flow 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 flow node according to the flow 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 receiving and transmitting unit is used for receiving a collaboration request for a target item from the user terminal; wherein the collaboration request includes: operation type information;
a determining unit, configured to determine a current flow node in the target item;
the execution unit is used for executing related operations on the target pages associated with the current flow nodes according to the operation type information;
the receiving and transmitting unit is further configured to receive a flow node switching request from the user terminal after completing the related operation on the target page;
and the updating unit is used for updating the current flow node according to the flow 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-described 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 technical scheme provided by the embodiments of the application has the beneficial effects that at least:
determining a current flow node in a target project according to a collaboration request of a user terminal to the target project, executing related operations on one or more target pages related to the current flow node, updating the current flow node according to a flow 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 collaborative 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 application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a network block diagram provided by an embodiment of the present application;
fig. 2 is a flow chart of a method for managing a flow node according to an embodiment of the present application;
FIG. 3 is a schematic diagram of each process node in an item provided by an embodiment of the present application;
fig. 4 is a schematic structural diagram of a management device for a process 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 apparent, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings.
When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application as detailed in the accompanying claims.
In the description of the present application, it should 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 will be understood in specific cases by those of ordinary skill in the art. Furthermore, in the description of the present application, unless otherwise indicated, "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
Referring to fig. 1, a network architecture diagram provided in an embodiment of the present application includes a server 10 and a plurality of user terminals, for example: the plurality of user terminals includes: user terminal 11, user terminal 12 and user terminal 13, each of which may log in to one or more users, for example: user a logs into the server 10 via user terminal 11, user B logs into the server 10 via user terminal 12, and user C logs into the server 10 with user terminal 13. The user terminal may communicate with the server 10 wirelessly or by wire, for example: the user terminal communicates with the server 10 via a wireless local area network, a cellular network, an optical fiber, a coaxial line or a network cable. 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, etc.
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, and may be run on a management device based on a flow node of the von neumann system. The computer program may be integrated in the application or may run as a stand-alone tool class application.
Fig. 2 is a flow chart of a method for managing a flow node according to an embodiment of the present application. As shown in fig. 1, the method according to the embodiment of the present application may include the following steps:
s101, receiving a collaboration request for a target item 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, and then the user terminal sends a collaboration request aiming at the target project to the server, wherein the collaboration request is used for developing the target project, and the collaboration request carries an identification of the target project; the server receives a collaboration request from the user terminal, the message type of the collaboration request including, but not limited to, an HTTP message, a TCP message, or a UDP message. The type of the target item can be a webpage design item, a time program development item, a video editing item or other items, and the like. The target project includes a plurality of process nodes, the plurality of process nodes have a certain execution sequence, and development of the target project can be completed after related operations of the plurality of process nodes are completed, for example: for a web page design project, the web page design project includes the following flow nodes: UI design, page layout design, page content design and background code design, 4 flow nodes are all executed in sequence: UI design, page layout design, page content design, and background code design. The collaboration request carries the identification of the target item and operation type information, wherein the identification of the target item is used for uniquely representing the identity of the target item, the operation type information represents a mode of operating a page associated with the flow node, and the operation is divided into a read operation and a write operation, and the write operation can also comprise a delete operation, an insert operation, a change operation and the like.
S102, determining a current flow node in the target item.
The target item comprises a plurality of flow nodes, when the target item is not finished, the current flow node is an ongoing flow node in the target item, and the server records and updates the current flow node in the target item. When the target item is started for the first time, the target item is the first flow node in the plurality of flow nodes.
For example: referring to fig. 3, for item P, item P includes a flow node a, a flow node b, and a flow node c. At a certain time, the target flow node in the project P is a flow node a; at another time, the target flow node in item P is flow node b.
S103, executing related operations on the target pages associated with the current flow nodes according to the operation type information.
The number of the target pages associated with the current flow node can be one or more, and according to the indication of the operation type information, a read operation or a write operation is performed on the one or more target pages.
It should be noted that, in order to avoid a conflict between multiple users, in the embodiment of the present application, the performing, according to the operation type information, a related operation on a page associated with the current flow node may include:
inquiring the state of the target page when the operation type information is used for executing writing operation;
when the target page is in a locking state, sending a read operation notification message to the first user terminal; or (b)
When the target page is in an unlocked state, executing writing operation on the target interface;
and after the writing operation of the target page is completed, updating the target page into a locking state.
The embodiment of the application solves the conflict problem by adopting a lock mechanism when a plurality of users simultaneously perform related operations on the same page. When the multi-user co-processes the page, the server records the state of the page, wherein the state of the page is divided into a locking state and an unlocking state, the locking state indicates that the page has a user for executing writing operation, and other users can only execute reading operation on the page. The unlocked state indicates that the page does not have a user performing a write operation, at which time other users select one of the users to perform a read operation on the page in a competing manner.
For example: when the user A enters a page of an item, the locking state of the page is obtained first to see whether other users edit (write operation), and if the user B edits, the user A only has viewing (write operation) authority. The server sends a prompt message to the user terminal of user a to prompt B that the user is editing the page (in addition, user a may apply for editing rights to user B, and when user B agrees, user B switches to viewing rights, user a switches to editing rights, and modifies the prompt message of the page to be edited by user a). If no other user is editing the page, the user A has editing authority, and modifies the prompting message of the page to be edited by the user A, and when the user A exits the page, the state of the page is reset to be an unlocked state.
In this embodiment, the server may use the redis database to store the state of the page, 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, so as to ensure the validity of the page state.
The embodiment may be implemented by using a socket technology, where a user applies for a function of editing (writing operation) rights. socket.io is a webSocket library comprising js at the client and nodejs at the server, the goal of which is to build real-time applications that can be used on different browsers and mobile devices. The implementation automatically selects the best mode from various modes of webSocket, AJAX long polling, iframe streaming and the like according to the browser to realize network real-time communication and chat.
In one possible implementation, the management method further includes: creating a chat room, and adding the users associated with the target items in an online state into the chat room.
For example: all online users of a target item are added into a chat room, when a user A can send an application message to a user B with editing authority 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 redis internal page.
S104, after the related operation on the target page is completed, receiving a flow node switching request from the user terminal.
When the writing operation of the target interface in the current flow node is completed, the user terminal sends a flow node switching request to the server, and the request is used for switching the current flow node, so that the current flow node can be switched to the previous flow node or the next flow node.
S105, updating the current flow node according to the flow node switching request.
In one possible implementation manner, the updating the current flow node according to the flow node switching request includes:
when the flow node switching request is used for executing a transfer flow, and when the current flow node exists a next flow node, switching the current flow node to the next flow node; or (b)
When the flow node switching request is used for executing a rollback flow and the current flow node has a previous node, switching the current flow node to the previous flow node;
further, when the flow node switching request is used for executing the ending flow, the state of the target item is updated to an ended state.
When the current flow node is not started, the state of the current flow node is a non-starting state; or (b)
And when any page of the current flow node is executing related operation, the state of the current flow node is an in-process state.
For example: referring to fig. 3, the item P includes a path flow node a, a flow node b, and a flow node c, and after the creation of the item P is completed, the execution order of each flow node, a head node, and each flow node of the item P may be set. The server stores the information of item P and the respective flow nodes as follows:
information of item P: unique identification ID, item name, creator, item status (enabled, ended, discarded).
Flow node information: unique identification ID, flow, name, processing role, rights type (edit, view), next flow node ID, last flow node ID, whether it is the first flow node.
Current flow node information: flow node ID, flow state (unactuated state, in-progress state, ended state)
Flow history trace information: flow node ID, status, handler.
After the user selects to start the flow, the server modifies the current flow node information (the flow node ID is the ID of the flow head node, and the flow state is in progress).
The user selects to transfer (i.e., when the current flow node a flows to the next flow node b) or rollback (i.e., when the current flow node a flows to the previous node c), if the current flow node a is the first node, only the flow can be transferred, and if a is not the next flow node, only the flow or rollback flow can be ended.
The transmission flow is as follows: the server modifies the current flow node information (flow node ID is the ID of flow node b).
The rollback flow is as follows: the server modifies the current flow node information (flow node ID is the ID of flow node c).
Ending the flow: the server modifies the current flow node information (flow state is finished).
The method comprises the steps of inquiring current flow information, finding out a current role, and finding out users belonging to the current flow role, wherein the users can inquire about a project P, and after the users open the project P. Inquiring the current flow authority. If the user is authorized to view, only the project can be viewed, and if the user is authorized to edit, the project is processed in a multi-user collaborative processing mode.
The collaboration request also includes user role information; in one possible embodiment, the method further comprises:
and verifying whether the role associated with the current flow node is matched with the role indicated by the user role information.
In one possible embodiment, the method further comprises:
acquiring flow history track information and displaying the flow history track information through a display unit; wherein the flow history track information includes: user identification, project status and process node ID;
the method of managing a flow node of the present application is described below with respect to a specific embodiment,
in the present embodiment, the roles of the users are classified into a demand role, a UI role, and a development role. The flow nodes are simply referred to as flows.
The users under the demand roles are u1 and u2; u3 and u4 are users under the UI role; u5 and u6 are users under the development roles; project P includes a demand flow a1, a UI flow a2, and a development flow a3, for a total of 3 flow nodes, each of the 3 flow nodes being associated with 3 pages: page1, page2, page3. The development process of project P is as follows:
step a, a user u1 creates a project P, and 3 pages 1, 2 and 3 are corresponding 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: an example flow; the creator: u1; status: and enabling. Item P has three flow nodes:
a demand flow a1, a UI flow a2, and a development flow a3. Wherein, the demand flow a1; ID: a1 procedure ID: liucheng; name: a demand; processing roles: a demand person; rights type: editing; the next node: a2; the last node is 'none'; and judging whether the node is the first node or not, and judging whether the node is the first node or not.
UI flow a2: ID: a2; flow ID, liucheng; name: a UI; processing roles: UI personnel; rights type: editing; the next node: a3; a1 is the last node; and judging whether the node is the first node or not.
Development flow a3: ID: a3; flow ID, liucheng; name: development; processing roles: a developer; rights type: editing; the next node: "none"; a2, the previous node; and judging whether the node is the first node or not. Initializing current flow node information: flow node ID: ""; the flow state is as follows: not activated.
Step c, a user u1 starts a process and sets process node information: flow node ID: a1; the flow state is as follows: in progress; flow history trace information: [ { a1, u1, go medium } ].
In the step d, only users u1 and u2 can enter the project, when the user u1 opens the project and enters 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 page1:u1.
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 the viewing authority, u2 clicks the editing authority of the page1, u1 becomes the viewing authority after u1 clicks agreements, u2 becomes the editing authority, and the server updates the state of the page1 to be page1:u2.
And f, when u2 leaves page1, updating the state of page1 to be page1: ", by the server.
Step g, u1 transmits the flow to a2, and sets the flow node information: flow node ID: a2; the flow state is as follows: in progress; flow history trace information: [ { a1, u1, go medium }, { a2, u2, go medium } ]; at this time, items can be seen by u1, u2, u3 and u4, only viewing rights of u1 and u2 are judged according to page states, and steps d to f are repeated.
Step h, u3 returns the flow to a1, and sets flow node information: flow node ID: a1; the flow state is as follows: in progress; flow history trace information: [ { a1, u1, go medium }, { a2, u2, go medium }, { a1, u1, go medium } ]; at this time, u1 and u2 can see the item, the authority of u1 and u2 is judged according to the page state, and the steps d to f are repeated.
Step i, u1 transmits the flow to a2, and sets flow node information: flow node ID: a2; the flow state is as follows: in progress; flow history trace information: [ { a1, u1, go medium }, { a2, u2, go medium }, { a1, u1, go medium }, { a2, u2, go medium } ]. u2, transmitting the flow to a3, and setting flow node information: flow node ID: a3; the flow state is as follows: in progress; flow history trace information: [ { a1, u1, in progress }, { a2, u2, in progress }, { a3, u3, in progress } ]. At this time, items can be seen by u1, u2, u3, u4, u5 and u6, only viewing rights of u1, u2, u3 and u4 are seen at this time, rights of u5 and u6 are judged according to page states, and steps d to f are repeated.
Step j, user u5 ends the process, and the server sets process node information: flow node ID: a3; the flow state is as follows: has ended; flow history trace information: [ { a1, u1, go medium }, { a2, u2, go medium }, { a3, u3, end } ].
According to the embodiment of the application, in a scene of multi-role collaboration, a requirement can create a project in a prototype design tool, one or more requirement pages are designed in canvas, then the requirement pages can be transferred to UI personnel through a flow system, a to-be-handled task is generated, the UI personnel check UI specifications and beautify the pages, the UI personnel transfer to a developer, the to-be-handled task is generated, and the developer can obtain a real page after exporting the pages, namely codes (js, css, html) and other settings (setting page element IDs and the like). And the communication cost under the multi-role line is reduced by smooth circulation and in a to-do notification mode.
In multi-user collaboration of the same role, multiple requirements (UI, development) personnel can log in a prototype design tool at the same time to design the same project, and for each page of the project, only the first user who enters page editing has editing permission, and other users 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, and after the user A passes through, the user B is used for editing authority, and the 'A' becomes the viewing authority. When the user with the editing authority leaves the page, other personnel can switch to the page or refresh the page to acquire the editing authority of the page. Multiple users can be supported to co-design different pages of the same item at the same time. And each user can work separately and automatically combine the results, so that the project development efficiency is greatly improved.
The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.
Referring to fig. 4, a schematic structural diagram of a management apparatus for 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 by 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 collaboration request for a target item from a user terminal; wherein the collaboration request includes: operation type information and identification of a target item;
a determining unit 41, configured to determine a current flow node in the target item;
an execution unit 42, configured to execute a related operation on a target page associated with the current flow node according to the operation type information;
the transceiver unit 40 is further configured to receive a flow node switching request from the user terminal after completing the related operation on the target page;
an updating unit 43, configured to update the current flow node according to the flow node switching request.
In one possible implementation manner, the updating the current flow node according to the flow node switching request includes:
when the flow node switching request is used for executing a transfer flow, and when the current flow node exists a next flow node, switching the current flow node to the next flow node; or (b)
When the flow node switching request is used for executing a rollback flow and the current flow node has a previous node, switching the current flow node to the previous flow node;
and updating the state of the target item to an ended state when the flow node switching request is used for executing the ending flow.
In a possible implementation manner, when the current flow node is not started, the state of the current flow node is a non-started state; or (b)
And when any page of the current flow node is executing related operation, the state of the current flow node is an in-process state.
In a possible implementation manner, the performing, according to the operation type information, a related operation on the page associated with the current flow node includes:
inquiring the state of the target page when the operation type information is used for executing writing operation;
when the target page is in a locking state, sending a read operation notification message to the first user terminal; or (b)
When the target page is in an unlocked state, executing writing operation on the target interface;
and after the writing operation of the target page is completed, updating the target page into a locking state.
In one 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 item into the chat room.
In a possible implementation manner, the collaboration request further comprises user role information;
the management device 4 further includes:
and the verification unit is used for verifying whether the roles associated with the current flow node are matched with the roles indicated by the user role information.
In one possible embodiment, the method further comprises:
the acquisition unit is used for acquiring the flow history track information and displaying the flow history track information through the display unit; wherein the flow history track information includes: 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 performs the management method for a flow node, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the management device of the flow node and the management method embodiment of the flow node provided in the foregoing embodiments belong to the same concept, which embody the detailed implementation process and are not described herein again.
The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
The 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 adapted to be loaded by a processor and execute the steps of the method shown in the embodiment of fig. 2, and the specific execution process may refer to the specific description of the embodiment shown in fig. 2, which is not repeated herein.
Referring to fig. 5, a schematic structural diagram of a server is provided in 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, a memory 1005, at least one communication bus 1002.
Wherein the communication bus 1002 is used to enable connected communication between these components.
The user interface 1003 may include a Display (Display), a physical keyboard, a touch screen, among others, and the optional user interface 1003 may also include a standard wired interface, a wireless interface.
The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
Wherein the processor 1001 may include one or more processing cores. The processor 1001 connects various parts within the entire 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 (Digital Signal Processing, DSP), field-Programmable gate array (FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 1001 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), and a modem, etc. 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 will be appreciated that the modem may not be integrated into the processor 1001 and may be implemented by a single chip.
The Memory 1005 may include a random access Memory (RandomAccess Memory, RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 1005 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). The memory 1005 may be used to store instructions, programs, code, sets of codes, or sets 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 above-described respective method embodiments, etc.; the storage data area may store data or the like referred to in the above respective method embodiments. The memory 1005 may also optionally be at least one storage device located remotely from the processor 1001. As shown in fig. 5, an operating system, a network communication module, a user interface module, and an identification application may be included in the memory 1005, which is one type of computer storage medium.
In the server 1000 shown in fig. 5, the user interface 1003 is mainly used for providing an input interface 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, and specific principles and processes and embodiments of the method referring to fig. 2 are not described herein.
In the embodiment of the application, the current flow node in the target project is determined according to the collaboration request of the user terminal to the target project, the related operation is executed on one or more target pages related to the current flow node, after the related operation on the target pages is completed, the current flow node is updated according to the flow node switching request of the user terminal, so that a plurality of users can simultaneously carry out collaborative design on different pages of the same project, and finally, the edited pages are combined to obtain the final development result of the project, thereby improving the project development efficiency.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory, a random access memory, or the like.
The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.
Claims (10)
1. A method for managing a process node, the method comprising:
receiving a collaboration request for a target item from a user terminal; wherein the collaboration request includes: operation type information and identification of a target item, wherein the target item is a webpage design item, and the webpage design item comprises 4 flow nodes: UI design, page layout design, page content design, and background code design;
determining a current flow node in the target item; the server stores the information of the target item, the information of each flow node, the current flow node information and the flow history track information; the information of the target item includes: unique identification ID, project name, creator, project status; the flow node information includes: unique identification ID, flow, name, processing role, authority type, next flow node ID, last flow node ID, whether it is the first flow node; the current flow node information includes: a flow node ID, a flow state; the flow history track information includes: flow node ID, status, handler;
performing related operations on the target page associated with the current flow node according to the operation type information;
after the related operation on the target page is completed, receiving a flow node switching request from the user terminal;
and updating the current flow node according to the flow node switching request.
2. The method according to claim 1, wherein updating the current flow node according to a flow node switching request comprises:
when the flow node switching request is used for executing a transfer flow, and when the current flow node exists a next flow node, switching the current flow node to the next flow node; or (b)
When the flow node switching request is used for executing a rollback flow and the current flow node has a previous node, switching the current flow node to the previous flow node;
and updating the state of the target item to an ended state when the flow node switching request is used for executing the ending flow.
3. The method of claim 2, wherein,
when the current flow node is not started, the state of the current flow node is a non-starting state; or (b)
And when any page of the current flow node is executing related operation, the state of the current flow node is an in-process state.
4. The method according to claim 1, wherein the performing a related operation on the page associated with the current flow node according to the operation type information includes:
inquiring the state of the target page when the operation type information is used for executing writing operation;
when the target page is in a locking state, sending a read operation notification message to the user terminal; or (b)
When the target page is in an unlocked state, executing writing operation on the target interface;
and after the writing operation of the target page is completed, updating the target page into a locking state.
5. The method of managing as set forth in claim 4, further comprising:
creating a chat room, and adding the users associated with the target items in an online state into the chat room.
6. The method of managing according to claim 1, characterized in that the collaboration request further includes user role information;
the method further comprises the steps of:
and verifying whether the role associated with the current flow node is matched with the role indicated by the user role information.
7. The method of managing as set forth in claim 1, further comprising:
and acquiring the flow history track information and displaying the flow history track information through a display unit.
8. A management device for a flow node, the management device comprising:
the receiving and transmitting unit is used for receiving a collaboration request for a target item from the user terminal; wherein the collaboration request includes: operation type information and identification of a target item, wherein the target item is a webpage design item, and the webpage design item comprises 4 flow nodes: UI design, page layout design, page content design, and background code design;
a determining unit, configured to determine a current flow node in the target item; the server stores the information of the target item, the information of each flow node, the current flow node information and the flow history track information; the information of the target item includes: unique identification ID, project name, creator, project status; the flow node information includes: unique identification ID, flow, name, processing role, authority type, next flow node ID, last flow node ID, whether it is the first flow node; the current flow node information includes: a flow node ID, a flow state; the flow history track information includes: flow node ID, status, handler;
the execution unit is used for executing related operations on the target pages associated with the current flow nodes according to the operation type information;
the receiving and transmitting unit is further configured to receive a flow node switching request from the user terminal after completing the related operation on the target page;
and the updating unit is used for updating the current flow node according to the flow node switching request.
9. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the method steps of 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-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010398787.7A CN111598428B (en) | 2020-05-12 | 2020-05-12 | Management method and device of flow node, storage medium and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010398787.7A CN111598428B (en) | 2020-05-12 | 2020-05-12 | Management method and device of flow node, storage medium and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111598428A CN111598428A (en) | 2020-08-28 |
| CN111598428B true CN111598428B (en) | 2023-10-17 |
Family
ID=72185273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010398787.7A Active CN111598428B (en) | 2020-05-12 | 2020-05-12 | Management method and device of flow node, storage medium and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111598428B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112950138B (en) * | 2020-09-11 | 2024-03-12 | 深圳市明源云科技有限公司 | Collaborative development state management method, device and server |
| CN115526579A (en) * | 2021-11-26 | 2022-12-27 | 北京字跳网络技术有限公司 | Method and device for determining item flow, electronic equipment and storage medium |
| CN114596077B (en) * | 2022-03-25 | 2023-04-18 | 诺正集团股份有限公司 | Full-flow visual management method, device, equipment and medium for patent cases |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103077453A (en) * | 2012-12-31 | 2013-05-01 | 南京烽火星空通信发展有限公司 | Method and system for analyzing data by multiple-people cooperative work |
| CN106569797A (en) * | 2016-10-11 | 2017-04-19 | 东软集团股份有限公司 | Method, device and system for collaboratively drawing process by multiple persons |
| CN108683694A (en) * | 2018-03-22 | 2018-10-19 | 厦门欣旅通科技有限公司 | A kind of information synergism processing method, system and server |
| CN110120968A (en) * | 2019-04-02 | 2019-08-13 | 北京大麦地信息技术有限公司 | A kind of method, apparatus, electronic equipment and the server of online collaborative process file |
| CN110610406A (en) * | 2019-09-20 | 2019-12-24 | 上海同在互联网科技有限公司 | Business process configuration method and device, computer equipment and storage medium |
| CN111080270A (en) * | 2019-12-31 | 2020-04-28 | 杨剑峰 | Collaborative system application design method, system, device, server and storage medium |
-
2020
- 2020-05-12 CN CN202010398787.7A patent/CN111598428B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103077453A (en) * | 2012-12-31 | 2013-05-01 | 南京烽火星空通信发展有限公司 | Method and system for analyzing data by multiple-people cooperative work |
| CN106569797A (en) * | 2016-10-11 | 2017-04-19 | 东软集团股份有限公司 | Method, device and system for collaboratively drawing process by multiple persons |
| CN108683694A (en) * | 2018-03-22 | 2018-10-19 | 厦门欣旅通科技有限公司 | A kind of information synergism processing method, system and server |
| CN110120968A (en) * | 2019-04-02 | 2019-08-13 | 北京大麦地信息技术有限公司 | A kind of method, apparatus, electronic equipment and the server of online collaborative process file |
| CN110610406A (en) * | 2019-09-20 | 2019-12-24 | 上海同在互联网科技有限公司 | Business process configuration method and device, computer equipment and storage medium |
| CN111080270A (en) * | 2019-12-31 | 2020-04-28 | 杨剑峰 | Collaborative system application design method, system, device, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111598428A (en) | 2020-08-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111598428B (en) | Management method and device of flow node, storage medium and server | |
| CN102187314B (en) | Interactive design environments to visually model, debug and execute resource oriented programs | |
| JPWO2009116163A1 (en) | Application development support apparatus, program, and recording medium | |
| CN111580820A (en) | Applet generation method and device | |
| JP2009176269A (en) | Event management system, event management method, and event management program | |
| Ma et al. | Modularized and Flow-Based Approach to Chatbot Design and Deployment. | |
| CN116136758A (en) | Page generation method, device, equipment and medium | |
| CN111367561B (en) | Remote development method and device for software program | |
| CN114647412A (en) | Content display method and terminal equipment | |
| CN114968032A (en) | Service processing method, device, equipment and computer readable storage medium | |
| JP4714199B2 (en) | Application development support apparatus and program | |
| Barnett et al. | A conceptual model for architecting mobile applications | |
| CN113609423B (en) | Task configuration method and device, storage medium and computer equipment | |
| CN107003867A (en) | Use customization of the section for cross-platform application | |
| CN116107869A (en) | Arrangement test method and device, electronic equipment and readable storage medium | |
| CN105141586A (en) | Method and system for verifying user | |
| CN105955718B (en) | A kind of software customized method and system | |
| CN114968741A (en) | Performance test method, system, equipment and medium based on scene platform | |
| KR100979519B1 (en) | Structure integrated service method and system of scenario/requirement analysis | |
| KR101741417B1 (en) | Method for using responsive web solution and recording medium storing program for executing the same, and recording medium storing program for executing the same | |
| KR20200139038A (en) | Devices and methods for relaying between game developers and producers | |
| KR102605698B1 (en) | System, method and program for providing 3d website making platform with event build function | |
| KR20110024478A (en) | Homepage manufacture system and method that design cording for program include | |
| CN112187993B (en) | Cross-application relationship chain extension method, device, equipment and storage medium | |
| CN113672225B (en) | User interface processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |