CN108305010B - Workflow engine system and cross-platform and cross-application flow propelling method thereof - Google Patents
Workflow engine system and cross-platform and cross-application flow propelling method thereof Download PDFInfo
- Publication number
- CN108305010B CN108305010B CN201810138600.2A CN201810138600A CN108305010B CN 108305010 B CN108305010 B CN 108305010B CN 201810138600 A CN201810138600 A CN 201810138600A CN 108305010 B CN108305010 B CN 108305010B
- Authority
- CN
- China
- Prior art keywords
- workflow engine
- flow
- layer
- information
- management module
- 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.)
- Active
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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
A workflow engine system and a cross-platform and cross-application flow propelling method thereof are provided, wherein the workflow engine system comprises a workflow engine server and a workflow engine client; the workflow engine server comprises a workflow engine external interaction module, a workflow engine UI control layer, a workflow engine core module, a physical layer and a data persistence layer. The invention realizes the unidirectional complete decoupling of the workflow engine to the application system, and the addition of various self-defined parameters and MARK identification elements, so that the use of the workflow engine becomes flexible and changeable.
Description
Technical Field
The invention belongs to the field of information, and relates to a workflow engine system and a cross-platform and cross-application flow propulsion method thereof.
Background
With the development of information-based systems, the role of workflow is more and more indispensable, various workflow engine design schemes are developed, and there are embedded, service-oriented and plug-in schemes, which are all used to break barriers between data islands and between departments, so that various data and various departments work cooperatively according to a set business process, and a set of simple or complex business is completed. Most of workflow engine design schemes can meet the business flow propelling function of a single information system to achieve the effect of breaking data barriers among departments, but under the large environment of rapid popularization of the current information system, various information systems with special and precise business are arranged in a lot, ERP, CRM, OA, WMS, MES and the like appear, how to communicate business flows of various platforms and different information systems, and the problem of dealing with business association among the systems is needed to be solved.
According to the traditional offline communication scheme, the output data of one system is re-recorded in the other system, or the data and services of two informatization systems are communicated by using a file exporting and importing mode, so that the promotion of the service flow is realized. Due to excessive manual on-line operation intervention, the accuracy of data is difficult to control, the export and import of secondary data also cause data redundancy, and the timeliness of the process is seriously reduced. Another conventional scheme is a class message notification scheme, which is to send related message information of an information system in a previous stage of a process to an information system in a next stage through a tool similar to a message middleware, so as to implement notification of a service state. The class message notification scheme has the defects that only the service state notification can be achieved, and service data in each information system is difficult to share.
In the existing information system, in order to connect various platforms and information systems of different applications, an overall business process needs to be divided into two or more separate processes, and the two or more separate processes exist in different process engines.
Disclosure of Invention
The invention aims to provide a workflow engine system and a cross-platform and cross-application flow propelling method thereof, aiming at the problems in the prior art, wherein one workflow engine server is used for simultaneously serving a plurality of applications of different platforms, so that the barriers between different application business flows are broken, and the one-way complete decoupling of a workflow engine management system to other application systems can be realized.
In order to achieve the purpose, the technical scheme adopted by the workflow engine system is as follows:
the system comprises a workflow engine server and a workflow engine client; the workflow engine server comprises a workflow engine external interaction module, a workflow engine UI control layer, a workflow engine core module, a physical layer and a data persistence layer; the workflow engine external interaction module comprises a Web UI layer and a workflow WebService service layer, and the Web UI layer comprises a workflow engine basic information management module and a workflow engine flow management module; the workflow engine core module comprises an event handler, an application system WebService management module, a workflow engine WebService management module, a rule engine management module, a message pushing management module, an exception handling module and a parameter handling mechanism management module; the entity layer comprises a database entity, a workflow entity and a common entity for the common use of the workflow engine and the application system; the data persistence layer comprises a workflow engine business processing layer, a database access layer, a data persistence layer adapter and a data layer interface; the workflow engine client comprises a workflow engine WebService access object management module, an application system WebService callback service management module, a workflow engine service request management module, a callback processing factory and a callback agent control management module.
In the process of flow creation, the Web UI layer configures basic information and transmits the basic information to the data persistence layer through the workflow engine UI control layer to be stored in a database, when a business flow is initiated, the workflow WebService service layer receives a request for flow creation and transmits the request information to the workflow engine core module, the workflow engine core module creates a flow instance and transmits information of a person to be handled of the flow to the workflow engine WebService management module, the workflow engine WebService management module transmits the information to a callback processing factory through the application system WebService callback service management module, and the callback processing factory analyzes the data and transmits the data to the business processing method of the application program.
The database access layer comprises a MySql database access layer, a SqlServer database access layer and an Oracle database access layer. The callback processing factory comprises a general callback module and a user-defined callback module.
The workflow engine client also comprises a service information packaging factory and a workflow engine common entity class layer; the service information packaging factory, the workflow engine public entity class layer and the callback agent control management module are respectively connected with the workflow engine service request management module and the callback processing factory through the data processing layer.
The invention relates to a cross-platform and cross-application flow propulsion method of a workflow engine system, which comprises the following steps:
and 3, creating a flow instance by an application system according to the flow template, retrieving task nodes or gateways needing to be activated by the workflow engine according to the inlet route, and judging the types of flow elements by the flow element controller to activate the task nodes, the gateways or end nodes, wherein the flow elements refer to different types of nodes and gateways in the flow.
The flow elements in the step 3 comprise an approval node, an operation node, a countersigning node, an automatic node, a concurrent branch gateway, a concurrent convergence gateway, an exclusive branch gateway and an exclusive convergence gateway; the flow elements are added during the design phase of the flow template.
if the gateway element is the gateway element, distributing the gateway element to different types of gateway processors for processing according to the gateway type; if the gateway contains the rule statement, the rule statement is processed by a rule engine, then the downstream flow element is found according to the routing information obtained after calculation and is sent to a flow element controller for processing, and a processing cycle is completed;
if the task node is the task node, the task node is distributed to a corresponding node processor, the node processor judges a task stage configured by the node to judge an application system, a process type and a service stage to which the task node belongs, and after the task node is processed, a downstream process element is found according to an outflow route and is delivered to a process element controller for processing, and a processing cycle is completed again;
if the node is finished, executing a flow finishing transaction, closing all activated nodes and tasks to be handled, modifying the flow state to be finished, and pushing a flow finished message to all application systems related to the flow.
Compared with the prior art, the invention has the following beneficial effects: the application system reserves a WebService access interface in the workflow engine configuration information for receiving the process information sent by the workflow engine, thereby realizing the simultaneous service of a plurality of applications on a single deployed workflow engine server. The purpose of cross-platform application of the workflow engine is realized by means of the cross-platform characteristic of the WebService service. The method has the advantages that the simple information of the application system and the relevant information of the process are configured, the business part related to the process in each application is integrated into a workflow engine system, the information is controlled in a unified mode, different process businesses of a plurality of applications are connected in series in the same process through visual process design, and barriers among different application business processes are broken. In addition, after single release, source codes cannot be modified or configuration information influencing the use of the previous application cannot be modified due to the addition of the subsequent application, and the purpose of unidirectional and complete decoupling of the workflow engine system to other application systems is achieved.
Compared with the prior art, the cross-platform and cross-application flow propelling method adds a system unique identifier, a flow type unique identifier and a flow stage unique identifier, namely 'MARK element', in an information configuration process, wherein the MARK element is a unique identifier manually set for each business key node by a user in a workflow engine designer, the uniqueness of the MARK element is verified by a workflow engine, the workflow engine transmits the unique identifiers to an application system in the process of propelling the flow, and the application system can judge the unique identifiers set by the application system and then execute preset business processing logic. The addition of the 'MARK element' plays a very large role in the flow main information, the task node and the gateway configuration of the workflow engine for unidirectional decoupling, the parameter element is similar to the 'MARK element' and is variable information which is set by an application system in the design stage of the workflow engine, the uniqueness of the variable information is verified by the workflow engine, the values of the set parameters are required to be attached when the application system submits a receipt processing request to the workflow engine, the workflow engine acquires the parameter values, and the parameter values are replaced into the places where the parameters are set in a flow advancing logic code, so that the application system can change the flow direction of the flow by using information generated by business processing in some judgment logics of the flow. The flow advancing method of the invention completely realizes the configuration and the execution of the work flow of the cross-application system, enables a plurality of application systems (informatization management systems) in the same company to realize the cooperation, greatly improves the business processing efficiency of the cross-application system, reduces the information confusion and the lag possibly caused by links of off-line and manual participation, and breaks the cooperation barrier between the application systems on the basis of breaking information isolated islands and department barriers.
Drawings
FIG. 1 is a network topology diagram of the workflow engine system of the present invention;
FIG. 2 is a block diagram of a workflow engine server according to the present invention;
FIG. 3 is a block diagram of a workflow engine client of the present invention;
FIG. 4 is an information interaction diagram of the workflow engine system of the present invention;
FIG. 5 is a flow chart of a flow advancing method of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings.
Referring to fig. 1, the deployment of the workflow engine system of the present invention has no special requirement, and may be deployed on the same server as other application systems, or may be deployed on a dedicated server separately.
Referring to fig. 2-3, the workflow engine system of the present invention includes a workflow engine server and a workflow engine client; the workflow engine server comprises a workflow engine external interaction module 1, a workflow engine UI control layer 2, a workflow engine core module 3, a physical layer 4 and a data persistence layer 5; the workflow engine external interaction module 1 comprises a Web UI layer and a workflow WebService service layer, wherein the Web UI layer comprises a workflow engine basic information management module and a workflow engine flow management module; the workflow engine core module 3 comprises an event handler, an application system WebService management module, a workflow engine WebService management module, a rule engine management module, a message pushing management module, an exception handling module and a parameter handling mechanism management module; the entity layer 4 comprises a database entity, a workflow entity and a common entity for the common use of the workflow engine and the application system; the data persistence layer 5 comprises a workflow engine business processing layer, a database access layer, a data persistence layer adapter and a data layer interface; the database access layer comprises a MySql database access layer, a SqlServer database access layer and an Oracle database access layer. The workflow engine client comprises a workflow engine WebService access object management module 6, an application system WebService callback service management module 7, a workflow engine service request management module 8, a callback processing factory 9 and a callback agent control management module 10. The callback processing factory 9 includes a general callback module and a user-defined callback module. The workflow engine client further comprises a service information packaging factory 12 and a workflow engine common entity class layer 13, wherein the service information packaging factory 12, the workflow engine common entity class layer 13 and the callback proxy control management module 10 are respectively connected with the workflow engine service request management module 8 and the callback processing factory 9 through a data processing layer 11.
Referring to fig. 4, the information interaction process of the workflow engine system of the present invention is as follows:
(1) firstly, configuring basic information on a Web UI layer (a workflow engine background management website), wherein the basic information comprises: application system information, process type service phase information, and the like; then drawing the flow chart of different flow types. And the information is delivered to a data persistence layer through a workflow engine UI control layer and is stored in a database.
(2) The application system initiates a business process, calls a process initiation interface of a workflow engine client tool, and the interface calls a workflow WebService service layer interface of a workflow engine end and sends a request for creating the process (accompanied by information such as process type, creator, process title and the like) to the workflow engine.
(3) After receiving the flow creation request, the workflow engine WebService service layer transmits the request information to the workflow engine core module, creates a flow instance according to the flow diagram configured in the step (1), transmits the flow data information to the data persistence layer to be stored in the database, and transmits the information of the person to be handled in the first task node to the application system WebService management module.
(4) The application system WebService management module packages the received information of the to-be-handled person (information of adding message types such as to-be-handled messages and flow result messages) and transmits the information to the workflow engine client tool by calling the application system WebService callback management module, and the tool analyzes data in a callback processing factory and transmits the data to a service processing method of an application program.
(5) The execution process of the process approval and the like is similar to the execution process of the process creation task.
Referring to fig. 5, the cross-platform and cross-application flow propulsion method of the present invention includes the following steps:
1. before the process engine is used, necessary information needs to be configured on a management page of the workflow engine:
(1) configuration of information of an application system (an application system using a workflow engine), including a system name, a system MARK (unique identifier), a callback WebService URL address, and the like;
(2) configuring information of flow types (such as leave-asking flow and overtime flow), wherein the information comprises an application system, a flow type MARK (unique identifier), a type name and the like;
(3) and the information configuration of the process stages (such as a form filling stage, an approval stage and a deposit stage) comprises the type of the process to which the process belongs, the application system to which the process belongs, a stage MARK (unique identifier), a stage name and the like.
In order to decouple the application system and the workflow engine from the business, a MARK element is added, wherein the MARK element is a unique identifier (the uniqueness is verified by the workflow engine) which is automatically set (manually input) for each business key node by a user in a workflow engine designer, the workflow engine transmits the unique identifiers to the application system in the process of advancing the process, and the application system can judge the unique identifiers set by the application system and then execute preset business processing logic. The addition of the 'MARK element' plays a great role in unidirectional decoupling of the service-oriented and cross-application workflow engine.
2. Key points in the process template design stage:
(1) each task node must belong to a process stage under the process type, which service stage of which application system the task node belongs to is determined at all times, and a service processing mode can be determined according to the MARK identification;
(2) the process main information, the task nodes and the gateway are provided with 'parameter elements', key parameter information can be freely added, and key data can be conveniently shared among different task stages and different application systems. The "parameter element" is similar to the "MARK element", and is variable information (uniqueness is checked by the workflow engine) set by the application system itself in the workflow engine design stage, when the application system submits a document processing request to the workflow engine, the values of the set parameters need to be attached, the workflow engine acquires the parameter values, and the parameter values are replaced into the place where the parameters are set in the process advancing logic code, so that the application system can change the flow direction of the process by using information generated in the business processing process in some judgment logics of the process.
3. The business process advances the process across application systems: an application system creates a flow instance according to a flow template, a workflow engine retrieves task nodes or gateways needing to be activated according to an entry route, and a flow element controller judges the types of flow elements to activate the task nodes, the gateways or end nodes. "flow element" refers to different types of nodes and gateways in the flow, such as: the method comprises the following steps of examining and approving nodes, operating nodes, countersigning nodes, automatic nodes, concurrent branch gateways, concurrent convergence gateways, exclusive branch gateways and exclusive convergence gateways, wherein the elements are added in the process design stage.
If the gateway element is the gateway element, the gateway element is handed to a gateway controller for processing, the gateway controller distributes the gateway element to different types of gateway processors for processing according to gateway types (exclusive branch, exclusive convergence, concurrent branch and concurrent convergence), if the gateway contains a rule statement, the rule statement is handed to a rule engine for processing, then a downstream flow element is found according to the calculated routing information and handed to a flow element controller for processing, and a processing cycle is completed.
If the task node is a task node, the task node is handed to a task node controller, the controller distributes the node to a corresponding node processor according to the node type (operation, approval, countersigning, automatic node and the like), the node processor judges the task stage configured by the node to judge which business stage of which flow type of which application system the task node belongs to (the "business stage" is a business key stage mark set for the corresponding flow type, and is configured in a workflow engine by the application system to mark which stage of the whole business the certain flow node belongs to, such as a delivery stage, a transportation stage and a signing stage, and the "flow type" is configured in corresponding application system information, so that the "business stage" can be judged to belong to which flow type and which application system according to the "business stage" information), and then the task to be handled is pushed to the corresponding application system, and the application system distributes the information to corresponding to-do task handlers according to the pushed to-do task information. After the task node is processed by the appointed executor, finding out the downstream flow elements according to the outflow route and delivering the downstream flow elements to the flow element controller for processing, and completing a processing cycle again.
If the node is the end node, executing the flow end transaction, closing all activated nodes and tasks to be handled, modifying the flow state to be end, and pushing a flow end message to all application systems related to the flow.
The invention well realizes the unidirectional complete decoupling of the workflow engine to the application system, and the addition of various self-defined parameters and MARK identification elements, so that the workflow engine is very freely and changeably used. The service-oriented cross-platform workflow engine can serve a plurality of application systems only by single deployment, and the most important point is that cross-application system configuration and execution workflow are completely realized, so that a plurality of application systems (information management systems) in the same company can realize cooperation, the service processing efficiency of the cross-application system is greatly improved, and information confusion and delay possibly caused by offline and manual participation links are reduced. And the cooperation barrier between the application systems is broken on the basis of breaking information islands and department barriers.
Claims (7)
1. A workflow engine system, characterized by: the system comprises a workflow engine server and a workflow engine client; the workflow engine server comprises a workflow engine external interaction module (1), a workflow engine UI control layer (2), a workflow engine core module (3), a physical layer (4) and a data persistence layer (5); the workflow engine external interaction module (1) comprises a Web UI layer and a workflow WebService service layer, wherein the Web UI layer comprises a workflow engine basic information management module and a workflow engine process management module; the workflow engine core module (3) comprises an event handler, an application system WebService management module, a workflow engine WebService management module, a rule engine management module, a message pushing management module, an exception handling module and a parameter handling mechanism management module; the entity layer (4) comprises a database entity, a workflow entity and a common entity for the common use of the workflow engine and the application system; the data persistence layer (5) comprises a workflow engine business processing layer, a database access layer, a data persistence layer adapter and a data layer interface; the workflow engine client comprises a workflow engine WebService access object management module (6), an application system WebService callback service management module (7), a workflow engine service request management module (8), a callback processing factory (9) and a callback agent control management module (10);
in the process of flow creation, the Web UI layer configures basic information and transmits the basic information to the data persistence layer (5) through the workflow engine UI control layer (2) to be stored in a database, when a service flow is initiated, the workflow WebService service layer receives a request for flow creation and transmits the request information to the workflow engine core module (3), the workflow engine core module (3) creates a flow instance and transmits information of a person to be handled of the flow to the workflow engine WebService management module, the workflow engine WebService management module transmits the information to the callback processing factory (9) through the application system WebService callback service management module (7), and the callback processing factory (9) transmits the data to the service processing method of the application program after analyzing the data.
2. The workflow engine system of claim 1 wherein: the database access layer comprises a MySql database access layer, a SqlServer database access layer and an Oracle database access layer.
3. The workflow engine system of claim 1 wherein: the callback processing factory (9) comprises a general callback module and a user-defined callback module.
4. The workflow engine system of claim 1 wherein: the workflow engine client also comprises a service information packaging factory (12) and a workflow engine common entity class layer (13); the service information packaging factory (12), the workflow engine public entity class layer (13) and the callback agent control management module (10) are respectively connected with the workflow engine service request management module (8) and the callback processing factory (9) through a data processing layer (11).
5. A cross-platform, cross-application flow-advancing method based on the workflow engine system of any one of claims 1 to 4, characterized by comprising the following steps:
step 1, configuring information of a workflow engine basic information management module and a workflow engine process management module, configuring information of an application system and information of process types respectively by process stage information, adding a system unique identifier, a process type unique identifier and a process stage unique identifier in an information configuration process, and verifying uniqueness by a workflow engine;
step 2, designing a flow template to enable each task node to belong to a flow stage under the flow type, and allocating parameter elements for flow main information, the task nodes and the gateway, wherein the parameter information of the parameter elements can be freely added;
and 3, creating a flow instance by an application system according to the flow template, retrieving task nodes or gateways needing to be activated by the workflow engine according to the inlet route, and judging the types of flow elements by the flow element controller to activate the task nodes, the gateways or end nodes, wherein the flow elements refer to different types of nodes and gateways in the flow.
6. The cross-platform, cross-application flow-advancing method of claim 5, characterized in that: the flow elements in the step 3 comprise an approval node, an operation node, a countersigning node, an automatic node, a concurrent branch gateway, a concurrent convergence gateway, an exclusive branch gateway and an exclusive convergence gateway; the flow elements are added during the design phase of the flow template.
7. The cross-platform and cross-application flow advancing method according to claim 5, wherein the specific steps of activating the task node, the gateway or the end node in step 3 are as follows:
if the gateway element is the gateway element, distributing the gateway element to different types of gateway processors for processing according to the gateway type; if the gateway contains the rule statement, the rule statement is processed by a rule engine, then the downstream flow element is found according to the routing information obtained after calculation and is sent to a flow element controller for processing, and a processing cycle is completed;
if the task node is the task node, the task node is distributed to a corresponding node processor, the node processor judges a task stage configured by the node to judge an application system, a process type and a service stage to which the task node belongs, and after the task node is processed, a downstream process element is found according to an outflow route and is delivered to a process element controller for processing, and a processing cycle is completed again;
if the node is finished, executing a flow finishing transaction, closing all activated nodes and tasks to be handled, modifying the flow state to be finished, and pushing a flow finished message to all application systems related to the flow.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810138600.2A CN108305010B (en) | 2018-02-10 | 2018-02-10 | Workflow engine system and cross-platform and cross-application flow propelling method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810138600.2A CN108305010B (en) | 2018-02-10 | 2018-02-10 | Workflow engine system and cross-platform and cross-application flow propelling method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108305010A CN108305010A (en) | 2018-07-20 |
| CN108305010B true CN108305010B (en) | 2021-07-20 |
Family
ID=62864872
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810138600.2A Active CN108305010B (en) | 2018-02-10 | 2018-02-10 | Workflow engine system and cross-platform and cross-application flow propelling method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108305010B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109064136A (en) * | 2018-08-01 | 2018-12-21 | 北京奇虎科技有限公司 | The management method and device of product treatment process calculate equipment, storage medium |
| EP3640868A1 (en) * | 2018-10-17 | 2020-04-22 | Siemens Aktiengesellschaft | Method of and system for enacting a business process in an event-driven environment |
| CN110097255A (en) * | 2019-04-08 | 2019-08-06 | 中通服创发科技有限责任公司 | A kind of coordination management system based on workflow engine |
| CN110298630A (en) * | 2019-06-27 | 2019-10-01 | 南京冰鉴信息科技有限公司 | A kind of workflow engine |
| CN110390496B (en) * | 2019-09-18 | 2021-03-09 | 浙江华云信息科技有限公司 | Workflow design method suitable for complex and changeable services and organizations |
| CN110717656A (en) * | 2019-09-18 | 2020-01-21 | 武汉空心科技有限公司 | Work platform workflow construction system and construction method |
| JP7317659B2 (en) * | 2019-10-09 | 2023-07-31 | 株式会社日立製作所 | Computer system and cooperative control method |
| CN110942372B (en) * | 2019-11-21 | 2023-05-12 | 杭州涂鸦信息技术有限公司 | Butt joint method and gateway of business end and ERP system |
| CN110969414A (en) * | 2019-11-27 | 2020-04-07 | 中国地质大学（武汉） | Cross-platform workflow implementation method and system based on Java |
| CN111667239B (en) * | 2020-05-27 | 2023-04-18 | 山东建筑大学 | Workflow implementation method based on breadth traversal and stiff branch removal |
| CN111724144B (en) * | 2020-07-17 | 2022-06-28 | 江苏苏宁银行股份有限公司 | Bank transaction workflow engine system |
| CN112465448B (en) * | 2020-11-11 | 2023-07-07 | 中国人民大学 | Cross-organization workflow operation method and system based on blockchain |
| CN112596865A (en) * | 2020-12-22 | 2021-04-02 | 航天信息股份有限公司企业服务分公司 | System for pushing to-do message based on workflow affair |
| CN112950348B (en) * | 2021-02-05 | 2023-02-28 | 中国建设银行股份有限公司 | Flexible model assembling method and system based on main engine and sub engine |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102592198A (en) * | 2011-12-30 | 2012-07-18 | 福建富士通信息软件有限公司 | Workflow engine supporting combined service |
| CN105183441A (en) * | 2015-05-22 | 2015-12-23 | 京华信息科技股份有限公司 | Workflow management system realized by microkernel architecture |
| CN105868962A (en) * | 2016-03-27 | 2016-08-17 | 郭玥瑶 | Intelligent product specification management system based on Internet |
| CN107133024A (en) * | 2016-02-29 | 2017-09-05 | 北京广联达正源兴邦科技有限公司 | Business management system based on OSGI frameworks |
| CN107193545A (en) * | 2017-04-07 | 2017-09-22 | 广东省科技基础条件平台中心 | Multilingual co-development device, the method and system of a kind of component-oriented |
-
2018
- 2018-02-10 CN CN201810138600.2A patent/CN108305010B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102592198A (en) * | 2011-12-30 | 2012-07-18 | 福建富士通信息软件有限公司 | Workflow engine supporting combined service |
| CN105183441A (en) * | 2015-05-22 | 2015-12-23 | 京华信息科技股份有限公司 | Workflow management system realized by microkernel architecture |
| CN107133024A (en) * | 2016-02-29 | 2017-09-05 | 北京广联达正源兴邦科技有限公司 | Business management system based on OSGI frameworks |
| CN105868962A (en) * | 2016-03-27 | 2016-08-17 | 郭玥瑶 | Intelligent product specification management system based on Internet |
| CN107193545A (en) * | 2017-04-07 | 2017-09-22 | 广东省科技基础条件平台中心 | Multilingual co-development device, the method and system of a kind of component-oriented |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108305010A (en) | 2018-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108305010B (en) | Workflow engine system and cross-platform and cross-application flow propelling method thereof | |
| CN101207838B (en) | Message forwarding based on sender and recipient relationship | |
| JPS63239552A (en) | Apparatus for dispersing data processing over a plurality of control positions | |
| CN105893055B (en) | Flow engine hardware and software platform triggering method | |
| CN103780686A (en) | Method and system for customizing application approval procedure in cloud organization | |
| CN101650804A (en) | Method for managing process of third generation mobile communication operating and maintaining system | |
| CN107203421A (en) | A kind of adaptive work in combination stream method in cloud computing environment | |
| CN113947485A (en) | Block chain customizable system | |
| Pawar et al. | ETL based Billing System for Azure Services with Cost Estimation using Cloud Computing | |
| CN112527523A (en) | Distributed message transmission method and system for high-performance computing multiple clouds | |
| CN112688802B (en) | High-performance exchange middleware based on API gateway | |
| CN111104181A (en) | Webpage data filling system for visually editing task flow | |
| CN114066394A (en) | Implementation method of multi-tenant workflow engine and multi-tenant workflow engine system | |
| CN109586946B (en) | Exception handling method and device and computer readable storage medium | |
| CN112686580A (en) | Workflow definition method and system capable of customizing flow | |
| US20050278303A1 (en) | System and method for production planning utilizing on-line state-space planning | |
| CN110969414A (en) | Cross-platform workflow implementation method and system based on Java | |
| CN103971225A (en) | Workflow dynamic expanding method and system | |
| CN110298630A (en) | A kind of workflow engine | |
| CN115617480A (en) | Task scheduling method, device and system and storage medium | |
| CN1316408C (en) | Signaling events in workflow management systems | |
| CN100464303C (en) | Method of implementing distribution type operation logical calculation in structure software system | |
| CN114116467A (en) | Processing method and system for visual management of data service interface | |
| CN111222793A (en) | Data interaction method and system | |
| CN103679432A (en) | A VNMS system supporting a dynamic structured application platform |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |