Process configuration method, process management method and related device

Abstract

Provided in the present disclosure are a process configuration method, a process management method and a related device. The process configuration method comprises: determining a review node of a target process; acquiring one or more resources associated with the review node; and on the basis of the one or more resources, creating for the review node one or more work sub-items for review, wherein at least some fields in the one or more work sub-items are filled with field values on the basis of the one or more resources.

Description

Process configuration and management method and related device

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to the Chinese patent application No. 202410692870.3, filed on May 30, 2024, and entitled "Process configuration and management method and related device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present disclosure relates to the technical field of computer, and in particular, to a process configuration and management method and related device. BACKGROUND

[0004] With the continuous development of Internet technology, many work can be completed intelligently. For example, some process management can be performed on process transactions or objects through management software. SUMMARY

[0005] The present disclosure provides a process configuration and management method and related device.

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

[0007] determining an evaluation node of a target process;

[0008] obtaining one or more resources associated with the evaluation node;

[0009] creating one or more sub-work items for evaluation for the evaluation node based on the one or more resources, at least part of the fields in the one or more sub-work items being filled with field values based on the one or more resources.

[0010] In a second aspect, the present disclosure provides a process management method, comprising:

[0011] obtaining configuration information of a target process configured by using the method of the first aspect;

[0012] in response to a viewing instruction for an evaluation node of the target process, displaying one or more sub-work items of the evaluation node, at least part of the fields in the one or more sub-work items being filled with field values based on one or more resources associated with the evaluation node.

[0013] In a third aspect, the present disclosure provides a process configuration device, comprising:

[0014] a determining module configured to determine an evaluation node of a target process.

[0015] The obtaining module is configured to obtain one or more resources associated with the review node.

[0016] The creating module is configured to create one or more sub-work items for review for the review node based on the one or more resources, at least part of fields in the one or more sub-work items being filled with field values based on the one or more resources.

[0017] In a fourth aspect, the present disclosure provides a process management apparatus, comprising:

[0018] The obtaining module is configured to obtain configuration information of a target process configured by using the method in the first aspect.

[0019] The display module is configured to display one or more sub-work items of the review node in response to a viewing instruction for the review node of the target process, at least part of fields in the one or more sub-work items being filled with field values based on one or more resources associated with the review node.

[0020] In a fifth aspect, the present disclosure provides 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 comprise instructions for performing the method in the first aspect.

[0021] In a sixth aspect, the present disclosure provides a non-transitory computer-readable storage medium containing a computer program, which, when executed by one or more processors, causes the processors to perform the method in the first aspect.

[0022] In a seventh aspect, the present disclosure provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the method in the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the present disclosure or the related art, the following will briefly introduce the drawings needed to be used in the embodiments or the related art description. Obviously, the drawings in the following description are only embodiments of the present disclosure, and for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

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

[0025] FIG. 1B shows a schematic diagram of an exemplary work breakdown structure (WBS) according to an embodiment of the present disclosure.

[0026] FIG. 2A shows a schematic diagram of an example page according to an embodiment of the present disclosure.

[0027] FIG. 2B shows another schematic diagram of an example page according to an embodiment of the present disclosure.

[0028] FIG. 2C shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0029] FIG. 2D shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0030] FIG. 2E shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0031] FIG. 2F shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0032] FIG. 2G shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0033] FIG. 2H shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0034] FIG. 2I shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0035] FIG. 2J shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0036] FIG. 2K shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0037] FIG. 2L shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0038] FIG. 3A shows a schematic diagram of an example page according to an embodiment of the present disclosure.

[0039] FIG. 3B shows another schematic diagram of an example page according to an embodiment of the present disclosure.

[0040] FIG. 3C shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0041] FIG. 3D shows yet another schematic diagram of an example page according to an embodiment of the present disclosure.

[0042] FIG. 4A shows a flow diagram of an example method provided by an embodiment of the present disclosure.

[0043] FIG. 4B shows a flow diagram of another example method provided by an embodiment of the present disclosure.

[0044] FIG. 5 shows a hardware structure diagram of an example computer device provided by an embodiment of the present disclosure.

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

[0046] FIG. 7 shows a schematic diagram of an exemplary device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0047] As described above, many works can be completed intelligently. However, the inventors of the present disclosure find that in the related art, it is inconvenient to use when managing the review nodes in the process by using management software.

[0048] For the purpose, technical solutions and advantages of the present disclosure to be clearer, below, in combination with specific embodiments and with reference to the drawings, the present disclosure is further described in detail.

[0049] 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 as the usual meaning understood by those skilled in the art to which the present disclosure belongs. The terms "first", "second" and the like used in the embodiments of the present disclosure do not represent any order, number or importance, but are only used to distinguish different components. The terms "include" or "contain" and the like mean that the elements or objects before the term cover the elements or objects listed after the term and their equivalents, and do not exclude other elements or objects. The terms "connect" or "connected" and the like are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to represent relative positional relationships, and when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0050] It can be understood that before using the technical solutions of various embodiments of the present disclosure, the user will be informed of the type, use range, use scenario, etc. of the personal information involved by appropriate means, and the authorization of the user will be obtained.

[0051] For example, in response to receiving the user's active request, the user is sent prompt information to explicitly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can choose whether to provide personal information to the software or hardware such as electronic devices, application programs, servers or storage media that perform the technical solutions of the present disclosure according to the prompt information.

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

[0053] It can be understood that the above notification and user authorization obtaining process is only illustrative and does not limit the implementation of the present disclosure, and other manners meeting the relevant laws and regulations can also be applied to the implementation of the present disclosure.

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

[0055] As shown in FIG. 1A, the system 100 can be used to implement online or offline project management functions, and can include terminal devices 102A, 102B, a server 106 and a database server 108. The terminal devices 102A, 102B and the server 106 and the database server 108 can include a medium (for example, a network) providing a communication link therebetween. The network can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

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

[0057] The terminal devices 102A, 102B herein can be hardware or software. When the terminal devices 102A, 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 (Laptop) and desktop computers (PC), etc. When the terminal devices 102A, 102B are software, they can be installed in the above-mentioned electronic devices. They can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module. No specific limitation is made herein.

[0058] The service server 106 can be a server providing various services, such as a background server providing support for various applications displayed on the terminal devices 102A and 102B. The database server 108 can also be a database server providing various services. It can be understood that, in the case where the service server 106 can implement the related functions of the database server 108, the database server 108 can not be arranged in the system 100.

[0059] The service server 106 and the database server 108 herein can be hardware or software. When they are hardware, they can be implemented as a distributed server cluster composed of multiple servers or as a single server. When they are software, they can be implemented as multiple software or software modules (for example, used to provide distributed services) or as a single software or software module. No specific limitation is made herein.

[0060] It should be noted that the method for editing a document provided by the embodiments of the present disclosure can be executed by the service server 106. It should be understood that the number of terminal devices, users, servers, and database servers in FIG. 1A is merely illustrative. According to the implementation needs, there can be any number of terminal devices, users, servers, and database servers.

[0061] In some embodiments, the terminal devices 102A and 102B can be installed with a project management application or software, and the users 104A and 104B can use the application or software installed in the terminal devices 102A and 102B to perform project management. For example, setting a work item related to a project process and a process node, and the like. As an optional embodiment, the user 104A can be an administrator of a project, used to manage the entire process of the project, and the user 104B can be a participant of the project. After the user 104A establishes the process, the user 104B can view the process and operate according to the process.

[0062] One type of project management is 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 be normally transferred.

[0063] Generally, the integrated product development process can go through multiple different types of review nodes, such as peer review, technical review, decision review, and the like. Each review node needs relevant personnel to participate. Therefore, the project management software needs a review management function, which conforms to the user's usage habits and greatly improves the user experience.

[0064] The review process usually needs a decision maker to give a review conclusion for the content to be reviewed according to the review dimension and reference decision reference resources, and the review conclusion affects the project process or state.

[0065] FIG. IB shows a schematic diagram of an example work breakdown structure (WBS) according to an embodiment of the present disclosure.

[0066] As shown in FIG. IB, the project development process work item can be broken down into a plurality of process nodes, which have a certain execution order. Among them, the feasibility analysis node, the peer review node, the technical review node, the decision review node and the like can be review nodes, and the project process can be transferred to the next node only after passing the review process.

[0067] As shown in FIG. IB, the feasibility analysis node is further associated with a deliverable work item, and the deliverable work item and the project development process work item have a parent-child relationship. Therefore, 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 deliverable of the feasibility analysis node (for example, a project feasibility report), such as submitting the feasibility report, reviewing the report, storing the feasibility report after passing the review, so that the review node is completed and the project process is transferred to the next node.

[0068] As shown in FIG. IB, the decision review node is further associated with a review work item, and the decision review work item and the project development process work item have a parent-child relationship. 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.

[0069] As shown in FIG. IB, the decision review node is further associated with a review work item, and the decision review work item and the project development process work item have a parent-child relationship. 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.

[0070] The peer review node and the technical review node are similar in structure to the decision review node (generally not including the decision sub-node), and will not be described here.

[0071] As can be seen, due to the complexity of the review process, in order to enable the review process to proceed smoothly, the project management software needs to provide the user with the function of conveniently completing the decision process, but the project management software of the related technology more or less has certain problems in use.

[0072] In view of this, one aspect of the embodiments of the present disclosure provides a process configuration method.

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

[0074] As shown in FIG. 2A, in some embodiments, the user 104A can open a collaborative office type software by using the terminal device 102A, and then the page 200 can be displayed in the terminal device 102A. Exemplarily, the first area 200A of the page 200 can display a project process diagram, which further includes a plurality of process nodes arranged and connected according to the process execution order.

[0075] As shown in FIG. 2A, exemplarily, 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. Exemplarily, 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 FIG. 2B.

[0076] Optionally, the user 104A clicks the configuration button 204A, and can send an instruction to the terminal device 102A to add a sub-work item to the review node based on a 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 FIG. 2C. Optionally, the terminal device 102A can obtain a resource list from a resource library and display the resource list, as shown in FIG. 2C. 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 the resources.

[0077] As shown in FIG. 2C, optionally, a search box can be included in the window 206 for searching the desired resource by keyword. Optionally, the window 206 can further include a filter control, and the user 104A can trigger the filter control, and a pop-up window can be displayed on one side of the filter control, which can be used to set the filtering conditions, so that the resources in the resource list can be filtered based on the filtering conditions (e.g., classification conditions, stage conditions, etc.). In this way, the user 104A can conveniently find the resources to be added.

[0078] As shown in FIG. 2C, optionally, a check box is provided in front of each resource in the resource list, and the user 104A can select the desired added resource by checking the check box of the corresponding resource. As shown in FIG. 2C, for example, 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, and an adding instruction for one or more resources (e.g., resources 2, 4, and 7) in the resource list can be sent to the terminal device 102A. According to the adding instruction, the terminal device 102A can obtain one or more resources (e.g., resources 2, 4, and 7) associated with the review node.

[0079] Then, 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, and 7), and at least part of the fields (e.g., review element fields) in the one or more sub-work items are filled with field values based on the one or more resources. In this way, some sub-work items can be pre-configured for the review node in advance, so that manual addition is not required. It can be understood that the matching relationship between the resource and the sub-work item can be pre-configured, and subsequently only the resource needs to be imported to automatically create the sub-work item and fill at least part of the field values.

[0080] In some embodiments, after adding the sub-work item based on the resource, the added sub-work item can be displayed in the page, and a first configuration button 2042-2046 is displayed on one side of the sub-work item, as shown in FIG. 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 that the sub-work item corresponds to what review element.

[0081] The first configuration buttons 2042-2046 are used to edit the added sub-work items, and can also be used to configure the visibility conditions of the added sub-work items. For example, in response to the first configuration button being triggered (e.g., the user 104A clicks the button 2042), a visibility condition configuration window 208 of the sub-work item is displayed, as shown in FIG. 2E. Optionally, the visibility condition configuration window 208 can include first configuration items 2082, 2084 for configuring the visibility conditions. In some embodiments, after the window 208 is opened, the default visibility button is selected by default, and after the condition-satisfied visibility button is selected, a configuration condition area is displayed in the window 208, as shown in FIG. 2E. For example, the first configuration items 2082, 2084 in the window 208 can be generated by the user 104A by triggering an add condition control 2086 in the window 208. Optionally, the optional range of the leftmost option of the first configuration items 2082, 2084 can be a field of the parent work item to which the sub-work item belongs (e.g., a review element of the parent work item), a role (e.g., a reviewer of the parent work item), and the like. The middle option of the first configuration items 2082, 2084 can be an operator, and the rightmost option can be the content corresponding to the leftmost option. The “and” or “or” relationship between multiple conditions can also be set, or the relationship between the conditions can be set by inputting a condition formula. For example, as shown in FIG. 2E, the currently set condition is that when the review element of the parent work item includes “Is the market segment large enough?” and the reviewer of the parent work item includes Zhang San, the sub-work item corresponding to the review element “Is the demand reasonable?” can be displayed.

[0082] In response to receiving the configuration completion instruction, the terminal device 102A determines the visibility condition of the sub-work item according to the configuration information of the first configuration item, for displaying the sub-work item when the visibility condition is satisfied. In this way, by setting the visibility condition, the sub-work item can be displayed when the condition is satisfied, and the sub-work item can not be displayed when the condition is not satisfied, so that the user 104A can flexibly configure the review process and use conveniently.

[0083] 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 can retrieve the sub-work item.

[0084] Referring back to FIG. 2B, optionally, a second configuration button 204B for configuring the sub-task table view can also be displayed in the second area 200B of the page 200. Since a task includes multiple fields, in order to fully present the content of a sub-task, a table form of a schedule can be used to display the task. Also, since the fields required by different review nodes or review processes can be different, the effect of the final presented schedule can be adjusted by configuring the sub-task table view.

[0085] Exemplarily, in response to the second configuration button being triggered (e.g., the user clicks the button 204B), a table view configuration window 210 of the one or more sub-tasks can be displayed in the page 200, as shown in FIG. 2F. 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 210A, the table view preview area 210A includes a preview of the table view of the one or more sub-tasks generated based on the currently selected table column (as shown in FIG. 2F), and the table column resource list includes multiple table column resources for adding corresponding table columns in the table view of the one or more sub-tasks. Optionally, as shown in FIG. 2F, the table column resources include resources of table columns for filling in text, such as name, description, etc. As shown in FIG. 2F, the table column resources can also include resources for selecting field values, such as priority, requirement status, review conclusion, label, etc.

[0086] The table column resources in the table column resource list area 210B can all be added to the table view preview area 210A to update the preview, and the table view on the application side can be updated based on the preview. Therefore, in response to an adding instruction (e.g., long-pressing a target table column resource in the table column resource list area 210B 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 in the preview, so as to update the preview, and the updated preview is consistent with the table view presented on the application side (including consistent in arrangement format and specific content).

[0087] In this way, the user can conveniently 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 habits of the user when presenting the schedule.

[0088] In some embodiments, as shown in FIG. 2F, the table column resource list includes an evaluation conclusion table column resource 2102; in response to an adding instruction (e.g., dragging the evaluation conclusion table column resource 2102 to the right of the evaluation element preview table column) for the evaluation conclusion table column resource 2102, an evaluation conclusion preview table column 2104 corresponding to the evaluation conclusion table column resource is added in the preview diagram, and the evaluation conclusion preview table column includes a first preview table column 2104A corresponding to an evaluation role, a second preview table column 2104B corresponding to an evaluation staff, a third preview table column 2104C corresponding to an evaluation conclusion, a fourth preview table column 2104D corresponding to an evaluation opinion, and a fifth preview table column 2104E corresponding to an evaluation operation, as shown in FIG. 2G. In some embodiments, the user 104A can also configure an associated node for each evaluation conclusion in the preview diagram, so that the relevant node is also associated with the corresponding evaluation conclusion table column, and there is no need to separately set the node.

[0089] In this way, the user 104A conveniently adds the evaluation conclusion table column in the table view, and the subsequent user 104B can give his own evaluation conclusion (e.g., pass, fail, or conditional pass) for each evaluation element sub-work item based on the evaluation conclusion table column.

[0090] As shown in FIG. 2F, the window 210 also includes a basic setting tab, and by clicking the tab, the content of the window 210 can be switched to display the configuration items corresponding to the basic setting, which can include various table view templates. The user 104A can select any template to generate a corresponding table view, so that there is no need to configure by himself, and the use is convenient. Alternatively, the user 104A can first select a template to generate a table view, and then switch to the table setting to further adjust the table view template.

[0091] Returning to FIG. 2B, in some embodiments, the page 200 can also display a third configuration button 204C for configuring a staff linkage rule of the sub-work item. Alternatively, in response to a hovering instruction (e.g., moving the cursor over the third configuration button 204C and staying) for the third configuration button 204C, a prompt information “if the rule is configured, the configuration of all node leaders of the sub-work item will no longer take effect, and if the rule is not configured, the node leader configuration of the sub-work item will take effect” can be displayed, so as to prompt the user 104A that once the rule is configured, the original configuration of the leader for each sub-work item will not take effect, and the automatically added leader to meet the rule will be the leader of the sub-work item.

[0092] In response to the third configuration button 204C being triggered, a personnel linkage rule configuration window 212 of the one or more sub-tasks can be displayed, as shown in FIG. 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.

[0093] As shown in FIG. 2H, the user 104A can add a condition group by clicking the third configuration item 2124. The second configuration item 2122 for configuring linkage conditions is further displayed in the condition group configuration area. In each condition group, the leftmost option is the field of the sub-task, the operator, and the rightmost option is the content configured by the user.

[0094] After setting the conditions, the result of the rule can be configured. The left drop-down box can be selected from the roles on the parent task of the sub-task, which can be multiple selected. The right drop-down box can be selected from the designated node owners of the designated process template on the sub-task, which can be single selected.

[0095] In response to receiving a configuration completion instruction (e.g., the user 104A clicking the OK button in the lower right corner of the window 212), the personnel linkage rule of the sub-task is determined according to the configuration information of the second configuration item 2122 and / or the third configuration item 2124, for adding the review personnel corresponding to the personnel linkage rule to the one or more sub-tasks when the personnel linkage rule is met.

[0096] For example, as shown in FIG. 2H, the current created personnel linkage rule is that when the sub-task belongs to the market field and the development field, the director and the product manager of the parent task will be synchronized as the R&D representative / node owner in the sub-task.

[0097] In this way, through the setting of the personnel linkage rule, it is avoided that some review processes miss important owners, and it is ensured that the review process is more perfect.

[0098] Optionally, the above-mentioned editing record can also be recorded in the operation log for the user to trace back or retrieve.

[0099] In some embodiments, a pruning control can also be added for each sub-task, which is used for the user 104B to delete unnecessary sub-tasks (especially review element sub-tasks) on the application side, so as to avoid unnecessary review elements appearing in the review process. When configuring the pruning control, it can be configured for each sub-task, and the pruning permission (i.e., what role can prune the sub-task) can be configured. After configuring the pruning control, the pruning control can be displayed on the side of the corresponding sub-task on the application side, so that the user B can use the pruning control to delete unnecessary sub-tasks in the review process.

[0100] Returning to FIG. 2A, the second area 200B of the page 200 displays the configuration items corresponding to the node information tab 202A. Under the page corresponding to the node information tab 202A, the fields of the review node can be customized, and whether and how to display the fields can be configured. Optionally, the system default node fields can include node name, node ID, node owner, node schedule, node estimated score, and node actual working hours.

[0101] In some embodiments, as shown in FIG. 2A, the node completion conclusion configuration item 2142 and the node completion opinion configuration item 2144 can be displayed in the page 200, and the user 104A can configure the node completion conclusion and the node completion opinion attributes of 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 can be considered completed only when the node completion conclusion and the node completion opinion are filled in.

[0102] Optionally, after the node completion conclusion configuration item 2142 is checked, the application side needs to display the filling control of the node completion conclusion, and needs to fill in the node completion conclusion (the completion conclusion of the node as a whole) and the review conclusion of the node owner corresponding to each work item in the filling control, wherein the review conclusion of the node owner corresponding to each work item can only be modified and filled in by the node owner himself, and the node completion conclusion can be manually filled in by the node authorized role. The node completion conclusion and the review conclusion filled in by the owner and others can be displayed in the page of the application side. In some embodiments, the node completion conclusion can be summarized according to the node completion conclusion rule. The user 104A can configure the node completion conclusion rule.

[0103] The options corresponding to the conclusion can be configured, and at least one option needs to be reserved. Optionally, the default options of the conclusion can include pass, fail, and conditional pass, and the user 104A can view the configured options of the conclusion and modify these options through the option configuration item 2146.

[0104] Optionally, after the node completion opinion configuration item 2144 is checked, the application side needs to display the filling control of the node completion opinion, and needs to fill in the node completion opinion (the completion opinion of the node as a whole) and the review opinion of the node owner corresponding to each work item in the filling control, and the opinion can be in text format. Among them, the review opinion of the node owner corresponding to each work item can only be modified and filled in by the node owner himself, and the node completion opinion can be manually filled in by the node authorized role. The node completion opinion and the review opinion filled in by the owner and others can be displayed in the page of the application side.

[0105] As shown in FIG. 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 by default manually filled by the node authorized role. In some embodiments, in response to the fourth configuration button 2148 being triggered, a node completion conclusion rule configuration window 216 of the review node can also be displayed in the page 200, as shown in FIG. 2I. Optionally, the node completion conclusion rule configuration window 216 includes fourth configuration items 2162, 2164 for configuring the node completion conclusion rule. It can be understood that in the initial state, the fourth configuration items 2162, 2164 can not be displayed in the window 216, and the user 104A can add the fourth configuration items by clicking the add rule button to complete the rule configuration.

[0106] Exemplarily, as shown in FIG. 2I, the fourth configuration items 2162, 2164 include the condition of the rule and the rule result when the condition is met. The rule condition includes five options from left to right, the first option is single selection, and the optional range is more than or less than; the second option is to fill in a number; the third option is single selection, and the optional range is a number or a percentage; the fourth option is used to select the reviewer (or the responsible person) role, which can be multiple selection, and the drop-down menu can include all the personnel related to the review node; the fifth option is used to select the completion conclusion, which can be multiple selection, as described above, the option can be configured, and generally includes pass, fail, and conditional pass. The rule result when the condition is met can be pass or fail.

[0107] For example, taking rule 1 configured in FIG. 2I as an example, the rule is that when the total number of review conclusions of product managers or R&D personnel is more than 3, the node completion conclusion is pass. Optionally, if a person's role is both a product manager and an R&D personnel, the count is only 1.

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

[0109] In response to receiving a configuration completion instruction, determining a node completion conclusion rule of the review node according to the configuration information of the fourth configuration items, for generating a node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is met.

[0110] Exemplarily, after the above rules are configured, on the application side, when all the node responsible persons (e.g., the responsible person or the reviewer corresponding to each sub-work item) corresponding to the review node submit the review conclusion, the above rules are triggered to perform the summary calculation on the review conclusion, and if the node responsible person updates the review conclusion, the recalculation is triggered.

[0111] As shown in FIG. 2I, optionally, the prompt information 2166 can also be displayed in the window 216, for prompting the user the consequence of the rule configuration (e.g., “when all people fill in the review conclusion, the following rules are executed for summary”), the order of the executed rules (e.g., “the rules are effective from top to bottom”) and the configuration method (e.g., “the order can be adjusted by dragging”).

[0112] Correspondingly, on the application side, when the review conclusion summary calculation is triggered, the rules can be sequentially judged according to the order of the rules configured in the window 216, and when the first hit rule appears, the subsequent rules are no longer matched.

[0113] In addition, optionally, the options can also be verified. For example, when the name of the node completion conclusion option in the rule is edited, the rule is synchronously updated; when the node completion conclusion option in the rule is all deleted, the rule is not effective, and an error is given, and the user is prompted when saving.

[0114] In some embodiments, in addition to the above configuration of the node completion conclusion and the node completion opinion, the configuration can also be performed in the general node information page, and the selected node can be selected in the drop-down menu of the node name configuration item, and the optional range is all the nodes in the work item process template, and the same name node appears only once (i.e., if the node has been configured with the node completion conclusion and the node completion opinion, the node is no longer displayed in the drop-down menu), and the node is located according to the name.

[0115] Returning to FIG. 2A, optionally, the second area 200B of the page 200 can also include a node flow label 202C, and the user 104A can click the node flow label 202C to display the configuration items related to the state flow of the review node in the second area 200B of the page 200, as shown in FIG. 2J. Optionally, the second area 200B can include a fifth configuration button 218 for configuring the completion flow condition of the review node.

[0116] Optionally, in response to the fifth configuration button 218 being triggered, a completion flow condition configuration window 220 of the review node can be displayed in the page 200, as shown in FIG. 2K. Optionally, the completion flow condition configuration window 220 can include fifth configuration items 2202 for configuring the completion flow condition of the review node. As shown in FIG. 2K, the fifth configuration items 2202 can be created in the window 220 by clicking the Add Condition button, and each fifth configuration item 2202 can include three options, the leftmost option for selecting a field of a sub-work item under the review node, the middle option for selecting a logical operator, and the rightmost option for selecting a specific content.

[0117] In response to receiving a configuration completion instruction (e.g., the user 104A completes the configuration of each option and clicks the OK button in the lower right corner of the window 220), the completion flow condition of the review node is determined according to the configuration information of the fifth configuration items, for determining whether the review node can flow according to the completion flow condition.

[0118] The so-called whether can flow refers to whether the state of the review node can change. In some embodiments, as shown in FIG. 2J, the user can first configure the node flow condition and then configure the completion flow condition, wherein the checked configuration item in the node flow condition requires the corresponding review field to be completed, and when the node flow condition is met, the completion flow condition (e.g., the review form field contains the to-be-confirmed technical solution and the review personnel contains Zhang San) is further met, and it is considered that the state of the review node meets the condition of change.

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

[0120] 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 FIG. 2L. Optionally, the node flow state configuration window 224 includes sixth configuration items 2242 for configuring the node flow state calculation rule of the review node.

[0121] As shown in Figure 2L, the workflow status of a review node can exemplarily include three states: Not Started, In Progress, and Completed. Each state can be configured with corresponding node workflow status calculation rules, and these rules can be configured in window 224. Optionally, as shown in Figure 2L, each state corresponds to a sixth configuration item 2242. When each sixth configuration item 2242 is triggered, a dropdown list is generated for that state, containing specific options for configuring the node workflow status calculation rules. For example, as shown in Figure 2L, the dropdown list 2244 for the Completed state is displayed in window 224. The right side of the dropdown list 2244 includes information about the conditions currently being configured, and the left side includes conditions that have been configured. When any of the configured conditions on the left side of the dropdown list 2244 is selected, the selected condition is highlighted, and the right side of the dropdown list 2244 can display the specific information of that condition, which can be modified by changing this information. As shown in Figure 2L, optionally, a new node flow state and its calculation rules can be created by adding a set of state and condition buttons.

[0122] In response to receiving a configuration completion instruction (e.g., 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 rules.

[0123] For example, as shown in Figure 2L, when the review node is in the project initiation stage and the node leader does not include Zhang San, the workflow status of the review node is completed.

[0124] Optionally, a fallback rule can be set, which means that when no node transition status calculation rule is configured, the node's status is calculated as "completed" upon completion.

[0125] In some embodiments, overall project status calculation rules can also be configured to calculate the overall project status. Optionally, these status calculation rules can be determined based on the flow status of each node. The method of setting the status calculation rules is similar to the configuration method of the node flow status calculation rules, and will not be described again here.

[0126] In some embodiments, user 104A can also configure the buttons (buttons with corresponding text) corresponding to the review operations (including pass, fail, conditional pass, etc.), for example, configuring the button name, button style, button events (events triggered after the button is clicked, such as configuration form, data assignment, completion node, etc.).

[0127] After configuring using the methods described above, workflow management can be performed based on the configured information. For example, user 104B can use terminal device 102B to open collaborative office software to manage project workflows.

[0128] Figure 3A shows a schematic diagram of an exemplary page 300 according to an embodiment of the present disclosure.

[0129] As shown in Figure 3A, for example, user 104B can use terminal device 102B to open collaborative office software and obtain the configuration information of the target process (current project) configured using the aforementioned process configuration method. Then, page 300 can be displayed on terminal device 102B. For example, as shown in Figure 3A, page 300 can display the project's flowchart, which further includes multiple process nodes arranged and connected according to the process execution order.

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

[0131] In some embodiments, in response to a viewing instruction for a review node of the target process (e.g., double-clicking the review node in the flowchart), the one or more sub-work items of the review node are displayed, as shown in FIG3B.

[0132] For example, Figure 3B shows multiple sub-work items corresponding to the review elements of review node 2. At least some of these sub-work items may be created based on one or more resources associated with review node 2, and the field values ​​of at least some of their fields 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 may be filled in based on resources.

[0133] As mentioned earlier, review elements 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, and so on. In the review process, reviewers or responsible persons can conduct reviews around these review elements and give review conclusions based on the information obtained during the review process. Therefore, review elements, deliverables to be reviewed, and review issues can all be independent sub-work items under a review node; this description focuses only on the sub-work items corresponding to review elements.

[0134] In some embodiments, in response to the deletion of the review node, the parent-child association between the one or more sub-work items and the review node is terminated, and the state of the one or more sub-work items remains unchanged; in response to the restoration of the review node, the one or more sub-work items are automatically re-associated with the review node in a parent-child relationship. This ensures that sub-work items are not deleted after the review node is deleted, and that the original sub-work items are automatically associated with the review node when it is recreated, thus eliminating the need to recreate the already created sub-work items.

[0135] In some embodiments, when displaying one or more sub-work items of the review node, the visibility conditions of the sub-work items can be obtained (refer to FIG. 2E). Then, based on the visibility conditions, one or more sub-work items that satisfy the visibility conditions are displayed. In this way, sub-work items that satisfy the visibility conditions are displayed, while sub-work items that do not satisfy the visibility conditions are hidden. This saves page space and avoids users spending time on sub-work items that do not need to be reviewed, thereby improving work efficiency.

[0136] In some embodiments, when displaying one or more sub-work items of the review node, the personnel linkage rules of the sub-work items can be obtained, and then personnel information that meets the personnel linkage rules can be displayed in the sub-work items.

[0137] Referring to Figure 2H, for existing personnel linkage rules, all condition groups are executed according to the order of the personnel linkage rules corresponding to the sub-item. Execution stops after matching the first condition group, and the field value of the reviewer of the parent item of the sub-item that meets the conditions is filled into the node leader of the sub-item. If the node leader of the sub-item does not match any personnel linkage rules, the node leader is matched according to the node leader rules of the sub-item itself.

[0138] Optionally, after a sub-item is successfully created, modifying the information of either the parent or sub-item will not automatically change the node owner of the sub-item; at the same time, modifying the node owner of a sub-item will not affect the role of the parent item.

[0139] In some embodiments, the one or more sub-work items include a review conclusion table column, which 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 comments, and a fifth table column corresponding to the review operation.

[0140] As shown in Figure 3B, exemplarily, the first-level heading of the review conclusion table column can be "Review Conclusion". The review conclusion table column has five second-level headings. The first column heading can be "Review Role", with its field value being the reviewer's role name in the parent work item. If multiple role names exist, they can be displayed; if no role exists, a "-" can be displayed. The second column heading can be "Reviewer", with its field value being the configured person in charge or node person in charge, with each person in charge displayed on one row. The third column heading can be "Review Conclusion", with its field value being the node completion conclusion configured for the node, and the current user's editing permissions can be determined according to node logic. The fourth column heading can be "Review Comments", with its field value being the node completion comments configured for the node, and the current user's editing permissions can be determined according to node logic. The fifth column heading can be "Review Operation", with its field value being the node completion operation button configured for the node, and the current user's editing permissions can be determined according to node logic. Rows without editing permissions can display the current process status of the review node. Optionally, the review role, reviewer, review conclusion, and review comments can also be filtered.

[0141] As mentioned earlier, trimming controls can also be configured for resources or sub-work items to delete unwanted resources or sub-work items. Therefore, in some embodiments, a checkbox can be displayed on the far left of each sub-work item. When the user checks the corresponding sub-work item and clicks the delete button, the sub-work item can be deleted.

[0142] Figure 3C shows another schematic diagram of an exemplary page 310 according to an embodiment of the present disclosure.

[0143] As shown in Figure 3C, review node 2 corresponds to parent work item 312, which includes review element sub-work items and review issue sub-work items. The review element sub-work items and review issue 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 resources from the resource library to automatically create sub-work items and establish a parent-child relationship with the current parent work item.

[0144] In some embodiments, referring to Figure 3C, if the review node is in progress, the operation buttons (pass, fail, conditionally pass) for the completed node in the parent work item 312 can be displayed on page 310. Only authorized roles can perform these operations; unauthorized roles can only view them, preventing accidental operation by unauthorized roles. If the review node is not started or has been completed, the operation buttons (pass, fail, conditionally pass) in the parent work item 312 may not be displayed on page 310, preventing accidental user operation due to inappropriate button display. When an authorized role clicks the corresponding operation button, a prompt message "Data xx modified to xx, this node is complete" is displayed, indicating successful operation to the user. In some embodiments, in response to the operation button being clicked, the node flow conditions configured in the aforementioned embodiments can be obtained first, and the node flow conditions can be verified (including whether the selected required fields have been filled in and the configured node flow conditions). If they are not met, a required field identifier or a prompt "Does not meet the node flow 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 state is not changed, and the node state is not changed.

[0145] In some embodiments, if the review process of a review node involves multiple participants and the node status is in progress, in response to user 104B (the current user) being the node leader and user 104B not operating the node completion button in the parent work item 312, the node completion button in the parent work item 312 is displayed as shown in Figure 3C 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 not operating, the node flow conditions configured in the aforementioned embodiments can be obtained first, and the node flow conditions can be verified (including whether the selected required fields have been filled and the configured node flow conditions). If they are not met, a required field identifier or a prompt "Node flow conditions are not met, 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 any node leader does not activate the node completion button in the parent work item 312 of their page 310, after that node leader activates the button, a message "xx data modified to xx, single person completed" will be displayed, and all operation buttons will still be shown until all leaders of that node have performed operations. In this case, the node status will be displayed on page 310, but the operation buttons will not be shown. In some embodiments, as shown in Figure 3C, when the parent work item 312 of page 310 contains node leaders, the node leaders are linked to roles. If user 104B is a leader, they can fill in their various roles in the parent work item 312, thereby achieving linkage based on personnel linkage rules.

[0146] As can be understood, referring to Figure 1B, the review process can be abstracted into three steps: review preparation, review conclusion, and review summary. Review preparation involves determining the materials to be reviewed (e.g., whether deliverables are ready) and the factors to be reviewed (e.g., adjusting review factors using trimming controls). Review conclusion includes the review comments and conclusions given by each reviewer. Review summary includes generating the final review conclusion (node ​​completion conclusion).

[0147] The foregoing embodiments described the presentation of relevant review information. The following describes the rules for giving and summarizing review conclusions, as well as the node flow rules based on the summarized review conclusions.

[0148] In some embodiments, each participant in the review process at each review node can provide their own review conclusions in their own collaborative management software.

[0149] Figure 3D shows yet another schematic diagram of an exemplary page 320 according to an embodiment of the present disclosure.

[0150] As shown in Figure 3D, user 104B can view page 320 in the collaborative management software of terminal device 102B. This page 320 summarizes all the operable process nodes for user 104B. For example, for project 1, user 104B can generate a drop-down window 3202 by clicking any operation button. This window 3202 displays the nodes that user 104B needs to operate under project 1, and also provides operation buttons after each node for user 104B to perform quick operations. After the operation is completed, system 100 can obtain the review operation information of one or more sub-work items of each review node to summarize the review conclusions. Then, based on this review operation information, the node completion conclusion and workflow status of the review node can be determined.

[0151] In some embodiments, determining the node completion conclusion and workflow status of the review node based on the review operation information includes: obtaining the node completion conclusion rules of the review node; and determining the node completion conclusion of the review node based on the review operation information and the node completion conclusion rules, thereby enabling automatic summarization of node completion conclusions. Optionally, the page may display specific completion information of the node leader, wherein the node completion conclusion and node completion comments may be displayed in separate columns.

[0152] In some embodiments, determining the node completion conclusion and flow status of the review node based on the review operation information includes: obtaining the completion flow conditions of the review node; and determining the flow status of the review node based on the review operation information, the node completion conclusion, the completion flow conditions, and the node flow status calculation rules, thereby enabling automatic calculation of the node flow status.

[0153] For example, in some embodiments, when user 104B clicks the operation button, the operation can be verified according to the node flow conditions. If the conditions are met, the operation corresponding to the operation button can be completed. Then, it is determined whether the review node has been completed (both the node leader and the reviewer have completed the operation). Otherwise, a reminder is sent 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 the flow is transferred to the next node.

[0154] As can be seen from the above embodiments, the process configuration and management method provided in this disclosure automatically creates work items and fills in some fields based on resources, so that users do not need to manually create and fill in work items, making the operation simpler and smoother.

[0155] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.

[0156] It should be noted that the above description describes some embodiments of this 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 a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0157] Figure 4A illustrates a flowchart of an exemplary method 400 provided in an embodiment of this disclosure. This method 400 can be used to configure a project's workflow. Optionally, this method 400 can be implemented independently by the terminal device 102A of Figure 1A, or it can be implemented by the system 100 of Figure 1A.

[0158] As shown in Figure 4A, the method 400 may further include the following steps.

[0159] In step 402, the review node of the target process is determined (e.g., review node 2 in Figure 2A).

[0160] In step 404, one or more resources associated with the review node are obtained (e.g., resources 2, 4, and 7 in Figure 2C).

[0161] In step 406, based on the one or more resources, one or more sub-work items for review are created for the review node, wherein at least some fields in the one or more sub-work items are populated with field values ​​based on the one or more resources (e.g., the review element work items and their field values ​​in Figure 2F).

[0162] The process configuration method provided in this disclosure automatically creates work items and fills in some fields based on resources, so that users do not need to manually create and fill in work items, making the operation simpler and smoother.

[0163] In some embodiments, acquiring one or more resources associated with the review node includes:

[0164] Receive instructions to add sub-work items to the review node based on resources;

[0165] Retrieve a list of resources from the resource library and display the list of resources (see Figure 2C);

[0166] Based on the addition instruction for one or more resources in the resource list (e.g., selecting the corresponding resources 2, 4, and 7), obtain one or more resources associated with the review node.

[0167] This makes adding resources more convenient by automatically displaying the resource list.

[0168] In some embodiments, the method further includes:

[0169] The page displays one or more sub-work items, and a first configuration button (e.g., configuration buttons 2042-2046 in Figure 2D) is displayed on one side of each sub-work item;

[0170] In response to the first configuration button being triggered, the visibility condition configuration window of the sub-work item is displayed (e.g., window 208 in FIG2E), the visibility condition configuration window includes a first configuration item for configuring visibility conditions (e.g., configuration items 2082, 2084 in FIG2E).

[0171] In response to receiving a configuration completion instruction, the visibility conditions of the sub-work item are determined based on the configuration information of the first configuration item, so as to display the sub-work item when the visibility conditions are met.

[0172] In this way, by setting visibility conditions, sub-task items can be filtered based on visibility conditions when displayed, avoiding unnecessary sub-task items from taking up page space and preventing users from accidentally clicking on them.

[0173] In some embodiments, the method further includes:

[0174] Display a second configuration button on the page for configuring the sub-work item table view (e.g., configuration button 204B in Figure 2B);

[0175] In response to the triggering of the second configuration button, a table view configuration window for the one or more sub-work items is displayed (e.g., window 210 in FIG2F). The table view configuration window includes 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 includes a preview image of the table view of the one or more sub-work items generated based on the currently selected table column. The table column resource list includes multiple table column resources for adding corresponding table columns to the table view of the one or more sub-work items.

[0176] In response to an instruction to add a target table column resource among a plurality of table column resources, a preview table column corresponding to the target table column resource is added to the preview image.

[0177] 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.

[0178] In some embodiments, the list of table column resources includes review conclusion table column resources;

[0179] In response to an add instruction for a target table column resource among a plurality of table column resources, a preview table column corresponding to the target table column resource is added to the preview image, including:

[0180] In response to the 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 to the preview image. 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 comments, and a fifth preview table column 2104E corresponding to the review operation.

[0181] By configuring review conclusion table columns for the table view, users can easily provide or view review conclusions, thus improving work efficiency.

[0182] In some embodiments, the method further includes:

[0183] Display a third configuration button on the page for configuring personnel linkage rules for sub-work items (e.g., configuration button 204C in Figure 2B);

[0184] In response to the triggering of the third configuration button, the personnel linkage rule configuration window of the one or more sub-work items is displayed (e.g., window 212 in FIG2H). The personnel linkage rule configuration window includes a second configuration item 2122 for configuring linkage conditions and a third configuration item 2124 for configuring linkage condition groups.

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

[0186] In this way, by using personnel linkage rules to automatically associate relevant personnel, work efficiency can be improved while avoiding the omission of relevant personnel.

[0187] In some embodiments, the method further includes:

[0188] A fourth configuration button (e.g., configuration button 2148 in Figure 2A) is displayed on the page for configuring the node completion conclusion of the review node;

[0189] In response to the triggering of the fourth configuration button, the node completion conclusion rule configuration window of the review node is displayed (e.g., window 216 in Figure 2I). The node completion conclusion rule configuration window includes fourth configuration items 2162 and 2164 for configuring the node completion conclusion rules.

[0190] In response to receiving a configuration completion instruction, the 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 the node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is satisfied.

[0191] In this way, by configuring the rules for completing the conclusions at each node, the conclusions can be automatically calculated, thus completing the conclusion summary. Users do not need to calculate manually, which improves work efficiency.

[0192] In some embodiments, the method further includes:

[0193] A fifth configuration button (e.g., configuration button 218 in Figure 2J) is displayed on the page for configuring the completion flow conditions of the review node;

[0194] In response to the triggering of the fifth configuration button, the completion flow condition configuration window of the review node is displayed (e.g., window 220 in Figure 2K), the completion flow condition configuration window includes a fifth configuration item 2202 for configuring the completion flow conditions of the review node;

[0195] In response to receiving a configuration completion instruction, the completion conditions of the review node are determined based on the configuration information of the fifth configuration item, which is used to determine whether the review node can be processed based on the completion conditions.

[0196] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.

[0197] It should be noted that the above description describes some embodiments of this 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 a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0198] Figure 4B illustrates a flowchart of an exemplary method 410 provided in an embodiment of this disclosure. This method 410 can be used for project process management. Optionally, this method 410 can be implemented independently by the terminal device 102B of Figure 1A, or it can be implemented by the system 100 of Figure 1A.

[0199] As shown in Figure 4B, the method 400 may further include the following steps.

[0200] In step 412, configuration information of the target process configured using any embodiment or arrangement / combination of embodiments as described in the method 400 is obtained;

[0201] In step 414, 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 (as shown in Figure 3B), and at least some 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.

[0202] The process management method provided in this disclosure automatically creates work items and fills in some fields based on resources, so that users do not need to manually create and fill in work items, making the operation simpler and smoother.

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

[0204] Obtain the visibility conditions of the sub-work item;

[0205] Display one or more of the sub-work items that satisfy the visibility condition.

[0206] This way, sub-tasks that meet the visibility criteria are displayed, while those that do not are hidden. This saves page space and prevents users from wasting time on sub-tasks that do not require review, thus improving work efficiency.

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

[0208] Obtain the personnel linkage rules for the sub-work item;

[0209] The sub-task item displays personnel information that meets the personnel linkage rules.

[0210] Referring to Figure 2H, for existing personnel linkage rules, all condition groups are executed according to the order of the personnel linkage rules corresponding to the sub-item. Execution stops after matching the first condition group, and the field value of the reviewer of the parent item of the sub-item that meets the conditions is filled into the node leader of the sub-item. If the node leader of the sub-item does not match any personnel linkage rules, the node leader is matched according to the node leader rules of the sub-item itself.

[0211] In some embodiments, the one or more sub-work items include a review conclusion table column, which 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 comments, and a fifth table column corresponding to the review operation.

[0212] As shown in Figure 3B, exemplarily, the first-level heading of the review conclusion table column can be "Review Conclusion". The review conclusion table column has five second-level headings. The first column heading can be "Review Role", with its field value being the reviewer's role name in the parent work item. If multiple role names exist, they can be displayed; if no role exists, a "-" can be displayed. The second column heading can be "Reviewer", with its field value being the configured person in charge or node person in charge, with each person in charge displayed on one row. The third column heading can be "Review Conclusion", with its field value being the node completion conclusion configured for the node, and the current user's editing permissions can be determined according to node logic. The fourth column heading can be "Review Comments", with its field value being the node completion comments configured for the node, and the current user's editing permissions can be determined according to node logic. The fifth column heading can be "Review Operation", with its field value being the node completion operation button configured for the node, and the current user's editing permissions can be determined according to node logic. Rows without editing permissions can display the current process status of the review node. Optionally, the review role, reviewer, review conclusion, and review comments can also be filtered.

[0213] In some embodiments, the method further includes:

[0214] Obtain the review operation information of the one or more sub-work items of the review node;

[0215] Based on the review operation information, determine the node completion conclusion and workflow status of the review node.

[0216] In some embodiments, determining the node completion conclusion and workflow status of the review node based on the review operation information includes:

[0217] Obtain the node completion conclusion rules of the review node;

[0218] Based on the review operation information and the node completion conclusion rules, the node completion conclusion of the review node is determined.

[0219] In some embodiments, determining the node completion conclusion and workflow status of the review node based on the review operation information includes:

[0220] Obtain the completion conditions and node transition status calculation rules for the review node;

[0221] The flow status of the review node is determined based on the review operation information, the node completion conclusion, the completion flow conditions, and the node flow status calculation rules.

[0222] For example, in some embodiments, when user 104B clicks the operation button, the operation can be verified according to the node flow conditions. If the conditions are met, the operation corresponding to the operation button can be completed. Then, it is determined whether the review node has been completed (both the node leader and the reviewer have completed the operation). Otherwise, a reminder is sent 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 the flow is transferred to the next node.

[0223] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.

[0224] It should be noted that the above description describes some embodiments of this 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 a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0225] This disclosure also provides a computer device for implementing the above-described method 400 or method 410. Figure 5 shows a schematic diagram of the hardware structure of an exemplary computer device 500 provided in this disclosure. The computer device 500 can be used to implement the server 106 of Figure 1A, or it can be used to implement the terminal devices 102A and 102B of Figure 1A. In some scenarios, the computer device 500 can also be used to implement the database server 108 of Figure 1A.

[0226] As shown in Figure 5, the computer device 500 may include: a processor 502, a memory 504, a network interface 506, a peripheral interface 508, and a bus 510. The processor 502, memory 504, network interface 506, and peripheral interface 508 are interconnected within the computer device 500 via the bus 510.

[0227] Processor 502 may be a central processing unit (CPU), a graphics 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. Processor 502 can be used to perform functions related to the techniques described in this disclosure. In some embodiments, processor 502 may also include multiple processors integrated as a single logic component. For example, as shown in FIG. 5, processor 502 may include multiple processors 502a, 502b, and 502c.

[0228] Memory 504 can be configured to store data (e.g., instructions, computer code, etc.). As shown in FIG5, the data stored in memory 504 may include program instructions (e.g., program instructions for implementing method 400 or method 410 of embodiments of this disclosure) and data to be processed (e.g., the memory may store configuration files of other modules, etc.). Processor 502 can also access the program instructions and data stored in memory 504 and execute the program instructions to operate on the data to be processed. Memory 504 may include volatile storage devices or non-volatile storage devices. In some embodiments, memory 504 may include random access memory (RAM), read-only memory (ROM), optical disk, magnetic disk, hard disk, solid-state drive (SSD), flash memory, memory stick, etc.

[0229] Network interface 506 can be configured to provide communication with other external devices to computer device 500 via a network. This 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), etc.), a cellular network, the Internet, or a combination thereof. It is understood that the type of network is not limited to the specific examples described above.

[0230] The peripheral interface 508 can be configured to connect the computer device 500 to one or more peripheral devices to enable information input and output. For example, peripheral devices may include input devices such as keyboards, mice, touchpads, touch screens, microphones, and various sensors, as well as output devices such as displays, speakers, vibrators, and indicator lights.

[0231] Bus 510 can be configured to transfer information between various components of computer device 500 (e.g., processor 502, memory 504, network interface 506, and peripheral interface 508), such as internal buses (e.g., processor-memory bus), external buses (USB port, PCI-E bus), etc.

[0232] It should be noted that although the architecture of the computer device 500 described above only shows the processor 502, memory 504, network interface 506, peripheral interface 508, and bus 510, in specific implementations, the architecture of the computer device 500 may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the architecture of the computer device 500 described above may only include the components necessary for implementing the embodiments of this disclosure, and does not necessarily include all the components shown in the figures.

[0233] This disclosure also provides a process configuration apparatus. Figure 6 shows a schematic diagram of an exemplary apparatus 600 provided in this disclosure. As shown in Figure 6, the apparatus 600 can be used to implement method 400 and may further include the following modules.

[0234] Module 602 is configured to: determine the review nodes of the target process.

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

[0236] Module 606 is configured to: create one or more sub-work items for review of the review node based on the one or more resources, wherein at least some fields in the one or more sub-work items are populated with field values ​​based on the one or more resources.

[0237] The process configuration method provided in this disclosure automatically creates work items and fills in some fields based on resources, so that users do not need to manually create and fill in work items, making the operation simpler and smoother.

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

[0239] Receive instructions to add sub-work items to the review node based on resources;

[0240] Retrieve a list of resources from the resource library and display the list of resources;

[0241] Based on the add instruction for one or more resources in the resource list, obtain one or more resources associated with the review node.

[0242] In some embodiments, the device further includes a display module configured to:

[0243] The page displays one or more sub-work items, with a first configuration button displayed on one side of each sub-work item;

[0244] In response to the first configuration button being triggered, the visibility condition configuration window of the sub-work item is displayed, the visibility condition configuration window including a first configuration item for configuring visibility conditions;

[0245] In response to receiving a configuration completion instruction, the visibility conditions of the sub-work item are determined based on the configuration information of the first configuration item, so as to display the sub-work item when the visibility conditions are met.

[0246] In some embodiments, the display module is configured to:

[0247] Display a second configuration button on the page for configuring the sub-work item table view;

[0248] In response to the triggering of the second configuration button, a table view configuration window for the one or more sub-work items is displayed. The table view configuration window includes 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 includes a preview image of the table view of the one or more sub-work items generated based on the currently selected table column. The table column resource list includes multiple table column resources for adding corresponding table columns to the table view of the one or more sub-work items.

[0249] In response to an instruction to add a target table column resource among a plurality of table column resources, a preview table column corresponding to the target table column resource is added to the preview image.

[0250] In some embodiments, the list of table column resources includes review conclusion table column resources;

[0251] The display module is configured as follows:

[0252] In response to the 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 to the preview image. 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 comments, and a fifth preview table column corresponding to the review operation.

[0253] In some embodiments, the display module is configured to:

[0254] The page displays a third configuration button for configuring personnel linkage rules for sub-work items;

[0255] In response to the triggering of the third configuration button, the personnel linkage rule configuration window for the one or more sub-work items is displayed. The personnel linkage rule configuration window includes a second configuration item for configuring linkage conditions and a third configuration item for configuring linkage condition groups.

[0256] In response to receiving a configuration completion instruction, the personnel linkage rule for the sub-work item is determined based on the configuration information of the second configuration item and / or the third configuration item, and is used to add the reviewer corresponding to the personnel linkage rule to the one or more sub-work items when the personnel linkage rule is satisfied.

[0257] In some embodiments, the display module is configured to:

[0258] A fourth configuration button for configuring the node completion conclusion of the review node is displayed on the page;

[0259] In response to the triggering of the fourth configuration button, the node completion conclusion rule configuration window of the review node is displayed, and the node completion conclusion rule configuration window includes a fourth configuration item for configuring the node completion conclusion rule;

[0260] In response to receiving a configuration completion instruction, the 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 the node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is satisfied.

[0261] In some embodiments, the display module is configured to:

[0262] The page displays a fifth configuration button for configuring the completion conditions of the review node;

[0263] In response to the triggering of the fifth configuration button, the completion flow condition configuration window of the review node is displayed. The completion flow condition configuration window includes a fifth configuration item for configuring the completion flow conditions of the review node.

[0264] In response to receiving a configuration completion instruction, the completion conditions of the review node are determined based on the configuration information of the fifth configuration item, which is used to determine whether the review node can be processed based on the completion conditions.

[0265] For ease of description, the above apparatus is described in terms of its functions, divided into various modules. Of course, in implementing this disclosure, the functions of each module can be implemented in one or more software and / or hardware.

[0266] The apparatus of the above embodiments is used to implement the corresponding method 400 in any of the foregoing embodiments and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0267] This disclosure also provides a process management device. Figure 7 shows a schematic diagram of an exemplary device 700 provided in this disclosure. As shown in Figure 7, the device 700 can be used to implement method 410 and may further include the following modules.

[0268] The acquisition module 702 is configured to: acquire configuration information of the target process configured using any embodiment or arrangement or combination of embodiments as described in the method 400;

[0269] Display module 704 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, wherein at least some 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.

[0270] The process management method provided in this disclosure automatically creates work items and fills in some fields based on resources, so that users do not need to manually create and fill in work items, making the operation simpler and smoother.

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

[0272] Obtain the visibility conditions of the sub-work item;

[0273] Display one or more of the sub-work items that satisfy the visibility condition.

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

[0275] Obtain the personnel linkage rules for the sub-work item;

[0276] The sub-task item displays personnel information that meets the personnel linkage rules.

[0277] In some embodiments, the one or more sub-work items include a review conclusion table column, which 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 comments, and a fifth table column corresponding to the review operation.

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

[0279] Obtain the review operation information of the one or more sub-work items of the review node;

[0280] Based on the review operation information, determine the node completion conclusion and workflow status of the review node.

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

[0282] Obtain the node completion conclusion rules of the review node;

[0283] Based on the review operation information and the node completion conclusion rules, the node completion conclusion of the review node is determined.

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

[0285] Obtain the completion conditions and node transition status calculation rules for the review node;

[0286] The flow status of the review node is determined based on the review operation information, the node completion conclusion, the completion flow conditions, and the node flow status calculation rules.

[0287] For ease of description, the above apparatus is described in terms of its functions, divided into various modules. Of course, in implementing this disclosure, the functions of each module can be implemented in one or more software and / or hardware.

[0288] The apparatus of the above embodiments is used to implement the corresponding method 410 in any of the foregoing embodiments and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0289] Based on the same inventive concept, corresponding to any of the above embodiments, this disclosure also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method 400 or method 410 as described in any of the above embodiments.

[0290] 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, program modules, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0291] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to perform the 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.

[0292] Based on the same inventive concept, corresponding to method 400 or method 410 in any of the above embodiments, this disclosure also provides a computer program product, which includes a computer program. In some embodiments, the computer program is executable by one or more processors to cause the processors to perform the method 400 or method 410. Corresponding to the execution entity for each step in each embodiment of method 400 or method 410, the processor performing the corresponding step may belong to the corresponding execution entity.

[0293] In some embodiments, the computer program product includes program modules for resolving operational conflicts, the program modules including modules compiled as a stack-based virtual machine binary instruction set (e.g., wasm) for use by terminal devices and / or modules compiled as static libraries for use by servers.

[0294] The computer program product of the above embodiments is used to cause the processor to execute the 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 repeated here.

[0295] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this disclosure (including the claims) is limited to these examples; within the framework of this disclosure, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this disclosure as described above, which are not provided in detail for the sake of brevity.

[0296] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this disclosure, the provided drawings may or may not show well-known power / ground connections to integrated circuit (IC) chips and other components. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this disclosure, and this also takes into account the fact that the details of implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this disclosure will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuitry) have been set forth to describe exemplary embodiments of this disclosure, it will be apparent to those skilled in the art that the embodiments of this disclosure may be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0297] Although this disclosure has been described in conjunction with specific embodiments thereof, many substitutions, 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 be used with the embodiments discussed.

[0298] This disclosure is 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 this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A process configuration method, comprising: Identify the review points for the target process; Retrieve one or more resources associated with the review node; Based on the one or more resources, create one or more sub-work items for the review node for review, wherein at least some fields in the one or more sub-work items are populated with field values ​​based on the one or more resources.

2. The method as described in claim 1, wherein, Retrieving one or more resources associated with the review node, including: Receive instructions to add sub-work items to the review node based on resources; Retrieve a list of resources from the resource library and display the list of resources; Based on the add instruction for one or more resources in the resource list, obtain one or more resources associated with the review node.

3. The method as described in claim 1, wherein, The method further includes: The page displays one or more sub-work items, with a first configuration button displayed on one side of each sub-work item; In response to the first configuration button being triggered, the visibility condition configuration window of the sub-work item is displayed, the visibility condition configuration window including a first configuration item for configuring visibility conditions; In response to receiving a configuration completion instruction, the visibility conditions of the sub-work item are determined based on the configuration information of the first configuration item, so as to display the sub-work item when the visibility conditions are met.

4. The method of claim 1, wherein, The method further includes: Display a second configuration button on the page for configuring the sub-work item table view; In response to the triggering of the second configuration button, a table view configuration window for the one or more sub-work items is displayed. The table view configuration window includes 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 includes a preview image of the table view of the one or more sub-work items generated based on the currently selected table column. The table column resource list includes multiple table column resources for adding corresponding table columns to the table view of the one or more sub-work items. In response to an instruction to add a target table column resource among a 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 of claim 4, wherein, The list of table column resources includes review conclusion table column resources; In response to an add instruction for a target table column resource among a plurality of table column resources, a preview table column corresponding to the target table column resource is added to the preview image, including: In response to the 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 to the preview image. 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 comments, and a fifth preview table column corresponding to the review operation.

6. The method of claim 1, wherein, The method further includes: The page displays a third configuration button for configuring personnel linkage rules for sub-work items; In response to the triggering of the third configuration button, the personnel linkage rule configuration window for the one or more sub-work items is displayed. The personnel linkage rule configuration window includes a second configuration item for configuring linkage conditions and a third configuration item for configuring linkage condition groups. In response to receiving a configuration completion instruction, the personnel linkage rule for the sub-work item is determined based on the configuration information of the second configuration item and / or the third configuration item, and is used to add the reviewer corresponding to the personnel linkage rule to the one or more sub-work items when the personnel linkage rule is satisfied.

7. The method of claim 1, wherein, The method further includes: A fourth configuration button for configuring the node completion conclusion of the review node is displayed on the page; In response to the triggering of the fourth configuration button, the node completion conclusion rule configuration window of the review node is displayed, and the node completion conclusion rule configuration window includes a fourth configuration item for configuring the node completion conclusion rule; In response to receiving a configuration completion instruction, the 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 the node completion conclusion of the review node corresponding to the node completion conclusion rule when the node completion conclusion rule is satisfied.

8. The method of claim 1, wherein, The method further includes: The page displays a fifth configuration button for configuring the completion conditions of the review node; In response to the triggering of the fifth configuration button, the completion flow condition configuration window of the review node is displayed. The completion flow condition configuration window includes a fifth configuration item for configuring the completion flow conditions of the review node. In response to receiving a configuration completion instruction, the completion conditions of the review node are determined based on the configuration information of the fifth configuration item, which is used to determine whether the review node can be processed based on the completion conditions.

9. A process management method, comprising: Obtain configuration information of the target process configured using the method described in any one of claims 1 to 8; In response to a view command for a review node of the target process, one or more sub-work items of the review node are displayed, wherein at least some fields of the one or more sub-work items are populated with field values ​​based on one or more resources associated with the review node.

10. The method of claim 9, wherein, Display one or more sub-work items of the review node, including: Obtain the visibility conditions of the sub-work item; Display one or more of the sub-work items that satisfy the visibility condition.

11. The method of claim 9, wherein, Display one or more sub-work items of the review node, including: Obtain the personnel linkage rules for the sub-work item; The sub-task item displays personnel information that meets the personnel linkage rules.

12. The method of claim 9, wherein, The one or more sub-work items include a review conclusion table column, which includes at least one of the following: 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 comments, and a fifth table column corresponding to the review operation.

13. The method of claim 12, wherein, The method further includes: Obtain the review operation information of the one or more sub-work items of the review node; Based on the review operation information, determine the node completion conclusion and workflow status of the review node.

14. The method of claim 13, wherein, Based on the review operation information, the node completion conclusion and workflow status of the review node are determined, including: Obtain the node completion conclusion rules of the review node; Based on the review operation information and the node completion conclusion rules, the node completion conclusion of the review node is determined.

15. The method of claim 14, wherein, Based on the review operation information, the node completion conclusion and workflow status of the review node are determined, including: Obtain the completion conditions and node transition status calculation rules for the review node; The flow status of the review node is determined based on the review operation information, the node completion conclusion, the completion flow conditions, and the node flow status calculation rules.

16. A process configuration apparatus, comprising: The module is configured to: determine the review nodes 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 of the review node based on the one or more resources, wherein at least some fields in the one or more sub-work items are populated with field values ​​based on the one or more resources.

17. A process management device, comprising: The acquisition module is configured to: acquire configuration information of the target process configured using the method described in 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, wherein at least some 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.

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, the programs comprising instructions for performing the method according to any one of claims 1 to 15.

19. A non-volatile computer-readable storage medium comprising 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 that, when executed by one or more processors, implement the steps of the method as claimed in any one of claims 1 to 15.

Images