CN117632416A - A method, device, medium and equipment for process engine trigger task arrangement - Google Patents

Abstract

The invention provides a method, device, medium and equipment for process engine trigger task arrangement. The task arrangement method includes: subscribing to trigger events through a front-end visual interface according to the event type of the task, where the event types include node events and branch events. and process events; select the triggering condition of the trigger according to the trigger event; trigger and schedule the trigger event according to the triggering condition according to the task. In the embodiment of the present invention, different types of event definitions such as process events, branch events, and node events are introduced, so that triggers can subscribe to multiple events as needed. At the same time, each trigger event can be configured with trigger conditions independently, solving the problems in the existing technology. Technical issues include insufficient event subscription management support for processes and branch conditions, and insufficient orchestration capabilities for the combination of multiple conditions and actions.

Description

A method, device, medium and equipment for process engine trigger task arrangement

Technical field

The present invention relates to the field of computer technology, and in particular, to a method, device, medium and equipment for arranging process engine trigger tasks.

Background technique

Trigger task orchestration configuration is mainly used in the fields of Internet of Things, big data processing and automated operation platforms to improve the ease of use of trigger event subscription and the scalability of task scheduling. Traditional trigger configuration is mainly aimed at the integration of rule engines. , designed to solve event triggering in office approval scenarios.

Existing technical solutions for task orchestration and configuration only solve form processing during process running. The scheduling capabilities for task execution are mainly reflected in individual conditions and action configurations. It can be seen that the existing technical solutions have limitations on process and branch conditions. Technical issues include insufficient support for event subscription management, insufficient ability to orchestrate the combination of multiple conditions and actions, and weak asynchronous task configuration capabilities.

Contents of the invention

In view of this, the purpose of embodiments of the present invention is to provide a method, device, medium and equipment for process engine trigger task arrangement, so as to solve the problem of insufficient support for event subscription management of processes and branch conditions in the prior art, and for multiple conditions. Technical problems caused by insufficient ability in combination and choreography of movements.

In order to achieve the above object, in a first aspect, an embodiment of the present invention provides a method for arranging process engine trigger tasks. The method includes:

Subscribe to the triggering event of the trigger through the front-end visual interface according to the event type of the task, where the event type includes node events, branch events and process events;

Select the triggering condition of the trigger according to the triggering event;

The trigger is scheduled to execute the task according to the triggering condition and the triggering event.

In some possible implementations, the method further includes:

The trigger number is associated with the task number and persisted in the database.

In some possible implementations, the subscription trigger event includes:

During the running process of the task, a trigger event is sent to the outside according to the node, branch or process of the task. The trigger event carries the number, form data and context data of the task, and is compared with the trigger event in the database. associated with the trigger number to trigger the execution of the trigger; wherein the trigger event includes:

Create process: The trigger fires when the user creates a process;

End the process, and the trigger is triggered when the process execution is completed, the process execution fails, or the process is actively closed;

To cancel the process, the trigger is fired when the user cancels the process;

Suspend the process, the trigger is fired when the user suspends the process;

Resume process, the trigger fires when the user resumes the suspended process.

In some possible implementations, the triggering conditions include: form field judgment, global context judgment, task execution result judgment, any one or more of multi-condition OR and multi-condition AND; wherein,

Form field judgment refers to the configuration parameters of task execution. When the node input data meets the configuration parameters, the trigger is executed;

Global context judgment refers to the context content of the configuration execution field. When the configuration execution field of the process meets the context content, the trigger is executed;

Task execution result judgment refers to the return value of task execution. When the return result of node task execution meets the return value, the trigger is executed;

Multi-condition or refers to the multiple judgment conditions in the configuration condition rule engine. Multiple judgment conditions are judged in the form of OR to determine whether the trigger condition is met; multi-condition AND refers to the multiple judgment conditions in the configuration condition engine. Multiple judgments The conditions are ANDed in the form of AND to determine whether the trigger condition is met.

In a second aspect, embodiments of the present invention also provide a device for arranging process engine trigger tasks. The device includes:

A trigger configuration module, used to subscribe to trigger events through the front-end visual interface according to the event type of the task, where the event types include node events, branch events and process events;

A conditional rule engine module, used to select the triggering condition of the trigger according to the trigger event;

A task scheduling engine module, configured to trigger and schedule the trigger to execute the task according to the triggering condition according to the triggering event.

In some possible implementations, the device further includes:

An association module, configured to associate the number of the trigger with the number of the task and persist it in the database.

In some possible implementations, the trigger configuration module is specifically used to:

During the running process of the task, a trigger event is sent to the outside according to the node, branch or process of the task. The trigger event carries the number, form data and context data of the task, and is compared with the trigger event in the database. associated with the trigger number to trigger the execution of the trigger; wherein the trigger event includes:

Create process: The trigger fires when the user creates a process;

End the process, and the trigger is triggered when the process execution is completed, the process execution fails, or the process is actively closed;

To cancel the process, the trigger is fired when the user cancels the process;

Suspend the process, the trigger is fired when the user suspends the process;

Resume process, the trigger fires when the user resumes the suspended process.

In some possible implementations, the trigger conditions selected by the conditional rule engine module specifically include: form field judgment, global context judgment, task execution result judgment, any one or more of multi-condition OR and multi-condition AND; wherein ,

Form field judgment refers to the configuration parameters of task execution. When the node input data meets the configuration parameters, the trigger is executed;

Global context judgment refers to the context content of the configuration execution field. When the configuration execution field of the process meets the context content, the trigger is executed;

Task execution result judgment refers to the return value of task execution. When the return result of node task execution meets the return value, the trigger is executed;

Multi-condition or refers to the multiple judgment conditions in the configuration condition rule engine, and multiple judgment conditions are judged in the form of OR to determine whether the trigger condition is met; multi-condition and refers to the multiple judgment conditions in the configuration condition rule engine, multiple The judgment conditions are determined in the form of AND to determine whether the trigger conditions are met.

In a third aspect, embodiments of the present invention provide a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method for arranging any process engine trigger task is implemented.

In a fourth aspect, embodiments of the present invention provide an electronic device, which includes:

processor;

memory for storing instructions executable by the processor;

Wherein, the processor is configured to execute the instruction to implement any of the process engine trigger task arrangement methods.

The above technical solution has the following beneficial effects:

The invention provides a method, device, medium and equipment for process engine trigger task arrangement. The task arrangement method includes: subscribing to trigger events through a front-end visual interface according to the event type of the task, where the event types include node events and branch events. and process events; select the triggering condition of the trigger according to the trigger event; trigger the scheduling trigger to execute the task according to the triggering condition according to the triggering event. In the embodiment of the present invention, different types of event definitions such as process events, branch events, and node events are introduced, so that triggers can subscribe to multiple events as needed. At the same time, each trigger event can be configured with trigger conditions independently, solving the problems in the existing technology. Technical issues include insufficient event subscription management support for processes and branch conditions, and insufficient orchestration capabilities for the combination of multiple conditions and actions.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. It is obvious that the drawings in the following description are only For some embodiments of the present invention, those of ordinary skill in the art can also obtain other drawings based on these drawings without exerting creative efforts.

Figure 1 is a flow chart of a method for arranging process engine trigger tasks according to an embodiment of the present invention;

Figure 2 is an architectural diagram of a process engine trigger task arrangement according to an embodiment of the present invention;

Figure 3 is a flow diagram of configuring node triggers according to an embodiment of the present invention;

Figure 4 is a flow diagram of configuring branch flip-flops according to an embodiment of the present invention;

Figure 5 is a flow diagram of configuring process triggers according to the embodiment of the present invention.

Figure 6 is a structural block diagram of a device for arranging process engine trigger tasks according to an embodiment of the present invention;

Figure 7 is a structural block diagram of another device for process engine trigger task arrangement according to an embodiment of the present invention;

Figure 8 is a functional block diagram of a computer-readable storage medium according to an embodiment of the present invention;

Figure 9 is a functional block diagram of an electronic device according to an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present invention.

Embodiment 1

Figure 1 is a flow chart of a method for arranging process engine trigger tasks according to an embodiment of the present invention. As shown in Figure 1, the task arranging method includes the following steps:

Step S11, subscribe to the triggering event of the trigger through the front-end visual interface according to the event type of the task, where the event type includes node events, branch events and process events.

Step S12: Select the triggering condition of the trigger according to the triggering event.

Step S13: Trigger the scheduling trigger to execute the task according to the triggering condition according to the triggering event.

Figure 2 is an architectural diagram of a process engine trigger task arrangement according to an embodiment of the present invention. As shown in Figure 2, in this embodiment, the task arrangement includes the following steps:

S1, trigger configuration: The process configurer configures the trigger in advance and selects the configured trigger according to the event type. Node events configure node triggers, branch events configure branch triggers, and process events configure process triggers;

S2, trigger condition configuration: Each trigger has a corresponding trigger condition, which can be configured through the condition rule engine, such as form field judgment, global context judgment, task execution result judgment, multi-condition OR and multi-condition AND.

S3, execution of task scheduling: When the process is initiated externally, the event type of the task can be determined through the event scheduler. The task scheduling engine schedules the configured trigger according to the event type to execute the task according to the triggering conditions.

In this embodiment, each task will be configured with multiple nodes, and each node will be packaged into different event types according to processing specific tasks. Among them, there will be connections between nodes, and each connection will be associated with branch conditions and processes. The event will associate the trigger to the node, the process itself and the branch to trigger. During the task running process, it will be executed in such a defined order.

Figure 3 is a flow diagram for configuring node triggers in an embodiment of the present invention, as shown in Figures 2 and 3. In this embodiment, node events can be configured with node triggers. By configuring the process, select the process node, and then configure the node trigger. trigger, that is, a trigger configured in a process node, which will be triggered only when the process flows to the corresponding process node. A process node can be configured with multiple trigger events, and each trigger event can be executed independently according to its own configured trigger conditions. Specifically, the trigger events can be but are not limited to the following:

The trigger event is the entry node: when the process flows to the corresponding node in the node event, the trigger of the node is triggered;

The trigger event is leaving the node: the process flows to the corresponding node in the node event and the task is successfully executed through the node. The trigger is triggered when leaving the current node and going to the next node;

The trigger event is the dispatch node: the process flows to the corresponding node in the node event and the trigger is triggered when the "dispatch person" of the node completes the action of dispatching the node.

Figure 4 is a flow diagram for configuring branch triggers in an embodiment of the present invention. As shown in Figures 2 and 4, branch events can be configured with branch triggers. By configuring the process, select the process branch, and then configure the branch trigger, that is, configure it in The triggering event in the process line, for example, the triggering event is entering a branch, and the process will only be triggered when the process flows to the corresponding process branch.

Figure 5 is a flow diagram for configuring process triggers in an embodiment of the present invention. As shown in Figures 2 and 5, process events can configure process triggers. By configuring the process, the process triggers are configured, that is, the triggers configured in the process. , it will be triggered when the process performs a certain operation.

Multiple trigger events can be configured in process events, and each trigger can be executed independently according to its own configured trigger conditions. The trigger events can be but are not limited to the following:

The triggering event is process creation: the trigger fires when the user creates a process;

The trigger event is to end the process: the trigger is triggered when the process execution is completed, the process execution fails, or the process is actively closed;

The triggering event is the cancellation process: the trigger fires when the user cancels the process;

The trigger event is a suspended process: the trigger fires when the user suspends the process;

The trigger event is the resumption process: the trigger fires when the user resumes the suspended process.

In this embodiment, different types of event definitions such as process events, branch events, and node events are introduced in the process of trigger event subscription management, so that triggers can subscribe to multiple events as needed.

In this embodiment, after subscribing to the triggering event of the trigger in step S11, in step S12, the triggering conditions of the trigger are managed through the conditional rule engine, which is referred to as conditional management. Conditional management specifically refers to using rule judgment and context parameters as Conditional configuration. After the configuration is completed, the conditional configuration will be converted into a string expression and persisted in the database. When the process runs to the specified node, an event will be emitted. At this time, a rule will be made based on the data of the current node, the context parameters of the process, etc. Only take specific actions after making judgment.

The conditional rule engine is mainly used to configure trigger conditions, parameter parsing of trigger conditions and execution of trigger condition rules. Through the conditional rule engine, condition groups can be set to realize the OR and AND judgment of multiple conditions. Each condition is associated with multiple conditional expressions. As well as classifying trigger conditions, dynamic trigger mechanisms can be realized under complex conditions. In this embodiment, the triggering conditions may include: form field judgment, global context judgment, task execution result judgment, any one or more of multiple conditions or and multiple conditions and, specifically:

Form field judgment refers to the configuration parameters of task execution. When the node input data meets the configuration parameters, the trigger is executed;

Global context judgment refers to the context content of the configuration execution field. When the configuration execution field of the process meets the context content, the trigger is executed;

Task execution result judgment refers to the return value of task execution. When the return result of node task execution meets the return value, the trigger is executed;

Multi-condition or refers to multiple judgment conditions in the configuration condition rule engine. Multiple judgment conditions are judged in the form of OR to determine whether the trigger condition is met; the trigger condition is multi-condition AND: multiple judgment conditions in the configuration condition rule engine. Multiple judgment conditions are used in the form of AND to determine whether the trigger conditions are met, that is, the trigger is executed when all conditions are met.

In this embodiment, different conditional expressions are executed and parameter parsing is completed according to different triggering conditions. Each triggering condition rule corresponds to a conditional expression. All triggering conditions are traversed according to the conditional calculation expression. When the conditional calculation expression returns true Indicates that the rule hits, that is, triggers the execution of the trigger. Returning false indicates that the rule fails and the trigger is not triggered at this time. The condition calculation expression can include: contains, equals, equals (ignoring case), regular matching, does not contain, and is not empty. , starts with the set value, ends with the set value, is not equal to, is not within the value, etc.

In this embodiment, a task scheduling strategy based on multi-condition combination and concurrency is adopted, allowing users to customize task triggering conditions and execution order, supporting multiple conditions and and or, and supporting serial and parallel execution of multiple tasks.

In addition, in step S13, when the user initiates a task, the event scheduler can be used to determine the type of the task, for example, whether the task is a node event, a branch event, or a process event. Then, the task scheduling engine will perform task scheduling according to the event type. Referring to S3 in Figure 2, execution task scheduling mainly includes:

Task parsing: It can also be called parameter parsing. Parameter parsing includes task request parameter parsing and task context parameter parsing. Task request parameter parsing refers to parsing the task name and task number by matching the process form data based on the parameters in the task definition. , filled into the request parameters of the task; task context parameter parsing refers to injecting the upper and lower parameters of the task into the process context data, such as the node name contained in the process, the number of the process, the information of the process, the current operator and the process global variable information, etc.

Resource allocation: In this embodiment, different working nodes are scheduled according to the priority of tasks to meet the isolation control of tasks. Some tasks require quick response, and some tasks require long execution. In order to meet the rapid execution of high-priority tasks, To avoid backlog, a task priority scheduling algorithm is designed. For example, you can design two message queues (for example, task_high_priority and task_default_priority) to receive task messages and execute tasks;

Synchronous execution and asynchronous execution: This embodiment adopts a task scheduling strategy based on multi-condition combination and concurrency, allowing users to customize the conditions and execution order of task triggers, supporting multiple conditions and and or, and supporting the synchronous execution of multiple tasks ( Parallel execution) and asynchronous execution (serial execution);

Task polling and failure compensation: In this embodiment, execution results can be associated with process nodes, providing task synchronous and asynchronous execution capabilities, capturing task exceptions, completing task retries through polling configuration, recording task failure results, and system management Operators can query failure records for manual execution and complete task compensation.

The embodiment of the present invention allows tasks to be executed cyclically according to specific conditions during task execution to achieve more complex process control. At the same time, a context management mechanism is introduced for triggers so that task execution results can be easily associated with the conditions of subsequent tasks to achieve more precise trigger conditions.

For example, in an industrial Internet of Things temperature control scenario, a temperature sensor task pipeline is configured, which mainly includes three nodes: sensor parameter analysis, preprocessing, and data storage. A process trigger is configured during the configuration process. The process trigger triggers tasks based on multiple conditions such as sensor temperature, season, device threshold, etc. Each action can be independently associated with conditions. The task mainly contains 3 actions: 1. Send Notify the designated personnel; 2. Execute the control command of a certain device to reduce the load; 3. Send an alarm notification to the production line. The definition of the process is a thread (Pipeline), which defines three nodes (including parameter parsing, preprocessing, and data storage). Each thread contains a trigger (TriggerPublisher), which can be configured by configuring a trigger configuration (TriggeConfig ) is associated with the thread and is persistently stored in the database. There is an external task scheduling and execution module, which mainly includes task registration, task scheduling and execution, including sending notifications, executing IOT commands (Internet of Things device control commands), and sending external Sending API (ApplicationProgram Interface, application program interface) requests is a task.

In some embodiments, the task arrangement method further includes: associating the number of the trigger with the number of the task and persisting them in the database. In the embodiment of the present invention, the event type and trigger condition can be selected on the interface, and then whether to trigger execution. After the configuration is completed, the trigger number and the process number are associated and persisted in the database.

In addition, in this embodiment, the trigger event of the subscription trigger includes: during the task running process, the trigger event is sent to the outside according to the node, branch or process of the task. The trigger event carries the task number, form data and context data, and is passed through It is associated with the trigger number in the database to trigger the execution of the trigger. During the running of the pipeline, an event will be sent to the outside based on the pipeline running to a certain node, branch and completion of the operation. The event carries the process number, the form data of the process and the context data of the process, and is associated with the trigger number in the database. , which ultimately triggers the execution of the trigger.

Figure 6 is a structural block diagram of a device for arranging process engine trigger tasks according to an embodiment of the present invention. As shown in Figure 6, the device 100 includes:

The trigger configuration module 110 is used to subscribe to trigger events through the front-end visual interface according to the event type of the task, where the event types include node events, branch events and process events;

Specifically, in this embodiment, each task will be configured with multiple nodes, and each node will be packaged into different event types according to processing specific tasks. Among them, there will be connections between nodes, and each connection will be associated with Branch conditions, triggers will be associated with the node, process itself and branches to trigger, and will be executed in this defined order during task running.

Each task will be configured with multiple nodes, and each node will be packaged into different event types according to the processing of specific tasks. Among them, there will be connections between nodes, each connection will be associated with branch conditions, and process events will trigger It is triggered by being associated with the node, the process itself and the branch. During the task running process, it will be executed in such a defined order.

Specifically, in this embodiment, the node event can be configured with a node trigger. The trigger configuration module 110 selects the process node through the configuration process, and then configures the node trigger, that is, the trigger configured in the process node, and the process flows to the corresponding It will only be triggered when the process node is reached. A process node can be configured with multiple trigger events, and each trigger event can be executed independently according to its own configured trigger conditions. Specifically, the trigger events can be but are not limited to the following:

The trigger event is the entry node: when the process flows to the corresponding node in the node event, the trigger of the node is triggered;

The trigger event is leaving the node: the process flows to the corresponding node in the node event and the task is successfully executed through the node. The trigger is triggered when leaving the current node and going to the next node;

The trigger event is the dispatch node: the process flows to the corresponding node in the node event and the trigger is triggered when the "dispatch person" of the node completes the action of dispatching the node.

The branch event can be configured with a branch trigger. The trigger configuration module 110 selects the process branch by configuring the process, and then configures the branch trigger, that is, the trigger event configured in the process line. For example, the trigger event is to enter a branch, and the process flows to the corresponding process. It will only be triggered when branching.

Process events can configure process triggers. The trigger configuration module 110 configures the process and then configures the process trigger, that is, the trigger configured in the process will be triggered when the process performs a certain operation.

Multiple trigger events can be configured in process events, and each trigger can be executed independently according to its own configured trigger conditions. The trigger events can be but are not limited to the following:

The triggering event is process creation: the trigger fires when the user creates a process;

The trigger event is to end the process: the trigger is triggered when the process execution is completed, the process execution fails, or the process is actively closed;

The triggering event is the cancellation process: the trigger fires when the user cancels the process;

The trigger event is a suspended process: the trigger fires when the user suspends the process;

The trigger event is the resumption process: the trigger fires when the user resumes the suspended process.

In this embodiment, different types of event definitions such as process events, branch events, and node events are introduced in the process of trigger event subscription management, so that triggers can subscribe to multiple events as needed.

The conditional rule engine module 120 is used to select the triggering condition of the trigger according to the trigger event.

In this embodiment, after the trigger configuration module 110 subscribes to the triggering event of the trigger, the conditional rule engine module 120 will manage the triggering conditions of the trigger through the conditional rule engine, which is referred to as conditional management. Conditional management specifically refers to judging by rules, Context parameters are used as conditional configurations. After the configuration is completed, the conditional configuration will be converted into a string expression and persisted in the database. When the process runs to the specified node, an event will be emitted. At this time, according to the data of the current node, the context parameters of the process Wait for a rule judgment to be made before taking specific actions.

The conditional rule engine module 120 is mainly used to configure trigger conditions, parameter analysis of trigger conditions and execution of trigger condition rules. Through the conditional rule engine, condition groups can be set to realize the OR and AND judgment of multiple conditions. Each condition is associated with multiple conditions. Expressions and classification of trigger conditions can realize dynamic trigger mechanisms under complex conditions. In this embodiment, the triggering conditions may include: form field judgment, global context judgment, task execution result judgment, any one or more of multiple conditions or and multiple conditions and, specifically:

Form field judgment refers to the configuration parameters of task execution. When the node input data meets the configuration parameters, the trigger is executed;

Global context judgment refers to the context content of the configuration execution field. When the configuration execution field of the process meets the context content, the trigger is executed;

Task execution result judgment refers to the return value of task execution. When the return result of node task execution meets the return value, the trigger is executed;

Multi-condition or refers to multiple judgment conditions in the configuration condition rule engine. Multiple judgment conditions are judged in the form of OR to determine whether the trigger condition is met; the trigger condition is multi-condition AND: multiple judgment conditions in the configuration condition rule engine. Multiple judgment conditions are used in the form of AND to determine whether the trigger conditions are met, that is, the trigger is executed when all conditions are met.

In this embodiment, different conditional expressions are executed and parameter parsing is completed according to different triggering conditions. Each triggering condition rule corresponds to a conditional expression. All triggering conditions are traversed according to the conditional calculation expression. When the conditional calculation expression returns true Indicates that the rule hits, that is, triggers the execution of the trigger. Returning false indicates that the rule fails and the trigger is not triggered at this time. The condition calculation expression can include: contains, equals, equals (ignoring case), regular matching, does not contain, and is not empty. , starts with the set value, ends with the set value, is not equal to, is not within the value, etc.

In this embodiment, the conditional rule engine module 120 executes different conditional expressions and completes parameter analysis according to different triggering conditions. Each triggering condition rule corresponds to a conditional expression, and all triggering conditions are traversed according to the conditional calculation expression. When the condition If the calculation expression returns true, it means that the rule is hit, that is, triggering the execution of the trigger. If it returns false, it means that the rule fails, and the trigger is not triggered at this time. The condition calculation expression can include: contains, equal to, equal to (ignoring case), regular matching, not Contains, is not empty, starts with the set value, ends with the set value, is not equal to, is not within the value, etc.

In this embodiment, a task scheduling strategy based on multi-condition combination and concurrency is adopted, allowing users to customize task triggering conditions and execution order, supporting multiple conditions and and or, and supporting serial and parallel execution of multiple tasks.

The task scheduling engine module 130 is configured to trigger a scheduling trigger to execute a task according to the trigger condition according to the trigger event.

Specifically, when the user initiates a task, the task scheduling engine module 130 can determine the type of the task through the event scheduler, for example, whether the task is a node event, a branch event, or a process event. Then, the task scheduling engine will execute the task according to the event type. . Referring to step S3 in Figure 2, the execution tasks mainly include:

Task parsing: It can also be called parameter parsing. Parameter parsing includes task request parameter parsing and task context parameter parsing. Task request parameter parsing refers to parsing the task name and task number by matching the process form data based on the parameters in the task definition. , filled into the request parameters of the task; task context parameter parsing refers to injecting the upper and lower parameters of the task into the process context data, such as the node name contained in the process, the number of the process, the information of the process, the current operator and the process global variable information, etc.

Resource allocation: In this embodiment, different working nodes are scheduled according to the priority of tasks to meet the isolation control of tasks. Some tasks require quick response, and some tasks require long execution. In order to meet the rapid execution of high-priority tasks, To avoid backlog, a task priority scheduling algorithm is designed. For example, you can design two message queues (for example, task_high_priority and task_default_priority) to receive task messages and execute tasks;

Synchronous execution and asynchronous execution: This embodiment adopts a task scheduling strategy based on multi-condition combination and concurrency, allowing users to customize the conditions and execution order of task triggers, supporting multiple conditions and and or, and supporting the synchronous execution of multiple tasks ( Parallel execution) and asynchronous execution (serial execution);

Task polling and failure compensation: In this embodiment, execution results can be associated with process nodes, providing task synchronous and asynchronous execution capabilities, capturing task exceptions, completing task retries through polling configuration, recording task failure results, and system management Operators can query failure records for manual execution and complete task compensation.

The embodiment of the present invention allows tasks to be executed cyclically according to specific conditions during task execution to achieve more complex process control. At the same time, a context management mechanism is introduced for triggers so that task execution results can be easily associated with the conditions of subsequent tasks to achieve more precise trigger conditions.

Figure 7 is a structural block diagram of another device for process engine trigger task arrangement according to an embodiment of the present invention. As shown in Figure 7, in some embodiments, the task arrangement device 100' also includes:

The association module 140 is used to associate the trigger number with the task number and persist them in the database. In the embodiment of the present invention, the event type and trigger condition can be selected on the interface, and then whether to trigger execution. After the configuration is completed, the trigger number and the process number are associated and persisted in the database.

In some embodiments, the trigger configuration module 110 is specifically used to: during the task running process, send trigger events to the outside according to the node, branch or process of the task. The trigger event carries the task number, form data and context data, through It is associated with the trigger number in the database to trigger the execution of the trigger. During the running of the pipeline, an event will be sent to the outside based on the pipeline running to a certain node, branch and completion of the operation. The event carries the process number, the form data of the process and the context data of the process, and is associated with the trigger number in the database. , which ultimately triggers the execution of the trigger.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional units and modules is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs. Module completion means dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be hardware-based. It can also be implemented in the form of software functional units. In addition, the specific names of each functional unit and module are only for the convenience of distinguishing each other and are not used to limit the scope of the present invention. For the specific working processes of the units and modules in the above system, please refer to the corresponding processes in the foregoing method embodiments, and will not be described again here.

Embodiment 3

Figure 8 is a functional block diagram of a computer-readable storage medium according to an embodiment of the present invention. As shown in Figure 8, an embodiment of the present invention also provides a computer-readable storage medium 300. The computer-readable storage medium 300 stores a computer program 310. When the computer program 310 is executed by a processor, it implements:

Subscribe to the triggering event of the trigger through the front-end visual interface according to the event type of the task, where the event type includes node events, branch events and process events;

Select the triggering condition of the trigger according to the triggering event;

The trigger is scheduled to execute the task according to the triggering condition and the triggering event.

If the integrated module/unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention can implement all or part of the processes in the methods of the above embodiments, and can also be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can be stored in a computer-readable storage medium. When the program is executed by the processor, the steps of each of the above method embodiments can be implemented. Wherein, the computer program includes computer program code, which may be in the form of source code, object code, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media, etc. Of course, there are other ways of readable storage media, such as quantum memory, graphene memory, etc. It should be noted that the content contained in the computer-readable medium can be appropriately added or deleted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium Excludes electrical carrier signals and telecommunications signals.

Embodiment 4

Figure 9 is a functional block diagram of an electronic device according to an embodiment of the present invention. An embodiment of the present invention also provides an electronic device. Please refer to FIG. 9. At the hardware level, the electronic device includes a processor and optionally an internal bus, a network interface, and a memory. The memory may include memory, such as high-speed random access memory (Random-Access Memory, RAM), or may also include non-volatile memory (non-volatile memory), such as at least one disk memory. Of course, the electronic equipment may also include other hardware required by the business.

The processor, network interface and memory can be connected to each other through an internal bus, which can be an industry standard architecture ISA bus, a peripheral component interconnection standard PCI bus or an extended industry standard architecture EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one bidirectional arrow is used in Figure 9, but it does not mean that there is only one bus or one type of bus.

Memory, used to store programs. Specifically, a program may include program code including computer operating instructions. Memory may include internal memory and non-volatile memory and provides instructions and data to the processor. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a process engine trigger task arrangement method at the logical level.

The processor executes the program stored in the memory, and is specifically configured to execute a process engine trigger task arrangement method disclosed in the embodiment shown in FIGS. 1 to 4 .

The method for arranging process engine trigger tasks disclosed in the above embodiments shown in FIGS. 1 to 4 can be applied in a processor or implemented by the processor. The processor may be an integrated circuit chip that has signal processing capabilities. During the implementation process, each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor. The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (DigitalSignal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit) Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components. Each method, step and logical block diagram disclosed in the embodiment of the present invention can be implemented or executed. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present invention can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

Of course, in addition to software implementation, the electronic device of the present invention does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logical unit. It can also be hardware or logic devices. The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet Computers, wearables, or a combination of any of these devices.

Although the present invention provides method operation steps as described in the embodiments or flow charts, more or less operation steps may be included based on conventional or non-inventive means. The sequence of steps listed in the embodiment is only one way of executing the sequence of many steps, and does not represent the only execution sequence. When the actual device or terminal product is executed, it may be executed sequentially or in parallel according to the methods shown in the embodiments or figures (for example, a parallel processor or a multi-thread processing environment, or even a distributed data processing environment).

The invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, and computer program products according to embodiments of the invention. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or operations are mutually exclusive. any such actual relationship or sequence exists between them. Furthermore, the terms "comprising," "comprising," or any other variation thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also those not expressly listed other elements, or elements inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or apparatus that includes the stated element.

Each embodiment in this specification is described in a related manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the device, electronic equipment and readable storage medium embodiments, since they are basically similar to the method embodiments, the descriptions are relatively simple. For relevant details, please refer to the partial description of the method embodiments.

The above descriptions are only preferred embodiments of the present invention and are not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention are included in the protection scope of the present invention.

Claims (10)

1. A method of scheduling tasks of a flow engine trigger, the method comprising:

subscribing a trigger event of a trigger through a front-end visual interface according to an event type of a task, wherein the event type comprises a node event, a branch event and a flow event;

selecting a trigger condition of the trigger according to the trigger event;

and scheduling the trigger to execute the task according to the trigger condition according to the trigger event.

2. The method of task orchestration according to claim 1, wherein the method further comprises:

and correlating the number of the trigger with the number of the task and persisting the number into a database.

3. The method of task orchestration according to claim 2, wherein the trigger event of the subscription trigger comprises:

in the task running process, according to the node, branch or flow of the task, a trigger event is sent to the outside, wherein the trigger event carries the number, form data and context data of the task, and the trigger is triggered to be executed by associating with the number of the trigger in the database; wherein the triggering event comprises:

the creation flow is as follows: triggering a trigger when a user creates a flow;

ending the flow, and triggering the trigger when the flow execution is completed, the flow execution fails or the active closing is performed;

the process is withdrawn, and when the user withdraws the process, the trigger is triggered;

suspending the process, wherein the trigger is triggered when the user suspends the process;

and restoring the flow, wherein the trigger is triggered when the user restores the suspended flow.

4. The method of task orchestration according to claim 1, wherein the trigger conditions comprise: form field judgment, global context judgment, task execution result judgment, multi-condition or any one or more of multi-condition and multi-condition; wherein,

The form field judgment refers to configuration parameters of task execution, and when the node input data meets the configuration parameters, the trigger is executed;

the global context judgment refers to context content of a configuration execution field, and when the context content is met by a context text segment of the flow, the trigger is executed;

the task execution result judgment refers to a return value of task execution, and when the return result of node task execution meets the return value, the trigger is executed;

multiple conditions or multiple judging conditions in the configuration condition rule engine are used for judging whether the trigger condition is met in a OR mode;

the multi-condition and the multi-judgment condition in the configuration condition rule engine are judged in a AND mode to judge whether the triggering condition is met or not.

5. An apparatus for scheduling tasks of a flow engine trigger, said apparatus comprising:

the trigger configuration module is used for subscribing trigger events of the trigger through the front-end visual interface according to event types of tasks, wherein the event types comprise node events, branch events and flow events;

the condition rule engine module is used for selecting the trigger condition of the trigger according to the trigger event;

And the task scheduling engine module is used for triggering and scheduling the trigger to execute the task according to the trigger condition according to the trigger event.

6. The tasking apparatus of claim 5 further comprising:

and the association module is used for associating the number of the trigger with the number of the task and persisting the number of the trigger and the number of the task into a database.

7. The task orchestration device according to claim 6, wherein the trigger configuration module is specifically configured to:

in the task running process, according to the node, branch or flow of the task, a trigger event is sent to the outside, wherein the trigger event carries the number, form data and context data of the task, and the trigger is triggered to be executed by associating with the number of the trigger in the database; wherein the triggering event comprises:

the creation flow is as follows: triggering a trigger when a user creates a flow;

ending the flow, and triggering the trigger when the flow execution is completed, the flow execution fails or the active closing is performed;

the process is withdrawn, and when the user withdraws the process, the trigger is triggered;

suspending the process, wherein the trigger is triggered when the user suspends the process;

And restoring the flow, wherein the trigger is triggered when the user restores the suspended flow.

8. The task orchestration device according to claim 5, wherein the trigger conditions selected by the condition rules engine module specifically comprise: form field judgment, global context judgment, task execution result judgment, multi-condition or any one or more of multi-condition and multi-condition; wherein,

the form field judgment refers to configuration parameters of task execution, and when the node input data meets the configuration parameters, the trigger is executed;

the global context judgment refers to context content of a configuration execution field, and when the configuration execution field of the flow meets the context content, the trigger executes;

the task execution result judgment refers to a return value of task execution, and when the return result of node task execution meets the return value, the trigger is executed;

multiple conditions or multiple judging conditions in the configuration condition rule engine are used for judging whether the trigger condition is met in a OR mode; the multi-condition and the multi-judgment condition in the configuration condition rule engine are judged in a AND mode to judge whether the triggering condition is met or not.

9. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements a method of flow engine trigger task orchestration according to any one of claims 1-4.

10. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement a method of flow engine trigger task orchestration according to any one of claims 1-4.