Implementation method and system of process item rule engine based on trusted data space

Abstract

The invention relates to the technical field of process management, in particular to an implementation method and system of a process item rule engine based on trusted data space, comprising item engine configuration and management, process configuration and management, service orchestration and process item rule engine use. The method has the beneficial effects that the problems of frequent fixed code modification, insufficient flexibility and high maintenance cost in traditional process management are solved by dynamically configuring the process, the item engine and the form. By establishing a matter-form-process-service orchestration decoupling mapping relation, providing a declarative rule configuration interface, supporting business personnel to autonomously adjust business rules, realizing dynamic assembly of service orchestration and the like, flexible triggering and execution of processes and services are realized, and the development and maintenance cost is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of process management, in particular to an implementation method and system of a process matter rule engine based on a trusted data space. BACKGROUND

[0002] In traditional process management systems, the triggering of processes and matters usually depends on fixed code logic. Traditional business process systems lack flexibility: the triggering rules of processes and matters need to be manually modified by developers, making it difficult to quickly respond to changes in business requirements. When business processes change, the corresponding approval processes, form designs, and service calls may all need to be adjusted, and these adjustments often take a long time to implement. Matters and processes are strongly coupled, which means that each business matter needs to be hard-coded and bound to a specific process. This means that any modification to existing processes or matters requires re-development and deployment of the application, increasing the complexity and risk of the project. In addition, this close association also limits the reusability of components, making it difficult to expand and maintain the system. Form-driven capabilities are weak, with page jump logic fixed in the code, making it difficult to adapt to changes in multiple scenarios. Service coordination is complex, and cross-system service calls require the development of an adaptation layer, lacking a unified orchestration mechanism, and other issues.

[0003] Existing rule engine solutions mostly use script configuration methods, which have the defect of high configuration complexity and fail to effectively solve the problem of trusted data transmission. SUMMARY

[0004] The present application aims to provide an implementation method and system of a process matter rule engine based on a trusted data space to solve the problems raised in the background.

[0005] To achieve the above-mentioned purpose, the present application provides the following technical solution: an implementation method of a process matter rule engine based on a trusted data space, comprising:

[0006] Defining a matter engine: identifying form information related to the matter through a unique matter code and name that identifies the business scenario;

[0007] Form definition: including code, name, and value, form value is not limited to page path, but also includes parameters required for jumping;

[0008] Execution method definition: divided into two categories of process and service orchestration, each method has a unique code, name, and type, and the corresponding execution method is selected according to the form value and preset rules;

[0009] Rule definition: composed of attributes, operators, and rule values, used to determine which form or execution method to trigger under certain conditions;

[0010] Provide an intuitive interface: allow administrators to dynamically adjust the relationship between the transaction engine, process, and service orchestration, without the need to write code to modify business logic.

[0011] Preferably, it also includes process configuration and management, specifically:

[0012] Process definition: a business process is composed of multiple links, each link contains specific forms and approval logic; support adding new approval links, and specify participants, associated form attributes, and execution methods for each link; the process supports dynamic expansion, including branch condition judgment, parallel processing, sub-process nesting, and rollback mechanism in abnormal situations; provide a visual interface when configuring the process, allowing users to quickly create and configure process basic information and links by dragging and dropping components;

[0013] Process adjustment: dynamically adjust the running process without affecting completed links, such as adding new links, modifying branch conditions, or redistributing participants.

[0014] Preferably, it also includes service orchestration:

[0015] Organize multiple independent services according to specific business logic to coordinate interaction to complete complex business operations; provide a management page for users to add service orchestration, configure interfaces and other logic to automatically execute related services when specific conditions are met, ensuring efficient collaboration across system interfaces.

[0016] Preferably, it also includes the use of process transaction rule engines:

[0017] According to the transaction code and parameters, get the transaction engine form and jump to the form value configuration page; after operating on the form page, get the execution method according to the form code and other parameters.

[0018] Preferably, after obtaining the execution method:

[0019] If the execution method type is a process, proceed from the current start node to the next approval node until the end node; if the execution method type is service orchestration, directly execute the corresponding service orchestration until it is successfully completed.

[0020] A system for implementing a process transaction rule engine based on a trusted data space, comprising:

[0021] Transaction engine definition module: used to identify the form information related to the transaction through the unique transaction code and name that identifies the business scenario;

[0022] Form definition module: used to define forms, forms contain code, name and value, where form values are not limited to page paths, but also include jump required parameters;

[0023] Execution method definition module: used to define execution methods, which are divided into two categories: flow and service orchestration. Each method has a unique code, name and type, and selects the corresponding execution method according to the form value and preset rules;

[0024] Rule definition module: used to define rules, which are composed of attributes, operators and rule values, used to determine which form or execution method is triggered under certain conditions;

[0025] Dynamic adjustment interface module: provides an intuitive interface that allows administrators to dynamically adjust the relationship between the matter engine, flow and service orchestration without writing code to modify business logic.

[0026] Preferably, it also includes a flow configuration and management module, which includes:

[0027] Flow definition submodule: used to define flow, which is a business process composed of multiple links. Each link contains specific forms and approval logic; supports adding new approval links and can specify participants, associated form attributes and execution methods for each link; flow supports dynamic expansion, including branch condition judgment, parallel processing, sub-flow nesting and rollback mechanism in abnormal situations, so that even complex business processes can be easily managed and adjusted; at the same time, it provides a visual interface that allows users to quickly create and configure basic information and links of the flow by dragging and dropping components;

[0028] Flow adjustment submodule: used to dynamically adjust running flow without affecting completed links, such as adding new links, modifying branch conditions or redistributing participants.

[0029] Preferably, it also includes a service orchestration module, which includes:

[0030] Service organization coordination submodule: used to organize and coordinate multiple independent services according to specific business logic to complete complex business operations;

[0031] Service orchestration management submodule: provides a management page for users to add service orchestration, configure interfaces and other logic to automatically execute related services when certain conditions are met, ensuring efficient collaboration across system interfaces.

[0032] Preferably, it also includes a flow matter rule engine usage module, which includes:

[0033] Form acquisition and jump submodule: used to acquire matter engine forms according to matter code and parameters and jump to the page configured by form values;

[0034] Execution method acquisition submodule: used to acquire execution methods according to form code and other parameters after operation on the form page.

[0035] Preferably, the process matter rule engine usage module further comprises:

[0036] A process execution submodule: if the execution method acquisition submodule acquires an execution method type of a process, the execution method acquisition submodule is pushed from the current starting node to the next approval node until the ending node;

[0037] A service orchestration execution submodule: if the execution method acquisition submodule acquires an execution method type of service orchestration, the corresponding service orchestration is directly executed until the end.

[0038] Compared with the prior art, the beneficial effects of the present application are:

[0039] The implementation method and system of the process matter rule engine based on the trusted data space provided by the present application solve the problems of frequent modification of fixed codes, insufficient flexibility, and high maintenance cost in traditional process management by dynamically configuring processes, matter engines, and forms. BRIEF DESCRIPTION OF DRAWINGS

[0040] Figure 1 The process graph is configured and managed for the matter engine of the present application;

[0041] Figure 2 The process graph is configured and managed for the process of the present application;

[0042] Figure 3 The process graph is configured and managed for the process matter rule engine of the present application. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical scheme of the present application clear, complete and more clear and understandable, the embodiments of the present application are further described in detail below in combination with the drawings. It should be understood that the specific embodiments described herein are part of the embodiments of the present application, not all embodiments, and are only used to explain the embodiments of the present application, and do not limit the embodiments of the present application. All other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0044] Embodiment one, the present application provides a technical scheme: an implementation method of a process matter rule engine based on a trusted data space, comprising:

[0045] S1, matter engine configuration and management

[0046] 1) Transaction Engine Definition: Transaction code and name are used to uniquely identify a business scenario. Through the transaction code, you can query the form information related to the transaction, which is used to describe the specific content that the user sees when performing operations in the system.

[0047] 2) Form Definition: Form contains code, name and value. Form value not only includes page path but also may contain parameters required for jumping. This enables the system to dynamically adjust interface elements based on user input.

[0048] 3) Execution Method Definition: Execution methods are divided into two categories: process and service orchestration. Each method has its unique code, name, type, and other information. After the user completes the form operation, the system selects the corresponding execution method based on the form value and pre-set rules.

[0049] 4) Rule Definition: Rules are composed of attributes, operators, and rule values. These rules are used to determine which form or execution method to trigger under specific conditions. Rules can not only be simple numerical comparisons, but also involve complex logical judgments. This provides strong support for flexible configuration of business logic. For example, if the user's input meets the condition of "greater than a certain value", a specific service orchestration is triggered.

[0050] 5) Transaction Engine Configuration and Management: Provides an intuitive interface that allows administrators to dynamically adjust the relationship between transaction engines, processes, and service orchestrations without the need to write code to modify business logic.

[0051] S2, Process Configuration and Management

[0052] 1) Process Definition: Process is a business processing procedure composed of multiple links. Each link can contain specific forms, approval logic, service calls, or sub-processes. Process supports dynamic expansion, including branch condition judgment, parallel processing, sub-process nesting, and rollback mechanism in exceptional cases.

[0053] Start node is the entry point of the process, which can be triggered by the transaction engine; each link is an independent processing unit, which can be form filling, approval operation, service call or sub-process execution, and the links are transferred through pre-set rules; conditional branching is supported, which dynamically selects different paths based on user input or system state; sub-process is an independent process nested in the main process, used to handle complex business scenarios; each link can specify participants, which can be individuals, roles or departments, supporting dynamic allocation of participants. Process end, indicating the completion of the process. It can be configured as a success or failure state and supports notification mechanism. During the process execution, if a link fails or needs to be revoked, the rollback mechanism can be triggered. After the start node is started, the process proceeds according to the pre-set path to the next link until all necessary approvals or service calls are completed.

[0054] 2) Process configuration and management: Support adding new approval steps and can specify participants, associated form attributes and execution methods for each step. This flexibility ensures that even rapidly changing business requirements can be quickly responded to without redeveloping or deploying the application.

[0055] S3, Service orchestration

[0056] 1) Service orchestration definition: Service orchestration is a technology architecture pattern that organizes multiple independent services according to specific business logic and workflows, coordinates their interactions to complete complex business operations. A service orchestration can implement an application scenario. The advantage is that business processes are visualized, monitored, and complex transaction management is simplified.

[0057] 2) Service orchestration management: Provide a management page for users to add service orchestrations, configure interfaces and other logic to automatically execute related services when certain conditions are met.

[0058] S4, Process matter rule engine usage

[0059] After configuring the matter engine, process, service orchestration, click the button to get the matter engine form according to the matter code and parameters, and jump to the form value configuration page. After operating on the form page, get the execution method according to the form code and other parameters.

[0060] If the execution method type is process, it is the starting node of the process, automatically pushes the process to the next approval node, and lets the participants perform the audit operation. If the node is configured with a service orchestration, the corresponding service orchestration is called, and the execution is ended at the end node. If the execution method type is orchestration, the corresponding service orchestration is executed, and the execution is ended after success.

[0061] In the embodiment one, a system for implementing a process matter rule engine based on a trusted data space is provided, comprising:

[0062] Matter engine definition module: used to identify the form information related to the matter through the unique identification of the business scenario matter code and name;

[0063] Form definition module: used to define the form, the form includes code, name and value, wherein the form value is not limited to the page path, but also includes the required parameters for jumping;

[0064] Execution method definition module: used to define the execution method, the execution method is divided into two categories of process and service orchestration, each method has a unique code, name and type, and selects the corresponding execution method according to the form value and preset rules;

[0065] Rule definition module: used for defining rules, which are composed of attributes, operators and rule values, for determining which form to trigger or method to execute under certain conditions;

[0066] Dynamic adjustment interface module: provides an intuitive interface to allow administrators to dynamically adjust the relationship between the matter engine, the process and the service orchestration without writing code to modify the business logic.

[0067] It also includes a process configuration and management module, which includes: a process definition submodule: used for defining processes, which are business processing procedures composed of multiple links, each link containing specific forms and approval logic; supports adding new approval links and can specify participants, associated form attributes and execution methods for each link; the process supports dynamic expansion, including branch condition judgment, parallel processing, sub-process nesting and rollback mechanism in abnormal situations, so that even complex business processes can be easily managed and adjusted; at the same time, a visual interface is provided to allow users to quickly create and configure process basic information and links by dragging and dropping components; a process adjustment submodule: used for dynamically adjusting running processes without affecting completed links, such as adding new links, modifying branch conditions or redistributing participants.

[0068] It also includes a service orchestration module, which includes: a service organization coordination submodule: used for organizing multiple independent services according to specific business logic to coordinate interaction to complete complex business operations; a service orchestration management submodule: provides a management page for users to add service orchestrations, configure interfaces and other logic to automatically execute related services when certain conditions are met, ensuring efficient collaboration across system interfaces.

[0069] It also includes a process matter rule engine usage module, which includes: a form acquisition and jump submodule: used to acquire matter engine forms according to matter codes and parameters and jump to the page configured by form values; an execution method acquisition submodule: used to acquire execution methods according to form codes and other parameters after operations on the form page.

[0070] It also includes a process matter rule engine usage module, which specifically includes: a process execution submodule: if the execution method type acquired by the execution method acquisition submodule is a process, it will proceed from the current start node to the next approval node until the end node; a service orchestration execution submodule: if the execution method type acquired by the execution method acquisition submodule is a service orchestration, it will directly execute the corresponding service orchestration until it is successfully completed.

[0071] Although embodiments of the present application have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made therein without departing from the principles and spirit of the application, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for implementing a process item rule engine based on a trusted data space, characterized in that: include: Define the item engine: Identify form information related to an item by using an item code and name that uniquely identifies the business scenario; Form definition: includes code, name and value. Form values ​​are not limited to page paths, but also include parameters required for redirection; Execution method definition: Divided into two main categories: process and service orchestration. Each method has a unique code, name, and type. The corresponding execution method is selected based on form values ​​and preset rules. Rule definition: Consists of attributes, operators, and rule values, used to determine which form or method to trigger under specific conditions; Provides an intuitive interface: Allows administrators to dynamically adjust the relationship between the event engine, processes, and service orchestration, and modify business logic without writing code.

2. The implementation method of a process item rule engine based on trusted data space according to claim 1, characterized in that: It also includes process configuration and management, specifically: Process definition: A business process consisting of multiple steps, each containing specific forms and approval logic; supports adding new approval steps, and specifying participants, associated form attributes, and execution methods for each step; the process supports dynamic expansion, including branch condition judgment, parallel processing, nested sub-processes, and rollback mechanisms in case of exceptions; a visual interface is provided for process configuration, allowing users to quickly create and configure basic process information and steps by dragging and dropping components; Process Adjustment: Without affecting completed steps, the running process can be dynamically adjusted, such as adding new steps, modifying branch conditions, or reassigning participants.

3. The implementation method of a process item rule engine based on trusted data space according to claim 2, characterized in that: This also includes service orchestration: Multiple independent services are organized and coordinated to complete complex business operations according to specific business logic; a management page is provided so that users can add service orchestrations, configure interfaces and other logic to automatically execute related services when specific conditions are met, ensuring efficient collaboration of cross-system interfaces.

4. The implementation method of a process item rule engine based on trusted data space according to claim 3, characterized in that: This also includes the use of the process item rules engine: The system retrieves the event engine form based on the event code and parameters, and redirects the user to the page configured with the form values. After performing operations on the form page, the system retrieves the execution method based on the form code and other parameters.

5. The implementation method of a process item rule engine based on trusted data space according to claim 4, characterized in that: After obtaining the execution method: If the execution method type is a process, it will proceed from the current start node to the next approval node and then to the end node; if the execution method type is a service orchestration, it will directly execute the corresponding service orchestration until it is successfully completed.

6. A system for implementing a process item rule engine based on a trusted data space as described in claim 5, characterized in that: include: Item Engine Definition Module: Used to identify form information related to an item by using an item code and name that uniquely identifies the business scenario; Form definition module: Used to define forms. Forms include codes, names, and values. The form values ​​are not limited to page paths, but also include parameters required for navigation. Execution Method Definition Module: Used to define execution methods. Execution methods are divided into two main categories: process and service orchestration. Each method has a unique code, name, and type, and the corresponding execution method is selected based on form values ​​and preset rules. The rule definition module is used to define rules. A rule consists of attributes, operators, and rule values, and is used to determine which form or execution method is triggered under specific conditions. Dynamically Adjustable Interface Module: Provides an intuitive interface that allows administrators to dynamically adjust the relationship between the event engine, processes, and service orchestration, modifying business logic without writing code.

7. The system according to claim 6, characterized in that: It also includes a process configuration and management module, which includes: The process definition submodule is used to define processes, which are business processes consisting of multiple stages. Each stage contains specific forms and approval logic. It supports adding new approval stages and allows specifying participants, associated form attributes, and execution methods for each stage. Processes support dynamic expansion, including branch condition judgments, parallel processing, nested subprocesses, and rollback mechanisms in case of exceptions, making even complex business processes easy to manage and adjust. It also provides a visual interface that allows users to quickly create and configure basic process information and stages by dragging and dropping components. The process adjustment submodule is used to support dynamic adjustments to a running process without affecting completed steps, such as adding new steps, modifying branch conditions, or reassigning participants.

8. The system according to claim 7, characterized in that: It also includes a service orchestration module, which includes: Service organization and coordination submodule: Used to organize and coordinate multiple independent services according to specific business logic to complete complex business operations; Service Orchestration Management Submodule: Provides a management page that allows users to add service orchestrations, configure interfaces and other logic to automatically execute related services when specific conditions are met, ensuring efficient collaboration across system interfaces.

9. A system according to claim 8, characterized in that: It also includes a module used by the process item rules engine, which includes: Form retrieval and redirect module: used to retrieve the item engine form based on the item code and parameters and redirect to the page configured with the form values; The execution method retrieval submodule is used to retrieve the execution method based on the form code and other parameters after an operation is performed on the form page.

10. A system according to claim 9, characterized in that: It also includes a module for using the process item rules engine, specifically including: Process execution submodule: If the execution method type obtained by the execution method acquisition submodule is process, then proceed from the current start node to the next approval node until the end node; Service orchestration execution submodule: If the execution method type obtained by the execution method acquisition submodule is service orchestration, then the corresponding service orchestration will be executed directly until it is successfully completed.

Images