Cross-system process approval method based on BPMN2.0 standard

Abstract

The invention discloses a cross-system process approval method based on a BPMN2.0 standard, and the method comprises the following steps: building a business process model based on a BPMN2.0 modeling tool; configuring approval key elements of each process node; storing different process definition files; performing BPMN2.0 standard formatting on the process definition file; analyzing and executing the process definition file formatted by the BPMN2.0 standard through a process engine; performing cross-system integration; the system integration layer exchanges formats through standardized data; each system provides a corresponding API interface, and the system integration layer calls each API interface according to an instruction of the process engine. Cross-system seamless collaboration and automatic approval are realized by setting a process engine and cross-system integration; and through a unified process management system, global process optimization and adjustment are realized. And the system integration layer adopts a standardized data exchange format, so that cross-system integration is more efficient.

Description

Technical Field

[0001] The present invention relates to a process approval method, and in particular to a cross-system process approval method based on the BPMN2.0 standard. Background Art

[0002] At present, government information management departments at all levels rely on multiple different systems in business process approval, which leads to complexity and inefficiency in the approval process. Although some existing BPM tools provide process automation functions, they are usually limited to a single system, lack cross-system collaboration capabilities, and have low approval efficiency. In addition, existing systems often face performance bottlenecks and lack unified management when processing high-incidence concurrent requests and online collaboration. Summary of the invention

[0003] In order to solve the deficiencies of the above technologies, the present invention provides a cross-system process approval method based on the BPMN2.0 standard.

[0004] In order to solve the above technical problems, the technical solution adopted by the present invention is: a cross-system process approval method based on the BPMN2.0 standard, comprising the following steps:

[0005] Step S1: Build a business process model based on the actual approval business and the BPMN2.0 modeling tool;

[0006] Step S2: configure the key approval elements of each process node, including application ID and approval user;

[0007] Step S3: Adjust the process design according to the business changes and save different process definition files; format the process definition files according to the BPMN2.0 standard;

[0008] Step S4: The process engine parses and executes the process definition file formatted in the BPMN2.0 standard to handle cross-system data exchange and user interaction;

[0009] Step S5: Perform cross-system integration to achieve data exchange and collaborative processing between different systems;

[0010] Step S6: The system integration layer uses a standardized data exchange format to achieve data intercommunication between different systems;

[0011] Step S7: Each system provides a corresponding API interface, and the system integration layer calls each API interface according to the instructions of the process engine to obtain and transfer data.

[0012] Furthermore, in step S3, the process definition file is translated into a BPMN2.0 standard format file based on bpmn.js.

[0013] Furthermore, in step S4, Activiti in the process engine parses and executes the process definition file formatted according to the BPMN2.0 standard.

[0014] Furthermore, in step S5, cross-system integration is performed through a standardized interface, namely, a RESTful API.

[0015] Furthermore, cross-system integration is performed through RESTful API, including the following steps:

[0016] Step S51-1: When the business process flows to the corresponding approval node, the process engine writes a record to the message queue MQ;

[0017] Step S51-2: The corresponding business system subscribes to the message queue MQ to obtain current system data;

[0018] Step S51 - 3: The corresponding business system calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) in the process engine to process the task;

[0019] Step S51 - 4 : After the process is successful, the data status in the message queue MQ is updated.

[0020] Furthermore, the system data in step S51 - 2 includes pending tasks and approval user information.

[0021] Furthermore, in step S5, cross-system integration is performed through a message queue.

[0022] Furthermore, cross-system integration is performed through message queues, including the following steps:

[0023] Step S52-1: When the business system flows to the corresponding approval node, the process engine writes a record into the database approval table;

[0024] Step S52-2: The corresponding business system passes the application ID of the approval system through the RESTful API (Get / v2 / tasks / todos);

[0025] Step S52-3: query the database content to obtain current system data;

[0026] Step S52-4: The business system calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) in the process engine to process the task;

[0027] Step S52-5: Update the data status in the database after the processing is successful.

[0028] Furthermore, the system data in step S52-3 includes pending tasks and approval user information.

[0029] Furthermore, the standard data exchange format in step S6 includes JSON.

[0030] The present invention discloses a cross-system process approval method based on the BPMN2.0 standard. By setting a process engine and cross-system integration, seamless cross-system collaboration and automated approval are achieved, which significantly improves approval efficiency and data consistency. Through a unified process management system, each business process is centrally managed and monitored to achieve global process optimization and adjustment. The system integration layer adopts a standardized data exchange format to make cross-system integration more efficient and promote data exchange and collaborative processing between different systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 This is the structure diagram of the BPMN2.0 modeling tool in the present invention.

[0032] Figure 2 Generate a BPMN2.0 standard format file process structure diagram in the present invention.

[0033] Figure 3 This is an architectural diagram of the process engine in the present invention.

[0034] Figure 4 This is a cross-system integration architecture diagram of Example 1 in the present invention.

[0035] Figure 5 This is a cross-system integration architecture diagram of Example 2 in the present invention. DETAILED DESCRIPTION

[0036] The present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

[0037] A cross-system process approval method based on the BPMN2.0 standard includes the following steps:

[0038] Step S1: Build a business process model based on the actual approval business and the BPMN2.0 modeling tool;

[0039] Step S2: configure the key approval elements of each process node, including application ID and approval user;

[0040] Step S3: Adjust the process design according to the business changes and save different process definition files; format the process definition files according to the BPMN2.0 standard;

[0041] Step S4: The process engine parses and executes the process definition file formatted in the BPMN2.0 standard to handle cross-system data exchange and user interaction;

[0042] Step S5: Perform cross-system integration to achieve data exchange and collaborative processing between different systems;

[0043] Step S6: The system integration layer uses a standardized data exchange format to achieve data intercommunication between different systems;

[0044] Step S7: Each system provides a corresponding API interface, and the system integration layer calls each API interface according to the instructions of the process engine to obtain and transfer data.

[0045] Specifically, in step S3, the process definition file is translated into a BPMN2.0 standard format file based on bpmn.js.

[0046] In step S4, Activiti in the process engine parses and executes the process definition file formatted according to the BPMN2.0 standard.

[0047] In step S5, cross-system integration is performed through a standardized interface, namely, a RESTful API.

[0048] Cross-system integration through RESTful API includes the following steps:

[0049] Step S51-1: When the business process flows to the corresponding approval node, the process engine writes a record to the message queue MQ;

[0050] Step S51-2: The corresponding business system subscribes to the message queue MQ to obtain current system data;

[0051] Step S51 - 3: The corresponding business system calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) in the process engine to process the task;

[0052] Step S51 - 4 : After the process is successful, the data status in the message queue MQ is updated.

[0053] In step S51 - 2 , the system data includes pending tasks and approval user information.

[0054] In step S5, cross-system integration is performed through a message queue.

[0055] Cross-system integration through message queues includes the following steps:

[0056] Step S52-1: When the business system flows to the corresponding approval node, the process engine writes a record into the database approval table;

[0057] Step S52-2: The corresponding business system passes the application ID of the approval system through the RESTful API (Get / v2 / tasks / todos);

[0058] Step S52-3: query the database content to obtain current system data;

[0059] Step S52-4: The business system calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) in the process engine to process the task;

[0060] Step S52-5: Update the data status in the database after the processing is successful.

[0061] In step S52-3, the system data includes pending tasks and approval user information. In step S6, the standard data exchange format includes JSON.

[0062] Implementation 1 provides a cross-system process approval method based on the BPMN2.0 standard and implements a cross-system process approval method using the message queue MQ mode; Figure 1 As shown in the BPMN2.0 modeling tool structure diagram in a cross-system process approval method based on the BPMN2.0 standard, the business process manager builds a business model in the BPMN2.0 modeling tool according to the actual approval business; configures the key approval elements of each node, which include the approval application appid and the approval user user, and adjusts the process design according to the changes in the business, and saves them as different process definition files; including approval node A, approval node B and approval node C; wherein the initialization approval node A has appid=app1, user=user1; the approval node B has appid=app2, user=user2; the approval node C has appid=app3, user=user1.

[0063] like Figure 2As shown in the process structure diagram of generating BPMN2.0 standard format files in a cross-system process approval method based on BPMN2.0 standard, different process definition files are translated into BPMN2.0 standard format files through bpmn.js to ensure data consistency and efficient access. bpmn.js is a BPMN2.0 rendering toolkit and web modeler written in JavaScript. It embeds BPMN2.0 diagrams in the browser and is independent of the backend. It understands BPMN, builds diagrams to verify user operations, maps modeling operations to BPMN2.0, and provides BPMN-specific operations. bpmn.js is built on the diagram-js and bpmn-moddle libraries. Diagram-js is used to draw shapes and connections, provides methods for interacting with these graphic elements, and helps users build powerful BPMN viewers and other auxiliary tools. It provides context, palette, and redo / undo functions for modeling, and provides an extensible infrastructure module mode, plug-in system, event bus, command stack, and service lookup processing. bpmn-moddle allows reading and writing XML documents that conform to the BPMN2.0 model and access to BPMN-related information behind the shapes and connections drawn on the diagram.

[0064] like Figure 3 As shown in the architecture diagram of the process engine in a cross-system process approval method based on the BPMN2.0 standard, the process engine includes task scheduling, exception handling, event handling, activiti, logging and API interface; the process engine uses activiti to parse and execute the process definition file of the BPMN2.0 standard, and coordinates the interaction between various systems and users through the application appid and approval user user set by the process approval node, providing efficient task scheduling, exception handling, real-time monitoring and detailed logging functions to ensure the smooth execution of business processes and rapid troubleshooting of problems, thereby realizing cross-system automated approval and data exchange.

[0065] like Figure 4As shown in the cross-system integration architecture diagram implemented in a cross-system process approval method based on the BPMN2.0 standard, when the business process flows to the approval node A, the process engine will write a record to the message queue MQ with the topic app1, triggering the write message event, and write messages 1, 2, 3 and 4 to app1; the message queue MQ is a communication method between processes or different threads of the same process. The queue is a message container. The message queue itself does not store the message content. It is a middleware that allows asynchronous communication between applications, which helps to decouple the communication of different components and improve the scalability and maintainability of the system. Business system A subscribes to the queue of app1 in MQ through the subscription mode Topic and passes in the application ID, that is, application 1 (app1), and consumes Topic messages according to appid to obtain the current pending tasks and approval user information; business system A calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) provided by the process engine to handle the task, and updates the message queue MQ after the handling is successful. The message queue supports asynchronous communication, ensures the reliable transmission and processing of messages, and improves the scalability and fault tolerance of the system.

[0066] When the business process flows to the approval node B, the process engine will write a record to the topic app2 in the message queue MQ, triggering a message write event, and write messages 1, 2, 3, 4, and 5 to app2; business system B subscribes to the queue of app2 in MQ through the subscription mode Topic and passes in the application ID, that is, application 2 (app2), and consumes Topic messages according to appid to obtain the current pending tasks and approval user information; business system B calls the RESTful API provided by the process engine (PUT / v1 / tasks / {taskId} / complete) to handle the task, and updates the message queue MQ after successful handling.

[0067] When the business process flows to the approval node C, the process engine will write a record to the topic app3 in the message queue MQ, triggering a write message event, and write messages 1, 2, and 3 to app3; the message queue MQ is a communication method between processes or different threads of the same process. The queue is a message container. The message queue itself does not store the message content. It is a middleware that allows asynchronous communication between applications, which helps to decouple the communication of different components and improve the scalability and maintainability of the system. Business system C subscribes to the queue of app3 in MQ through the subscription mode Topic and passes in the application ID, that is, application 3 (app3), and consumes Topic messages based on appid to obtain the current pending tasks and approval user information; business system C calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) provided by the process engine to handle the task, and updates the message queue MQ after the handling is successful.

[0068] The system integration layer uses a standardized data exchange format, such as JSON, to achieve data intercommunication between different systems; each system provides a corresponding API interface, as shown in Table 1. The system integration layer calls the API interface according to the instructions of the process engine to achieve data acquisition and transmission. Table 1 is as follows:

[0069] Table 1

[0070]

[0071]

[0072] Embodiment 2 is a cross-system process approval method based on the BPMN2.0 standard, which implements a cross-system process approval method in a RESTful API mode;

[0073] A cross-system process approval method based on the BPMN2.0 standard specifically includes the following steps:

[0074] Step 1: Build a business model based on the actual approval business and the BPMN2.0 modeling tool;

[0075] Step 2: Configure the key approval factors of each node, including application ID and approval user;

[0076] Step 3: Adjust the process design according to business changes and save different process definition files; and translate the process definition files into BPMN2.0 standard format files based on bpmn.js;

[0077] Step 4: Activiti in the process engine parses and executes the process definition file that conforms to the BPMN2.0 standard, and coordinates the interaction between various systems and users through the application ID and approval user set in the process approval node; it can provide efficient task scheduling, exception handling, real-time monitoring and detailed logging functions to ensure the smooth execution of business processes and rapid troubleshooting of problems, thereby realizing cross-system automated approval and data exchange;

[0078] Step 5: Perform cross-system integration; Figure 5 A cross-system process approval method based on the BPMN2.0 standard is shown in the cross-system integration architecture diagram of Example 2; when the business process flows to the approval node A, the process engine writes a record to the database approval table ACT_RU_TASK, and the data record 1 is id=1, appid=app1, and user=user1; the business system A passes in the application ID app1 through the RESTful API (Get / v2 / tasks / todos), queries the database content, and obtains the current to-do tasks and approval user information; the business system A calls the RESTful API provided by the process engine (PUT / v1 / tasks / {taskId} / complete) to handle the task, and updates the data status in the database after the handling is successful;

[0079] When the business process flows to approval node B, the process engine writes a record to the database approval table ACT_RU_TASK, where data record 2 is id=2, appid=app2, and user=user2; business system B passes in the application ID app2 through the RESTful API (Get / v2 / tasks / todos), queries the database content, and obtains the current to-do tasks and approval user information; business system B calls the RESTful API provided by the process engine (PUT / v1 / tasks / {taskId} / complete) to process the task, and updates the data status in the database after successful processing;

[0080] When the business process flows to the approval node C, the process engine writes a record to the database approval table ACT_RU_TASK, where data record 3 is id=3, appid=app3, and user=user1; business system C passes in the application ID app2 through the RESTful API (Get / v2 / tasks / todos), queries the database content, and obtains the current pending tasks and approval user information; business system C calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) provided by the process engine to handle the task, and updates the data status in the database after successful handling; cross-system business process approval is realized;

[0081] The RESTful API allows synchronous requests and responses, so that the business system can directly call the approval service for data transmission and operations.

[0082] Step 6: The system integration layer uses a standard data exchange format to communicate data between different systems; each system provides a corresponding API interface, and the system integration layer calls each API interface according to the instructions of the process engine to complete data acquisition and transmission.

[0083] The two methods of implementing cross-system process approval in Example 1 and Example 2 enable the system to flexibly adapt to different business needs, ensure efficient and reliable data exchange between business systems, and further enhance the automation and collaborative working capabilities of the approval process.

[0084] Through the BPMN2.0 modeling tool, process engine, cross-system integration and standard data exchange format, cross-system process approval is realized, approval efficiency is improved, human intervention and errors are reduced, and a good user experience is provided. The BPMN2.0 modeling tool is the process of using the BPMN2.0 standard to define and design business processes in detail. Through graphical tools, clear and intuitive flowcharts are created, covering elements such as activities, events, gateways and connectors, ensuring that each process step and approval node is clear; in the BPMN2.0 modeling tool, the approval system is distinguished by the application identification attribute of the process node, and the cross-system approval identification is defined in the process modeling process. Each system obtains the corresponding approval information according to the system identification. The process engine is the core component of the business process management system, responsible for parsing, executing and managing the business process definition of the BPMN2.0 standard. It coordinates and automates the tasks of each process node, handles cross-system data exchange and user interaction, and provides exception handling to ensure efficient and reliable operation of the process. Cross-system integration realizes data exchange and collaborative processing between different systems through standardized interfaces and message queues. The business system establishes a communication protocol through RESTful API or message queue technology according to the system identification to ensure efficient and reliable information transmission and system flexibility. The standard data exchange format is a standardized data exchange format used by the system integration layer to achieve data interoperability between different systems. Each system provides a corresponding API interface, and the system integration layer calls these interfaces according to the instructions of the process engine to complete data acquisition and transmission.

[0085] By establishing a unified process management system and using the BPMN2.0 standard to model and define business processes, business process approval across different systems can be achieved. By utilizing distributed architecture and microservice technology, the high availability and scalability of the system can be ensured. It supports the use of the BPMN2.0 standard to model and define business processes, and integrates multiple notification methods to improve approval efficiency and business transparency.

[0086] The above implementation modes are not limitations of the present invention, and the present invention is not limited to the above examples. Changes, modifications, additions or substitutions made by technicians in this technical field within the scope of the technical solution of the present invention also belong to the protection scope of the present invention.

Claims

1. A cross-system process approval method based on BPMN2.0 standard, characterized in that: The following steps are involved: Step S1: Build a business process model based on the actual approval business and the BPMN2.0 modeling tool; Step S2: configure the key approval elements of each process node, including application ID and approval user; Step S3: Adjust the process design according to the business changes and save different process definition files; format the process definition files according to the BPMN2.0 standard; Step S4: The process engine parses and executes the process definition file formatted in the BPMN2.0 standard to handle cross-system data exchange and user interaction; Step S5: Perform cross-system integration to achieve data exchange and collaborative processing between different systems; Step S6: The system integration layer uses a standardized data exchange format to achieve data intercommunication between different systems; Step S7: Each system provides a corresponding API interface, and the system integration layer calls each API interface according to the instructions of the process engine to obtain and transfer data.

2. The cross-system process approval method based on the BPMN2.0 standard according to claim 1 is characterized in that: In the step S3, the process definition file is translated into a BPMN2.0 standard format file based on bpmn.js.

3. The cross-system process approval method based on the BPMN2.0 standard according to claim 1 is characterized in that: In step S4, Activiti in the process engine parses and executes the process definition file formatted according to the BPMN2.0 standard.

4. The cross-system process approval method based on the BPMN2.0 standard according to claim 1 is characterized in that: In step S5, cross-system integration is performed through a standardized interface, namely, RESTful API.

5. The cross-system process approval method based on the BPMN2.0 standard according to claim 4 is characterized in that: The cross-system integration through RESTful API includes the following steps: Step S51-1: When the business process flows to the corresponding approval node, the process engine writes a record to the message queue MQ; Step S51-2: The corresponding business system subscribes to the message queue MQ to obtain current system data; Step S51-3: The corresponding business system calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) in the process engine to process the task; Step S51 - 4 : After the process is successful, the data status in the message queue MQ is updated.

6. The cross-system process approval method based on the BPMN2.0 standard according to claim 5 is characterized in that: The system data in step S51 - 2 includes pending tasks and approval user information.

7. The cross-system process approval method based on the BPMN2.0 standard according to claim 1 is characterized in that: In step S5, cross-system integration is performed through a message queue.

8. The cross-system process approval method based on the BPMN2.0 standard according to claim 7 is characterized in that: The cross-system integration through the message queue includes the following steps: Step S52-1: When the business system flows to the corresponding approval node, the process engine writes a record into the database approval table; Step S52-2: The corresponding business system passes the application ID of the approval system through the RESTful API (Get / v2 / tasks / todos); Step S52-3: query the database content to obtain current system data; Step S52-4: The business system calls the RESTful API (PUT / v1 / tasks / {taskId} / complete) in the process engine to process the task; Step S52-5: Update the data status in the database after the processing is successful.

9. The cross-system process approval method based on the BPMN2.0 standard according to claim 8 is characterized in that: The system data in step S52-3 includes pending tasks and approval user information.

10. The cross-system process approval method based on the BPMN2.0 standard according to claim 1, characterized in that: The standard data exchange format in step S6 includes JSON.

Images