View generation method, apparatus, electronic device and storage medium

Abstract

This disclosure provides a view generation method, apparatus, electronic device, and storage medium. The method includes: when view transformation conditions are met, traversing the node content and node dependencies of each execution node in the execution flowchart; generating a target swimlane view consistent with swimlane format based on the node dependencies, the node execution roles in the node content, and / or the project stages corresponding to the nodes; wherein the target swimlane view includes cross-display elements, and the cross-display elements are consistent with the processing content of each execution node. Through the technical solution of this disclosure, the clarity and standardization of project flow display are improved.

Description

Technical Field

[0001] This disclosure relates to project management technology, and more particularly to a view generation method, apparatus, electronic device, and storage medium. Background Technology

[0002] Currently, many companies generate a large amount of information at various stages of the new product development process, from project initiation to final mass production. This includes development requirements, product design documents, and project process files. By establishing project flowcharts in project management, the entire project's operation can be visualized.

[0003] However, due to the limited display method and poor data correlation of project flowcharts, if the number of nodes is large, the completeness and clarity of the project flowchart cannot be guaranteed, which will lead to a poor user experience. Summary of the Invention

[0004] This disclosure provides a view generation method, apparatus, electronic device, and storage medium to achieve the technical effect of improving the clarity and standardization of project process display.

[0005] In a first aspect, embodiments of this disclosure provide a view generation method, the method comprising:

[0006] When the view transformation conditions are met, traverse the node content and node dependencies of each execution node in the execution flowchart;

[0007] Based on the node dependencies, the node execution roles and / or the project stages corresponding to the nodes in the node content, a target swimlane view consistent with the swimlane format is generated.

[0008] The target swimlane view includes cross-display elements, which are consistent with the processing content of each execution node.

[0009] Secondly, embodiments of this disclosure also provide a view generation apparatus, the apparatus comprising:

[0010] The execution flowchart traversal module is used to traverse the node content and node dependencies of each execution node in the execution flowchart when the view transformation conditions are met.

[0011] The target swimlane view generation module is used to generate a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content, and / or the project stages corresponding to the nodes.

[0012] The target swimlane view includes cross-display elements, which are consistent with the processing content of each execution node.

[0013] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0014] One or more processors;

[0015] Storage device for storing one or more programs.

[0016] When the one or more programs are executed by the one or more processors, the one or more processors implement the view generation method as described in any of the embodiments of this disclosure.

[0017] Fourthly, embodiments of this disclosure also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the view generation method as described in any of the embodiments of this disclosure.

[0018] The technical solution of this disclosure, by traversing the node content and node dependencies of each execution node in the execution flowchart when the view transformation conditions are met, and generating a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content and / or the project stage corresponding to the node, solves the problem of poor completeness and clarity when using the execution flowchart, and achieves the technical effect of improving the clarity and standardization of the project process display. Attached Figure Description

[0019] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0020] Figure 1 This is a schematic flowchart of a view generation method provided in an embodiment of the present disclosure;

[0021] Figure 2 This is a schematic diagram illustrating an example of adding a node corresponding to a project stage, as provided in an embodiment of this disclosure.

[0022] Figure 3 This is a schematic diagram illustrating another project stage for adding nodes, as provided in an embodiment of this disclosure.

[0023] Figure 4 A schematic diagram of an input box pop-up layer corresponding to a node in a project stage provided in an embodiment of this disclosure;

[0024] Figure 5 This is a schematic diagram illustrating an embodiment of adding a node execution role provided in this disclosure;

[0025] Figure 6This is a schematic diagram illustrating the addition of a sub-role as provided in an embodiment of this disclosure;

[0026] Figure 7 This is a schematic diagram of an embodiment of the present disclosure that does not include a swimlane node;

[0027] Figure 8 This is a schematic diagram illustrating the editing of cross-display elements provided in an embodiment of the present disclosure;

[0028] Figure 9 This is a schematic diagram of a view generation device provided in an embodiment of the present disclosure;

[0029] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0030] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0031] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0032] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0033] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0034] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0035] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0036] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0037] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0038] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0039] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0040] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0041] Figure 1 This is a flowchart illustrating a view generation method provided in an embodiment of the present disclosure. This embodiment is applicable to situations where an execution flowchart is displayed clearly. The method can be executed by a view generation device, which can be implemented in software and / or hardware, or optionally by an electronic device, such as a mobile terminal, a PC, or a server.

[0042] like Figure 1 As shown, the method includes:

[0043] S110. When the view transformation condition is met, traverse the node content and node dependencies of each execution node in the execution flowchart.

[0044] The view transformation conditions can be the conditions for converting the execution flowchart into a swimlane view; specific conditions can be set according to actual needs. The execution flowchart can be a flowchart established during project management, consisting of various execution nodes and their dependencies, such as a tree diagram. An execution node can be each node in the execution flowchart. Node content can describe the execution role corresponding to the node and / or the project phase corresponding to the node. Node dependencies can include dependency information between execution nodes, such as descriptions of the parent node, child nodes, and parallel nodes of the execution node.

[0045] Specifically, when the view transformation conditions are met, the execution flowchart to be transformed is determined and processed. Each execution node in the execution flowchart is traversed to obtain its content and dependencies, which are then used to create the swimlane view.

[0046] Optionally, view transformation conditions may include at least one of the following:

[0047] The first type is when a view conversion control is detected.

[0048] The view transformation control can be a control used to transform the execution flowchart into a swimlane view, and can be a physical control or a virtual control.

[0049] Specifically, when a view transformation control is detected to be triggered, the execution flowchart is determined so that a view transformation can be performed on the execution flowchart.

[0050] For example, view transformation controls are configured in each execution flowchart. When a view transformation is required, the user can trigger the view transformation control to transform the current execution flowchart.

[0051] The second type is when the number of execution nodes arranged in parallel in the execution flowchart is greater than a preset threshold.

[0052] In this approach, execution nodes belonging to the same parent node are arranged in parallel. A preset quantity threshold, set according to requirements, is used to determine whether the execution flowchart can be converted into a swimlane view.

[0053] Specifically, the number of parallel execution nodes in the execution flowchart is judged. If the number of parallel execution nodes is greater than a preset threshold, it indicates that the display effect of the execution flowchart is not good. The execution flowchart is then converted into a swimlane view to improve the display effect.

[0054] S120. Based on node dependencies, node execution roles in node content, and / or the corresponding project stage of the node, generate a target swimlane view consistent with the swimlane format.

[0055] The target swimlane view includes cross-tab elements, which correspond to the processing content of each execution node. These cross-tab elements can be nodes at the intersection of horizontal and vertical swimlanes in the target swimlane view. The processing content can be the specific execution event corresponding to the current execution node, such as team building or quality planning. The node execution role can be the role handling the execution node, such as project manager, structure manager, or service representative. The node's corresponding project stage can be content describing the various stages and states in the project process, such as the concept stage, planning stage, and development stage. The target swimlane view can be a swimlane view corresponding to the execution flowchart.

[0056] Specifically, the order of swimlanes in the target swimlane view can be automatically determined based on some information of the nodes, or the order of swimlanes in the target swimlane view can be set manually. Furthermore, the horizontal and vertical swimlanes can be determined based on the node execution role and / or the project stage corresponding to the node in the node content to construct the target swimlane view, and the content of the cross-display elements corresponding to the execution node in the target swimlane view can be determined based on the processing content of the execution node.

[0057] The technical solution of this disclosure, by traversing the node content and node dependencies of each execution node in the execution flowchart when the view transformation conditions are met, and generating a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content and / or the project stage corresponding to the node, solves the problem of poor completeness and clarity when using the execution flowchart, and achieves the technical effect of improving the clarity and standardization of the project process display.

[0058] Optionally, based on the above-disclosed embodiments, it further includes:

[0059] Create an execution flowchart and edit the processing content, node content, and node dependencies of each execution node in the execution flowchart.

[0060] The processing content is used to characterize the specific execution events of the execution node. The node content includes the node's execution role and / or the project stage corresponding to the node. Node dependencies can include dependency information between execution nodes, such as descriptions of the execution node's parent node, child nodes, and parallel nodes.

[0061] Specifically, an execution flowchart can be created for one or more projects, and each execution node can be created and edited within the flowchart according to the specific circumstances of the project. Furthermore, the processing content, node content, and node dependencies of the execution nodes can be edited to complete the creation of the execution flowchart.

[0062] Optionally, based on the above-disclosed embodiments, a target swimlane view consistent with the swimlane format can be generated by the following steps, according to node dependencies, node execution roles in the node content, and / or the project stage corresponding to the node:

[0063] Step 1: Based on the node's execution role and / or the project phase corresponding to the node, determine at least one horizontal swimlane and at least one vertical swimlane.

[0064] In this view, the horizontal lanes can be any row in the lane view. The vertical lanes can be any column in the lane view.

[0065] Specifically, horizontal and vertical swimlanes can be created based on the node's execution role and the corresponding project stage. For example, horizontal swimlanes can be created based on the node's execution role, and vertical swimlanes can be created based on the corresponding project stage; or, vertical swimlanes can be created based on the node's execution role, and horizontal swimlanes can be created based on the corresponding project stage. If the node content only contains the node's execution role or the corresponding project stage, then only horizontal or vertical swimlanes need to be created.

[0066] Alternatively, the determination of the transverse and longitudinal lanes can be done in the following ways:

[0067] The node's execution role is used as the horizontal information of the horizontal swimlane, and the project stage corresponding to the node is used as the vertical information of the vertical swimlane; based on the horizontal information, at least one horizontal swimlane is determined, and based on the vertical information, at least one vertical swimlane is determined.

[0068] The horizontal information can be the lane name information of the horizontal lane, and the vertical information can be the lane name information of the vertical lane.

[0069] Specifically, for each node's execution role, that node's execution role can be treated as horizontal information corresponding to a horizontal swimlane, and thus, a horizontal swimlane corresponding to that horizontal information can be created. For each node's corresponding project stage, that node's corresponding project stage can be treated as vertical information corresponding to a vertical swimlane, and thus, a vertical swimlane corresponding to that vertical information can be created.

[0070] Optionally, the horizontal information corresponds to the project stage of the node, and the vertical information corresponds to the execution role of the node.

[0071] Step 2: Based on the display information of the horizontal and vertical lanes, determine the cross-display elements.

[0072] The information displayed for the horizontal lanes can be horizontal, and the information displayed for the vertical lanes can be vertical.

[0073] Specifically, based on the display information of the horizontal and vertical lanes, the nodes at the intersection of each horizontal and vertical lane, i.e., the intersection display elements, can be determined, and then the processing content of the execution node corresponding to the intersection position can be determined.

[0074] Step 3: Based on the node dependencies, display the corresponding cross-display elements to obtain the target swimlane view.

[0075] Specifically, based on node dependencies, the positions of horizontal and / or vertical swimlanes can be adjusted, for example, placing the swimlane corresponding to the parent node before the swimlane corresponding to the child node. Furthermore, after constructing the target swimlane view, the processing content corresponding to each execution node is added to the corresponding cross-display element.

[0076] Optionally, if the corresponding project stage and / or node execution role of the current execution node cannot be found in the target swimlane view, horizontal and / or vertical swimlanes can be added to include the current execution node in the target swimlane view.

[0077] Specifically, it could be:

[0078] If the target swimlane view does not include the project stage corresponding to the currently executing node, and does not include the node's execution role, then an unincluded horizontal swimlane without role information is created in the target swimlane view to display the execution node in the unincluded horizontal swimlane.

[0079] The "unincluded role information" can be the node execution role corresponding to the currently executing node. The "unincluded horizontal swimlanes" can be the horizontal swimlanes corresponding to the "unincluded role information".

[0080] Specifically, if the target swimlane view does not include the project stage corresponding to the currently executing node, and does not include the node execution role, it means that the target swimlane view does not include the horizontal and vertical swimlanes corresponding to the currently executing node. Therefore, a horizontal swimlane can be created in the target swimlane view based on the role information that is not included, i.e., a horizontal swimlane that is not included.

[0081] If the target swimlane view does not include the project stage corresponding to the currently executing node, but includes the node execution role, then the project stage corresponding to the node will be used as the vertical information in the target swimlane view, and a new vertical swimlane will be added.

[0082] Specifically, if the target swimlane view does not include the project stage corresponding to the current execution node, but includes the node execution role, it means that only the vertical swimlane corresponding to the current execution node needs to be added. Therefore, the project stage corresponding to the current execution node is determined, and the project stage corresponding to the node is used as the vertical information of the newly added vertical swimlane to complete the addition of the vertical swimlane.

[0083] Optionally, horizontal and vertical swimlanes can be added to the target swimlane view. If the horizontal swimlanes in the target swimlane view correspond to the node's execution role, and the vertical swimlanes correspond to the node's project phase, then the horizontal and vertical swimlanes can be added in the following ways:

[0084] When a vertical state swimlane corresponding to the project stage of the node is detected to be added, a vertical state swimlane is added to the far right of the target swimlane view.

[0085] Among them, the longitudinal state swimlanes correspond to the project stages corresponding to the added nodes.

[0086] Specifically, when it is detected that a vertical state swimlane corresponding to the project stage of the node is to be added, the vertical information of the vertical state swimlane to be added can be determined, and the vertical state swimlane corresponding to the determined vertical information can be added to the far right of the target swimlane view.

[0087] When a horizontal role swimlane corresponding to the node's execution role is detected, a horizontal role swimlane is added to the bottom of the target swimlane view.

[0088] The horizontal role swimlane corresponds to the role executed by the added node.

[0089] Specifically, when it is detected that a horizontal role swimlane corresponding to the node execution role is to be added, the horizontal information of the horizontal state swimlane to be added can be determined, and the horizontal state swimlane corresponding to the determined horizontal information can be added at the bottom of the target swimlane view.

[0090] For example, if the current execution node is a brand new execution node, only the preset state, such as the "Start" state, is displayed, and no node execution role is shown. The preset current execution node can be placed in the "Not Included in Swimlane" node field. If the current execution node has been broken down into the node's corresponding project stage and node execution role, then the corresponding swimlanes for the node's corresponding project stage and node execution role are determined and displayed in the target swimlane view. When the node's corresponding project stage is not in the target swimlane view, it is determined whether the current execution node has a configured node execution role. If it has, a swimlane corresponding to the node's corresponding project stage is added; if it has not, no swimlane corresponding to the node's corresponding project stage is added, and the current execution node is placed in the "Not Included in Swimlane" node field. If the current execution node already has a corresponding project stage or execution role, and then adds nodes associated with execution roles or corresponding project stages, these swimlanes will be added to the target swimlane view (if and only if the current execution node has a configured execution role; otherwise, swimlanes corresponding to the project stage will not be added). When adding a swimlane corresponding to a project stage, the last node among all preceding nodes under that project stage will be identified as having its corresponding project stage, and a new swimlane will be inserted to the right of that project stage, i.e., the swimlane corresponding to the current execution node's project stage. When adding a swimlane corresponding to a execution role, it will be added directly at the bottom. If an execution node in the "Not Included in Swimlanes" column changes its corresponding execution role, and the corresponding project stage of that execution node does not exist in the target swimlane view, swimlanes corresponding to that execution role and the project stage will be added automatically and synchronously. In this embodiment of the disclosure, there is only logic for automatically adding swimlanes, and no logic for automatically deleting or hiding swimlanes. That is, when the last execution node under a swimlane is removed from the swimlane, the swimlane is not automatically deleted.

[0091] For example, when the cursor moves to an existing swimlane, a "Create Node" entry appears. Clicking it brings up a node name input box. When the node is created successfully, a node information sidebar pops up on the right side of the interface. The information is filled in according to the current cursor position. For example, if the current swimlane is the node execution role swimlane, the node leader will be filled in with "Specified Role" by default; the current status of the project stage corresponding to the node will be automatically filled in; the preceding node will be the first node in the process by default.

[0092] For example, a diagram showing the addition of nodes corresponding to different project stages is shown below. Figure 2As shown, clicking the "Add Status" entry on the far right of the swimlane expands the drop-down menu. The options can be any of the options pre-set in the status management section of field management. Clicking any value will add a swimlane with the same name to the far right. The last option in the drop-down menu is "Create Status." Clicking it will bring up an input box pop-up for adding a new status. Clicking "Confirm?" will display a message saying "This status has been synchronously added to the {Work Item Type} status option," and the swimlane will appear synchronously on the target swimlane view. Another illustration of adding nodes corresponding to project stages is shown below. Figure 3 As shown, when the cursor moves to the middle of the two vertical swimlanes, a "+" button appears, indicating the insertion state. Clicking it expands the drop-down menu, with the same content as clicking "Add State" on the far right of the swimlane. A diagram illustrating the input box pop-up corresponding to the node in the project stage is shown below. Figure 4 As shown. Additionally, under each node's corresponding project stage swimlane, the expected completion time of the last executed node can be displayed as the completion time for that stage. In practical applications, users can edit and save the expected completion time of each node on the display interface. When the user moves the cursor over that expected completion time, a message will appear: "Estimated completion time for this status."

[0093] An example diagram illustrating the addition of a node execution role is shown below. Figure 5 As shown, clicking the "Add Role" entry at the bottom of the swimlane expands the drop-down menu. The options can be all those pre-set in the role management section of field management. Clicking any value adds a swimlane with the same name at the bottom. The last option in the drop-down menu is "Create Role." Clicking it brings up a pop-up for adding a role. After clicking "Create," a message appears saying "This role has been added to the {Work Item Type} role list," and the swimlane appears simultaneously on the target swimlane view. You can also move the cursor between two execution roles and determine the parent / child role to add based on the indentation position. A "+" button appears; clicking it expands the drop-down menu, which contains the same content as the "Add Role" entry at the bottom of the swimlane. Moving the cursor to the header of any role displays a "..." entry. Clicking it displays the "Add Child Role" entry, which contains the same content as the "Add Role" entry. Clicking it adds a child role below the current role, such as... Figure 6 As shown. Figure 6 The left side of each execution role (e.g., TR, DA) in the middle node list includes an arrow icon. Clicking the arrow icon expands or collapses the list of sub-roles; sub-roles are collapsed by default. A "Unassigned Roles" row can also be displayed at the bottom, showing execution nodes for roles that are not yet assigned.

[0094] An exemplary diagram excluding swimlane nodes is shown below. Figure 7As shown. If any swimlane in the target swimlane view does not support displaying all execution nodes (e.g., swimlane corresponding to node execution roles, several execution nodes with designated persons as responsible persons, and no node execution roles set), the hidden execution nodes will appear at the bottom of the panel and clustered as "Nodes Not Included in Swimlane"; if such nodes are not processed, they will not be visible to the user. Furthermore, both horizontal and vertical swimlanes without execution nodes can be set to show / hide. If an administrator adds an execution node and sets it to match a group in the hidden group area, that group will automatically be restored to the target swimlane view. The target swimlane view can display a message stating "Groups without nodes will be hidden on the user's side." During initialization, i.e., when no execution nodes are created, all project stages and node execution roles corresponding to all nodes can be fully enumerated.

[0095] Optionally, based on the above-disclosed embodiments, removal can also be performed on horizontal or vertical swimlanes. When removing a swimlane corresponding to a node's execution role, the entire swimlane can be deleted. When removing a swimlane corresponding to a project stage of a node, it cannot be removed directly; it is necessary to first determine whether the swimlane includes an execution node. If removal is performed while including an execution node, the process corresponding to the node's execution role will be disconnected. Therefore, a notification is required. Specifically, this could be:

[0096] When a removal operation is detected in the target swimlane view, and the removal operation corresponds to the project stage of the node, determine whether the project stage of the node includes an execution node.

[0097] The removal operation can be an operation to delete either the horizontal lane or the vertical lane.

[0098] Specifically, when a removal operation is detected in the target swimlane view, it is determined whether the removal operation corresponds to the project stage of the node. If not, it means that the removal operation corresponds to the node execution role and the swimlane can be removed. If so, it is further determined whether the swimlane of the project stage corresponding to the node contains an execution node in the target swimlane view, so as to determine whether to issue a reminder or remove the node.

[0099] If so, a pop-up message box containing the prompt information will appear.

[0100] The prompt message can be used to remind the user that the current swimlane cannot be directly deleted. The prompt message may include information such as "The project stage corresponding to the node cannot be removed. Please remove the execution node and try again."

[0101] Specifically, if so, it means that the swimlane corresponding to the project stage of the node contains an execution node, and it cannot be removed directly. At this time, a prompt box with prompt information will pop up to remind the user of the reason why it cannot be removed, and that the execution node can be removed first and then the swimlane can be removed.

[0102] If not, remove the swimlane corresponding to the project stage of the node to update the target swimlane view.

[0103] Specifically, if not, it means that the swimlane corresponding to the project stage of the node does not contain an execution node, and the removal operation can be performed directly. In this case, the swimlane corresponding to the project stage of the node is removed, and the swimlane view after the removal operation is used as the new target swimlane view.

[0104] For example, when the cursor moves to the header of the project stage corresponding to a node, a "..." entry appears, displaying the "Remove this status" option. If there are execution nodes under the project stage corresponding to that node, the project stage cannot be removed; "Remove this status" is grayed out and the message "Cannot be removed, please remove the node and try again" is displayed. If there are no execution nodes under the project stage corresponding to that node, the project stage can be removed; clicking "Remove this status" displays the message "Removal successful."

[0105] For example, when the cursor moves to the header of a node execution role, a "..." entry appears, displaying the "Remove this role" option. If the node execution role has child roles (execution nodes), removing the node execution role will also remove all child roles; if the node execution role has execution nodes, removing the role is equivalent to setting the "Person in Charge" configuration of the nodes under the node execution role to "Add by User"; clicking "Remove this role" will, if the node execution role has child roles, check if there are any execution nodes. If not, a secondary confirmation dialog will pop up: "Confirm removal of this role? Removing this role will remove all child roles under this role." Clicking "Confirm" will remove the node execution role and all child roles; if there are child roles, ... A secondary confirmation pop-up will appear: "Confirm removal of this role? 1. All child roles under this role will also be removed. 2. All nodes under this role will be moved to 'Nodes Not Included in Swimlane'." Click "Confirm," and the role and all child roles of this node will be removed, and all nodes will be added to the "Nodes Not Included in Swimlane" column. If the role of this node has no child roles but has nodes, a secondary confirmation pop-up will appear: "Confirm removal of this role? All nodes under this role will be moved to 'Nodes Not Included in Swimlane'." Click "Confirm," and all execution nodes will be added to the "Nodes Not Included in Swimlane" column. When there are no execution nodes under the project stage corresponding to this node (including the execution nodes corresponding to the project stage of this node in the "Nodes Not Included in Swimlane" column), the role of this node can be removed directly. Click "Remove this role," and a message "Removal successful" will appear.

[0106] Optionally, based on the above-disclosed embodiments, the positions of horizontal and / or vertical swimlanes in the target swimlane view can also be changed by dragging. When dragging a swimlane corresponding to a node's execution role, the entire swimlane can be moved. When dragging a swimlane corresponding to a project stage, the position cannot be moved directly; it is necessary to first determine whether there are any conflicts in the dependencies between the execution nodes at the current and target positions to avoid confusion in dependencies after the position is moved. Specifically, it can be:

[0107] When it is detected that the project stage corresponding to the target node is dragged from the current position to the target position in the target swimlane view, the dependencies between the execution nodes located between the current position and the target position are determined.

[0108] The target location can be the location to which the element is dragged, i.e., the location after the change.

[0109] Specifically, when it is detected that the project stage corresponding to the target node is dragged from the current position to the target position in the target swimlane view, the execution nodes corresponding to all swimlanes between the current position and the target position are determined, and the dependencies of these execution nodes are determined.

[0110] If the dependency conflicts with the target location of the project phase corresponding to the node, the target location will be set to a disabled location of the project phase corresponding to the target node, and a prompt message indicating that it cannot be placed will be displayed.

[0111] The disabled location can be a target location that cannot be placed.

[0112] Specifically, a conflict between a dependency and the target location of the corresponding project stage can occur due to issues such as a disordered execution order of nodes. If a dependency conflicts with the target location of the corresponding project stage, it means that the target node's corresponding project stage cannot be dragged from its current location to the target location. In this case, the target location is set as a disabled location for the target node's corresponding project stage, and a "Cannot be placed" message pops up to remind the user that the location cannot be moved.

[0113] For example, dragging and dropping the node execution role header can reorder the nodes; releasing the cursor completes the reordering. When dragged onto a node execution role (target role), the dragged node execution role becomes a child role of the target role. If the target role has child roles and they are currently collapsed, hovering over the target role for 1.5 seconds will automatically expand the child roles. The current node execution role can be dragged to any position in the child role list. Dragging and dropping the node corresponding to the project stage header can also reorder the nodes; releasing the cursor completes the reordering. If the dragged node's corresponding project stage has nodes that depend on nodes in the target location's corresponding project stage, and the change in state order conflicts with the node dependencies, the node execution role cannot be released to that position. The cursor will be disabled, and the message "Node dependency conflict, cannot be moved to this position" will be displayed.

[0114] Optionally, based on the above-disclosed embodiments, horizontal and / or vertical lanes can be added to the target lane view using pre-set controls.

[0115] When it is detected that the project stage control corresponding to the newly created node and / or the execution role control of the newly created node are triggered, add a horizontal swimlane and / or a vertical swimlane in the target swimlane view.

[0116] The control for the project stage corresponding to the newly created node can be a control used for the swimlane corresponding to the project stage of the newly created node. The control for the execution role of the newly created node can be a control used for the swimlane corresponding to the execution role of the newly created node.

[0117] Specifically, when it is detected that the project stage control corresponding to the newly created node and / or the execution role control of the newly created node are triggered, a horizontal swimlane and / or a vertical swimlane are added to the target swimlane view, that is, a swimlane corresponding to the project stage control corresponding to the newly created node and / or the execution role control of the newly created node is created.

[0118] Optionally, based on the above-disclosed embodiments, the cross-display elements in the target swimlane view can also be edited, specifically:

[0119] When a crossover element in the target swimlane view is detected, an edit box corresponding to the crossover element pops up, allowing you to update the information of the crossover element in the edit box.

[0120] The edit box can be a text box used for editing information, allowing users to edit the information of the cross-display elements. The cross-display elements can be nodes at the intersection of horizontal and vertical lanes in the target swimlane view, and can include node names, node information, etc.

[0121] Specifically, the triggering method for the cross-display element in the target swimlane view can be clicking the cross-display element, or hovering the cursor for a preset time, etc., and is not specifically limited in this embodiment. When the cross-display element in the target swimlane view is detected, an editing box for editing the cross-display element can pop up, allowing the user to edit information in the editing box to update the information of the cross-display element.

[0122] Optionally, the content edited in the edit box can be the correspondence between the currently crossed element and other crossed elements. Furthermore, other crossed elements can be updated based on the update of the currently crossed element. Specifically, this could be:

[0123] Edit the correspondence between the currently crossed element and other crossed elements in the edit box, and execute the corresponding content based on the correspondence.

[0124] The content to be executed corresponds to the processing content of the execution nodes in the execution flowchart. This correspondence can be an association between the two, meaning the execution content of the currently displayed element is determined based on the execution content of other displayed elements, or vice versa.

[0125] Specifically, you can also edit the correspondence between the currently crossed element and other crossed elements in the edit box, so as to change the execution content of the crossed element corresponding to the edited correspondence.

[0126] For example, in the edit box, the current cross-display element A can be edited to X, and the correspondence between the previous cross-display element A and other cross-display elements B can be edited to B = A + 4. Then, the execution content of the other cross-display elements B is X + 4.

[0127] Optionally, the above-mentioned edit box can be displayed by triggering the "Schedule Default Relationship" in the cross-display element, or the above-mentioned edit box can be displayed by triggering the cross-display element.

[0128] For example, clicking on a node and its name (cross-displaying elements) will bring up a node information sidebar on the right side of the interface, allowing you to edit the node details; double-clicking on a node name will activate the node name editing mode, and you can save the edit by defocusing or pressing Enter.

[0129] When the operation of content editing is detected to be completed, the display position of the corresponding cross-display element in the target swimlane view is updated according to the corresponding relationship.

[0130] Specifically, when the operation of content editing is detected to be completed, such as when the completion control is triggered or when the Enter button is triggered, the content of the relevant cross-display elements can be determined according to the corresponding relationship, and the content of the corresponding display position in the target swimlane view can be updated based on this content.

[0131] An example, a diagram illustrating the editing of cross-display elements, is shown below. Figure 8 As shown. Within the same cell (cross-display elements), execution nodes are arranged by default according to their "Schedule Default Relationship - Estimated Completion Time". For example: If node A's estimated completion time is X, and node B's estimated completion time is X+3, then node B is to the right of node A; if node A's estimated completion time is C+1, and node B's estimated completion time is C+4, then node B is to the right of node A; if node A's estimated completion time is C+1, and node B's estimated completion time is D+4, then the estimated completion times of nodes C and D are searched. If they exist, the positions of nodes A and B are displayed according to the schedule default relationship; otherwise, the positions of nodes A and B are displayed according to their dependency order. If N estimated completion times appear in a cell, there will be at least N columns of nodes. When there is no "Schedule Default Relationship - Estimated Completion Time", the execution nodes are arranged according to the order of their startup dependencies by default. For example: if node B is the successor of node A, then node B is to the right of node A; if both node B and node A are first-degree successors of node C, then node B and node A are arranged vertically; if node B is the successor of node A, the two nodes are not under the same role and node B has no predecessor node under that role, then node B is located in the column to the right of node A.

[0132] For example, dragging and dropping execution nodes allows for reordering. Reordering changes the "Node Owner - Specified Role" value or "Node Association Status" value (node ​​execution role or corresponding project stage) of the execution node based on the drop point. The reordering conditions for execution nodes are as follows: multiple execution nodes in a linear chain with dependencies cannot be swapped; two execution nodes with a pre-defined scheduling relationship cannot be swapped; parallel nodes without dependencies can have their order changed. When an execution node is dragged to an area that cannot be reordered, the cursor is disabled, and the message "Due to node dependency / expected completion time conflict, this node cannot be moved into this area" appears.

[0133] For example, an entry for "Node Position Description" can be displayed in the target swimlane view, with the prompt text "The relative positions of the nodes on the current interface are only simulated data drawn based on the estimated completion time or dependencies of the nodes. The user-side effect is based on the work item instance data."

[0134] Optionally, the dependencies between execution nodes can be displayed in the target swimlane view. Specifically, the dependency lines of each execution node in the target swimlane view can be displayed transparently in the display interface.

[0135] When the cursor is detected to correspond to an execution node, the first-level dependency line corresponding to the execution node is displayed.

[0136] Among them, the first-level dependency line can be the connection line between the execution node and the connected node corresponding to the execution node. The connected node can include the parent node and the child node.

[0137] Specifically, when the cursor is detected to correspond to an execution node, the first-level dependency lines of that execution node, which are currently transparent, can be made non-transparent.

[0138] When the dependency display control is triggered, the dependency lines of each execution node in the target swimlane view are displayed.

[0139] The dependency display control can be a control used to display dependency lines at all levels in the target swimlane view.

[0140] Specifically, when the dependency display control is triggered, the transparent dependency lines in the display interface can be adjusted to be non-transparent so that users can intuitively see the dependencies between the execution nodes.

[0141] For example, when the "Show Dependencies" switch is turned on, all dependency lines between execution nodes are displayed (dependency lines in the target swimlane view); when the switch is turned off, selecting an execution node or moving the cursor over an execution node displays all preceding and following dependency lines for that execution node (first-level dependency lines corresponding to the execution node). When the cursor moves over an execution node, the dependency connection points on both sides of that execution node are displayed. When the cursor moves to a connection point, a prompt "Drag to establish dependency" appears. Dragging the connection line to the target execution node establishes the preceding and following dependency relationship between the two execution nodes.

[0142] Optionally, based on the above-disclosed embodiments, the execution flowchart corresponding to the target swimlane view can also be adjusted according to the target swimlane view. Specifically, it can be:

[0143] When a modification to a cross-show element is detected in the target swimlane view, the execution flowchart is updated in conjunction with the cross-show element.

[0144] Specifically, when a cross-display element is detected to be modified in the target swimlane view, the execution node to be changed in the execution flowchart can be determined based on the modified cross-display element, and the information of the execution node can be updated based on the information of the cross-display element to complete the linkage update of the execution flowchart.

[0145] Based on the above-disclosed embodiments, each execution node can be marked with a status such as "not started", "in progress", "completed", "completed - risk", "completed - delayed", "in progress - delayed", etc. Among them, "completed - risk" means that the execution node has been completed, but there are unfinished tasks under the execution node.

[0146] Based on the above-disclosed embodiments, the execution node can be displayed in the target swimlane view according to the project stage and execution role of the node configured in the administrator backend. In the target swimlane view, execution nodes are arranged by default according to their estimated completion time. For example, if node A's estimated completion time is the 10th and node B's estimated completion time is the 13th, then node B is to the right of node A. The minimum number of columns for execution nodes corresponds to the number of estimated completion times across all execution nodes. When no estimated completion time is set, execution nodes are arranged by default according to their startup dependency order. For example, if node B is a successor node of node A, then node B is to the right of node A; if both node B and node A are first-degree successors of node C, and neither node B nor node A has an estimated completion time, or only one of them has an estimated completion time, then nodes B and A are arranged vertically.

[0147] Based on the above-disclosed embodiments, when the cursor moves to the node name of an execution node, a node details pop-up appears. Clicking on a regular execution node displays node details at the bottom; when the execution node is at the bottom of the page, the page pushes up; clicking on other areas collapses the node details. When clicking on a dependency of an execution node with dependencies (i.e., the clicked execution node includes multiple nested sub-work items), if the work item instance of the execution node has already been created, the work item instance details page is opened directly. When clicking on an execution node with dependencies, if the work item instance has not been created, the cursor is disabled, and the message "The associated work item for this node has not yet been created" is displayed. Furthermore, the node details and the ongoing execution node cannot be clicked to complete the process, with the message "The associated work item for this node has not yet been created."

[0148] Figure 9 This is a schematic diagram of a view generation device provided in an embodiment of the present disclosure, as shown below. Figure 9 As shown, the device includes: an execution flowchart traversal module 210 and a target swimlane view generation module 220.

[0149] The execution flowchart traversal module 210 is used to traverse the node content and node dependencies of each execution node in the execution flowchart when the view transformation conditions are met. The target swimlane view generation module 220 is used to generate a target swimlane view consistent with the swimlane form based on the node dependencies, the node execution roles in the node content and / or the project stage corresponding to the node. The target swimlane view includes cross-display elements, which are consistent with the processing content of each execution node.

[0150] Optionally, the view transformation condition includes at least one of the following: detecting that a view transformation control is triggered; detecting that the number of execution nodes arranged in parallel in the execution flowchart is greater than a preset number threshold; wherein, execution nodes belonging to the same parent node are regarded as execution nodes arranged in parallel.

[0151] Optionally, the device further includes: an execution flowchart creation module, used to create the execution flowchart and edit the processing content, node content, and node dependency relationships of each execution node in the execution flowchart; wherein, the processing content is used to characterize the specific execution events of the execution node, the node content includes the node execution role and / or the project stage corresponding to the node, and the node dependency relationships include dependency information between each execution node.

[0152] Optionally, the target swimlane view generation module 220 is specifically used to determine at least one horizontal swimlane and at least one vertical swimlane based on the node execution role and / or the project stage corresponding to the node; determine cross-display elements based on the display information of the horizontal swimlane and the display information of the vertical swimlane; and display the corresponding cross-display elements according to the node dependency relationship to obtain the target swimlane view.

[0153] Optionally, the target swimlane view generation module 220 is further configured to use the node execution role as the horizontal information of the horizontal swimlane and the project stage corresponding to the node as the vertical information of the vertical swimlane; determine at least one horizontal swimlane based on the horizontal information, and determine at least one vertical swimlane based on the vertical information.

[0154] Optionally, the device further includes: the horizontal information corresponds to the project stage corresponding to the node, and the vertical information corresponds to the execution role of the node.

[0155] Optionally, the device further includes: a node addition module, configured to: if the target swimlane view does not include the node-corresponding project stage of the currently executing node and does not include the node execution role, then create an unincluded horizontal swimlane in the target swimlane view to display the executing node in the unincluded horizontal swimlane; if the target swimlane view does not include the node-corresponding project stage of the currently executing node but includes the node execution role, then use the node-corresponding project stage as vertical information in the target swimlane view and add a vertical swimlane.

[0156] Optionally, the horizontal swimlanes of the target swimlane view correspond to node execution roles, and the vertical swimlanes correspond to node corresponding project stages. The device further includes: a swimlane addition module, used to add the vertical state swimlane corresponding to the node's corresponding project stage to the far right of the target swimlane view when the addition of the vertical state swimlane corresponding to the node's corresponding project stage is detected; wherein the vertical state swimlane corresponds to the added node's corresponding project stage; and to add the horizontal role swimlane corresponding to the node's execution role to the bottom of the target swimlane view when the addition of the horizontal role swimlane corresponding to the node's execution role is detected; wherein the horizontal role swimlane corresponds to the added node's execution role.

[0157] Optionally, the device further includes: a swimlane removal module, configured to, when a removal operation is detected in the target swimlane view and the removal operation corresponds to a node-corresponding project stage, determine whether the node-corresponding project stage includes an execution node; if so, pop up a prompt box including a prompt message; wherein the prompt message includes that the node-corresponding project stage cannot be removed, please remove the execution node and try again; if not, remove the swimlane corresponding to the node-corresponding project stage to update the target swimlane view.

[0158] Optionally, the device further includes: a drag-and-drop module, used to determine the dependency relationship between each execution node located between the current position and the target position when it is detected that the project stage corresponding to the target node is dragged from the current position to the target position in the target swimlane view; if the dependency relationship conflicts with the target position of the project stage corresponding to the node, the target position is set as the disabled position of the project stage corresponding to the target node, and a prompt message indicating that it cannot be placed is displayed.

[0159] Optionally, the device further includes: a node-corresponding project stage and / or node execution role creation module, used to add horizontal and / or vertical swimlanes in the target swimlane view when the triggering of the new node-corresponding project stage control and / or the new node execution role control is detected.

[0160] Optionally, the device further includes: a cross-display element update module, configured to pop up an edit box corresponding to the cross-display element when a cross-display element in the target swimlane view is detected, so as to update the information of the cross-display element in the edit box.

[0161] Optionally, the device further includes: a cross-display element display module, used to edit the correspondence between the current cross-display element and other cross-display elements in the editing box, so as to execute the execution content corresponding to the corresponding cross-display element based on the correspondence; wherein the execution content is consistent with the processing content of the execution node in the execution flowchart; when the operation of content editing is detected to be completed, the display position of the corresponding cross-display element in the target swimlane view is updated according to the correspondence.

[0162] Optionally, the dependency lines of each execution node in the target swimlane view are displayed transparently in the display interface; when the cursor is detected to correspond to an execution node, the first-level dependency line corresponding to the execution node is displayed; when the dependency display control is triggered, the dependency lines of each execution node in the target swimlane view are displayed.

[0163] Optionally, the apparatus further includes: an execution flowchart update module, used to update the execution flowchart in conjunction with the cross-display element when a modification of the cross-display element is detected in the target swimlane view.

[0164] The technical solution of this disclosure, by traversing the node content and node dependencies of each execution node in the execution flowchart when the view transformation conditions are met, and generating a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content and / or the project stage corresponding to the node, solves the problem of poor completeness and clarity when using the execution flowchart, and achieves the technical effect of improving the clarity and standardization of the project process display.

[0165] The view generation apparatus provided in this disclosure can execute the view generation method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of executing the method.

[0166] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0167] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Reference is made below. Figure 10It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 10 The diagram below shows the structure of the terminal device or server 300. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and vehicle terminals (e.g., vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 10 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0168] like Figure 10 As shown, the electronic device 300 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 into a random access memory (RAM) 303. The RAM 303 also stores various programs and data required for the operation of the electronic device 300. The processing unit 301, ROM 302, and RAM 303 are interconnected via a bus 304. An edit / output (I / O) interface 305 is also connected to the bus 304.

[0169] Typically, the following devices can be connected to I / O interface 305: input devices 306 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 307 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 308 including, for example, magnetic tapes, hard disks, etc.; and communication devices 309. Communication device 309 allows electronic device 300 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 10 An electronic device 300 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0170] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 309, or installed from storage device 308, or installed from ROM 302. When the computer program is executed by processing device 301, it performs the functions defined in the methods of embodiments of this disclosure.

[0171] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0172] The electronic device provided in this embodiment and the view generation method provided in the above embodiments belong to the same inventive concept. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0173] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the view generation method provided in the above embodiments.

[0174] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0175] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0176] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0177] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to:

[0178] The aforementioned computer-readable medium carries one or more programs. When the aforementioned one or more programs are executed by the electronic device, the electronic device: when the view transformation conditions are met, traverses the node content and node dependencies of each execution node in the execution flowchart; based on the node dependencies, and the node execution roles and / or the project stages corresponding to the nodes in the node content, generates a target swimlane view consistent with the swimlane format; wherein the target swimlane view includes cross-display elements, and the cross-display elements are consistent with the processing content of each execution node.

[0179] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0180] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0181] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0182] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0183] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0184] According to one or more embodiments of this disclosure, [Example 1] provides a view generation method, the method comprising:

[0185] When the view transformation conditions are met, traverse the node content and node dependencies of each execution node in the execution flowchart;

[0186] Based on the node dependencies, the node execution roles and / or the project stages corresponding to the nodes in the node content, a target swimlane view consistent with the swimlane format is generated.

[0187] The target swimlane view includes cross-display elements, which are consistent with the processing content of each execution node.

[0188] According to one or more embodiments of this disclosure, [Example 2] provides a view generation method, which further includes:

[0189] Optionally, the view transformation condition includes at least one of the following:

[0190] A view transition control was detected.

[0191] The number of execution nodes arranged in parallel in the execution flowchart is detected to be greater than a preset threshold.

[0192] In this approach, execution nodes belonging to the same parent node are arranged in parallel.

[0193] According to one or more embodiments of this disclosure, [Example 3] provides a view generation method, which further includes:

[0194] Optional, also includes:

[0195] Create the execution flowchart and edit the processing content, node content, and node dependencies of each execution node in the execution flowchart;

[0196] The processing content is used to characterize the specific execution events of the execution node. The node content includes the node execution role and / or the project stage corresponding to the node. The node dependency relationship includes the dependency information between each execution node.

[0197] According to one or more embodiments of this disclosure, Example 4 provides a view generation method, which further includes:

[0198] Optionally, generating a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content, and / or the project stages corresponding to the nodes includes:

[0199] Based on the node's execution role and / or the project phase corresponding to the node, determine at least one horizontal swimlane and at least one vertical swimlane;

[0200] Based on the display information of the horizontal lanes and the display information of the vertical lanes, the cross-display elements are determined;

[0201] Based on the node dependencies, the corresponding cross-display elements are displayed to obtain the target swimlane view.

[0202] According to one or more embodiments of this disclosure, Example 5 provides a view generation method, which further includes:

[0203] Optionally, determining at least one horizontal lane and at least one vertical lane based on the node's execution role and / or the project stage corresponding to the node includes:

[0204] The node's execution role is used as the horizontal information of the horizontal swimlane, and the project stage corresponding to the node is used as the vertical information of the vertical swimlane.

[0205] Based on the lateral information, at least one lateral lane is determined, and based on the longitudinal information, at least one longitudinal lane is determined.

[0206] According to one or more embodiments of this disclosure, Example Six provides a view generation method, further comprising:

[0207] Optional, also includes:

[0208] The horizontal information corresponds to the project stage of the node, and the vertical information corresponds to the execution role of the node.

[0209] According to one or more embodiments of this disclosure, [Example Seven] provides a view generation method, further comprising:

[0210] Optional, also includes:

[0211] If the target swimlane view does not include the project stage corresponding to the currently executing node, and does not include the node execution role, then an unincluded horizontal swimlane without role information is created in the target swimlane view to display the executing node in the unincluded horizontal swimlane.

[0212] If the target swimlane view does not include the project stage corresponding to the currently executing node, but includes the node execution role, then the project stage corresponding to the node will be used as the vertical information in the target swimlane view, and a new vertical swimlane will be added.

[0213] According to one or more embodiments of this disclosure, [Example Eight] provides a view generation method, further comprising:

[0214] Optionally, the horizontal swimlanes of the target swimlane view correspond to the node's execution role, and the vertical swimlanes correspond to the project phase of the node. The method further includes:

[0215] When it is detected that a vertical state swimlane corresponding to the project stage of the node is to be added, the vertical state swimlane is added to the far right of the target swimlane view; wherein the vertical state swimlane corresponds to the project stage of the added node.

[0216] When a horizontal role swimlane corresponding to a node execution role is detected to be added, the horizontal role swimlane is added to the bottom of the target swimlane view; wherein the horizontal role swimlane corresponds to the added node execution role.

[0217] According to one or more embodiments of this disclosure, [Example Nine] provides a view generation method, further comprising:

[0218] Optional, also includes:

[0219] When a removal operation is detected in the target swimlane view, and the removal operation corresponds to the project stage corresponding to the node, it is determined whether the project stage corresponding to the node includes an execution node.

[0220] If so, a prompt box will pop up with a message indicating that the project stage corresponding to the node cannot be removed and that the node should be removed before trying again.

[0221] If not, remove the swimlane corresponding to the project stage of the node to update the target swimlane view.

[0222] According to one or more embodiments of this disclosure, Example 10 provides a view generation method, which further includes:

[0223] Optional, also includes:

[0224] When it is detected that the project stage corresponding to the target node is dragged from the current position to the target position in the target swimlane view, the dependencies between the execution nodes located between the current position and the target position are determined;

[0225] If the dependency conflicts with the target location of the project stage corresponding to the node, the target location will be set as a disabled location for the project stage corresponding to the target node, and a prompt message indicating that it cannot be placed will be displayed.

[0226] According to one or more embodiments of this disclosure, Example 11 provides a view generation method, which further includes:

[0227] Optional, also includes:

[0228] When it is detected that the project stage control corresponding to the newly created node and / or the execution role control of the newly created node are triggered, a horizontal swimlane and / or a vertical swimlane are added to the target swimlane view.

[0229] According to one or more embodiments of this disclosure, [Example Twelve] provides a view generation method, further comprising:

[0230] Optional, also includes:

[0231] When a cross-display element in the target swimlane view is detected, an edit box corresponding to the cross-display element pops up, allowing the information of the cross-display element to be updated in the edit box.

[0232] According to one or more embodiments of this disclosure, Example Thirteen provides a view generation method, which further includes:

[0233] Optional, also includes:

[0234] Edit the correspondence between the current cross-display element and other cross-display elements in the edit box, so as to execute the execution content corresponding to the corresponding cross-display element based on the correspondence; wherein, the execution content is consistent with the processing content of the execution node in the execution flowchart;

[0235] When the operation of content editing is detected to be completed, the display position of the corresponding cross-display element in the target swimlane view is updated according to the correspondence.

[0236] According to one or more embodiments of this disclosure, [Example Fourteen] provides a view generation method, further comprising:

[0237] Optionally, the dependency lines of each execution node in the target swimlane view are displayed transparently in the display interface;

[0238] When the cursor is detected to correspond to an execution node, the first-level dependency line corresponding to the execution node is displayed;

[0239] When the dependency display control is triggered, the dependency lines of each execution node in the target swimlane view are displayed.

[0240] According to one or more embodiments of this disclosure, [Example Fifteen] provides a view generation method, further comprising:

[0241] Optional, also includes:

[0242] When a modification of a cross-display element is detected in the target swimlane view, the execution flowchart is updated in conjunction with the cross-display element.

[0243] According to one or more embodiments of this disclosure, [Example Sixteen] provides a view generation apparatus, the apparatus comprising:

[0244] The execution flowchart traversal module is used to traverse the node content and node dependencies of each execution node in the execution flowchart when the view transformation conditions are met.

[0245] The target swimlane view generation module is used to generate a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content, and / or the project stages corresponding to the nodes.

[0246] The target swimlane view includes cross-display elements, which are consistent with the processing content of each execution node.

[0247] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0248] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0249] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A view generation method, characterized in that, include: When the view transformation conditions are met, traverse the node content and node dependencies of each execution node in the execution flowchart; The view transformation condition is: the number of execution nodes arranged in parallel in the execution flowchart is detected to be greater than a preset threshold; wherein, execution nodes belonging to the same parent node are considered as execution nodes arranged in parallel. Based on the node dependencies, the node execution roles and / or the project stages corresponding to the nodes in the node content, a target swimlane view consistent with the swimlane format is generated. The target swimlane view includes cross-display elements, which are consistent with the processing content of each execution node. The horizontal and / or vertical swimlanes of the target swimlane view are determined according to the node execution role and / or the project stage corresponding to the node in the node content, and the order of the horizontal and / or vertical swimlanes is determined according to the node dependency relationship.

2. The method according to claim 1, characterized in that, The view transformation conditions also include: A view transition control has been detected.

3. The method according to claim 1, characterized in that, Also includes: Create the execution flowchart and edit the processing content, node content, and node dependencies of each execution node in the execution flowchart; The processing content is used to characterize the specific execution events of the execution node. The node content includes the node execution role and / or the project stage corresponding to the node. The node dependency relationship includes the dependency information between each execution node.

4. The method according to claim 1, characterized in that, The step of generating a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content, and / or the project stages corresponding to the nodes includes: Based on the node's execution role and / or the project phase corresponding to the node, determine at least one horizontal swimlane and at least one vertical swimlane; Based on the display information of the horizontal lanes and the display information of the vertical lanes, the cross-display elements are determined; Based on the node dependencies, the corresponding cross-display elements are displayed to obtain the target swimlane view.

5. The method according to claim 4, characterized in that, The step of determining at least one horizontal lane and at least one vertical lane based on the node's execution role and / or the project stage corresponding to the node includes: The node's execution role is used as the horizontal information of the horizontal swimlane, and the project stage corresponding to the node is used as the vertical information of the vertical swimlane. Based on the lateral information, at least one lateral lane is determined, and based on the longitudinal information, at least one longitudinal lane is determined.

6. The method according to claim 5, characterized in that, Also includes: The horizontal information corresponds to the project stage of the node, and the vertical information corresponds to the execution role of the node.

7. The method according to claim 5, characterized in that, Also includes: If the target swimlane view does not include the project stage corresponding to the currently executing node, and does not include the node execution role, then an unincluded horizontal swimlane without role information is created in the target swimlane view to display the executing node in the unincluded horizontal swimlane. If the target swimlane view does not include the project stage corresponding to the currently executing node, but includes the node execution role, then the project stage corresponding to the node will be used as the vertical information in the target swimlane view, and a new vertical swimlane will be added.

8. The method according to claim 1, characterized in that, The horizontal swimlanes of the target swimlane view correspond to the node's execution role, and the vertical swimlanes correspond to the project phase of the node. The method further includes: When it is detected that a vertical state swimlane corresponding to the project stage of the node is to be added, the vertical state swimlane is added to the far right of the target swimlane view; wherein the vertical state swimlane corresponds to the project stage of the added node. When a horizontal role swimlane corresponding to a node execution role is detected to be added, the horizontal role swimlane is added to the bottom of the target swimlane view; wherein the horizontal role swimlane corresponds to the added node execution role.

9. The method according to claim 1, characterized in that, Also includes: When a removal operation is detected in the target swimlane view, and the removal operation corresponds to the project stage corresponding to the node, it is determined whether the project stage corresponding to the node includes an execution node. If so, a prompt box will pop up with a message indicating that the project stage corresponding to the node cannot be removed and that the node should be removed before trying again. If not, remove the swimlane corresponding to the project stage of the node to update the target swimlane view.

10. The method according to claim 1, characterized in that, Also includes: When it is detected that the project stage corresponding to the target node is dragged from the current position to the target position in the target swimlane view, the dependencies between the execution nodes located between the current position and the target position are determined; If the dependency conflicts with the target location of the project stage corresponding to the node, the target location will be set as a disabled location for the project stage corresponding to the target node, and a prompt message indicating that it cannot be placed will be displayed.

11. The method according to claim 1, characterized in that, Also includes: When it is detected that the project stage control corresponding to the newly created node and / or the execution role control of the newly created node are triggered, a horizontal swimlane and / or a vertical swimlane are added to the target swimlane view.

12. The method according to claim 1, characterized in that, Also includes: When a cross-display element in the target swimlane view is detected, an edit box corresponding to the cross-display element pops up, allowing the information of the cross-display element to be updated in the edit box.

13. The method according to claim 12, characterized in that, Also includes: Edit the correspondence between the current cross-display element and other cross-display elements in the edit box, so as to execute the execution content corresponding to the corresponding cross-display element based on the correspondence; wherein, the execution content is consistent with the processing content of the execution node in the execution flowchart; When the operation of content editing is detected to be completed, the display position of the corresponding cross-display element in the target swimlane view is updated according to the correspondence.

14. The method according to claim 1, characterized in that, The dependency lines of each execution node in the target swimlane view are displayed transparently in the display interface; When the cursor is detected to correspond to an execution node, the first-level dependency line corresponding to the execution node is displayed; When the dependency display control is triggered, the dependency lines of each execution node in the target swimlane view are displayed.

15. The method according to claim 1, characterized in that, Also includes: When a modification of a cross-display element is detected in the target swimlane view, the execution flowchart is updated in conjunction with the cross-display element.

16. A view generation apparatus, characterized in that, include: The execution flowchart traversal module is used to traverse the node content and node dependencies of each execution node in the execution flowchart when the view transformation conditions are met. The view transformation condition is: the number of execution nodes arranged in parallel in the execution flowchart is detected to be greater than a preset threshold; wherein, execution nodes belonging to the same parent node are considered as execution nodes arranged in parallel. The target swimlane view generation module is used to generate a target swimlane view consistent with the swimlane format based on the node dependencies, the node execution roles in the node content, and / or the project stages corresponding to the nodes. The target swimlane view includes cross-display elements, which are consistent with the processing content of each execution node. The horizontal and / or vertical swimlanes of the target swimlane view are determined according to the node execution role and / or the project stage corresponding to the node in the node content, and the order of the horizontal and / or vertical swimlanes is determined according to the node dependency relationship.

17. An electronic device, characterized in that, The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the view generation method as described in any one of claims 1-15.

18. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the view generation method as described in any one of claims 1-15.

Images