CN114253542A

CN114253542A - Triggering and running method based on visual trigger and computer storage medium

Info

Publication number: CN114253542A
Application number: CN202111645704.0A
Authority: CN
Inventors: 曹中余; 罗义; 张剑卿; 黎风顺; 吴迪
Original assignee: Chongqing Yuncheng Internet Technology Co Ltd
Current assignee: Chongqing Yunfeng Technology Co ltd
Priority date: 2021-12-30
Filing date: 2021-12-30
Publication date: 2022-03-29
Anticipated expiration: 2041-12-30
Also published as: CN114253542B

Abstract

The invention relates to a visual trigger-based triggering and running method, which comprises the following steps: presetting a trigger mode and a corresponding trigger condition, analyzing the trigger mode from a trigger node after starting a trigger, if the analyzed trigger mode is form trigger, and the action type of the trigger action and the corresponding form ID are the same as the trigger action type and the form ID set by the trigger condition, or the analyzed trigger mode is time trigger, and whether the time for starting the trigger reaches the timing time, triggering the trigger, and executing the action of each node step by step from the trigger node according to the parent-child relationship. In the invention, the form triggering and the time triggering can be realized by setting the triggering node and configuring the triggering logic of the trigger at the triggering node, the triggering condition configuration is flexible, the method can be adapted to various different triggering scenes, the universality is good, and the node of the trigger can be conveniently adjusted according to the service requirement.

Description

Triggering and running method based on visual trigger and computer storage medium

Technical Field

The invention belongs to the technical field of industrial internet management platforms, and relates to a visual trigger-based triggering and operating method and a computer storage medium.

Background

Industrial internet platforms often require data flow configuration and orchestration on pages, requiring the use of a large number of triggers. In a traditional development mode, a trigger is configured once, trigger logic is executed according to initial configuration all the time, the initial configuration cannot meet the requirements of new services along with the development of services and the iteration of functions, and when an enterprise involves a large amount of service changes, the trigger needs to be reconfigured according to the traditional configuration.

However, if the reconfiguration is performed on the conventional configuration, there are more problems, such as: the traditional trigger needs to be reconfigured after the service is changed, so that the traditional trigger cannot be directly modified and iterated in the old trigger, and the labor cost is increased. When the trigger is reconfigured, the traditional trigger has no visual interface, the whole operation process of the trigger cannot be foreseen, the configuration is difficult and the error rate is high. In addition, in the traditional trigger mode, one execution action is applied to all enterprises, and flexible loading and execution actions cannot be realized according to the requirements of the enterprises. Therefore, the existing trigger cannot directly perform iteration and modification according to the service change, has poor flexibility, cannot adapt to the diversification of enterprise requirements, and has poor universality.

Disclosure of Invention

In view of the above, the present invention provides a visual trigger-based triggering and operating method and a computer storage medium.

In order to achieve the purpose, the invention provides the following technical scheme:

a visual trigger-based triggering and running method comprises the following steps:

s1, setting a trigger mode and a corresponding trigger condition in a trigger node of the trigger in advance, wherein the trigger mode comprises form trigger and time trigger; when the trigger mode is form trigger, the trigger condition comprises trigger action type and form ID; when the triggering mode is timing triggering, the triggering condition comprises timing time;

s2, starting a trigger, analyzing a trigger mode from the trigger node, executing the step S3 when the analyzed trigger mode is form trigger, and executing the step S4 when the analyzed trigger mode is time trigger;

s3, detecting the trigger action, judging whether the action type of the trigger action and the corresponding form ID are the same as the trigger action type and the form ID set by the trigger condition, and executing the step S5 if the action type of the trigger action and the corresponding form ID are the same as the trigger action type and the form ID set by the trigger condition;

s4, detecting whether the time for starting the trigger reaches the timing time, and executing the step S5 if the time reaches the timing time;

and S5, executing the actions of each node from the trigger node to the end node step by step according to the parent-child relationship.

Further, the trigger condition further includes a type of the form, the type of the form includes an object form and a flow form, and when the type of the form is the object form, the step S3 includes the following sub-steps:

s311, when the form data is changed, the form service sends an MQ message to the trigger, wherein the MQ message comprises the form ID of the changed data form, the enterprise ID of the enterprise to which the form belongs and the executed action type;

s312, after the trigger receives the MQ message, the form ID and the enterprise ID are analyzed from the MQ message, whether the trigger of the form in the enabled state exists under the enterprise is inquired, and if the trigger exists, the step S313 is executed;

s313, the trigger parses the action type from the MQ message, and if the parsed action type is consistent with the trigger action type set by the trigger node, step S5 is executed.

Further, the trigger condition further comprises a trigger field and a data filtering rule; in the step S311, the MQ message sent by the form service to the trigger further includes the changed form data; in the step S313, when the analyzed action type is consistent with the trigger action type set by the trigger node, the following steps are performed before the step S5 is performed:

s314, the trigger analyzes the changed field of the form and the changed data of the field from the MQ message, and detects whether the changed field is a trigger field; when the changed field is the trigger field, executing the step S315;

s315, checking whether the data of the trigger field meets the data filtering rule, and executing the step S5 when the data meets the data filtering rule.

Further, when the type of the form is a flow form, before executing step S311, the following steps are also executed:

s301, a flow form is created in the flow, when a new flow is initiated, a piece of data is newly added in the flow form, each item of the flow corresponds to a field of the flow form, and when the items of the flow are processed, the data of the corresponding field in the flow form is edited.

Further, the step of S4 includes the following substeps:

s411, when the trigger is started, firstly analyzing whether a trigger node of the trigger is timed trigger, and if the trigger node is timed trigger, calculating the trigger time according to the starting time of the trigger and the set timing time;

s412, when the current moment is detected to be the trigger moment, the timing server sends a timing callback request to the trigger, wherein the timing callback request comprises the latest parameter information configured by the trigger;

s413, when the trigger receives the timing callback request, re-acquiring the configuration parameters of the trigger, and executing step S5.

Further, the following steps are also performed before forming the trigger:

sa1, predefining a list set of key-value structures;

after forming the trigger, the following steps are also executed:

sa2, setting an exception handling mechanism of a trigger, wherein the exception handling mechanism comprises an interruption operation mechanism and a continuation operation mechanism; the continuous operation mechanism is used for finishing the action of the current node and continuously operating the next node of the trigger when the execution of the node is abnormal; the operation stopping mechanism is used for storing the node operation data in the list set into the database and deleting the list set when the execution of the node is abnormal; executing a rerun mechanism according to needs, creating a list set in a memory, writing data from a database back to the list set, and continuing to run from a stopped node;

the step of S5 further includes the steps of:

s531, when the trigger is triggered, generating a trigger running log in a database; creating the list set in the memory to store the running data of the trigger node, wherein the key is the node ID of the node; the value is the running data of the node, and comprises a form ID of a form called when the node runs, a field ID of a field operated when the node runs, and data corresponding to the field after the node runs;

s532, when the trigger runs abnormally, executing an abnormal processing mechanism, and writing abnormal data into the trigger running log, wherein the trigger running log is used for displaying the running condition of the trigger and the running data of each node in a visual mode after analysis; if the operation exception does not occur, the node is considered to be successfully executed, and the operation data of the node is recorded in the list set for the subsequent node to call; and writing the node operation data in the list set into the trigger operation log.

Further, the method also comprises the following steps:

s901, creating a trigger node and forming configuration parameters of the trigger node, wherein the trigger node is used for running a trigger when a trigger action meets a trigger condition, and the configuration parameters of the trigger node are used for configuring the trigger condition of the trigger;

s902, decomposing the execution action of the trigger operation overall process into a plurality of independent basic logic actions, respectively creating at least one action node corresponding to each basic logic action, and forming configuration parameters of each action node, wherein the configuration parameters of the action nodes are used for configuring parameters required by the action node to execute the action;

s903, creating an end node, wherein the end node is used for ending the trigger operation;

the action node comprises a data acquisition node, a data processing node, a notification node and a manual filling node according to the executed action;

the data acquisition node is used for acquiring one or more pieces of data meeting the data filtering rule from the specified form; the configuration parameters comprise the form name of the acquired data, the name of the trigger field and the data filtering rule;

the data processing node is used for automatically adding, deleting or modifying the data of the form in the front node according to the set parameters; the configuration parameters comprise form ID and field name of the preposed node needing data processing; when new adding or modifying operation is executed, the configuration parameters also comprise assignment rules when data is added or modified;

the notification class node is used for sending a notification message to a specified user in a specified mode; the configuration parameters comprise a notification sending mode and a notification receiving object name;

the manual filling node is used for adding a new piece of data in the form in a manual filling mode, and the configuration parameters of the manual filling node comprise the form name of the filled data and the user name with filling authority.

Further, the step S902 further includes the steps of:

s9021, creating a parallel branch node; the parallel branch nodes comprise branch operation nodes, branch nodes and branch combination nodes, wherein the branch operation nodes are used for dividing one execution flow into two or more branch execution flows, each branch execution flow is provided with one branch node, and the branch nodes are used for setting data filtering rules of execution branches; when the data filtering rule is satisfied, executing the branch flow where the branch node is located, otherwise, not executing the branch flow where the branch node is located; the branch combination nodes are in one-to-one correspondence with the branch operation nodes and are used for converging the branch execution flows of the branches of the corresponding branch operation nodes into one execution flow.

Further, the method also comprises the following steps:

sc, pre-creating a node configuration drawer; the configuration drawer is internally provided with a plurality of action node configuration modules for executing different actions; the configuration drawer is also internally provided with a branch configuration module for configuring the parallel branch nodes;

and Sd, allocating a node ID number to each action node, allocating an enterprise ID number to each user, associating the node ID numbers of a plurality of action nodes in each enterprise ID number, generating icons of parallel branch nodes and associated action nodes in a node configuration drawer of the user corresponding to the enterprise ID number, and forming mapping between the icons and the corresponding action nodes.

A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the above-mentioned visual trigger-based triggering and running method.

In the invention, by setting the trigger node and configuring the trigger logic of the trigger at the trigger node, the form trigger and the time trigger can be realized, the trigger condition configuration is flexible, and the application range is wide; the action nodes depend on visual triggers, and the whole trigger configuration process can be predicted; because the action node of the trigger is not strongly associated with the trigger, a new trigger is not needed to be reconfigured when the service changes, and the action node of the old trigger can be immediately effective only by adding, deleting and editing the action node of the old trigger; the trigger is more flexible and changeable. In addition, by establishing the running data of the list set storage node in the memory, the running data of each node can be stored in the list set when the trigger is executed, when the running data of the preposed node needs to be called, the running data of any preposed node can be directly acquired from the list set to execute the assignment or filtering operation of the current node, and the running logic is flexible and convenient.

Drawings

For the purposes of promoting a better understanding of the objects, aspects and advantages of the invention, reference will now be made to the following detailed description taken in conjunction with the accompanying drawings in which:

fig. 1 is a flow chart of a preferred embodiment of the triggering and running method based on the visual trigger according to the present invention.

FIG. 2 is a flow diagram of creating trigger nodes, action nodes, and end nodes in a node repository.

FIG. 3 is a flow diagram of adding nodes to a visualization configuration canvas to form triggers.

FIG. 4 is a schematic diagram of a node added to a visualization configuration canvas.

FIG. 5 is a flow chart of form triggering.

FIG. 6 is a diagram of a device repair trigger.

In the figure: 101. trigger node, 102 add node operator, 103 delete operator, 104 action node, 105 branch operation node, 106 branch combination node, 107 branch node, 108 end node.

Detailed Description

The embodiments of the invention are explained below by means of specific examples, the illustrations provided in the following examples are merely illustrative of the basic idea of the invention, and features in the following examples and examples can be combined with one another without conflict.

The invention discloses a triggering and running method based on a visual trigger, which can realize form triggering and time triggering by setting a triggering node 101 and configuring the triggering logic of the trigger at the triggering node 101, has flexible triggering condition configuration, can adapt to various different triggering scenes and has good universality; and the execution actions of the action nodes 104 are independent from each other when the trigger runs, so that the nodes can be added and deleted and the node configuration can be modified conveniently on the existing trigger without changing the core running logic of the whole trigger or influencing the actions of other nodes, and the actions can be adjusted conveniently according to the service requirements.

As shown in fig. 1, a preferred embodiment of the triggering and running method based on the visual trigger of the present invention comprises the following steps:

s1, setting a trigger mode and a corresponding trigger condition in a trigger node 101 of the trigger in advance, wherein the trigger mode comprises form trigger and time trigger; when the trigger mode is form trigger, the trigger condition comprises trigger action type and form ID; when the triggering mode is timing triggering, the triggering condition comprises timing time.

Before executing the step S1, it is necessary to create the trigger node 101, the action node 104, and the end node 108 in the node repository, and then add nodes in the visualization configuration canvas in a stepwise manner according to the parent-child relationship to form a trigger with the trigger node 101 as an initial node and the end node 108 as a final node.

As shown in fig. 2, creating the trigger node 101, the action node 104, and the end node 108 in the node repository includes the following steps:

s901, creating the trigger node 101 in the node warehouse, and forming the configuration parameters of the trigger node 101. The node repository refers to a database for storing node codes. The trigger node 101 is configured to run a trigger when the trigger action meets a trigger condition, and the configuration parameter of the trigger node 101 is configured to configure the trigger condition of the trigger. The trigger condition is that: on the user application level, the user opens or triggers the switch of the trigger. Such as adding new data to a specified form, modifying data in a specified form, reaching a preset time, initiating a process (the process is created by relying on a process engine), processing a process backlog (when the process flow goes to a certain node, the event of the node is backlog if the process is not processed), and the like.

The configuration parameters of the trigger node 101 include a trigger mode and a corresponding trigger condition, where the trigger mode includes form triggering and timing triggering. When the trigger mode of the trigger node 101 is set as a timing trigger, the trigger condition includes a timing time; the trigger starts timing after being started, and triggers when the timing time reaches the set timing time.

When the trigger mode of the trigger node 101 is set as form trigger, the trigger condition includes a form ID and a trigger action type. For example: when new data is used as a trigger action type, when detecting that a certain form has user new data, triggering a corresponding trigger. When the modification data is used as the trigger action type, when a certain form data is detected to be modified, a corresponding trigger is triggered.

When the trigger condition needs to be more accurately defined, the trigger condition also comprises a trigger field and a data filtering rule; configuring the data filtering rules includes selecting a matching rule, selecting a filtering value type, and setting a filtering value. The matching rule is used for specifying a matching algorithm, and the filter value type is used for specifying a method for converting a filter value into a parameter of the matching rule; the filter value is used to obtain parameters of the matching rule (i.e., matching parameters). The matching rule may include: (match parameter) is null, (match parameter) is not null, equal to match parameter, not equal to match parameter, greater than or equal to match parameter, less than or equal to match parameter, within a range of two match parameters, equal to one of the plurality of match parameters. The filter value type comprises custom and variable fields; when the filter value type is self-defined, the required data is manually input to be used as the filter value. When the filter value type is a variable field, the field of the form in a front node is used as a target field, and the target field is used as a filter value.

S902, decomposing the execution actions of the trigger operation overall process into a plurality of independent basic logic actions (i.e. there is no intersection between the execution actions of the respective basic logic actions), respectively creating at least one action node 104 in the node warehouse corresponding to each basic logic action, and forming configuration parameters of each action node 104, where the configuration parameters of the action node 104 are used to configure parameters required by the execution action corresponding to the action node 104. The action node 104 is divided into an acquisition data class node, a data processing class node, a notification class node and a manual filling node according to executed actions.

The data acquiring class node is configured to acquire one or more pieces of data satisfying the data filtering rule from a specified form (i.e., a data table, each data table has an independent ID number, the form can be specified by the ID number of the data table, or the form can be specified by the name of the data table), for example: acquiring a data single node; the configuration parameters comprise the form name of the acquired data, the name of the trigger field and the data filtering rule. The configuration method of the data filtering rule is the same as that of the trigger node 101.

The data processing node is used for automatically adding, deleting or modifying the data of the form according to the set parameters, for example: adding data nodes, deleting data nodes and editing data nodes; the configuration parameters comprise forms and fields which need data processing (the column titles of a column of cells in the forms are the field names of the column of cells; each cell is also distributed with an independent field ID number, the column of cells of the forms can be appointed by the field names of the data tables, and one cell of the forms can also be appointed by the field ID); when a new or modified operation is performed, the configuration parameters thereof also include assignment rules when data is newly added or modified.

The assignment rules include field assignments, formula assignments, custom assignments, form assignments, and null value assignments. When field assignment is selected, selecting a field of a form as a target field from fields of forms of a preceding node (i.e. a node that may be executed before the node, such as a parent node of the node, a parent node of the node, etc.), and using the target field as an assignment parameter; therefore, during assignment, the running data of the node where the form of the target field is located can be called from the memory, and then the data assignment of the target field is found from the running data and is assigned to the assigned field. When a formula assignment rule is selected, displaying preset function formulas in an assignment parameter area, firstly selecting one function formula as a formula of the assignment rule, then setting each operation parameter of the function formula, taking a specified value as a parameter of the function formula or selecting a field of a form from form fields of front nodes as a target field, taking the target field as a parameter of the function formula, and taking the function formula containing the parameter as the assignment parameter; when assigning, the value of the parameter is operated through a function formula, and the operation result is assigned to the assigned field; when the parameter of the function formula is the designated value, directly taking the designated value as the value of the function parameter; when the parameter of the function formula is a form field (hereinafter referred to as a target field) of a front node, firstly, the running data of the node where the form of the target field is located is called from the memory, and then the data of the target field is found from the running data to be used as the value of the function parameter. By defining the assignment rule of formula assignment, the field data of the forms of a plurality of prepositive nodes can be called to carry out formula operation, and then the operation result is assigned to the field of the form of the execution node, or the field data of the forms of the prepositive nodes and the assigned value are subjected to formula operation, and then the operation result is assigned to the field of the form of the execution node, so that the assignment mode is more flexible.

When a user-defined assignment rule is selected, writing data needing to be assigned to an assigned field in an assignment parameter area, and taking the data written in the assignment parameter area as an assignment parameter; the assigned field is assigned with data written in the assigned parameter area.

And when the assignment rule is set as the form assignment rule, the default value of the assigned field is used as the assignment parameter assignment, and the default value of the assigned field is obtained and assigned to the assigned field.

When the assignment rule is set as a null value assignment rule, the null value is used as an assignment parameter, and the assigned field is directly assigned with the null value during assignment; so that the user can modify the field after determining its content.

The notification class node is configured to send a notification message to a specified user in a specified manner, for example: app notification nodes; the configuration parameters include the way of sending the notification and the name of the object receiving the notification.

In order to execute several branch flows in parallel or execute corresponding branch flows according to filtering conditions (i.e. data filtering rules), the step S902 may further include the following steps:

s9021, creating a parallel branch node 107 in the node warehouse; the parallel branch nodes 107 include branch operation nodes 105, branch nodes 107 and branch combination nodes 106, the branch operation nodes 105 are configured to divide one execution flow into two or more branch execution flows, each branch execution flow is provided with one branch node 107, and the branch nodes 107 are configured to set data filtering rules for executing branches; when the data filtering rule is satisfied, executing the branch flow where the branch node 107 is located, otherwise, not executing the branch flow where the branch node 107 is located; the branch combination nodes 106 correspond to the branch operation nodes 105 one to one, and are configured to merge the branch execution flows branched by the corresponding branch operation nodes 105 into one execution flow.

And S903, creating an end node 108 in the node warehouse, wherein the end node 108 is used for ending the trigger operation.

As shown in fig. 3, adding a node to the visualization configuration canvas to form a trigger may specifically include the following sub-steps:

s911, creating a trigger visualization configuration canvas so as to configure the execution flow of the trigger in a visual mode on the visualization configuration canvas.

S912, generating a trigger node 101 and an end node 108 in the visualization configuration canvas, and setting a trigger condition of a trigger in the trigger node 101.

S913, configuring a child node with a corresponding execution action between the trigger node 101 and the end node 108 according to the trigger condition, thereby forming a trigger execution flow from the trigger node 101 to the end node 108 through the child node.

In the present application, details are given in a state where all nodes configured between the trigger node 101 and the end node 108 are child nodes, and when it has a subordinate node, it is parent node of the subordinate node. The child nodes preferably include action nodes 104 and parallel branch nodes including two or more branches, each branch having branch nodes 107 and action nodes 104 with corresponding execution actions. In one embodiment, a plurality of child nodes are arranged in parallel between the trigger node 101 and the end node 108, and all of the child nodes are the same-level child nodes of the trigger node 101. In another embodiment, the trigger node 101 is used as a parent node or a root node, the end node 108 is used as a terminal node, and a plurality of child nodes are gradually arranged between the parent node and the terminal node from the parent node to the terminal node from the beginning to the end. Specifically, in combination with the example, it is assumed that the number of child nodes is five, that is, child node 1, child node 2, child node 3, child node 4, and child node 5, and the child node 1 is connected to the next stage of the trigger node 101, the child node 2 is connected to the next stage of the child node 1, the child node 3 is connected to the next stage of the child node 2, the child node 4 is connected to the next stage of the child node 3, and the child node 5 is connected between the child node 4 and the end node 108.

The configuration user may configure one or more parallel or serial action nodes 104 as a trigger to execute a flow based on the requirements and may also configure one or more parallel branch nodes as a trigger to execute a flow based on the requirements. The configuration of the action nodes 104 and the parallel branch nodes has no sequence, that is, a configuration user may preferentially configure the action nodes 104 or the parallel branch nodes based on a requirement, may also configure the parallel branch nodes between two serial action nodes 104, may also configure the parallel branch nodes below one branch node 107 of the parallel branch nodes, and the like. In summary, when independent actions need to be performed in sequence, the action node 104 may be configured, and when multiple actions need to be performed in parallel, parallel branch nodes may be configured, and then branch nodes 107 may be configured in each branch, respectively.

According to an aspect of the present invention, the step S913 specifically includes:

s9131, setting a child node attached below the parent node in the visual configuration canvas with the trigger node 101 as the parent node and the end node 108 as the end node, where the child node is located between the trigger node 101 and the end node 108.

In this step, the trigger node 101 is used as a child node added to the parent node, and the child node is a child node of the trigger node 101; another child node is added at the next level of a certain child node, and the added child node is taken as the child node of the previous level child node; thereby forming parent-child relationships. The action node 104 and each of the parallel branch nodes 107 are connected to their parent nodes, and the action node 104 and each of the parallel branch nodes 107 are connected to their child nodes.

As shown in fig. 4, in order to facilitate operations of adding or deleting child nodes and increase flexibility, operability and compatibility of the configuration of the trigger, an adding node operator 102 for configuring a user to add a child node may be provided between each child node and its parent node and between each child node and its child node, and a deleting operator 103 for configuring a user to delete the child node may be provided on each child node.

S9132, point to the end node 108 step by step from parent to child according to the parent-child relationship, and make the last-stage child node point to the end node 108, that is, the child node without the next-stage child node is taken as the parent node of the end node 108, so that the child node points to the end node 108, and a trigger execution flowchart is formed in the visual configuration canvas after the connection is performed according to the parent-child relationship.

In order to facilitate the selection of the corresponding child node according to the requirement, before the trigger visualization configuration canvas is created, the following steps may be further performed:

sc, pre-creating a node configuration drawer; the configuration drawer is used for selecting the nodes with mapping relations to be added to the visualization configuration canvas when the trigger is configured. The configuration drawer is internally provided with a plurality of action node configuration modules for executing different actions; the configuration drawer is also internally provided with a branch configuration module for configuring the parallel branch nodes.

And Sd, allocating a node ID number to each action node, allocating an enterprise ID number to each user, associating the node ID numbers of a plurality of action nodes in each enterprise ID number, generating icons of parallel branch nodes and associated action nodes in a node configuration drawer of the user corresponding to the enterprise ID number, and forming mapping between the icons and the corresponding action nodes in the action node warehouse. When adding action nodes, a user can only add action nodes mapped in the node configuration drawer. In this embodiment, when the visual configuration canvas is created, the trigger node and the end node are generated together with the visual configuration canvas without mapping, and the parallel branch nodes are set as the mandatory nodes and directly mapped in the node configuration drawer without reconfiguring the mapping relationship.

The specific method of the step S9131 is as follows:

adding configuration child nodes according to an adding node operator 102 between a trigger node 101 and the end node 108; i.e., clicking on add node operator 102 between trigger node 101 and end node 108 opens the configuration drawer. Then selecting a corresponding node configuration method according to whether two or more actions need to be executed in parallel:

(1) when only one action is executed at the same time, the action node configuration module corresponding to the executed action in the configuration drawer is selected according to the trigger condition, and the action node 104 is configured between the trigger node 101 and the end node 108, so as to form a first action node 104.

(2) When two or more actions need to be executed in parallel, the branch configuration module in the configuration drawer is selected according to the trigger condition to configure a first parallel branch node between the trigger node 101 and the end node 108.

And then, when the child nodes need to be added continuously, adding and configuring a second action node 104 and/or a second parallel branch node between the first action node 104 (or the first parallel branch node) and the trigger node 101 or between the first action node 104 (or the first parallel branch node) and the end node 108 according to requirements. Thereafter, action nodes 104 or parallel branch nodes may also continue to be added between action nodes 104 (or parallel branch nodes) and trigger nodes 101, between action nodes 104 (or parallel branch nodes) and end nodes 108, or between two action nodes 104 (or parallel branch nodes), and between action nodes 104 and parallel branch nodes, as desired.

The specific method for selecting the branch configuration module to configure the corresponding parallel branch node comprises the following steps:

the branch configuration module is first selected from the configuration drawer to trigger a parallel branch node configuration instruction.

Then a branch operation node 105 and a branch combination node 106 are configured at corresponding positions in the visual configuration canvas according to the configuration of the parallel branch nodes. The branch operation node 105 is configured to form a plurality of branches, and the branch combination node 106 is configured to combine the plurality of branches into one path.

Thereafter, two branches are generated in parallel between the branch operation node 105 and the branch combination node 106, and one branch node 107 is generated at a corresponding position in each branch.

And then judging whether the branch execution flow needs to be added or not, if so, enabling the branch operator of the corresponding branch operation node 105 to execute the task of adding the branch node, so as to add a branch node 107 between the corresponding branch operation node 105 and the branch combination node 106 in parallel. Because the two branches are fixedly generated in the mode, when the two branches do not meet the requirement, the branches can be continuously added by clicking a branch operator until the requirement is met.

Finally, the child nodes are configured for each branch in the manner of an action node 104 or a parallel branch node, such that the branch is assigned a corresponding execution action.

S914, setting parameters of each child node, and generating a trigger according to the parameters; the trigger takes the trigger execution flow chart as an execution basis, and executes the flow shown by the trigger flow chart step by step. That is, from the trigger node 101, corresponding actions are sequentially executed downward according to the trigger execution flow chart until the execution-to-end node 108108 completes the whole trigger execution flow. When a certain child node needs to be assigned, configuring an assignment rule of the child node based on the data requirement of the corresponding child node; so that the corresponding child node can assign the value to the corresponding field of the child node according to the assignment rule; and when the assignment rule needs to be assigned according to the running data after the execution of the front node, calling the running data of the front node from the memory, and assigning the corresponding field according to the running data and the set assignment rule.

And S2, starting a trigger, analyzing the trigger mode from the trigger node, executing the step S3 when the analyzed trigger mode is form trigger, and executing the step S4 when the analyzed trigger mode is time trigger.

S3, detecting the trigger action and judging whether the action type of the trigger action and the corresponding form ID are the same as the trigger action type and the form ID set by the trigger condition, if so, executing the step S5.

The triggering condition further comprises the type of a form, the type of the form comprises an object form and a flow form, and the object form is a common data form and is used for recording the working data of an enterprise; the flow form is a special form and is used for recording matters in the flow.

As shown in fig. 5, when the type of the form is an object form, the S3 step includes the following sub-steps:

s311, when the form data is changed, the form service sends an MQ message to the trigger, wherein the MQ message comprises the form ID of the form of the changed data, the enterprise ID of the enterprise to which the form belongs and the executed action type. MQ messages refer to the fact that an event occurs in a program language, and a message is sent to a service subscribed to the event, and a specific example of the MQ message is as follows:

s312, after the trigger receives the MQ message, the form ID and the enterprise ID are analyzed from the MQ message, whether the trigger of the form in the enabled state exists under the enterprise is inquired, and if the trigger exists, the step S503 is executed.

S313, the trigger analyzes the action type from the MQ message, and when the analyzed action type is consistent with the trigger action type set by the trigger node 101, the trigger action is judged to meet the trigger condition set by the trigger node 101; otherwise, it is determined that the trigger action does not satisfy the trigger condition set by the trigger node 101.

To set the trigger condition of the trigger more precisely, the configuration parameters of the trigger node 101 may further include data filtering rules; in the step S311, the MQ message sent by the form service to the trigger further includes the changed form data; in the step S313, when the analyzed action type is consistent with the trigger action type set by the trigger node 101, the following steps are performed before the step S5 is performed:

s315, checking whether the data of the trigger field meets the data filtering rule, and executing the step S5 when the data meets the data filtering rule, so that the trigger triggers and executes the next node; otherwise, the flip-flop does not trigger.

For example, when the trigger field of the specified form is "name", the matching rule of the data filtering rule is set to be "equal to the matching parameter", the filtering value type is "custom", and the filtering value is "Zhang III" in the trigger condition of the new added data; the trigger is triggered when the newly added data of the name field of the specified form is three, and the trigger cannot be triggered if the newly added data of the name field of the specified form is not three. It will be appreciated that the trigger field may be a date type field in the form, and the filter value may also be set to a date, in which case the trigger triggers when the trigger field of the form reaches the date on which the filter value is set.

In the form triggering mode, the process triggering can be compatible, and when the form type is a process form, before executing step S311, the following steps are further executed:

s301, a flow form is created in the flow, when a new flow is initiated, a piece of data is newly added in the flow form, each item of the flow corresponds to a field of the flow form, and when the to-do item of the flow is processed, the data of the corresponding field in the flow form is edited. Therefore, the initiating process corresponds to the newly added data of the object form, and the backlog of the processing process corresponds to the edited data of the object form. A date field can be set in the flow form to record the date in the flow, so that the trigger can be triggered by the flow in a form triggering mode.

When the trigger mode is set as the timing trigger, the step S4 includes the following sub-steps:

s411, when the trigger is started, whether the trigger node 101 of the trigger is timed trigger is firstly analyzed, and if the trigger node is timed trigger, the trigger time is calculated according to the starting time of the trigger and the set timed time.

S412, when it is detected that the current time is the trigger time, the timing server sends a timing callback request to the trigger, wherein the timing callback request includes the latest parameter information configured by the trigger.

S413, when the trigger receives the timing callback request, judging that the starting time of the trigger reaches the timing time; at this time, the configuration parameters of the trigger are first obtained again, and then the step S5 is executed to trigger the trigger and execute the next node.

And S5, executing the actions of each node from the trigger node 101 to the end node step by step according to the parent-child relationship.

In order to enable the action node 104 to call the operation data of the front node when executing the assignment rule or the data filtering rule, before forming the trigger, the following steps may also be executed:

sa1, a list set of key-value structures is predefined.

The step of S5 further includes the following steps:

s521, creating the list set in the memory to store the running data of the trigger node, wherein the key is the node ID of the node; the value is the running data of the node, and comprises a form ID of a form called when the node runs, a field ID of a field operated when the node runs, and data corresponding to the field after the node runs; when the operation of the trigger is finished, the corresponding list set is automatically deleted.

For example: adding a new piece of data to an employee information table (formStaff Info01) form at a newly added node (ID is addNode01), and assuming that three fields in the employee information table are 'name' (ID is nam e01), 'telephone' (ID is phone01) and 'address' (ID is address 01); when a newly added node is executed to add a piece of data with the name of "zhang san", the telephone number of "18933223355" and the address of "28 th of rising area in beijing city" to the employee information form, the operation data of the node in the list set is as follows:

when an assignment rule or a data filtering rule is executed and data of a target field needs to be called from a list set, a corresponding node is found from a first layer structure of the list set according to a nodeId (node ID of a front node where the target field is located), a corresponding form is found from a second layer structure of the node according to a formId (form ID of the form where the target field is located), corresponding fields and data are found from a third layer structure of the form according to an elementId (field ID of the target field), and the number of field values of the form corresponding to the current node can be accurately inquired according to the obtained nodeId, formId and elementId. For example: when the data of the telephone field in the employee information table of the newly added node is called, the newly added node is found from the list set according to the addNode01, the employee information table is found from the data of the newly added node according to the formStaffInfo01, the telephone field is found according to the telephone 01, and the data corresponding to the telephone field is read to obtain the telephone field 18933223355, namely the data of the target field.

Since the trigger is configured in the node manner in this embodiment, and the action nodes 104 of the trigger are not crossed in executing actions, that is, each action node 104 does not need to rely on another action node 104 when executing its logic action, when the service of the trigger needs to be adjusted, the configuration parameters can be directly added, deleted, and modified to the relevant action node 104, without affecting other action nodes 104, and the trigger can be immediately activated when the trigger is restarted, so that the trigger node can be directly changed on the existing trigger, the trigger can iterate along with the service quickly, and the trigger is more flexible and changeable.

The following description is made by an implementation, as shown in fig. 6, it is assumed that an equipment repair trigger is configured, a starting node is a trigger node 101, and a trigger condition of the trigger node 101 is set as a new record in an "equipment warranty" form; adding a newly-added data node as a child node under the trigger node 101, setting a form of the newly-added data as an 'equipment warranty record table', and setting the content of a field in the newly-added record as data of a related field in a newly-added record in the 'equipment warranty' form, so that a record can be newly added in the 'equipment warranty record table' form according to the content of the newly-added record in the 'equipment warranty record table'; adding an app notification node as a child node under the newly added data node, setting a notified person (assumed to be equipment maintenance personnel), a notification mode (assumed to be short message notification) and notification content in the app notification node, wherein the notification content can comprise data of a field related to fault content in an equipment warranty record table form, so that the equipment maintenance personnel can be notified of the fault content in the notification, and the equipment maintenance personnel can conveniently carry corresponding maintenance equipment; setting child nodes of the app notification nodes as manual filling nodes, setting filled forms as 'equipment maintenance forms', and setting users with filling authority as equipment maintenance personnel set by the app notification nodes; and finally, setting child nodes of the manual filling nodes as end nodes 108, and completing the configuration of the trigger.

When a record is newly generated in the 'equipment warranty' form, the trigger is triggered; firstly, generating a list set in a memory, and storing newly generated recorded data in an equipment warranty form in running data of a trigger node 101; then, the newly-added data node calls data of related fields in the 'equipment warranty' form from the list set, and a record is added in the 'equipment warranty record table' according to the called data; and then the app notification node sends a message notification to the configured equipment maintenance personnel, after receiving the notification, the equipment maintenance personnel can carry related equipment to arrive at the on-site maintenance equipment according to the fault phenomenon explained in the notification, and after the equipment maintenance is finished, the equipment maintenance list is filled in through the manual filling node, so that the execution of the one-time completely triggered operation process is finished.

Assuming that the current requirement changes due to the service requirement, and after the equipment maintenance order is filled in by the equipment maintenance staff, the equipment state in the equipment maintenance record table is required to be simultaneously modified (assuming that the newly added data node includes an equipment state field in the equipment maintenance record table), and an equipment maintenance completion message is required to be respectively sent to the supervisor and the equipment operator, the following two nodes can be continuously configured in the trigger:

(1) after the nodes are filled in manually, an edit data node is added as a child node (when a node is added behind the node, the newly added node is automatically set as a child node of the node and a parent node of the child node of the node to ensure the continuity of the parent-child relationship, namely, the end node 108 is automatically set as the child node of the added edit data node at the moment), and the form of edit data is configured as an equipment warranty record table, the edited field is in an equipment state, and the edited data content is in an already repaired state.

(2) After the data node is edited, an app notification node is added as a child node (at this time, the end node 108 is automatically set as the child node of the added app notification node), notified persons of the app notification node are set as device operators and supervisors, the notification mode is short message notification, and the notification content is "device maintenance is completed".

When the trigger is executed again, after a maintenance person fills in the equipment maintenance order, the equipment state of the equipment maintenance record table is modified into the maintained state, and a message of the current equipment maintenance completion is sent to inform the equipment operator and the supervisor.

Because the service requirement changes, two nodes are added in the original trigger to adapt to the change of the requirement, and because the nodes are independent and non-invasive, the two newly added nodes can not affect the original logics of repair reporting, message sending, maintenance record filling and the like, and certainly, if more processing logics are needed, the operation can be finished by only adding corresponding nodes and configuring corresponding conditions.

Suppose that at present, because of service change (for example, a repair report record is added to the trigger node 101 "repair report" for equipment ", a message is directly sent to the equipment maintenance personnel, the equipment maintenance personnel maintain the equipment, and after the maintenance is finished, the message is directly sent to complete the repair report of the equipment), the newly added data node and the edited data node of the trigger can be directly deleted without newly adding and editing data in the" maintenance record table for equipment (when a node is deleted, the child node of the deleted node is automatically set as the child node of the parent node of the deleted node to ensure the continuity of parent-child relationship). Therefore, when the node is deleted due to the change of the service requirement, the core logic of the whole trigger is still not changed, meanwhile, the configuration of the trigger is changed, and other operations are not needed, so that the trigger is automatically effective when being executed next time, and the replacement of the node on the service is completed.

In order to timely handle the abnormal operation of the trigger, the following steps are executed after the trigger is formed:

sa2, setting an exception handling mechanism of a trigger, wherein the exception handling mechanism comprises an interruption operation mechanism and a continuation operation mechanism; the continuous operation mechanism is used for finishing the action of the current node and continuously operating the next node of the trigger when the execution of the node is abnormal; the operation stopping mechanism is used for storing the node operation data in the list set into the database and deleting the list set when the execution of the node is abnormal; and executing a rerun mechanism as required, creating a list set in the memory, writing data from the database back to the list set, and continuing to run from the node where the data is stopped.

When the exception handling mechanism of the trigger is set, the step S5 further includes the steps of:

and S531, when the trigger is triggered, generating a trigger running log in the database.

S532, when the trigger runs abnormally, executing an abnormal processing mechanism, writing abnormal data into the trigger running log, and when the abnormal processing mechanism is a continuous running mechanism, executing the step S533; when the exception handling mechanism is the operation stopping mechanism, executing the step S534; if the operation exception does not occur, the node is considered to be successfully executed, and the operation data of the node is recorded in the list set for the subsequent node to call; and writing the node operation data in the list set into the trigger operation log.

And S533, ending the action of the current node and continuing to operate the next node of the trigger.

S534, generating a trigger operation context in the database, storing the data in the list set into the trigger operation context, and deleting the list set from the memory; while a "rerun" option is displayed on the trigger interface.

At this time, the user may also parse the trigger operation log. Firstly, the detailed configuration of the corresponding trigger is obtained according to the trigger ID in the trigger running log, and the node configuration of the trigger is displayed on a canvas in a visual mode. And then sequentially taking out the running data of each node from the trigger running log, and matching the data of each node into the corresponding node on the canvas through the node ID. When a user moves a mouse over (a method for simulating a hovering event, namely a method for moving a mouse over an object and moving the mouse out of the object) to a node of a visual canvas, judging whether the node successfully operates in the operation of a trigger according to data of the node, if the node successfully operates in the popup window on the upper layer of the node, and displaying the detailed condition of the triggering of the node in the popup window according to the data of the node; and if the node is judged to be not operated successfully or the node has no data, no response is made. So as to search the abnormal reason of the trigger and process the abnormal reason correspondingly. When the user can select "rerun" after handling the cause of the abnormality, the step S535 is performed.

And S535, creating a list set in the memory, and writing the data of the trigger operation context back to the list set from the database, thereby recovering the operation data of the trigger during the suspension and continuing to operate from the suspended node.

In the embodiment, the triggering condition is flexibly configured and can be adapted to various different triggering scenes; the action node 104 relies on a visual trigger, and the full operation process of the trigger configuration can be predicted; the trigger does not need to be reconfigured aiming at the change of the service, and the trigger can be immediately effective only by adding, deleting and editing the action node of the old trigger, so that the trigger iterates along with the service, and because the action node 104 of the trigger is not strongly associated with the trigger, the trigger node can be directly changed on the existing trigger, so that the trigger is more flexible and changeable and has good universality; different action nodes 104 are mapped aiming at different enterprises, so that the action nodes are integrated, the different action nodes 104 are matched with different enterprises, and the problem of poor universality of the existing trigger is solved.

In addition, by establishing the running data of the list set storage node in the memory, the running data of each node can be stored in the list set when the trigger is executed, that is, the running data can be obtained from the list set, when the running data of the front node needs to be called in a service scene, the running data of any front node can be directly obtained from the list set, and the assignment or filtering operation of the current node is executed through the obtained data call. The functions of stopping the trigger operation and rerunning from the stopped node can be realized by storing the data in the list set in the database, so that the trigger operation process is convenient to process when an abnormal condition occurs in the trigger operation process, and the trigger operation process is convenient to continue after the processing.

The invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a computer, the computer program executes part or all of the actual operations of the triggering and running method based on the visual trigger, so as to implement the functions of any one of the above embodiments.

Finally, the above embodiments are only intended to illustrate the technical solutions of the present invention and not to limit the present invention, and although the present invention has been described in detail with reference to the preferred embodiments, it will be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions, and all of them should be covered by the claims of the present invention.

Claims

1. A visual trigger-based triggering and running method is characterized by comprising the following steps:

2. The visual trigger-based triggering and running method according to claim 1, wherein the triggering condition further includes a type of form, the type of form includes an object form and a flow form, and when the type of form is the object form, the step S3 includes the following sub-steps:

3. The visualization trigger based triggering and running method of claim 2, wherein the triggering condition further comprises a triggering field and a data filtering rule; in the step S311, the MQ message sent by the form service to the trigger further includes the changed form data; in the step S313, when the analyzed action type is consistent with the trigger action type set by the trigger node, the following steps are performed before the step S5 is performed:

4. The visual trigger-based triggering and running method according to claim 2 or 3, wherein when the type of the form is a flow form, before executing the step S311, the following steps are further executed:

5. The visual trigger-based triggering and running method according to claim 1, wherein the step S4 includes the following sub-steps:

6. The visual trigger-based triggering and running method according to claim 1, characterized in that the following steps are further performed before forming the trigger:

sa1, predefining a list set of key-value structures;

after forming the trigger, the following steps are also executed:

the step of S5 further includes the steps of:

7. The visual trigger-based triggering and running method according to claim 1, further comprising the steps of:

8. The visual trigger-based triggering and running method according to claim 1, wherein the step S902 further comprises the steps of:

9. The visual trigger-based triggering and running method according to claim 7, further comprising the steps of:

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a visualization trigger based triggering and running method according to any of claims 1 to 9.