CN113918637A - BPMN2.0 specification-based process engine platform creation method and system - Google Patents

Abstract

The invention discloses a process engine platform establishing method and a system based on BPMN2.0 specification, wherein the method comprises the following steps: storing data stored by the system management service to a flow engine container according to BPMN2.0 specifications; the flow and form designer nodularizes and represents the target flow file according to the flow requirement; calling data from the flow engine container according to the nodularization information; generating a flow file compatible with a target flow engine by using the called data according to a configuration rule; testing and running a process file compatible with the target process engine; and the flow core module issues the flow file data packet after test operation to a target flow engine for operation, and stores the flow file as a target flow file after debugging operation is successful. The advantages are that: the method stores each nodularization information required by the target process file according to the BPMN2.0 specification, is convenient for quickly indexing the nodularization information, does not need the connection among tables, has simple calling link and transaction link, can realize quick retrieval, and also reduces the pressure of system operation.

Description

BPMN2.0 specification-based process engine platform creation method and system

Technical Field

The invention relates to the field of process creation, in particular to a BPMN2.0 specification-based process engine platform creation method and system.

Background

With the continuous development of computer technology, network technology and database technology, the number of users and the number of system processes increase, so that the call dependency relationship among the processes is more complicated, and the system architecture is also migrated from the single-architecture era to the multi-architecture era.

In the existing business system, there are two main schemes for the automatic creation of the system flow: 1) an open-source flow library such as Activiti or Flowable is embedded, so that a plurality of additional functions are realized; 2) an integration scheme (a productive process engine platform) of a market process line is adopted.

The two schemes can realize quick process creation and realize service appeal. However, in the case of the solution 1, the embedded development library required by the current implementation technology has many defects, such as: 1) the embedded development library has higher requirements on developers and needs to know the heavy point interface and the operation principle of the library; 2) the development library does not relate to a drawing front end, if integration is needed, a front end program and a corresponding rear end interface need to be stripped from other projects, and complexity is increased; 3) the embedded development library only has basic functions, all complex functions need to be realized automatically, and particularly the synchronous realization of a large number of front ends is involved; 4) the embedded development library strongly depends on a fixed database, and is not easy to integrate with the current internet project; 5) if the integration of the service fields is needed, the integration can be realized only by a linked list form, the list searching depth during the process operation is increased, and the performance of the high concurrency state is obviously reduced.

On the other hand, for scheme 2, the existing flowerlike integrated scheme products often have the following disadvantages: 1) the technology stack of marketized products is old, which generally requires 2 to 3 years of iteration, however, the current technology development is changing day by day; 2) because the product is a marketized product, a targeted service scene is bound to be designed on the product, the adaptability of a novel service scene is limited, and the compatibility is not high; 3) many optimizations are made on UI by marketized products, which leads to a great deviation from the bpmn2.0 specification, and some products even completely deviate from the bpmn2.0 specification and are independently designed; 4) the marketable products are hindered in expansion, and more design schemes are needed particularly when a plurality of systems are docked; 5) the database of the marketized product is almost a fixed traditional database mode, so that the marketized product is incompatible with the novel Nosql from the bottom layer; 6) the exports of the marketized products are not compatible with the bpmn2.0 file format, so that the data cannot be smoothly migrated, more consideration is needed for the release work, and errors are easy to occur by adopting the marketized products; 7) because a large number of customized tables are adopted to support the realization of related functions, the calling link and the transaction link are deep, and the performance is reduced in a concurrent scene. From the foregoing, there is a need for a fast and convenient process engine creation method.

Disclosure of Invention

The invention aims to provide a BPMN2.0 specification-based process engine platform creation method and a BPMN2.0 specification-based process engine platform creation system, data stored in a system management service is stored in a process engine container according to the BPMN2.0 specification, a process and form designer directly searches for nodularization information from the process engine container according to an index after nodularization of a target process file according to a process requirement, a target process engine compatible process file is generated according to the nodularization information and a configuration rule, the target process engine compatible process file is verified in a test environment, a process file data packet is issued to the target process engine to run after the verification is successful, and the successfully-run file is stored as the created target process file. The method stores various kinds of nodularization information required by the target process file according to BPMN2.0 standard, is convenient for quickly indexing the nodularization information during process creation, does not need connection among tables, is simple in calling link and transaction link, can realize quick retrieval, and reduces the pressure of system operation.

In order to achieve the purpose, the invention is realized by the following technical scheme:

a process engine platform creating method based on BPMN2.0 specification comprises the following steps:

storing data stored by the system management service to a flow engine container according to BPMN2.0 specifications;

the flow and form designer nodularizes and represents the target flow file according to the flow requirement;

calling data from the flow engine container according to the nodularization information;

generating a flow file compatible with a target flow engine by the called data according to the nodularization information and the configuration rule;

testing and running a process file compatible with the target process engine;

and the flow core module issues the flow file data packet after test operation to a target flow engine for operation, and stores the flow file as a target flow file after debugging operation is successful.

Optionally, the process engine container includes multiple types of data, and the multiple types of data are correspondingly stored in a local framework table that can be identified by a framework of the process and form designer.

Optionally, the data stored in the system management service is analyzed and calculated, the data is converted into a BPMN object according to a BPMN2.0 specification, the BPMN object is converted into file element structure data that can be identified by a framework of the process and form designer based on a user-defined configuration parameter, an original storage interface of the local framework table is called, and the file element structure data is persisted to the local framework table.

Optionally, the framework of the flow and form designer is a Flowable framework.

Optionally, when the called data is generated into a process file compatible with the target process engine according to the nodularization information and the configuration rule, the process engine core module acquires the handler configuration data required by the process file from the process definition file to generate the process file compatible with the target process engine, analyzes the handler account of the process file, creates a task to be handled corresponding to the handler accordingly, and asynchronously pushes the state data of the current process to the service system through the message queue middleware.

Optionally, the configuration rule includes: the method comprises the following steps of initiator self-selection, designated link processing person, designated link processing group, designated link approval organization level, designated link continuous multi-level and designated link superior supervisor.

Optionally, the process file data packet after test operation includes: the target process engine compatible process files and the compatibility configuration data generated by the target process engine for different environments during test operation.

Optionally, the method further includes: the query module issues a query instruction, and the task center module receives the query instruction and calls query information from the flow engine container according to the index of the query instruction.

Optionally, a system adopting the BPMN2.0 specification-based process engine platform creation method includes:

the flow engine container is used for storing data stored by the system management service according to the BPMN2.0 specification;

the flow and form designer is used for nodularizing and representing the target flow file according to the flow requirement;

the flow core module is used for issuing the flow file data packet after the operation test to a target flow engine for operation, and storing the flow file data packet as a target flow file after the debugging operation is successful;

and the task center module is connected with each module and is used for receiving and forwarding task instructions of the system.

Optionally, the method further includes:

the flow engine core module is used for acquiring the configuration data of a handler required by the flow file from the flow definition file so as to generate a flow file compatible with the target flow engine;

and the task center module receives the query instruction and calls query information from the flow engine container according to the index of the query instruction.

Compared with the prior art, the invention has the following advantages:

the invention discloses a BPMN2.0 specification-based process engine platform creation method and a system, wherein data stored by a system management service is stored in a process engine container according to a BPMN2.0 specification, a process and form designer directly searches for nodularization information from the process engine container according to an index after nodularization representation of a target process file according to a process requirement, a process file compatible with a target process engine is generated according to the nodularization information and a configuration rule, the process file compatible with the target process engine is verified in a test environment, a process file data packet is issued to the target process engine for operation after successful verification, and the successfully operated file is stored as a created target process file. The method stores various kinds of nodularization information required by the target process file according to BPMN2.0 standard, is convenient for quickly indexing the nodularization information during process creation, does not need connection among tables, is simple in calling link and transaction link, can realize quick retrieval, and reduces the pressure of system operation.

Drawings

FIG. 1 is a schematic diagram of a process engine platform creation method based on BPMN2.0 specification;

FIG. 2 is a schematic diagram of the operation of the core module of the process engine of the present invention;

FIG. 3 is a schematic diagram of data synchronization between a test environment and a production environment according to the present invention;

FIG. 4 is a flow chart of the present invention;

FIG. 5 is another flow chart of the present invention;

FIG. 6 is a to-do task page according to the present invention;

FIG. 7 is a task hand-off page of the present invention;

FIG. 8 is a schematic diagram of security verification of the account service of the present invention;

FIG. 9 is a logic diagram of the system docking of the present invention.

Detailed Description

The present invention will now be further described by way of the following detailed description of a preferred embodiment thereof, taken in conjunction with the accompanying drawings.

As shown in fig. 1, a method for creating a process engine platform based on BPMN2.0 specification according to the present invention includes:

and S1, storing the data stored by the system management service to a flow engine container according to the BPMN2.0 specification.

In this embodiment, the process engine container contains multiple types of data, and the multiple types of data are correspondingly stored in a local framework table that can be identified by the framework of the process and form designer. The local frame table is a form configuration table, and different identification information, namely table indexes, is added to the data according to different types, so that quick indexing is performed when the information is needed.

The process core module extracts and analyzes data stored by the management service of the computing system, converts the data into a BpmnModel object according to BPMN2.0 specification, converts the BpmnModel object into file element structure data which can be identified by a framework of a process and form designer during operation based on self-defined configuration parameters, and finally calls an original storage interface of a local framework table to persist the converted file element structure data into the local framework table. Optionally, the file element structure data is in an XML format. In this embodiment, the framework of the flow and form designer is a Flowable framework, and therefore, the file element structure data that can be identified by the Flowable framework is stored in the local framework table.

In the application, based on a flow and form designer complying with BPMN2.0 specification, a flow core module avoids configuration data in a configuration file, namely a flow engine container, to the maximum extent, so that caching of high-frequency data access and migration release of one-click flow design are facilitated.

And S2, the flow and form designer nodularizes and expresses the target flow file according to the flow requirement.

And S3, calling data from the flow engine container according to the node information.

And S4, generating a flow file compatible with the target flow engine according to the called data and the configuration rule according to the nodularization information.

When the called data is generated into a target process engine compatible process file according to the nodularization information and the configuration rule, the process engine core module acquires the processor configuration data required by the process file from the process definition file to generate the target process engine compatible process file, analyzes the processor account of the process file, accordingly creates a task to be handled corresponding to the processor, and asynchronously pushes the state data of the current process to the service system through the message queue middleware.

That is, as shown in fig. 2, after the flow definition is issued to the flow engine core module, the task center module fills in initiation of the relevant service form execution flow, at this time, the flow engine core module starts an operation instance of the corresponding flow definition, acquires the required configuration data of the handler from the flow definition file, analyzes the account of the handler in the flow link, creates a task to be handled corresponding to the handler accordingly, and asynchronously pushes the status data of the current flow to the service system (including mail, short message, and wechat notification) through the message queue middleware. The system comprises an independent notification system, and the time-consuming and unnecessary functions of notification messages are separated from the operation of the flow core module and are asynchronously executed, so that the operation failure of the system caused by the delay of the relevance system is greatly improved.

During the creation of the task to be handled, the task instance data objects are assembled and asynchronously flushed into the NoSQL database (read library of the task to be handled).

In this embodiment, the configuration rule includes: a) the initiator selects by oneself: node configuration conforming to BPMN2.0 specification; b) and (3) designating a link handler: directly setting a user number of a processor in a process link; c) and (3) designating a link processing group: the group number configured in background management is set in the process link; d) and (3) specifying the organization level of link approval: finding out the leader of the organization of the corresponding hierarchy or the personnel of the designated role according to the configured hierarchy according to the organization where the designated personnel are located; e) successive multi-level hierarchies of links are specified: the method comprises the steps that examination and approval are carried out on an organization leader of a previous level step by step according to an organization level where a current handler is located, and the leader of the previous level is continuously searched after the current level is examined and approved until the current level is examined and approved to a configured organization level; f) the upper manager of the designated link: according to the person who is currently handling the director role of the organization in which the person is located. The configuration rule can simplify the data volume during operation, improve the efficiency of the system creation process, and is simple and clear in analysis rule and beneficial to later-stage expansion.

And S5, carrying out test operation on the flow files compatible with the target flow engine in the test environment.

And S6, the process core module issues the process file data packet after test operation to a target process engine, namely a production environment, and stores the file successfully debugged and operated as a target process file.

In this embodiment, the process file data packet after the test operation includes: the target process engine compatible process files and the compatibility configuration data generated by the target process engine for different environments during test operation.

As shown in fig. 3, based on the complete isolation of the test environment (e.g., the UAT environment) and the production environment (e.g., the PAT environment), when a new target process file, i.e., a business process, is created, a full amount of tests need to be performed in the test environment, at this time, a large amount of configuration data exists, and if the production environment is created again for the data, a very large amount of work is performed, and even a high risk of human misoperation exists. Therefore, in this embodiment, a file based on the JSON structure is redesigned based on the BPMN2.0 specification, and a large amount of configuration data is stored in the file, so that when a synchronization file is generated, more logical checksum compatibility data processing can be performed on data in different environments. Therefore, only a small part of data (such as user account numbers) needs to be manually adjusted during importing, and other processes and forms can adapt to the data of the new environment. By adopting the method, the release risk can be reduced, the production deployment efficiency is greatly improved, and the full test result of the test environment is also kept.

After the target flow file is successfully created, a corresponding operation flow chart can be generated. As shown in fig. 4 and 5, a flowchart for running two target flow files created. Further, as shown in fig. 6, the user can view his/her tasks to be handled in the task area to be handled, and based on the unified concept, a task handover area (see fig. 7) can be created for daily operation.

In practical application, some information is often required to be indexed, specifically, a query module of the system issues a query instruction, a task center module receives the query instruction, and queries the query information from a flow engine container according to the index of the query instruction. During daily operation, the pressure of data streams related to a task center module is usually large, file element structure data in a process engine container of the method are classified and stored in a local frame table, all the data are structure data capable of being dynamically assembled and adapted to a page during operation, and the method has a detailed table index design.

On the other hand, all interfaces related to query are directly set as task center modules, and stateless is guaranteed. When the system is in service flow bottleneck, the system can meet the access requirement of higher flow through Docker dynamic capacity expansion, and the system is prevented from being broken down due to overlarge flow access. The design based on the distributed micro-service architecture system ensures that the system has the advantages of supporting high concurrency, rapid scaling and the like. Meanwhile, the task center module is used as a unified system inlet, so that distributed inlets of multiple systems are simplified, and the use experience and the use efficiency of users are greatly improved.

Based on the same inventive concept, the invention also discloses a system adopting the BPMN2.0 specification-based process engine platform creation method, and the system comprises: the system comprises a process engine container, a process and form designer, a process core module and a task center module.

The flow engine container is used for storing data stored by the system management service according to BPMN2.0 standard; the flow and form designer is used for nodularizing and representing the target flow file according to the flow requirement; the flow core module is used for issuing a flow file data packet after running test to a target flow engine for running, and storing the flow file data packet as a target flow file after debugging and running are successful; the task center module is connected with each module and is used for receiving and forwarding task instructions of the system.

Furthermore, the system adopting the BPMN2.0 specification-based process engine platform creation method also comprises a process engine core module and an inquiry module. The process engine core module is used for acquiring the configuration data of a handler required by the process file from the process definition file so as to generate a process file compatible with the target process engine; the query module is used for issuing a query instruction, and the task center module receives the query instruction and calls query information from the flow engine container according to the index of the query instruction. Of course, the system is not limited to include the above modules, and other functional modules may be provided according to the requirements, which is not limited in this application.

According to the above modules, the multi-task creation in the system can be realized, for example, as shown in table 1 below, a service deployment unit may be included, where each service deployment unit serves user management, role management, menu management, resource management, timed task management, batch management, data dictionary management, system parameter management, and process management (process approval group management, process form management, process diagram design management, and advanced parameter management of process execution logic). Of course, the service deployment unit in the system is not limited to the above, and may directly create the corresponding nodes of the target flow file, that is, the nodes of the flow form and the business flow graph, by means of the above modules after the demand analysis, and issue and execute the nodes according to the target flow file.

TABLE 1 service deployment units and their classes

After the nodes of the target flow file are issued and executed, initiating the target flow file, wherein the initiating of the target flow file needs to create a form page corresponding to a flow template, at the moment, form configuration data is extracted from a local frame table, namely a form configuration table, the rendering of the form is completed by a flow and a form designer at the front end, and the flow file compatible with a target flow engine is generated. And testing and running the flow files compatible with the target flow engine in a testing environment, issuing the flow file data packets after the testing and running into the target flow engine by the flow core module for running, and storing the flow files as the target flow files after the debugging and running are successful. When the target process engine runs, the user information is supplemented, modified and perfected, and the task center module calls the process core module to execute the creation of the target process file after recording related data.

And after the target flow file is successfully created, the flow is executed, the user fills in personal login information, at the moment, information such as request information or query instructions is received and forwarded by the task center module, and then the flow is executed.

As shown in fig. 8, to implement the security of the system, the account service of the system may adopt a security verification manner. The method specifically comprises the following steps: 1) the account service uses a private key in a stored JWK key pair to realize the creation of a JWT token, wherein the JWT token comprises an encryption mode, basic information of a user and signed information; the account service parses JWK of the public key from the stored JWK key and opens up for other services (specifically gateway access) via HTTP.

2) The gateway adopts a filter to analyze the attribute of Authorization in all the request execution headers, and signature verification is carried out on the analyzed JWT token by using a Nimbus library; and analyzing the role owned by the current user from the token, acquiring the corresponding authority from Redis through the role, and checking whether the current request is in compliance.

After the task center module successfully initiates the process, the process core module can generate the task to be handled according to a plurality of calculations, and at the moment, when the page of the task center module is checked to be handled, the task center module is requested to inquire data of the task table to be handled.

And when the page of the task center module enters the task management page to be handled or the task detail page to be handled, the conventional operations of task passing, refuting, handling, transferring, signing, upgrading and the like can be executed, and the user with the corresponding authority can also execute operations of withdrawing, terminating and the like. Further, a user with a higher authority of the task center module can also perform detailed process runtime management.

In this embodiment, the task to be handled may be designed in a cold-hot table mode, that is, the task is moved to the already-handled table once the task to be handled is completed, rather than being identified by using the commercially available status field, so as to improve the large-table performance problem of high-frequency access data.

As shown in fig. 9, in terms of system docking, other business systems dock the process engine platform, i.e., the task center module, through the channel service, and all interfaces (start, task complete, task reject, etc.) enter through the synchronous interface, and synchronously respond to the data of the process state. When the state data of the process engine platform, namely the task center module, is changed, the events are put into a message queue (RabbitMQ) through the process core module, the message queue is monitored in the push service, the process state data notification is asynchronously executed, and if the service system has errors, the corresponding interface is called again through the retry mechanism of batch processing or the message queue to realize the synchronous robustness.

In summary, in the BPMN2.0 specification-based process engine platform creation method and system of the present invention, the method stores data stored in a system management service into a process engine container according to the BPMN2.0 specification, after a process and form designer nodularizes a target process file according to a process requirement, the process and form designer directly searches for nodularization information from the process engine container according to an index, generates a process file compatible with the target process engine according to the nodularization information and a configuration rule, verifies the process file compatible with the target process engine in a test environment, issues a process file data packet to the target process engine for running after successful verification, and stores the file successfully running as the created target process file. The method stores various kinds of nodularization information required by the target process file according to BPMN2.0 standard, is convenient for quickly indexing the nodularization information during process creation, does not need connection among tables, is simple in calling link and transaction link, can realize quick retrieval, and reduces the pressure of system operation.

Furthermore, the method preprocesses the data stored by the system management service, the identification information is assembled before the data is called, excessive table connection is not needed during actual query operation, the development efficiency and the operation efficiency are improved, and the method has natural advantages in large-user-quantity and multi-transaction type operation; the method is based on a distributed micro-service architecture system and has the advantages of high concurrency, rapid scaling and the like.

Furthermore, the method has an independent message notification system, and the message notification function which is time-consuming and has unnecessary functions is separated from the flow core module and is asynchronously executed, so that the operation fault of the system caused by the delay of the correlation system is greatly avoided.

While the present invention has been described in detail with reference to the preferred embodiments, it should be understood that the above description should not be taken as limiting the invention. Various modifications and alterations to this invention will become apparent to those skilled in the art upon reading the foregoing description. Accordingly, the scope of the invention should be determined from the following claims.

Claims (10)

1. A process engine platform creation method based on BPMN2.0 specification, comprising:

storing data stored by the system management service to a flow engine container according to BPMN2.0 specifications;

the flow and form designer nodularizes and represents the target flow file according to the flow requirement;

calling data from the flow engine container according to the nodularization information;

generating a flow file compatible with a target flow engine by the called data according to the nodularization information and the configuration rule;

testing and running a process file compatible with the target process engine;

and the flow core module issues the flow file data packet after test operation to a target flow engine for operation, and stores the flow file as a target flow file after debugging operation is successful.

2. The BPMN2.0 specification-based process engine platform creation method of claim 1,

the flow engine container contains various types of data, and the various types of data are correspondingly stored in a local framework table which can be identified by a framework of the flow and form designer.

3. The BPMN2.0 specification-based process engine platform creation method of claim 2,

analyzing and calculating data stored by the system management service, converting the data into a BpmnModel object according to BPMN2.0 specification, converting the BpmnModel object into file element structure data which can be identified by a framework of a process and form designer based on a self-defined configuration parameter, calling an original storage interface of a local framework table, and persisting the file element structure data into the local framework table.

4. The BPMN2.0 specification-based process engine platform creation method of claim 2,

the framework of the flow and form designer is a Flowable framework.

5. The BPMN2.0 specification-based process engine platform creation method of claim 1,

when the called data is generated into a target process engine compatible process file according to the nodularization information and the configuration rule, the process engine core module acquires the processor configuration data required by the process file from the process definition file to generate the target process engine compatible process file, analyzes the processor account of the process file, accordingly creates a task to be handled corresponding to the processor, and asynchronously pushes the state data of the current process to the service system through the message queue middleware.

6. The BPMN2.0 specification-based process engine platform creation method of claim 5,

the configuration rule includes: the method comprises the following steps of initiator self-selection, designated link processing person, designated link processing group, designated link approval organization level, designated link continuous multi-level and designated link superior supervisor.

7. The BPMN2.0 specification-based process engine platform creation method of claim 1,

the process file data packet after test operation comprises: the target process engine compatible process files and the compatibility configuration data generated by the target process engine for different environments during test operation.

8. The BPMN2.0 specification-based process engine platform creation method of claim 1, further comprising:

the query module issues a query instruction, and the task center module receives the query instruction and calls query information from the flow engine container according to the index of the query instruction.

9. A system using the BPMN2.0 specification-based process engine platform creation method according to any one of claims 1 to 8, comprising:

the flow engine container is used for storing data stored by the system management service according to the BPMN2.0 specification;

the flow and form designer is used for nodularizing and representing the target flow file according to the flow requirement;

the flow core module is used for issuing the flow file data packet after the operation test to a target flow engine for operation, and storing the flow file data packet as a target flow file after the debugging operation is successful;

and the task center module is connected with each module and is used for receiving and forwarding task instructions of the system.

10. The system of claim 9 employing a BPMN2.0 specification based process engine platform creation method, further comprising:

the flow engine core module is used for acquiring the configuration data of a handler required by the flow file from the flow definition file so as to generate a flow file compatible with the target flow engine;

and the task center module receives the query instruction and calls query information from the flow engine container according to the index of the query instruction.

Images