A rule-based process flow engine that is not a BPMN standard

Abstract

The application relates to the technical field of workflow, in particular to a rule-based non-BPMN standard process flow engine, which comprises a current consciousness and a meta, wherein the current consciousness is composed of a neurotransmitter, a consciousness switch and a meta signal processor; the neurotransmitter is used for transmitting information and context in the non-BPMN standard process flow engine, and the neurotransmitter can contain data and information in a business process; the consciousness switch is used for controlling the start and shutdown of a consciousness state; and the meta signal processor is responsible for receiving and processing a meta signal, the meta signal is triggered by an internal event, the meta signal processor captures the meta signal and triggers corresponding operation and process transfer. Compared with the prior art, the application has the advantages that: the complexity of a license and implementation is reduced, and the cost is lowered; the application can adapt to the requirements of various different industries and fields, and has flexibility; the application can describe a process flow by defining rules, and has ease of use; the application can quickly and accurately execute tasks, and improves process execution efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of workflow, in particular to a rule-based non-BPMN standard process engine. BACKGROUND

[0002] Currently, the process engines on the market are usually designed based on the BPMN standard, which usually requires expensive licenses and complex implementation steps. In addition, the BPMN standard is a very general process representation method, which may not fully adapt to the needs of certain specific industries or fields. SUMMARY

[0003] The technical problem to be solved by the present application is to overcome the shortcomings of the prior art, and to provide a rule-based non-BPMN standard process engine for managing specific industries.

[0004] In order to achieve the above purpose, a rule-based non-BPMN standard process engine is designed, which includes current awareness and meta, wherein the current awareness is composed of neurotransmitter, awareness switch and meta signal processor; neurotransmitter is used to transmit information and context in the non-BPMN standard process engine, neurotransmitter can contain data and information in business processes, and information sharing and exchange are realized through the transmission and update of neurotransmitter; awareness switch is used to control the start and stop of awareness state, when a specific event occurs, the awareness state can be started or stopped, thereby triggering corresponding operations and tasks; the meta signal processor is responsible for receiving and processing meta signals, the meta signals are triggered by internal events, and the meta signal processor captures the meta signals and triggers corresponding operations and process transitions; the meta is the basic building unit in the non-BPMN standard process engine, each meta is composed of a meta switch, a meta signal, a worker and a sentinel, the meta switch is used to control the start and stop of the meta, the meta signal is used to trigger specific operations, the worker represents an entity that performs specific work tasks, and the sentinel is used to control and guide the execution of the meta.

[0005] Preferably, neurotransmitter is further subdivided into meta neurotransmitter and context neurotransmitter, meta neurotransmitter is a neurotransmitter type used to transmit information and data in the non-BPMN standard process engine, meta neurotransmitter can store and transmit global information related to business processes for use by each meta and worker, and context neurotransmitter is a neurotransmitter type used to transmit context and local information in the non-BPMN standard process engine, used to transmit and store local data and context information within a specific awareness state or meta.

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

[0007] Preferably, the sentinels are used to control and guide the execution of the non-BPMN standard process engine elements, and the sentinels trigger the start and stop of the elements according to the satisfaction of specific conditions, or guide the process transfer between elements.

[0008] Preferably, the sentinels are divided into three types: process sentinels, signature sentinels and logic sentinels. The process sentinels are used to control the start and stop of the elements, which monitor specific conditions related to the elements and trigger the start or stop of the elements when the conditions are met. The process sentinels are based on time, events or other conditions triggers, which are used to determine the execution timing of the elements in the non-BPMN standard process engine. The signature sentinels are used to control the execution path and process transfer of the elements, which check specific conditions related to the elements and decide the next step of the element execution according to the satisfaction of the conditions. The signature sentinels can be based on specific rules, constraints or business logic, which are used to decide the execution direction and process of the elements. The logic sentinels are used to make logical judgments and controls during the execution of the elements, which check logical conditions related to the elements and take corresponding actions according to the results of the conditions. The logic sentinels can be used to verify business rules, condition constraints or logical paths during the execution of the elements, to ensure that the elements are executed in the expected way.

[0009] Compared with the prior art, the present application has the following advantages:

[0010] 1. Low cost: compared with the BPMN standard process engine, the engine of the present application can reduce the cost and complexity of licensing and implementation;

[0011] 2. Flexibility: can adapt to various industry and field requirements, and can be customized and extended to meet the specific needs of users;

[0012] 3. Ease of use: can describe the process by defining rules and execute relevant operations according to these rules, so that users can easily create and edit the process, while being able to monitor the process execution in real time;

[0013] 4. Efficiency: using rule engine to execute the process can quickly and accurately execute tasks, improving the efficiency of process execution. BRIEF DESCRIPTION OF DRAWINGS

[0014] Figure 1 is a flowchart of the non-BPMN process engine provided by the present application. DETAILED DESCRIPTION

[0015] The structure and principles of the present application are very clear to those skilled in the art. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0016] The application discloses a rule-based non-BPMN standard process engine, including current awareness and meta, wherein the current awareness is composed of neurotransmitters, awareness switches and meta signal processors.

[0017] The neurotransmitters are used to transmit information and context in the non-BPMN standard process engine, and the neurotransmitters can contain data and information in the business process, and information sharing and exchange are realized through transmission and updating of the neurotransmitters.

[0018] For the neurotransmitters in the non-BPMN standard process engine, the neurotransmitters can be further divided into meta neurotransmitters and context neurotransmitters. The meta neurotransmitters are a type of neurotransmitters used to transmit information and data in the non-BPMN standard process engine, and the meta neurotransmitters can store and transmit global information related to the business process for use by various meta and workers. The context neurotransmitters are a type of neurotransmitters used to transmit context and local information in the non-BPMN standard process engine, and are used to transmit and store local data and context information in a specific awareness state or meta.

[0019] Such subdivision can help the non-BPMN standard process engine better manage the visibility and accessibility of information, and ensure that appropriate information is transmitted and used at the right time and in the right scope. By properly using meta neurotransmitters and context neurotransmitters, more accurate and effective information flow can be achieved to support decision-making and execution in the business process.

[0020] The awareness switches are used to control the start and stop of the awareness state, and the awareness state can be started or stopped when a specific event occurs, thereby triggering corresponding operations and tasks.

[0021] The meta signal processors are responsible for receiving and processing meta signals, and the meta signals are triggered by internal events. The meta signal processors capture the meta signals and trigger corresponding operations and process transitions.

[0022] The meta is a basic building unit in the non-BPMN standard process engine, and each meta is composed of a meta switch, a meta signal, a worker and a sentinel. The meta switch is used to control the start and stop of the meta, the meta signal is used to trigger specific operations, the worker represents an entity that performs specific work tasks, and the sentinel is used to control and guide the execution of the meta.

[0023] The worker represents an entity that performs specific work tasks, and is a human-computer interaction interface or an automatic program. The worker interacts with the meta to complete related work and operations.

[0024] The sentinel is used to control and guide the execution of the meta in the non-BPMN standard process engine. The sentinel triggers the start and stop of the meta according to the degree of satisfaction of specific conditions, or guides the process transition between the meta.

[0025] In non-BPMN standard process engine, a sentinel is a mechanism for controlling and guiding the execution of a meta. There are three types of sentinels: process sentinel, signature sentinel and logic sentinel. Process sentinel is used to control the start and close of a meta, which monitors specific conditions related to the meta and triggers the start or close of the meta when the conditions are met. Process sentinel is a trigger based on time, event or other conditions, used to determine the execution timing of the meta in non-BPMN standard process engine. Signature sentinel is used to control the execution path and process transfer of a meta, which checks specific conditions related to the meta and decides the next step of the meta execution according to the satisfaction degree of the conditions. Signature sentinel can be based on specific rules, constraints or business logic, used to decide the execution direction and process of the meta. Logic sentinel is used for logical judgment and control during the execution of a meta, which checks logical conditions related to the meta and takes corresponding actions according to the results of the conditions. Logic sentinel can be used to verify business rules, condition constraints or logical paths during the execution of a meta to ensure that the meta executes in the expected way.

[0026] The role of these sentinels is to help control and guide the execution process of a meta in non-BPMN standard process engine, ensuring that the meta starts, closes or transfers at the appropriate time. They affect the behavior of the meta by checking specific conditions or logic, thereby achieving flexibility, adaptability and controllability of non-BPMN standard process engine.

[0027] By using process sentinel, signature sentinel and logic sentinel, non-BPMN standard process engine can better manage the execution process of a meta, ensuring that the business process proceeds as expected and required, and making corresponding adjustments and controls when needed.

[0028] The process engine described in the present application includes the following aspects:

[0029] I. In the engine, multiple processes and rules can be defined, each process containing multiple nodes, each node having input elements and output elements. A process is composed of a series of nodes, each node being a description of a specific operation or function, each node including the following attributes:

[0030] 1. Title: describes the name of the node, used to identify the node;

[0031] 2. Description: describes the information data of the node, used to introduce the task;

[0032] 2. Input parameters: describe the input materials required by the task, including name, URL trace code, code and other information;

[0033] 3. Output parameters: describe the output materials required by the task, including name, URL trace code, code and other information;

[0034] 4. Execution condition: describes the execution condition of the task, including input parameters, output parameters, other conditions, etc.

[0035] 5. Signature: describes the execution personnel information required by the task.

[0036] II. In this engine, a rule-based flow language can be used to describe the business logic calculation of the nodes. This flow language uses rule statements to describe the execution condition and execution operation of the task, where the rule statement can contain instructions, operations, and business variable elements.

[0037] The rule engine is the core part of the engine, responsible for parsing and executing rule statements in the flow language. The rule engine includes the following components:

[0038] 1. Instruction: stores the execution operation;

[0039] 2. Operation: stores the operation operation;

[0040] 3. Business variable: stores the business variable of the system;

[0041] 4. Rule verification: verifies the rules configured by the user.

[0042] In this engine, a graphical user interface is used to create and edit the process flow. The user creates and edits the process through this interface, and specifies the input and output of each task. The interface can also display the status and execution of each task, so that the user can monitor the execution of the process flow at any time.

[0043] The flow execution process of the engine is as follows:

[0044] 1. The user creates or edits the process, and saves it to the process;

[0045] 2. The user configures the process and inputs the required input parameters, output parameters, objects and signatures;

[0046] 3. Build flow nodes;

[0047] 4. The engine executes each task on the flow execution node in turn;

[0048] 5. For each task, the engine passes the input parameters and execution conditions to the rule engine, which determines whether the execution conditions are met and executes the corresponding execution operation;

[0049] 6. For each task, the engine passes the execution result to the next task until the flow execution is completed or an exception occurs;

[0050] 7. The engine returns the output parameters to the user and marks the process flow execution complete.

[0051] The specific working process of the engine is as follows:

[0052] The user splits the process into process step nodes and gateways, sorts the process steps in the form of process flow, sets up a start node and an end node, connects the start node, process step node, gateway and end node according to the process, defines the rules for each process node after the connection is completed, including function calculation of the node, verifies the final function calculation formula, and completes the configuration of the process flow engine based on the rules after the verification is completed.

[0053] The advantages of the engine are:

[0054] 1. The process flow of a specific industry field can be flexibly defined and managed, and is not limited by the BPMN standard;

[0055] 2. The process language based on rules is supported, and the execution conditions and execution operations of tasks can be flexibly described;

[0056] 3. The rule engine is used to execute the process, which can quickly and accurately execute tasks and improve the efficiency of process execution;

[0057] 4. A graphical user interface is provided to facilitate the user to create and edit the process flow, and the process execution situation can be monitored in real time.

[0058] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can make equivalent substitutions or changes to the technical solution and novel concept of the present application within the technical range disclosed by the present application, which should be covered within the protection scope of the present application.

Claims

1. A rule-based, non-BPMN standard process flow engine, characterized in that... The non-BPMN standard process engine includes current consciousness and meta, wherein current consciousness is composed of neurotransmitters, consciousness switches and meta signal processors; The relay is used to transmit information and context in a non-BPMN standard process engine. The relay can contain data and information in the business process, and information sharing and communication are realized through the transmission and updating of the relay. The consciousness switch is used to control the activation and deactivation of the consciousness state. When a specific event occurs, the consciousness 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. The meta signal processor captures meta signals and triggers corresponding operations and process transfers. The element is the basic building block in a non-BPMN standard process engine. Each element consists of an element switch, an element signal, a worker, and a sentinel. The element switch is used to control the start and stop of the element, the element 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 element. The sentinel is used to control and guide the execution of elements in the non-BPMN standard process engine. The sentinel triggers the start and stop of elements or guides the process transfer between elements based on the degree to which specific conditions are met. The sentinels are divided into three types: process sentinels, signature sentinels, and logic sentinels. Process sentinels are used to control the start and stop of elements. Specifically, they monitor specific conditions related to elements and trigger the start or stop of elements when the conditions are met. Process sentinels are triggers based on time, events, or other conditions to determine the execution timing of elements in non-BPMN standard process flow engines. The signature sentinel is used to control the execution path and flow transfer of the meta. It checks specific conditions related to the meta and determines the next step of the meta execution based on the degree to which the conditions are met. The signature sentinel can be used to decide the execution direction and flow of the meta based on specific rules, constraints or business logic. The logic sentinel is used to make logical judgments and controls during the execution of a meta. It checks the logical conditions related to the meta and takes corresponding actions based on the results of the conditions. The logic sentinel can be used to verify the business rules, conditional constraints or logical paths in the execution of a meta to ensure that the meta executes in the expected way.

2. The rule-based, non-BPMN standard process flow engine as described in claim 1, characterized in that... The relays are further subdivided into meta relays and context relays. Meta relays are a type of relay used to transmit information and data in a non-BPMN standard process engine. Meta relays can store and transmit global information related to business processes for use by various meta-processes and workers. Context relays are a type of relay used to transmit context and local information in a non-BPMN standard process engine. They are used to transmit and store local data and context information within a specific state of consciousness or meta-process.

3. The rule-based, non-BPMN standard process flow engine as described in claim 1, characterized in that... The worker is an entity that performs specific work tasks. It is a human-computer interaction interface or an automatic program. The worker interacts with the element to complete related work and operations.

Images