CN116700174A - A rule-based non-BPMN standard process engine - Google Patents

Abstract

The invention relates to the technical field of workflow, specifically a rule-based non-BPMN standard technological process engine, including current awareness and element, wherein the current awareness is composed of transmitter, awareness switch and element signal processor; For the transfer of information and context in non-BPMN standard process engines, the transmitter can contain data and information in the business process; the consciousness switch is used to control the startup and shutdown of the consciousness state; the meta-signal processor is responsible for receiving and processing meta-signals, Meta-signals are triggered by internal events, and meta-signal processors capture meta-signals and trigger corresponding operations and process transfers. Compared with the prior art, the present invention has the advantages of: reducing the complexity of licensing and implementation, and reducing costs; it can adapt to the needs of various industries and fields, and has flexibility; it can describe the process flow by defining rules, It is easy to use; it can perform tasks quickly and accurately, and improve the efficiency of process execution.

Description

A rule-based non-BPMN standard process engine

technical field

The invention relates to the technical field of workflow, in particular to a rule-based non-BPMN standard technological process engine.

Background technique

Process engines currently on the market are usually designed based on the BPMN standard, and they usually require expensive licenses and complicated implementation steps. Furthermore, the BPMN standard is a very general notation for processes and may not fully adapt to the needs of some specific industries or domains.

Contents of the invention

The technical problem to be solved by the present invention is to overcome the deficiencies of the prior art and provide a rule-based non-BPMN standard technological process engine for managing specific industry fields.

In order to achieve the above purpose, a rule-based non-BPMN standard process flow engine is designed, including current awareness and meta, where current awareness is composed of transmitter, awareness switch and meta signal processor; transmitter is used in non-BPMN standard Information and context are transmitted in the process engine, and the transmitter can contain data and information in the business process, and information sharing and communication can be realized through the transfer and update of the transmitter; the consciousness switch is used to control the startup and shutdown of the consciousness state, when a specific event When it occurs, the state of consciousness can be activated or deactivated, thereby triggering corresponding operations and tasks; the meta-signal processor is responsible for receiving and processing the meta-signal, which is triggered by an internal event, and the meta-signal processor captures the meta-signal and triggers the corresponding operation and process transfer; element is the basic building unit in non-BPMN standard process engine, each element is composed of element switch, element signal, worker and sentinel, element switch is used to control the start and stop of element, and element signal is used to trigger For specific operations, workers represent entities that perform specific work tasks, while sentries are used to control and guide the execution of meta.

Preferably, transmitters are further subdivided into metatransmitters and context transmitters. Metatransmitters are a type of transmitter used to transfer information and data in non-BPMN standard process engines. Metatransmitters can be stored and transmitted The global information related to the business process is used by each element and worker. The context transmitter is a transmitter type used to transfer context and local information in a non-BPMN standard process engine, and is used in a specific state of consciousness Or internally transfer and store local data and context information.

Preferably, the worker is an entity that performs specific work tasks, is a human-computer interaction interface or an automatic program, and the worker interacts with the unit to complete related work and operations.

Preferably, the sentry is used to control and guide the execution of elements in the non-BPMN standard process flow engine, and the sentinel triggers the start and stop of the element according to the satisfaction degree of the specific condition, or guides the process transfer between the elements.

Preferably, sentinels are divided into three types: process sentinel, signature sentinel and logic sentinel. Process sentinel is used to control the startup and shutdown of elements. It monitors specific conditions related to elements and triggers the startup or shutdown of elements when the conditions are met. Process sentinels are triggers based on time, events or other conditions, and are used to determine the execution timing of elements in non-BPMN standard process engine; signature sentinels are used to control the execution path and process transfer of elements, and it checks elements related to Specific conditions, and determine the next step of meta-execution according to the degree of satisfaction of the conditions. Signature sentinels can be used to decide the execution direction and process of meta-executions based on specific rules, constraints, or business logic; logic sentries are used for logic in the meta-execution process Judgment and control, which checks the logical conditions associated with the meta and takes corresponding actions based on the results of the conditions. Logical sentinels can be used to verify business rules, conditional constraints, or logical paths in the meta execution process to ensure that meta behaves as expected implement.

Compared with the prior art, the present invention has the advantages of:

1. Low cost: Compared with the process engine of BPMN standard, the engine of the present invention can reduce the cost, reduce the complexity of license and implementation;

2. Flexibility: It can adapt to the needs of various industries and fields, and can be customized and expanded to meet the specific needs of users;

3. Ease of use: The process flow can be described by defining rules, and related operations can be performed according to these rules, so that users can easily create and edit the process flow, and at the same time monitor the process execution in real time;

4. Efficiency: Using the rule engine to execute the process can quickly and accurately execute tasks and improve the efficiency of process execution.

Description of drawings

Fig. 1 is a flow chart of the non-BPMN process flow engine provided by the present invention.

Detailed ways

The present invention will be further described below in conjunction with accompanying drawing, and the structure and principle of the present invention are very clear to those skilled in the art. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

The invention discloses a rule-based non-BPMN standard process flow engine, which includes current awareness and element, wherein the current awareness is composed of transmitter, awareness switch and element signal processor.

Transmitters are used to transfer information and context in non-BPMN standard process engines. Transmitters can contain data and information in business processes, and information sharing and communication can be realized through transfer and update of transmitters;

For transmitters in non-BPMN standard process flow engines, they can be further subdivided into metatransmitters and contextual transmitters. Metatransmitter is a type of transmitter used to transfer information and data in a non-BPMN standard process engine. Metatransmitter can store and transmit global information related to business processes for use by each element and worker; context A transmitter is a transmitter type used to transfer context and local information in a non-BPMN standard process engine, and is used to transfer and store local data and context information within a specific state of consciousness or element.

Such segmentation can help non-BPMN standard process engines to better manage the visibility and accessibility of information, ensuring that the appropriate information is delivered and used at the appropriate time and scope. Through the proper use of metatransmitters and contextual mediators, a more precise and efficient flow of information can be achieved to support decision-making and execution in business processes.

The consciousness switch is used to control the activation and deactivation of the conscious state. When a specific event occurs, the conscious state can be activated or deactivated, thereby triggering corresponding operations and tasks;

The meta-signal processor is responsible for receiving and processing meta-signals. Meta-signals are triggered by internal events. Meta-signal processors capture meta-signals and trigger corresponding operations and process transfers;

Meta is the basic building unit in non-BPMN standard process engine. Each meta is composed of meta switch, meta signal, worker and sentinel. Meta switch is used to control the startup and shutdown of meta, and meta signal is used to trigger specific operations. Workers represent entities that perform specific work tasks, while Sentinels are used to control and guide the execution of meta.

A worker represents an entity that performs specific work tasks. It is a human-computer interaction interface or an automatic program. The worker interacts with the unit to complete related work and operations.

Sentinels are used to control and guide the execution of elements in non-BPMN standard process engines. Sentinels trigger the startup and shutdown of elements according to the satisfaction of specific conditions, or guide the process transfer between elements.

Sentinels are a mechanism for controlling and directing meta-execution in non-BPMN standard process engines. Sentinels are divided into three types: process sentinel, signature sentinel and logic sentinel. Process sentinel is used to control the startup and shutdown of elements. It monitors specific conditions related to elements and triggers the startup or shutdown of elements when conditions are met. Process sentinels are Triggers based on time, events or other conditions are used to determine the execution timing of elements in non-BPMN standard process engines; signature sentinels are used to control the execution path and process transfer of elements, which check specific conditions related to elements, And determine the next step of meta execution according to the degree of satisfaction of the conditions. The signature sentinel can be used to decide the execution direction and process of the meta based on specific rules, constraints or business logic; the logic sentinel is used for logical judgment and control in the meta execution process , which checks the logical conditions associated with the meta and takes corresponding actions based on the results of the conditions. Logical sentinels can be used to verify business rules, conditional constraints, or logical paths during meta execution to ensure that meta executes as expected.

The role of these sentinels is to help control and guide the execution process of elements in the non-BPMN standard process engine to ensure that elements start, shut down or transfer at the appropriate time. They affect the behavior of elements by checking specific conditions or logic, so as to realize the flexibility, adaptability and controllability of non-BPMN standard process engine.

By using process sentinel, signature sentinel and logic sentinel, non-BPMN standard process engine can better manage the execution process of elements, ensure that business processes are carried out according to expectations and requirements, and make corresponding adjustments and controls when necessary.

Process engine of the present invention includes the following aspects:

1. In the engine, multiple processes and rules can be defined, each process contains multiple nodes, and each node has input elements and output elements. A process consists of a series of nodes, each node is a description of a specific operation or function, and each node includes the following attributes:

1. Title: Describe the name of the node, used to identify the node;

2. Description: Describe the information data of the node, which is used to introduce the task;

2. Input parameters: describe the input materials required by the task, including name, URL traceability code, encoding and other information;

3. Output parameters: describe the output materials required by the task, including name, URL traceability code, encoding and other information;

4. Execution conditions: describe the execution conditions of the task, including input parameters, output parameters, other conditions, etc.;

5. Signature: Describe the executor information required for the task.

2. In this engine, a rule-based process language can be used to describe the business logic calculation of nodes. This process language uses rule statements to describe the execution conditions and operations of tasks, where the rule statements can contain instructions, operations, and business variable elements.

The rule engine is the core part of the engine, which is responsible for parsing and executing rule statements in the process language. The rules engine includes the following components:

1. Instructions: store and execute operations;

2. Operation: storage operation;

3. Business variables: business variables of the storage system;

4. Rule verification: verify the rules configured by the user.

In the engine, a graphical user interface is used to create and edit process flows. Users create and edit processes through this interface, and specify the inputs and outputs for each task. The interface can also display the status and execution of each task, so that users can monitor the execution of the process at any time.

The process execution process of the engine is as follows:

1. The user creates or edits the process and saves it in the process;

2. The user configures the process and enters the required input parameters, output parameters, subject matter and signature;

3. Build process nodes;

4. The engine executes each task on the process execution node in sequence;

5. For each task, the engine passes the input parameters and execution conditions to the rule engine, and the rule engine judges whether the execution conditions are met, and executes the corresponding execution operation;

6. For each task, the engine passes the execution result to the next task until the execution of the process is completed or an exception occurs;

7. The engine returns the output parameters to the user and marks the execution of the process flow as completed.

The specific workflow of engine described in the present invention is as follows:

The user splits the process into various process step nodes and gateways, sorts the process steps according to the flow of the process, sets up the start node and end node, and sets the start node, process step node, gateway, and end node Connect according to the process. After the connection is completed, define the rules for each process node, including the function calculation of the node, and verify the final function calculation formula. After the verification is completed, the rule-based non-BPMN standard process engine configuration is completed. .

The advantages of this engine are:

1. It can flexibly define and manage the process flow of a specific industry field, without being restricted by the BPMN standard;

2. Support rule-based process language, which can flexibly describe the execution conditions and operations of tasks;

3. Use the rule engine to execute the process, which can execute tasks quickly and accurately, and improve the efficiency of process execution;

4. Provide a graphical user interface, which is convenient for users to create and edit technological processes, and can monitor the execution of the process in real time.

The above description of the present invention is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person familiar with the technical field within the technical scope disclosed in the present invention, according to the technical scheme of the present invention and Novel ideas plus equivalent replacements or changes should be covered within the protection scope of the present invention.

Claims (5)

1. A technical process engine based on a rule-based non-BPMN standard, characterized in that the non-BPMN technical process engine comprises current awareness and element, wherein current awareness is made of transmitter, awareness switch and element signal processor; The transmitter is used to transfer information and context in the non-BPMN standard process engine, the transmitter can contain data and information in the business process, and information sharing and communication can be realized through the transfer and update of the transmitter; The consciousness switch is used to control the start and stop of the state of consciousness. When a specific event occurs, the state of consciousness can be turned on or off, thereby triggering corresponding operations and tasks; the meta-signal processor is responsible for receiving and processing the meta-signal, and the meta-signal The signal is triggered by an internal event, and the meta-signal processor captures the meta-signal and triggers the corresponding operation and process transfer; the meta-unit is the basic building unit in the non-BPMN standard process engine, and each unit consists of meta-switch, meta-signal, work The meta switch is used to control the startup and shutdown of the meta, the meta signal is used to trigger specific operations, the worker represents the entity that performs specific work tasks, and the sentinel is used to control and guide the execution of the meta. 2. The process engine of a kind of rule-based non-BPMN standard process engine as claimed in claim 1, it is characterized in that said transmitter is further subdivided into metatransmitter and context transmitter, and said metatransmitter is a kind of For the transfer type of information and data in the non-BPMN standard process engine, the meta transferer can store and transfer the global information related to the business process for use by each element and worker. The context transferr is a Transmitter type used to transfer context and local information in non-BPMN standard process engines, used to transfer and store local data and context information inside a specific state of consciousness or meta. 3. a kind of rule-based non-BPMN standard technological process engine as claimed in claim 1, it is characterized in that described worker is the entity that carries out specific work task, is man-machine interaction interface or automatic program, and worker and element Interact and complete related work and operations. 4. A kind of rule-based non-BPMN standard technological process engine as claimed in claim 1, it is characterized in that said sentinel is used for controlling and guiding the execution of elements in the non-BPMN standard technological process engine, sentinel according to specific conditions Satisfaction levels trigger the startup and shutdown of cells, or direct process transfers between cells. 5. A rule-based non-BPMN standard technological process engine as claimed in claim 1 or 4, wherein said sentinel is divided into three types: process sentinel, signature sentinel and logic sentinel, and process sentinel is used for control element It monitors the specific conditions associated with the element and triggers the start or shutdown of the element when the condition is met. The process sentinel is a trigger based on time, event or other conditions, which is used to determine the process of the element in the non-BPMN standard The execution timing in the process engine; the signature sentinel is used to control the execution path and process transfer of the element. It checks the specific conditions related to the element and determines the next step of the element execution according to the degree of satisfaction of the conditions. The signature sentinel can be based on specific rules, Constraints or business logic are used to determine the execution direction and flow of the element; logic sentinels are used for logical judgment and control during the execution of the element, it checks the logical conditions related to the element, and takes corresponding actions according to the results of the conditions, logic Sentinels can be used to validate business rules, conditional constraints, or logical paths in the meta execution process to ensure that the meta executes as expected.