CN115756405A - Process approval system based on container cloud and process engine - Google Patents
Process approval system based on container cloud and process engine Download PDFInfo
- Publication number
- CN115756405A CN115756405A CN202211442225.3A CN202211442225A CN115756405A CN 115756405 A CN115756405 A CN 115756405A CN 202211442225 A CN202211442225 A CN 202211442225A CN 115756405 A CN115756405 A CN 115756405A
- Authority
- CN
- China
- Prior art keywords
- container
- flow
- engine
- system based
- setting unit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a flow approval system based on a container cloud and a flow engine, belongs to the technical field of micro-service architecture, and solves the problem that a service flow in the prior art cannot be added or deleted at any time; the rules submitted for verification cannot be changed at any time; the processing personnel/roles of the process nodes are fixed and cannot be changed at any time; the process node processing personnel \ roles cannot synchronize external data; the development process approval center function consumes too long time; more maintenance personnel are needed, and the labor cost is high. The system comprises a rule setting unit, a node setting unit, a role setting unit and a process setting unit, wherein a process design subunit is realized based on a process engine and adopts a container cloud architecture mode. The invention can add/delete flow nodes, change check rules and change the roles of the processing personnel at any time, can acquire the data of the processing personnel through an external interface, effectively improves the development efficiency by more than 200 percent, only needs one person for normal state maintenance personnel and reduces the labor cost by 200 percent.
Description
Technical Field
The invention relates to a process approval microservice, in particular to a process approval system based on a container cloud and a process engine, and belongs to the technical field of microservice architectures.
Background
In order to meet the requirements of high efficiency and low cost of enterprise workflows in the Internet era, more and more enterprises change the working modes to informatization. Under such a large background, based on the requirements of business control and risk prevention, enterprises generally need a process control software to manage the enterprises, so that a system with a business process approval function is developed.
At present, an enterprise management and control system mostly adopts a fixed flow, and research and development personnel write codes for a certain service to realize the fixed flow. Each set of business process has different requirements, and needs to be researched and developed to carry out specific compiling to match with the examination and approval of related business, and the following problems exist:
1. the service flow realized by writing codes is fixed, and flow nodes cannot be added or deleted at any time;
2. the rules submitted for verification in the business process are fixed and cannot be changed at any time;
3. in the business process, the process node processing personnel/roles are fixed and cannot be changed at any time;
4. the flow node processing personnel \ roles are only limited to the existing organization data in the system and cannot synchronize external data;
5. the development process approval center function in the traditional research and development mode usually takes 15 days, and the development time is too long;
6. developing the function in the traditional research and development mode requires 5 normal state maintainers, including front end development, back end development, testing, UI and product manager, and the labor cost is high.
In addition, with the popularization of the application and development of the micro service architecture, many IT companies launch new products based on the micro service architecture, and in order to avoid the influence of different operating environments on code operation, the micro service needs to be deployed in an isolation environment. Initially, micro service providers tend to deploy micro services in virtual machines, which can also achieve isolation of the micro services, but cannot perform rapid expansion, are limited by implementation principles of the virtual machines, take some time to start the micro service providers, cannot immediately react to instantly sudden loads or flows, and from the cost consideration, each application or micro service must be operated in one virtual machine in order to achieve isolation using conventional virtual machine technology, and such repeated and wasted allocation of operating systems and resources can be avoided by container technology, thereby greatly reducing investment of the cloud service providers in hardware and saving the cost of the cloud service center.
One container contains the complete runtime environment: except the application program itself, all the dependencies, class libraries, other binary files, configuration files and the like required by the application are uniformly typed into a package called container mirror image, and the differences caused by the release version of the operating system and other basic environments are abstracted by containerizing the application program itself and the dependencies thereof, so that the mirror image is more flexibly transplanted from one environment to another environment. For example, the same image may run in a Windows or Linux, development, test, or production environment. Meanwhile, the container is deployed in the cloud host through the container cloud architecture, a user can flexibly and conveniently use the micro-service only through the SaaS (software as a service) layer without considering the problems of data storage, software maintenance, safety and the like, and the operation and maintenance cost of an enterprise is greatly saved.
The applicant has found that the prior art has at least the following technical problems:
1. in the prior art, a service flow is fixed, and flow nodes cannot be added or deleted at any time;
2. in the prior art, the rule for submitting the verification in the business process is fixed, and the change cannot be carried out at any time;
3. in the prior art, in a business process, process node processing personnel/roles are fixed and cannot be changed at any time;
4. in the prior art, the flow node processing personnel \ roles are only limited to the existing organization data in the system and cannot synchronize external data;
5. in the prior art, the development process approval center function consumes too long time;
6. in the prior art, more maintenance personnel are needed for developing the functions of the process approval center, and the labor cost is high.
Disclosure of Invention
The invention aims to provide a process approval system based on a container cloud and a process engine, which aims to solve the problems that in the prior art, a service process is fixed and process nodes cannot be added or deleted at any time; the rules submitted for verification in the business process are fixed and cannot be changed at any time; in the business process, the process node processing personnel/roles are fixed and cannot be changed at any time; the flow node processing personnel \ roles are only limited to the existing organization data in the system and cannot synchronize external data; the development process approval center function consumes too long time; more maintenance personnel are needed, and the labor cost is high.
In order to achieve the purpose, the invention provides the following technical scheme:
the invention provides a process approval system based on a container cloud and a process engine, which is a process design system based on the process engine, and comprises the following steps:
the rule setting unit is used for changing the quantity and the attribute of the flow rule;
the node setting unit is used for changing the number of the flow nodes;
the role setting unit is used for setting the processing roles of a plurality of nodes in the process;
and the flow setting unit is used for setting a flow auditing function and setting a flow operation authority.
Further, the rule setting unit includes:
an add rule subunit, configured to add a branch rule;
a delete rule subunit for deleting the rule;
and the custom rule subunit is used for customizing the rule attribute by a user.
Further, the node setting unit includes:
a delete node subunit, configured to delete a node in the flow;
and the node adding subunit is used for adding one node in the process.
Further, the role setting unit includes:
and the user-defined node processing person subunit is used for setting processing persons/roles/departments when the service flows to the nodes, setting the operation authority of the processing persons/roles/departments and setting the opinion feedback function of the operation authority of the processing persons/roles/departments.
Further, the flow setting unit includes:
the approval-free subunit is used for setting whether the approval person automatically passes through the initiator or not;
the duplicate removal subunit is used for setting whether duplicate removal is carried out when the approvers of the two continuous nodes are the same;
and the process authority management subunit is used for setting whether the process supports the modification revocation operation.
Furthermore, the system uses a Java-based workflow process engine, the workflow process engine adopts a SpringBoot technical framework, mySql, oracle and PostGreSQL are used as bottom-layer databases to support the workflow process engine to acquire data through a Mybatis persistent layer, the whole workflow process engine interacts with a Vue front-end server through a server, and the workflow process engine reads the data of the MongoDB database through MongoTemplate.
Further, the workflow process engine performs data verification through a controller, and the controller comprises a timing controller, a message notification controller and a data verification controller.
Further, the process approval system based on the container cloud and the process engine is developed based on a container cloud technology, and comprises the following steps:
the IaaS layer is arranged at the bottom layer of the process approval system based on the container cloud and the process engine and is used for providing container resources;
the PaaS layer is arranged in the middle layer of the process approval system based on the container cloud and the process engine, and comprises a Docker container engine system used for managing the life cycle of the container; the k8s cluster management system is used for container management;
the SaaS layer is arranged on the upper layer of the process approval system based on the container cloud and the process engine and used for decoupling and splitting the process approval microservices and performing application distributed arrangement on the microservices based on the process approval business.
Further, the Docker container engine system comprises a container parameter configuration module, a container starting module and a container destroying module, wherein the container parameter configuration module is used for configuring parameters of the bottom container, the container starting module is used for starting the container, and the container destroying module is used for destroying the container when the container is not used any more; the k8s cluster management system comprises a resource scheduling module used for carrying out uniform resource scheduling on containers in the cluster; the operation monitoring module is used for monitoring the operation condition of each container in the cluster; and the deployment starting module is used for uniformly deploying the starting of each container in the cluster.
Further, the process approval system based on the container cloud and the process engine further comprises a security and confidentiality system, the user sends an access request to the nqinx, the nqinx receives a connection request on the internet, and then the request is forwarded to a routing module, an authentication module and a white list module on an internal network in a reverse proxy mode to determine the access right of the user.
Based on the technical scheme, the embodiment of the invention can at least produce the following technical effects:
(1) The flow approval system based on the container cloud and the flow engine can add or delete flow nodes at any time.
(2) The process approval system based on the container cloud and the process engine can change the verification rules at any time.
(3) The process approval system based on the container cloud and the process engine can change the processing personnel \ roles at any time.
(4) The process approval system based on the container cloud and the process engine can acquire data of processing personnel through an external interface.
(5) According to the process approval system based on the container cloud and the process engine, the process construction takes 5 working days, and the development efficiency is effectively improved by more than 200%.
(6) According to the process approval system based on the container cloud and the process engine, only one person is needed for normal state maintenance personnel, and the labor cost is reduced by 200%.
Drawings
FIG. 1 is a schematic flow sheet design of a preferred embodiment of the present invention;
FIG. 2 is a schematic diagram of a workflow process engine framework in accordance with a preferred embodiment of the present invention.
Detailed Description
The invention provides a process approval system based on a container cloud and a process engine, and a preferred embodiment of the invention is described in detail with reference to fig. 1 and 2.
In a preferred embodiment of the present invention, the workflow process engine is Flowable. The Flowable is a lightweight business process engine written by Java, an Apache V2 license protocol is used for opening a source, the key is a core engine of the engine, and the core engine is a set of services and provides an API for managing and executing business processes. The Flowable supports BPMN 2.0 industry standard, and meanwhile, a plurality of Flowable self-defined BPMN extensions (extensions) are provided for selection, so that the flow is established by importing XML files or a front-end visual interface.
In a preferred embodiment of the present invention, as shown in fig. 2, the system uses a Java-based workflow process engine, the workflow process engine adopts a SpringBoot technology framework, and uses MySql, oracle, and PostGreSQL as underlying databases to support the workflow process engine to acquire data through a Mybatis persistent layer, the workflow process engine interacts with a Vue front-end server through a server as a whole, and the workflow process engine reads the data of a mongoddb database through a MongoTemplate.
In a preferred embodiment of the present invention, the workflow process engine performs data verification through a controller, and the controller includes a timing controller, a message notification controller, and a data verification controller.
In the preferred embodiment of the invention, the microservice is based on a container cloud architecture. The container cloud architecture includes three layers:
the IaaS layer is arranged at the bottom layer of the process approval system based on the container cloud and the process engine and is used for providing container resources;
the PaaS layer is arranged in the middle layer of the process approval system based on the container cloud and the process engine, and comprises a Docker container engine system used for managing the life cycle of the container; the k8s cluster management system is used for container management;
and the SaaS layer is arranged on the upper layer of the process approval system based on the container cloud and the process engine and is used for decoupling and splitting the process approval microservices and performing application distributed arrangement on the microservices based on the process approval business.
Further specifically, in a preferred embodiment of the present invention, the Docker engine system includes a container parameter configuration module, a container starting module and a container destroying module, wherein the container parameter configuration module is configured to configure parameters of the bottom container, the container starting module is configured to start the container, and the container destroying module is configured to destroy the container when the container is no longer used; the k8s cluster management system comprises a resource scheduling module used for carrying out uniform resource scheduling on containers in the cluster; the operation monitoring module is used for monitoring the operation condition of each container in the cluster; and the deployment starting module is used for uniformly deploying the starting of each container in the cluster.
In the preferred embodiment of the invention, the Pod is deployed in the wing cloud host, one Pod is deployed in one Pod, the container is managed and operated by a Docker container engine system and a k8s cluster management system of the PaaS layer through a container encapsulation process engine component, and a user remotely uses a process design subunit of the process engine through the SaaS layer.
In order to ensure the security and confidentiality of the microservice, the preferred embodiment of the invention also comprises a security and confidentiality system, the user sends an access request to the nqinx, the nqinx (a high-performance HTTP and reverse proxy web server) accepts a connection request on the internet, and then the request is forwarded to a routing module, an authentication module and a white list module on the internal network in a reverse proxy mode to determine the access authority of the user.
In order to ensure the normal operation of the micro-service, the preferred embodiment of the invention further comprises a Prometheus monitoring alarm system, which is matched with AlertManager and a visual platform Grafana of universal time sequence data to complete dynamic monitoring, wherein the AlertManager is used as an independent component and is responsible for receiving and processing the alarm information from the Prometheus Server.
In a preferred embodiment of the present invention, based on the container cloud architecture and the Flowable flow engine, an approval flow design may be implemented, including:
the rule setting unit is used for changing the quantity and the attribute of the flow rule;
the node setting unit is used for changing the number of the flow nodes;
the role setting unit is used for setting the processing roles of a plurality of nodes in the process;
and the flow setting unit is used for setting a flow auditing function and setting a flow operation authority.
Preferably, the rule setting unit includes:
an add rule subunit, configured to add a branch rule;
a delete rule subunit configured to delete a rule;
and the custom rule subunit is used for customizing the rule attribute by a user.
Preferably, the node setting unit includes:
a delete node subunit, configured to delete a node in the flow;
and the node adding subunit is used for adding one node in the process.
Preferably, the role setting unit includes:
and the user-defined node processing person subunit is used for setting processing persons/roles/departments when the business flows to the node, setting the operation authority of the processing persons/roles/departments and setting the opinion feedback function of the operation authority of the processing persons/roles/departments.
Preferably, the process setting unit includes:
the approval-free sub-unit is used for setting whether the approval person automatically passes through when initiating the person;
the duplicate removal subunit is used for setting whether duplicate removal is carried out when the approvers of the two continuous nodes are the same;
and the flow authority management subunit is used for setting whether the flow supports the operation of modifying and canceling.
Referring now to FIG. 1, the steps of the process design of the preferred embodiment of the present invention will be described in further detail, including:
step one, a flow designer needs to sort the flow according to a service appeal;
step two, the process designer sets by the initiator, and sets the operation which can be performed on the business form by the initiator, wherein the operation comprises field visible authority, writing authority, filling authority and printing authority;
step three, the flow designer sets a plurality of branches through the rule setting unit according to the service appeal, sets the number of nodes which each branch needs to pass through after the initiator, and sets the flow rule of each node;
step four, the process designer sets the node processing personnel, including copying, handling and examining and approving personnel selection, wherein the personnel selection is not limited to individuals/roles/departments;
step five, setting a transaction process by a process designer, and setting which step the approval service can be stopped when the approval service is carried out;
step six, the process designer can select the following steps according to the service appeal:
whether the approver automatically passes when the approver is the initiator is set, whether duplicate removal is carried out when the approvers of two continuous nodes are the same, and whether modification cancellation operation is supported.
It is to be understood that the present invention has been described with respect to the preferred embodiments, and it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the spirit and scope of the invention. In addition, many modifications may be made to adapt a particular situation to the teachings of the present invention without departing from its spirit or scope. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.
Claims (9)
1. A process approval system based on a container cloud and a process engine is characterized by comprising:
the rule setting unit is used for changing the quantity and the attribute of the flow rule;
the node setting unit is used for changing the number of the flow nodes;
the role setting unit is used for setting processing roles of a plurality of nodes in the process;
and the flow setting unit is used for setting a flow auditing function and setting a flow operation authority.
2. The process approval system based on the container cloud and the process engine according to claim 1, wherein the rule setting unit comprises:
an add rule subunit, configured to add a branch rule;
a delete rule subunit for deleting the rule;
and the custom rule subunit is used for customizing the rule attribute by a user.
3. The process approval system based on the container cloud and the process engine according to claim 1,
the node setting unit includes:
a delete node subunit, configured to delete a node in the flow;
and the node adding subunit is used for adding one node in the process.
4. The process approval system based on the container cloud and the process engine according to claim 1,
the role setting unit includes:
and the user-defined node processing person subunit is used for setting processing persons/roles/departments when the service flows to the nodes, setting the operation authority of the processing persons/roles/departments and setting the opinion feedback function of the operation authority of the processing persons/roles/departments.
5. The process approval system based on the container cloud and the process engine according to claim 1,
the flow setting unit includes:
the approval-free subunit is used for setting whether the approval person automatically passes through the initiator or not;
the duplicate removal subunit is used for setting whether duplicate removal is carried out when the two continuous node approvers are the same;
and the flow authority management subunit is used for setting whether the flow supports the operation of modifying and canceling.
6. The process approval system based on the container cloud and the process engine according to claim 1, wherein the process approval system is developed based on a container cloud technology, and the container cloud comprises:
the IaaS layer is arranged at the bottom layer of the process approval system based on the container cloud and the process engine and is used for providing container resources;
the PaaS layer is arranged in the middle layer of the process approval system based on the container cloud and the process engine, and comprises a Docker container engine system used for managing the life cycle of the container; the k8s cluster management system is used for container management;
the SaaS layer is arranged on the upper layer of the process approval system based on the container cloud and the process engine and used for decoupling and splitting the process approval microservices and performing application distributed arrangement on the microservices based on the process approval business.
7. The process approval system based on the container cloud and the process engine according to claim 6, wherein the Docker container engine system comprises a container parameter configuration module, a container starting module and a container destroying module, wherein the container parameter configuration module is used for configuring parameters of a bottom container, the container starting module is used for starting the container, and the container destroying module is used for destroying the container when the container is not used any more; the k8s cluster management system comprises a resource scheduling module used for carrying out uniform resource scheduling on containers in the cluster; the operation monitoring module is used for monitoring the operation condition of each container in the cluster; and the deployment starting module is used for uniformly deploying the starting of each container in the cluster.
8. The process approval system based on the container cloud and the process engine as claimed in claim 1, wherein the system uses a Java-based workflow process engine, the workflow process engine adopts a SpringBoot technology framework, mySql, oracle, postGreSQL are used as underlying databases to support the workflow process engine to obtain data through a Mybatis persistent layer, the workflow process engine integrally interacts with a Vue front-end server through a server, and the workflow process engine reads the data of the MongoDB database through MongoTemplate.
9. The system of claim 1, wherein the workflow process engine performs data verification through a controller, and the controller comprises a timing controller, a message notification controller, and a data verification controller.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211442225.3A CN115756405A (en) | 2022-11-17 | 2022-11-17 | Process approval system based on container cloud and process engine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211442225.3A CN115756405A (en) | 2022-11-17 | 2022-11-17 | Process approval system based on container cloud and process engine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115756405A true CN115756405A (en) | 2023-03-07 |
Family
ID=85372867
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211442225.3A Pending CN115756405A (en) | 2022-11-17 | 2022-11-17 | Process approval system based on container cloud and process engine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115756405A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116739327A (en) * | 2023-08-11 | 2023-09-12 | 长沙睿展数据科技有限公司 | Lightweight flow engine implementation method in dynamic business flow |
| CN117389681A (en) * | 2023-10-09 | 2024-01-12 | 北京五一嘉峪科技有限公司 | Network security competition fusion platform system |
-
2022
- 2022-11-17 CN CN202211442225.3A patent/CN115756405A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116739327A (en) * | 2023-08-11 | 2023-09-12 | 长沙睿展数据科技有限公司 | Lightweight flow engine implementation method in dynamic business flow |
| CN116739327B (en) * | 2023-08-11 | 2023-10-27 | 长沙睿展数据科技有限公司 | Lightweight flow engine implementation method in dynamic business flow |
| CN117389681A (en) * | 2023-10-09 | 2024-01-12 | 北京五一嘉峪科技有限公司 | Network security competition fusion platform system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107370786B (en) | General information management system based on micro-service architecture | |
| JP6327725B2 (en) | System, method, and graphical user interface for workflow generation, deployment, and / or execution | |
| CN115756405A (en) | Process approval system based on container cloud and process engine | |
| US10956013B2 (en) | User interface for automated flows within a cloud based developmental platform | |
| CN102291464B (en) | System and method for dynamically generating Web Service by business flow in BPM (Business Process Management) | |
| Adams et al. | Dynamic, extensible and context-aware exception handling for workflows | |
| US20200090052A1 (en) | Decision tables and enterprise rules for object linking within an application platform as a service environment | |
| US10146599B2 (en) | System and method for a generic actor system container application | |
| TWI713846B (en) | Domain module computation unit, system containing a model of an enterprise, single board computational unit, grid of computational units, method to provide propagation traceability, and non-transitory computer program product | |
| JP5982366B2 (en) | Systems and methods for private cloud computing | |
| US20180324051A1 (en) | User interface for automated flows within a cloud based developmental platform | |
| US10101972B1 (en) | Data modelling and flow engine for building automated flows within a cloud based developmental platform | |
| US20170038919A1 (en) | Event-driven data processing system | |
| US11137732B2 (en) | Flow engine for building automated flows within a cloud based developmental platform | |
| US11783254B2 (en) | Method and system for implementing an adaptive data governance system | |
| US10747573B2 (en) | Virtualized execution across distributed nodes | |
| JP2014194814A (en) | System, method and graphical user interface for workflow generation, deployment and/or execution | |
| CN112104723A (en) | Multi-cluster data processing system and method | |
| CN116760705B (en) | Multi-tenant platform isolation management system and method based on comprehensive energy management system | |
| CN113672240A (en) | Container-based multi-machine-room batch automatic deployment application method and system | |
| CN113238731B (en) | Ebed development platform | |
| US11663349B2 (en) | System and method for managing data object creation | |
| US10534640B2 (en) | System and method for providing a native job control language execution engine in a rehosting platform | |
| CN117076096A (en) | Task flow execution method and device, computer readable medium and electronic equipment | |
| CN112564979B (en) | Execution method and device of construction task, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |