CN116911766A - Workflow engine and implementation method thereof, readable storage medium and electronic equipment - Google Patents
Workflow engine and implementation method thereof, readable storage medium and electronic equipment Download PDFInfo
- Publication number
- CN116911766A CN116911766A CN202310646006.5A CN202310646006A CN116911766A CN 116911766 A CN116911766 A CN 116911766A CN 202310646006 A CN202310646006 A CN 202310646006A CN 116911766 A CN116911766 A CN 116911766A
- Authority
- CN
- China
- Prior art keywords
- node
- flow
- business
- rule
- logic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 248
- 230000008569 process Effects 0.000 claims abstract description 193
- 230000004048 modification Effects 0.000 claims abstract description 23
- 238000012986 modification Methods 0.000 claims abstract description 23
- 238000012217 deletion Methods 0.000 claims abstract description 11
- 230000037430 deletion Effects 0.000 claims abstract description 11
- 230000008859 change Effects 0.000 claims description 68
- 238000012545 processing Methods 0.000 claims description 20
- 230000004044 response Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 9
- 238000006243 chemical reaction Methods 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 13
- 230000000694 effects Effects 0.000 description 13
- 238000007726 management method Methods 0.000 description 11
- 230000002093 peripheral effect Effects 0.000 description 10
- 230000000007 visual effect Effects 0.000 description 9
- 238000012423 maintenance Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000004886 process control Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the specification provides a workflow engine and an implementation method, a readable storage medium and electronic equipment thereof, when the workflow engine is used for realizing a business process, a business process adapter generates a process link related to the business process, a process node adapter configures a process node for the business process according to the process link to obtain the business process, a business rule manager responds to at least one of rule modification operation, rule addition operation and rule deletion operation, so that the business rule is changed, the rule engine configures the business rule for the business process, a process executor executes the business process according to the business rule, and the business process can cope with sudden-change business scenes.
Description
Technical Field
The embodiment of the specification relates to the technical field of flow management, in particular to a workflow engine and an implementation method thereof, a computer readable storage medium and electronic equipment.
Background
The workflow engine refers to a workflow (workflow) as a part of an application system, and provides a core solution for determining information delivery routes, content levels and the like according to different roles, division of work and conditions, which have a determining effect on each application system.
In a complex service system, with the change of complex services, usually, enterprise developers need to change and reconstruct complex service codes frequently, which brings great maintenance cost. A common solution is to orchestrate complex traffic using workflow engines, for example, currently common workflow engines are Activiti. When the service processing is realized through the Activiti, the configuration flexibility of the service flow is insufficient, and when the sudden change of the service or the change of the external environment is faced, a developer is required to carry out service logic arrangement on the Activiti again, even part of codes are modified and the system release is carried out, so that the service flow cannot be processed in time through the Activiti.
It should be noted that the information disclosed in the foregoing background section is only for enhancement of understanding of the background of the present specification and thus may include information that does not form the prior art that is already known to those of ordinary skill in the art.
Disclosure of Invention
The embodiment of the specification provides a workflow engine, an implementation method thereof, a computer-readable storage medium and electronic equipment, at least the workflow engine can realize flexible configuration of the business flow of burst business, and the workflow engine is beneficial to meeting burst business requirements.
Additional features and advantages of embodiments of the present description will be set forth in the detailed description which follows, or in part will be apparent from the practice of the present description.
In a first aspect, a workflow engine is provided, the workflow engine comprising:
a business process adapter for generating a process link for a business process;
a process node adapter, configured to configure a process node for the process link to obtain the service flow;
the business rule manager is used for responding to the business change operation and changing the business rule according to the business change operation; wherein, the operation of changing the above-mentioned business includes at least one of rule modifying operation, rule adding operation and rule deleting operation;
the rule engine is used for configuring the business rules for the business process;
and the flow executor is used for executing the business flow according to the business rule.
With reference to the first aspect, in some possible implementations, the workflow engine further includes:
a configuration analysis loader for loading configuration data about the business process from a database; wherein the configuration data includes first configuration data for configuring a flow;
the business process adapter is specifically configured to perform data conversion processing on the first configuration data to obtain the process link.
With reference to the first aspect, in some possible implementations, the configuration data further includes second configuration data for configuring the node; the flow node adapter includes:
the first acquisition unit is used for acquiring the node configuration sequence and the node identification corresponding to the flow link;
a second obtaining unit, configured to obtain the flow node corresponding to the node identifier from a node library, and configure control logic for the flow node according to the second configuration data;
and the node configuration unit is used for configuring the flow nodes for the flow links according to the node configuration sequence to obtain the business flow.
With reference to the first aspect, in some possible implementations, the workflow engine further includes:
And the execution logic changing module is used for responding to the logic modifying operation, determining target control logic from the control logic configured by the flow node according to the logic modifying operation and modifying the target control logic.
With reference to the first aspect, in some possible implementations, the configuration data further includes third configuration data for configuring a rule;
the execution logic changing module is further configured to respond to a logic execution limiting operation, determine a target flow node from the business flow according to the logic execution limiting operation, acquire an execution rule from the third configuration data, and configure the execution rule for the target flow node; wherein the execution rules include rules of different attributes.
With reference to the first aspect, in some possible implementations, the workflow engine further includes:
the expansion logic management module is used for responding to the logic newly-added operation, determining newly-added control logic and a target flow node in the node library according to the logic newly-added operation, and configuring the newly-added control logic for the target flow node.
With reference to the first aspect, in some possible implementations, the workflow engine further includes:
The node expansion module is used for responding to the node change operation and changing the service flow according to the node change operation; the node changing operation includes at least one of a node modifying operation, a node adding operation and a node deleting operation.
With reference to the first aspect, in some possible implementation manners, the node expansion module is specifically configured to respond to the node addition operation, change a dynamic scripting language according to the node addition operation, so as to generate an added flow node, and add the added flow node to the business flow.
In a second aspect, a method for implementing a workflow engine is provided, where the method includes: generating a flow link for the business flow; configuring a flow node for the flow link to obtain the service flow; responding to the service changing operation, and changing the service rule according to the service changing operation; wherein, the operation of changing the above-mentioned business includes at least one of rule modifying operation, rule adding operation and rule deleting operation; and configuring the business rule for the business process, and executing the business process according to the business rule.
With reference to the second aspect, in some possible implementations, before the step of generating a flow link related to the business flow, the method further includes: loading configuration data about the business processes from a database; wherein the configuration data includes first configuration data for configuring a flow; the step of generating a flow link for the business flow includes: and carrying out data conversion processing on the first configuration data to obtain the flow link.
With reference to the second aspect, in some possible implementations, the configuration data further includes second configuration data for configuring the node; the step of configuring the process node for the process link to obtain the business process includes: acquiring a node configuration sequence and a node identification corresponding to the flow link; acquiring the flow node corresponding to the node identifier from a node library, and configuring control logic for the flow node according to the second configuration data; and configuring the flow nodes for the flow links according to the node configuration sequence to obtain the business flow.
With reference to the second aspect, in some possible implementations, the method further includes: in response to a logic modification operation, determining a target control logic from control logic configured by the flow node according to the logic modification operation, and modifying the target control logic.
With reference to the second aspect, in some possible implementations, the configuration data further includes third configuration data for configuring a rule; the method further comprises the following steps: responding to logic execution limiting operation, determining a target flow node from the business flow according to the logic execution limiting operation, and acquiring an execution rule from the third configuration data; configuring the execution rule for the target flow node; wherein the execution rules include rules of different attributes.
With reference to the second aspect, in some possible implementations, the method further includes: responding to the logic adding operation, and determining new control logic and a target flow node in a node library according to the logic adding operation; and configuring the newly added control logic for the target flow node.
With reference to the second aspect, in some possible implementations, the method further includes: responding to the node changing operation, and changing the business flow according to the node changing operation; the node changing operation includes at least one of a node modifying operation, a node adding operation and a node deleting operation.
With reference to the second aspect, in some possible implementations, in a case where the node change operation includes the node addition operation, the step of, in response to the node change operation, changing the service flow according to the node change operation includes: responding to the node adding operation, and changing the dynamic scripting language according to the node adding operation so as to generate a new flow node; and adding the newly added flow section into the business flow.
In a third aspect, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements a method for implementing a workflow engine as in the above embodiment when the processor executes the computer program.
In a fourth aspect, a computer readable storage medium is provided, where instructions are stored, which when executed on a computer or a processor, cause the computer or the processor to perform a method for implementing a workflow engine as in the above embodiment.
According to another aspect of the present description, there is provided a computer program product containing instructions which, when run on a computer or processor, cause the computer or processor to perform the method of implementing a workflow engine as in the above embodiments.
The workflow engine and the implementation method, the computer-readable storage medium and the electronic device provided by the embodiments of the present specification have the following technical effects:
in the scheme provided by the embodiment of the specification, when the workflow engine realizes the business process, the business process adapter is adopted to generate the process link related to the business process, the process node adapter configures the process node for the business process according to the process link to obtain the business process, the business rule manager responds to at least one of rule modification operation, rule addition operation and rule deletion operation, so that the business rule is changed, the rule engine configures the business rule for the business process, the process executor executes the technical scheme of the business process according to the business rule, the sudden change business scene can be dealt with, and under the condition that a developer is not required to participate, the business process is convenient to flexibly change (such as modify, add and delete) the business rule of the business process according to the sudden business requirement, and the business rule changed for the business process configuration is quickly configured, so that the sudden business requirement is met, the quick release of the business process and the low-cost update of the workflow engine are realized, and the maintenance cost of the workflow engine is reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and together with the description, serve to explain the principles of the specification. It is obvious that the drawings in the following description are only some embodiments of the present specification, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 illustrates an exemplary architecture diagram of a workflow engine provided by embodiments of the present disclosure;
FIG. 2 is a flow chart illustrating a method for implementing a workflow engine according to an embodiment of the present disclosure;
FIG. 3 illustrates another exemplary architecture diagram of a workflow engine provided by embodiments of the present disclosure;
FIG. 4 is a flow diagram illustrating the generation of a flow link in the implementation method of the workflow engine according to the embodiment of the present disclosure;
FIG. 5 is a schematic diagram of a flow node adapter according to an embodiment of the present disclosure;
FIG. 6 is a flow diagram illustrating a business process generated in a method for implementing a workflow engine according to an embodiment of the present disclosure;
Fig. 7 shows a structural diagram of an electronic device in the embodiment of the present specification.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present specification more apparent, the following detailed description of the embodiments of the present specification will be given with reference to the accompanying drawings.
When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present description as detailed in the accompanying claims.
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present specification. One skilled in the relevant art will recognize, however, that the aspects of the specification may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known aspects have not been shown or described in detail to avoid obscuring aspects of the description.
Furthermore, the drawings are only schematic illustrations of the present specification and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
The workflow engine refers to a workflow (workflow) as a part of an application system, and provides a core solution for determining information delivery routes, content levels and the like according to different roles, division of work and conditions, which have a determining effect on each application system.
In a complex service system, with the change of complex services, usually, enterprise developers need to change and reconstruct complex service codes frequently, which brings great maintenance cost. A common solution is to orchestrate complex traffic using workflow engines, for example, currently common workflow engines are Activiti. Activiti has the following problems:
1. When the service processing is realized through the Activiti, the configuration flexibility of the service flow is insufficient, and when the sudden change of the service or the change of the external environment is faced, a developer is required to carry out service logic arrangement on the Activiti again, even part of codes are modified and the system release is carried out, so that the service flow cannot be processed in time through the Activiti.
2. Expansion is difficult, and it is generally desired to expand the workflow engine of the open source, on the one hand, deep knowledge of the BPMN (Business Process Modeling Notation, business process modeling and labeling) model is required, and further deep understanding of the implementation mechanism and code of the engine is required, so that the threshold and difficulty are high for developers and business personnel. Wherein the business person is not a developer.
3. The configuration capability is insufficient, a workflow engine generally provides visual configuration for a business process, but each node in the business process cannot be flexibly managed, information in the configuration is often related to program codes, the relativity is large, the method is friendly to developing personnel, the method is quite unfriendly to the business personnel, and the overall configurable rate is low. In the consumption financial business, there are various different financial products and financial scenes, and the business is frequently changed, and there are characteristics such as abrupt flow, etc., based on the Activiti, it is difficult to process and frequent business. Accordingly, the embodiments of the present specification provide a workflow engine, a method of implementing the same, a computer-readable storage medium, and an electronic device, which can solve the above-mentioned problems existing in the related art. The workflow engine provided by the embodiment of the specification is a lightweight, easy-to-maintain, expandable and configurable engine, on one hand, specific implementation details can be shielded for business personnel, and business personnel can flexibly expand business; on the other hand, by combining a rule engine, the whole configuration of the flow can be realized, the service personnel can complete the service release only through configuration in the face of service change and sudden service appeal, and the maintenance cost can be obviously reduced. Specifically, embodiments of the present specification first describe embodiments of workflow engines.
As shown in fig. 1, fig. 1 shows an exemplary architecture diagram of a workflow engine provided in an embodiment of the present disclosure. The workflow engine 100 provided in the embodiment of the present disclosure may be applied to an approval process system, a complaint handling process system, a complex business system, a management scenario requiring use of process configuration, and the like. The workflow engine 100 includes a business process adapter 110, a process node adapter 120, a business rule manager 130, a rule engine 140, and a process executor 150. As shown in fig. 2, fig. 2 is a flow chart illustrating an implementation method of the workflow engine according to the embodiment of the present disclosure. The execution subject of the implementation method of the workflow engine is an electronic device with computing capability, for example, a computer. Referring to fig. 1 and 2, the implementation method of the workflow engine includes the following schemes:
in S310, the business process adapter 110 generates a process link for the business process.
In an exemplary embodiment, a business process may be understood as a workflow, and business process adapter 110 generates a flow link for the business process, where the business scenario is different, and the generated flow link for the business process is different. If the service scene is one, generating a flow link of the service flow corresponding to the service scene, namely, the flow link is one. If the business scenes are multiple, generating flow links of the business processes corresponding to all the business scenes, namely, the flow links are multiple. For example, if the service scenario is a user registration scenario, generating a flow link of a user registration flow; the business scenario comprises a user registration scenario and a complaint processing scenario, and then a flow link of a user registration flow and a flow link of a complaint processing flow are generated.
In S320, the process node adapter 120 configures a process node for the process link to obtain the service flow.
A flow node may be understood as program logic that performs a task, and to accomplish a particular thing, a flow node may be understood. For example, when the system asks for the false, the false requesting information is filled in as the flow node filled in by the false requesting information.
After the business process adapter 110 generates the process links, the process links may indicate how the entire business process is executed, what the execution order of the entire business process is, and which of the required process nodes are. The process node adapter 120 configures a process node for the process link to obtain a business process. The method comprises the steps of planning the node position of each flow node in a flow link, and generating a complete business flow after configuring the corresponding flow node for each node position in the flow link. For example, the flow link includes 3 node positions, in order of position 1, position 2, and position 3, where the flow node 1 is configured in position 1, the flow node 2 is configured in position 2, and the flow node 3 is configured in position 3, and after the configuration of the flow node 1, the flow node 2, and the flow node 3 is completed, the business flow is generated.
In S330, the business rule manager 130 changes the business rule according to the above-described business change operation in response to the business change operation.
Business rules manager 130 can configure and alter business rules for a business process. The business rule manager 130 is provided with a visualization page, and business personnel can perform business configuration and change operations on business rules on the visualization page, so that management of business rules of a business process is realized through the business rule manager 130.
The business change operation comprises at least one of a rule modification operation, a rule addition operation and a rule deletion operation. Assuming that the generated business process is a leave-request business process, the business rule configured in advance in the leave-request business process comprises a rule 1 and a rule 2, and business personnel can execute business change operation through the visual page. For example, if the business modification operation is a rule modification operation, specifically, a modification to rule 1, then business rule manager 130 modifies rule 1 in response to the rule modification operation. If the service change operation is a rule adding operation and rule 3 is newly added, the service rule manager 130 responds to the rule adding operation to add rule 3 for the leave-looking service flow configuration. If the service change operation is a rule deletion operation, and in particular rule 1 is deleted, the service rule manager 130 deletes rule 1 in response to the rule deletion operation. By combining the workflow engine and the rule engine, the business process control and the business rule configuration are separated from the codes, so that business personnel can update and maintain the business rules, and the system maintenance cost is reduced.
In S340, the rule engine 140 configures the business rule for the business process.
In S350, the process executor 150 executes the business process according to the business rule.
After the business personnel completes the change to the business rule through the business rule manager 130, the rule engine 140 configures the changed business rule for the generated business process, and the process executor 150 executes the business process according to the business rule. For example, the changed business rule includes rule 1, and rule engine 140 configures the business rule for the business process, which is executed by process executor 150 according to business rule 1. The business process is executed by sequentially executing each process node according to the node configuration sequence. As shown in fig. 1, the business process includes 3 process nodes, and when the business process is executed, the process node 1 is executed first, then the process node 2 is executed, and finally the process node 3 is executed.
The embodiment of the specification provides a workflow engine comprising a business process adapter, a process node adapter, a business rule manager, a rule engine and a process executor, wherein when the workflow engine realizes a business process, the business process adapter is adopted to generate a process link related to the business process, the process node adapter configures a process node for the business process according to the process link to obtain the business process, the business rule manager responds to at least one of rule modification operation, rule addition operation and rule deletion operation, so as to change the business rule, the rule engine configures the business rule for the business process, the process executor executes the technical scheme of the business process according to the business rule, the business process executor can cope with the sudden change business scene, and under the condition of no participation of a developer, the business process is convenient for the business staff to flexibly change (for example, modify, add and delete) the business rule related to the business process according to the sudden business complaint, the business rule configured and the business process is quickly changed, so that the sudden business complaint is not only met, but also the quick release of the business process and the low-cost update of the business process engine are realized, and the maintenance cost of the workflow engine is reduced.
In one possible implementation, as shown in fig. 3, fig. 3 shows another exemplary architecture diagram of a workflow engine provided by an embodiment of the present disclosure.
The workflow engine 100 provided in the embodiment of the present specification further includes: node metadata configuration module 160, flow definition and configuration module 170, node manager 180, and configuration resolution loader 190. The node metadata configuration module 160 is configured to implement configuration of node basic information and node execution logic, and the node basic information and the node execution logic are stored in the database after the configuration is completed. The process definition and configuration module 170 is configured to implement configuration of the business process data and the business extension data, and the business process data and the business extension data are stored in the database after the configuration is completed. The node manager 180 is configured to implement management of nodes, and the nodes managed by the node manager 180 are stored in a node library, wherein the nodes can be previously constructed, the already constructed nodes can be modified, and the already constructed nodes can be deleted by the node manager 180. In addition, business rules managed by the business rule manager 130 described above are also stored in the quantity.
Wherein, the business process data and business expansion data stored in the database are used for realizing configuration business processes, and are called first configuration data for configuration processes; the node basic information and the node execution logic stored in the database are used for realizing node configuration, and are called second configuration data for configuring the nodes; the business rules stored in the database are used for rule configuration of the business process, referred to as third configuration data for configuring the rules.
As shown in fig. 4, fig. 4 is a flow diagram illustrating generation of a flow link in the implementation method of the workflow engine according to the embodiment of the present disclosure. Before S310, the implementation method further includes the following scheme:
in S300, the configuration resolution loader 190 loads configuration data about the above-described business processes from the database.
After business rule manager 130, node metadata configuration module 160, and flow definitions and configuration module 170 store the corresponding data in the database, configuration resolution loader 190 is responsible for loading configuration data about the business flow from the database into the program memory. The configuration data loaded by the configuration parsing loader 190 includes the first configuration data, the second configuration data, and the third configuration data. The configuration data is loaded into the program memory through the configuration analysis loader 190, so that unified allocation of the data is facilitated.
In S310', the business process adapter 110 performs data conversion processing on the first configuration data to obtain the process link.
After the configuration analysis loader 190 is responsible for loading the configuration data about the business process into the program memory from the database, the business process adapter 110 obtains the first configuration data, performs data conversion processing on the first configuration data to obtain a process link, and then stores the process link in the program memory. The data conversion processing is to convert the first configuration data into machine-recognizable data.
In a possible implementation manner, as shown in fig. 5, fig. 5 shows a schematic structural diagram of a flow node adapter provided in an embodiment of the present disclosure. The flow node adapter 120 includes a first acquisition unit 121, a second acquisition unit 121, and a node configuration unit 123.
As shown in fig. 6, fig. 6 is a flow chart illustrating a business process generated in the implementation method of the workflow engine according to the embodiment of the present disclosure. The step S320 includes the following steps:
in S321, the first obtaining unit 121 obtains the node configuration sequence and the node identifier corresponding to the flow link;
in S322, the second obtaining unit 122 obtains the flow node corresponding to the node identifier from the node library, and configures control logic for the flow node according to the second configuration data;
in S323, the node configuration unit 123 configures the flow nodes for the flow links according to the node configuration order, to obtain the service flow.
The workflow comprises a plurality of process nodes, each process node comprising a unique node identification (ID, identity document), each process node stored in the node library carrying its own unique node ID. After the flow link generation with respect to the business flow, the first acquisition unit 121 may acquire the node configuration order and the node ID of each node from the flow link. The node configuration sequence is also the execution sequence of each flow node in the subsequent business flow. The second obtaining unit 122 obtains the corresponding flow nodes from the node library according to the different node IDs, obtains the control logic corresponding to each flow node from the second configuration data according to the node IDs, configures the control logic for each flow node, and after each flow node configures the control logic, the possible flow nodes carry one control logic, the possible flow nodes carry multiple control logics, and the possible flow nodes do not carry the control logic.
The node configuration unit 123 configures flow nodes for the flow links according to the node configuration sequence, analyzes the configuration of the flow nodes, registers the configuration of the flow nodes in the program, and generates a business flow. Wherein, some flow nodes in the business flow carry at least one control logic, and some flow nodes do not carry the control logic. During the whole business process, each process node carries out corresponding execution logic according to the control logic carried by the process node. As shown in fig. 3, the business process shown in fig. 3 includes a process node 1, a process node 2, a process node 4, a process node 5, a process node 6, and a process node 7, wherein the process node 2 and the process node 4 carry control logic.
Because the whole business process is executed according to the business rules, and the business rules are configured for the whole business process by the rule engine 140, that is, the execution of each process node is controlled by the rule engine 140, the business rules configured by the rule engine 140 are different, the control of the process nodes is also different, and the flexible control of the business process according to the operation parameters and the operation results of the process nodes is realized.
In a possible implementation manner, as shown in fig. 3, the workflow engine 100 provided in the embodiment of the present disclosure further includes: the logic change module 200 is executed. The implementation method of the workflow engine further comprises the following scheme:
The execution logic change module 200 determines a target control logic from among the control logic configured by the flow node according to the logic modification operation in response to the logic modification operation, and modifies the target control logic.
For normal change of the service, the execution logic change module 200 is provided with a visual page, and a service person can modify control logic configured by a certain flow node in the generated service flow through the visual page, namely, the service person executes a limiting operation in the visual page provided by the execution logic change module 200, the execution logic change module 200 responds to the logic to execute the limiting operation, so that control logic configured by a certain flow node to be modified by the service person is obtained, the control logic is the target control logic, then the target control logic is modified, and therefore, change of the service flow is realized, and when the subsequent service flow is executed, the flow node is executed according to the modified control logic. For example, the business process a includes a process node 1, a process node 2 and a process node 3, where after the execution logic change module 200 responds to the logic to execute the limiting operation, a control logic 2 configured by the process node 1 to be modified by the business personnel is obtained, that is, the control logic 2 is a target control logic, and the control logic 2 is modified, so as to implement the change of the business process a. The control logic is modified by the execution logic changing module 200, so that the business personnel can flexibly manage the flow node control logic, and the configuration capability of the workflow engine is improved.
In a possible implementation manner, the implementation method of the workflow engine further includes the following schemes:
the execution logic changing module 200 further determines a target flow node from the business flow according to the logic execution limiting operation in response to the logic execution limiting operation, obtains an execution rule from the third configuration data, and configures the execution rule for the target flow node.
For sudden or temporary change of the service, if a certain flow node in the service flow needs to execute special control logic, service personnel can configure an execution rule for the corresponding flow node to execute the special control logic, and the special control logic is a certain control logic configured by the flow node. The execution rules comprise rules with different attributes, for example, the execution rules comprise time period rules, age rules, business type rules and the like, and certain control logic configured by the flow node can be controlled to be executed within a certain time period through the time period rules; the special control logic configured by the flow node can be controlled to be executed through the age rule, if the age range is set to be 20 years to 25 years in the age rule, and the age of the personnel associated with the business to be processed is 22 years, the special control logic configured by the flow node is executed; the special control logic configured by the flow node can be controlled to execute through the service type rule, and if the type set by the service type rule comprises a type A and a type B, the type related to the service to be processed is the type A, the special control logic configured by the flow node is executed.
The execution rules are configured by the business rule manager 130, i.e. the third configuration data loaded from the database by the configuration resolution loader 190 includes the execution rules.
The service personnel execute the logic execution limiting operation in the visual page provided by the execution logic changing module 200, the execution logic changing module 200 responds to the logic execution limiting operation, determines a target flow node from the service flow through the logic execution limiting operation, acquires the execution rule from the third configuration data, and configures the execution rule for the target flow node. When a target flow node executes, the execution rules will restrict the target flow node to execute with some control logic of its own. For example, the target flow node is the flow node 2, the control logic configured by the flow node 2 comprises a control logic 1 and a control logic 2, the flow node 2 is executed according to the control logic 1 at 8-12 hours a day, the flow node is not executed according to the control logic 2, and the flow node 2 is executed according to the control logic 1 and the control logic 2 at other times than 8-12 hours a day. After the execution logic is configured for the flow node 2, the flow node 2 is always executed according to the control logic 1 within 8-12 hours, and the flow node 2 is executed according to the control logic 1 and the control logic 2 at a time other than 8-12 hours. The flexible management of the flow node control logic is realized, the sudden or temporary change of the strain service is facilitated, and the abrupt service scene is satisfied.
In a possible implementation manner, as shown in fig. 3, the workflow engine 100 provided in the embodiment of the present disclosure further includes: the expansion logic management module 210. The implementation method of the workflow engine further comprises the following scheme:
the expansion logic management module 210 responds to the logic adding operation, determines the adding control logic and the target flow node in the node library according to the logic adding operation, and configures the adding control logic for the target flow node.
For normal change of the service, a developer can add expansion logic to any flow node in the node library through the expansion logic management module 210, and the expansion logic can be understood as newly added control logic, wherein any flow node in the node library can be regarded as a target flow node. The developer executes the logic newly-added operation through the visual page provided by the expansion logic management module 210, the expansion logic management module 210 responds to the logic newly-added operation, determines newly-added control logic and a target flow node in the node library according to the logic newly-added operation, and then configures the newly-added control logic for the target flow node. For example, the target flow node is a flow node 5 in the node library, the newly added control logic is an expansion logic a and an expansion logic B, the expansion logic a and the expansion logic B are configured for the flow node 5, and if the generated business flow includes the flow node 5, the flow node 5 is executed according to the expansion logic a and the expansion logic B.
In a possible implementation manner, as shown in fig. 3, the workflow engine 100 provided in the embodiment of the present disclosure further includes: the node extension module 220. The implementation method of the workflow engine further comprises the following scheme:
the node extension module 220 responds to the node changing operation and changes the business process according to the node changing operation.
The node change operation includes at least one of a node modification operation, a node addition operation, and a node deletion operation. The service personnel execute the node changing operation through the visual page provided by the node expanding module 220, and the node expanding module 220 responds to the node changing operation and changes the flow nodes in the service flow according to the node changing operation. For example, if the node change operation is a node modification operation, determining a flow node to be modified in the business flow through the node modification operation, and modifying the flow node to be modified to implement the change of the business flow. For example, if the flow node to be modified is the flow node 1 in the business flow shown in fig. 3, the flow node 1 is modified.
If the node changing operation is the node adding operation, adding a new flow node in the business flow, and realizing the change of the business flow. For example, the new flow node is flow node 8, and flow node 8 is added between flow node 6 and flow node 7 in the business flow shown in fig. 3.
If the node changing operation is the node deleting operation, determining the flow node to be deleted in the service flow through the node deleting operation, deleting the flow node to be deleted, and realizing the change of the service flow, so that service staff can conveniently deal with the emergency changed service. For example, if the flow node to be deleted is the flow node 6 in the business flow shown in fig. 3, the flow node 6 is deleted.
In a possible implementation manner, in a case where the node change operation includes the node add operation, the node expansion module 220 is specifically configured to respond to the node add operation, change the dynamic scripting language according to the node add operation, so as to generate an add flow node, and add the add flow node to the business flow.
When the node changing operation is the node newly adding operation, the service personnel execute the node changing operation through the visual page provided by the node expanding module 220, the node expanding module 220 responds to the node changing operation and modifies the dynamic script language, so as to generate a newly added flow node, the newly added flow node is added into the service flow, and the new flow node is added into the service flow. The node expansion module 220 defines a uniform father node and a node execution method through the SPI, and combines a dynamic script language to generate a newly added flow node, so that the newly added flow node can be supported to be dynamically configured into a program, emergency service newly added requirements can be conveniently handled by service personnel, and the expansibility of the program is improved.
The workflow engine provided by the embodiment of the specification realizes the modularization, structuring and high-expansion splitting of the business logic, and improves the stability, high maintainability and flexibility of the workflow engine. When the business personnel face the sudden change or temporary change business, the business personnel can change the business rules of the business process, the process nodes, the control logic of the process nodes and the execution rules of the process nodes through the workflow engine according to the change requirement of the business, the participation of developers is not needed, the business personnel are favorable for meeting the change requirement of the business, and the maintenance cost is reduced.
The above-described figures are merely schematic illustrations of processes involved in a method according to exemplary embodiments of the present description, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
The embodiments of the present specification also provide an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of any of the methods of the embodiments described above when the program is executed by the processor.
Fig. 7 shows a structural diagram of an electronic device in the embodiment of the present specification. Referring to fig. 7, an electronic device 700 includes: a processor 701 and a memory 702.
In the embodiment of the present disclosure, the processor 701 is a control center of a computer system, and may be a processor of a physical machine or a processor of a virtual machine. Processor 701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 701 may be implemented in hardware in at least one of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), programmable logic array (Programmable Logic Array, PLA). Processor 701 may also include a main processor, which is a processor for processing data in an awake state, and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state.
In the embodiment of the present disclosure, the processor 701 is specifically configured to: generating a flow link for the business flow; configuring a flow node for the flow link to obtain the service flow; responding to the service changing operation, and changing the service rule according to the service changing operation; wherein, the operation of changing the above-mentioned business includes at least one of rule modifying operation, rule adding operation and rule deleting operation; and configuring the business rule for the business process, and executing the business process according to the business rule.
Further, the processor 701 is further configured to: loading configuration data about the business processes from a database; wherein the configuration data includes first configuration data for configuring a flow; the step of generating a flow link for the business flow includes: and carrying out data conversion processing on the first configuration data to obtain the flow link.
Further, the configuration data further includes second configuration data for configuring the node, and the processor 701 is further configured to: acquiring a node configuration sequence and a node identification corresponding to the flow link; acquiring the flow node corresponding to the node identifier from a node library, and configuring control logic for the flow node according to the second configuration data; and configuring the flow nodes for the flow links according to the node configuration sequence to obtain the business flow.
Further, the processor 701 is further configured to: in response to a logic modification operation, determining a target control logic from control logic configured by the flow node according to the logic modification operation, and modifying the target control logic.
Further, the configuration data further includes third configuration data for configuring rules, and the processor 701 is further configured to: responding to logic execution limiting operation, determining a target flow node from the business flow according to the logic execution limiting operation, and acquiring an execution rule from the third configuration data; configuring the execution rule for the target flow node; wherein the execution rules include rules of different attributes.
Further, the processor 701 is further configured to: responding to the logic adding operation, and determining new control logic and a target flow node in a node library according to the logic adding operation; and configuring the newly added control logic for the target flow node.
Further, the processor 701 is further configured to: responding to the node changing operation, and changing the business flow according to the node changing operation; the node changing operation includes at least one of a node modifying operation, a node adding operation and a node deleting operation.
Further, the processor 701 is further configured to: responding to the node adding operation, and changing the dynamic scripting language according to the node adding operation so as to generate a new flow node; and adding the newly added flow section into the business flow.
Memory 702 may include one or more computer-readable storage media, which may be non-transitory. The memory 702 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments of the present description, a non-transitory computer readable storage medium in memory 702 is used to store at least one instruction for execution by processor 701 to implement the methods in embodiments of the present description.
In some embodiments, the electronic device 700 further includes: a peripheral interface 703 and at least one peripheral. The processor 701, the memory 702, and the peripheral interface 703 may be connected by a bus or signal lines. The individual peripheral devices may be connected to the peripheral device interface 703 via buses, signal lines or a circuit board. Specifically, the peripheral device includes: at least one of a display 704, a camera 705, and an audio circuit 706.
A peripheral interface 703 may be used to connect at least one Input/Output (I/O) related peripheral to the processor 701 and memory 702. In some embodiments of the present description, the processor 701, the memory 702, and the peripheral interface 703 are integrated on the same chip or circuit board; in some other embodiments of the present description, either or both of the processor 701, the memory 702, and the peripheral interface 703 may be implemented on separate chips or circuit boards. The embodiment of the present specification is not particularly limited thereto.
The display screen 704 is used to display a User Interface (UI). The UI may include graphics, text, icons, video, and any combination thereof. When the display 704 is a touch display, the display 704 also has the ability to collect touch signals at or above the surface of the display 704. The touch signal may be input to the processor 701 as a control signal for processing. At this point, the display 704 may also be used to provide virtual buttons and/or virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments of the present description, the display 704 may be one, providing a front panel of the electronic device 700; in other embodiments of the present disclosure, the display 704 may be at least two, respectively disposed on different surfaces of the electronic device 700 or in a folded design; in still other embodiments of the present description, the display 704 may be a flexible display disposed on a curved surface or a folded surface of the electronic device 700. Even more, the display screen 704 may be arranged in a non-rectangular irregular pattern, i.e., a shaped screen. The display 704 may be made of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.
The camera 705 is used to capture images or video. Optionally, camera 705 includes a front camera and a rear camera. In general, a front camera is disposed on a front panel of an electronic device, and a rear camera is disposed on a rear surface of the electronic device. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments of the present description, camera 705 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.
The audio circuit 706 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 701 for processing. For purposes of stereo acquisition or noise reduction, the microphone may be multiple, and disposed at different locations of the electronic device 700. The microphone may also be an array microphone or an omni-directional pickup microphone.
The power supply 707 is used to power the various components in the electronic device 700. The power supply 707 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power supply 707 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.
The block diagrams of the electronic device shown in the embodiments of the present specification do not constitute a limitation of the electronic device 700, and the electronic device 700 may include more or less components than illustrated, or may combine some components, or may employ different arrangements of components.
In the description of the present specification, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The specific meaning of the terms in this specification will be understood by those of ordinary skill in the art in the light of the specific circumstances. In addition, in the description of the present specification, unless otherwise indicated, "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
The present description also provides a computer-readable storage medium having instructions stored therein, which when executed on a computer or processor, cause the computer or processor to perform one or more steps of the above embodiments. The constituent modules of the workflow engine may be stored in the computer-readable storage medium if implemented in the form of software functional units and sold or used as independent products.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product described above includes one or more computer instructions. When the computer program instructions described above are loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present specification are all or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted across a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage media may be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a digital versatile Disk (Digital Versatile Disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
It should be noted that the foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The foregoing is merely specific embodiments of the present disclosure, but the scope of the disclosure is not limited thereto, and any person skilled in the art who is skilled in the art can easily think about variations or substitutions within the scope of the disclosure. Accordingly, equivalent variations from the claims of the present specification are intended to be covered by the present specification.
Claims (18)
1. A workflow engine, wherein the workflow engine comprises:
a business process adapter for generating a process link for a business process;
a process node adapter, configured to configure a process node for the process link to obtain the service flow;
The business rule manager is used for responding to business change operation and changing business rules according to the business change operation; wherein the service change operation comprises at least one of a rule modification operation, a rule addition operation and a rule deletion operation;
a rule engine for configuring the business rule for the business process;
and the flow executor is used for executing the business flow according to the business rule.
2. The workflow engine of claim 1, wherein the workflow engine further comprises:
a configuration analysis loader for loading configuration data about the business process from a database; wherein the configuration data comprises first configuration data for configuring a flow;
the business process adapter is specifically configured to perform data conversion processing on the first configuration data to obtain the process link.
3. The workflow engine of claim 2, wherein the configuration data further comprises second configuration data for configuring a node;
the flow node adapter comprises:
the first acquisition unit is used for acquiring the node configuration sequence and the node identification corresponding to the flow link;
The second obtaining unit is used for obtaining the flow node corresponding to the node identifier from a node library and configuring control logic for the flow node according to the second configuration data;
and the node configuration unit is used for configuring the flow nodes for the flow links according to the node configuration sequence to obtain the business flow.
4. The workflow engine of claim 3, wherein the workflow engine further comprises:
and the execution logic changing module is used for responding to logic modifying operation, determining target control logic from control logic configured by the flow node according to the logic modifying operation and modifying the target control logic.
5. The workflow engine of claim 4, wherein the configuration data further comprises third configuration data for configuring rules;
the execution logic changing module is further configured to respond to a logic execution limiting operation, determine a target flow node from the business flow according to the logic execution limiting operation, acquire an execution rule from the third configuration data, and configure the execution rule for the target flow node; wherein the execution rules include rules of different attributes.
6. The workflow engine of any one of claims 1 to 5, wherein the workflow engine further comprises:
the expansion logic management module is used for responding to the logic newly-added operation, determining newly-added control logic and a target flow node in the node library according to the logic newly-added operation, and configuring the newly-added control logic for the target flow node.
7. The workflow engine of any one of claims 1 to 5, wherein the workflow engine further comprises:
the node expansion module is used for responding to the node change operation and changing the business flow according to the node change operation; the node change operation comprises at least one of a node modification operation, a node addition operation and a node deletion operation.
8. The workflow engine of claim 7, wherein the node expansion module is specifically configured to respond to the node addition operation, change a dynamic scripting language according to the node addition operation, so as to generate an added flow node, and add the added flow node to the business flow.
9. A method of implementing a workflow engine, wherein the method comprises:
Generating a flow link for the business flow;
configuring a flow node for the flow link to obtain the business flow;
responding to a service change operation, and changing a service rule according to the service change operation; wherein the service change operation comprises at least one of a rule modification operation, a rule addition operation and a rule deletion operation;
and configuring the business rule for the business process, and executing the business process according to the business rule.
10. The method of claim 9, wherein prior to the step of generating a flow link for a business flow, the method further comprises:
loading configuration data about the business process from a database; wherein the configuration data comprises first configuration data for configuring a flow;
the step of generating a flow link for a business flow includes:
and carrying out data conversion processing on the first configuration data to obtain the flow link.
11. The method of claim 10, wherein the configuration data further comprises second configuration data for configuring a node;
the step of configuring a process node for the process link to obtain the business process includes:
Acquiring a node configuration sequence and a node identification corresponding to the flow link;
acquiring the flow node corresponding to the node identifier from a node library, and configuring control logic for the flow node according to the second configuration data;
and configuring the flow nodes for the flow links according to the node configuration sequence to obtain the business flow.
12. The method of claim 11, wherein the method further comprises:
in response to a logic modification operation, determining a target control logic from control logic configured by the flow node according to the logic modification operation, and modifying the target control logic.
13. The method of claim 11, wherein the configuration data further comprises third configuration data for a configuration rule;
the method further comprises the steps of:
responding to logic execution limiting operation, determining a target flow node from the business flow according to the logic execution limiting operation, and acquiring an execution rule from the third configuration data;
configuring the execution rule for the target flow node; wherein the execution rules include rules of different attributes.
14. The method of any of claims 9 to 13, wherein the method further comprises:
Responding to a logic adding operation, and determining a new control logic and a target flow node in a node library according to the logic adding operation;
and configuring the newly added control logic for the target flow node.
15. The method of any of claims 9 to 13, wherein the method further comprises:
responding to a node changing operation, and changing the business flow according to the node changing operation; the node change operation comprises at least one of a node modification operation, a node addition operation and a node deletion operation.
16. The method of claim 15, wherein, in the event that the node change operation includes the node add operation, the step of changing the business process in accordance with the node change operation in response to the node change operation comprises:
responding to the node adding operation, and changing a dynamic script language according to the node adding operation so as to generate a newly added flow node;
and adding the newly added flow section into the business flow.
17. A computer readable storage medium having instructions stored therein which, when run on a computer or processor, cause the computer or processor to perform a method of implementing a workflow engine of any of claims 9 to 16.
18. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements a method of implementing a workflow engine according to any of claims 9 to 16 when the computer program is executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310646006.5A CN116911766A (en) | 2023-06-01 | 2023-06-01 | Workflow engine and implementation method thereof, readable storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310646006.5A CN116911766A (en) | 2023-06-01 | 2023-06-01 | Workflow engine and implementation method thereof, readable storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116911766A true CN116911766A (en) | 2023-10-20 |
Family
ID=88365643
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310646006.5A Pending CN116911766A (en) | 2023-06-01 | 2023-06-01 | Workflow engine and implementation method thereof, readable storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116911766A (en) |
-
2023
- 2023-06-01 CN CN202310646006.5A patent/CN116911766A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109324787B (en) | Business software development method and device and terminal equipment | |
| US20240184438A1 (en) | Interactive content generation method and apparatus, and storage medium and electronic device | |
| CN109523187A (en) | Method for scheduling task, device and equipment | |
| CN111598533A (en) | Process approval processing method and device, electronic equipment and storage medium | |
| CN112181576A (en) | Form processing method, device, terminal and storage medium | |
| CN109634764A (en) | Work-flow control method, apparatus, equipment, storage medium and system | |
| CN110070592B (en) | Generation method and device of special effect package and hardware device | |
| CN110727869A (en) | Page construction method and device | |
| CN111144837A (en) | Flow arrangement method and device, storage medium and electronic equipment | |
| CN115526578A (en) | Method and device for generating project flow, electronic equipment and storage medium | |
| CN113220366A (en) | Sub-application starting method and device, terminal and server | |
| CN112764802A (en) | Business logic customization method and device, electronic equipment and storage medium | |
| CN114882333B (en) | Training method and device of data processing model, electronic equipment and storage medium | |
| CN116136758A (en) | Page generation method, device, equipment and medium | |
| CN117389647A (en) | Plug-in generation method, application development method, device, equipment and medium | |
| CN112558968A (en) | Resource tree view generation method, device, equipment and storage medium | |
| US20210097772A1 (en) | Creation and management of virtual twins using geometric primitives | |
| CN114998068B (en) | Learning plan generation method and electronic equipment | |
| CN113138996A (en) | Statement generation method and device | |
| CN116911766A (en) | Workflow engine and implementation method thereof, readable storage medium and electronic equipment | |
| CN106815765A (en) | A kind of asset allocation method and apparatus | |
| CN113778542B (en) | Service configuration table generation method and device | |
| CN114968960A (en) | Log processing method and device, computer equipment and storage medium | |
| CN112418796A (en) | Sub-process node activation method and device, electronic equipment and storage medium | |
| CN109885707A (en) | The method for refreshing of picture, device, terminal device and storage medium in picture library |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |