CN115292022B - Workflow engine system, implementation method, storage medium and computer equipment - Google Patents
Workflow engine system, implementation method, storage medium and computer equipment Download PDFInfo
- Publication number
- CN115292022B CN115292022B CN202211194978.7A CN202211194978A CN115292022B CN 115292022 B CN115292022 B CN 115292022B CN 202211194978 A CN202211194978 A CN 202211194978A CN 115292022 B CN115292022 B CN 115292022B
- Authority
- CN
- China
- Prior art keywords
- workflow
- engine
- form structure
- unit
- structure data
- 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
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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
Abstract
The invention provides a workflow engine system, an implementation method, a storage medium and computer equipment, wherein the system comprises: the system comprises a plurality of independently deployed engine service terminals, a plurality of workflow servers and a plurality of workflow servers, wherein the engine service terminals are used for executing automatic creation of form structure data and integrating role information in the form structure data to create workflows; the client adapter is used for calling a service interface of the workflow provided by the engine server and waiting for the engine server to feed back a calling result; the registry is used for distributing the workflow to the client-side adapter according to a preset load strategy and a circulation request; in the workflow engine system, when a workflow is circulated, if a trigger event and a path condition judgment exist, a corresponding business application is informed to execute a corresponding event according to an application identifier bound when the workflow is created, and whether the workflow continues to be circulated or not is determined according to an execution result. The technical problem that the management efficiency of the workflow engine management system is reduced can be solved.
Description
Technical Field
The present invention relates to the field of process management technologies, and in particular, to a workflow engine system, an implementation method, a storage medium, and a computer device.
Background
The workflow engine is a software system, is an important component in the workflow system, and mainly completes the routing control of a process instance, namely the circulation of tasks involved in the process.
The existing workflow engine is usually highly coupled with a business system, and runs in the business system using the workflow engine in the form of a software component, and the workflow technology mainly solves the problems of flexible customization and convenient change of a complex business process, so that the workflow engine can also be regarded as a part of a business logic layer on an application logic level and cannot be stripped from businesses.
Under the application of the micro-service architecture, a complex service is usually split into a plurality of sub-services, each service uses its own workflow engine to process the service, and the processes of different services cannot be managed in a centralized manner, which finally results in the reduction of management efficiency.
Disclosure of Invention
Based on this, the present invention provides a workflow engine system, an implementation method, a storage medium and a computer device, and aims to solve the technical problem in the prior art that a plurality of sub-services use their own workflow engine to process services under the application of a micro-service architecture, which results in a reduction in management efficiency.
A first aspect of the present invention provides a workflow engine system comprising:
the system comprises a plurality of independently deployed engine service sides, a plurality of independent deployed engine service sides and a plurality of workflow processing servers, wherein each engine service side is used for automatically creating form structure data and integrating role information in the form structure data to create a workflow;
the client adapter is used for calling a service interface of the workflow provided by the engine service end and waiting for the engine service end to feed back a calling result;
the registry is used for distributing the workflow to the client-side adapter according to a preset load strategy and a flow request;
in the workflow engine system, when the workflow is circulated, if a trigger event and a path condition judgment exist, a corresponding business application is informed to execute a corresponding event according to an application identifier bound when the workflow is created, and whether the workflow continues to be circulated is determined according to an execution result.
According to one aspect of the above technical solution, the engine server includes a metadata management unit, a role configuration unit, and a model management unit; wherein
The metadata management unit is used for automatically creating form structure data and updating the version of the form structure data after the form structure data is created;
the role configuration unit is used for acquiring organization personnel and role information and integrating the organization personnel and the role information into the form structure data;
the model management unit is used for designing and configuring the workflow through a graphic designer and issuing a model as a workflow definition to create the workflow.
According to one aspect of the above technical solution, the client adapter includes a service invocation unit and a feedback data management unit; wherein
The service calling unit is used for calling a service interface of a workflow provided by the engine service end so as to establish communication connection between a client and the engine service end;
the feedback data management unit is used for acquiring a service calling result and a communication connection result between the client adapter and the engine server.
According to one aspect of the above technical solution, the registry includes a flow request receiving unit and a workflow distributing unit; wherein
The flow request receiving unit is used for acquiring a flow request sent by the client and distributing the workflow through the workflow distributing unit based on a preset load strategy.
According to an aspect of the foregoing technical solution, the workflow engine system further includes a flow event triggering unit, specifically configured to:
judging whether a trigger event exists or not and judging a path condition in the circulation process of the workflow;
if yes, notifying the corresponding business application to execute the corresponding event according to the application identifier bound when the workflow is created, and determining whether the workflow continues to circulate according to an execution result.
According to an aspect of the above technical solution, in the workflow engine system:
after the whole flow circulation is completed, inquiring the information of the current workflow to be dealt with, and returning the inquiry result to the client;
and after the client application receives the result, writing the result data back into the database of the service connection for joint check of the subsequent application data and the information to be handled.
The second aspect of the present invention provides a method for implementing a workflow engine system, the method comprising:
creating form structure data through an engine server, and integrating role information in the form structure data to create a workflow;
calling a service interface of the workflow provided by the engine server through a client adapter, and acquiring a calling result of the service interface;
based on the registry, distributing the workflow to the client-side adapter according to a preset load strategy and a circulation request;
judging whether a trigger event exists or not and judging the path condition when the workflow flows;
if yes, notifying the corresponding business application to execute the corresponding event according to the application identifier bound when the workflow is created, and determining whether the workflow continues to circulate according to an execution result.
According to one aspect of the above technical solution, the step of creating the form structure data through the engine server and integrating the role information in the form structure data to create the workflow specifically includes:
executing automatic creation of form structure data through a preset metadata management unit, and updating the version of the form structure data after the form structure data is created;
acquiring organization personnel and role information through a preset role configuration unit, and integrating the organization personnel and the role information into the form structure data;
and designing and configuring the workflow based on a graphic designer through a preset model management unit, and publishing the model as a workflow definition to create the workflow.
A third aspect of the present invention is to provide a storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method of the above-mentioned solution.
A fourth aspect of the present invention is to provide a computer device, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method according to the above technical solution when executing the program.
Compared with the prior art, the workflow engine system, the implementation method, the storage medium and the computer equipment have the advantages that:
1) The table structure automatic creating and updating function can ensure the correctness of the table structure and data in the initial stage and the subsequent iteration updating of engine deployment, and is convenient for operation and maintenance personnel to manage;
2) The client and the engine server are separately deployed, so that the difficulty of use under a micro-service architecture can be reduced, the invasion to business application is small, and the workload brought by integration is reduced;
3) The integrated role information in the invention can be quickly accessed to different third party organization personnel structures on the premise of not modifying the program, thereby reducing the development workload brought by the adapter personnel.
Drawings
Fig. 1 is a block diagram showing a configuration of a workflow engine system according to a first embodiment of the present invention;
FIG. 2 is a flow chart of a method for implementing the workflow engine system according to the second embodiment of the present invention;
the following detailed description will further illustrate the invention in conjunction with the above-described figures.
Detailed Description
To facilitate an understanding of the invention, the invention will now be described more fully with reference to the accompanying drawings. Several embodiments of the invention are presented in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
Example one
Referring to fig. 1, a first embodiment of the present invention provides a workflow engine system, including: a plurality of independently deployed engine servers 10, client adapters 20, registries 30. The workflow engine system is developed based on standard BPMN2.0 specifications, and can be compatible with other workflow model files generated based on the specifications to be directly imported and used.
The workflow engine system shown in this embodiment mainly provides distributed workflow services for business applications in the form of micro services, so that business processing logic and business logic are decoupled, and unified management of business processes accessed to the engine is realized through the model management unit and the instance management unit, thereby really solving the problem that management is difficult when process data is scattered in each business service under the current micro service architecture, improving the operation efficiency of the business processes, and ensuring service availability by distributed deployment.
In this embodiment, each engine service 10 is configured to perform automatic creation of form structure data, and integrate role information in the form structure data to create a workflow.
Each engine server 10 is provided with a metadata management unit, a role configuration unit and a model management unit. The metadata management unit is used for automatically creating form structure data and updating the version of the form structure data after the form structure data is created; the role configuration unit is used for acquiring organization personnel and role information and integrating the organization personnel and the role information into the form structure data; the model management unit is used for designing and configuring the workflow through a graphic designer and publishing a model as a workflow definition to create the workflow.
Specifically, the metadata management unit is configured to automatically detect a connected database type and a metadata version during an engine starting process, automatically perform table building and data initialization operations according to the detected database type if a table structure required by the workflow engine does not exist in a data source, and automatically update the table structure if the detected versions are inconsistent.
Further, the role configuration unit is used for configuring organization, personnel and role information used in the workflow engine by using files, and inquiring a database or calling an external interface to obtain the information.
Furthermore, the model management unit is used for managing all the model information of the business process accessed to the workflow engine, and then combining and configuring the process elements by using a graphic designer to finally form a model file to be embodied in the model management unit.
In this embodiment, the client adapter 20 is configured to invoke a service interface of the workflow provided by the engine server 10, and it is integrated into a business application that needs to use the workflow in the form of a plug-in, provide an interface needed by operating the workflow to the business application through the adapter, and wait for the engine server 10 to feed back a call result.
Specifically, the client adapter 20 includes a service call unit and a feedback data management unit. The service calling unit is used for calling a service interface of a workflow provided by the engine service end 10 so as to establish communication connection between a client and the engine service end 10; the feedback data management unit is configured to obtain a service call result and a communication connection result between the client adapter and the engine server 10.
In this embodiment, the registry 30 is configured to distribute the workflow to the client adapters according to a preset load policy and a flow request.
Specifically, the registry 30 includes a flow request receiving unit and a workflow distributing unit; the flow request receiving unit is configured to obtain a flow request sent by the client, and distribute the workflow through the workflow distributing unit based on a preset load policy.
In this embodiment, in the workflow engine system, in the process of flowing the workflow, if a trigger event and a path condition judgment exist, notifying a corresponding service application to execute a corresponding event according to an application identifier bound when the workflow is created, and determining whether the workflow continues to flow according to an execution result.
Specifically, the workflow engine further comprises a flow event triggering unit, different types of events can be triggered before and after a specific operation in the workflow circulation process, a client is informed of executing the events and returning an execution result in a remote calling mode, and the event triggering unit executes subsequent circulation operation according to the feedback result.
The engine server 10 further includes a flow decision unit, which notifies the service application to execute a corresponding condition and returns to execute the corresponding condition, and the flow decision unit may determine whether to continue to execute the flow operation according to a return result.
In some embodiments of the present invention, the engine server 10 further includes a flow log recording unit, which is capable of recording a flow event, a flow type, an operator, an operation time, and an operation content in the workflow flow.
In some embodiments of the present invention, after the whole flow is completed, the information of the workflow to be dealt with currently is queried, and a query result is returned to the client;
and after the client application receives the result, writing the result data back into the database of the service connection for joint check of the subsequent application data and the information to be handled.
Compared with the prior art, the workflow engine system shown in the embodiment has the advantages that:
1) The table structure automatic creation and updating function in the embodiment can ensure the correctness of the table structure and data in the initial stage and the subsequent iteration updating of engine deployment, and is convenient for operation and maintenance personnel to manage;
2) The client and the engine server in the embodiment are separately deployed, so that the difficulty in use under a micro-service architecture can be reduced, the intrusion on service application is small, and the workload caused by integration is reduced;
3) The integrated role information in the embodiment can be quickly accessed to different third-party organization personnel structures on the premise of not modifying the program, and the development workload brought by adaptation personnel is reduced.
Example two
Referring to fig. 2, a second embodiment of the present invention provides a method for implementing a workflow engine system, where the method includes steps S01 to S05:
and S01, creating form structure data through an engine server, and integrating role information in the form structure data to create a workflow.
Each engine server is provided with a metadata management unit, a role configuration unit and a model management unit. The metadata management unit is used for automatically creating form structure data and updating the version of the form structure data after the form structure data is created; the role configuration unit is used for acquiring organization personnel and role information and integrating the organization personnel and the role information into the form structure data; the model management unit is used for designing and configuring the workflow through a graphic designer and publishing a model as a workflow definition to create the workflow.
Specifically, the metadata management unit is used for automatically detecting the type and the version of the connected database in the process of starting the engine, automatically performing table building and data initialization operations according to the detected type of the database if a table structure required by the workflow engine does not exist in a data source, and automatically updating the table structure if the detected versions are inconsistent.
Further, the role configuration unit is used for configuring organization, personnel and role information used in the workflow engine by using files, and inquiring a database or calling an external interface to obtain the information.
Furthermore, the model management unit is used for managing model information of all business processes accessed to the workflow engine, and then combining and configuring the process elements by using a graphic designer to finally form a model file to be embodied in the model management unit.
Step S02, calling a service interface of the workflow provided by the engine server through a client adapter, and acquiring a calling result of the service interface;
specifically, the client adapter includes a service invocation unit and a feedback data management unit. The service calling unit is used for calling a service interface of a workflow provided by the engine service end so as to establish communication connection between a client and the engine service end; the feedback data management unit is used for acquiring a service calling result and a communication connection result between the client adapter and the engine server.
Step S03, based on the registry, distributing the workflow to the client adapter according to a preset load strategy and a flow request;
specifically, the registry comprises a circulation request receiving unit and a workflow distributing unit;
the flow request receiving unit is configured to obtain a flow request sent by the client, and distribute the workflow through the workflow distributing unit based on a preset load policy.
Step S04, judging whether a trigger event exists or not and judging a path condition when the workflow flows;
if yes, the method of the present embodiment proceeds to step S05.
And step S05, notifying corresponding business applications to execute corresponding events according to the bound application identifiers when the workflow is created, and determining whether the workflow continues to circulate according to an execution result.
Specifically, the workflow engine further comprises a flow event triggering unit, different types of events can be triggered before and after a specific operation in the workflow circulation process, a client is informed of executing the events and returning an execution result in a remote calling mode, and the event triggering unit executes subsequent circulation operation according to the feedback result.
In this embodiment, the creating, by an engine server, form structure data, and integrating role information in the form structure data to create a workflow step specifically includes:
the method comprises the steps that automatic creation of form structure data is executed through a preset metadata management unit, and version updating is conducted on the form structure data after the form structure data are created;
acquiring organization personnel and role information through a preset role configuration unit, and integrating the organization personnel and the role information into the form structure data;
and designing and configuring the workflow based on a graphic designer through a preset model management unit, and publishing the model as a workflow definition to create the workflow.
Compared with the prior art, the implementation method of the workflow engine system disclosed by the embodiment has the beneficial effects that:
1) The table structure automatic creation and updating function in the embodiment can ensure the correctness of the table structure and data in the initial stage and subsequent iteration updating of engine deployment, and is convenient for operation and maintenance personnel to manage;
2) The client and the engine server in the embodiment are separately deployed, so that the difficulty in use under a micro-service architecture can be reduced, the intrusion on service application is small, and the workload caused by integration is reduced;
3) The integrated role information in the embodiment can be quickly accessed to different third-party organization personnel structures on the premise of not modifying the program, and the development workload brought by adaptation personnel is reduced.
EXAMPLE III
A third embodiment of the present invention provides a storage medium, on which computer instructions are stored, and the instructions, when executed by a processor, implement the steps of the implementation method of the workflow engine system in the above-described embodiments.
Example four
A fourth embodiment of the invention provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of implementation of the workflow engine system when executing the program.
Those of skill in the art will understand that the logic and/or steps illustrated in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (7)
1. A workflow engine system, the workflow engine system comprising:
the system comprises a plurality of independently deployed engine service sides, a plurality of independent deployment engine service sides and a plurality of form configuration management server sides, wherein each engine service side is used for automatically creating form structure data and integrating role information in the form structure data so as to create a workflow;
the client adapter is used for calling the service interface of the workflow provided by the engine server and waiting for the feedback of a calling result by the engine server;
the registry is used for distributing the workflow to the client-side adapter according to a preset load strategy and a flow request;
in the workflow engine system, when the workflow is circulated, if a trigger event and a path condition judgment exist, notifying a corresponding service application to execute a corresponding event according to an application identifier bound when the workflow is created, and determining whether the workflow continues to be circulated according to an execution result;
the engine server comprises a process decision unit and a process log recording unit, wherein the process decision unit is used for informing the business application of executing corresponding conditions, returning to execute and judging whether to continue to execute the circulation operation according to a return result; the flow log recording unit is used for recording a flow event, a flow type, an operator, operation time and operation content in workflow flow;
the engine server side also comprises a metadata management unit, a role configuration unit and a model management unit;
the metadata management unit is used for automatically creating form structure data and updating the version of the form structure data after the form structure data is created;
the role configuration unit is used for acquiring organization personnel and role information and integrating the organization personnel and the role information into the form structure data;
the model management unit is used for designing and configuring the workflow through a graphic designer and publishing a model as a workflow definition to create the workflow.
2. The workflow engine system of claim 1, wherein the client adapter comprises a service invocation unit and a feedback data management unit; wherein
The service calling unit is used for calling a service interface of a workflow provided by the engine service end so as to establish communication connection between a client and the engine service end;
the feedback data management unit is used for acquiring a service calling result and a communication connection result between the client adapter and the engine server.
3. The workflow engine system according to claim 1, wherein the registry comprises a circulation request receiving unit and a workflow distributing unit; wherein
The flow request receiving unit is used for acquiring a flow request sent by the client and distributing the workflow through the workflow distributing unit based on a preset load strategy.
4. The workflow engine system of claim 1 wherein:
after the whole flow circulation is completed, inquiring the information of the current workflow to be dealt with, and returning the inquiry result to the client;
and after the client application receives the result, writing the result data back into the database of the service connection for joint check of the subsequent application data and the information to be handled.
5. A method for implementing a workflow engine system, the method comprising:
creating form structure data through an engine server, and integrating role information in the form structure data to create a workflow;
calling a service interface of the workflow provided by the engine server through a client adapter, and acquiring a calling result of the service interface;
based on the registry, distributing the workflow to the client-side adapter according to a preset load strategy and a circulation request;
judging whether a trigger event exists or not and judging the path condition when the workflow circulates;
if yes, notifying the corresponding business application to execute a corresponding event according to the application identifier bound when the workflow is created, and determining whether the workflow continues to circulate according to an execution result;
the engine server comprises a process decision unit and a process log recording unit, wherein the process decision unit is used for informing the business application of executing corresponding conditions, returning to execute and judging whether to continue to execute the circulation operation according to a return result; the flow log recording unit is used for recording a flow event, a flow type, an operator, operation time and operation content in workflow flow;
creating form structure data through an engine server side, and integrating role information in the form structure data to create a workflow, wherein the steps specifically comprise:
executing automatic creation of form structure data through a preset metadata management unit, and updating the version of the form structure data after the form structure data is created;
acquiring organization personnel and role information through a preset role configuration unit, and integrating the organization personnel and the role information into the form structure data;
and designing and configuring the workflow based on a graphic designer through a preset model management unit, and publishing the model as a workflow definition to create the workflow.
6. A storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method of claim 5.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method as claimed in claim 5 are implemented when the processor executes the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211194978.7A CN115292022B (en) | 2022-09-29 | 2022-09-29 | Workflow engine system, implementation method, storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211194978.7A CN115292022B (en) | 2022-09-29 | 2022-09-29 | Workflow engine system, implementation method, storage medium and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115292022A CN115292022A (en) | 2022-11-04 |
| CN115292022B true CN115292022B (en) | 2023-01-20 |
Family
ID=83834832
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211194978.7A Active CN115292022B (en) | 2022-09-29 | 2022-09-29 | Workflow engine system, implementation method, storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115292022B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115421824B (en) * | 2022-11-07 | 2023-05-02 | 北京领雁科技股份有限公司 | Micro-service execution engine, running method and application method |
| CN117634865A (en) * | 2024-01-25 | 2024-03-01 | 卓望数码技术（深圳）有限公司 | Workflow creation method, device, equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107316183A (en) * | 2017-07-06 | 2017-11-03 | 郑州云海信息技术有限公司 | Method and workflow engine that a kind of flow is created |
| CN113902393A (en) * | 2021-09-16 | 2022-01-07 | 中企云链（北京）金融信息服务有限公司 | Workflow engine approval system-based implementation method and system |
Family Cites Families (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003528358A (en) * | 1998-08-24 | 2003-09-24 | 富士通株式会社 | Workflow system and method |
| WO2001069431A2 (en) * | 2000-03-14 | 2001-09-20 | Commerceroute, Inc. | System and method for automating business processes and performing data interchange operations in a distributed computing environment |
| US7653566B2 (en) * | 2000-11-30 | 2010-01-26 | Handysoft Global Corporation | Systems and methods for automating a process of business decision making and workflow |
| CN101076793A (en) * | 2004-08-31 | 2007-11-21 | 国际商业机器公司 | System structure for enterprise data integrated system |
| US8543903B2 (en) * | 2008-01-14 | 2013-09-24 | International Business Machines Corporation | System and method of integrating a plurality of form related workflow tools |
| US20160232491A1 (en) * | 2015-02-09 | 2016-08-11 | Max Nalsky | Flexible workflow automation system |
| CN105046408A (en) * | 2015-06-25 | 2015-11-11 | 国网山东省电力公司 | Configurable workflow realization method and system |
| AU2017322337B2 (en) * | 2016-09-09 | 2022-08-18 | Dematic Corp. | Communication system for operation and management of workflows and integration of multiple devices utilizing different operating platforms |
| CN110717656A (en) * | 2019-09-18 | 2020-01-21 | 武汉空心科技有限公司 | Work platform workflow construction system and construction method |
| CN112311869B (en) * | 2020-10-28 | 2022-04-05 | 苏州万店掌网络科技有限公司 | Multi-type micro-service registration center management system and method |
| CN112286503A (en) * | 2020-10-28 | 2021-01-29 | 平安科技（深圳）有限公司 | Multi-registration center micro-service unified management method, device, equipment and medium |
| CN112465448B (en) * | 2020-11-11 | 2023-07-07 | 中国人民大学 | Cross-organization workflow operation method and system based on blockchain |
| CN112581080A (en) * | 2020-12-14 | 2021-03-30 | 南方电网海南数字电网研究院有限公司 | Lightweight distributed workflow engine construction system |
| CN114971506A (en) * | 2021-02-26 | 2022-08-30 | 中国移动通信集团广东有限公司 | System and method for separating process engine and business event processing |
| CN113094037B (en) * | 2021-04-20 | 2022-10-11 | 上海携宁计算机科技股份有限公司 | Interaction method, development platform, equipment and storage medium for forms and workflows |
| CN113722298A (en) * | 2021-09-15 | 2021-11-30 | 中国银行股份有限公司 | Workflow processing method, client, server and workflow engine |
| CN114493479A (en) * | 2021-12-17 | 2022-05-13 | 上海甄云信息科技有限公司 | Enterprise-level workflow engine implementation method and system based on micro-service SaaS |
| CN115204736A (en) * | 2022-08-03 | 2022-10-18 | 医利捷(上海)信息科技有限公司 | Business system and workflow engine interaction method and system |
-
2022
- 2022-09-29 CN CN202211194978.7A patent/CN115292022B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107316183A (en) * | 2017-07-06 | 2017-11-03 | 郑州云海信息技术有限公司 | Method and workflow engine that a kind of flow is created |
| CN113902393A (en) * | 2021-09-16 | 2022-01-07 | 中企云链（北京）金融信息服务有限公司 | Workflow engine approval system-based implementation method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115292022A (en) | 2022-11-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115292022B (en) | Workflow engine system, implementation method, storage medium and computer equipment | |
| US8626878B2 (en) | Techniques for establishing a connection with a message-oriented middleware provider, using information from a registry | |
| US7676538B2 (en) | Systems and methods for application view transactions | |
| EP1061446A2 (en) | Web-based enterprise management with multiple repository capability | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| US20020152277A1 (en) | System and method for agent reporting in to server | |
| EP1437657A2 (en) | System and method for management of software applications | |
| JP2013522769A (en) | Virtual machine image update service | |
| AU2007289177A1 (en) | Dynamically configuring, allocating and deploying computing systems | |
| US8365261B2 (en) | Implementing organization-specific policy during establishment of an autonomous connection between computer resources | |
| US8924947B2 (en) | Direct deployment of static content | |
| US20110258620A1 (en) | Method and Apparatus for Making a BPM Application Available to Multiple Tenants | |
| CN111858007A (en) | Task scheduling method and device based on message middleware | |
| US8239849B2 (en) | Class loading delegation network | |
| CN110098952A (en) | A kind of management method and device of server | |
| EP1782598B1 (en) | Dynamical reconfiguration of distributed composite state machines | |
| CN109684028A (en) | A kind of method, device and equipment that operating system is separated with user data | |
| CN109756557B (en) | User authority server and service method and system based on user authority | |
| CN108664343B (en) | State calling method and device for micro-service | |
| US11663349B2 (en) | System and method for managing data object creation | |
| CN114255016A (en) | Workflow system application method, system, computer and readable storage medium | |
| CN112256351B (en) | Method for realizing Feign component, method and device for calling micro-service | |
| CN111008064B (en) | Virtual machine resource scheduling method and device, and cluster deployment method and device | |
| US7007280B1 (en) | Schema driven management of a component-based application | |
| CN112418796B (en) | Sub-process task node activation method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |