Visual page driven structured process modeling, execution and dynamic management and control method

Abstract

The invention discloses a structured process modeling, execution and dynamic management and control method driven by a visual page, and belongs to the field of computer software and business process management.The technical scheme is that the method comprises the steps that a process model is established, and process model data is generated; inputting the data of the process model into a JSON converter to obtain a BPMN 2.0 XML (Extensible Markup Language) document; deploying the BPMN 2.0 XML document to a process engine, loading the BPMN 2.0 XML document by the process engine and taking the BPMN 2.0 XML document as an execution basis; performing simulation prediction on process execution through a stateless simulation engine based on a BPMN 2.0 XML (Extensible Markup Language) document and input simulation parameters; displaying a flow chart, a node state and a historical flow path on the basis of an execution state output by the flow engine, and providing an operation entry, so that a service user can initiate a dynamic operation instruction; the dynamic operation instruction is sent to a jump module; and collecting the execution log and the operation record to generate a statistical report. The method has the beneficial effect that the method for modeling, executing and dynamically managing and controlling the structured process driven by the visual page is provided.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of computer software and business process management, in particular to a structured process modeling, execution and dynamic control method based on visual page driving. BACKGROUND

[0002] In the process of enterprise digital transformation, business process management (BPM) realizes business standardization through process modeling, execution and optimization, and BPMN (business process modeling notation) as an international standard for process modeling is widely used in various process management systems. Although traditional BPMN-based process modeling tools can meet the needs of standardized process design, they have the following limitations: 1. Insufficient modeling flexibility: Non-technical users cannot quickly build complex processes, and the support for non-standard process actions such as rejection, withdrawal, and jump is insufficient, requiring secondary development through code, increasing implementation costs.

[0003] 2. Lack of execution visualization: The process execution process is only presented in the form of a task list or a log, lacking a dynamic display of a flowchart, making it difficult for initiators and approvers to grasp the complete execution trajectory of the process instance in real time.

[0004] 3. Weak dynamic control capability: Traditional systems strictly follow BPMN process definitions, and administrators cannot directly intervene in the process during the execution phase (such as temporarily modifying approvers or forcibly jumping to a node), making it inefficient to adjust in the face of sudden business changes, and lacking multi-dimensional process execution analysis reports, making it difficult to support data-driven process optimization.

[0005] 4. Existing BPMN-based process management systems lack efficient process verification methods during the design phase, and users need to verify the logic correctness through real process instances after publication, leading to problems such as "incomplete process branch coverage", "process condition errors", and "incorrect approver allocation" often being discovered after actual operation to specific nodes, increasing iteration costs. Especially for processes involving complex decision conditions (such as multi-dimensional permission judgment and dynamic data association), it is difficult to predict the actual execution effect through static modeling alone.

[0006] With the increasing demand for business flexibility and real-time control in enterprises, there is an urgent need for a new process management method that retains the advantages of BPMN visual modeling, provides process prediction means, supports extended process execution actions, and provides full-process visual execution and dynamic intervention capabilities SUMMARY The purpose of the present application is to provide a visual page-driven structured process modeling, execution and dynamic control method.

[0007] This invention is achieved through the following measures: In a first aspect, this embodiment provides a method for modeling, executing, and dynamically managing a structured process driven by a visual page, characterized by including: S100. On the visual modeling page, based on the BPMN 2.0 element library, a process model is created by dragging and dropping, and process model data represented in JSON structure is generated. S200. Input the process model data into a JSON converter to parse and convert the process model data to obtain a BPMN 2.0 XML document carrying the extended control attributes; S300. Deploy the converted BPMN 2.0 XML document carrying the extended control attributes to the process engine, where it is loaded and used as the basis for the execution of subsequent process instances. S400. During the design phase and before the process is initiated, based on the BPMN 2.0 XML document and the input simulation parameters, the process execution is simulated and predicted through a stateless simulation engine to obtain one or more predicted execution paths and the predicted handlers of each user task node, and the predicted execution paths are visualized on the visualization modeling page. S500. During the execution of the process instance, based on the execution status output by the process engine, the flowchart, node status and historical flow path are displayed on the front-end page through the visualization module, and an operation entry is provided so that business users and administrators can initiate dynamic operation commands such as withdrawal, rejection, forced jump and task reassignment on the front-end page. S600. The dynamic operation command is sent to the jump module that works in conjunction with the process engine. The jump module adjusts the execution status of the process instance according to the extended control attribute and the preset jump logic, including ending the affected execution instance and creating a new execution instance on the target activity. S700. Collect and summarize the execution logs, node processing records, and operation records of the jump module of the process instance to generate multi-dimensional statistical reports that include at least efficiency analysis, quality analysis, and resource allocation analysis, which are used to guide subsequent process optimization.

[0008] Furthermore, the process model data includes at least: The activity list describes the identifier, type, layout position, and node attributes of each activity node; The connector list describes the source node, target node, layout control point, and connection attributes of each connector. Extend control attributes to configure rejection permissions, withdrawal permissions, form field permissions, and connection condition configuration information on activity nodes and / or connection lines; Further, S200 includes: S201. Receive and parse the JSON format process model data, and extract the activity list and the connection list; S202. Initialize the BPMN XML document object; S203. Iterate through the list of activities and, for each activity: S203A. Create the corresponding BPMN XML element according to the activity type; S203B: Process the standard BPMN attributes of the activity and assign them to the BPMN XML element; S203C: Process the extended control attributes associated with the activity and add them to the BPMN XML element through the BPMN extension mechanism; S203D: If the activity contains sub-activities, then recursively execute the traversal processing of S203 with the list of sub-activities as input; S204. Traverse the list of connecting lines, and for each connecting line: S204A, Create the BPMN XML element corresponding to the connection line; S204B, Set the source node reference and target node reference of the connector element; S204C. If the connection line is a conditional flow, then create and populate BPMN conditional expression elements according to the conditional configuration on the connection line. S205. Serialize the BPMN XML document object into an XML string and output a BPMN 2.0 XML document that conforms to the BPMN 2.0 specification and contains the extended control attributes.

[0009] Furthermore, in S400, when the stateless simulation engine performs process execution simulation prediction: Execution path and status information are maintained only in memory, and no data is written to the business database; It supports single-step execution mode, pausing after each simulated activity and waiting for a continue command before executing the next activity; it also supports setting breakpoints, pausing when the simulation reaches a preset breakpoint activity, allowing users to adjust simulation parameters and then continue execution.

[0010] Furthermore, the S400 also includes: Before the process is officially initiated, the system receives real business form data filled in by the initiator and inputs the real business form data as simulation parameters into the stateless simulation engine. Based on the real business form data, the system simulates the execution path under actual conditions and the predicted handlers for each user task node. It also calculates the estimated processing time for each node and the estimated processing time for the entire process by combining historical process instance running data. The system then displays the estimated execution path, predicted handlers, and estimated processing time to the initiator on the front-end page.

[0011] Furthermore, in S500, the step of displaying the flowchart, node status, and historical flow path through the visualization module includes: Draw the flowchart on the front-end page using a layout consistent with the modeling phase; Completed nodes and connections are highlighted, currently active nodes are marked with a status indicator, and rejected nodes are marked with a special style. When a user clicks on any node, the system displays the person who handled the task, the time of handling, the handling opinion, and related attachments.

[0012] Furthermore, in S600, the workflow of the jump module includes: Receive a redirection request and identify the target activity; analyze the execution status of the current process instance; calculate the affected execution scope based on the current execution unit and the target activity; instruct the process engine to terminate the affected execution instance and clean up related resources; trigger the BPMN activity termination listener for the activity that is forcibly terminated; The process engine is instructed to create a new execution instance on the target activity, so that the process instance continues execution from the target activity.

[0013] Furthermore, in S700, the multi-dimensional statistical report includes at least one of the following: Efficiency analysis reports are used to display the average processing time, timeout rate, and number of items in transit for each process and node; quality analysis reports are used to count the number of rejections, withdrawals, and non-linear jumps at each node and the distribution of their causes; resource allocation analysis reports are used to count the number of tasks, completion efficiency, and timeout status for each processor.

[0014] Secondly, this embodiment provides a visual page-driven structured process modeling, execution, and dynamic control system, characterized in that it includes: The modeling module is used to create process models in the visual modeling page by dragging and dropping elements based on the BPMN 2.0 element library, and to generate process model data represented in JSON structure. The conversion module is used to input the process model data into a JSON converter for parsing and conversion, to obtain a BPMN 2.0 XML document carrying the extended control attributes; The deployment module is used to deploy the BPMN 2.0 XML document to the process engine, which loads it and uses it as the basis for the execution of subsequent process instances. The simulation module is used to simulate and predict the execution of the process based on the BPMN 2.0 XML document and simulation parameters during the design phase and before the process is initiated. By simulating and predicting the execution of the process through the stateless simulation engine, one or more predicted execution paths and the predicted handlers of each user task node are obtained, and the predicted execution paths are visualized on the visualization modeling page. The visualization execution module is used to display the flowchart, node status and historical flow path on the front-end page based on the execution status output by the process engine during the process instance operation. It also provides an operation entry point for business users and administrators to initiate dynamic operation commands such as withdrawal, rejection, forced jump and task reassignment. The jump module is used to receive the dynamic operation instructions and, in collaboration with the process engine, adjust the execution state of the process instance according to the extended control attributes and preset jump logic, including terminating the affected execution instance and creating a new execution instance on the target activity. The analysis module is used to collect and summarize the execution logs of the process instance, node processing records, and operation records of the jump module, and generate efficiency analysis reports, quality analysis reports, and resource allocation analysis reports.

[0015] Thirdly, this embodiment provides a computer device, including a processor and a memory, wherein the memory stores a computer program that can run on the processor, characterized in that, when the processor executes the computer program, it implements the visual page-driven structured process modeling, execution and dynamic control method.

[0016] The beneficial effects of the technical solution provided by the embodiments of this invention are as follows: Compared with the prior art, this invention has the following beneficial effects: It realizes closed-loop management of the process from "modeling - deployment - design-phase prediction - runtime execution - post-analysis". This invention adopts the visual modeling method of BPMN 2.0 specification, uniformly storing the process model obtained by users through drag-and-drop configuration as JSON structure process model data, and automatically generating BPMN 2.0 XML documents with extended management attributes through a JSON converter. Combined with a stateless simulation engine, this makes the process form a closed loop from design, verification, operation to evaluation, significantly improving the correctness and predictability of process configuration and reducing the risk of going live. Through the stateless simulation engine, this invention can predict the execution path of the process based on BPMN 2.0 XML documents and simulation parameters during the design phase and before the process is initiated. It can detect problems such as gateway condition configuration errors, no available branches, and potential infinite loops in advance. At the same time, combined with historical process instance running data, it calculates and displays the estimated processing time of each node and the overall process to the initiator, thereby greatly reducing the production accidents caused by process configuration errors and the cost of frequent rollback modifications. This invention stores extended control attributes for activities and connectors in the process model and works in conjunction with the process engine through a jump module. This enables various extended process operations based on configuration, such as withdrawal, rejection, forced jumps across nodes, and task reassignment, without requiring intrusive modifications to the standard BPMN engine kernel. Compared to traditional methods that require custom development or direct database manipulation, this invention achieves flexible runtime adjustment capabilities at a lower cost, while avoiding impacts on engine upgrades and maintenance. Attached Figure Description

[0017] To more clearly illustrate the technical solution of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings listed below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Fig. 1 This is a flowchart of the visual page-driven structured process modeling, execution, and dynamic control method in this embodiment of the invention; Fig. 2 This is a flowchart of the JSON converter's parsing and conversion process; Fig. 3 This is a flowchart for the process engine and jump module. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments. Of course, the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0020] Example 1: See Figs. 1-3 This embodiment provides a visual page-driven method for structured process modeling, execution, and dynamic control, characterized by including: S100. In the visual modeling page, based on the BPMN 2.0 element library, users create process models by dragging and dropping, generating process model data represented in JSON structure. In practical applications, the visual modeling page typically includes: a BPMN 2.0 element toolbar, a central canvas area, and a right-hand attribute configuration panel. Users drag BPMN elements such as start events, end events, user tasks, service tasks, gateways, and sub-processes from the toolbar onto the canvas, adjusting their positions and connections using the mouse to form a complete process topology. While the user is modeling, the system maintains the process model as a JSON-structured process model data. This process model data includes: The process model data includes at least: The activity list describes the identifier, type, layout position, and node attributes of each activity node; The connector list describes the source node ID, target node ID, layout control point, and connection attributes (sequential flow, default flow, etc.) of each connector. Extend control attributes to configure rejection permissions, withdrawal permissions, form field permissions, and connection condition configuration information on activity nodes and / or connection lines.

[0021] S200. Input the process model data into a JSON converter to parse and convert the process model data to obtain a BPMN 2.0 XML document carrying the extended control attributes; The JSON converter can be implemented as a component in the backend service. After receiving the aforementioned JSON process model data, it parses the activity list and connector list according to predetermined mapping rules, constructs a BPMN 2.0 XML DOM object or equivalent data structure in memory, and writes the extended control attributes recorded in the JSON into the XML document through the BPMN extension mechanism. This ensures that the generated BPMN 2.0 XML document not only meets the standard specifications but also contains the extended control information defined in this invention, specifically including: S201. Receive and parse the JSON format process model data, and extract the activity list and the connection list; S202. Initialize the BPMN XML document object; S203. Iterate through the list of activities and, for each activity: S203A. Create the corresponding BPMN XML element according to the activity type; S203B: Process the standard BPMN attributes of the activity and assign them to the BPMN XML element; S203C: Process the extended control attributes associated with the activity and add them to the BPMN XML element through the BPMN extension mechanism; S203D: If the activity contains sub-activities, then recursively execute the traversal processing of S203 with the list of sub-activities as input; S204. Traverse the list of connecting lines, and for each connecting line: S204A, Create the BPMN XML element corresponding to the connection line; S204B, Set the source node reference and target node reference of the connector element; S204C. If the connection line is a conditional flow, then create and populate BPMN conditional expression elements according to the conditional configuration on the connection line. S205. Serialize the BPMN XML document object into an XML string and output a BPMN 2.0 XML document that conforms to the BPMN 2.0 specification and contains the extended control attributes.

[0022] S300. Deploy the converted BPMN 2.0 XML document carrying the extended control attributes to the process engine, where it is loaded and used as the basis for the execution of subsequent process instances. In this step, the system deploys the aforementioned BPMN 2.0 XML document to the process engine via the deployment API provided by the process engine. The process engine assigns a unique process definition ID to this process definition and persists the XML document. Subsequently, when the business system initiates a process instance, it can reference this process definition ID to have the process engine create and run the process instance.

[0023] S400. During the design phase and before the process is initiated, based on the BPMN 2.0 XML document and the input simulation parameters, the process execution is simulated and predicted through a stateless simulation engine to obtain one or more predicted execution paths and the predicted handlers of each user task node, and the predicted execution paths are visualized on the visualization modeling page. When the stateless simulation engine performs process execution simulation prediction: Execution path and status information are maintained only in memory, and no data is written to the business database; It supports single-step execution mode, pausing after each simulated activity and waiting for a continue command before executing the next activity; it also supports setting breakpoints, pausing when the simulation reaches a preset breakpoint activity, allowing users to adjust simulation parameters and then continue execution.

[0024] The S400 also includes: Before the process is officially initiated, the system receives real business form data filled in by the initiator and inputs the real business form data as simulation parameters into the stateless simulation engine. Based on the real business form data, the system simulates the execution path under actual conditions and the predicted handlers for each user task node. It also calculates the estimated processing time for each node and the estimated processing time for the entire process by combining historical process instance running data. The system then displays the estimated execution path, predicted handlers, and estimated processing time to the initiator on the front-end page.

[0025] Before the process is officially released to the business, the target process definition can be selected and simulation parameters (such as amount, department, initiator role, etc.) can be entered on the visual modeling page. The system calls the stateless simulation engine to load the corresponding BPMN 2.0 XML document and simulates execution from the process start node based on gateway conditions, connection configurations, etc. During the simulation execution, the predicted handler is calculated at the user task node based on the configured candidate users, candidate groups, organizational structure, etc., and the next path is calculated at the gateway based on the conditional expression, thus obtaining one or more predicted execution paths. The system returns the simulated path to the front end and highlights the nodes and connections passed through on the modeling page, allowing designers to intuitively check whether the process configuration is reasonable. Before the process is initiated, after the initiator fills in the real business form data, the stateless simulation engine can also be called to perform a "pre-initiation prediction", using real data to extrapolate the path and display the predicted handlers and possible execution paths for each subsequent approval node, showing the initiator the process flow and estimated time.

[0026] S500. During the execution of the process instance, based on the execution status output by the process engine, the flowchart, node status and historical flow path are displayed on the front-end page through the visualization module, and an operation entry is provided so that business users and administrators can initiate dynamic operation commands such as withdrawal, rejection, forced jump and task reassignment on the front-end page. In S500, the step of displaying the flowchart, node status, and historical flow path through the visualization module includes: Draw the flowchart on the front-end page using the same layout as the modeling phase; Completed nodes and connections are highlighted, currently active nodes are marked with their status, and rejected nodes are marked with a special style. Node status: Clearly indicate the current status of each node, such as "Pending," "Processing," "Completed," "Rejected," "Withdrawn," etc., and can be distinguished by different colors or icons. When a user clicks on any node, the system displays the person who handled the process, the processing time, the processing comments, and related attachments. Workflow path: Clearly indicate the paths that the process instance has already traversed and is currently active using highlighted or bold lines, and the system can also predict possible future paths.

[0027] S600. The dynamic operation command is sent to the jump module that works in conjunction with the process engine. The jump module adjusts the execution status of the process instance according to the extended control attribute and the preset jump logic, including ending the affected execution instance and creating a new execution instance on the target activity. When a user or administrator submits a dynamic operation command on the front-end page, the system sends the relevant command and parameters (such as the target activity ID, rejection policy, and reassigned handler) to the redirection module. The redirection module reads the execution tree structure of the current process instance in the process engine, and, combined with the process definition and extended control attributes, analyzes the relationship between the current execution unit and the target activity to determine the range of execution instances that need to be terminated. After terminating these execution instances and triggering the corresponding activity end listeners, the redirection module instructs the process engine to create new execution instances on the target activity, thereby achieving non-linear redirection or rollback of the process. This approach ensures both the flexibility of dynamic control and the consistency of core process data.

[0028] In S600, the workflow of the jump module includes: Receive a redirection request and identify the target activity; analyze the execution status of the current process instance; calculate the affected execution scope based on the current execution unit and the target activity; instruct the process engine to terminate the affected execution instance and clean up related resources; trigger the BPMN activity termination listener for the activity that is forcibly terminated; The process engine is instructed to create a new execution instance on the target activity, so that the process instance continues execution from the target activity.

[0029] The jump module obtains the current set of activity instances by querying the runtime tables of the process engine (such as the execution table, task table, etc.), and determines the execution branches that need to be closed by combining the location and path of the target activity. It then issues termination instructions to these branches and cleans up related variables or tasks, and creates new execution instances at the target activity node to ensure the continuity and consistency of the process state.

[0030] S700. Collect and summarize the execution logs, node processing records, and operation records of the jump module of the process instance to generate multi-dimensional statistical reports that include at least efficiency analysis, quality analysis, and resource allocation analysis, which are used to guide subsequent process optimization.

[0031] During process execution, the system continuously collects execution logs of process instances (such as instance creation time, end time, current status, etc.), node processing records (such as task creation time, completion time, handler, processing comments, whether timeout occurred, etc.), and various dynamic operation records executed by the jump module (such as withdrawal, rejection, forced jump, etc.). The above data is cleaned and summarized to generate multi-dimensional statistical reports to reflect process efficiency, node quality, and resource allocation, thus providing managers with a basis for process optimization and personnel management.

[0032] In S700, the multi-dimensional statistical report includes at least one of the following: Efficiency analysis reports are used to display the average processing time, timeout rate, and number of items in transit for each process and node; quality analysis reports are used to count the number of rejections, withdrawals, and non-linear jumps at each node and the distribution of their causes; resource allocation analysis reports are used to count the number of tasks, completion efficiency, and timeout status for each processor.

[0033] In practice, the analysis module periodically extracts data from the process history database and operation logs, performs aggregation calculations using predefined statistical models, and displays the results in the form of charts or data tables on the front-end report page. It supports filtering and comparison by time period, process type, department, and other conditions, thereby helping managers identify problems such as process bottlenecks, abnormal nodes, and uneven resource load.

[0034] Example 2: This embodiment provides a visual page-driven structured process modeling, execution, and dynamic management system, characterized by including: The modeling module is used to create process models in the visual modeling page by dragging and dropping elements based on the BPMN 2.0 element library, and to generate process model data represented in JSON structure. The conversion module is used to input the process model data into a JSON converter for parsing and conversion, to obtain a BPMN 2.0 XML document carrying the extended control attributes; The deployment module is used to deploy the BPMN 2.0 XML document to the process engine, which loads it and uses it as the basis for the execution of subsequent process instances. The simulation module is used to simulate and predict the execution of the process based on the BPMN 2.0 XML document and simulation parameters during the design phase and before the process is initiated. By simulating and predicting the execution of the process through the stateless simulation engine, one or more predicted execution paths and the predicted handlers of each user task node are obtained, and the predicted execution paths are visualized on the visualization modeling page. The visualization execution module is used to display the flowchart, node status and historical flow path on the front-end page based on the execution status output by the process engine during the process instance operation. It also provides an operation entry point for business users and administrators to initiate dynamic operation commands such as withdrawal, rejection, forced jump and task reassignment. The jump module is used to receive the dynamic operation instructions and, in collaboration with the process engine, adjust the execution state of the process instance according to the extended control attributes and preset jump logic, including terminating the affected execution instance and creating a new execution instance on the target activity. The analysis module is used to collect and summarize the execution logs of the process instance, node processing records, and operation records of the jump module, and generate efficiency analysis reports, quality analysis reports, and resource allocation analysis reports.

[0035] The specific functions of each module are described in Example 1, which is a visual page-driven method for structured process modeling, execution and dynamic control. The details will not be repeated here.

[0036] Example 3: This embodiment provides a computer device, including a processor and a memory, wherein the memory stores a computer program that can run on the processor. The feature is that when the processor executes the computer program, it implements the visual page-driven structured process modeling, execution and dynamic control method.

[0037] A computer device includes at least one processor, memory, at least one network interface, and other user interfaces. The various components of the computer device are coupled together via a bus system. The bus system is used to enable communication between these components. In addition to a data bus, the bus system also includes a power bus, a control bus, and a status signal bus.

[0038] The user interface may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen). It is understood that the memory in this embodiment may be volatile memory or non-volatile memory, or may include both.

[0039] In this embodiment of the invention, the processor executes the method steps provided in each method embodiment by calling a program or instruction stored in the memory, specifically a program or instruction stored in an application program.

[0040] In some implementations, the memory stores elements such as executable units or data structures, or subsets thereof, or extended sets thereof: operating systems and applications.

[0041] The operating system includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application programs include various applications, such as media players and browsers, used to implement various application functions. The program implementing the method of this invention can be included in the application programs.

[0042] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A visual page-driven structured process modeling, execution and dynamic control method, characterized in that, The method comprises the following steps: S100, in a visual modeling page, a process model is established by a drag-and-drop manner based on a BPMN 2.0 element library, and process model data in a JSON structure is generated; S200, the process model data is input into a JSON converter, the process model data is parsed and converted, and a BPMN 2.0 XML document carrying the extended management and control attributes is obtained; S300, the converted BPMN 2.0 XML document carrying the extended management and control attributes is deployed to a process engine, and the process engine is loaded and used as an execution basis for subsequent process instances; S400, before a design stage and process initiation, based on the BPMN 2.0 XML document and input simulation parameters, a stateless simulation engine is used to simulate and predict process execution, one or more predicted execution paths and predicted handlers of each user task node are obtained, and the predicted execution paths are visually displayed in the visual modeling page; S500, during process instance running, based on an execution state output by the process engine, a visual module is used to display a process chart, node states and historical flow paths in a front-end page, and operation entrances are provided, so that business users and administrators can initiate dynamic operation instructions of withdrawal, rejection, forced jump and task reassignment on the front-end page; S600, the dynamic operation instructions are sent to a jump module cooperating with the process engine, the jump module adjusts an execution state of a process instance according to the extended management and control attributes and preset jump logic, including ending an affected execution instance and creating a new execution instance on a target activity; S700, execution logs of the process instance, node processing records and operation records of the jump module are collected and summarized, and multi-dimensional statistical reports including at least efficiency analysis, quality analysis and resource allocation analysis are generated, which are used to guide subsequent process optimization.

2. The method of claim 1, wherein, The process model data at least comprises: an activity list used to describe the identification, type, layout position and node attribute of each activity node; a connection line list used to describe the source node, target node, layout control point and connection attribute of each connection line; extended management and control attributes used to configure rejection permissions, withdrawal permissions, form field permissions and connection condition configuration information on the activity node and / or the connection line.

3. The method of claim 2, wherein, The S200 comprises: S201, the JSON format process model data is received and parsed, and the activity list and the connection line list are extracted; S202, a BPMN XML document object is initialized; S203, the activity list is traversed, and for each activity: S203A, a corresponding BPMN XML element is created according to the activity type; S203B, processing the standard BPMN attributes of the activity and assigning values to the BPMN XML elements; S203C, processing the extended governance attributes associated with the activity and adding them to the BPMN XML elements through the BPMN extension mechanism; S203D, if the activity contains sub-activities, recursively performing the traversal processing of S203 with the list of sub-activities as input; S204, traversing the list of connection lines and for each connection line: S204A, creating the BPMN XML element corresponding to the connection line; S204B, setting the source node reference and the target node reference of the connection line element; S204C, if the connection line is a conditional flow, creating and filling the BPMN conditional expression element according to the conditional configuration on the connection line; S205, serializing the BPMN XML document object into an XML string and outputting the BPMN 2.0 XML document that conforms to the BPMN 2.0 specification and contains the extended governance attributes.

4. The method of claim 1, wherein, In the S400, when performing process execution simulation prediction, the stateless simulation engine: only maintains execution path and state information in memory and does not write data to the business database; supports single-step execution mode, which pauses after simulating the execution of an activity and continues to execute the next activity after receiving a continue instruction; supports setting breakpoints, which pauses when simulating execution to a preset breakpoint activity and allows the user to adjust simulation parameters before continuing execution.

5. The method of claim 4, wherein, The S400 further includes: Before the formal initiation of the process, receiving the real business form data filled in by the initiator, inputting the real business form data as simulation parameters into the stateless simulation engine, simulating the execution path and the predicted processors of each user task node under actual conditions based on the real business form data, calculating the predicted processing time of each node and the predicted processing time of the overall process in combination with historical process instance running data, and displaying the predicted execution path, predicted processors, and predicted processing time on the front-end page for the initiator.

6. The method of claim 4, wherein, In the S500, the process of displaying the process diagram, node status, and historical flow path through the visualization module includes: drawing the process diagram on the front-end page with the same layout as in the modeling stage; highlighting completed nodes and connection lines, identifying the status of the current active node, and identifying rejected nodes with special styles; when the user clicks on any node, the processor, processing time, processing opinion, and related attachment information of the node are displayed.

7. The method of claim 4, wherein, In the S600, the workflow of the jump module includes: receiving a jump request and determining the target activity; analyzing the execution state of the current process instance; calculating the affected execution range according to the current execution unit and the target activity; instructing the process engine to end the affected execution instance and clean up related resources; triggering the BPMN activity end listener for the activity that is forced to end; instructing the process engine to create a new execution instance on the target activity and continue the process instance from the target activity.

8. The method of claim 1, wherein, In the S700, the multi-dimensional statistical report at least includes one of the following: Efficiency analysis report for showing the average processing time, timeout rate and in-transit quantity of each process and each node; Quality analysis report for counting the number of rejections, withdrawals and non-linear jumps of each node and the cause distribution; resource allocation analysis report for counting the number of tasks, completion efficiency and timeout of each processor.

9. A visual page driven structured process modeling, execution and dynamic governance system, characterized in that, Comprise: A modeling module for establishing a process model by dragging based on the BPMN 2.0 element library in a visual modeling page, and generating process model data in JSON structure; A conversion module for inputting the process model data into a JSON converter for parsing and conversion to obtain a BPMN 2.0 XML document carrying the extended management and control attributes; A deployment module for deploying the BPMN 2.0 XML document to a process engine, which loads and serves as the basis for subsequent process instance execution; An analog module for simulating and predicting process execution based on the BPMN 2.0 XML document and simulation parameters before the design stage and process initiation, calling a stateless simulation engine to simulate and predict process execution, obtaining one or more predicted execution paths and predicted processors of each user task node, and visually displaying the predicted execution paths in the visual modeling page; A visual execution module for displaying a process diagram, node state and historical flow path in the front-end page based on the execution state output by the process engine during the process instance running process, and providing an operation entry for business users and administrators to initiate dynamic operation instructions for withdrawal, rejection, forced jump and task reassignment; A jump module for receiving the dynamic operation instructions and cooperating with the process engine to adjust the execution state of the process instance according to the extended management and control attributes and the preset jump logic, including ending the affected execution instance and creating a new execution instance on the target activity; An analysis module for collecting and summarizing the execution log, node processing record and operation record of the jump module of the process instance to generate efficiency analysis report, quality analysis report and resource allocation analysis report.

10. A computer device comprising a processor and a memory, said memory having stored thereon a computer program operable to run on said processor, characterized in that, The processor executes the computer program to realize the visual page driven structured process modeling, execution and dynamic control method of any one of claims 1-8.

Images