Flow chart display method and device

Abstract

The invention discloses a flow chart display method and device, and relates to the technical field of computers. A specific embodiment of the method comprises the steps of receiving a flow chart display request; determining a request task node and a request level corresponding to the flow chart display request, and determining a plurality of descendant task nodes of the request task node under the request level; for each descendant task node, drawing a node icon corresponding to the descendant task node on the canvas according to the coordinate information corresponding to the descendant task node; for each descendant task node, determining dependency information corresponding to the descendant task node; determining a plurality of path node icons corresponding to the dependency information from a plurality of node icons on the canvas; and sequentially connecting the path node icons through directed edges. According to the embodiment, the flow chart is displayed in a layered mode, the number of task nodes needing to be displayed can be reduced, the display performance of a chart visualization engine is improved, and a user can browse the flow chart conveniently.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular, to a method and apparatus for displaying a flowchart. Background Art

[0002] Process scheduling systems are widely used in fields such as computing resource management, industrial production, and task allocation. Their core value lies in solving the contradiction between resource finiteness and demand complexity. With the development of information technology and automation, the demand for process scheduling systems is increasing day by day. Process scheduling systems are usually implemented through flowcharts. Flowcharts use various different icons to represent tasks or activities in the work process, and use the connection relationships between the icons to represent the execution order between tasks. Existing graph visualization engines usually display flowcharts in a flat manner, that is, all node icons are uniformly displayed in the flowchart. However, when the number of task nodes is greater than a certain value, the display performance of the graph visualization engine will show a significant decline, and this display method is also not convenient for users to browse and manage the flowchart. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a method and apparatus for displaying a flowchart, which display the flowchart in a hierarchical manner, can reduce the number of task nodes to be displayed, improve the display performance of the graph visualization engine, and are convenient for users to browse and manage the flowchart.

[0004] In a first aspect, an embodiment of the present invention provides a method for displaying a flowchart, including: Receiving a flowchart display request; Determining a requested task node and a requested level corresponding to the flowchart display request, and determining a plurality of descendant task nodes of the requested task node at the requested level; For each descendant task node, drawing a node icon corresponding to the descendant task node on the canvas according to the coordinate information corresponding to the descendant task node; For each descendant task node, determining the dependency information corresponding to the descendant task node; determining a plurality of path node icons corresponding to the dependency information from the plurality of node icons on the canvas; and sequentially connecting the plurality of path node icons through directed edges.

[0005] Optionally, the flowchart display request is issued for the current flowchart; Determining the requested task node and the requested level corresponding to the flowchart display request includes: Determining a current node icon corresponding to the flowchart display request from the plurality of node icons of the current flowchart; Determining the task node corresponding to the current node icon as the requested task node; Determining the level of the sub-flowchart corresponding to the requested task node as the requested level.

[0006] Optionally, determining the request task nodes and request levels corresponding to the flowchart display request includes: In response to the flowchart being the top-level flowchart of the request business system, determining the root task node corresponding to the business system as the request task node, and determining the top level as the request level; In response to the flowchart being a sub-flowchart of the request business system, determining the root task node corresponding to the sub-flowchart as the request task node, and determining the level corresponding to the sub-flowchart as the request level.

[0007] Optionally, before receiving the flowchart display request, it further includes: Determining multiple configuration node icons and multiple dependency edges in the process configuration interface; For each configuration node icon, determining the coordinate information of the configuration node icon in the process configuration interface; generating the attribute information of the configuration task node corresponding to the configuration node icon; wherein, the attribute information includes: the task number and coordinate information corresponding to the configuration task node; For each dependency edge, determining the target node icon and multiple path node icons corresponding to the dependency edge; generating the dependency information corresponding to the dependency edge; wherein, the dependency information includes: the task number corresponding to the target node icon and the task numbers corresponding to each path node icon.

[0008] Optionally, before determining multiple configuration node icons and multiple dependency edges in the process configuration interface, it further includes: Receiving a flowchart configuration request and displaying the process configuration interface; Receiving an orchestration operation for the process configuration interface; Generating multiple configuration node icons and multiple dependency edges in the process configuration interface according to the orchestration operation.

[0009] Optionally, generating the attribute information of the configuration task node corresponding to the configuration node icon includes: Determining the parent task node and sub-process identifier of the configuration task node; wherein, the sub-process identifier is used to identify whether the configuration task node corresponds to a sub-process; Generating the attribute information corresponding to the configuration task node; wherein, the attribute information includes: the task number and coordinate information corresponding to the configuration task node, the task number corresponding to the parent task node, and the sub-process identifier.

[0010] Optionally, after determining multiple configuration node icons and multiple dependency edges in the process configuration interface, it further includes: Determining the target level corresponding to the process configuration interface; Combining the task numbers corresponding to each configuration node icon to generate a task node set corresponding to the target level.

[0011] Optionally, for each descendant task node, after drawing the node icon corresponding to the descendant task node on the canvas according to the coordinate information corresponding to the descendant task node, it further includes: Determine multiple display node icons in the canvas; For each display node icon, determine the running status of the task node corresponding to the display node icon; according to the running status, determine the display information corresponding to the display node icon; according to the display information, display the display node icon in the canvas.

[0012] In a second aspect, an embodiment of the present invention provides a display device for a flowchart, including: A request receiving module, configured to receive a flowchart display request; A node determining module, configured to determine a request task node and a request level corresponding to the flowchart display request, and determine multiple descendant task nodes of the request task node at the request level; An icon drawing module, configured to, for each descendant task node, draw the node icon corresponding to the descendant task node on the canvas according to the coordinate information corresponding to the descendant task node; An edge connection module, configured to, for each descendant task node, determine the dependency information corresponding to the descendant task node; determine multiple path node icons corresponding to the dependency information from multiple node icons on the canvas; and sequentially connect each path node icon through a directed edge.

[0013] In a third aspect, an embodiment of the present invention provides an electronic device, including: One or more processors; A storage device, configured to store one or more programs, and when the one or more programs are executed by the one or more processors, enable the one or more processors to implement the method of any of the above embodiments.

[0014] In a fourth aspect, an embodiment of the present invention provides a computer-readable medium, on which a computer program is stored, and when the program is executed by a processor, the method of any of the above embodiments is implemented.

[0015] One embodiment of the above invention has the following advantages or beneficial effects: Determine the request task node and the request level corresponding to the flowchart display request. Generate a flowchart corresponding to the flowchart display request according to multiple descendant task nodes of the request task node at the request level. By splitting the entire process of the business system into multiple different levels, the number of task nodes to be displayed in the flowchart can be reduced, the display performance of the graph visualization engine can be improved, and it is convenient for users to browse and manage the flowchart.

[0016] In addition, clustering multiple request task nodes that perform the same function, have similar effects, or have similar task attributes into a sub - flowchart can reduce the number of task nodes displayed in the top - level flowchart or high - level flowchart, further facilitating the user's browsing and management in the top - level flowchart or high - level flowchart.

[0017] The further effects of the above - mentioned non - conventional alternative methods will be described below in conjunction with specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings are used to better understand the present invention and do not unduly limit the present invention. Among them: Figure 1 is a schematic flowchart of a method for displaying a flowchart provided by the first embodiment of the present invention; Figure 2 is a schematic flowchart of a method for displaying a flowchart provided by the second embodiment of the present invention; Figure 3 is a schematic flowchart of a method for displaying a flowchart provided by the third embodiment of the present invention; Figure 4 is a schematic diagram of a configuration interface of a main flowchart provided by an embodiment of the present invention; Figure 5 is a schematic diagram of a configuration interface of a sub - flowchart provided by an embodiment of the present invention; Figure 6 is a schematic diagram of another configuration interface of a sub - flowchart provided by an embodiment of the present invention; Figure 7 is a schematic diagram of a display interface of a main flowchart provided by an embodiment of the present invention; Figure 8 is a schematic diagram of a display interface of a sub - flowchart provided by an embodiment of the present invention; Figure 9 is a schematic diagram of another display interface of a sub - flowchart provided by an embodiment of the present invention; Figure 10 is a schematic structural diagram of a flowchart display device provided by an embodiment of the present invention; Figure 11 is a schematic structural diagram of a computer system of a terminal device or a server suitable for implementing the embodiments of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] The following describes exemplary embodiments of the present invention with reference to the accompanying drawings. Various details of the embodiments of the present invention are included to facilitate understanding, and they should be considered merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, descriptions of well-known functions and structures are omitted below for clarity and conciseness.

[0020] In the technical solution of this application, the acquisition, transmission, storage, use, processing, etc. of data all comply with the relevant provisions of national laws and regulations.

[0021] It should be noted that in the embodiments of this application, some existing industry solutions such as certain software, components, models, etc. may be mentioned. They should be considered exemplary, and their purpose is only to illustrate the feasibility in the implementation of the technical solution of this application, but it does not mean that the applicant has already or necessarily used this solution.

[0022] Figure 1 is a schematic flowchart showing a method for displaying a flowchart provided by the first embodiment of the present invention. As Figure 1 shown, the method includes: Step 101: Receive a flowchart display request.

[0023] Step 102: Determine the request task node and request level corresponding to the flowchart display request, and determine multiple descendant task nodes of the request task node at the request level.

[0024] The entire process of the business system is split into a top-level flowchart and multiple sub-flowcharts. The top-level flowchart is the uppermost flowchart of the business system. All sub-flowcharts are subordinate flowcharts of the top-level flowchart.

[0025] Different flowcharts correspond to different root task nodes and levels. Determine the flowchart corresponding to the flowchart display request, determine the root task node corresponding to the flowchart as the request task node, and determine the level corresponding to the flowchart as the request level.

[0026] If the flowchart is used to request the top-level flowchart of the business system, determine the root task node corresponding to the business system as the request task node, and determine the top level as the request level. If the flowchart is used to request a sub-flowchart of the business system, determine the root task node corresponding to the sub-flowchart as the request task node, and determine the level corresponding to the sub-flowchart as the request level.

[0027] For example, a business system is used to handle user logins. The top-level flowchart includes: a root task node, a user login information acquisition task node, a user identity confirmation task node, a login success processing node, and a login failure processing node. Among them, the user login information acquisition task node, the user identity confirmation task node, the login success processing node, and the login failure processing node each correspond to their own sub-flowcharts.

[0028] In the sub-flowchart corresponding to the login success processing node, the login success processing node is the root task node of this sub-flowchart, and each task node in this sub-flowchart is a descendant node of the login success processing node. The level corresponding to this sub-flowchart is: top-level flowchart\login success processing. This sub-flowchart may include: a user permission determination node, a login interface display node, and a to-do reminder node. By sequentially executing the above task nodes, the process corresponding to the login success processing node is completed.

[0029] Step 103: For each descendant task node, according to the coordinate information corresponding to the descendant task node, draw the node icon corresponding to the descendant task node on the canvas.

[0030] The coordinate information may include: the x-axis coordinate and y-axis coordinate corresponding to the task node. Utilize the high performance and rich built-in components of the canvas to ensure the efficient and stable operation of functions such as task node status refresh, operation and maintenance monitoring, and task manual intervention.

[0031] Step 104: For each descendant task node, determine the dependency information corresponding to the descendant task node; from the multiple node icons on the canvas, determine the multiple path node icons corresponding to the dependency information; and sequentially connect each path node icon through a directed edge.

[0032] The dependency information corresponding to the task node includes at least one node set. Each node set includes multiple task nodes with an execution order. The dependency information is used to represent other task nodes that the task node depends on during execution.

[0033] For example, the dependency information corresponding to the target task node includes: node set 1. Node set 1 sequentially includes: task node 1, task node 2, task node 3, and task node 4. Then the task corresponding to task node 1 is the pre-dependency task of the task corresponding to task node 2, the task corresponding to task node 2 is the pre-dependency task of the task corresponding to task node 3, the task corresponding to task node 3 is the pre-dependency task of the task corresponding to task node 4, and the task corresponding to task node 4 is the pre-dependency task of the task corresponding to the target task node. During the execution of the business system, task node 1 -> task node 2 -> task node 3 -> task node 4 -> target task node are sequentially executed to complete the execution of the target task node.

[0034] From multiple node icons on the canvas, determine multiple path node icons corresponding to the dependency information of the descendant task nodes. Then, connect each path node icon in sequence through directed edges, and finally generate a flowchart corresponding to the flowchart display request. The directed edge is a line segment with an arrow. The directed edges in the flowchart can reflect the sequential execution order and dependency relationship between task nodes.

[0035] In the solution of the embodiment of the present invention, determine the request task node and request level corresponding to the flowchart display request. Generate a flowchart corresponding to the flowchart display request according to multiple descendant task nodes of the request task node at the request level. By splitting the entire process of the business system into multiple different levels, the number of task nodes that need to be displayed in the flowchart can be reduced, the display performance of the graph visualization engine can be improved, and it is convenient for users to browse the flowchart.

[0036] In an embodiment of the present invention, the flowchart display request is issued for the current flowchart; determining the request task node and request level corresponding to the flowchart display request includes: from multiple node icons of the current flowchart, determining the current node icon corresponding to the flowchart display request; determining the task node corresponding to the current node icon as the request task node; and determining the level of the sub-flowchart corresponding to the request task node as the request level.

[0037] The user browses the current flowchart and hopes to view the sub-flowchart of a certain task node in the current flowchart. The user can click the node icon of the task node with the left mouse button, and a function menu for the task node pops up in the current flowchart. The function menu may include: viewing the sub-process, viewing task attributes, setting checkpoints, etc. The user issues a flowchart display request by selecting to view the sub-process.

[0038] Determine the task node corresponding to the current node icon as the request task node. Determine the level of the sub-flowchart corresponding to the request task node as the request level. Display the sub-flowchart corresponding to the request task node to respond to the flowchart display request.

[0039] Figure 2 It is a schematic flowchart of a method for displaying a flowchart provided by the second embodiment of the present invention. As Figure 2 shown, the method includes: Step 201: Determine multiple configuration node icons and multiple dependency edges in the process configuration interface.

[0040] The user configures the flowchart in the process configuration interface. The flowchart configured in the process configuration interface includes: multiple configuration node icons and multiple dependency edges.

[0041] Step 202: For each configuration node icon, determine the coordinate information of the configuration node icon in the process configuration interface; generate the attribute information of the configuration task node corresponding to the configuration node icon; wherein, the attribute information includes: the task number and coordinate information corresponding to the configuration task node.

[0042] The attribute information of the configuration task node corresponding to the configuration node icon can be generated in the following manner: Determine the parent task node and sub - process identifier of the configuration task node. Generate the attribute information corresponding to the configuration task node. The attribute information includes: the task number corresponding to the configuration task node, the coordinate information corresponding to the configuration task node, the task number corresponding to the parent task node, and the sub - process identifier. Among them, the sub - process identifier is used to identify whether the configuration task node corresponds to a sub - process.

[0043] Step 203: For each dependency edge, determine the target node icon and multiple path node icons corresponding to the dependency edge; generate the dependency information corresponding to the dependency edge; wherein, the dependency information includes: the task number corresponding to the target node icon and the task numbers corresponding to each path node icon.

[0044] Determine the end task node corresponding to the dependency edge as the target task node corresponding to the dependency edge. The dependency information corresponding to the dependency edge is the dependency information corresponding to the target task node.

[0045] For example, if the dependency edge passes through the icon of task node 1, the icon of task node 2, and the icon of task node 3 in sequence, then the task corresponding to task node 1 is the pre - dependency task of the task corresponding to task node 2, and the task corresponding to task node 2 is the pre - dependency task of the task corresponding to task node 3. During the execution of the business system, it is necessary to execute the task corresponding to task node 1, the task corresponding to task node 2, and the task corresponding to task node 3 in sequence. Task node 3 is the target task node of this dependency edge. The dependency information corresponding to this dependency edge includes: the task number corresponding to task node 3 and the node set. Among them, the node set includes: the task number corresponding to task node 1, the task number corresponding to task node 2, and the task number corresponding to task node 3.

[0046] In an embodiment of the present invention, the format of the node set can also be expressed as: V1x,V1y;V2x,V2y;V3x,V3y;...;Vnx,Vny. Wherein, V1x,V1y represents the x - axis coordinate and y - axis coordinate of the first path node icon corresponding to the dependency edge. Vnx,Vny represents the x - axis coordinate and y - axis coordinate of the nth path node icon corresponding to the dependency edge.

[0047] In an embodiment of the present invention, after determining a plurality of configuration node icons and a plurality of dependency edges in a process configuration interface, the method further includes: determining a target level corresponding to the process configuration interface; combining the task numbers corresponding to each configuration node icon to generate a task node set corresponding to the target level. By generating the task node set corresponding to the target level, after receiving a flowchart display request, it is possible to quickly determine the task nodes at the request level corresponding to the flowchart display request.

[0048] By obtaining the coordinate information in the attribute information of the task nodes at the request level, draw the node icons corresponding to the nodes on the canvas. By obtaining the dependency information of the task nodes at the request level, use directed edges to sequentially connect each path node icon in the dependency information, thereby efficiently completing the flowchart display.

[0049] Step 204: Receive a flowchart display request.

[0050] Step 205: Determine the request task nodes and the request level corresponding to the flowchart display request, and determine a plurality of descendant task nodes of the request task nodes at the request level.

[0051] Step 206: For each descendant task node, draw the node icon corresponding to the descendant task node on the canvas according to the coordinate information corresponding to the descendant task node.

[0052] Step 207: For each descendant task node, determine the dependency information corresponding to the descendant task node; from a plurality of node icons on the canvas, determine a plurality of path node icons corresponding to the dependency information; use directed edges to sequentially connect each path node icon.

[0053] In the solution of the embodiment of the present invention, according to a plurality of configuration node icons and a plurality of dependency edges in the process configuration interface, generate the attribute information and dependency information corresponding to each task node. Among them, there is a one-to-one correspondence between the configuration node icon and the task node. After receiving a flowchart display request, according to the attribute information and dependency information corresponding to each task node, it is possible to efficiently complete the generation and display of the flowchart.

[0054] The system also provides functions for adding, deleting, modifying, and querying the attribute information of task nodes, and functions for adding, deleting, modifying, and querying dependency information. Among them, the attribute information of task nodes includes: the parent task number and the coordinate information of the task node. The parent task number and the coordinate information of the task node determine the level of the task node and the position of the task node in this level. The dependency information includes: the task number of the target node corresponding to the dependency information, the task numbers or coordinate information of each path task node, etc. Using the dependency information, it is possible to complete the drawing of each directed edge in the flowchart.

[0055] In an embodiment of the present invention, before determining multiple configuration node icons and multiple dependency edges in the process configuration interface, the following steps are further included: receiving a flowchart configuration request, displaying the process configuration interface; receiving an orchestration operation for the process configuration interface; and generating multiple configuration node icons and multiple dependency edges in the process configuration interface according to the orchestration operation.

[0056] The orchestration operation may include drag-and-drop operations, editing operations, etc. The node icons in the configuration interface can be dragged. The front end will call the interface for updating task node information to update the attribute information of the task node. The directed edges in the configuration interface can also be dragged. The front end will call the interface for updating dependency information to update the information of the path task nodes corresponding to the dependency information. It is also possible to click on the task node for an editing operation. The front end will call the interface for updating the attribute information of the task node to update the attribute information of the task node.

[0057] Figure 3 It is a schematic flowchart of a method for displaying a flowchart provided by the third embodiment of the present invention, as Figure 3 shown, the method includes: Step 301: Receive a flowchart display request.

[0058] Step 302: Determine the request task node and request level corresponding to the flowchart display request, and determine multiple descendant task nodes of the request task node at the request level.

[0059] Step 303: For each descendant task node, draw the node icon corresponding to the descendant task node on the canvas according to the coordinate information corresponding to the descendant task node.

[0060] Step 304: For each descendant task node, determine the dependency information corresponding to the descendant task node; from multiple node icons on the canvas, determine multiple path node icons corresponding to the dependency information; and sequentially connect the path node icons through directed edges.

[0061] Step 305: Determine multiple display node icons in the canvas.

[0062] Step 306: For each display node icon, determine the running state of the task node corresponding to the display node icon; according to the running state, determine the display information corresponding to the display node icon; and display the display node icon on the canvas according to the display information.

[0063] The running state may include: not running, running, completed, failed to run, etc. The display information may include: display color, display shape, display size, display font, etc. A mapping relationship between the running state and the display information is preset in the system. According to this mapping relationship, determine the display information corresponding to each display node icon, and display the display node icon on the canvas.

[0064] For example, if the task node is in an unrun state, the display color is the first color. When the task node starts running, the display color is the second color. The icon of the completed task node is displayed as the third color. The icon of the task node that fails to run is displayed as the fourth color.

[0065] In the solution of the embodiment of the present invention, after generating the flow chart corresponding to the flow chart display request, according to the running state of the task node corresponding to the display node icon, the display information corresponding to the display node icon is determined, and the display node icon is displayed on the canvas. By using different display information to display the task node icons in different running states, it is convenient for users to observe the running state of the task nodes, understand the overall running situation of the business system, and improve the user's flow chart browsing experience.

[0066] The solution of the embodiment of the present invention is based on the nesting of directed acyclic graphs to achieve task hierarchization. By analyzing the dependency relationships of the tasks in the process and using a grouped and layered mode, the task nodes in each layer and each group are controlled within a reasonable range. At the same time, the solution of the embodiment of the present invention also transforms the intricate dependency relationships in the original flat flow chart into parent-child relationships and front-back dependency relationships between task nodes through subprocess nesting, which can reduce the complexity of the flow chart layout and display.

[0067] During the flow chart configuration process, visual layout design is adopted to obtain the coordinate information of the task node icons and the coordinate information of the path nodes of the dependency edges. The attribute information and dependency information of the tasks in the flow chart are saved in the system. During the flow chart display process, the coordinate information of the task nodes and the coordinate information of the path nodes of the dependency edges are used to perform flow chart rendering to achieve the restoration and display of the flow chart.

[0068] Figure 4 is a schematic diagram of a configuration interface of a main flow chart provided by an embodiment of the present invention, as Figure 4 shown, the main flow configuration interface provides a work area for visually editing the flow chart. The information in the upper left corner of the main flow configuration interface shows the level corresponding to the current flow chart. The configuration interface can also provide rich flow chart components, such as database batch tasks, database flow tasks, kafka flow tasks, and other types of tasks. Different flow chart components are used to represent different task types, enabling the generated flow chart to express more complete flow execution information and providing a better browsing experience for users.

[0069] In addition, the configuration interface can also provide a thumbnail function. When the number of task nodes in the flow chart is large, by using the thumbnail function, users can quickly understand the architecture of the business system and the execution of the process, which is convenient for users to analyze and manage the business system.

[0070] Figure 4 The configuration interface shown in is used to edit the flowchart corresponding to as400-sq-prod-test. as400-sq-prod-test is the description information corresponding to the main process of the business system.

[0071] The task nodes in solid-line boxes correspond to specific tasks. The task nodes in dashed-line boxes correspond to virtual tasks. Generally, a virtual task corresponds to a sub-process. A virtual task is a special type of task that is not responsible for specific business processing in the scheduling system and is mainly used to simplify the dependency relationships between task nodes. Virtual tasks include: virtual tasks with a convergence function and virtual tasks containing sub-processes.

[0072] Figure 4 The directed edges with arrows in are used to reflect the dependency relationships between task nodes. For example, the start of both Task 30 and Task 31 depends on the completion of Task 406. There is a directed edge with an arrow connecting Task 406 to Task 30. There is also a directed edge with an arrow connecting Task 406 to Task 31.

[0073] Click Figure 4 on Task 33 in to display the configuration interface of the sub-process corresponding to Task 33. Figure 5 is a schematic diagram of the configuration interface of a sub-process flowchart provided by an embodiment of the present invention. As shown in Figure 5 , the sub-process configuration interface provides a work area for visually editing the flowchart. The breadcrumb navigation in the upper left corner of the sub-process configuration interface shows the level corresponding to the currently edited flowchart. Figure 5 The configuration interface shown in is used to edit the flowchart corresponding to deal-receiving-and-resolving under as400-sq-prod-test. deal-receiving-and-resolving is the parent task node of the current 419->420 process.

[0074] Click Figure 5 on Task 419 in to display the configuration interface of its corresponding sub-process. Figure 6 is a schematic diagram of another sub-process configuration interface provided by an embodiment of the present invention. As shown in Figure 6 , Figure 6 the breadcrumb navigation in the upper left corner shows the level corresponding to the currently edited flowchart. deal-receiving-and-resolving is the parent task node of deal-receiving. deal-receiving is the parent task node of the current (421, 422, 423)->427 process.

[0075] Figure 7It is a schematic diagram of a display interface of a main flowchart provided by an embodiment of the present invention. Figure 7 is Figure 4 the display effect diagram of the arranged main flowchart. Figure 7 The displayed main flowchart is a view for operation and maintenance personnel to monitor the running status of the business system during system operation. The information in the upper left corner of the main flowchart shows the level where the flowchart is located. The main flowchart and sub-flowcharts are all displayed in the canvas. The task numbers and Chinese task names of the task nodes are displayed in the canvas. The task nodes cannot be dragged, and the directed edges between task nodes cannot be edited.

[0076] If the entire task process is in an unrun state, the colors of all task nodes are gray. When the process starts running, the running task nodes will be displayed in yellow, the completed task nodes will be displayed in blue, and the task nodes that have failed to run will be displayed in red.

[0077] Similar to visual arrangement, the display of the flowchart also includes the function of nested sub-processes. Right-click on Figure 7 Task 33 in, and select View Sub-Flowchart, then the system will display the sub-flowchart corresponding to Task 33. Figure 8 It is a schematic diagram of a display interface of a sub-flowchart provided by an embodiment of the present invention. Figure 8 is Figure 5 the display effect diagram of the arranged sub-flowchart. There is a built-in toolbar set at the upper left corner of the sub-flowchart or the main flowchart, providing functions such as picture zooming, task node retrieval, switching between up-and-down layout and left-and-right layout, thumbnail, exporting pictures, full screen, and switching theme colors for operation and maintenance personnel to use.

[0078] Right-click on Figure 8 Task 419 in, and select View Sub-Flowchart, the system will display the sub-flowchart corresponding to Task 419. Figure 9 It is a schematic diagram of another display interface of a sub-flowchart provided by an embodiment of the present invention. Figure 9 is Figure 6 the display effect diagram of the arranged sub-flowchart. Figure 9 It is used to display the sub-flowchart corresponding to Task 419.

[0079] During the process of visual arrangement of the flowchart, the attribute information and dependency information of the task nodes are saved. During the display process of the flowchart, the saved attribute information and dependency information of the task nodes are obtained for flowchart display. After the flowchart is displayed, the running status of each task node is obtained in real time, and according to the running status of the task node, the display information of the task node icon in the flowchart is determined.

[0080] The solution of the embodiment of the present invention decomposes a complex large-scale scheduling task flowchart into multiple small editable and restorable flowcharts. In the solution of the embodiment of the present invention, by using the nesting of directed acyclic graphs, the dependency relationship between task nodes is simplified, the number of tasks for layout display is reduced, and fast retrieval under nested sub-processes is achieved. In addition, the solution of the embodiment of the present invention also provides functions such as graph layout and graph display, improving the rendering performance and layout stability of the graph visualization engine.

[0081] Figure 10 is a schematic structural diagram of a display device for a flowchart provided by an embodiment of the present invention, applied to a business system, such as Figure 10 shown, the device includes: A request receiving module 1001, configured to receive a flowchart display request; A node determination module 1002, configured to determine a request task node and a request level corresponding to the flowchart display request, and determine multiple descendant task nodes of the request task node at the request level; An icon drawing module 1003, configured to draw node icons corresponding to the descendant task nodes on the canvas according to the coordinate information corresponding to the descendant task nodes for each descendant task node; An edge connection module 1004, configured to determine the dependency information corresponding to the descendant task nodes for each descendant task node; determine multiple path node icons corresponding to the dependency information from multiple node icons on the canvas; and sequentially connect each path node icon through a directed edge.

[0082] Optionally, the flowchart display request is issued for the current flowchart; The node determination module 1002 is specifically configured to: Determine a current node icon corresponding to the flowchart display request from multiple node icons of the current flowchart; Determine the task node corresponding to the current node icon as the request task node; Determine the level of the sub-flowchart corresponding to the request task node as the request level.

[0083] Optionally, the node determination module 1002 is specifically configured to: In response to the flowchart being used to request the top-level flowchart of the business system, determine the root task node corresponding to the business system as the request task node, and determine the top level as the request level; In response to the flowchart being used to request a sub-flowchart of the business system, determine the root task node corresponding to the sub-flowchart as the request task node, and determine the level corresponding to the sub-flowchart as the request level.

[0084] Optionally, it further includes: A configuration module, configured to determine a plurality of configuration node icons and a plurality of dependency edges in a process configuration interface; For each configuration node icon, determine the coordinate information of the configuration node icon in the process configuration interface; generate attribute information of a configuration task node corresponding to the configuration node icon; wherein, the attribute information includes: a task number corresponding to the configuration task node and the coordinate information; For each dependency edge, determine a target node icon and a plurality of path node icons corresponding to the dependency edge; generate dependency information corresponding to the dependency edge; wherein, the dependency information includes: a task number corresponding to the target node icon and task numbers corresponding to each path node icon.

[0085] Optionally, the configuration module is further configured to: Receive a flowchart configuration request and display a process configuration interface; Receive an orchestration operation for the process configuration interface; Generate a plurality of configuration node icons and a plurality of dependency edges in the process configuration interface according to the orchestration operation.

[0086] Optionally, the configuration module is further configured to: Determine a parent task node and a sub - process identifier of a configuration task node; wherein, the sub - process identifier is used to identify whether the configuration task node corresponds to a sub - process; Generate attribute information corresponding to the configuration task node; wherein, the attribute information includes: a task number corresponding to the configuration task node and the coordinate information, a task number corresponding to the parent task node, and the sub - process identifier.

[0087] Optionally, the configuration module is further configured to: Determine a target level corresponding to the process configuration interface; Combine the task numbers corresponding to each configuration node icon to generate a task node set corresponding to the target level.

[0088] Optionally, it further includes: A display module, configured to determine a plurality of display node icons in a canvas; For each display node icon, determine the running state of a task node corresponding to the display node icon; according to the running state, determine the display information corresponding to the display node icon; and display the display node icon in the canvas according to the display information.

[0089] An embodiment of the present invention provides an electronic device, including: One or more processors; A storage device, configured to store one or more programs, which when executed by one or more processors, cause the one or more processors to implement the method according to any one of the above embodiments.

[0090] An embodiment of the present invention provides a computer program product, including a computer program which, when executed by a processor, implements the method for displaying the flowchart in the embodiment of the present invention.

[0091] Reference is made below Figure 11 to FIG. 1100, which shows a schematic structural diagram of a computer system 1100 of a terminal device suitable for implementing the embodiments of the present invention. Figure 11 The terminal device shown is only an example and should not impose any limitation on the functions and scope of use of the embodiments of the present invention.

[0092] As Figure 11 shown, the computer system 1100 includes a central processing unit (CPU) 1101 which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1102 or a program loaded from a storage section 1108 into a random access memory (RAM) 1103. In the RAM 1103, various programs and data required for the operation of the system 1100 are also stored. The CPU 1101, ROM 1102, and RAM 1103 are connected to each other via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0093] The following components are connected to the I / O interface 1105: an input section 1106 including a keyboard, a mouse, etc.; an output section 1107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN card, a modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to the I / O interface 1105 as required. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1110 as required so that a computer program read from it can be installed into the storage section 1108 as required.

[0094] Specifically, according to the embodiments disclosed by the present invention, the processes described above with reference to the flowchart can be implemented as computer software programs. For example, an embodiment of the present invention includes a computer program product which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1109, and / or installed from the removable medium 1111. When the computer program is executed by the central processing unit (CPU) 1101, the above-mentioned functions defined in the system of the present invention are executed.

[0095] It should be noted that the computer-readable medium shown in the present invention can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. 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 of the above. More specific examples of a computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, in which computer-readable program code is carried. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0096] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks can occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0097] The modules involved in the embodiments of the present invention can be implemented in software or in hardware. The described modules can also be provided in a processor. For example, they can be described as: a request receiving module, a node determining module, an icon drawing module, and an edge connecting module. Among them, the names of these modules do not constitute a limitation to the modules themselves in some cases. For example, the request receiving module can also be described as "a module for receiving a flowchart display request".

[0098] As another aspect, the present invention also provides a computer-readable medium, which can be included in the device described in the above embodiments; or can exist alone without being assembled into the device. The above computer-readable medium carries one or more programs. When the one or more programs are executed by the device, the device includes: Receiving a flowchart display request; Determining a request task node and a request hierarchy corresponding to the flowchart display request, and determining a plurality of descendant task nodes of the request task node at the request hierarchy; For each descendant task node, according to the coordinate information corresponding to the descendant task node, drawing a node icon corresponding to the descendant task node on the canvas; For each descendant task node, determining the dependency information corresponding to the descendant task node; from the plurality of node icons on the canvas, determining a plurality of path node icons corresponding to the dependency information; and sequentially connecting the plurality of path node icons through directed edges.

[0099] According to the technical solution of the embodiments of the present invention, determining a request task node and a request hierarchy corresponding to the flowchart display request. Generating a flowchart corresponding to the flowchart display request according to a plurality of descendant task nodes of the request task node at the request hierarchy. By splitting the entire process of the business system into multiple different levels, the number of task nodes to be displayed in the flowchart can be reduced, the display performance of the graph visualization engine can be improved, and it is convenient for users to browse the flowchart.

[0100] The above specific embodiments do not constitute a limitation to the protection scope of the present invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for displaying a flowchart, characterized in that Including: Receiving a flowchart display request; Determining a request task node and a request level corresponding to the flowchart display request, and determining a plurality of descendant task nodes of the request task node at the request level; For each of the descendant task nodes, drawing a node icon corresponding to the descendant task node on a canvas according to coordinate information corresponding to the descendant task node; For each of the descendant task nodes, determining dependency information corresponding to the descendant task node; Determining, from a plurality of node icons on the canvas, a plurality of path node icons corresponding to the dependency information; and sequentially connecting each of the path node icons through a directed edge.

2. The method according to claim 1, wherein The flowchart display request is issued for the current flowchart; The determining the request task node and the request level corresponding to the flowchart display request includes: Determining a current node icon corresponding to the flowchart display request from a plurality of node icons of the current flowchart; Determining the task node corresponding to the current node icon as the request task node; Determining the level of the sub-flowchart corresponding to the request task node as the request level.

3. The method according to claim 1, characterized in that The determining the request task node and the request level corresponding to the flowchart display request includes: In response to the flowchart being used to request the top-level flowchart of the business system, determining the root task node corresponding to the business system as the request task node, and determining the top level as the request level; In response to the flowchart being used to request a sub-flowchart of the business system, determining the root task node corresponding to the sub-flowchart as the request task node, and determining the level corresponding to the sub-flowchart as the request level.

4. The method according to claim 1, wherein Before receiving the flowchart display request, further including: Determining a plurality of configuration node icons and a plurality of dependency edges in a process configuration interface; For each of the configuration node icons, determining coordinate information of the configuration node icon in the process configuration interface; and generating attribute information of a configuration task node corresponding to the configuration node icon; wherein the attribute information includes: a task number and coordinate information corresponding to the configuration task node; For each of the dependency edges, determining a target node icon and a plurality of path node icons corresponding to the dependency edge; and generating dependency information corresponding to the dependency edge; wherein the dependency information includes: a task number corresponding to the target node icon and task numbers corresponding to each of the path node icons.

5. The method according to claim 4, wherein Before determining the plurality of configuration node icons and the plurality of dependency edges in the process configuration interface, further including: Receiving a flowchart configuration request and displaying the process configuration interface; Receiving an arrangement operation for the process configuration interface; Generating the plurality of configuration node icons and the plurality of dependency edges in the process configuration interface according to the arrangement operation.

6. The method according to claim 4, characterized in that The generating the attribute information of the configuration task node corresponding to the configuration node icon includes: Determining a parent task node and a sub-flowchart identifier of the configuration task node; wherein the sub-flowchart identifier is used to identify whether the configuration task node corresponds to a sub-flowchart; Generate the attribute information corresponding to the configuration task node; wherein, the attribute information includes: the task number corresponding to the configuration task node, the coordinate information corresponding to the configuration task node, the task number corresponding to the parent task node, and the sub-process identifier.

7. The method according to claim 4, characterized in that, After determining the multiple configuration node icons and multiple dependency edges in the process configuration interface, it further includes: Determine the target level corresponding to the process configuration interface; Combine the task numbers corresponding to each of the configuration node icons to generate a task node set corresponding to the target level.

8. The method according to claim 1, characterized in that After drawing the node icon corresponding to each of the descendant task nodes on the canvas according to the coordinate information corresponding to the descendant task node, it further includes: Determine the multiple display node icons in the canvas; For each of the display node icons, determine the running state of the task node corresponding to the display node icon; according to the running state, determine the display information corresponding to the display node icon; and display the display node icon on the canvas according to the display information.

9. A display device for a flowchart, characterized in that, It includes: A request receiving module, configured to receive a flowchart display request; A node determining module, configured to determine the request task node and request level corresponding to the flowchart display request, and determine multiple descendant task nodes of the request task node at the request level; An icon drawing module, configured to draw the node icon corresponding to each of the descendant task nodes on the canvas according to the coordinate information corresponding to the descendant task node; An edge connection module, configured to determine the dependency information corresponding to each of the descendant task nodes; Determine multiple path node icons corresponding to the dependency information from the multiple node icons on the canvas; and sequentially connect each of the path node icons through a directed edge.

10. An electronic device, characterized in that, It includes: One or more processors; A storage device, configured to store 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 method according to any one of claims 1-8.

11. A computer-readable medium having a computer program stored thereon, characterized in that , the program implements the method according to any one of claims 1-8 when executed by the processor.

Images