CN118674392A - Process configuration and management method and related equipment - Google Patents

Abstract

The present disclosure provides a process configuration and management method and related equipment. The process configuration method includes: determining a review node of a target process; obtaining one or more resources associated with the review node; creating one or more sub-work items for review for the review node based on the one or more resources, and filling in field values for at least some fields in the one or more sub-work items based on the one or more resources.

Description

Process configuration and management methods and related equipment

Technical Field

The present disclosure relates to the field of computer technology, and in particular to a process configuration and management method and related equipment.

Background Art

With the continuous development of Internet technology, many tasks can be completed intelligently. For example, management software can be used to manage some process affairs or objects.

However, the inventors of the present disclosure have discovered that in the related art, it is inconvenient to use management software to manage the review nodes in the process.

Summary of the invention

The present disclosure proposes a process configuration and management method and related devices to solve or partially solve the above problems.

In a first aspect, the present disclosure provides a process configuration method, comprising:

Determine the review nodes of the target process;

Obtaining one or more resources associated with the review node;

Based on the one or more resources, one or more sub-work items for review are created for the review node, and at least part of the fields in the one or more sub-work items are filled with field values based on the one or more resources.

In a second aspect, the present disclosure provides a process management method, including:

Obtaining configuration information of a target process configured by the method described in the first aspect;

In response to a viewing instruction for a review node of the target process, one or more sub-work items of the review node are displayed, and at least some fields of the one or more sub-work items are filled with field values based on one or more resources associated with the review node.

In a third aspect of the present disclosure, a process configuration device is provided, comprising:

The determination module is configured to: determine the review node of the target process.

The acquisition module is configured to: acquire one or more resources associated with the review node.

The creation module is configured to: create one or more sub-work items for review for the review node based on the one or more resources, and fill in field values of at least some fields in the one or more sub-work items based on the one or more resources.

In a fourth aspect of the present disclosure, a process management device is provided, comprising:

An acquisition module is configured to: acquire configuration information of a target process configured by the method described in the first aspect;

The display module is configured to: in response to a viewing instruction for a review node of the target process, display one or more sub-work items of the review node, and fill in field values of at least some fields in the one or more sub-work items based on one or more resources associated with the review node.

In a fifth aspect of the present disclosure, a computer device is provided, comprising one or more processors, a memory; and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, and the program includes instructions for executing the method described in the first aspect.

According to a sixth aspect of the present disclosure, a non-volatile computer-readable storage medium containing a computer program is provided. When the computer program is executed by one or more processors, the processors execute the method described in the first aspect.

According to a seventh aspect of the present disclosure, a computer program product is provided, including a computer program, characterized in that when the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.

The process configuration and management method and related devices provided by the embodiments of the present disclosure automatically create work items based on resources and fill in some fields, so that users do not need to manually create and fill in work items, and the operation is simpler and smoother.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings required for use in the embodiments or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG. 1A shows a schematic diagram of an exemplary system provided by an embodiment of the present disclosure.

FIG1B shows a schematic diagram of an exemplary work breakdown structure (WBS) according to an embodiment of the present disclosure.

FIG. 2A shows a schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2B shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2C shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2D shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2E shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2F shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2G shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2H shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2I shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2J shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2K shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 2L shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 3A shows a schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 3B shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 3C shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 3D shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.

FIG. 4A shows a schematic flow chart of an exemplary method provided in an embodiment of the present disclosure.

FIG. 4B shows a schematic flow chart of another exemplary method provided by an embodiment of the present disclosure.

FIG5 shows a schematic diagram of the hardware structure of an exemplary computer device provided in an embodiment of the present disclosure.

FIG. 6 shows a schematic diagram of an exemplary device provided by an embodiment of the present disclosure.

FIG. 7 shows a schematic diagram of an exemplary device provided by an embodiment of the present disclosure.

DETAILED DESCRIPTION

In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

It is understandable that before using the technical solutions of each embodiment of the present disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.

For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly remind the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can independently choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

As an optional but non-limiting implementation, in response to receiving the user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.

FIG. 1A shows a schematic diagram of an exemplary system 100 provided by an embodiment of the present disclosure.

As shown in FIG1A , the system 100 may be used to implement online or offline project management functions, and may include terminal devices 102A, 102B, a server 106, and a database server 108. A medium (e.g., a network) providing a communication link may be included between the terminal devices 102A, 102B and the server 106 and the database server 108. The network may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

Various applications (APPs) or software may be installed on the terminal devices 102A and 102B, such as project management applications or software, collaborative office applications or software, image processing applications or software, video conferencing applications or software, reading applications or software, video applications or software, social applications or software, payment applications or software, web browsers, and instant messaging tools, etc. In some embodiments, these applications or software may be used to manage projects.

The terminal devices 102A and 102B here can be hardware or software. When the terminal devices 102A and 102B are hardware, they can be various electronic devices with display screens, including but not limited to smart phones, tablet computers, e-book readers, MP3 players, laptop computers (Laptops) and desktop computers (PCs), etc. When the terminal devices 102A and 102B are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

The server 106 may be a server that provides various services, such as a backend server that provides support for various applications displayed on the terminal devices 102A and 102B. The database server 108 may also be a database server that provides various services. It is understood that if the server 106 can implement the relevant functions of the database server 108, the database server 108 may not be set in the system 100.

Here, the server 106 and the database server 108 can also be hardware or software. When they are hardware, they can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When they are software, they can be implemented as multiple software or software modules (for example, for providing distributed services), or as a single software or software module. No specific limitation is made here.

It should be noted that the method for editing a document provided in the embodiment of the present disclosure can be executed by the server 106. It should be understood that the number of terminal devices, users, servers, and database servers in FIG. 1A is only illustrative. Any number of terminal devices, users, servers, and database servers may be provided as required.

In some embodiments, the terminal devices 102A and 102B may be installed with a project management application or software, and the users 104A and 104B may use the application or software installed in the terminal devices 102A and 102B to manage the project. For example, the work items related to the project process and process nodes may be set. As an optional embodiment, the user 104A may be the administrator of the project, who is responsible for coordinating the management of the entire process of the project, and the user 104B may be a participant of the project. After the user 104A has established the process, the user 104B may view the process and operate according to the process.

One type of project management is the integrated product development process (IPD), in which review management is a very important business management scenario in the process, which determines whether the process can flow normally.

Generally, the integrated product development process may go through multiple different types of review nodes, such as peer review, technical review, decision review, etc. Each review node requires the participation of relevant personnel. Therefore, project management software needs a review management function, which conforms to user habits and can greatly improve user experience.

The review process usually requires decision makers to give review conclusions on the review content based on the review dimensions and reference decision-making reference resources. The review conclusions affect the project process or status.

FIG1B shows a schematic diagram of an exemplary work breakdown structure (WBS) according to an embodiment of the present disclosure.

As shown in Figure 1B, the project development process work items can be decomposed into multiple process nodes, which have a certain execution order. Among them, the feasibility analysis node, peer review node, technical review node, decision review node and other process nodes can be review nodes. The project process can only flow to the next node after the review process and passing the review.

As shown in FIG1B , illustratively, the feasibility analysis node is further associated with a deliverable work item, and the deliverable work item and the project development process work item are in a parent-child relationship, so the deliverable work item can be a child work item of the project development process work item, and the project development process work item can be a parent work item of the deliverable work item. The deliverable work item under the feasibility analysis node can further include a review process for the deliverables (e.g., a project feasibility report) of the feasibility analysis node, for example, submitting a feasibility report, reviewing the report, and storing the feasibility report after the review is passed, so that the review node is completed and the project process flows to the next node.

Exemplarily, as shown in FIG1B , the decision review node is further associated with a review work item, and there is a parent-child relationship between the decision review work item and the project development process work item. Therefore, the decision review work item can be a child work item of the project development process work item, and the project development process work item can be a parent work item of the decision review work item.

Exemplarily, the decision review work items under the decision review node may further include the review process for the deliverables of the decision review node (e.g., the developed product), such as review preparation, market representative & product representative review, and decision. Among them, review preparation mainly involves the deliverable work items, review problem work items, and review element resources required for decision review for preparing the deliverables to be reviewed. The review problem work items and the decision review work items may be parent-child relationships. Therefore, the review problem work items may be child work items of the decision review work items, and the decision review work items may be parent work items of the review problem work items. The market representative & product representative review mainly involves the deliverable work items, review element work items, and review problem work items. The review element work items and review problem work items may be parent-child relationships with the decision review work items. Among them, each review element work item corresponds to a reviewer, a review conclusion, and a review description. The representative review node of the decision review work item also corresponds to a reviewer, a review conclusion, and a review description. The decision mainly involves the review problem work items related to making decisions, and the decision child nodes also correspond to reviewers, review conclusions, and review descriptions, and also correspond to final reviewers and final review conclusions.

The structures of peer review nodes and technical review nodes are similar to those of decision review nodes (generally excluding decision sub-nodes), and will not be described in detail here.

It can be seen that, given the complexity of the review process, in order for the review process to proceed smoothly, project management software needs to provide users with functions that facilitate the completion of the decision-making process. However, project management software of related technologies more or less has certain problems of being not smooth to use.

In view of this, one aspect of an embodiment of the present disclosure provides a process configuration method.

Fig. 2A shows a schematic diagram of an exemplary page 200 according to an embodiment of the present disclosure. The page 200 can be used to configure a project process.

As shown in Fig. 2A, in some embodiments, user 104A can use terminal device 102A to open collaborative office software, and then terminal device 102A can display page 200. Exemplarily, the first area 200A of page 200 can display a project flow chart, which further includes multiple process nodes arranged and connected in the order of process execution.

As shown in FIG2A , for example, the user 104A can select the review node 2 (the review node 2 is highlighted), and the second area 200B of the page 200 displays the node information of the selected node by default, and the node information label 202A is highlighted. For example, the user 104A clicks the sub-work item label 202B, and the second area can display a plurality of configuration buttons for configuring the sub-work items of the review node 2, as shown in FIG2B .

Optionally, the user 104A clicks the configuration button 204A to issue an instruction to the terminal device 102A to add a sub-work item for the review node based on the resource, and the terminal device 102A responds to the instruction and can display a resource adding window 206 in the page 200, as shown in FIG2C. Optionally, the terminal device 102A can obtain a resource list from a resource library and display the resource list, as shown in FIG2C. The resource library can be pre-configured, and the resources therein can be used for the review process, and some sub-work items can be automatically generated for the review node by importing resources.

As shown in FIG2C , window 206 may optionally include a search box for searching required resources by keywords. Optionally, window 206 may also include a filter control. When user 104A triggers the filter control, a pop-up window may be displayed on one side of the filter control. The pop-up window may be used to set filter conditions, so that resources in the resource list may be filtered based on the filter conditions (e.g., classification conditions, stage conditions, etc.). In this way, user 104A may easily find the resources to be added.

As shown in FIG2C , optionally, a check box is set in front of each resource in the resource list, and the user 104A can select the resource to be added by checking the check box of the corresponding resource. As shown in FIG2C , illustratively, the user 104A selects resources 2, 4, and 7, and the selected resources are displayed on the right side of the window 206. The user 104A clicks the OK button to issue an add instruction for one or more resources (e.g., resources 2, 4, and 7) in the resource list to the terminal device 102A, and the terminal device 102A can obtain one or more resources (e.g., resources 2, 4, and 7) associated with the review node according to the add instruction.

Next, the terminal device 102A can create one or more sub-work items for review for the review node based on the one or more resources (e.g., resources 2, 4, 7), and at least some of the fields in the one or more sub-work items (e.g., review element fields) are filled with field values based on the one or more resources. In this way, some sub-work items can be preset for the review node in advance, so there is no need to add them manually. It can be understood that the matching relationship between resources and sub-work items can be pre-set, and the sub-work items can be automatically created and filled with values of at least some fields by only importing resources later.

In some embodiments, after adding a sub-work item based on a resource, the added sub-work item can be displayed on the page, and the first configuration buttons 2042 to 2046 are displayed on one side of the sub-work item, as shown in Figure 2D. Optionally, the added sub-work item can display relevant prompt information, for example, the information of the review element field corresponding to the sub-work item is displayed on the sub-work item, so that the user can intuitively know what review element the sub-work item corresponds to.

The first configuration buttons 2042 to 2046 are used to edit the added sub-work items, and can also be used to configure the visible conditions of the added sub-work items. Exemplarily, in response to the first configuration button being triggered (for example, the user 104A clicks the button 2042), the visible condition configuration window 208 of the sub-work item is displayed, as shown in FIG2E. Optionally, the visible condition configuration window 208 may include first configuration items 2082 and 2084 for configuring the visible conditions. In some embodiments, after opening the window 208, the default visible button is selected by default, and after the condition-satisfied visible button is selected, the configuration condition area is displayed in the window 208, as shown in FIG2E. Exemplarily, the first configuration items 2082 and 2084 in the window 208 can be generated in the window 208 by the user 104A by triggering the add condition control 2086 in the window 208. Optionally, the optional range of the leftmost option of the first configuration items 2082 and 2084 can be the field of the parent work item to which the sub-work item belongs (for example, the review element of the parent work item), the role (for example, the reviewer of the parent work item), etc. The middle option of the first configuration items 2082 and 2084 can be an operator, and the rightmost option can be the content corresponding to the leftmost option. "And" and "Or" relationships can also be set between multiple conditions, or the relationship between conditions can be set by entering a conditional formula. For example, taking Figure 2E as an example, the currently set condition is that when the review elements of the parent work item include "Is the market segment large enough?" and the reviewers of the parent work item include Zhang San, the sub-work item corresponding to the review element "Is the demand reasonable?" can be displayed.

In response to receiving the configuration completion instruction, the terminal device 102A determines the visible condition of the sub-work item according to the configuration information of the first configuration item, so as to display the sub-work item when the visible condition is met. In this way, by setting the visible condition, the sub-work item can be displayed when the condition is met, and not displayed when the condition is not met, so that the user 104A can flexibly configure the review process and use it conveniently.

Optionally, the added sub-work item can also be deleted, and the operation log of editing and deleting the sub-work item can be recorded. The user 104A can view the log in the log page and retrieve the sub-work item.

Returning to FIG. 2B , optionally, a second configuration button 204B for configuring the sub-work item table view may also be displayed in the second area 200B of the page 200. Since the work item includes multiple fields, in order to fully present the sub-work item content, the work item may be presented in the form of a schedule. Furthermore, since the fields required for different review nodes or review processes may be different, the effect of the final presented schedule may be adjusted by configuring the sub-work item table view.

Exemplarily, in response to the triggering of the second configuration button (e.g., the user clicks button 204B), a table view configuration window 210 of the one or more sub-work items may be displayed in page 200, as shown in FIG2F. Optionally, the table view configuration window 210 includes a table view preview area 210A and a table column resource list area 210B (including a table column resource list) located on one side of the table view preview area, the table view preview area 210A includes a preview image of the table view of the one or more sub-work items generated based on the currently selected table column (as shown in FIG2F), and the table column resource list includes a plurality of table column resources for adding corresponding table columns in the table view of the one or more sub-work items. Optionally, as shown in FIG2F, the table column resources include resources for table columns for filling in text, such as name, description, and the like. As shown in FIG2F, the table column resources may also include resources for selecting field values, such as priority, requirement status, review conclusion, label, and the like.

The table column resources in the table column resource list area 210B can be added to the table view preview area 210A to update the preview image, and then the table view on the application side can be updated based on the preview image. Therefore, in response to an add instruction for a target table column resource (any table column resource in the table column resource list area 210B) among the multiple table column resources (for example, long pressing the resource and dragging it to the table view preview area 210A), the preview table column corresponding to the target table column resource can be added to the preview image, thereby updating the preview image, and the updated preview image is consistent with the table view presented on the application side (including consistency in arrangement format and specific content).

In this way, the user can easily adjust the table view of the schedule so that the application side can be more in line with the habits of the review process or the user's habits when displaying the schedule.

In some embodiments, as shown in FIG2F , the table column resource list includes a review conclusion table column resource 2102; in response to an add instruction for the review conclusion table column resource 2102 (for example, dragging the review conclusion table column resource 2102 to the right side of the review element preview table column), a review conclusion preview table column 2104 corresponding to the review conclusion table column resource is added in the preview image, and the review conclusion preview table column includes a first preview table column 2104A corresponding to the review role, a second preview table column 2104B corresponding to the reviewer, a third preview table column 2104C corresponding to the review conclusion, a fourth preview table column 2104D corresponding to the review opinion, and a fifth preview table column 2104E corresponding to the review operation, as shown in FIG2G . In some embodiments, the user 104A can also configure an associated node for each review conclusion in the preview image, so that the relevant node is also associated with the corresponding review conclusion table column, and there is no need to set it separately for the node.

In this way, user 104A conveniently adds a review conclusion table column in the table view, and user 104B can subsequently give his own review conclusion based on the review conclusion table column for each review element sub-work item through review operations (for example, pass, fail, or conditionally pass).

As shown in FIG. 2F , window 210 also includes a basic settings label. By clicking on the label, the content of window 210 can be switched to display the configuration items corresponding to the basic settings, which may include various table view templates. User 104A can select any template to generate a corresponding table view, so that there is no need to configure it by itself, which is convenient to use. Optionally, user 104A can also select a template to generate a table view first, and then switch to the table settings to further adjust the table view template.

Returning to FIG. 2B , in some embodiments, page 200 may also display a third configuration button 204C for configuring the personnel linkage rules of the sub-work items. Optionally, in response to a hover instruction for the third configuration button 204C (e.g., moving the cursor to the third configuration button 204C and staying there), a prompt message "If the rule is configured, the configuration of all node responsible persons of the sub-work items will no longer take effect; if the rule is not configured, the configuration of the node responsible person of the sub-work items will take effect" may be displayed, thereby prompting user 104A that once the rule is configured, the responsible person originally configured for each sub-work item will not take effect, and the responsible person automatically added to meet the rule will be the responsible person of the sub-work item.

In response to the third configuration button 204C being triggered, a personnel linkage rule configuration window 212 for the one or more sub-work items may be displayed, as shown in Figure 2H. Optionally, the personnel linkage rule configuration window 212 includes a second configuration item 2122 for configuring linkage conditions and a third configuration item 2124 for configuring linkage condition groups.

As shown in Figure 2H, user 104A can add a condition group by clicking the third configuration item 2124. The condition group configuration area further displays a second configuration item 2122 for configuring linkage conditions. In each condition group, the optional range of the leftmost option is the field of the sub-work item, and the operator and the rightmost option are the contents configured by the user.

After setting the conditions, you can configure the results of the rules. The selectable range of the drop-down box on the left is the role on the parent work item of the child work item, and multiple selections are allowed. The selectable range of the drop-down box on the right is the designated node owner of the designated process template on the child work item, and only a single selection is allowed.

In response to receiving a configuration completion instruction (for example, user 104A clicks the OK button in the lower right corner of window 212), the personnel linkage rules of the sub-work items are determined according to the configuration information of the second configuration item 2122 and/or the third configuration item 2124, so as to add reviewers corresponding to the personnel linkage rules to the one or more sub-work items when the personnel linkage rules are met.

Taking Figure 2H as an example, when the personnel linkage rule is currently created, when the sub-work item belongs to the marketing field and the development field, the director and product manager of the parent work item will be synchronized as the R&D representative/node person in charge in the sub-work item.

In this way, by setting up personnel linkage rules, we can avoid omitting important persons in charge in certain review processes and ensure that the review process is more complete.

Optionally, the above editing records may also be recorded in an operation log for the user to trace back or retrieve.

In some embodiments, a trimming control may be added to each sub-work item, so that user 104B can delete unnecessary sub-work items (especially review element sub-work items) on the application side, thereby avoiding unnecessary review elements from appearing in the review process. When configuring the trimming control, each sub-work item may be configured, and trimming permissions (i.e., which roles can trim sub-work items) may be configured. After the trimming control is configured, the trimming control may be displayed on the side of the corresponding sub-work item on the application side, so that user B can use the trimming control to delete unnecessary sub-work items in the review process.

Returning to FIG. 2A , the second area 200B of the page 200 displays the configuration items corresponding to the node information label 202A. Under the page corresponding to the node information label 202A, the fields of the review node can be customized, and whether and how the field is displayed can be configured. Optionally, the system default node fields may include node name, node ID, node person in charge, node schedule, node estimated score, and node actual working hours.

In some embodiments, as shown in FIG2A , a node completion conclusion configuration item 2142 and a node completion opinion configuration item 2144 may be displayed in page 200, and user 104A may configure the node completion conclusion and node completion opinion attributes for the review node by checking the node completion conclusion configuration item 2142 and the node completion opinion configuration item 2144, so that the review node is considered completed only when the node completion conclusion and the node completion opinion are filled in.

Optionally, after the node completion conclusion configuration item 2142 is checked, the node completion conclusion filling control needs to be displayed on the application side, and the node completion conclusion (the completion conclusion of the node as a whole) and the review conclusion of the node person in charge corresponding to each work item need to be filled in the filling control, wherein the review conclusion of the node person in charge corresponding to each work item is only authorized to be modified and filled in by the node person in charge of the work item, and the node completion conclusion can be filled in manually by the node authorized role. The node completion conclusion and review conclusion filled in by myself and others can be displayed on the page of the application side. In some embodiments, it can be summarized according to the node completion conclusion rule. User 104A can configure the node completion conclusion rule.

The options corresponding to the conclusion can be configured, and at least one option needs to be retained. Optionally, the default options for the conclusion may include pass, fail, and conditional pass. User 104A can view the configured options for the conclusion and modify these options through option configuration item 2146.

Optionally, after the node completion opinion configuration item 2144 is checked, the node completion opinion filling control needs to be displayed on the application side, and the node completion opinion (the overall node completion opinion) and the review opinion of the node person in charge corresponding to each work item need to be filled in the filling control. The opinions can be in text format. Among them, the review opinions of the node person in charge corresponding to each work item are only authorized to be modified and filled in by the node person in charge of the work item, and the node completion opinions can be filled in manually by the node authorized role. The node completion opinions and review opinions filled in by myself and others can be displayed on the page on the application side.

As shown in Figure 2A, optionally, a fourth configuration button 2148 for configuring the node completion conclusion of the review node can also be displayed in the page 200, and the node completion conclusion is defaulted to be manually filled in by the node authorization role. In some embodiments, in response to the fourth configuration button 2148 being triggered, the node completion conclusion rule configuration window 216 of the review node can also be displayed in the page 200, as shown in Figure 2I. Optionally, the node completion conclusion rule configuration window 216 includes fourth configuration items 2162 and 2164 for configuring the node completion conclusion rule. It can be understood that in the initial state, the fourth configuration items 2162 and 2164 may not be displayed in the window 216, and the user 104A can add the fourth configuration item by clicking the add rule button to complete the rule configuration.

Exemplarily, as shown in FIG2I, the fourth configuration items 2162 and 2164 include the conditions of the rule and the rule results when the conditions are met. Among them, the rule conditions include 5 options from left to right. The first option is a single choice, and the optional range is more than or less than; the second option is to fill in a number; the third option is a single choice, and the optional range is a number or a percentage; the fourth option is used to select the role of the reviewer (or person in charge), multiple selections are allowed, and the drop-down menu may include all personnel related to the review node; the fifth option is used to select the completion conclusion, multiple selections are allowed, as mentioned above, this option is configurable, and usually includes three types: pass, fail, and conditional pass. The rule result when the conditions are met can be pass or fail.

For example, taking Rule 1 configured in FIG. 2I as an example, the rule is that when the total number of review conclusions of the product manager or the R&D personnel as passed or conditionally passed exceeds 3, the node completion conclusion is passed. Optionally, if there is a person whose role is both a product manager and a R&D personnel, its count is only 1.

As shown in Figure 2I, optionally, multiple rules can be set, and a fallback rule can be set, that is, when all configured rules are not met, the completion conclusion is summarized as pass or fail. Taking the rules configured in Figure 2I as an example, when both rule 1 and rule 2 are not met, the node completion conclusion is fail.

In response to receiving a configuration completion instruction, a node completion conclusion rule of the review node is determined according to the configuration information of the fourth configuration item, and is used to generate a node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is met.

Exemplarily, after configuring the above rules, on the application side, when all node leaders corresponding to the review node (for example, the leader or reviewer corresponding to each sub-work item) submit their review conclusions, the above rules are triggered to summarize and calculate the review conclusions. If the node leader updates his review conclusion, recalculation is triggered.

As shown in FIG. 2I , optionally, prompt information 2166 may also be displayed in window 216 to prompt the user of the consequences of the rule configuration (for example, “When everyone has completed filling in the review conclusion, execute the following rules for summary”), the order of executing the rules (for example, “The rules take effect from top to bottom”), and the configuration method (for example, “The order can be adjusted by dragging”).

Correspondingly, on the application side, when the summary calculation of the review conclusion is triggered, the rules configured in the window 216 can be judged in sequence. When the first rule is hit, the subsequent rules will no longer be matched.

In addition, the options can be optionally verified. For example, when the name of the node completion conclusion option in the rule is edited, the rule display is updated synchronously; when all the node completion conclusion options in the rule are deleted, the rule does not take effect, an error mark is given, and the user is prompted when saving.

In some embodiments, in addition to the above-mentioned method of configuring node completion conclusions and node completion opinions, configuration can also be performed in the general node information page, and the configured node can be selected in the drop-down menu of the node name configuration item. The optional range is all nodes in the work item process template. Nodes with the same name only appear once (that is, if the node has been configured with node completion conclusions and node completion opinions, it will no longer be displayed in the drop-down menu) and are positioned by name.

Returning to FIG. 2A , optionally, the second area 200B of the page 200 may further include a node flow label 202C. When the user 104A clicks the node flow label 202C, configuration items for configuring the state flow of the review node may be displayed in the second area 200B of the page 200, as shown in FIG. 2J . Optionally, the second area 200B may include a fifth configuration button 218 for configuring the completion flow condition of the review node.

Optionally, in response to the fifth configuration button 218 being triggered, a completion flow condition configuration window 220 of the review node may be displayed in the page 200, as shown in FIG2K. Optionally, the completion flow condition configuration window 220 may include a fifth configuration item 2202 for configuring the completion flow condition of the review node. As shown in FIG2K, the fifth configuration item 2202 may be newly created in the window 220 by clicking the Add Condition button, and each fifth configuration item 2202 may include three options, the leftmost option is used to select the field of the sub-work item under the review node, the middle option is used to select the logical operator, and the rightmost option is used to select the specific content.

In response to receiving a configuration completion instruction (for example, user 104A completes the configuration of each option and clicks the OK button in the lower right corner of window 220), the completion flow condition of the review node is determined according to the configuration information of the fifth configuration item, which is used to determine whether the review node can flow according to the completion flow condition.

Whether it can be transferred may refer to whether the status of the review node can change. In some embodiments, as shown in FIG2J, the user can first configure the node transfer condition and then configure the completion transfer condition, wherein the configuration item checked in the node transfer condition requires the corresponding review field to be completed, and when the node transfer condition is met, the completion transfer condition is further met (for example, the review form field contains the technical solution to be confirmed and the reviewer includes Zhang San), then the status of the review node is considered to meet the change condition.

Optionally, after the state change condition is met, the state to which the state of the node should flow can also be set through configuration. As shown in Figure 2J, the second area 200B can also include a sixth configuration button 222 for configuring the node flow state of the review node.

In response to the sixth configuration button 222 being triggered, a node flow state configuration window 224 of the review node is displayed, as shown in Figure 2L. Optionally, the node flow state configuration window 224 includes a sixth configuration item 2242 for configuring a node flow state calculation rule of the review node.

As shown in FIG. 2L, illustratively, the flow state of the review node may include three, unstarted, in progress and completed. Each state may correspond to the configuration node flow state calculation rule, and the node flow state calculation rule of each state may be configured in the window 224. Optionally, as shown in FIG. 2L, each state corresponds to a sixth configuration item 2242, and after each sixth configuration item 2242 is triggered, a drop-down box may be generated for the state, and the drop-down box includes specific options for configuring the node flow state calculation rule. Exemplarily, as shown in FIG. 2L, a drop-down box 2244 of a completed state is displayed in the window 224, and the right side of the drop-down box 2244 includes information about the condition currently being configured, and the left side of the drop-down box 2244 includes the conditions that have been configured. When any condition that has been configured on the left side of the drop-down box 2244 is selected, the selected condition is highlighted, and the right side of the drop-down box 2244 can display the specific information of the condition, and the condition can be modified by modifying this information. As shown in FIG. 2L , optionally, a new node flow state and its calculation rules may be created by adding a set of state and condition buttons.

In response to receiving a configuration completion instruction (for example, user 104A completes the configuration of each option and clicks the OK button in the lower right corner of window 224), the node flow status of the review node is determined according to the configuration information of the sixth configuration item 2242, and is used to calculate the flow status of the review node according to the node flow status calculation rule.

Exemplarily, as shown in FIG2L , when the stage of the review node is the project establishment stage and the node leader does not include Zhang San, the flow status of the review node is completed.

Optionally, a fallback rule can also be set, that is, when no node flow status calculation rule is configured, the status calculation is completed when the node is completed.

In some embodiments, the state calculation rules of the entire project can also be configured to calculate the overall state of the project. Optionally, these state calculation rules can be judged according to the flow state of each node. The way of setting the state calculation rules is similar to the way of configuring the node flow state calculation rules, which will not be repeated here.

In some embodiments, user 104A can also configure buttons (buttons with corresponding words) corresponding to review operations (including pass, fail, conditional pass, etc.), for example, configure button names, button styles, button events (events triggered after the button is clicked, such as configuration forms, data assignments, completion nodes, etc.).

After the configuration is completed by the above method, process management can be performed based on the information of the completed configuration. For example, the user 104B can use the terminal device 102B to open the collaborative office software to perform project process management.

FIG. 3A shows a schematic diagram of an exemplary page 300 according to an embodiment of the present disclosure.

As shown in FIG3A , for example, user 104B can use terminal device 102B to open collaborative office software and obtain configuration information of the target process (current project) configured by the aforementioned process configuration method, and then terminal device 102B can display page 300. For example, as shown in FIG3A , page 300 can display a flowchart of the project, and the flowchart further includes multiple process nodes arranged and connected in the order of process execution.

In some embodiments, the configuration information of the target process (current project) configured using the aforementioned process configuration method can also be obtained, for example, one or more resources associated with the review node in the target process, and then one or more sub-work items corresponding to the configuration information are created for the review node in the target process, and at least some of the fields in the one or more sub-work items are filled in with field values based on the one or more resources associated with the review node.

In some embodiments, in response to a view instruction for a review node of the target process (eg, double-clicking the review node in the flowchart), the one or more sub-work items of the review node are displayed, as shown in FIG. 3B .

Exemplarily, FIG3B shows a plurality of sub-work items corresponding to the review elements of review node 2. At least part of these sub-work items may be created based on one or more resources associated with the review node 2, and the field values of at least part of the fields therein may be filled in based on the one or more resources associated with the review node. For example, the work items corresponding to review elements 1 to 11 may be created based on resources, and the field values of review elements 1 to 11 are filled in based on resources.

As mentioned above, the review factor can be a standard or requirement in the review process, such as whether the market segment is large enough, whether the market research is sufficient, whether the demand is reasonable, etc. In the review process, the reviewer or the person in charge can conduct the review around the review factor and give the review conclusion based on the information obtained during the review process. It can be seen that the review factor, the deliverables to be reviewed, and the review questions can all be independent sub-work items under the review node. Here, only the sub-work items corresponding to the review factor are described.

In some embodiments, in response to the review node being deleted, the parent-child association relationship between the one or more sub-work items and the review node is released, and the status of the one or more sub-work items remains unchanged; in response to the review node being restored, the one or more sub-work items are automatically associated with the review node again in a parent-child relationship. In this way, it is ensured that the sub-work items are not deleted after the review node is deleted, and when the review node is created again, the original sub-work items are automatically associated with the review node, so that the sub-work items that have been created do not need to be created again.

In some embodiments, when displaying one or more sub-work items of the review node, the visible condition of the sub-work item can be obtained (see FIG. 2E ), and then, based on the visible condition, one or more sub-work items that meet the visible condition are displayed. In this way, the sub-work items that meet the visible condition are displayed, and the sub-work items that do not meet the visible condition are hidden, which can save page space on the one hand, and prevent users from spending effort on sub-work items that do not need to be reviewed on the other hand, thereby improving work efficiency.

In some embodiments, when displaying one or more sub-work items of the review node, the personnel linkage rules of the sub-work items may be acquired, and then the personnel information satisfying the personnel linkage rules may be displayed in the sub-work items.

As shown in FIG2H, for the personnel linkage rules that have been created, all condition groups are executed in the order of the personnel linkage rules corresponding to the sub-work item, and the execution stops after the first condition group is matched, and the field value of the reviewer of the parent work item of the sub-work item that meets the conditions is filled into the node leader of the sub-work item. If the node leader of the sub-work item does not hit any personnel linkage rules, the node leader is matched according to the node leader rule of the sub-work item itself.

Optionally, after a child work item is successfully created, modifying the information of the parent work item or the child work item will not automatically modify the node leader of the child work item; at the same time, modifying the node leader of the child work item will not affect the role of the parent work item.

In some embodiments, the one or more sub-work items include a review conclusion table column, and the review conclusion table column includes at least one of a first table column corresponding to the review role, a second table column corresponding to the review personnel, a third table column corresponding to the review conclusion, a fourth table column corresponding to the review opinion, and a fifth table column corresponding to the review operation.

As shown in FIG3B, illustratively, the first-level title of the review conclusion table column can be the review conclusion. The second-level title of the review conclusion table column includes 5. Among them, the column title of the first table column can be the review role, and its field value can be the role name of the reviewer in the parent work item. If there are multiple role names, multiple can be displayed, and "-" can be displayed when there is no role. The column title of the second table column can be the reviewer, and its field value can be the configured person in charge or the node person in charge, and each person in charge displays a row. The column title of the third table column can be the review conclusion, and its field value can be the node completion conclusion on the configured node, and the editing authority of the current user can be judged according to the node logic. The column title of the fourth table column can be the review opinion, and its field value can be the node completion opinion on the configured node, and the editing authority of the current user can be judged according to the node logic. The column title of the fifth table column can be the review operation, and its field value can be the node completion operation button on the configured node, and the editing authority of the current user can be judged according to the node logic. The row without editing authority can display the current process status of the review node. Optionally, the review role, reviewer, review conclusion, and review opinion can also be filtered.

As mentioned above, a trimming control may also be configured for resources or sub-work items to delete unnecessary resources or sub-work items. Therefore, in some embodiments, a check box may be displayed on the leftmost side of each sub-work item, and when the user 104B checks the corresponding sub-work item and clicks the delete button, the sub-work item may be deleted.

FIG. 3C shows another schematic diagram of an exemplary page 310 according to an embodiment of the present disclosure.

As shown in FIG3C , review node 2 corresponds to parent work item 312, which includes review element sub-work items and review question sub-work items. The review element sub-work items and review question sub-work items display column fields according to the aforementioned configuration information, and display filtering, sorting, and grouping controls. In some embodiments, user 104B can also use terminal device 102B on the application side to import resource library resources to automatically create sub-work items and establish a parent-child relationship with the current parent work item.

In some embodiments, as shown in FIG3C , if the status of the review node is in progress, the operation button (pass, fail, conditional pass) of the node in the parent work item 312 can be displayed in page 310, and only the authorized role can perform the operation, and the unauthorized role can only view it, so as to avoid the unauthorized role from making an erroneous operation; if the status of the review node is not started or completed, the operation button (pass, fail, conditional pass) in the parent work item 312 can not be displayed in page 310, so as to avoid the user from making an erroneous operation by displaying the button at an inappropriate time. When the authorized role clicks the corresponding operation button, a prompt message "xx data is modified to xx, and the node has been completed" can be displayed, prompting the user that the operation is successful. In some embodiments, in response to the operation button being clicked, the node transfer conditions configured in the aforementioned embodiments can be obtained first, and the node transfer conditions can be verified (including whether the checked mandatory items have been filled in and the configured node transfer conditions). If they are not met, the mandatory item mark can be displayed or the prompt "Does not meet the node transfer conditions, xxx (the name of the first rule that does not meet the conditions, for example, Rule 1)" can be displayed. At this time, the operation button status is not changed, and the node status is not changed.

In some embodiments, if the review process of the review node involves multiple people and the node status is in progress, in response to user 104B (current user) being the node leader and user 104B not operating the node completion operation button in the parent work item 312, the node completion operation button in the parent work item 312 in FIG. 3C is displayed for user 104B to operate. If the node status is not started or the node is completed, the operation button is not displayed. In some embodiments, in response to the operation button being clicked and only one node leader is left without operation, the node transfer conditions configured in the aforementioned embodiment can be obtained first, and the node transfer conditions can be checked (including whether the checked mandatory items have been filled in and the configured node transfer conditions). If not satisfied, the mandatory item mark can be displayed or the prompt "Does not meet the node transfer conditions, xxx (the first rule name that does not meet the conditions, for example, rule 1)" can be displayed. At this time, the operation button state is not changed, and the node state is not changed. In some embodiments, if any node leader does not operate the node completion operation button in the parent work item 312 of its page 310, after the node leader triggers the operation button, a prompt "xx data is modified to xx, single person has completed" is displayed, and all operation buttons are still displayed until all the leaders of the node have operated, and the node status is displayed in page 310, and the operation button is not displayed. In some embodiments, as shown in FIG3C, when the parent work item 312 of page 310 includes the node leader, the node leader is linked with the role. If user 104B is the leader, he can fill in the various roles he has in the parent work item 312, so that linkage can be achieved based on the personnel linkage rules.

It can be understood that, referring to Figure 1B, the review process can be abstracted into three steps: review preparation, review conclusion, and review summary. Among them, review preparation can be used to determine the materials that need to be reviewed (for example, whether the deliverables are ready) and the elements to be reviewed (for example, the review elements can be adjusted through the trimming control); the review conclusion includes the review opinions and review conclusions given by each reviewer; the review summary includes generating the final review conclusion (node completion conclusion).

The above-mentioned embodiment describes the presentation of the relevant information of the review. The following introduces the review conclusion presentation and summary rules and the node flow rules based on the summarized review conclusion.

In some embodiments, each person who participates in the review process of the review node can give his or her own review conclusion in his or her own collaborative management software.

FIG. 3D shows another schematic diagram of an exemplary page 320 according to an embodiment of the present disclosure.

As shown in FIG3D , user 104B can display page 320 in the collaborative management software of terminal device 102B, and all the operational process nodes of user 104B are summarized in page 320. Exemplarily, for project 1, user 104B can generate a drop-down window 3202 by clicking any operation button, and the nodes that user 104B needs to operate under project 1 can be displayed in the window 3202, and the window 3202 also sets an operation button after each node for user 104B to perform quick operations. After the operation is completed, system 100 can obtain the review operation information of the one or more sub-work items of each review node to summarize the review conclusion. Then, based on these review operation information, the node completion conclusion and flow status of the review node can be determined.

In some embodiments, according to the review operation information, determining the node completion conclusion and flow status of the review node includes: obtaining the node completion conclusion rule of the review node; determining the node completion conclusion of the review node according to the review operation information and the node completion conclusion rule, so as to realize automatic aggregation of the node completion conclusion. Optionally, the page can display the specific completion information of the node person in charge, wherein the node completion conclusion and node completion opinion can be displayed in independent columns.

In some embodiments, the node completion conclusion and flow status of the review node are determined based on the review operation information, including: obtaining the completion flow condition of the review node; determining the flow status of the review node based on the review operation information, the node completion conclusion, the completion flow condition and the node flow status calculation rule, thereby realizing automatic calculation of the node flow status.

Exemplarily, in some embodiments, when user 104B clicks an operation button, a check can be performed according to the node flow conditions. If the conditions are met, the operation corresponding to the operation button can be completed, and then it is determined whether the review node has been completed (both the node leader and the reviewer have completed the operation). If not, a reminder is given to the corresponding node leader or reviewer who has not completed the operation. When the review node has been completed, the flow of the review node is calculated according to the node flow status calculation rules, and it is transferred to the next node.

It can be seen from the above embodiments that the process configuration and management method provided by the embodiments of the present disclosure automatically creates work items based on resources and fills in some fields, so that users do not need to manually create and fill in work items, and the operation is simpler and smoother.

It should be noted that the method of the embodiment of the present disclosure can be performed by a single device, such as a computer or a server. The method of the present embodiment can also be applied in a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present disclosure, and the multiple devices will interact with each other to complete the described method.

It should be noted that some embodiments of the present disclosure are described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

FIG4A shows a flow diagram of an exemplary method 400 provided in an embodiment of the present disclosure. The method 400 can be used to configure a process for a project. Optionally, the method 400 can be implemented by the terminal device 102A of FIG1A alone, or by the system 100 of FIG1A.

As shown in FIG. 4A , the method 400 may further include the following steps.

In step 402, a review node of the target process is determined (eg, review node 2 of FIG. 2A).

In step 404, one or more resources associated with the review node (eg, resources 2, 4, 7 in FIG. 2C) are obtained.

In step 406, based on the one or more resources, one or more sub-work items for review are created for the review node, and at least some of the fields in the one or more sub-work items are filled with field values based on the one or more resources (for example, the review element work items and their field values in Figure 2F).

The process configuration method provided by the embodiment of the present disclosure automatically creates work items based on resources and fills in some fields, so that users do not need to manually create and fill in work items, and the operation is simpler and smoother.

In some embodiments, obtaining one or more resources associated with the review node includes:

Receive instructions to add sub-work items to review nodes based on resources;

Obtain a resource list from the resource library and display the resource list (see FIG2C );

According to an adding instruction for one or more resources in the resource list (for example, checking corresponding resources 2, 4, 7), one or more resources associated with the review node are acquired.

In this way, adding by automatically displaying the resource list makes it more convenient to use.

In some embodiments, the method further comprises:

Displaying the one or more sub-work items in the page, and displaying a first configuration button (eg, configuration buttons 2042 to 2046 in FIG. 2D ) on one side of the sub-work items;

In response to the first configuration button being triggered, displaying a visible condition configuration window (e.g., window 208 in FIG. 2E ) of the sub-work item, wherein the visible condition configuration window includes a first configuration item (e.g., configuration items 2082 and 2084 in FIG. 2E ) for configuring a visible condition;

In response to receiving the configuration completion instruction, a visibility condition of the sub-work item is determined according to the configuration information of the first configuration item, so as to display the sub-work item when the visibility condition is met.

In this way, by setting visible conditions, you can filter based on the visible conditions when displaying sub-work items, avoid unnecessary sub-work items taking up page space and avoid user misoperation.

In some embodiments, the method further comprises:

Displaying a second configuration button (eg, configuration button 204B in FIG. 2B ) for configuring the sub-work item table view on the page;

In response to the second configuration button being triggered, a table view configuration window (e.g., window 210 in FIG. 2F ) of the one or more sub-work items is displayed, the table view configuration window comprising a table view preview area 210A and a table column resource list located on one side of the table view preview area, the table view preview area comprising a preview image of a table view of the one or more sub-work items generated based on a currently selected table column, and the table column resource list comprising a plurality of table column resources for adding corresponding table columns in the table view of the one or more sub-work items;

In response to an adding instruction for a target table column resource among the plurality of table column resources, a preview table column corresponding to the target table column resource is added to the preview image.

In this way, the table column resource list is used to display the optional table columns of the table view, and the table view can be configured by dragging and dropping, which is convenient to use.

In some embodiments, the table column resource list includes a review conclusion table column resource;

In response to an instruction to add a target table column resource among the plurality of table column resources, adding a preview table column corresponding to the target table column resource in the preview image includes:

In response to an instruction to add the review conclusion table column resource, a review conclusion preview table column 2104 corresponding to the review conclusion table column resource is added in the preview image, and the review conclusion preview table column includes a first preview table column 2104A corresponding to the review role, a second preview table column 2104B corresponding to the reviewer, a third preview table column 2104C corresponding to the review conclusion, a fourth preview table column 2104D corresponding to the review opinion, and a fifth preview table column 2104E corresponding to the review operation.

In this way, by configuring the review conclusion table column for the table view, users can easily give or view the review conclusion, thereby improving work efficiency.

In some embodiments, the method further comprises:

Displaying a third configuration button (eg, configuration button 204C in FIG. 2B ) for configuring the personnel linkage rule of the sub-work item on the page;

In response to the third configuration button being triggered, a personnel linkage rule configuration window (e.g., window 212 of FIG. 2H ) of the one or more sub-work items is displayed, wherein the personnel linkage rule configuration window includes a second configuration item 2122 for configuring a linkage condition and a third configuration item 2124 for configuring a linkage condition group;

In response to receiving a configuration completion instruction, the personnel linkage rules of the sub-work items are determined according to the configuration information of the second configuration item and/or the third configuration item, and are used to add reviewers or node leaders corresponding to the personnel linkage rules to the one or more sub-work items when the personnel linkage rules are met.

In this way, the personnel linkage rules are used to automatically associate relevant personnel, thereby improving work efficiency and preventing relevant personnel from being missed.

In some embodiments, the method further comprises:

Displaying a fourth configuration button (eg, configuration button 2148 in FIG. 2A ) for configuring the node completion conclusion of the review node on the page;

In response to the fourth configuration button being triggered, a node completion conclusion rule configuration window (e.g., window 216 of FIG. 2I ) of the review node is displayed, wherein the node completion conclusion rule configuration window includes fourth configuration items 2162 and 2164 for configuring a node completion conclusion rule;

In response to receiving a configuration completion instruction, a node completion conclusion rule of the review node is determined according to the configuration information of the fourth configuration item, and is used to generate a node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is met.

In this way, by configuring the node completion conclusion rules, the node completion conclusion can be automatically calculated, thereby completing the conclusion summary. Users do not need to calculate manually, which improves work efficiency.

In some embodiments, the method further comprises:

Displaying a fifth configuration button (eg, configuration button 218 in FIG. 2J ) for configuring the completion flow condition of the review node on the page;

In response to the fifth configuration button being triggered, a completion flow condition configuration window of the review node (e.g., window 220 of FIG. 2K ) is displayed, wherein the completion flow condition configuration window includes a fifth configuration item 2202 for configuring the completion flow condition of the review node;

In response to receiving the configuration completion instruction, a completion flow condition of the review node is determined according to the configuration information of the fifth configuration item, and is used to determine whether the review node can flow according to the completion flow condition.

It should be noted that the method of the embodiment of the present disclosure can be performed by a single device, such as a computer or a server. The method of the present embodiment can also be applied in a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present disclosure, and the multiple devices will interact with each other to complete the described method.

It should be noted that some embodiments of the present disclosure are described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

FIG4B shows a flow chart of an exemplary method 410 provided in an embodiment of the present disclosure. The method 410 can be used to manage the process of a project. Optionally, the method 410 can be implemented by the terminal device 102B of FIG1A alone, or by the system 100 of FIG1A.

As shown in FIG. 4B , the method 400 may further include the following steps.

In step 412, configuration information of a target process configured by any embodiment or arrangement or combination of the embodiments of method 400 is obtained;

In step 414, in response to a view instruction for the review node of the target process, one or more sub-work items of the review node are displayed (as shown in FIG. 3B ), and at least some of the fields in the one or more sub-work items are filled with field values based on one or more resources associated with the review node.

The process management method provided by the embodiment of the present disclosure automatically creates work items based on resources and fills in some fields, so that users do not need to manually create and fill in work items, and the operation is simpler and smoother.

In some embodiments, displaying one or more sub-work items of the review node includes:

Obtaining the visibility condition of the sub-work item;

One or more of the sub-work items that meet the visibility condition are displayed.

In this way, sub-work items that meet the visibility conditions are displayed, and sub-work items that do not meet the visibility conditions are hidden. On the one hand, it can save page space, and on the other hand, it can prevent users from spending effort on sub-work items that do not need to be reviewed, thereby improving work efficiency.

In some embodiments, displaying one or more sub-work items of the review node includes:

Obtaining the personnel linkage rules of the sub-work item;

The personnel information satisfying the personnel linkage rule is displayed in the sub-work item.

As shown in FIG2H, for the personnel linkage rules that have been created, all condition groups are executed in the order of the personnel linkage rules corresponding to the sub-work item, and the execution stops after the first condition group is matched, and the field value of the reviewer of the parent work item of the sub-work item that meets the conditions is filled into the node leader of the sub-work item. If the node leader of the sub-work item does not hit any personnel linkage rules, the node leader is matched according to the node leader rule of the sub-work item itself.

In some embodiments, the one or more sub-work items include a review conclusion table column, and the review conclusion table column includes at least one of a first table column corresponding to the review role, a second table column corresponding to the review personnel, a third table column corresponding to the review conclusion, a fourth table column corresponding to the review opinion, and a fifth table column corresponding to the review operation.

As shown in FIG3B, illustratively, the first-level title of the review conclusion table column can be the review conclusion. The second-level title of the review conclusion table column includes 5. Among them, the column title of the first table column can be the review role, and its field value can be the role name of the reviewer in the parent work item. If there are multiple role names, multiple can be displayed, and "-" can be displayed when there is no role. The column title of the second table column can be the reviewer, and its field value can be the configured person in charge or the node person in charge, and each person in charge displays a row. The column title of the third table column can be the review conclusion, and its field value can be the node completion conclusion on the configured node, and the editing authority of the current user can be judged according to the node logic. The column title of the fourth table column can be the review opinion, and its field value can be the node completion opinion on the configured node, and the editing authority of the current user can be judged according to the node logic. The column title of the fifth table column can be the review operation, and its field value can be the node completion operation button on the configured node, and the editing authority of the current user can be judged according to the node logic. The row without editing authority can display the current process status of the review node. Optionally, the review role, reviewer, review conclusion, and review opinion can also be filtered.

In some embodiments, the method further comprises:

Acquire review operation information of the one or more sub-work items of the review node;

According to the review operation information, a node completion conclusion and a flow status of the review node are determined.

In some embodiments, determining the node completion conclusion and flow status of the review node according to the review operation information includes:

Obtaining a node completion conclusion rule of the review node;

The node completion conclusion of the review node is determined according to the review operation information and the node completion conclusion rule.

In some embodiments, determining the node completion conclusion and flow status of the review node according to the review operation information includes:

Obtaining the completion flow conditions and node flow status calculation rules of the review node;

The flow status of the review node is determined according to the review operation information, the node completion conclusion, the completion flow condition and the node flow status calculation rule.

Exemplarily, in some embodiments, when user 104B clicks an operation button, a check can be performed according to the node flow conditions. If the conditions are met, the operation corresponding to the operation button can be completed, and then it is determined whether the review node has been completed (both the node leader and the reviewer have completed the operation). If not, a reminder is given to the corresponding node leader or reviewer who has not completed the operation. When the review node has been completed, the flow of the review node is calculated according to the node flow status calculation rules, and it is transferred to the next node.

It should be noted that the method of the embodiment of the present disclosure can be performed by a single device, such as a computer or a server. The method of the present embodiment can also be applied in a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present disclosure, and the multiple devices will interact with each other to complete the described method.

It should be noted that the above describes some embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The embodiment of the present disclosure also provides a computer device for implementing the above method 400 or method 410. FIG5 shows a schematic diagram of the hardware structure of an exemplary computer device 500 provided in the embodiment of the present disclosure. The computer device 500 can be used to implement the server 106 of FIG1A, and can also be used to implement the terminal devices 102A and 102B of FIG1A. In some scenarios, the computer device 500 can also be used to implement the database server 108 of FIG1A.

As shown in Fig. 5, computer device 500 may include: processor 502, memory 504, network interface 506, peripheral interface 508 and bus 510. Processor 502, memory 504, network interface 506 and peripheral interface 508 are connected to each other in communication within computer device 500 via bus 510.

The processor 502 may be a central processing unit (CPU), an image processor, a neural network processor (NPU), a microcontroller (MCU), a programmable logic device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or one or more integrated circuits. The processor 502 may be used to perform functions related to the technology described in the present disclosure. In some embodiments, the processor 502 may also include multiple processors integrated into a single logical component. For example, as shown in FIG. 5 , the processor 502 may include multiple processors 502a, 502b, and 502c.

The memory 504 may be configured to store data (e.g., instructions, computer codes, etc.). As shown in FIG. 5 , the data stored in the memory 504 may include program instructions (e.g., program instructions for implementing the method 400 or method 410 of the disclosed embodiment) and data to be processed (e.g., the memory may store configuration files of other modules, etc.). The processor 502 may also access the program instructions and data stored in the memory 504, and execute the program instructions to operate on the data to be processed. The memory 504 may include a volatile storage device or a non-volatile storage device. In some embodiments, the memory 504 may include a random access memory (RAM), a read-only memory (ROM), an optical disk, a magnetic disk, a hard disk, a solid-state drive (SSD), a flash memory, a memory stick, etc.

The network interface 506 can be configured to provide the computer device 500 with communication with other external devices via a network. The network can be any wired or wireless network capable of transmitting and receiving data. For example, the network can be a wired network, a local wireless network (e.g., Bluetooth, WiFi, near field communication (NFC)), a cellular network, the Internet, or a combination thereof. It is understood that the type of network is not limited to the above specific examples.

The peripheral interface 508 can be configured to connect the computer device 500 to one or more peripheral devices to achieve information input and output. For example, the peripheral devices can include input devices such as a keyboard, a mouse, a touch pad, a touch screen, a microphone, and various sensors, and output devices such as a display, a speaker, a vibrator, and an indicator light.

The bus 510 may be configured to transmit information between various components of the computer device 500 (e.g., the processor 502, the memory 504, the network interface 506, and the peripheral interface 508), such as an internal bus (e.g., a processor-memory bus), an external bus (USB port, PCI-E bus), etc.

It should be noted that, although the architecture of the above-mentioned computer device 500 only shows the processor 502, the memory 504, the network interface 506, the peripheral interface 508 and the bus 510, in the specific implementation process, the architecture of the computer device 500 may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the architecture of the above-mentioned computer device 500 may also only include the components necessary for implementing the embodiments of the present disclosure, and does not necessarily include all the components shown in the figure.

The embodiment of the present disclosure also provides a process configuration device. Figure 6 shows a schematic diagram of an exemplary device 600 provided by the embodiment of the present disclosure. As shown in Figure 6, the device 600 can be used to implement the method 400, and can further include the following modules.

The determination module 602 is configured to: determine the review node of the target process.

The acquisition module 604 is configured to: acquire one or more resources associated with the review node.

The creation module 606 is configured to: create one or more sub-work items for review for the review node based on the one or more resources, and fill in field values of at least some fields in the one or more sub-work items based on the one or more resources.

The process configuration method provided by the embodiment of the present disclosure automatically creates work items based on resources and fills in some fields, so that users do not need to manually create and fill in work items, and the operation is simpler and smoother.

In some embodiments, the acquisition module 604 is configured to:

Receive instructions to add sub-work items to review nodes based on resources;

Obtain a resource list from a resource library and display the resource list;

According to the adding instruction for one or more resources in the resource list, one or more resources associated with the review node are acquired.

In some embodiments, the device further comprises a display module configured to:

Displaying the one or more sub-work items on the page, and displaying a first configuration button on one side of the sub-work items;

In response to the first configuration button being triggered, displaying a visible condition configuration window of the sub-work item, the visible condition configuration window including a first configuration item for configuring a visible condition;

In response to receiving the configuration completion instruction, a visibility condition of the sub-work item is determined according to the configuration information of the first configuration item, so as to display the sub-work item when the visibility condition is met.

In some embodiments, the display module is configured to:

Displaying a second configuration button for configuring the sub-work item table view in the page;

In response to the second configuration button being triggered, displaying a table view configuration window of the one or more sub-work items, the table view configuration window comprising a table view preview area and a table column resource list located on one side of the table view preview area, the table view preview area comprising a preview image of the table view of the one or more sub-work items generated based on the currently selected table column, and the table column resource list comprising a plurality of table column resources for adding corresponding table columns in the table view of the one or more sub-work items;

In response to an adding instruction for a target table column resource among the plurality of table column resources, a preview table column corresponding to the target table column resource is added to the preview image.

In some embodiments, the table column resource list includes a review conclusion table column resource;

Display module, configured as:

In response to an instruction to add the review conclusion table column resource, a review conclusion preview table column corresponding to the review conclusion table column resource is added in the preview image, and the review conclusion preview table column includes a first preview table column corresponding to the review role, a second preview table column corresponding to the reviewer, a third preview table column corresponding to the review conclusion, a fourth preview table column corresponding to the review opinion, and a fifth preview table column corresponding to the review operation.

In some embodiments, the display module is configured to:

A third configuration button for configuring the personnel linkage rules of the sub-work item is displayed on the page;

In response to the third configuration button being triggered, displaying a personnel linkage rule configuration window of the one or more sub-work items, the personnel linkage rule configuration window including a second configuration item for configuring a linkage condition and a third configuration item for configuring a linkage condition group;

In response to receiving a configuration completion instruction, the personnel linkage rules of the sub-work items are determined according to the configuration information of the second configuration item and/or the third configuration item, and are used to add reviewers corresponding to the personnel linkage rules to the one or more sub-work items when the personnel linkage rules are met.

In some embodiments, the display module is configured to:

Displaying a fourth configuration button for configuring a node completion conclusion of the review node on the page;

In response to the fourth configuration button being triggered, displaying a node completion conclusion rule configuration window of the review node, the node completion conclusion rule configuration window including a fourth configuration item for configuring a node completion conclusion rule;

In response to receiving a configuration completion instruction, a node completion conclusion rule of the review node is determined according to the configuration information of the fourth configuration item, and is used to generate a node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is met.

In some embodiments, the display module is configured to:

Displaying a fifth configuration button for configuring the completion flow condition of the review node on the page;

In response to the fifth configuration button being triggered, displaying a completion flow condition configuration window of the review node, wherein the completion flow condition configuration window includes a fifth configuration item for configuring the completion flow condition of the review node;

In response to receiving the configuration completion instruction, a completion flow condition of the review node is determined according to the configuration information of the fifth configuration item, and is used to determine whether the review node can flow according to the completion flow condition.

For the convenience of description, the above device is described by dividing it into various modules according to its functions. Of course, when implementing the present disclosure, the functions of each module can be implemented in the same or multiple software and/or hardware.

The device of the above embodiment is used to implement the corresponding method 400 in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

The embodiment of the present disclosure also provides a process management device. Figure 7 shows a schematic diagram of an exemplary device 700 provided by the embodiment of the present disclosure. As shown in Figure 7, the device 700 can be used to implement the method 410, and can further include the following modules.

The acquisition module 702 is configured to: acquire configuration information of a target process configured by any embodiment or arrangement or combination of the method 400;

The display module 704 is configured to: in response to a viewing instruction for the review node of the target process, display one or more sub-work items of the review node, and fill in field values of at least some fields in the one or more sub-work items based on one or more resources associated with the review node.

The process management method provided by the embodiment of the present disclosure automatically creates work items based on resources and fills in some fields, so that users do not need to manually create and fill in work items, and the operation is simpler and smoother.

In some embodiments, the display module 704 is configured to:

Obtaining the visibility condition of the sub-work item;

One or more of the sub-work items that meet the visibility condition are displayed.

In some embodiments, the display module 704 is configured to:

Obtaining the personnel linkage rules of the sub-work item;

The personnel information satisfying the personnel linkage rule is displayed in the sub-work item.

In some embodiments, the one or more sub-work items include a review conclusion table column, and the review conclusion table column includes at least one of a first table column corresponding to the review role, a second table column corresponding to the review personnel, a third table column corresponding to the review conclusion, a fourth table column corresponding to the review opinion, and a fifth table column corresponding to the review operation.

In some embodiments, the display module 704 is configured to:

Acquire review operation information of the one or more sub-work items of the review node;

According to the review operation information, a node completion conclusion and a flow status of the review node are determined.

In some embodiments, the display module 704 is configured to:

Obtaining a node completion conclusion rule of the review node;

The node completion conclusion of the review node is determined according to the review operation information and the node completion conclusion rule.

In some embodiments, the display module 704 is configured to:

Obtaining the completion flow conditions and node flow status calculation rules of the review node;

The flow status of the review node is determined according to the review operation information, the node completion conclusion, the completion flow condition and the node flow status calculation rule.

For the convenience of description, the above device is described by dividing it into various modules according to its functions. Of course, when implementing the present disclosure, the functions of each module can be implemented in the same or multiple software and/or hardware.

The device of the above embodiment is used to implement the corresponding method 410 in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute method 400 or method 410 described in any of the above embodiments.

The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute method 400 or method 410 as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, method 400 or method 410, the present disclosure further provides a computer program product, which includes a computer program. In some embodiments, the computer program is executable by one or more processors so that the processors execute the described method 400 or method 410. Corresponding to the execution subject corresponding to each step in each embodiment of method 400 or method 410, the processor that executes the corresponding step may belong to the corresponding execution subject.

In some embodiments, the computer program product includes a program module for resolving operation conflicts, the program module including a module compiled into a binary instruction set based on a stack virtual machine (e.g., wasm) for being called by a terminal device and/or a module compiled into a static library for being called by a server.

The computer program product of the above embodiment is used to enable the processor to execute method 400 or method 410 as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be described in detail here.

Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. Based on the concept of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.

In addition, to simplify the description and discussion, and in order not to make the embodiments of the present disclosure difficult to understand, the known power/ground connections to the integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure will be implemented (that is, these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with changes in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

The embodiments of the present disclosure are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the scope of protection of the present disclosure.

Claims (20)

1. A process configuration method, comprising: Determine the review nodes of the target process; Obtaining one or more resources associated with the review node; Based on the one or more resources, one or more sub-work items for review are created for the review node, and at least part of the fields in the one or more sub-work items are filled with field values based on the one or more resources. 2. The method of claim 1, wherein obtaining one or more resources associated with the review node comprises: Receive instructions to add sub-work items to review nodes based on resources; Obtain a resource list from a resource library and display the resource list; According to the adding instruction for one or more resources in the resource list, one or more resources associated with the review node are acquired. 3. The method of claim 1, wherein the method further comprises: Displaying the one or more sub-work items on the page, and displaying a first configuration button on one side of the sub-work items; In response to the first configuration button being triggered, displaying a visible condition configuration window of the sub-work item, the visible condition configuration window including a first configuration item for configuring a visible condition; In response to receiving the configuration completion instruction, a visibility condition of the sub-work item is determined according to the configuration information of the first configuration item, so as to display the sub-work item when the visibility condition is met. 4. The method of claim 1, wherein the method further comprises: Displaying a second configuration button for configuring the sub-work item table view in the page; In response to the second configuration button being triggered, displaying a table view configuration window of the one or more sub-work items, the table view configuration window comprising a table view preview area and a table column resource list located on one side of the table view preview area, the table view preview area comprising a preview image of the table view of the one or more sub-work items generated based on the currently selected table column, and the table column resource list comprising a plurality of table column resources for adding corresponding table columns in the table view of the one or more sub-work items; In response to an adding instruction for a target table column resource among the plurality of table column resources, a preview table column corresponding to the target table column resource is added to the preview image. 5. The method according to claim 4, wherein the table column resource list includes a review conclusion table column resource; In response to an instruction to add a target table column resource among the plurality of table column resources, adding a preview table column corresponding to the target table column resource in the preview image includes: In response to an instruction to add the review conclusion table column resource, a review conclusion preview table column corresponding to the review conclusion table column resource is added in the preview image, and the review conclusion preview table column includes a first preview table column corresponding to the review role, a second preview table column corresponding to the reviewer, a third preview table column corresponding to the review conclusion, a fourth preview table column corresponding to the review opinion, and a fifth preview table column corresponding to the review operation. 6. The method of claim 1, wherein the method further comprises: A third configuration button for configuring the personnel linkage rules of the sub-work item is displayed on the page; In response to the third configuration button being triggered, displaying a personnel linkage rule configuration window of the one or more sub-work items, the personnel linkage rule configuration window including a second configuration item for configuring a linkage condition and a third configuration item for configuring a linkage condition group; In response to receiving a configuration completion instruction, the personnel linkage rules of the sub-work items are determined according to the configuration information of the second configuration item and/or the third configuration item, and are used to add reviewers corresponding to the personnel linkage rules to the one or more sub-work items when the personnel linkage rules are met. 7. The method of claim 1, wherein the method further comprises: Displaying a fourth configuration button for configuring a node completion conclusion of the review node on the page; In response to the fourth configuration button being triggered, displaying a node completion conclusion rule configuration window of the review node, the node completion conclusion rule configuration window including a fourth configuration item for configuring a node completion conclusion rule; In response to receiving a configuration completion instruction, a node completion conclusion rule of the review node is determined according to the configuration information of the fourth configuration item, and is used to generate a node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is met. 8. The method of claim 1, wherein the method further comprises: Displaying a fifth configuration button for configuring the completion flow condition of the review node on the page; In response to the fifth configuration button being triggered, displaying a completion flow condition configuration window of the review node, wherein the completion flow condition configuration window includes a fifth configuration item for configuring the completion flow condition of the review node; In response to receiving the configuration completion instruction, a completion flow condition of the review node is determined according to the configuration information of the fifth configuration item, and is used to determine whether the review node can flow according to the completion flow condition. 9. A process management method, comprising: Obtaining configuration information of a target process configured by the method according to any one of claims 1 to 8; In response to a viewing instruction for a review node of the target process, one or more sub-work items of the review node are displayed, and at least some fields of the one or more sub-work items are filled with field values based on one or more resources associated with the review node. 10. The method of claim 9, wherein displaying one or more sub-work items of the review node comprises: Obtaining the visibility condition of the sub-work item; One or more of the sub-work items that meet the visibility condition are displayed. 11. The method of claim 9, wherein displaying one or more sub-work items of the review node comprises: Obtaining the personnel linkage rules of the sub-work item; The personnel information satisfying the personnel linkage rule is displayed in the sub-work item. 12. A method as claimed in claim 9, wherein the one or more sub-work items include a review conclusion table column, and the review conclusion table column includes at least one of a first table column corresponding to the review role, a second table column corresponding to the reviewer, a third table column corresponding to the review conclusion, a fourth table column corresponding to the review opinion, and a fifth table column corresponding to the review operation. 13. The method of claim 12, wherein the method further comprises: Acquire review operation information of the one or more sub-work items of the review node; According to the review operation information, a node completion conclusion and a flow status of the review node are determined. 14. The method of claim 13, wherein determining the node completion conclusion and flow status of the review node according to the review operation information comprises: Obtaining a node completion conclusion rule of the review node; The node completion conclusion of the review node is determined according to the review operation information and the node completion conclusion rule. 15. The method of claim 14, wherein determining the node completion conclusion and flow status of the review node according to the review operation information comprises: Obtaining the completion flow conditions and node flow status calculation rules of the review node; The flow status of the review node is determined according to the review operation information, the node completion conclusion, the completion flow condition and the node flow status calculation rule. 16. A process configuration device, comprising: The determination module is configured to: determine the review node of the target process. The acquisition module is configured to: acquire one or more resources associated with the review node. The creation module is configured to: create one or more sub-work items for review for the review node based on the one or more resources, and fill in field values of at least some fields in the one or more sub-work items based on the one or more resources. 17. A process management device, comprising: An acquisition module is configured to: acquire configuration information of a target process configured by the method according to any one of claims 1 to 8; The display module is configured to: in response to a viewing instruction for a review node of the target process, display one or more sub-work items of the review node, and fill in field values of at least some fields in the one or more sub-work items based on one or more resources associated with the review node. 18. A computer device comprising one or more processors, a memory; and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, and the programs include instructions for executing the method according to any one of claims 1 to 15. 19. A non-volatile computer-readable storage medium containing a computer program, which, when executed by one or more processors, causes the processors to perform the method of any one of claims 1 to 15. 20. A computer program product, comprising one or more computer programs, wherein the one or more computer programs implement the steps of the method according to any one of claims 1 to 15 when executed by one or more processors.