CN118674392A

CN118674392A - Process configuration and management method and related equipment

Info

Publication number: CN118674392A
Application number: CN202410692870.3A
Authority: CN
Inventors: 别雨璇; 李金哲; 郭倩雯; 任航; 王宁; 余真帆; 易治; 杨能; 杨柳; 王胜; 任为; 杨晓轲; 叶云智; 杨雨亮; 章泰; 徐寅杰; 张华�; 赵民月
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2024-05-30
Filing date: 2024-05-30
Publication date: 2024-09-20

Abstract

The present disclosure provides a flow configuration and management method and related devices. The flow configuration method comprises the following steps: determining a review node of the target flow; obtaining one or more resources associated with the review node; one or more sub-work items for review are created for the review node based on the one or more resources, at least some of the fields in the one or more sub-work items being populated with field values based on the one or more resources.

Description

Process configuration and management method and related equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a flow configuration and management method and related devices.

Background

With the continuous development of internet technology, many works can be done intelligently. For example, some of the procedural transactions or objects may be flow managed by management software.

The inventors of the present disclosure have found that the related art is less convenient to use when managing the review nodes in the flow using management software.

Disclosure of Invention

The disclosure provides a flow configuration and management method and related devices to solve or partially solve the above-mentioned problems.

In a first aspect of the present disclosure, a flow configuration method is provided, including:

Determining a review node of the target flow;

obtaining one or more resources associated with the review node;

One or more sub-work items for review are created for the review node based on the one or more resources, at least some of the fields in the one or more sub-work items being populated with field values based on the one or more resources.

In a second aspect of the present disclosure, a process management method is provided, including:

acquiring configuration information of a target flow configured to be completed by the method according to the first aspect;

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

In a third aspect of the present disclosure, a flow configuration apparatus is provided, including:

a determination module configured to: and determining a review node of the target flow.

An acquisition module configured to: one or more resources associated with the review node are obtained.

A creation module configured to: one or more sub-work items for review are created for the review node based on the one or more resources, at least some of the fields in the one or more sub-work items being populated with field values based on the one or more resources.

In a fourth aspect of the present disclosure, there is provided a flow management apparatus, including:

an acquisition module configured to: acquiring configuration information of a target flow configured to be completed by the method according to the first aspect;

A display module configured to: in response to a view instruction for a review node of the target flow, one or more sub-work items of the review node are displayed, at least some of the fields of the one or more sub-work items being populated with field values based on one or more resources associated with the review node.

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

In a sixth aspect of the present disclosure, there is provided 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 of the first aspect.

In a seventh aspect of the present disclosure, there is provided a computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method according to the first aspect.

According to the flow configuration and management method and the related equipment, the work items are automatically created based on the resources and partial fields are filled, so that a user does not need to manually create and fill the work items, and the operation is simpler, more convenient and smoother.

Drawings

In order to more clearly illustrate the technical solutions of the present disclosure or related art, the drawings required for the embodiments or related art description will be briefly described below, and it is apparent that the drawings in the following description are only embodiments of the present disclosure, and other drawings may be obtained according to these drawings without inventive effort to those of ordinary skill in the art.

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

Fig. 1B illustrates a schematic diagram of an exemplary Work Breakdown Structure (WBS) according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Fig. 4A shows a flow diagram of an exemplary method provided by an embodiment of the present disclosure.

Fig. 4B shows a flow diagram of another exemplary method provided by an embodiment of the present disclosure.

Fig. 5 shows a hardware architecture diagram of an exemplary computer device provided by an embodiment of the present disclosure.

Fig. 6 shows a schematic diagram of an exemplary apparatus provided by an embodiment of the present disclosure.

Fig. 7 shows a schematic diagram of an exemplary apparatus provided by an embodiment of the present disclosure.

Detailed Description

For the purposes of promoting an understanding of the principles and advantages of the disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same.

It should be noted that unless otherwise defined, technical or scientific terms used in the embodiments of the present disclosure should be given the ordinary meaning as understood by one of ordinary skill in the art to which the present disclosure pertains. The terms "first," "second," and the like, as used in embodiments of the present disclosure, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that elements or items preceding the word are included in the element or item listed after the word and equivalents thereof, but does not exclude other elements or items. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", etc. are used merely to indicate relative positional relationships, which may also be changed when the absolute position of the object to be described is changed.

It will be appreciated that before using the technical solutions of the various embodiments in the disclosure, the user may be informed of the type of personal information involved, the range of use, the use scenario, etc. in an appropriate manner, and obtain the authorization of the user.

For example, in response to receiving an active request from a user, a prompt is sent to the user to explicitly prompt the user that the operation it is requesting to perform will require personal information to be obtained and used with the user. Therefore, the user can select whether to provide personal information to the software or hardware such as the electronic equipment, the application program, the server or the storage medium for executing the operation of the technical scheme according to the prompt information.

As an alternative but non-limiting implementation, in response to receiving an active request from a user, the manner in which the prompt information is sent to the user may be, for example, a popup, in which the prompt information may be presented in a text manner. In addition, a selection control for the user to select to provide personal information to the electronic device in a 'consent' or 'disagreement' manner can be carried in the popup window.

It will be appreciated that the above-described notification and user authorization process is merely illustrative, and not limiting of the implementations of the present disclosure, and that other ways of satisfying relevant legal regulations may be applied to the implementations of the present disclosure.

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

As shown in fig. 1A, the system 100 may be used to implement online or offline project management functionality and may include terminal devices 102A, 102B, a server 106, and a database server 108. The terminal devices 102A, 102B may include a medium (e.g., a network) that provides a communication link with the server 106 and database server 108. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

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

The terminal devices 102A, 102B may be hardware or software. When the terminal devices 102A, 102B are hardware, they may be various electronic devices with display screens, including but not limited to smartphones, tablets, electronic book readers, MP3 players, laptop portable computers (Laptop), desktop computers (PC), and the like. When the terminal devices 102A, 102B are software, they can be installed in the above-listed electronic devices. Which may be implemented as multiple software or software modules (e.g., to provide distributed services), or as a single software or software module. The present invention is not particularly limited herein.

The server 106 may be a server that provides various services, such as a background server that provides support for various applications displayed on the terminal devices 102A, 102B. Database server 108 may also be a database server that provides various services. It will be appreciated that the database server 108 may not be provided in the system 100 where the server 106 may implement the functions associated with the database server 108.

The server 106 and the database server 108 may be hardware or software. When they are hardware, they may be implemented as a distributed server cluster composed of a plurality of servers, or as a single server. When they are software, they may be implemented as a plurality of software or software modules (e.g., to provide distributed services), or as a single software or software module. The present invention is not particularly limited herein.

It should be noted that, the method for editing a document provided by the embodiment of the present disclosure may be performed by the server 106. It should be understood that the number of terminal devices, users, servers and database servers in fig. 1A is merely illustrative. There may be any number of terminal devices, users, servers, and database servers, as desired for implementation.

In some embodiments, the terminal devices 102A, 102B may have project management class applications or software installed therein, which the users 104A, 104B may utilize to project manage. For example, setting project flows and work items related to flow nodes, and so forth. As an alternative embodiment, the user 104A may be an administrator of the project for overall process management of the project, the user 104B may be a participant of the project, and after the user 104A has contracted the process, the user 104B may view the process and operate according to the process.

One type of project management is an integrated product development process (IPD), where review management is a very important business management scenario in the process, determining whether the process can be circulated normally.

In general, a plurality of different types of review nodes may be experienced in an integrated product development process, such as peer review, technology review, decision review, and so forth. Each review node requires the participation of the relevant personnel. Therefore, the project management software needs to review the management function, and the review management function accords with the use habit of the user and can also greatly improve the user experience.

The review process generally requires that a decision maker refer to decision reference resources according to a review dimension to give a review conclusion to the content to be reviewed, and the review conclusion affects the project process or state.

As shown in FIG. 1B, a project development process work item may be broken down into a plurality of process nodes having a certain order of execution. The process nodes such as the feasibility analysis node, the peer review node, the technology review node, the decision review node and the like can be review nodes, and the next node can be circulated only after the review process and the project process pass through.

As shown in FIG. 1B, illustratively, the availability analysis node further associates a deliverables item, which is a parent-child relationship between the deliverables item and the project development flow item, such that the deliverables item may be a child of the project development flow item, which may be a parent of the deliverables item. The deliverables workitem under the feasibility analysis node may further include a review process for the deliverables (e.g., project feasibility report) of the feasibility analysis node, such as submitting the feasibility report, reviewing the report, warehousing the feasibility report after the review passes, so that the review node completes, and the project process flows to the next node.

Illustratively, as shown in fig. 1B, the decision review node further associates a review work item, where a parent-child relationship exists between the decision review work item and the project development flow work item, and thus, the decision review work item may be a child work item of the project development flow work item, and the project development flow work item may be a parent work item of the decision review work item.

Illustratively, the decision review work item under the decision review node may further include a review flow for the deliverables (e.g., developed finished products) of the decision review node, e.g., review preparation, market representatives & product representatives review, decision. The review preparation mainly relates to a delivery work item for preparing a delivery to be reviewed, a review problem work item and review element resources required by decision review, wherein the review problem work item and the decision review work item can be in a father-son relationship, so that the review problem work item can be a child work item of the decision review work item, and the decision review work item can be a father work item of the review problem work item. The market representative and product representative review mainly relates to a delivery work item, a review element work item and a review problem work item, wherein the review element work item, the review problem work item and the decision review work item can be father-son relations, each review element work item corresponds to a review person, a review conclusion and a review explanation, and a representative review node of the decision review work item corresponds to a review person, a review conclusion and a review explanation. The decision is mainly related to a review problem work item related to making the decision, and the decision sub-node also corresponds to a reviewer, a review conclusion and a review explanation, and also corresponds to a final reviewer and a final review conclusion.

The peer review nodes and the technology review nodes are similar in structure to the decision review nodes (generally, decision sub-nodes are not included) and are not described in detail herein.

Therefore, in view of the complexity of the review process, in order to enable the review process to be performed smoothly, the project management software needs to provide the user with a function of conveniently completing the decision process, but the project management software of the related art has a problem that the use is not smooth more or less.

In view of this, in one aspect of the embodiments of the present disclosure, a flow configuration method is provided.

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

As shown in fig. 2A, in some embodiments, the user 104A may open the collaborative office class software with the terminal device 102A, and the page 200 may be presented in the terminal device 102A. Illustratively, the first region 200A of the page 200 may display a project flow diagram further including a plurality of flow nodes arranged and connected in a flow execution order.

As shown in fig. 2A, illustratively, user 104A may select review node 2 (review node 2 is highlighted), and second region 200B of page 200 defaults to displaying node information for the selected node, node information tab 202A being highlighted. Illustratively, the user 104A clicks on the sub-work item tab 202B, and the second area may display a plurality of configuration buttons for configuring the sub-work items of the review node 2, as shown in FIG. 2B.

Alternatively, user 104A clicking on configuration button 204A may issue an instruction to terminal device 102A to add a child work item for a review node based on the resource, which terminal device 102A responds to and may display resource addition window 206 in page 200, as shown in FIG. 2C. Alternatively, the terminal device 102A may obtain a resource list from the resource library and display the resource list, as shown in fig. 2C. The resource library can be preconfigured, resources in the resource library can be used for a review flow, and sub-work items can be automatically generated for the review node by means of importing the resources.

As shown in FIG. 2C, optionally, a search box may be included in window 206 for searching for desired resources by keywords. Optionally, window 206 may also include a screening control that user 104A triggers, and a popup window may be displayed on one side of the screening control that may be used to set screening conditions so that resources in the resource list may be screened based on the screening conditions (e.g., classification conditions, stage conditions, etc.). In this way, the user 104A can conveniently find the resources that need to be added.

As shown in fig. 2C, optionally, a checkbox is provided before each resource in the resource list, and the user 104A may select the resource to be added by checkpointing to the checkbox of the corresponding resource. As shown in fig. 2C, illustratively, the user 104A selects resources 2, 4, 7, the selected resources are displayed to the right of window 206, the user 104A clicks the ok button, an add instruction for one or more resources (e.g., resources 2, 4, 7) in the list of resources may be issued to the terminal device 102A, and the terminal device 102A may obtain one or more resources (e.g., resources 2, 4, 7) associated with the review node according to the add instruction.

Terminal device 102A may then create one or more sub-work items for review for the review node based on the one or more resources (e.g., resources 2, 4, 7), at least some of the fields (e.g., review element fields) in the one or more sub-work items being populated with field values based on the one or more resources. In this way, some sub-work items may be pre-set in advance for the review node, eliminating the need for manual addition. It can be appreciated that the matching relationship between the resource and the sub-work item can be preset, and the sub-work item can be automatically created and filled with at least part of the values of the fields only by importing the resource.

In some embodiments, after adding the child work items based on the resources, the added child work items may be displayed in the page, with the first configuration buttons 2042-2046 displayed on one side of the child work items, as shown in FIG. 2D. Alternatively, the added sub-work item may display related prompt information, for example, information of a review element field corresponding to the sub-work item is displayed on the sub-work item, so that the user can intuitively know what review element the sub-work item corresponds to.

The first configuration buttons 2042 to 2046 are used for editing the added child work items and may also be used for configuring the visible conditions of the added child work items. Illustratively, in response to the first configuration button being triggered (e.g., user 104A clicking on button 2042), a visible condition configuration window 208 of the child work item is displayed, as shown in FIG. 2E. Optionally, the visible condition configuration window 208 may include a first configuration item 2082, 2084 for configuring visible conditions. In some embodiments, after opening window 208, default selection of the default view button, and after selection of the condition view button, a configuration condition area is displayed in window 208, as shown in FIG. 2E. Illustratively, the first configuration items 2082, 2084 in the window 208 may be generated in the window 208 by the user 104A by triggering the add condition control 2086 in the window 208. Alternatively, the selectable scope of the leftmost option of the first configuration items 2082, 2084 may be a field of the parent work item to which the child 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 so forth. The middle option of the first configuration item 2082, 2084 may be an operator, and the rightmost option may be the content corresponding to the leftmost option. The relationship between the conditions may also be set as "and" ", or by inputting a condition formula. For example, taking the example shown in fig. 2E, the condition currently set is when the review element of the parent work item includes "is the market for segments large enough? "and the panelist of the parent work item includes Zhang Sanj," is the demand rational? "the sub-work item corresponding to the review element may be presented.

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

Optionally, the added sub-work items may also be deleted, an operation log of editing and deleting the sub-work items may be recorded, the user 104A may view the log in a log page, and the sub-work items may be retrieved.

Returning to FIG. 2B, optionally, a second configuration button 204B for configuring the child work item form view may also be displayed in a second area 200B of the page 200. Because the work item includes multiple fields, the work item may be presented in tabular form in a schedule table for complete presentation of the sub-work item content. Also, since the fields required for different review nodes or review flows may be different, the effect of the finally presented schedule may be adjusted by configuring the sub-work item table view.

Illustratively, in response to the second configuration button being triggered (e.g., the user clicking on button 204B), a form view configuration window 210 of the one or more child work items may be displayed in 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 at a side of the table view preview area, where the table view preview area 210A includes a preview view (as shown in fig. 2F) of the table view of the one or more sub-work items generated based on the currently selected table column, and the table column resource list includes a plurality of table column resources for adding corresponding table columns in the table view of the one or more sub-work items. Alternatively, as shown in FIG. 2F, the table column resources include resources for filling in a table column of text, e.g., names, descriptions, etc. As shown in FIG. 2F, the tabular column resources can also include resources for selecting field values, e.g., priority, demand status, review conclusion, labels, and so forth.

The table column resources in the table column resources list area 210B may be added to the table view preview area 210A to update the preview, and thus the table view on the application side may be updated based on the preview. Thus, in response to an add instruction (e.g., long press of the resource and drag to the table view preview area 210A) for a target table column resource (any of the table column resource list areas 210B) among the plurality of table column resources, a preview table column corresponding to the target table column resource may be added to the preview image, thereby updating the preview image, and the updated preview image is consistent with the table view presented on the application side (including consistency of the arrangement format and the specific content).

Thus, the user can conveniently adjust the table view of the schedule, so that the application side can be more in line with the habit of the review flow or the habit of the user when the schedule is displayed.

In some embodiments, as shown in FIG. 2F, the list of tabular column resources includes a review conclusion tabular column resource 2102; in response to an add instruction to the review form column resource 2102 (e.g., drag the review conclusion form column resource 2102 to the right of the review element preview form column), a review conclusion preview form column 2104 corresponding to the review form column resource is added in the preview image, including a first preview form column 2104A corresponding to a review role, a second preview form column 2104B corresponding to a review person, a third preview form column 2104C corresponding to a review conclusion, a fourth preview form column 2104D corresponding to a review opinion, and a fifth preview form column 2104E corresponding to a review operation, as shown in fig. 2G. In some embodiments, the user 104A may also configure an associated node for each review conclusion in the preview such that the associated node is also associated with the corresponding review conclusion table column, eliminating the need to set up the node separately.

In this way, user 104A conveniently adds a review conclusion table column in the table view, and subsequent user 104B can present its own review conclusion for each review element sub-work item via a review operation (e.g., pass, fail, or conditional pass) based on the review conclusion table column.

As shown in fig. 2F, the window 210 further includes a basic setting tab, and by clicking the tab, the content of the window 210 may be displayed in a switching manner to be a configuration item corresponding to the basic setting, where various form view templates may be included, and the user 104A may select any one of the templates to generate a corresponding form view, so that self-configuration is not required, and the use is convenient. Optionally, the user 104A may also select a template to generate a table view and then switch to the table setting to make further adjustments to the table view template.

Returning to FIG. 2B, in some embodiments, page 200 may also display a third configuration button 204C for configuring the person linkage rules for the child work items. Alternatively, in response to a hover instruction for the third configuration button 204C (e.g., move the cursor over the third configuration button 204C and stay), a prompt may be displayed "if a rule is configured, the configuration of all node principals of the child work items is no longer effective, if a rule is not configured, the node principal configuration of the child work items is effective", prompting the user 104A that once configured, the principal originally configured for each child work item will not be effective, to satisfy the rule and automatically add the principal to the principal of the child work item.

In response to the third configuration button 204C being triggered, a person linkage rules configuration window 212 of the one or more child work items may be displayed, as shown in fig. 2H. Optionally, the person linkage rules configuration window 212 includes a second configuration item 2122 for configuring a linkage condition and a third configuration item 2124 for configuring a linkage condition group.

As shown in fig. 2H, the user 104A may add a condition set by clicking on the third configuration item 2124. A second configuration item 2122 configuring the linkage condition is further displayed in the condition group configuration area. Within each condition set, the selectable scope of the leftmost option is a field of the child work item, and the operator and rightmost option are user-configured content.

After the condition is set, the result of the rule can be configured. The selectable scope of the drop-down box on the left is the role on the parent of the child workitem, which is selectable. The selectable scope of the drop-down box on the right side is the designated node responsible person of the designated flow template on the child work item, which is only selectable.

In response to receiving a configuration completion instruction (e.g., user 104A clicks a determination button in a lower right corner of window 212), a personnel linkage rule of the sub-work item is determined according to configuration information of the second configuration item 2122 and/or the third configuration item 2124, and a review personnel corresponding to the personnel linkage rule is added to the one or more sub-work items when the personnel linkage rule is satisfied.

Taking fig. 2H as an example, when a person linkage rule is currently created, when a child work item belongs to the market field and the development field, a principal and a product manager of a parent work item are synchronized as research and development representatives/node responsible persons in the child work item.

Therefore, through the arrangement of personnel linkage rules, important responsible persons are avoided from being missed in some review processes, and the review processes are ensured to be more perfect.

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

In some embodiments, a cut control may also be added for each sub-work item for the user 104B to delete unwanted sub-work items (particularly review element sub-work items) at the application side, thereby avoiding unwanted review elements from occurring in the review flow. In configuring the clipping control, a configuration may be made for each child work item and clipping rights may be configured (i.e., what roles may clip the child work item). After the clipping control is configured, the clipping control can be displayed on the application side at the side of the corresponding sub-work item, so that the user B can delete the sub-work item which is not needed in the review flow by utilizing the clipping control.

Returning to FIG. 2A, a second area 200B of the page 200 displays the configuration item corresponding to the node information tab 202A. Under the page corresponding to the node information tag 202A, the field of the review node may be customized, and whether and how the field is displayed may be configured. Optionally, the default node fields of the system may include node name, node ID, node principal, node schedule, node estimation, node actual man-hour.

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

Optionally, after the node completion conclusion configuration item 2142 is checked, a filling control of the node completion conclusion needs to be displayed at the application side, and the node completion conclusion (the completion conclusion of the node as a whole) and the review conclusion of the node responsible person corresponding to each work item need to be filled in the filling control, wherein the review conclusion of the node responsible person corresponding to each work item is only modified and filled in by the node responsible person of the work item, and the node completion conclusion can be manually filled in by the node authorization role. The node completion conclusion and the review conclusion filled in by the inventor and other people can be displayed in the page of the application side. In some embodiments, the conclusion rules may be aggregated by node completion. User 104A may configure the node completion conclusion rules.

The corresponding options for the conclusion may be configured, at least one option needs to be retained, alternatively, the default options for the conclusion may include pass, fail, conditional pass, and the user 104A may choose option configuration item 2146 to view the options for which the conclusion is configured and modify these options.

Optionally, after the node completion opinion configuration item 2144 is checked, a filling control of node completion opinions needs to be displayed on the application side, and the node completion opinions (the complete opinion of the whole node) and the review opinions of the node responsible persons corresponding to each work item need to be filled in the filling control, and the opinions can be in a text format. The review comments of the node responsible person corresponding to each work item are only authorized to be modified and filled by the node responsible person of the work item, and the node completion comments can be manually filled by the node authorized roles. The node completion opinion and the review opinion filled in by the inventor and other people can be displayed in the page of the application side.

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

Illustratively, as shown in FIG. 2I, the fourth configuration item 2162, 2164 includes the conditions of the rules and the results of the rules when the conditions are satisfied. The rule condition comprises 5 options from left to right, wherein the first option is single option, and the selectable range is more or not more than; the second option is to fill in the number; the third option is single option, and the selectable range is a number or a percentage; the fourth option is used for selecting a role of a reviewer (or a responsible person), and optionally, all personnel related to the review node can be contained in a drop-down menu; the fifth option is used to select a completion conclusion, which, as previously described, is configurable, typically comprising three of pass, no pass, conditional pass. The rule result when the condition is satisfied may be pass or fail.

For example, consider rule 1 configured in FIG. 2I, which is that when a product manager or developer's review concludes that there are more than 3 passes or conditional passes in total, the node completes the conclusion as a pass. Alternatively, if the role of the existing person is both a product manager and a developer, its count is only 1.

As shown in fig. 2I, alternatively, the rule may set a plurality of rules, and a rule may be set for spam, that is, when none of the configured rules is satisfied, the completion conclusion is summarized as pass or fail. Taking the rule configured in fig. 2I as an example, when neither rule 1 nor rule 2 is satisfied, the node completion conclusion is failed.

And responding to the received configuration completion instruction, determining a node completion conclusion rule of the evaluation node according to the configuration information of the fourth configuration item, and generating a node completion conclusion of the evaluation node corresponding to the node completion conclusion rule when the node completion conclusion rule is met.

Illustratively, after the rule is configured, at the application side, when all node responsible persons corresponding to the review node (for example, responsible persons or reviewers corresponding to each sub-work item) submit the review conclusion, the rule is triggered to perform summary calculation on the review conclusion, and if the node responsible person updates the review conclusion, the recalculation is triggered.

As shown in FIG. 2I, optionally, prompt 2166 may also be displayed in window 216 for prompting the user for the consequences of the rule configuration (e.g., "after all have filled out the review conclusion, the following rules are executed for summarization"), the order in which the rules are executed (e.g., "rules are validated from top to bottom"), and the configuration method (e.g., "order can be adjusted by dragging").

Accordingly, at the application side, when the review conclusion summary computation is triggered, it may be sequentially determined according to the order of the rules configured in the window 216, and when the first hit rule occurs, the subsequent rule is no longer matched.

Further, optionally, the options may also be checked. For example, when the node in the rule completes the editing of the name of the conclusion option, synchronous update is displayed in the rule; and after all node completion conclusion options in the rule are deleted, the rule is not effective, an error identification is given, and a prompt is given when the user saves the rule.

In some embodiments, in addition to the above manner of configuring node completion conclusions and node completion opinions, the configuration may be performed in a general node information page, and the configured node may be selected in a drop-down menu of a node name configuration item, where the selectable range is all nodes in the workflow template, and the same-name node appears only once (i.e., if the node has been configured with node completion conclusions and node completion opinions, the node is not shown in the drop-down menu any more), and is positioned by name.

Returning to fig. 2A, optionally, a node circulation tab 202C may be further included in the second area 200B of the page 200, and when the user 104A clicks on the node circulation tab 202C, a configuration item for configuring a status circulation related to the review node may be displayed in the second area 200B of the page 200, as shown in fig. 2J. Optionally, the second area 200B may include a fifth configuration button 218 for configuring the complete flow condition of the review node.

Optionally, in response to the fifth configuration button 218 being triggered, a completion flow condition configuration window 220 of the review node may be displayed in the page 200, as shown in fig. 2K. Optionally, the completion flow condition configuration window 220 may include a fifth configuration item 2202 for configuring completion flow conditions of the review node. As shown in fig. 2K, fifth configuration items 2202 may be newly built in window 220 by clicking on the add condition button, each fifth configuration item 2202 may include three options, a leftmost option for selecting a field of a sub-work item under the review node, a middle option for selecting a logical operator, and a rightmost option for selecting specific content.

In response to receiving a configuration completion instruction (e.g., user 104A completes configuration of options and clicks a determination button in the lower right corner of window 220), a completion circulation condition of the evaluation node is determined according to the configuration information of the fifth configuration item, for determining whether the evaluation node is capable of circulation according to the completion circulation condition.

Whether or not circulation is possible may mean whether or not the state of the review node can be changed. In some embodiments, as shown in fig. 2J, a user may configure a node circulation condition before configuring a completion circulation condition, where the checked configuration item in the node circulation condition requires that the corresponding review field needs to be completed, and when the node circulation condition is satisfied, the completion circulation condition is further satisfied (for example, the review form field includes a technical solution to be confirmed and the reviewer includes a third item), and the state of the review node is considered to satisfy the condition that the change occurs.

Alternatively, after the state change condition is satisfied, the state of the node should be circulated to what state, and may be set by configuration. As shown in fig. 2J, the second region 200B may further include a sixth configuration button 222 for configuring the node circulation status of the review node.

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

As shown in fig. 2L, the circulation state of the review node may include, for example, three, not started, neutralization completed. Each state may correspond to a configuration node-flow state calculation rule, and the node-flow state calculation rule for each state may be configured in window 224. Optionally, as shown in fig. 2L, each state corresponds to a sixth configuration item 2242, and after each sixth configuration item 2242 is triggered, a drop-down frame may be generated for the state, where the drop-down frame includes a specific option for configuring the node circulation state calculation rule. Illustratively, as shown in FIG. 2L, a drop-down box 2244 in the completed state is displayed in window 224, the right side of drop-down box 2244 includes information of the condition currently being configured, the left side of drop-down box 2244 includes the condition that has been configured, when any one of the conditions that has been configured to the left side of drop-down box 2244 is selected, the selected condition is highlighted, and the right side of drop-down box 2244 may display specific information of the condition, and the condition may be modified by modifying the information. As shown in fig. 2L, optionally, a new node circulation state and its calculation rules may also be created by adding a set of state and condition buttons.

In response to receiving a configuration completion instruction (e.g., user 104A completes configuration of options and clicks a determination button in the lower right corner of window 224), a node circulation state of the evaluation node is determined according to the configuration information of sixth configuration item 2242, for calculating the circulation state of the evaluation node according to the node circulation state calculation rule.

Illustratively, as shown in FIG. 2L, when the phase of the review node is the stand phase and the node principal does not contain Zhang three, the flow state of the review node is completed.

Alternatively, a spam rule may be set, i.e., when no node-flow state calculation rule is configured, the state calculation is completed when the node is completed.

In some embodiments, a state calculation rule for the entirety of the item may also be configured for calculating the entirety state of the item. Optionally, the state calculation rules may be determined according to the circulation state of each node, and the manner of setting the state calculation rules is similar to the configuration manner of the node circulation state calculation rules, which is not described herein.

In some embodiments, the user 104A may also configure the buttons (buttons of the respective typeface) corresponding to review operations (including pass, fail, conditional pass, etc.), such as configuring button names, button styles, button events (events triggered after a button is clicked, e.g., configuration forms, data assignments, completion nodes, etc.), and so forth.

After the configuration is completed by the method, the flow management can be performed based on the information of the configuration completion. Illustratively, the user 104B may utilize the terminal device 102B to open the collaborative office class software for flow management of the project.

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

As shown in fig. 3A, illustratively, the user 104B may open the collaborative office software by using the terminal device 102B and obtain configuration information of the target process (current item) configured by using the foregoing process configuration method, and further, the page 300 may be displayed in the terminal device 102B. Illustratively, as shown in FIG. 3A, page 300 may display a flow chart of items further including a plurality of flow nodes arranged and connected in a flow execution order.

In some embodiments, configuration information of the target process (current project) configured by the process configuration method may be further obtained, for example, one or more resources associated with a review node in the target process, so as to create one or more sub-work items corresponding to the configuration information for the review node in the target process, and fill field values in at least part of fields in the one or more sub-work items based on one or more resources associated with the review node.

In some embodiments, the one or more child work items of the review node are displayed in response to a view instruction for the review node of the target flow (e.g., double-clicking the review node in the flow chart), as shown with reference to fig. 3B.

Illustratively, a plurality of sub-work items corresponding to the review elements of the review node 2 are shown in FIG. 3B. At least part of the sub-workitems may be created from one or more resources associated with the review node 2 and field values of at least part of the fields therein may be populated based on the one or more resources associated with the review node. For example, work items corresponding to the review elements 1-11 may be created based on the resource, and the field values of the review elements 1-11 are populated based on the resource.

As previously mentioned, the review element may be some criteria or requirement in the review process, such as whether the market segment is large enough, whether the market research is adequate, whether the demand is reasonable, and so forth. In the review process, a reviewer or responsible person may develop the review around the review element and may make a review conclusion based on the information obtained by the review process. It follows that the review element, the deliverables to be reviewed, the review questions, etc. may all be separate sub-work items under the review node, described herein only in terms of the sub-work item to which the review element corresponds.

In some embodiments, responsive to the review node being deleted, releasing parent-child associations of the one or more child work items with the review node, the state of the one or more child work items unchanged; in response to the review node being restored, the one or more child work items are automatically associated with the review node again in a parent-child relationship. In this way, the sub-work items are not deleted after the review node is deleted, and the original sub-work items are automatically associated with the review node when the review node is created again, so that the created sub-work items are not required to be created.

In some embodiments, when one or more sub-work items of the review node are displayed, a visual condition of the sub-work item may be acquired (shown with reference to fig. 2E), and then, based on the visual condition, one or more of the sub-work items satisfying the visual condition are displayed. Therefore, the sub-work items meeting the visible conditions are displayed, the sub-work items not meeting the visible conditions are hidden, on one hand, page space can be saved, on the other hand, the user is prevented from spending effort on the sub-work items which do not need to be reviewed, and the work efficiency is improved.

In some embodiments, when one or more sub-work items of the review node are displayed, a person linkage rule of the sub-work item may be acquired, and then person information satisfying the person linkage rule is displayed in the sub-work item.

Referring to fig. 2H, for the person linkage rule that has been created, all the condition groups are executed according to the arrangement order of the person linkage rule corresponding to the child work item, execution is stopped after matching to the first condition group, and field values of reviewers of parent work items satisfying the condition child work items are filled into node responsible persons of the child work items. If the node responsible person of the sub-work item does not hit any person linkage rule, the node responsible person is matched according to the node responsible person rule of the sub-work item.

Optionally, after the child work item is successfully created, the parent work item or the information of the child work item is modified, and node responsible persons of the child work item cannot be automatically modified; meanwhile, the child work item modifies the node responsible person without affecting the role of the parent work item.

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

As shown in fig. 3B, the primary title of the review conclusion table column may be, for example, a review conclusion. The secondary header of the review conclusion table column includes 5. The column header of the first table column may be a review role, the field value may be a role name of the reviewer in the parent work item, if there are multiple role names, a plurality of role names may be displayed, and if there are no role, a "-" may be displayed. The column header of the second table column may be a reviewer, and the field value thereof may be a configured responsible person or a node responsible person, each of which displays a row. The column header of the third table column may be a review conclusion, and the field value may be a node completion conclusion on the configured node, and may determine the editing authority of the current user according to the node logic. The column header of the fourth table column may be a review opinion, and the field value may be a node completion opinion on the configured node, and the editing authority of the current user is judged according to the node logic. The column header of the fifth table column may be a review operation, the field value may be a node completion operation button on the configured node, the editing authority of the current user is judged according to the node logic, and the line without the editing authority may display the current flow state of the review node. Optionally, the review role, the reviewer, the review conclusion, and the review opinion may also be screened.

As previously described, a clipping control may also be configured for a resource or sub-work item for deleting an unwanted resource or sub-work item. Thus, in some embodiments, a checkbox may be displayed on the leftmost side of each sub-work item, which may be deleted when the user 104B checkes the corresponding sub-work item and clicks the delete button.

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

As shown in FIG. 3C, review node 2 corresponds to a parent workitem 312, which includes a review element child workitem and a review question child workitem. And displaying column fields according to the configuration information, and displaying screening, sorting and grouping controls by the review element sub-work item and the review problem sub-work item. In some embodiments, the user 104B can also utilize the terminal device 102B at the application side to import the repository resources to automatically create child workitems and establish parent-child relationships with the current parent workitem.

In some embodiments, referring to FIG. 3C, if the status of the review node is in progress, the operation buttons (pass, fail, conditional pass) completed by the nodes in parent workitem 312 may be displayed in page 310 and only authorized roles may operate, with the unauthorized roles only being able to view, avoiding false operations of the unauthorized roles; if the status of the review node is not started or completed, the operation buttons (pass, fail, conditional pass) in the parent work item 312 may not be displayed in the page 310, avoiding misoperation of the user by presenting the buttons at inappropriate timing. The authorized role clicks the corresponding operation button, and can display prompt information of xx data modification to xx, and the node is completed, so that the user is prompted to operate successfully. In some embodiments, in response to the clicking of the operation button, the configured node circulation condition in the foregoing embodiments may be obtained first, and verification of the node circulation condition (including whether the checked necessary filling item is filled in and the configured node circulation condition) may be performed, and if not, a necessary filling item identifier or a prompt "don't meet the node circulation condition, xxx (first rule name not meeting the condition, for example, rule 1)" may be displayed, where the state of the operation button is not changed, and the state of the node is not changed.

In some embodiments, if the review flow of the review node involves multiple people participating and the node status is in progress, in response to user 104B (the current user) being the node responsible and user 104B not operating the operation buttons completed by the nodes in parent work item 312, the operation buttons completed by the nodes in parent work item 312 as in fig. 3C are displayed for operation by user 104B. If the node state 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 responsible person remaining not to operate, the configured node circulation condition in the foregoing embodiments may be obtained first, and verification of the node circulation condition (including whether the checked padding item is filled out and the configured node circulation condition) may be performed, and if not, the padding item identifier or the prompt "do not meet the node circulation condition, xxx (rule name that does not meet the condition for the first time, for example, rule 1)" may be displayed, where the state of the operation button is not changed, and the node state is not changed. In some embodiments, if any node responsible person does not operate the operation button completed by the node in the parent work item 312 of the page 310, after the node responsible person triggers the operation button, the node responsible person prompts that "xx data is modified to xx, and the single person is completed", and still displays all the operation buttons until all responsible persons of the node operate, the state of the node is displayed in the page 310, and the operation buttons are not displayed. In some embodiments, as shown in fig. 3C, when the parent workitem 312 of the page 310 includes a node principal, the node principal links with roles, and if the node principal is the principal, the user 104B may fill in each role it has in the parent workitem 312, so that linkage may be implemented based on a person linkage rule.

It will be appreciated that referring to fig. 1B, the review flow may be abstracted into three steps of review preparation, review conclusion, and review summary. Wherein review preparation may be used to determine the material to be reviewed (e.g., whether the delivery is ready) and to review according to which elements (e.g., the review elements may be adjusted by a cropping control); the review conclusion comprises review comments and review conclusion which are given by each review person; the review summary includes generating the final review conclusion (node completion conclusion).

The foregoing embodiment describes the presentation of relevant information of the review, and the following describes the review conclusion giving and summarizing rules and node circulation rules according to the summarized review conclusion.

In some embodiments, each person participating in the review process of the review node may draw his or her review conclusion in his or her collaborative management software.

Fig. 3D shows yet another schematic diagram of an exemplary page 320 in accordance with an embodiment of the present disclosure.

As shown in fig. 3D, the user 104B may present a page 320 in the collaborative management software of the terminal device 102B, where the page 320 summarizes all operational flow nodes of the user 104B. Illustratively, for item 1, clicking any operation button by the user 104B may generate a drop-down window 3202, and a node that the user 104B needs to operate under item 1 may be displayed in the window 3202, and the window 3202 further sets an operation button after each node for the user 104B to perform a shortcut operation. After the operations are completed, the system 100 may obtain review operation information for the one or more sub-work items for each review node to aggregate the review results. And then determining the node completion conclusion and the circulation state of the evaluation node according to the evaluation operation information.

In some embodiments, determining the node completion conclusion and the circulation state of the evaluation node according to the evaluation operation information comprises: acquiring a node completion conclusion rule of the evaluation node; and determining the node completion conclusion of the evaluation node according to the evaluation operation information and the node completion conclusion rule, so that the node completion conclusion can be automatically summarized. Optionally, specific completion information of the node responsible person can be displayed in the page, wherein the node completion conclusion and the node completion opinion can be displayed by adopting independent columns.

In some embodiments, determining the node completion conclusion and the circulation state of the evaluation node according to the evaluation operation information comprises: acquiring a completion circulation condition of the evaluation node; and determining the circulation state of the evaluation node according to the evaluation operation information, the node completion conclusion, the completion circulation condition and the node circulation state calculation rule, so that the automatic calculation of the node circulation state can be realized.

For example, in some embodiments, when the user 104B clicks the operation button, verification may be performed according to the node circulation condition, and if the condition is met, the operation corresponding to the operation button may be completed, then it is determined whether the review node is completed (both the node responsible person and the review person complete the operation), if not, a reminder is given to the corresponding node responsible person or the review person who does not complete the operation, and when the review node is completed, the circulation of the review node is calculated according to the node circulation state calculation rule, and the next node circulation is performed.

According to the embodiment, the flow configuration and management method provided by the embodiment of the disclosure automatically creates the work items and fills part of fields based on the resources, so that a user does not need to manually create and fill the work items, and the operation is simpler, more convenient and smoother.

It should be noted that the method of the embodiments of the present disclosure may be performed by a single device, such as a computer or a server. The method of the embodiment can also be applied to a distributed scene, and is completed by mutually matching a plurality of devices. In the case of such a distributed scenario, one of the devices may perform only one or more steps of the methods of embodiments of the present disclosure, the devices interacting with each other to accomplish the methods.

It should be noted that the foregoing describes some embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments described above and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Fig. 4A shows a flow diagram of an exemplary method 400 provided by an embodiment of the present disclosure. The method 400 may be used to process configuration of items. Alternatively, the method 400 may be implemented by the terminal device 102A of fig. 1A alone or by the system 100 of fig. 1A.

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

At step 402, a review node (e.g., review node 2 of FIG. 2A) of the target flow is determined.

At step 404, one or more resources (e.g., resources 2, 4, 7 of FIG. 2C) associated with the review node are acquired.

At step 406, one or more sub-work items for review are created for the review node based on the one or more resources, at least some of the fields in the one or more sub-work items being populated with field values based on the one or more resources (e.g., the review element work item of FIG. 2F and its field values).

According to the flow configuration method provided by the embodiment of the disclosure, the work items are automatically created based on the resources and part of fields are filled, so that a user does not need to manually create and fill the work items, and the operation is simpler, more convenient and smoother.

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

Receiving an instruction for adding a sub-work item to a review node based on a resource;

Acquiring a resource list from a resource library and displaying the resource list (refer to fig. 2C);

One or more resources associated with the review node are obtained according to an add instruction for one or more resources in the resource list (e.g., to pick up the corresponding resources 2, 4, 7).

Therefore, the resource list is automatically displayed for adding, and the use is more convenient.

In some embodiments, the method further comprises:

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

In response to the first configuration button being triggered, displaying a visible condition configuration window (e.g., window 208 of fig. 2E) of the child work item, the visible condition configuration window including a first configuration item (e.g., configuration items 2082, 2084 of fig. 2E) for configuring a visible condition;

And in response to receiving a configuration completion instruction, determining a visible condition of the sub-work item according to the configuration information of the first configuration item, and displaying the sub-work item when the visible condition is met.

Therefore, by setting the visible conditions, screening can be performed based on the visible conditions when the sub-work items are displayed, the fact that the sub-work items which are not needed to be used occupy the page space is avoided, and misoperation of a user is avoided.

In some embodiments, the method further comprises:

Displaying a second configuration button (e.g., configuration button 204B of fig. 2B) in the page for configuring the child work item form view;

In response to the second configuration button being triggered, displaying a form view configuration window (e.g., window 210 of FIG. 2F) of the one or more child work items, the form view configuration window including a form view preview area 210A including a preview view of a form view of the one or more child work items generated based on a currently selected form column and a form column resource list located on a side of the form view preview area, the form column resource list including a plurality of form column resources for adding respective form columns in the form view of the one or more child work items;

And responding to an adding instruction aiming at a target table column resource in a plurality of table column resources, and adding a preview table column corresponding to the target table column resource in the preview image.

In this way, the selectable table columns of the table view are displayed by using the table column resource list, and the table view can be configured in a dragging mode and the like, so that the table view is convenient to use.

In some embodiments, the list of tabular column resources includes review conclusion tabular column resources;

responding to an adding instruction for a target table column resource in a plurality of table column resources, adding a preview table column corresponding to the target table column resource in the preview graph, wherein the adding instruction comprises the following steps:

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

Therefore, by configuring the review conclusion table column for the table view, a user can conveniently give or view the review conclusion, and the working efficiency is improved.

In some embodiments, the method further comprises:

Displaying a third configuration button (e.g., configuration button 204C of fig. 2B) for configuring the person linkage rules of the child work item in the page;

In response to the third configuration button being triggered, displaying a person linkage rules configuration window (e.g., window 212 of fig. 2H) of the one or more child work items, the person linkage rules configuration window including a second configuration item 2122 for configuring a linkage condition and a third configuration item 2124 for configuring a set of linkage conditions;

and in response to receiving a configuration completion instruction, determining a personnel linkage rule of the sub-work item according to the configuration information of the second configuration item and/or the third configuration item, wherein the personnel linkage rule is used for adding a review person or a node responsible person corresponding to the personnel linkage rule to the one or more sub-work items when the personnel linkage rule is met.

Therefore, related personnel are automatically associated by utilizing personnel linkage rules, the working efficiency is improved, and meanwhile, the related personnel are prevented from being missed.

In some embodiments, the method further comprises:

Displaying a fourth configuration button (e.g., configuration button 2148 of fig. 2A) in the page for configuring the node completion conclusion of the review node;

In response to the fourth configuration button being triggered, displaying a node completion conclusion rule configuration window (e.g., window 216 of fig. 2I) of the review node, the node completion conclusion rule configuration window including fourth configuration items 2162, 2164 for configuring node completion conclusion rules;

Therefore, the node completion conclusion can be automatically calculated by configuring the node completion conclusion rule, so that conclusion summarization is completed, manual calculation is not needed by a user, and the working efficiency is improved.

In some embodiments, the method further comprises:

Displaying a fifth configuration button (e.g., configuration button 218 of fig. 2J) in the page for configuring the complete flow condition of the review node;

In response to the fifth configuration button being triggered, displaying a completion flow condition configuration window (e.g., window 220 of fig. 2K) of the review node, the completion flow condition configuration window including a fifth configuration item 2202 for configuring a completion flow condition of the review node;

And in response to receiving a configuration completion instruction, determining a completion circulation condition of the evaluation node according to the configuration information of the fifth configuration item, wherein the completion circulation condition is used for determining whether the evaluation node can circulate or not according to the completion circulation condition.

Fig. 4B shows a flow diagram of an exemplary method 410 provided by an embodiment of the present disclosure. The method 410 may be used to process manage items. Alternatively, the method 410 may be implemented by the terminal device 102B of fig. 1A alone or by the system 100 of fig. 1A.

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

At step 412, configuration information for the configured target flow is obtained using any embodiment or arrangement of embodiments of the method 400 as described;

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

According to the flow management method provided by the embodiment of the disclosure, the work items are automatically created based on the resources and part of fields are filled, so that a user does not need to manually create and fill the work items, and the operation is simpler, more convenient and smoother.

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

obtaining visible conditions of the sub-work items;

Displaying one or more of the sub-work items satisfying the visual condition.

Therefore, the sub-work items meeting the visible conditions are displayed, the sub-work items not meeting the visible conditions are hidden, on one hand, page space can be saved, on the other hand, the user is prevented from spending effort on the sub-work items which do not need to be reviewed, and the work efficiency is improved.

acquiring personnel linkage rules of the sub-work items;

and displaying personnel information meeting the personnel linkage rule in the sub-work item.

In some embodiments, the method further comprises:

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

and determining a node completion conclusion and a circulation state of the evaluation node according to the evaluation operation information.

In some embodiments, determining the node completion conclusion and the circulation state of the evaluation node according to the evaluation operation information comprises:

acquiring a node completion conclusion rule of the evaluation node;

And determining the node completion conclusion of the evaluation node according to the evaluation operation information and the node completion conclusion rule.

acquiring a complete circulation condition and a node circulation state calculation rule of the evaluation node;

And determining the circulation state of the evaluation node according to the evaluation operation information, the node completion conclusion, the completion circulation condition and the node circulation state calculation rule.

Embodiments of the present disclosure also provide a computer device for implementing the above-described method 400 or method 410. Fig. 5 shows a hardware architecture diagram of an exemplary computer device 500 provided by an embodiment of the present disclosure. The computer device 500 may be used to implement the server 106 of fig. 1A, or the terminal devices 102A, 102B of fig. 1A. In some scenarios, the computer device 500 may also be used to implement the database server 108 of FIG. 1A.

As shown in fig. 5, the computer device 500 may include: processor 502, memory 504, network interface 506, peripheral interface 508, and bus 510. Wherein the processor 502, the memory 504, the network interface 506 and the peripheral interface 508 enable a communication connection therebetween within the computer device 500 via a bus 510.

The processor 502 may be a central processing unit (Central Processing Unit, CPU), an image processor, a neural Network Processor (NPU), a Microcontroller (MCU), a programmable logic device, a Digital Signal Processor (DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), or one or more integrated circuits. The processor 502 may be used to perform functions related to the techniques described in this disclosure. In some embodiments, processor 502 may also include multiple processors integrated as a single logical component. For example, as shown in fig. 5, the processor 502 may include a plurality of processors 502a, 502b, and 502c.

Memory 504 may be configured to store data (e.g., instructions, computer code, etc.). As shown in fig. 5, the data stored by the memory 504 may include program instructions (e.g., program instructions for implementing the method 400 or method 410 of embodiments of the present disclosure) as well as data to be processed (e.g., the memory may store configuration files of other modules, etc.). The processor 502 may also access program instructions and data stored in the memory 504 and execute the program instructions to perform operations on the data to be processed. Memory 504 may include volatile storage or nonvolatile storage. In some embodiments, memory 504 may include Random Access Memory (RAM), read Only Memory (ROM), optical disks, magnetic disks, hard disks, solid State Disks (SSD), flash memory, memory sticks, and the like.

The network interface 506 may be configured to provide the computer device 500 with communications with other external devices via a network. The network may be any wired or wireless network capable of transmitting and receiving data. For example, the network may 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 of the foregoing. It will be appreciated that the type of network is not limited to the specific examples described above.

Peripheral interface 508 may be configured to connect computer apparatus 500 with one or more peripheral devices to enable information input and output. For example, the peripheral devices may include input devices such as keyboards, mice, touchpads, touch screens, microphones, various types of sensors, and output devices such as displays, speakers, vibrators, and indicators.

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

It should be noted that, although the architecture of the computer device 500 described above illustrates only the processor 502, the memory 504, the network interface 506, the peripheral interface 508, and the bus 510, in a specific implementation, the architecture of the computer device 500 may also include other components necessary to achieve proper operation. Moreover, those skilled in the art will appreciate that the architecture of the computer device 500 described above may include only the components necessary to implement the disclosed embodiments, and not all of the components shown in the figures.

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

A determination module 602 configured to: and determining a review node of the target flow.

An acquisition module 604 configured to: one or more resources associated with the review node are obtained.

A creation module 606 configured to: one or more sub-work items for review are created for the review node based on the one or more resources, at least some of the fields in the one or more sub-work items being populated with field values based on the one or more resources.

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

Acquiring a resource list from a resource library and displaying the resource list;

One or more resources associated with the review node are obtained according to an add instruction for one or more resources in the resource list.

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

displaying the one or more sub-work items in a page, wherein a first configuration button is displayed on one side of the sub-work items;

Responsive to the first configuration button being triggered, displaying a visible condition configuration window of the child work item, the visible condition configuration window including a first configuration item for configuring a visible condition;

In some embodiments, the display module is configured to:

Displaying a second configuration button for configuring the child work item form view in the page;

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

a display module configured to:

And responding to an adding instruction aiming at the review list resource, adding a review conclusion preview list corresponding to the review list resource in the preview image, wherein the review conclusion preview list comprises a first preview list corresponding to a review role, a second preview list corresponding to a review person, a third preview list corresponding to a review conclusion, a fourth preview list corresponding to a review opinion and a fifth preview list corresponding to a review operation.

In some embodiments, the display module is configured to:

Displaying a third configuration button for configuring personnel linkage rules of the sub-work items in the page;

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

And in response to receiving a configuration completion instruction, determining a personnel linkage rule of the sub-work item according to the configuration information of the second configuration item and/or the third configuration item, wherein the personnel linkage rule is used for adding a review personnel corresponding to the personnel linkage rule to the one or more sub-work items when the personnel linkage rule is met.

In some embodiments, the display module is configured to:

displaying a fourth configuration button for configuring a node completion conclusion of the review node in a page;

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

In some embodiments, the display module is configured to:

Displaying a fifth configuration button for configuring the completion circulation condition of the review node in a page;

Responsive to the fifth configuration button being triggered, displaying a completion-flow-condition configuration window of the review node, the completion-flow-condition configuration window including a fifth configuration item for configuring a completion flow condition of the review node;

For convenience of description, the above devices are described as being functionally divided into various modules, respectively. Of course, the functions of the various modules may be implemented in the same one or more pieces of software and/or hardware when implementing the present disclosure.

The apparatus of the foregoing embodiments is configured to implement the corresponding method 400 in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein.

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

An acquisition module 702 configured to: acquiring configuration information of a configured target flow using any embodiment or arrangement of embodiments of the method 400 as described;

a display module 704 configured to: in response to a view instruction for a review node of the target flow, one or more sub-work items of the review node are displayed, at least some of the fields of the one or more sub-work items being populated with field values based on one or more resources associated with the review node.

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

obtaining visible conditions of the sub-work items;

Displaying one or more of the sub-work items satisfying the visual condition.

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

acquiring personnel linkage rules of the sub-work items;

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

acquiring a node completion conclusion rule of the evaluation node;

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

The apparatus of the foregoing embodiments is configured to implement the corresponding method 410 in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein.

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

The computer readable media of the present embodiments, including both permanent and non-permanent, removable and non-removable media, may be used to implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device.

The storage medium of the foregoing embodiments stores computer instructions for causing the computer to perform the method 400 or the method 410 described in any of the foregoing embodiments, and has the advantages of the corresponding method embodiments, which are not described herein.

Based on the same inventive concept, the present disclosure also provides a computer program product, corresponding to any of the embodiment methods 400 or 410 described above, comprising a computer program. In some embodiments, the computer program is executable by one or more processors to cause the processors to perform the described method 400 or method 410. Corresponding to the execution bodies to which the steps in the embodiments of the method 400 or the method 410 correspond, the processor that executes the corresponding step may belong to the corresponding execution body.

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

The computer program product of the above embodiment is configured to cause a processor to perform the method 400 or the method 410 according to any of the above embodiments, and has the advantages of the corresponding method embodiments, which are not described herein.

Those of ordinary skill in the art will appreciate that: the discussion of any of the embodiments above is merely exemplary and is not intended to suggest that the scope of the disclosure, including the claims, is limited to these examples; the technical features of the above embodiments or in the different embodiments may also be combined under the idea of the present disclosure, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in details for the sake of brevity.

Additionally, well-known power/ground connections to Integrated Circuit (IC) chips and other components may or may not be shown within the provided figures, in order to simplify the illustration and discussion, and so as not to obscure the embodiments of the present disclosure. Furthermore, the devices may be shown in block diagram form in order to avoid obscuring the embodiments of the present disclosure, and this also accounts for the fact that specifics with respect to implementation of such block diagram devices are highly dependent upon the platform on which the embodiments of the present disclosure are to be implemented (i.e., such specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the disclosure, it should be apparent to one skilled in the art that embodiments of the disclosure can be practiced without, or with variation of, these specific details. Accordingly, the description is to be regarded as illustrative in nature and not as restrictive.

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

The disclosed embodiments are intended to embrace all such alternatives, modifications and variances which fall within the broad scope of the appended claims. Accordingly, any omissions, modifications, equivalents, improvements, and the like, which are within the spirit and principles of the embodiments of the disclosure, are intended to be included within the scope of the disclosure.

Claims

1. A process configuration method, comprising:

Determining a review node of the target flow;

obtaining one or more resources associated with the review node;

2. The method of claim 1, wherein acquiring one or more resources associated with the review node comprises:

3. The method of claim 1, wherein the method further comprises:

4. The method of claim 1, wherein the method further comprises:

5. The method of claim 4, wherein the list of tabular column resources includes review conclusion tabular column resources;

6. The method of claim 1, wherein the method further comprises:

7. The method of claim 1, wherein the method further comprises:

8. The method of claim 1, wherein the method further comprises:

9. A process management method, comprising:

acquiring configuration information of a target flow configured to be completed by the method according to any one of claims 1 to 8;

10. The method of claim 9, wherein displaying one or more sub-work items of the review node comprises:

obtaining visible conditions of the sub-work items;

Displaying one or more of the sub-work items satisfying the visual condition.

11. The method of claim 9, wherein displaying one or more sub-work items of the review node comprises:

acquiring personnel linkage rules of the sub-work items;

12. The method of claim 9, wherein the one or more sub-work items comprise a review conclusion table column comprising at least one of a first table column corresponding to a review role, a second table column corresponding to a reviewer, a third table column corresponding to a review conclusion, a fourth table column corresponding to a review opinion, and a fifth table column corresponding to a review operation.

13. The method of claim 12, wherein the method further comprises:

14. The method of claim 13, wherein determining node completion conclusions and circulation states for the review node based on the review operation information comprises:

acquiring a node completion conclusion rule of the evaluation node;

15. The method of claim 14, wherein determining node completion conclusions and circulation states for the review node based on the review operation information comprises:

16. A flow configuration apparatus comprising:

17. A flow management apparatus comprising:

an acquisition module configured to: acquiring configuration information of a target flow configured to be completed by the method according to any one of claims 1 to 8;

18. A computer device comprising one or more processors, 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 of any of claims 1-15.

19. 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 of any of claims 1 to 15.

20. A computer program product comprising one or more computer programs which, when executed by one or more processors, implement the steps of the method of any of claims 1 to 15.