CN114493479A - Enterprise-level workflow engine implementation method and system based on micro-service SaaS - Google Patents
Enterprise-level workflow engine implementation method and system based on micro-service SaaS Download PDFInfo
- Publication number
- CN114493479A CN114493479A CN202111556056.1A CN202111556056A CN114493479A CN 114493479 A CN114493479 A CN 114493479A CN 202111556056 A CN202111556056 A CN 202111556056A CN 114493479 A CN114493479 A CN 114493479A
- Authority
- CN
- China
- Prior art keywords
- approval
- service
- flow
- node
- current
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Operations Research (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- General Engineering & Computer Science (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
An enterprise-level workflow engine implementation method and system based on micro-service SaaS (software as a service), wherein a process is defined through an online process designer, and expansion nodes are added according to a BPMN2.0 protocol to store customized business configuration, wherein the business configuration comprises an approval rule, an approval mode, a skip condition and service calling; the method comprises the steps of defining a flow form in advance, wherein the flow form comprises a read-only form and an editable form, and displaying details of a business document during examination and approval through the flow form; searching for an approval person at the artificial node through an approval rule, judging whether the artificial node leaves the current artificial node to continue to flow downwards when the artificial node meets the specified condition or not through an approval mode, controlling the flow branch trend through the jump condition, and remotely calling the service module at the specified node through service calling to execute the custom logic. The invention realizes high maintainability and high expandability of the approval flow under the scenes of multiple tenants and multiple services, and greatly improves the availability of the workflow engine.
Description
Technical Field
The invention relates to a method and a system for realizing an enterprise-level workflow engine based on micro-service software as a service (SaaS), belonging to the technical field of business data processing.
Background
With the development of business, enterprises adopting traditional local deployment software cannot keep up with the development speed and strategic changes of the enterprises. The local deployment has the problems of high operation and maintenance cost, difficulty in upgrading, difficulty in meeting personalized requirements in time and the like. Therefore, the SaaS platform is generated by the operation, the software is served, the supplier uniformly deploys the software on the cloud server for uniform operation and maintenance, the customer can use the service only by paying a certain subscription fee, and the software can flexibly purchase extended services and be developed in a customized manner. The enterprise information approval process is also a necessary way for enterprise development, and the OA system and the financial system almost mostly require workflow engines to open manual approval and system automation in systems with complex business.
The traditional workflow engine is generally divided into an internal workflow engine and an external workflow engine, wherein the internal workflow engine is directly integrated into a certain business system, for example, the workflow engine of an OA system, which is directly coupled with the OA system, and has insufficient flexibility and narrow application range. The external workflow engine is generally deployed independently and is used as a third-party system to communicate with each system. The existing mainstream service system needs to access an approval process, and a complex process design is needed for accessing an approval flow in a scene. The approval content of each scene is different, and the contents of forms submitted to the approvers for review and viewing are changed, so that review detail pages are different. Therefore, in the service approval process of the current service system, professional approval personnel need to manually verify and confirm the service request to be approved and finally make a corresponding decision, the approval efficiency is low, the service approval process is greatly influenced by personal factors of the approval personnel, and the accuracy of the approval decision is limited.
Disclosure of Invention
Therefore, the invention provides a method and a system for realizing an enterprise-level workflow engine based on a micro-service software as a service (SaaS), which overcome the problems of complex configuration, higher use cost, incomplete function and the like of a tenant workflow engine of the existing SaaS platform and realize high maintainability and high expandability of an approval flow in multi-tenant and multi-service scenes.
In order to achieve the above purpose, the invention provides the following technical scheme: an enterprise-level workflow engine implementation method based on micro-service SaaS comprises the following steps:
the method comprises the steps that a flow is defined through an online flow designer, and an expansion node is added according to a BPMN2.0 protocol to store customized business configuration, wherein the business configuration comprises an approval rule, an approval mode, a skip condition and service calling;
the method comprises the steps that a flow form is defined in advance, the flow form comprises a read-only form and an editable form, and the details of a business document are displayed during examination and approval through the flow form;
searching for an approval person at the manual node according to the approval rule, judging whether the approval person leaves the current manual node to continue to flow downwards when the approval person meets the specified condition or not in the approval mode, controlling the flow branch trend through the jump condition, and remotely calling the service module at the specified node through the service call to execute the custom logic.
As a preferred scheme of an enterprise-level workflow engine implementation method based on micro-service SaaS, the read-only form is implemented by iframe, and the editable form is implemented by dynamic routing and asynchronous loading to realize cross-module page loading.
As a preferred scheme of an enterprise-level workflow engine implementation method based on micro-service software as a service (SaaS), the definition of the flow form comprises a front-end route corresponding to the form;
configuring an examination and approval form for any artificial node in the process of designing the flow chart, and storing the code of the examination and approval form into the current node;
and in the approval process, dynamically analyzing the form address according to the form code and the process variable.
As an optimal scheme of an enterprise-level workflow engine implementation method based on micro-service SaaS, service definition codes are stored in the business configuration, and when a process is started, the service definition codes in process nodes are dynamically analyzed;
and when the approval rule does not meet the service scene, compiling the finder logic by self-defining the approval rule.
The method is used as a preferred scheme of an enterprise-level workflow engine implementation method based on micro-service SaaS, and further comprises the steps of selecting a required mail template from manual nodes defined by a process and storing template codes in the manual nodes by predefining the mail template and a source of data required by rendering the mail template;
when the process is started, mail template configuration is obtained according to template codes, mail contents are dynamically rendered through a Free marker engine in combination with a predefined data source, and finally the mail contents are sent to an approver through message service.
The preferable scheme of the enterprise-level workflow engine implementation method based on the microservice SaaS further comprises the steps of performing message embedding according to the execution period of the listener and sending different message types to different approvers at different periods.
As a preferred scheme of an enterprise-level workflow engine implementation method based on micro-service SaaS, a current to-be-handled example is used as a parent class to create a subclass to-be-handled example, the examination and approval person of the parent class is reset into an appointed type, the appointed type is determined according to an additional type, and the additional type comprises a front additional label and a rear additional label;
deleting the to-be-processed examples approved by the current approver, controlling flow circulation according to the type of the added labels, tracing the former added labels back to the original approver, and continuing to flow downwards according to the flow chart after the added labels;
and obtaining the nodes which are approved for the last time according to the current approver, deleting all to-be-processed examples of the current nodes, and backtracking the current flow to the specified nodes.
As a preferred scheme of the enterprise-level workflow engine implementation method based on the micro-service SaaS, the process definitions under the same classification are assigned by pre-configuring the service parameter group and associating different process definitions with different service parameter groups, so that when the workflow is started, the process definitions are dynamically selected by the service parameters and the workflow is started.
The invention also provides an enterprise-level workflow engine implementation system based on the microservice SaaS, which comprises the following steps:
the system comprises a process definition unit, a business configuration unit and a business configuration unit, wherein the process definition unit is used for carrying out process definition through an online process designer, expanding nodes are added according to a BPMN2.0 protocol to store self-defined business configuration, and the business configuration comprises an approval rule, an approval mode, a skipping condition and service calling;
the form definition unit is used for defining a flow form in advance, the flow form comprises a read-only form and an editable form, and the details of the business document are displayed during examination and approval through the flow form;
and the task processing unit is used for searching for an approval person in the manual node through the approval rule, judging whether the approval person leaves the current manual node and continues to flow downwards when the approval person meets the specified condition or not through the approval mode, controlling the flow branch trend through the jump condition, and remotely calling the service module to execute custom logic at the specified node through the service call.
As a preferred scheme of an enterprise-level workflow engine implementation system based on micro-service SaaS, the read-only form is implemented through iframe, and the editable form is implemented through dynamic routing and asynchronous loading to realize cross-module page loading.
As an optimal scheme of an enterprise workflow engine implementation system based on micro-service SaaS, the definition of the flow form comprises a front-end route corresponding to the form;
configuring an examination and approval form for any artificial node in the process of designing the flow chart, and storing the code of the examination and approval form into the current node;
and in the approval process, dynamically analyzing the form address according to the form code and the process variable.
As an optimal scheme of an enterprise-level workflow engine implementation system based on micro-service SaaS, service definition codes are stored in the business configuration, and when a process is started, the service definition codes in process nodes are dynamically analyzed;
and when the approval rule does not meet the service scene, compiling the finder logic by self-defining the approval rule.
The system further comprises a mail examination and approval unit, wherein the mail examination and approval unit is used for selecting a required mail template from manual nodes defined by a process and storing template codes in the manual nodes through predefining the mail template and a source of data required by rendering the mail template.
As a preferred scheme of an enterprise-level workflow engine implementation system based on micro-service SaaS, when a process is started, mail template configuration is obtained according to template codes, mail contents are dynamically rendered through a Free marker engine in combination with a predefined data source, and finally the mail contents are sent to an approver through a message service.
The enterprise-level workflow engine implementation system based on the microservice SaaS further comprises a message reminding unit, wherein the message reminding unit is used for performing message point burying according to the execution period of the monitor and sending different message types to different approvers at different periods.
The system is used as a preferred scheme of an enterprise-level workflow engine implementation system based on micro-service SaaS, and further comprises a tagging unit, a processing unit and a processing unit, wherein the tagging unit is used for creating a sub-class to-do instance by taking a current to-do instance as a parent class, resetting an examination and approval person of the parent class into a specified type, and determining the specified type according to a tagging type, wherein the tagging type comprises front tagging and rear tagging; deleting the to-be-processed examples approved by the current approver, controlling flow circulation according to the type of the added labels, tracing the former added labels back to the original approver, and continuing to flow downwards according to the flow chart after the former added labels.
The enterprise-level workflow engine implementation system based on the microservice SaaS further comprises a withdrawing unit, wherein the withdrawing unit is used for obtaining the nodes which are examined and approved last time according to the current approver, deleting all to-be-processed examples of the current nodes and backtracking the current process to the designated nodes.
The system further comprises a starting processing unit, which is used for defining the processes under the same classification, assigning different service parameter groups and associating different process definitions by pre-configuring the service parameter groups, so as to dynamically select the process definitions and start the workflows through the service parameters when the workflows are started.
The invention has the following advantages: the method comprises the steps that a flow is defined through an online flow designer, and self-defined business configuration is stored by adding an extension node according to a BPMN2.0 protocol, wherein the business configuration comprises an approval rule, an approval mode, a skip condition and service calling; the method comprises the steps of defining a flow form in advance, wherein the flow form comprises a read-only form and an editable form, and displaying details of a business document during examination and approval through the flow form; searching for an approval person at the artificial node through an approval rule, judging whether the artificial node leaves the current artificial node to continue to flow downwards when the artificial node meets the specified condition or not through an approval mode, controlling the flow branch trend through the jump condition, and remotely calling the service module at the specified node through service calling to execute the custom logic. The invention improves the high expansibility of process starting, and based on the approval example of the starting process after the workflow engine of the rule engine receives the service parameters, the invention meets the approval flow difference of different companies under the same tenant of the actual service; other services or external system collaboration of the process engine are enhanced, the process approval supports the embedded customized form, and the subsequent process flow can be controlled by using the business data configuration in the business form; the method comprises the following steps that in operation, the mobile terminal, the PC terminal and the mail approval mode are supported to be processed; performing cross-service task scheduling through a listener to realize business cooperation of a plurality of micro services; the development difficulty and the code amount of the process engine are reduced, and the requirement expansion and the collaborative development and maintenance are facilitated; the user and the implementer use configuration, the visual flow chart configuration and the configuration chart can lead out XML file multi-environment migration and message reminding in the system or external message reminding cooperation, and the use portability and the friendliness of the workflow engine are improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary, and that other embodiments can be derived from the drawings provided by those of ordinary skill in the art without inventive effort.
The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so that those skilled in the art can understand and read the present invention, and do not limit the conditions for implementing the present invention, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the functions and purposes of the present invention, should still fall within the scope of the present invention.
Fig. 1 is a schematic diagram of an implementation method of an enterprise-level workflow engine based on a microservice SaaS according to an embodiment of the present invention;
fig. 2 is a technical route of an enterprise-level workflow engine implementation method based on microservice SaaS provided in an embodiment of the present invention;
fig. 3 is a schematic diagram of tagging in an enterprise-level workflow engine implementation method based on microservice SaaS provided in an embodiment of the present invention;
fig. 4 is a schematic diagram of an enterprise-level workflow engine implementation system based on a microservice SaaS provided in an embodiment of the present invention.
Detailed Description
The present invention is described in terms of particular embodiments, other advantages and features of the invention will become apparent to those skilled in the art from the following disclosure, and it is to be understood that the described embodiments are merely exemplary of the invention and that it is not intended to limit the invention to the particular embodiments disclosed. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
Referring to fig. 1 and fig. 2, embodiment 1 of the present invention provides an enterprise-level workflow engine implementation method based on a microservice SaaS, including:
s1, flow definition is carried out through an online flow designer, and expansion nodes are added according to a BPMN2.0 protocol to store customized business configuration, wherein the business configuration comprises an approval rule, an approval mode, a jump condition and service calling;
s2, flow form definition is carried out in advance, the flow form comprises a read-only form and an editable form, and the details of the business document are displayed during examination and approval through the flow form;
s3, searching for an approval person in the manual node through an approval rule, judging whether the current manual node is left when the approval person meets the specified condition through an approval mode, continuing to flow downwards, controlling the flow branch trend through the skip condition, and remotely calling the service module at the specified node through service calling to execute custom logic.
In the implementation, based on an Activiti official standard online process designer, the BPMN2.0 protocol is expanded aiming at the customized process function configuration of a service scene, expansion nodes are added, and the customized service configuration is stored and comprises configurations such as an approval rule, an approval mode, a skip condition, service call and the like. The method can be based on the importing and exporting of the BPMN2.0 protocol flow, thereby realizing the multi-environment and multi-system migration of the flow, namely 'one-time configuration and everywhere use', and a client can directly configure or import the existing flow chart on line when using the SaaS platform.
Specifically, activti is an open source project brand that operates and manages independently, is a lightweight, embeddable BPM engine, and is also designed for an extensible cloud architecture. Activit provides a relaxed Apache license of 2.0 so that this item can be widely used, while facilitating the matching of the activit BPM engine with BPMN 2.0. BPMN2.0 defines meta-models and execution semantics for processes compared to BPMN1.x, i.e. BPMN2.0 solves the storage, exchange and execution problems.
In this embodiment, the read-only form is implemented by an iframe, and the editable form implements cross-module loading of pages by dynamic routing and asynchronous loading. The definition of the flow form comprises a front-end route corresponding to the form; configuring an examination and approval form for any artificial node in the process of designing the flow chart, and storing the code of the examination and approval form into the current node; and in the approval process, dynamically analyzing the form address according to the form code and the process variable.
Specifically, the flow form is used for displaying details of the business document during examination and approval. Including both read-only forms and editable forms. The read-only form is realized based on the iframe, and the editable form realizes the cross-module loading of the page based on the dynamic routing and the asynchronous loading. The method mainly comprises the steps of defining a flow form in advance and mainly comprising a front-end route corresponding to the form. When the flow chart is designed, the examination and approval form can be configured aiming at any manual node, and the examination and approval form code is stored in the current node. During approval, the workflow engine dynamically analyzes the form address according to the form code and the process variable, and the form can be changed on the premise of not modifying the process definition.
In particular, an iframe is an HTML tag that acts as a document within a document, or a floating frame. The iframe element creates an inline frame (i.e., inline frame) that contains another document.
In this embodiment, the service control of the trend of the four control flows, i.e., the approval rule, the approval mode, the skip condition, and the service call, can be abstracted into the service task. By defining in advance, the customer can directly select the above high-order configuration in the process design to realize more complicated process trend.
The approval rules, the approval modes, the skip conditions and the service calling support remote calling, expressions and other modes. The remote call is called based on Rest Template, and the expression is analyzed based on odyssus.
In this embodiment, the service definition code stored in the business configuration is dynamically analyzed when the process is started;
and when the approval rule does not meet the service scene, compiling the person finding logic by self-defining the approval rule.
Specifically, all the service definition codes are stored in the process definition, and when the process is started, the workflow engine dynamically analyzes the service definition codes in the process nodes, so that the process definition does not need to be modified after the service definition is modified, functions are not controlled by the version of the process definition to a certain extent, the flexibility of interaction between the workflow engine and other micro services is improved, more complex service scenes are supported finally, and if the built-in approval rule of the system does not meet the service scenes, the custom creation of the approval rule is supported to compile the finder logic in other micro services.
In this embodiment, the method further includes step S4, selecting a desired mail template from the manual nodes defined by the process by predefining the mail template and the source of data required for rendering the mail template, and storing the template code in the manual node;
when the process is started, mail template configuration is obtained according to template codes, mail contents are dynamically rendered through a Free marker engine in combination with a predefined data source, and finally the mail contents are sent to an approver through message service.
Specifically, a required mail template is selected from the process definition artificial nodes by predefining a mail template and a source of data required by rendering the template, and finally the template code is stored in the artificial nodes. When the process is started, the workflow engine acquires mail template configuration according to the template codes, dynamically renders mail contents by combining a Free marker engine with a predefined data source, and finally sends the mail contents to an approver through message service.
The mail can be attached with examination approval and examination approval rejection buttons, the mailto is set as the address of a mail receiving server in the buttons, and the mail subject contains the necessary data for examination approval to be handled. The approver can input the approval opinions by clicking the corresponding buttons and then replies the mails, and the workflow engine scans the mail receiving box of the mailbox server through the timing task and finishes approval of the process according to the mail receiving information.
In this embodiment, S5 further includes performing message embedding according to the execution time of the listener, and sending different message types to different approvers at different times.
Specifically, the activity manual node provides four listener execution periods such as create, assign, complete and delete, and the like, and the leave period is expanded, namely, the leave period is executed when the leave manual node meets the approval mode. And message embedding is carried out based on the five execution periods, different message types are sent aiming at different approvers at different periods, the approvers are finally reminded in the system, and the butt joint of an external system is supported, so that the to-be-handled reminding of the external system is achieved.
Referring to fig. 3, in the embodiment, a current to-be-handled instance is used as a parent class to create a child to-be-handled instance, an examination and approval person of the parent class is reset to be a specified type, the specified type is determined according to an additional type, and the additional type includes front additional tagging and rear additional tagging;
deleting the to-be-processed examples approved by the current approver in the to-be-processed approval execution process created by adding the labels, controlling flow circulation according to the type of the labels, tracing the labels to the original approver before adding the labels, and continuing to flow downwards according to the flow chart after adding the labels;
in the withdrawal process, the nodes which are approved for the last time are obtained according to the current approver, all to-be-handled examples of the current nodes are deleted, and the current process is traced back to the designated nodes.
Specifically, the workflow engine takes the current to-be-handled instance as a parent class to create a subclass to-be-handled instance, meanwhile, the examination and approval person of the parent class is reset to be a specified type, the type is determined according to the endorsement type, a manager of the subclass is set as the examination and approval person of the parent class, namely the current examination and approval person, and the number of created subclasses depends on the number of the examination and approval person and the number of endorsers. After the subclass finishes approval, the parent class is inquired and processed, the specific processing needs to be carried out according to the type of the label added to the parent class, the former label needs to reset the approver to the original approver and then directly returns, and the latter label adding needs to finish the approval on the basis of the former label adding.
And the workflow engine acquires the nodes (non-process current nodes) which are approved last time by the current approver according to the current approver, deletes all to-be-processed examples of the current nodes, and finally backtracks the current process to the designated nodes.
In this embodiment, for the process definitions under the same classification, by configuring the service parameter group in advance, different service parameter groups are specified to associate with different process definitions, so that when the workflow is started, the process definition is dynamically selected through the service parameters and the workflow is started.
Specifically, for the process definitions in the same category (using the same type of service documents), different service parameter sets are assigned to associate with different process definitions by pre-configuring the service parameter sets (see table 1), so that when the workflow is started, the process definitions are dynamically selected by the service parameters and the workflow is started.
| Serial number | Company(s) | Business entity | Purchasing group | Source system | Flow path | |
|
| 1 | Enterprise A | |
Purchase group 001 | SRM | Procedure A | Account a | |
| 2 | Enterprise A | |
/ | / | Procedure B | Account b | |
| 3 | / | |
/ | SRM | Procedure | Account c | |
| 4 | | Plant | 1 | / | / | Procedure D | Account d |
| 5 | / | / | / | / | Procedure E | Account d |
Matching the document parameter with the flow A, B, C, D, and selecting the flow A because the field value of the flow A has the most matching value; if data which is not matched with the process A exists, but the data is matched with the process B, C, D and the number of matched parameters is the same, because the variable [ company ] is earlier than the variable [ business entity ], the data is selected from the process B, D, and the two priorities of the process B, D are consistent, so that one data is randomly selected; the variable values of the flow E are all null, the flow is a default flow, the priority of the flow is the lowest, and when the values are not matched, the flow is selected.
In summary, the invention defines the flow through the online flow designer, and adds the expansion node to store the self-defined business configuration according to the BPMN2.0 protocol, wherein the business configuration comprises an approval rule, an approval mode, a jump condition and service call; the method comprises the steps of defining a flow form in advance, wherein the flow form comprises a read-only form and an editable form, and displaying details of a business document during examination and approval through the flow form; searching for an approval person at the artificial node through an approval rule, judging whether the artificial node leaves the current artificial node to continue to flow downwards when the artificial node meets the specified condition or not through an approval mode, controlling the flow branch trend through the jump condition, and remotely calling the service module at the specified node through service calling to execute the custom logic. Selecting a required mail template from the manual nodes defined by the process by predefining the mail template and the source of data required by rendering the mail template, and storing the template code in the manual nodes; when the process is started, mail template configuration is obtained according to template codes, mail contents are dynamically rendered through a Free marker engine in combination with a predefined data source, and finally the mail contents are sent to an approver through message service. And message embedding is carried out according to the execution period of the monitor, and different message types are sent to different approvers at different periods. Creating a subclass to-be-handled example by taking the current to-be-handled example as a parent class, resetting an approval person of the parent class as a specified type, and determining the specified type according to the tagging type, wherein the tagging type comprises front tagging and rear tagging; and obtaining the nodes which are approved for the last time according to the current approver, deleting all to-be-processed examples of the current nodes, and backtracking the current flow to the specified nodes. The invention improves the high expansibility of process starting, and based on the approval example of the starting process after the workflow engine of the rule engine receives the service parameters, the invention meets the approval flow difference of different companies under the same tenant of the actual service; enhancing the cooperation of other services or external systems of the process engine, supporting the embedding of customized forms for process approval, and configuring and controlling the flow of subsequent processes by using business data in the business forms; the method comprises the following steps that in operation, the mobile terminal, the PC terminal and the mail approval mode are supported to be processed; performing cross-service task scheduling through a listener to realize business cooperation of a plurality of micro services; the development difficulty and the code amount of the process engine are reduced, and the requirement expansion and the collaborative development and maintenance are facilitated; the user and the implementer use configuration, the visual flow chart configuration and the configuration chart can export XML file multi-environment migration, and message reminding in the system or external message reminding cooperation, so that the use portability and the friendliness of the workflow engine are improved.
Example 2
Referring to fig. 4, embodiment 2 of the present invention further provides an enterprise-level workflow engine implementation system based on a microservice SaaS, including:
the system comprises a flow definition unit 1, a business configuration unit and a business configuration unit, wherein the flow definition unit is used for carrying out flow definition through an online flow designer, adding an extension node according to a BPMN2.0 protocol and storing custom business configuration, and the business configuration comprises an approval rule, an approval mode, a jump condition and service calling;
the form definition unit 2 is used for carrying out flow form definition in advance, the flow form comprises a read-only form and an editable form, and the details of the business document are displayed during examination and approval through the flow form;
and the task processing unit 3 is used for searching for an approval person in the artificial node through the approval rule, judging whether the artificial node leaves the current artificial node and continues to flow downwards when the artificial node meets the specified condition or not in an approval mode, controlling the flow branch trend through the skip condition, and remotely calling the service module at the specified node through service call to execute the custom logic.
In this embodiment, the read-only form is implemented by an iframe, and the editable form implements cross-module loading of pages by dynamic routing and asynchronous loading.
In this embodiment, the definition of the flow form includes a front-end route corresponding to the form;
configuring an examination and approval form for any artificial node in the process of designing the flow chart, and storing the code of the examination and approval form into the current node;
and in the approval process, dynamically analyzing the form address according to the form code and the process variable.
In this embodiment, the service definition code stored in the business configuration is dynamically analyzed when the process is started;
and when the approval rule does not meet the service scene, compiling the person finding logic by self-defining the approval rule.
In this embodiment, the system further includes an email approval unit 4, configured to select a required email template from manual nodes defined by the process by predefining an email template and a source of data required for rendering the email template, and store a template code in the manual node.
In the embodiment, when the process is started, mail template configuration is obtained according to the template codes, mail contents are dynamically rendered through a Free marker engine in combination with a predefined data source, and finally the mail contents are sent to an approver through a message service.
In this embodiment, the system further includes a message reminding unit 5, configured to perform message dotting according to the execution period of the listener, and send different message types to different approvers at different periods.
In this embodiment, the system further includes an add-on unit 6, configured to create a child to-be-handled instance with the current to-be-handled instance as a parent class, and reset the approval person of the parent class as an assigned type, where the assigned type is determined according to an add-on type, and the add-on type includes a front add-on and a rear add-on; deleting the to-be-processed examples approved by the current approver, controlling flow circulation according to the type of the added labels, tracing the former added labels back to the original approver, and continuing to flow downwards according to the flow chart after the former added labels.
In this embodiment, the system further includes a withdrawing unit 7, configured to obtain a node that has been examined and approved for the last time according to the current approver, delete all to-do instances of the current node, and trace back the current process to the designated node.
In this embodiment, the system further includes a starting processing unit 8, configured to configure the service parameter group in advance for the process definitions in the same category, and specify different service parameter groups to associate with different process definitions, so as to dynamically select the process definition and start the workflow through the service parameters when the workflow is started.
It should be noted that, for the information interaction, execution process, and other contents between the modules/units of the system, since the same concept is based on the method embodiment in embodiment 1 of the present application, the technical effect brought by the information interaction, execution process, and other contents are the same as those of the method embodiment of the present application, and specific contents may refer to the description in the foregoing method embodiment of the present application, and are not described herein again.
Example 3
Embodiment 3 of the present invention provides a non-transitory computer-readable storage medium, where a program code of an enterprise-level workflow engine implementation method based on a microservice SaaS is stored in the computer-readable storage medium, where the program code includes an instruction for executing the enterprise-level workflow engine implementation method based on the microservice SaaS of embodiment 1 or any possible implementation manner thereof.
The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
Example 4
An embodiment 4 of the present invention provides an electronic device, including: a memory and a processor;
the processor and the memory are communicated with each other through a bus; the memory stores program instructions executable by the processor, and the processor calls the program instructions to execute the microservice SaaS-based enterprise-level workflow engine implementation method of embodiment 1 or any possible implementation manner thereof.
Specifically, the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated in the processor, located external to the processor, or stand-alone.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to be performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.).
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (10)
1. An enterprise-level workflow engine implementation method based on micro-service SaaS is characterized by comprising the following steps:
the method comprises the steps that a flow is defined through an online flow designer, and an expansion node is added according to a BPMN2.0 protocol to store customized business configuration, wherein the business configuration comprises an approval rule, an approval mode, a skip condition and service calling;
the method comprises the steps that a flow form is defined in advance, the flow form comprises a read-only form and an editable form, and the details of a business document are displayed during examination and approval through the flow form;
searching for an approval person at the manual node according to the approval rule, judging whether the approval person leaves the current manual node to continue to flow downwards when the approval person meets the specified condition or not in the approval mode, controlling the flow branch trend through the jump condition, and remotely calling the service module at the specified node through the service call to execute the custom logic.
2. The method as claimed in claim 1, wherein the read-only form is implemented by iframe, and the editable form is implemented by dynamic routing and asynchronous loading to load pages across modules.
3. The method for implementing an enterprise-level workflow engine based on microservice SaaS of claim 2, wherein the definition of the flow form comprises a front-end route corresponding to the form;
configuring an examination and approval form for any artificial node in the process of designing the flow chart, and storing the code of the examination and approval form into the current node;
and in the approval process, dynamically analyzing the form address according to the form code and the process variable.
4. The method for implementing an enterprise-level workflow engine based on microservice SaaS according to claim 1, wherein the service definition code is stored in the business configuration, and when a process is started, the service definition code in a process node is dynamically analyzed;
and when the approval rule does not meet the service scene, compiling the finder logic by self-defining the approval rule.
5. The method for realizing the enterprise-level workflow engine based on the microservice SaaS as claimed in claim 1, further comprising the steps of selecting a required mail template from manual nodes defined by a flow by predefining the mail template and a source of data required for rendering the mail template, and storing template codes in the manual nodes;
when the process is started, mail template configuration is obtained according to template codes, mail contents are dynamically rendered through a Free marker engine in combination with a predefined data source, and finally the mail contents are sent to an approver through message service.
6. The method as claimed in claim 5, further comprising performing message burial according to the execution period of the listener, and sending different message types to different approvers at different times.
7. The enterprise-level workflow engine implementation method based on microservice SaaS (software as a service) of claim 1, wherein the current to-be-handled instance is used as a parent class to create a subclass to-be-handled instance, the examination and approval person of the parent class is reset to be a specified type, the specified type is determined according to an additional type, and the additional type comprises a front additional type and a rear additional type;
deleting the to-be-processed examples approved by the current approver, controlling flow circulation according to the type of the added labels, tracing the former added labels back to the original approver, and continuing to flow downwards according to the flow chart after the added labels;
and obtaining the nodes which are approved for the last time according to the current approver, deleting all to-be-handled examples of the current nodes, and backtracking the current process to the specified nodes.
8. The method for implementing the enterprise-level workflow engine based on the microservice SaaS as claimed in claim 1, wherein for the process definitions under the same classification, the service parameter group is configured in advance, and different process definitions are associated with different service parameter groups, so that when the workflow is started, the process definition is dynamically selected through the service parameters and the workflow is started.
9. Enterprise-level workflow engine implementation system based on microservice SaaS (software as a service), which is characterized by comprising:
the system comprises a flow definition unit, a business configuration unit and a business configuration unit, wherein the flow definition unit is used for carrying out flow definition through an online flow designer, adding an extension node according to a BPMN2.0 protocol and storing custom business configuration, and the business configuration comprises an approval rule, an approval mode, a jump condition and service calling;
the form definition unit is used for defining a flow form in advance, the flow form comprises a read-only form and an editable form, and the details of the business document are displayed during examination and approval through the flow form;
and the task processing unit is used for searching for an approval person in the manual node through the approval rule, judging whether the approval person leaves the current manual node and continues to flow downwards when the approval person meets the specified condition or not through the approval mode, controlling the flow branch trend through the jump condition, and remotely calling the service module to execute custom logic at the specified node through the service call.
10. The microservice SaaS-based enterprise-level workflow engine implementation system of claim 9, wherein the read-only form is implemented by iframe, and the editable form implements cross-module loading of pages by dynamic routing and asynchronous loading;
the definition of the flow form comprises a front end route corresponding to the form;
configuring an examination and approval form for any artificial node in the process of designing the flow chart, and storing the code of the examination and approval form into the current node;
in the examination and approval process, dynamically analyzing the form address according to the form code and the process variable;
the business configuration stores service definition codes, and when the process is started, the service definition codes in the process nodes are dynamically analyzed;
when the approval rule does not meet the service scene, compiling the finder logic by self-defining the approval rule;
the mail examination and approval unit is used for selecting a required mail template from the manual nodes defined by the process through predefining the mail template and the source of data required by rendering the mail template, and storing the template code in the manual nodes;
when the process is started, mail template configuration is obtained according to template codes, mail contents are dynamically rendered through a Free marker engine in combination with a predefined data source, and finally the mail contents are sent to an approver through message service;
the system also comprises a message reminding unit, a message processing unit and a message processing unit, wherein the message reminding unit is used for carrying out message point burying according to the execution period of the monitor and sending different message types to different approvers at different periods;
the system also comprises a signing unit, a judging unit and a judging unit, wherein the signing unit is used for creating a subclass to-be-handled example by taking the current to-be-handled example as a parent class, resetting the examining and approving person of the parent class into a specified type, and determining the specified type according to a signing type which comprises front signing and back signing; deleting the to-be-processed examples approved by the current approver, controlling flow circulation according to the type of the added labels, tracing the former added labels back to the original approver, and continuing to flow downwards according to the flow chart after the added labels;
the system also comprises a withdrawing unit, a judging unit and a judging unit, wherein the withdrawing unit is used for obtaining the nodes which are examined and approved for the last time according to the current approver, deleting all to-be-handled examples of the current nodes and backtracking the current process to the designated nodes;
the system also comprises a starting processing unit, which is used for defining the processes under the same classification, appointing different service parameter groups to be associated with different process definitions by pre-configuring the service parameter groups so as to dynamically select the process definitions and start the workflow by the service parameters when the workflow is started.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111556056.1A CN114493479A (en) | 2021-12-17 | 2021-12-17 | Enterprise-level workflow engine implementation method and system based on micro-service SaaS |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111556056.1A CN114493479A (en) | 2021-12-17 | 2021-12-17 | Enterprise-level workflow engine implementation method and system based on micro-service SaaS |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114493479A true CN114493479A (en) | 2022-05-13 |
Family
ID=81494820
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111556056.1A Pending CN114493479A (en) | 2021-12-17 | 2021-12-17 | Enterprise-level workflow engine implementation method and system based on micro-service SaaS |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114493479A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115292022A (en) * | 2022-09-29 | 2022-11-04 | 泰豪软件股份有限公司 | Workflow engine system, implementation method, storage medium and computer equipment |
| CN115396511A (en) * | 2022-08-24 | 2022-11-25 | 数字浙江技术运营有限公司 | Multi-tenant process engine creating and applying method and system |
| CN117372177A (en) * | 2023-10-13 | 2024-01-09 | 国任财产保险股份有限公司 | Novel non-vehicle underwriting core system |
| CN117973828A (en) * | 2024-03-28 | 2024-05-03 | 北京首信科技股份有限公司 | Approval process management method and device for business general purpose based on Activiti |
-
2021
- 2021-12-17 CN CN202111556056.1A patent/CN114493479A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115396511A (en) * | 2022-08-24 | 2022-11-25 | 数字浙江技术运营有限公司 | Multi-tenant process engine creating and applying method and system |
| CN115292022A (en) * | 2022-09-29 | 2022-11-04 | 泰豪软件股份有限公司 | Workflow engine system, implementation method, storage medium and computer equipment |
| CN117372177A (en) * | 2023-10-13 | 2024-01-09 | 国任财产保险股份有限公司 | Novel non-vehicle underwriting core system |
| CN117973828A (en) * | 2024-03-28 | 2024-05-03 | 北京首信科技股份有限公司 | Approval process management method and device for business general purpose based on Activiti |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114493479A (en) | Enterprise-level workflow engine implementation method and system based on micro-service SaaS | |
| US9268538B2 (en) | Metadata driven user interface system and method | |
| CN112668295B (en) | Management system and method based on custom form and active workflow | |
| US20100042620A1 (en) | System and Methods for Managing Complex Service Delivery Through Coordination and Integration of Structured and Unstructured Activities | |
| CN104572068B (en) | For keeping the method and system of product behavioral data via catalogue | |
| CN103049271A (en) | Method and device for automatically generating description document of API (application program interface) | |
| ITMI20130390U1 (en) | METHODS AND SYSTEM FOR DYNAMIC ENDPOINT GENERATORS, DETECTION AND MEDIATION (BROKERAGE) OF DYNAMIC REMOTE OBJECTS | |
| CN106485390A (en) | The generation method of examination ＆ approval stream and device | |
| US20100153152A1 (en) | Method and system for recursion check and low-level code generation for directed graph | |
| CN109710528B (en) | Test script generation method, device, equipment and medium | |
| US20150347966A1 (en) | Meeting management and project management element reconciliation | |
| US9116708B2 (en) | Program creation support apparatus, program, and information system | |
| JP3146051B2 (en) | Document review support method | |
| CN112365226A (en) | Software service business management system | |
| CN111191180A (en) | Method and device for constructing micro-service system in invoice field and storage medium | |
| Bochon et al. | Challenges of cloud business process management | |
| CN115048103A (en) | Workflow implementation method, device and system | |
| CN114138797A (en) | System, method and device for realizing flow visualization configuration and operation based on mobile terminal, processor and computer storage medium thereof | |
| CN112508535A (en) | Jbpm-based method and device for improving approval workflow | |
| JP2021149405A (en) | Management device associating prepayment with transfer, management method associating prepayment with transfer and management program associating prepayment with transfer | |
| Hassan et al. | Development of an order processing system using Google Sheets and Appsheet for a Malaysian automotive SME factory warehouse | |
| US20240160440A1 (en) | Import process in a software package management system | |
| US20190303818A1 (en) | Methods and systems for generating and managing, automating inheritable and dynamic business processes | |
| KR102589989B1 (en) | System for managing simple approval requests using email and the operating method thereof | |
| JP6990574B2 (en) | Delivery date management device, delivery date management method and delivery date management program |
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 |