BPMN front-end workflow operation method
1. A BPMN front-end workflow operation method is characterized by comprising the following steps:
(1) entering a workflow configuration page, checking whether red error information exists or not, if so, checking the error information, and if not, starting to configure the workflow and moving a necessary starting node and an ending node into the workflow, wherein the result is caused by the incompleteness of the configured workflow; if not, directly entering the step (4);
(2) configuring a strategy to be executed and a rule component corresponding to the strategy between a starting node and an ending node;
(3) if a complex application scene is encountered in the configured flow, a high-order usage of the workflow is introduced, a conditional branch occurs at the moment, and different workflow execution results are generated according to different conditions;
(4) a fully automated decision engine is configured based on a BPMN workflow.
2. The method of claim 1, wherein in step (2), the method comprises the following steps: moving a serviceTask from a toolbar, immediately popping up a configuration popup window of a corresponding policy node, inputting a policy name to be executed on each node name, fuzzily searching a rule component corresponding to the policy, namely a corresponding rule and a version corresponding to the rule in the associated component, and then respectively connecting with a start node and an end node, so far, a simplest workflow without any condition judgment is completed, and as long as an outer layer executes the workflow, the workflow automatically calls the corresponding policy and rule component to complete a series of processes, thereby realizing the automatic whole process.
3. The method as claimed in claim 1, wherein in step (3), the workflow has multiple outputs, but in any case has one and only one workflow inlet, and the default branch on the branch is the default branch.
4. The BPMN front-end workflow operation method according to claim 1, 2 or 3, wherein the workflow includes a start node, a task node, a condition judgment node, a workflow edge, and an end node; the starting node is a starting point for strategy execution and is also a primary configuration starting point of the workflow, and only one starting node is in the workflow; the task nodes are the places where the rule components are configured in the workflow, the number of the rule components configurable by the task nodes is not limited, and the number of the task nodes in the workflow is not limited; the condition judgment node is a branch of workflow execution and is used for carrying out condition judgment by configuring a rule component in a component library; the task nodes and the condition judgment nodes are associated through a connecting line, the connecting line is called a workflow edge, a configuration rule component is arranged on the workflow edge, and the workflow edge is executed by default; the end node is the tail end of the workflow, and the workflow execution to the end node indicates the end of the workflow.
5. The BPMN frontend workflow operation method of claim 4, wherein said component library is a set of rules, a rule component is composed of a series of rules, each rule is a logical operation composed of a series of variables plus simple operation logic; the rule configuration logic may be understood as: if a certain rule is operated, if the condition is satisfied, the result of the rule is the result of the variable expression after the condition of the rule is satisfied, otherwise, the result is the result of the expression of a certain default rule; the rule is the minimum unit of the configuration strategy, the conditional expression is composed of variables and operation logic symbols, and the variables are default values or custom constants.
6. The BPMN front-end workflow operation method according to claim 2, wherein the policy is a logical expression of a series of rule components, and the policy includes a standard policy and a merchant policy, the standard policy is a common policy, the merchant policy is referenced and copied based on the standard policy to produce a new merchant policy, and the merchant policy is configured by manually adding the policy, referencing from the standard policy, copying from another merchant policy, and copying from another merchant policy.
Background
The conventional wind control decision engine mainly implements logical judgment of rules, such as: the rule for entering the scenic spot can be formulated into that 'children with the age less than 12 years enter the garden and need at least one adult to accompany', the existing commonly used wind control decision engine has richer functions on the traditional basis, can realize various types of logic nesting of rules, scoring cards, models, expressions and the like, realizes logic operation with richer levels, and meets the requirements of the existing internet financial business.
Disclosure of Invention
The invention provides a BPMN front-end workflow operation method for realizing a fully-automatic decision engine, aiming at overcoming the defect that a policy needs to be manually configured to realize the decision engine in the prior art.
In order to achieve the purpose, the invention adopts the following technical scheme:
a BPMN front-end workflow operation method specifically comprises the following steps:
(1) entering a workflow configuration page, checking whether red error information exists or not, if so, checking the error information, and if not, starting to configure the workflow and moving a necessary starting node and an ending node into the workflow, wherein the result is caused by the incompleteness of the configured workflow; if not, directly entering the step (4);
(2) configuring a strategy to be executed and a rule component corresponding to the strategy between a starting node and an ending node;
(3) if a complex application scene is encountered in the configured flow, a high-order usage of the workflow is introduced, a conditional branch occurs at the moment, and different workflow execution results are generated according to different conditions;
(4) a fully automated decision engine is configured based on a BPMN workflow.
The method is characterized in that a workflow based on BPMN is added on the basis of a modern wind control decision engine, the manual configuration of strategies and rules is realized through the workflow, the process of completing the strategy calling rules by one key and calling variables by the corresponding rules is realized, and thus the full-automatic decision engine based on the workflow configuration is realized.
Preferably, in the step (2), the specific operation method is as follows: moving a serviceTask from a toolbar, immediately popping up a configuration popup window of a corresponding policy node, inputting a policy name to be executed on each node name, fuzzily searching a rule component corresponding to the policy, namely a corresponding rule and a version corresponding to the rule in the associated component, and then respectively connecting with a start node and an end node, so far, a simplest workflow without any condition judgment is completed, and as long as an outer layer executes the workflow, the workflow automatically calls the corresponding policy and rule component to complete a series of processes, thereby realizing the automatic whole process.
Preferably, in step (3), the workflow has multiple outputs, but in any case the workflow has and only has one workflow input, and the default branch on the branch is the branch that is taken by default.
Preferably, the workflow comprises a start node, a task node, a condition judgment node, a workflow edge and an end node; the starting node is a starting point for strategy execution and is also a primary configuration starting point of the workflow, and only one starting node is in the workflow; the task nodes are the places where the rule components are configured in the workflow, the number of the rule components configurable by the task nodes is not limited, and the number of the task nodes in the workflow is not limited; the condition judgment node is a branch of workflow execution and is used for carrying out condition judgment by configuring a rule component in a component library; the task nodes and the condition judgment nodes are associated through a connecting line, the connecting line is called a workflow edge, a configuration rule component is arranged on the workflow edge, and the workflow edge is executed by default; the end node is the tail end of the workflow, and the workflow execution to the end node indicates the end of the workflow.
Preferably, the component library is a set of rules, the rule component is composed of a series of rules, and each rule is a logic operation formed by combining a series of variables and simple operation logic; the rule configuration logic may be understood as: if a certain rule is operated, if the condition is satisfied, the result of the rule is the result of the variable expression after the condition of the rule is satisfied, otherwise, the result is the result of the expression of a certain default rule; the rule is the minimum unit of the configuration strategy, the conditional expression is composed of variables and operation logic symbols, and the variables are default values or custom constants.
Preferably, the policy is a logical expression of a series of rule components, and includes a standard policy and a merchant policy, the standard policy is a public policy, the merchant policy is referenced and copied based on the standard policy to produce a new merchant policy, and the merchant policy is configured by manually adding a policy, referencing from the standard policy, copying, and copying from another merchant policy.
The invention has the beneficial effects that: based on the workflow of the BPMN, the manual configuration of the strategy and the rule is realized through the workflow, the process that the strategy calling rule is completed by one key and the corresponding rule calls the variable is realized, and thus, the full-automatic decision engine based on the workflow configuration is realized.
Drawings
FIG. 1 is a workflow design block diagram of the present invention.
Detailed Description
The invention is further described with reference to the following figures and detailed description.
In the embodiment shown in fig. 1, a BPMN front-end workflow operation method specifically includes the following steps:
(1) entering a workflow configuration page, checking whether red error information exists or not, if so, checking the error information, and if not, starting to configure the workflow and moving a necessary starting node and an ending node into the workflow, wherein the result is caused by the incompleteness of the configured workflow; if not, directly entering the step (4);
(2) configuring a strategy to be executed and a rule component corresponding to the strategy between a starting node and an ending node; the specific operation method comprises the following steps: moving a serviceTask from a toolbar, immediately popping up a configuration popup window of a corresponding policy node, inputting a policy name to be executed on each node name, fuzzily searching a rule component corresponding to the policy, namely a corresponding rule and a version corresponding to the rule in an associated component, and then respectively connecting the rule component with a start node and an end node, so far that the simplest workflow without any condition judgment is completed, and as long as an outer layer executes the workflow, the workflow automatically calls the corresponding policy and rule component to complete a series of processes and realize the automatic whole process;
(3) if a complex application scene is encountered in the configured flow, a high-order usage of the workflow is introduced, a conditional branch occurs at the moment, and different workflow execution results are generated according to different conditions; the workflow has a plurality of outputs, but the workflow in any case has and only has one workflow inlet, and the default branch on the branch is the branch which is taken by default;
(4) a fully automated decision engine is configured based on a BPMN workflow. The workflow for executing and configuring the decision engine is executed according to one node, and the result of each step of the decision engine is obtained through calculation of arithmetic logic and the like in the execution process. The process of the strategy engine is operated one node by one node along with the acquisition of variable data through rules such as logic operation and the like, and the result of the decision engine is obtained.
Wherein: the workflow comprises a starting node, a task node, a condition judgment node, a workflow edge and an ending node; the starting node is a starting point for strategy execution and is also a primary configuration starting point of the workflow, and only one starting node is in the workflow; the task nodes are the places where the rule components are configured in the workflow, the number of the rule components configurable by the task nodes is not limited, and the number of the task nodes in the workflow is not limited; the condition judgment node is a branch of workflow execution and is used for carrying out condition judgment by configuring a rule component in a component library; the task nodes and the condition judgment nodes are associated through a connecting line, the connecting line is called a workflow edge, a configuration rule component is arranged on the workflow edge, and the workflow edge is executed by default; the end node is the tail end of the workflow, and the workflow execution to the end node indicates the end of the workflow.
The component library is a set of rules, the rule components are composed of a series of rules, each rule is a logical operation that is a combination of a series of variables plus simple operation logics such as (+, -, #,/, &, =, | =, >, <, > =, <, =, and, or); the rule configuration logic may be understood as: if a certain rule is operated, if the condition is satisfied, the result of the rule is the result of the variable expression after the condition of the rule is satisfied, otherwise, the result is the result of the expression of a certain default rule; this can be expressed if expressed using a simple language, if (conditional expression) else if (conditional expression).. a plurality of else if (conditional expression) else (default conditional expression), the rule being the minimum unit of the configuration policy, the conditional expression being composed of variables and operands, the variables being either default values or custom constants.
For example: the mathematical rule component is used in a strategy requiring a mathematical operation scene, and mainly comprises some mathematical functions, wherein the mathematical functions are as follows: adding, subtracting, multiplying, dividing, reducing, enlarging, averaging, rounding down, rounding up, logarithms, exponentiation, and the like.
The strategy is a logic expression of a series of rule components, and comprises a standard strategy and a merchant strategy, wherein the standard strategy is a public strategy, the merchant strategy refers and copies on the basis of the standard strategy to produce a new merchant strategy, and the configuration approaches of the merchant strategy comprise manual strategy addition, reference from the standard strategy, copying and copying from other merchant strategies.
The method is characterized in that a workflow based on BPMN is added on the basis of a modern wind control decision engine, the manual configuration of strategies and rules is realized through the workflow, the process of completing the strategy calling rules by one key and calling variables by the corresponding rules is realized, and thus the full-automatic decision engine based on the workflow configuration is realized.