Process method taking event trigger as core

Abstract

The invention discloses a process method taking an event trigger as a core, and relates to the technical field of event triggering and process engines, and the process method comprises the following steps: S1, each form and each process node have a state, the change of the state triggers a corresponding action so as to push the progress of the process, and S2, the action is a response to the change of the state, so that the progress of the process is promoted. The state change is automatically executed and manually operated by a user, the automatic execution comprises notification sending and database updating, the manual operation of the user comprises form approval and filling, and S3, a tool box comprising predetermined actions and user-defined actions is introduced, and the predetermined actions comprise a process designer with a dragging function. Through the visual process designer and simple dragging operation, the use threshold of a process management tool is remarkably reduced, codes do not need to be written, and a user without a technical background can easily and rapidly design and configure the business process.

Description

Technical Field

[0001] The present invention relates to the technical field of event triggering and process engine, and in particular to a process method with an event trigger as the core. Background Art

[0002] There are many business process management software on the market that are built based on the BPMN2.0 business model. It has a graphical modeling process, but the model is too complex and requires users to have a certain technical background and programming knowledge. The learning curve is steep. It takes a lot of time and effort to configure and debug these tools. In addition, it is a non-visual process definition method. When using XML, it is often necessary to have a technical background such as computer development to implement it. It cannot be used for ToC-level products. This problem is solved by using semantic process definitions, but it is still too complex for users and requires a long time to configure. In terms of integrated configuration, many process management tools face great challenges when integrating with other systems or platforms. Even though some tools such as ProcessMaker provide APIs and third-party integration support, implementing these integrations usually requires advanced programming skills and a deep technical background.

[0003] Today's workflow design software is mainly divided into two categories, workflow editors and business flow editors. Workflow editors are mainly responsible for workflow definition, and business flow editors are mainly used to define action execution paths. Existing workflow editors on the market include teambition's workflow editor. Teambition's solution is to display business flow editing separately with a new drawing board, while traditional business flow editors are mainly based on the BPMN2.0 standard and related technologies such as the front-end bpmn.js library and the back-end flowable process engine library. The BPMN standard aims to define the flow of business, that is, the flow of actions, and cannot define the state flow of workflows. Summary of the invention

[0004] The purpose of the present invention is to provide a process method with event triggers as the core to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solution: a process method with event trigger as the core, comprising the following steps:

[0006] S1. Each form and process node has a state. Changes in the state trigger corresponding actions, thereby promoting the progress of the process.

[0007] S2, actions are responses to state changes, which include automatic execution and manual user operations. Automatic execution includes sending notifications and updating databases, and manual user operations include approval and filling out forms.

[0008] S3. Introduce a toolbox including pre-defined actions and custom actions. Pre-defined actions include a process designer with a drag function. Users design processes through the process designer through a visual interface. Custom actions refer to users customizing new states and actions to meet specific business needs.

[0009] S4. In the process designer, users can define different states, each with a unique identifier and description for identification and use in business processes;

[0010] S5. Change status and trigger actions based on event triggering mechanism;

[0011] S6. Based on the MyFlow process standard, the business process is defined as four elements: state, activity, gateway and auxiliary. The business process includes the development of front-end drawing components and the development of back-end process engines.

[0012] Preferably, in step S3, the functional design of the process designer includes a drag-and-drop interface, nodes and connecting lines, and a real-time preview, including the following steps:

[0013] S301. The user can drag states and actions from the process designer to the design canvas by dragging and dropping, and connect the states and states, states and actions, and actions and states corresponding to each form and process node by connecting lines to form a complete business process;

[0014] S302, each node represents a state or action, and a connecting line represents a transition between states or a trigger of an action. The user can edit the properties of a state or action and the properties of a transition between states or a trigger of an action by clicking on the node and the connecting line;

[0015] S303. The process designer has a real-time preview function, and users can view and test the operation of the business process at any time.

[0016] Preferably, in step S4, the state-state, state-action, and action-state connection operations are specifically:

[0017] S401, when a state is connected to another state, it means that the former state can be manually executed to the latter state;

[0018] S402: When a state is actively connected to an action, it means that the state can automatically or manually execute the action;

[0019] S403. When the action is actively connected to the state, it means that after the action is executed, the form will be set to the state.

[0020] Preferably, in step S5, the event triggering mechanism includes the following steps:

[0021] S501, by setting an event listener to monitor and capture events such as state changes and user operations, when an event is triggered, the event listener performs corresponding actions according to pre-defined trigger conditions and execution logic;

[0022] S502. Each action has a trigger condition and execution logic. When a state changes, the corresponding action is triggered and a notification is sent to the relevant approval personnel.

[0023] Preferably, in step S5, the event triggering mechanism further comprises the following steps:

[0024] S503. All states, actions and process configurations will be stored in the database to ensure data persistence and consistency. Users can integrate business process management tools with business systems by using rich APIs and integration interfaces to achieve data sharing and interoperability.

[0025] Preferably, in step S6, the state is used to represent the current state of the task, and the state node is connected to other state nodes by a straight directed arrow, indicating that the former state can flow to the latter state, and is connected to the activity node by a dotted directed arrow, representing the activity that needs to be performed when the task flows to this state. The activity is the basic unit of the business flow and represents the business itself in the business flow. The gateway represents a logic gate and is used to determine the branch of the business flow. The MyFlow process standard uses different legends to distinguish between workflow definitions and business flow definitions.

[0026] Preferably, in step S6, the development of the front-end drawing component includes graphics rendering, graphical editing, and XML import and export, including the following steps:

[0027] S601, rendering the XML description file under the MyFlow process standard into a graphical flow chart, and displaying it in the browser;

[0028] S602. Graphically edit the MyFlow process standard model in the browser. The user can add nodes and connecting lines by dragging and dropping to modify the business process structure.

[0029] S603, exporting the flowchart under the MyFlow process standard as an XML file, and importing and displaying the flowchart under the MyFlow process standard from the XML file.

[0030] Preferably, in step S6, the development of the backend process engine includes process engine and process splitting, including the following steps:

[0031] S611, the process engine first needs to parse and verify the XML file uploaded by the front end, and convert the XML process definition into the logic of the process definition model used inside the engine;

[0032] S612. Split the workflow definition and business flow definition based on the auxiliary elements defined in the MyFlow process standard. First, the engine will determine whether the task in the previous state can flow to the next state based on the business process definition. Secondly, the engine will create business flow deployment objects according to the business flow associated with each state node. When the task flows to the next state, the corresponding business process is automatically deployed and triggered, otherwise it continues to wait for the state to be triggered.

[0033] Compared with the prior art, the present invention has the following beneficial effects:

[0034] 1. Lower the threshold for use: Through the visual process designer and simple drag-and-drop operation, the threshold for using process management tools is significantly lowered. No code needs to be written, so that users without technical background can easily get started and quickly design and configure business processes;

[0035] 2. Improve efficiency and flexibility: The state and action mechanism of the present invention makes the design and modification of the process more flexible. Users can quickly adjust the process according to actual business needs, which significantly improves work efficiency.

[0036] 3. Enhanced scalability and customizability: Through the customization function of the toolbox, the present invention allows users to flexibly add, delete and modify states and actions according to specific business scenarios, thereby enhancing the scalability and customizability of the process management tool;

[0037] 4. Improve user experience: The present invention significantly improves user experience by providing an intuitive and easy-to-use visual interface and a friendly user interaction design, making the process management tool not only powerful but also easy to use;

[0038] 5. Simplify the process: Through the development of front-end drawing components and back-end process engines, the steps of defining enterprise processes can be simplified. With the help of MyFlow process standards, enterprise process solutions can be quickly implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A flow chart of the overall method provided by an embodiment of the present invention;

[0040] Figure 2 A flow chart of a business process design method provided by an embodiment of the present invention;

[0041] Figure 3 A flowchart of a task in state A provided by an embodiment of the present invention;

[0042] Figure 4 A flowchart of a task flow to state B provided in an embodiment of the present invention;

[0043] Figure 5 This is the flowchart required under the MyFlow process standard provided in the embodiment of the present invention. DETAILED DESCRIPTION

[0044] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0045] See also Figure 1-5 The present invention provides a technical solution: a process method with an event trigger as the core, comprising the following steps:

[0046] S1. Each form and process node has a state. Changes in the state trigger corresponding actions, thereby promoting the progress of the process.

[0047] S2, actions are responses to state changes, which include automatic execution and manual user operations. Automatic execution includes sending notifications and updating databases, and manual user operations include approval and filling out forms.

[0048] S3. Introduce a toolbox including pre-defined actions and custom actions. Pre-defined actions include a process designer with a drag function. Users design processes through the process designer through a visual interface. Custom actions refer to users customizing new states and actions to meet specific business needs.

[0049] S4. In the process designer, users can define different states, each with a unique identifier and description for identification and use in business processes;

[0050] S5. Change status and trigger actions based on event triggering mechanism;

[0051] S6. Based on the MyFlow process standard, the business process is defined as four elements: state, activity, gateway and auxiliary. The business process includes the development of front-end drawing components and the development of back-end process engines.

[0052] Specifically, in the process designer, the approval process can have statuses such as "pending approval", "under approval", "approved", and "rejected". Each status has a unique identifier and description for easy identification and use in the process;

[0053] Provides a visual interface that allows users to view, edit, add, and delete states. The definition and management of states are the basis of process configuration. Through flexible state management, users can adapt to various business needs.

[0054] In step S3, the functional design of the process designer includes a drag-and-drop interface, nodes and connection lines, and a real-time preview, including the following steps:

[0055] S301. The user can drag states and actions from the process designer to the design canvas by dragging and dropping, and connect the states and states, states and actions, and actions and states corresponding to each form and process node by connecting lines to form a complete business process;

[0056] S302, each node represents a state or action, and a connecting line represents a transition between states or a trigger of an action. The user can edit the properties of a state or action and the properties of a transition between states or a trigger of an action by clicking on the node and the connecting line;

[0057] S303. The process designer has a real-time preview function, and users can view and test the operation of the business process at any time;

[0058] In step S4, the operations of connecting states and states, states and actions, and actions and states are specifically as follows:

[0059] S401, when a state is connected to another state, it means that the former state can be manually executed to the latter state;

[0060] S402: When a state is actively connected to an action, it means that the state can automatically or manually execute the action;

[0061] S403, when the action is actively connected to the state, it means that after the action is executed, the form will be set to the state;

[0062] In step S5, the event triggering mechanism includes the following steps:

[0063] S501, by setting an event listener to monitor and capture events such as state changes and user operations, when an event is triggered, the event listener performs corresponding actions according to pre-defined trigger conditions and execution logic;

[0064] S502. Each action has a trigger condition and execution logic. When a state changes, the corresponding action is triggered and a notification is sent to the relevant approval personnel.

[0065] Specifically, when a status changes to "under review", a notification action is triggered to send a notification to the relevant reviewers;

[0066] S503. All states, actions and process configurations will be stored in the database to ensure data persistence and consistency. Users can integrate business process management tools with business systems by using rich APIs and integration interfaces to achieve data sharing and interoperability. Process management tools can be integrated with the company's ERP system, CRM system, AI triggers, etc. to optimize the overall efficiency of business processes.

[0067] In step S6, the state is used to represent the current state of the task. The state node is connected to other state nodes through a straight directed arrow, indicating that the former state can flow to the latter state. The dotted directed arrow is connected to the activity node, representing the activity that needs to be performed when the task flows to this state. The activity is the basic unit of the business flow and represents the business itself in the business flow. The gateway represents a logic gate and is used to determine the branch of the business flow. The MyFlow process standard uses different legends to distinguish between workflow definitions and business flow definitions;

[0068] In step S6, the development of the front-end drawing component includes graphics rendering, graphical editing, and XML import and export, including the following steps:

[0069] S601, rendering the XML description file under the MyFlow process standard into a graphical flow chart, and displaying it in the browser;

[0070] S602. Graphically edit the MyFlow process standard model in the browser. The user can add nodes and connecting lines by dragging and dropping to modify the business process structure.

[0071] S603, exporting the flowchart under the MyFlow process standard as an XML file, and importing and displaying the flowchart under the MyFlow process standard from the XML file;

[0072] In step S6, the development of the backend process engine includes the process engine and process splitting, including the following steps:

[0073] S611, the process engine first needs to parse and verify the XML file uploaded by the front end, and convert the XML process definition into the logic of the process definition model used inside the engine;

[0074] S612. Split the workflow definition and the business flow definition based on the auxiliary elements defined in the MyFlow process standard. First, the engine determines whether the task in the previous state can flow to the next state based on the business process definition. Secondly, the engine creates business flow deployment objects according to the business flow associated with each state node. When the task flows to the next state, the corresponding business process is automatically deployed and triggered. Otherwise, the waiting state continues to be triggered.

[0075] The MyFlow process standard will be based on the modification, integration, and addition of some or all of the concepts in the BPMN 2.0 standard. BPMN2.0 divides the elements of the business process diagram into the following four categories: activities, events, gateways, and auxiliary. Activities are the basic units of business flow and represent the business itself in the business flow. Events represent events that may be triggered in the business process and can be used to trigger or capture. Gateways represent logic gates and are used to determine the branches of the business flow. Auxiliary defines the form of the flow and is represented by directed lines, which can represent message flows or sequential flows.

[0076] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0077] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A process method with event trigger as the core, characterized in that: The following steps are involved: S1. Each form and process node has a state. Changes in the state trigger corresponding actions, thereby promoting the progress of the process. S2, actions are responses to state changes, which include automatic execution and manual user operations. Automatic execution includes sending notifications and updating databases, and manual user operations include approval and filling out forms. S3. Introduce a toolbox including pre-defined actions and custom actions. Pre-defined actions include a process designer with a drag function. Users design processes through the process designer through a visual interface. Custom actions refer to users customizing new states and actions to meet specific business needs. S4. In the process designer, users can define different states, each with a unique identifier and description for identification and use in business processes; S5. Change status and trigger actions based on event triggering mechanism; S6. Based on the MyFlow process standard, the business process is defined as four elements: state, activity, gateway and auxiliary. The business process includes the development of front-end drawing components and the development of back-end process engines.

2. A process method based on event triggers according to claim 1, characterized in that: In step S3, the functional design of the process designer includes a drag-and-drop interface, nodes and connecting lines, and real-time preview, including the following steps: S301. The user can drag states and actions from the process designer to the design canvas by dragging and dropping, and connect the states and states, states and actions, and actions and states corresponding to each form and process node by connecting lines to form a complete business process; S302, each node represents a state or action, and a connecting line represents a transition between states or a trigger of an action. The user can edit the properties of a state or action and the properties of a transition between states or a trigger of an action by clicking on the node and the connecting line; S303. The process designer has a real-time preview function, and users can view and test the operation of the business process at any time.

3. A process method based on event triggers according to claim 2, characterized in that: In step S4, the state-state, state-action, and action-state connection operations are specifically as follows: S401, when a state is connected to another state, it means that the former state can be manually executed to the latter state; S402: When a state is actively connected to an action, it means that the state can automatically or manually execute the action; S403. When the action is actively connected to the state, it means that after the action is executed, the form will be set to the state.

4. A process method based on event triggers according to claim 1, characterized in that: In step S5, the event triggering mechanism includes the following steps: S501, by setting an event listener to monitor and capture events such as state changes and user operations, when an event is triggered, the event listener performs corresponding actions according to pre-defined trigger conditions and execution logic; S502. Each action has a trigger condition and execution logic. When a state changes, the corresponding action is triggered and a notification is sent to the relevant approval personnel.

5. A process method based on event triggers according to claim 4, characterized in that: In step S5, the event triggering mechanism further includes the following steps: S503. All states, actions and process configurations will be stored in the database to ensure data persistence and consistency. Users can integrate business process management tools with business systems by using rich APIs and integration interfaces to achieve data sharing and interoperability.

6. A process method based on event triggers according to claim 1, characterized in that: In step S6, the state is used to represent the current state of the task. The state node is connected to other state nodes through a straight directed arrow, indicating that the former state can flow to the latter state. The dotted directed arrow is connected to the activity node, representing the activity that needs to be performed when the task flows to this state. The activity is the basic unit of the business flow and represents the business itself in the business flow. The gateway represents a logic gate and is used to determine the branch of the business flow. The MyFlow process standard uses different legends to distinguish between workflow definitions and business flow definitions.

7. The process method based on event triggers according to claim 1 is characterized in that: In step S6, the development of the front-end drawing component includes graphics rendering, graphical editing, and XML import and export, including the following steps: S601, rendering the XML description file under the MyFlow process standard into a graphical flow chart, and displaying it in the browser; S602. Graphically edit the MyFlow process standard model in the browser. The user can add nodes and connecting lines by dragging and dropping to modify the business process structure. S603, exporting the flowchart under the MyFlow process standard as an XML file, and importing and displaying the flowchart under the MyFlow process standard from the XML file.

8. The process method with event trigger as the core according to claim 1 is characterized in that: In step S6, the development of the backend process engine includes the process engine and process splitting, including the following steps: S611, the process engine first needs to parse and verify the XML file uploaded by the front end, and convert the XML process definition into the logic of the process definition model used inside the engine; S612. Split the workflow definition and business flow definition based on the auxiliary elements defined in the MyFlow process standard. First, the engine will determine whether the task in the previous state can flow to the next state based on the business process definition. Secondly, the engine will create business flow deployment objects according to the business flow associated with each state node. When the task flows to the next state, the corresponding business process is automatically deployed and triggered, otherwise it continues to wait for the state to be triggered.

Images