A workflow generation method for complex product development process

Abstract

This invention primarily relates to the field of system modeling technology. It provides a method for generating workflows for complex product development processes. This method involves establishing a workflow model to extract workflow objects, task objects, condition objects, and task flow objects; inputting the requirements definition of the workflow to be generated into the workflow model, and extracting the workflow objects, task objects, condition objects, and task flow objects respectively; matching the task objects extracted from the workflow model with the designer's capability model; and generating a complete workflow based on the matching results of the workflow objects, task objects, condition objects, task flow objects, and designer capability model. This ensures close connection between various stages of the manufacturing process, clarifies the flow relationships between stages, saves screening time, and ultimately improves the efficiency of the manufacturing process and the standardization of the manufactured products.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of data modeling, and in particular to a workflow generation method for a complex product development process. Background Art

[0002] The R&D process of modern intelligent equipment is integrated and collaborative, and is a system engineering with high complexity and high collaboration requirements. For example, in the R&D and design process of aircraft products, the orderly execution of various work tasks carried out by enterprises around the development of new products constitutes the product R&D workflow, which includes product design, strength verification, process design, cost accounting, quality inspection and other process links. These work tasks are carried out in an orderly manner by designers with relevant professional capabilities according to the business logic of product development. The work tasks are carried out accompanied by the generation, storage and transmission of process information data. The product R&D workflow needs to integrate work tasks, personnel, information flow, etc. into an organic whole, so as to achieve the purpose of orderly organizing product development.

[0003] The current problem faced by the actual product development and production process is that the various links in the production process are not closely connected, and the process design fails to fully consider the uncertainty and variability in actual production, resulting in a lack of effective communication and collaboration mechanisms between designers in different positions and departments in actual operations, and poor information and material transmission of work tasks, which leads to a disconnect between various task links. Taking the aircraft product development process as an example, it pays more attention to whether the product meets the functional requirements, but lacks systematic consideration or relatively less consideration of planning, production, sales, packaging, transportation, maintenance, operation and other links, resulting in low synergy in the entire product development process, which in turn causes problems such as high production process costs, difficult maintenance, and long manufacturing cycles. At the same time, in actual production, the professional technical classification and design capabilities of designers matching various design tasks are uneven, which may also cause some key processes to fail to be completed on time, thereby affecting the entire production progress. Summary of the invention

[0004] Technical Problems to be Solved by the Invention

[0005] This paper provides a workflow generation method for a complex product development process, aiming to improve the collaboration and efficiency of the product development workflow.

[0006] The technical solution adopted by the present invention to solve the above technical problems

[0007] A workflow generation method for a complex product development process, comprising:

[0008] Step S1: Establishing workflow model and designer capability model;

[0009] The workflow model is used to extract workflow objects, work task objects, condition objects and task flow objects; the workflow objects are used to describe the information of the workflow model; the work task objects are used to describe the work task information of each task node in the workflow; the condition objects are used to describe the work task completion standards of each task node in the workflow; the task flow objects are used to describe the flow relationship between task nodes;

[0010] Step S2: training the workflow model, inputting the requirement definition of the workflow to be generated into the workflow model, and extracting workflow objects, work task objects, condition objects, and task flow objects respectively;

[0011] Step S3: matching the designer capability model according to the work task objects extracted from the workflow model;

[0012] Step S4: Generate a complete workflow based on the matching results of the workflow objects, work task objects, condition objects, task flow objects extracted from the workflow model and the designer's capability model.

[0013] Furthermore, the designer capability model includes the designer's capability number, capability name, capability description and capability level.

[0014] Furthermore, step S3 specifically includes:

[0015] Step S31: identifying the design capability requirement of the corresponding task node according to the work task information of each task node in the work task object;

[0016] Step S32: matching the designer capability model according to the design capability requirements. If there is only one designer capability model matched, matching the designer corresponding to the designer capability model as the designer who completes the work task of the corresponding task node; if there is more than one designer capability model matched, proceeding to step S33;

[0017] Step S33: querying one by one whether the capability models of designers are associated with the work tasks being performed, excluding the capability models of designers associated with the work tasks being performed, and recording all the capability models of designers that are not associated with the tasks being performed;

[0018] Step S34: sort the capability levels of all the designer capability models that are not associated with the tasks being executed, and obtain the designer capability model with the highest capability level. If there is only one designer capability model with the highest capability level, match the designer corresponding to the designer capability model as the designer who completes the work task of the corresponding task node; if there is more than one designer capability model with the highest capability level, proceed to step S35;

[0019] Step S35: Pushing the capability models of all designers with the highest capability levels to the workflow modeler, who then selects the designer for the corresponding task node.

[0020] Furthermore, a designer is associated with multiple designer capability models according to professional classification.

[0021] Furthermore, the method also includes: after completing the work task of the task node, verifying the work task completion result according to the work task standard of the task node described by the condition object, and if it fails to pass the verification, prompting that entering the next task node pointed to by the task flow object is not allowed.

[0022] Furthermore, the method further comprises step S5: generating a workflow visualization flowchart based on the workflow generated in step S4, specifically comprising the following steps:

[0023] Step S51: searching for a work task object in the workflow, and arranging all task nodes in the work task object into a task node queue according to the flow relationship between task nodes described by the work task flow object;

[0024] Step S52: Create a canvas, determine the origin of the canvas, and place the task nodes in the task node queue into the canvas according to the flow relationship between the task nodes described by the task flow object;

[0025] Step S53: Generate a flow line according to the coordinates and size information of the task nodes in the canvas and the flow relationship between the task nodes described by the task flow object.

[0026] Furthermore, the method also includes, after the workflow visualization flowchart is drawn, writing the coordinates, size information, starting task control point, and ending task control point of the task node in the canvas into the work task object; writing the data in the workflow object, work task object, condition object, and task flow object into a database, and directly calling the stored data in the database when the workflow visualization flowchart needs to be reproduced.

[0027] Beneficial effects of the present invention

[0028] The workflow generation method of a complex product development process described in the present invention extracts workflow objects, work task objects, condition objects and task flow objects from the requirement definition of the workflow to be generated by establishing a workflow model, and matches appropriate designers according to the work task information of each task node in the work task object, so as to quickly define a full life cycle workflow that adapts to the product development process, so that each task node in the product development process is closely connected, and the flow relationship between each task node is clarified, thereby improving the efficiency of the product development process and the standardization of product development. At the same time, the generated workflow is visualized to generate a workflow visualization flow chart, so that the complex product development process can be explicitly displayed in a graphical form, which is convenient for managers to more intuitively grasp the information of the entire product development process. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 A flow relationship diagram between task nodes in a work task object in an embodiment of the present invention;

[0030] Figure 2 It is a schematic diagram of control points;

[0031] Figure 3 This is a flow line diagram when the end task node is above the start task node;

[0032] Figure 4 This is a flow line diagram when the end task node is below the start task node;

[0033] Figure 5 This is a flow line diagram when the end task node is located on the right side of the start task node;

[0034] Figure 6 This is a flow line diagram when the end task node is located on the left side of the start task node;

[0035] Figure 7 This is a flow line diagram when the end task node is above the right of the start task node;

[0036] Figure 8 This is a flow line diagram when the end task node is at the lower right of the start task node;

[0037] Fig. 9 This is a flow line diagram when the end task node is at the upper left of the start task node;

[0038] Fig.10 This is a flow line diagram when the end task node is at the lower left of the start task node. DETAILED DESCRIPTION

[0039] The workflow generation method of a complex product development process described in the present invention specifically includes:

[0040] Step S1: Establish a workflow model and a designer capability model.

[0041] The workflow model is used to extract workflow objects, work task objects, condition objects and task flow objects; the workflow objects are used to describe the information of the workflow model; the work task objects are used to describe the work task information of each task node in the workflow; the condition objects are used to describe the work task completion standards of each task node in the workflow; the task flow objects are used to describe the flow relationship between task nodes.

[0042] The data in the workflow object specifically includes the workflow model number, workflow name, workflow description, data type and data status of the workflow model, the R&D stage corresponding to the workflow, workflow creation time, creator, ownership user and modification time, etc.

[0043] A work task object may contain multiple task nodes, so there is a one-to-many relationship between the workflow object and the task nodes in the work task object. The data in the work task object specifically includes the task node number, task node name, task node description, task node data type, task node specialty, task node data status, task node workflow number, task node start time, completion ratio, completion time, sorting sequence number, etc.

[0044] The task flow object is used to describe the flow relationship between multiple task nodes. Task nodes can be serial or parallel. The starting task node represents the task node that is executed first in a task flow, and the ending task node represents the task node that is executed later in a task flow. A workflow can contain multiple task flow objects, and the workflow object and the task flow object have a one-to-many relationship. The data in the task flow object specifically includes: the workflow number, the starting task node number, the ending task node number, the data status and modification time, etc.

[0045] The condition object is used to verify the completion result of the task node. If the verification is qualified, the next task node will be executed according to the flow relationship between the task nodes described by the task flow object. If the verification is unqualified, the previous task node will be returned. The data in the condition object specifically includes: condition number, condition name, condition description, data type, major, responsible person, data status, workflow number, and corresponding task node number.

[0046] Taking the aircraft R&D workflow as an example, different task nodes require the participation of designers with different professional classifications and capability levels. The design capabilities involved specifically include key technical capabilities such as structural design capability, strength calculation capability, various system design simulation capabilities, process design capability, quality analysis capability, and project coordination capability. Different capabilities can also be subdivided, such as structural design capability including wing structure design capability, fuselage structure design capability, and nose design capability. When completing the work tasks at different task nodes, it is necessary to match designers with relevant design capabilities and capability levels. Therefore, the capabilities of designers are described, and a designer capability model is established. The designer capability model is matched according to the work task information of the task node described by the work task object, so as to match the appropriate designer for different task nodes. The data in the designer capability model specifically includes capability number, capability name, capability description, capability level, designer number, and update time. When a designer has multiple types of design capabilities at the same time, the designer is associated with multiple designer capability models.

[0047] Step S2: training the workflow model, inputting the requirement definition of the workflow to be generated into the workflow model, and extracting workflow objects, work task objects, condition objects and task flow objects respectively.

[0048] Step S3: Matching the designer capability model according to the work task objects extracted from the workflow model, specifically including the following steps:

[0049] Step S31: identifying the design capability requirement of the corresponding task node according to the work task information of each task node in the work task object;

[0050] Step S32: matching the designer capability model according to the design capability requirements. If there is only one designer capability model matched, matching the designer corresponding to the designer capability model as the designer who completes the work task of the corresponding task node; if there is more than one designer capability model matched, proceeding to step S33;

[0051] Step S33: querying one by one whether the capability models of designers are associated with the work tasks being performed, excluding the capability models of designers associated with the work tasks being performed, and recording all the capability models of designers that are not associated with the tasks being performed;

[0052] Step S34: sort the capability levels of all the designer capability models that are not associated with the tasks being executed, and obtain the designer capability model with the highest capability level. If there is only one designer capability model with the highest capability level, match the designer corresponding to the designer capability model as the designer who completes the work task of the corresponding task node; if there is more than one designer capability model with the highest capability level, proceed to step S35;

[0053] Step S35: Pushing the capability models of all designers with the highest capability levels to the workflow modeler, who then selects the designer for the corresponding task node.

[0054] Step S4: Generate a complete workflow based on the matching results of the workflow objects, work task objects, condition objects, task flow objects extracted from the workflow model and the designer's capability model. Figure 1 As shown in the figure, the task nodes in the work task objects of the aircraft development process include A system design, B system design, structural design, system simulation, strength verification, process review, finished product procurement, processing and manufacturing, assembly, and quality inspection; the task flow objects include A system design and B system design. The next task node of the flow is system simulation, and the next task node of the flow of structural design is strength verification and process review. If the system simulation result passes the standard verification of the work task completion of condition object "X", the next task node is finished product procurement. If the system simulation structure fails, it returns to the task node and redesigns. Similarly, if the strength verification result does not pass the verification of condition object "X", it returns to structural design. If it passes, it enters the process design task node. After the process design is completed, it enters the processing and manufacturing node. After the processing and manufacturing is completed, it enters the assembly node according to the purchased finished product. After the assembly is completed, it enters the quality inspection stage. If the quality inspection passes, the workflow is completed and delivered. If the quality inspection fails, it returns to processing and manufacturing and assembly.

[0055] Step S5: Generate a workflow visualization flowchart based on the workflow generated in step S4.

[0056] The workflow generated in step 4 is represented by creating a visual flowchart in the canvas in the form of drag-and-drop human-computer interaction, which specifically includes the following steps:

[0057] Step S51: searching for a work task object in the workflow, and arranging all task nodes in the work task object into a task node queue according to the flow relationship between task nodes described by the work task flow object;

[0058] Step S52: Create a canvas, determine the origin of the canvas, and place the task nodes in the task node queue into the canvas according to the flow relationship between the task nodes described by the task flow object;

[0059] Step S53: Generate a flow line according to the coordinates and size information of the task nodes in the canvas and the flow relationship between the task nodes described by the task flow object.

[0060] Furthermore, according to the coordinates and size information of the task nodes in the canvas, combined with the flow relationship between the task nodes described by the task flow object, generating the flow line specifically includes:

[0061] 1) Calculate the control points that can be used as the starting point or ending point of the flow line based on the size information of the task node in the canvas. Figure 2 As shown in the figure, when the task node icon is a rectangle, the control points are the midpoints of the four sides of the task node icon, respectively C UPP , C LWR , C L , C R , the coordinates of the center point O of the task node are marked as (X o , Y o ), the width of the task node is L and the height is H. The coordinate calculation formula of the 4 control points is as follows: C UPP The coordinates are: X=X o , Y=Y o +H / 2;C LWR The coordinates are: X=X o , Y=Y o -H / 2;C L The coordinates are: X=X o -L / 2, Y=Y o ; C R The coordinates are: X=X o +L / 2,Y=Y o ;

[0062] 2) According to the center coordinates O of the starting task node in the canvas S (X oS , Y oS ) and the center point coordinates O of the end task node E (X oE , Y oE ) Determine the relative position relationship between the start task node and the end task node; the start task node is the task node executed first in a task flow, and the end task node is the task node executed later in a task flow; the specific judgment rules are as follows:

[0063] If X oS =X oE And Y oS <Y oE , it means that the starting task node and the ending task node are at the same position in the vertical direction, and the ending task node is above the starting task node;

[0064] If X oS =X oE And Y oS >Y oE , it means that the starting task node and the ending task node are at the same position in the vertical direction, and the ending task node is below the starting task node;

[0065] If Y oS =Y oE And X oS <X oE , it means that the starting task node and the ending task node are in the same position horizontally, and the ending task node is located to the right of the starting task node;

[0066] If Y oS =Y oE And X oS >X oE , it means that the starting task node and the ending task node are in the same position horizontally, and the ending task node is located to the left of the starting task node;

[0067] If Y oE -Y oS >0 and X oE -X oS >0, it means the end task node is above and to the right of the start task node;

[0068] If Y oE -Y oS <0 and X oE -X oS >0, it means the end task node is below and to the right of the start task node;

[0069] If Y oE -Y oS >0 and X oE -X oS <0, it means the end task node is above and to the left of the start task node;

[0070] If Y oE -Y oS <0 and X oE -X oS <0, it means the end task node is at the lower left of the start task node;

[0071] 3) According to the relative position relationship between the start task node and the end task node, select the start control point from the control points of the start task node, select the end control point from the control points of the end task node, and generate a flow line with an arrow pointing from the start control point to the end control point. Since the position of each task node in the workflow is customized by the designer in an interactive way, this rule does not consider the situation where multiple task nodes partially or completely overlap. The flow line generation rules are as follows:

[0072] When X oS =X oE And Y oS <Y oE When the end task node is above the start task node, the C of the start task node is S-UPP As the starting control point of the flow line, the C of the end task node E-LWR As the end control point of the flow line, the generated flow line is as follows Figure 3 As shown. oS =X oE And Y oS >Y oE When the end task node is below the start task node, the C of the start task node is S-LWR As the starting control point of the flow line, the C of the end task node E-UPP As the end control point of the flow line, the generated flow line is as follows Figure 4 As shown. oS =Y oE And X oS <X oE When the end task node is on the right side of the start task node, the C of the start task node S-R As the starting control point of the flow line, the C of the end task node E-L As the end control point of the flow line, the generated flow line is as follows Figure 5 As shown. oS =Y oE And X oS >X oE When the end task node is on the left side of the start task node, the C S-L As the starting control point of the flow line, the C of the end task node E-R As the end control point of the flow line, the generated flow line is as follows Figure 6 As shown. oE -Y oS >0 and X oE -X oS >0, when the end task node is above and to the right of the start task node, select the C of the start task node. S-UPP As the starting control point of the flow line, the C of the end task nodeE-L As the end control point of the flow line, (X oS , Y oE ) point is taken as the turning point of the flow line, and the generated flow line is as follows Figure 7 As shown. oE -Y oS <0 and X oE -X oS >0 is true, the end task node is at the lower right of the start task node, then select the C of the start task node S-LWR As the starting control point of the flow line, the C of the end task node E-L As the end control point of the flow line, (X oS , Y oE ) point is taken as the turning point of the flow line, and the generated flow line is as follows Figure 8 As shown. oE -Y oS >0 and X oE -X oS <0 is true, the end task node is at the upper left of the start task node, then select the C of the start task node S-UPP As the starting control point of the flow line, the C of the end task node E-R As the end control point of the flow line, (X oS , Y oE ) point is taken as the turning point of the flow line, and the generated flow line is as follows Fig. 9 As shown. oE -Y oS <0 and X oE -X oS <0 is true, the end task node is at the lower left of the start task node, then select the C of the start task node S-LWR As the starting control point of the flow line, the C of the end task node E-R As the end control point of the flow line, (X oS , Y oE ) point is taken as the turning point of the flow line, and the generated flow line is as follows Fig.10 Repeat the above steps to generate all flow lines and draw a complete workflow visualization flowchart.

[0073] After the workflow visualization flowchart is drawn, the coordinates and size information of the task node in the canvas, as well as the starting control point and the ending control point are written into the work task object; the data in the workflow object, work task object, condition object and task flow object are written into the database, and when the workflow visualization flowchart needs to be reproduced, the content in the database is directly called to reproduce the workflow visualization flowchart in the canvas.

Claims

1. A workflow generation method for a complex product development process, characterized in that: include: Step S1: Establishing workflow model and designer capability model; The workflow model is used to extract workflow objects, work task objects, condition objects and task flow objects; the workflow objects are used to describe the information of the workflow model; the work task objects are used to describe the work task information of each task node in the workflow; the condition objects are used to describe the work task completion standards of each task node in the workflow; the task flow objects are used to describe the flow relationship between task nodes; Step S2: training the workflow model, inputting the requirement definition of the workflow to be generated into the workflow model, and extracting workflow objects, work task objects, condition objects, and task flow objects respectively; Step S3: matching the designer's capability model according to the work task objects extracted from the workflow model; Step S4: Generate a complete workflow based on the matching results of the workflow objects, work task objects, condition objects, task flow objects extracted from the workflow model and the designer's capability model; Step S5: Generate a workflow visualization flowchart based on the workflow generated in step S4; step S5 specifically includes: Step S51: searching for a work task object in the workflow, and arranging all task nodes in the work task object into a task node queue according to the flow relationship between task nodes described by the work task flow object; Step S52: Create a canvas, determine the origin of the canvas, and place the task nodes in the task node queue into the canvas according to the flow relationship between the task nodes described by the task flow object; Step S53: Generate a flow line according to the coordinates and size information of the task nodes in the canvas and the flow relationship between the task nodes described by the task flow object; Step S53 specifically includes: the task node icon is a rectangle, and the coordinates of the center point O of the rectangular task node are marked as (X o , Y o ), the width of the task node is L, the height is H; the midpoint C of the four sides of the rectangular task node UPP , C LWR , C L , C R As a control point, C UPP The coordinates are: X=X o , Y=Y o +H / 2;C LWR The coordinates are: X=X o , Y=Y o -H / 2;C L The coordinates are: X=X o -L / 2, Y=Y o ; C R The coordinates are: X=X o +L / 2,Y=Y o ; According to the center point coordinate O of the starting task node in the canvas S (X oS , Y oS ) and the center point coordinates O of the end task node E (X oE , Y oE ) Determine the relative position relationship between the start task node and the end task node; the start task node is the task node executed first in a task flow, and the end task node is the task node executed later in a task flow; the relative position relationship determination rule between the start task node and the end task node is as follows: if X oS =X oE And Y oS <Y oE , it means that the starting task node and the ending task node are at the same position in the vertical direction, and the ending task node is above the starting task node; if X oS =X oE And Y oS >Y oE , it means that the starting task node and the ending task node are in the same position in the vertical direction, and the ending task node is below the starting task node; if Y oS =Y oE And X oS <X oE , it means that the starting task node and the ending task node are in the same position horizontally, and the ending task node is located to the right of the starting task node; if Y oS =Y oE And X oS >X oE , it means that the starting task node and the ending task node are in the same position horizontally, and the ending task node is located to the left of the starting task node; if Y oE -Y oS >0 and X oE -X oS >0, it means the end task node is above and to the right of the start task node; if Y oE -Y oS <0 and X oE -X oS >0, it means the end task node is below and to the right of the start task node; if Y oE -Y oS >0 and X oE -X oS <0, it means the end task node is at the upper left of the start task node; if Y oE -Y oS <0 and X oE -X oS <0, it means the end task node is at the lower left of the start task node; When the end task node is above the start task node, the C S-UPP As the starting control point of the flow line, the C of the end task node E-LWR As the end control point of the flow line, generate the flow line; when the end task node is below the start task node, S-LWR As the starting control point of the flow line, the C of the end task node E-UPP As the end control point of the flow line, generate the flow line; when the end task node is on the right side of the start task node, the C of the start task node S-R As the starting control point of the flow line, the C of the end task node E-L As the end control point of the flow line, generate the flow line; when the end task node is on the left side of the start task node, S-L As the starting control point of the flow line, the C of the end task node E-R As the end control point of the flow line, generate the flow line; when the end task node is above the right of the start task node, change the C of the start task node S-UPP As the starting control point of the flow line, the C of the end task node E-L As the end control point of the flow line, (X oS , Y oE ) point as the turning point of the flow line to generate the flow line; when the end task node is at the lower right of the start task node, the C of the start task node is S-LWR As the starting control point of the flow line, the C of the end task node E-L As the end control point of the flow line, (X oS , Y oE ) point as the turning point of the flow line to generate the flow line; when the end task node is at the upper left of the start task node, the C of the start task node is S-UPP As the starting control point of the flow line, the C of the end task node E-R As the end control point of the flow line, (X oS , Y oE ) point as the turning point of the flow line to generate the flow line; when the end task node is at the lower left of the start task node, the C of the start task node is S-LWR As the starting control point of the flow line, the C of the end task node E-R As the end control point of the flow line, (X oS , Y oE ) point is used as the turning point of the flow line to generate the flow line.

2. The workflow generation method for a complex product development process according to claim 1, characterized in that: The designer capability model includes the designer's capability number, capability name, capability description and capability level.

3. The workflow generation method for a complex product development process according to claim 2, characterized in that: Step S3 specifically includes: Step S31: identifying the design capability requirement of the corresponding task node according to the work task information of each task node in the work task object; Step S32: matching the designer capability model according to the design capability requirements. If there is only one designer capability model matched, matching the designer corresponding to the designer capability model as the designer who completes the work task of the corresponding task node; if there is more than one designer capability model matched, proceeding to step S33; Step S33: querying one by one whether the capability models of designers are associated with the work tasks being performed, excluding the capability models of designers associated with the work tasks being performed, and recording all the capability models of designers that are not associated with the tasks being performed; Step S34: sort the capability levels of all the designer capability models that are not associated with the tasks being executed, and obtain the designer capability model with the highest capability level. If there is only one designer capability model with the highest capability level, match the designer corresponding to the designer capability model as the designer who completes the work task of the corresponding task node; if there is more than one designer capability model with the highest capability level, proceed to step S35; Step S35: Pushing the capability models of all designers with the highest capability levels to the workflow modeler, who then selects the designer for the corresponding task node.

4. The method for generating a workflow for a complex product development process according to claim 3, characterized in that: One designer is associated with multiple designer capability models based on professional classification.

5. The workflow generation method for a complex product development process according to claim 1, characterized in that: The method also includes: after completing the work task of the task node, verifying the work task completion result according to the work task standard of the task node described by the condition object, and if it fails to pass the verification, prompting that entering the next task node pointed to by the task flow object is not allowed.

6. The workflow generation method for a complex product development process according to claim 1 is characterized in that: The method also includes, after the workflow visualization flowchart is drawn, writing the coordinates, size information, start task control point, and end task control point of the task node in the canvas into the work task object; storing the data in the workflow object, work task object, condition object, and task flow object in a database, and directly calling the stored data in the database when the workflow visualization flowchart needs to be reproduced.

Images