CN117389528A - Service-oriented configurable workflow engine working method and device - Google Patents

Abstract

The invention relates to a service-oriented configurable workflow engine working method and equipment, which includes: creating a workflow; the workflow engine executes the workflow; during the execution process, the workflow engine calls external interface information according to the interface information configured by the process node. The business system receives the call results; the exception handler obtains the execution status information of each process node and handles exceptions.

Description

Service-oriented configurable workflow engine working method and equipment

Technical field

The invention relates to a service-oriented configurable workflow engine working method and equipment, and belongs to the field of workflow.

Background technique

Workflow is an abstract and general description of the workflow and the business rules between each operation step. Workflow modeling refers to expressing the logic and rules of how the work in the workflow is organized together in an appropriate model in the computer and implementing calculations on it. The main problem to be solved by workflow is to use computers to automatically transfer documents, information or tasks between multiple participants according to certain predetermined rules in order to achieve a certain business goal.

When processing large-scale or high-frequency tasks, existing workflow engines may face performance bottlenecks, resulting in a slowdown in task processing, which is a problem that cannot be ignored for applications that require high throughput. Therefore, a workflow engine that can adapt to high concurrency environments is needed.

Contents of the invention

In order to overcome the problems existing in the prior art, the present invention designs a service-oriented configurable workflow engine working method and equipment.

In order to achieve the above objects, the present invention adopts the following technical solutions:

Technical solution one

The working method of the service-oriented configurable workflow engine includes the following steps:

Create workflow;

The workflow engine executes the workflow; during the execution process, the workflow engine calls external services according to the interface information configured by the process node and receives the call results;

The exception handler obtains the execution status information of each process node and handles exceptions.

Furthermore, it also includes: creating forms, binding forms and process nodes.

Further, the creation workflow includes:

Design start nodes, application nodes, process nodes, process variables, gateways, triggers and end nodes;

Bind the start node to the initiation form and select candidates;

Configure the approval form for the approval node and select candidates;

Bind the gateway to process variables;

Configure triggers or external services on process nodes.

Furthermore, when the workflow engine executes a node task, a new task form containing task status information is created every time an external service is called; the external service provider and the workflow engine synchronize task information through the task form.

Further, the exception handler obtains the execution status of the external service from the task form to implement functions such as compensation mechanism, retry, and mapping exceptions.

Technical solution two

The service-oriented configurable workflow engine working equipment includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps described in the first technical solution. .

Compared with the prior art, the present invention has the following characteristics and beneficial effects:

The present invention provides a complete set of configuration mechanisms to realize form creation and process creation through steps S10 and S20. Each business process is decomposed into a series of services that can be executed independently. Through step S20, users can flexibly combine according to actual needs. and adjust these services to form workflows that meet specific business scenarios. In addition, the present invention also provides a complete set of service management and scheduling mechanisms. Through steps S2050, S40, and S50, it can ensure that various services can interact according to predetermined order and rules and support distributed transactions. At the same time, the robustness and maintainability of the entire process execution can be preserved. Through the separation of the process and business services in steps S10 and S20, the problem of large business concurrency is solved.

Description of the drawings

Figure 1 is a schematic diagram of the present invention.

Detailed ways

The present invention will be described in more detail below with reference to examples.

Embodiment 1

As shown in Figure 1, a service-oriented configurable workflow system includes:

Form designer, used to create forms, such as initiation forms, approval forms, etc.;

Process designer is used to create workflows. The workflow includes several process nodes and configures the relationships between process nodes. In particular, when creating a workflow, configure triggers on process nodes or call external services;

Process management platform, used to publish processes and instantiate them;

Exception handler, used to track and monitor workflow status, understand completed tasks and upcoming operations, etc. At the same time, error information during execution is recorded to facilitate analysis and recovery.

The workflow engine controls the workflow to move to the next node according to a preset sequence or conditions, and automatically or manually executes each node task to complete the entire process scheduling. During the execution of the workflow, the workflow engine calls the external business system according to the interface information configured by the process node and receives the call results.

Embodiment 2

As shown in Figure 1, the working method of the service-oriented configurable workflow engine includes the following steps:

S10: Design forms, such as initiation forms and approval forms, by using the form designer;

S20: Use process designer to create processes:

S2010: Design start node, application node, process node, process variable, gateway, trigger and end node;

S2020: Bind the start node to the initiation form and select candidates;

S2030: Configure the approval form for the approval node and select candidates;

S2040: Bind the gateway to the process variables;

S2050: The process node can configure triggers or call external services. This step is usually linked with the business system to complete service management;

S2060: Save the completed process design;

S30: Publish the corresponding process on the process management platform and instantiate it;

S40: The candidate fills in the relevant content on the process initiation form and clicks to submit the application, thereby triggering the workflow. At this time, the workflow engine will control the workflow to move to the next node according to the preset sequence or conditions, and automatically or manually execute each node task to complete the entire process scheduling.

S50: The exception handler tracks and monitors the workflow status to understand information such as completed tasks and upcoming operations. At the same time, error information during execution is recorded to facilitate analysis and recovery, such as compensation, polling, retry and other operations.

S60: When all tasks have been completed correctly, the workflow instance ends.

Embodiment 3

Furthermore, when the workflow engine executes a node task, a new task form is created every time an external service is called. The task form stores task status information, including: external service provider identification, call time, etc. The external service provider and the workflow engine synchronize task information through the task form; the exception handler obtains the execution status of the external service from the task form to implement functions such as compensation mechanism, retry, and mapping exceptions.

It should be noted that each functional unit/module in various embodiments of the present invention can be integrated into one processing unit/module, or each unit/module can exist physically alone, or it can be two or more units/modules. Modules are integrated in one unit/module. The above integrated units/modules can be implemented in the form of hardware or software functional units/modules.

Through the above description of the embodiments, those skilled in the art can clearly understand that the embodiments described herein can be implemented in hardware, software, firmware, middleware, code, or any appropriate combination thereof. For hardware implementation, the processor may be implemented in one or more of the following units: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Programmable gate array (FPGA), processor, controller, microcontroller, microprocessor, other electronic unit designed to perform the functions described herein, or combinations thereof. For software implementation, part or all of the processes of the embodiments can be completed by instructing relevant hardware through a computer program. When implemented, the above-mentioned program may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by the computer. Computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or may be used to carry or store desired program code in the form of instructions or data structures and any other media that can be accessed by a computer.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit the protection scope of the present invention. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should analyze , the technical solution of the present invention may be modified or equivalently substituted without departing from the essence and scope of the technical solution of the present invention.

Claims (10)

1. A service-oriented configurable workflow engine operating method, comprising the steps of:

creating a workflow;

a workflow engine executing the workflow; in the execution process, the workflow engine calls external services according to interface information configured by the flow nodes and receives call results;

the exception handler obtains the execution state information of each flow node and carries on the exception handling.

2. The service-oriented configurable workflow engine operating method of claim 1, further comprising: creating a form, binding the form and the flow node.

3. The service-oriented configurable workflow engine operating method of claim 1, wherein the creating workflow comprises:

designing a starting node, an application node, a flow variable, a gateway, a trigger and an ending node;

binding the starting node with the initiating form and selecting a candidate;

configuring an approval form for the approval node and selecting a candidate;

binding the gateway and the flow variable;

the flow node configures the trigger or external service.

4. The service-oriented configurable workflow engine working method of claim 1, wherein when the workflow engine executes node tasks, a task form with task state information is correspondingly created every time an external service is called; the external service provider and the workflow engine synchronize task information via a task form.

5. The service-oriented configurable workflow engine operating method of claim 4, wherein the exception handler obtains the execution status of the external service from the task form to implement a compensation mechanism, retry and map exceptions.

6. A service-oriented configurable workflow engine work device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the following steps when executing the program:

creating a workflow;

a workflow engine executing the workflow; in the execution process, the workflow engine calls external services according to interface information configured by the flow nodes and receives call results;

the exception handler obtains the execution state information of each flow node and carries on the exception handling.

7. The service-oriented configurable workflow engine work device of claim 6, further comprising: creating a form, binding the form and the flow node.

8. The service-oriented configurable workflow engine work device of claim 6, wherein the creation workflow comprises:

designing a starting node, an application node, a flow variable, a gateway, a trigger and an ending node;

binding the starting node with the initiating form and selecting a candidate;

configuring an approval form for the approval node and selecting a candidate;

binding the gateway and the flow variable;

the flow node configures the trigger or external service.

9. The service-oriented configurable workflow engine work apparatus of claim 6, wherein when the workflow engine performs a node task, a task form with task state information is created correspondingly every time an external service is called; the external service provider and the workflow engine synchronize task information via a task form.

10. The service-oriented configurable workflow engine work device of claim 9 wherein the exception handler obtains the execution status of the external service from the task form to implement a compensation mechanism, retry and map exceptions.