CN111831461A - Method and device for processing business process - Google Patents
Method and device for processing business process Download PDFInfo
- Publication number
- CN111831461A CN111831461A CN202010620833.3A CN202010620833A CN111831461A CN 111831461 A CN111831461 A CN 111831461A CN 202010620833 A CN202010620833 A CN 202010620833A CN 111831461 A CN111831461 A CN 111831461A
- Authority
- CN
- China
- Prior art keywords
- event
- workflow
- execution
- execute
- business
- 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
Images
Classifications
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
Abstract
The invention discloses a method and a device for processing a business process, and relates to the technical field of computers. One embodiment of the method comprises: receiving an event notification transmitted by a service flow, wherein the event notification carries an event type; matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic; receiving an execution result returned by the workflow framework, wherein the execution result carries an event type; matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic; or, the execution result is transmitted to the business process. The implementation method can solve the technical problem of strong coupling of the business process and the control process.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for processing a business process.
Background
Traditional flow control is written in the business logic and synchronization triggers execution of the workflow, resulting in binding of the business content to the workflow framework. The person writing the logical code must know about the workflow framework, resulting in high code maintenance costs.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
the process code is coupled into the service code, so that the modification of the service affects the change of the process. The complete service code cannot be abstracted, resulting in low reuse degree. The strong coupling of the business process and the control process increases the updating and upgrading difficulty of the workflow.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for processing a service flow, so as to solve the technical problem of strong coupling between the service flow and a control flow.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method for processing a business process, including:
receiving an event notification transmitted by a service flow, wherein the event notification carries an event type;
matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic;
receiving an execution result returned by the workflow framework, wherein the execution result carries an event type;
matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic; or, the execution result is transmitted to the business process.
Optionally, the event types include a process starting event, an internal event of a process execution link, and a token event for driving the next step of the process flow.
Optionally, the process starting event is triggered by an application entry of the business process; the internal event is triggered by a pre-event of the workflow framework; the token event is triggered by an automatic task invocation of the business logic.
Optionally, executing the business logic includes:
creating a flow based on business logic corresponding to a flow starting event, wherein the flow comprises a plurality of nodes;
if the next node is an automatic node, triggering the business logic corresponding to the internal event;
if the next node is a manual intervention node, waiting for the completion of the execution of the manual node service logic;
automatically triggering a token event.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes:
based on the distributed message middleware, sending an execution message to a workflow framework to enable the workflow framework to execute the business logic.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes:
based on the message consumption component, an execution message is sent to the workflow framework to cause the workflow framework to execute the business logic.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes:
and inserting the event information into a database, and reading the event information in the database by using an automatic task server so as to enable the workflow framework to execute the business logic.
In addition, according to another aspect of the embodiments of the present invention, there is provided an apparatus for processing a business process, including:
the first receiving module is used for receiving an event notification transmitted by a service process, wherein the event notification carries an event type;
the first sending module is used for matching out a corresponding service logic according to the event type and sending an execution message to a workflow frame so as to enable the workflow frame to execute the service logic;
the second receiving module is used for receiving an execution result returned by the workflow framework, and the execution result carries an event type;
the second sending module is used for matching out corresponding service logic according to the event type and sending an execution message to a workflow frame so as to enable the workflow frame to execute the service logic; or, the execution result is transmitted to the business process.
Optionally, the event types include a process starting event, an internal event of a process execution link, and a token event for driving the next step of the process flow.
Optionally, the process starting event is triggered by an application entry of the business process; the internal event is triggered by a pre-event of the workflow framework; the token event is triggered by an automatic task invocation of the business logic.
Optionally, executing the business logic includes:
creating a flow based on business logic corresponding to a flow starting event, wherein the flow comprises a plurality of nodes;
if the next node is an automatic node, triggering the business logic corresponding to the internal event;
if the next node is a manual intervention node, waiting for the completion of the execution of the manual node service logic;
automatically triggering a token event.
Optionally, the first sending module is further configured to:
based on the distributed message middleware, sending an execution message to a workflow framework to enable the workflow framework to execute the business logic.
Optionally, the first sending module is further configured to:
based on the message consumption component, an execution message is sent to the workflow framework to cause the workflow framework to execute the business logic.
Optionally, the first sending module is further configured to:
and inserting the event information into a database, and reading the event information in the database by using an automatic task server so as to enable the workflow framework to execute the business logic.
According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any of the embodiments described above.
According to another aspect of the embodiments of the present invention, there is also provided a computer readable medium, on which a computer program is stored, which when executed by a processor implements the method of any of the above embodiments.
One embodiment of the above invention has the following advantages or benefits: because the technical means of matching the corresponding service logic according to the event type and sending the execution message to the workflow framework so as to enable the workflow framework to execute the service logic is adopted, the technical problem of strong coupling between the service flow and the control flow in the prior art is solved. The embodiment of the invention improves the real-time performance through the AOP and the event mechanism, realizes the decoupling with the business process with the maximum force, realizes the separation and the mapping of the business process control and the technical process through the definition of various events, and realizes the workflow circulation based on the event drive by adopting the technical means of kafka, ActiveMq or a database table and the like.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of a main flow of a method of processing a business flow according to an embodiment of the invention;
FIG. 2 is a schematic diagram of decoupling a business process from a workflow according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a configuration interceptor according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of content intercepted by an interceptor according to an embodiment of the present invention;
FIG. 5 is a schematic view of a main flow of a method of processing a business flow according to one referential embodiment of the present invention;
FIG. 6 is a schematic diagram of the main modules of an apparatus for processing a business process in accordance with an embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 8 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main flow of a method for processing a business flow according to an embodiment of the present invention. As an embodiment of the present invention, as shown in fig. 1, the method for processing a business process may include:
step 101, receiving an event notification transmitted by a service flow, wherein the event notification carries an event type.
In order to decouple the business process from the workflow, as shown in fig. 2, the embodiment of the present invention designs a mapping relationship between an event and a process, so as to isolate the business process from the workflow.
In this step, an event notification delivered by the service flow is received, where the event notification carries an event type. The embodiment of the invention divides events into three types, which are respectively as follows: a process starting event, an internal event of a process execution link and a token (token) event for driving the process flow to the next step.
The workflow can be divided into automatic nodes and manual nodes. Where artificial nodes tend to bind executed workflow actions to specific business logic. In order to solve this problem, in the process of business logic circulation, interceptors must be configured for each link that may generate creation, circulation and termination of the workflow, as shown in fig. 3. And intercepting the business process, namely intercepting the manually intervened nodes through AOP configuration, and triggering the process flow to the next step through an interceptor after the business logic execution of the manual nodes is finished. AOP: the method is a technique for realizing unified maintenance of program functions by a precompilation mode and a running-period dynamic proxy facing to section programming.
For example, as shown in FIG. 4, during the approval process of the business card, the following are intercepted:
post-approval process (internal events)
One trial and repair part (internal event)
One trial (token event)
Artificial credit (internal event)
Second examine (token event)
Credit waiting element (token event)
Initial workflow (flow initiating event)
Three audits (token event)
Optionally, the process starting event is triggered by an application entry of the business process; the internal event is triggered by a pre-event of the workflow framework; the token event is triggered by an automatic task invocation of the business logic.
And 102, matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic.
And after matching the corresponding service logic according to the event type, sending an execution message to a workflow frame so as to enable the workflow frame to asynchronously execute the service logic.
Optionally, executing the business logic includes:
creating a flow based on business logic corresponding to a flow starting event, wherein the flow comprises a plurality of nodes;
if the next node is an automatic node, triggering the business logic corresponding to the internal event;
if the next node is a manual intervention node, waiting for the completion of the execution of the manual node service logic;
automatically triggering a token event.
For example, when a flow is started, an internally defined flow starting event is generated by a business flow code as a producer of a message and is acquired by a workflow framework as a consumer of the message, and then a corresponding flow starting node is created.
For example, after a Workflow Framework (WFE) creates a flow based on a flow initiation event, a cross-check automation stage is entered. The WFE pre-event of the automation node triggers an internal event to execute the business logic of the automation node. The cross-checking business logic is executed, for example, upon receipt of an incoming cross-check automation link event. After the cross-checking service is over, the token event is automatically triggered to be consumed by the WFE and then the flow is switched to the next step.
If the next node is also an automatic node, the step of cross checking the service logic is repeatedly executed, if the next node is a manual intervention node, the next node is triggered to reach the manual node by the WFE leading event of the manual node, then the manual node service logic is waited to be executed, and after the manual node service logic is executed, the next node is intercepted by an interceptor to trigger the token event to flow to the next step. And repeating the steps till the flow is finished.
On the asynchronous mechanism of events, the embodiment of the invention is mainly based on kafka distributed message middleware (a high-throughput distributed publish-subscribe message system), ActiveMQ (an open-source message middleware) and multiple implementation modes of data asynchronous tasks.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes: based on the distributed message middleware, sending an execution message to a workflow framework to enable the workflow framework to execute the business logic. The execution message may be sent to a distributed message middleware that buffers the synchronization data and then asynchronously synchronizes the execution message into the process processing system.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes: based on the message consumption component, an execution message is sent to the workflow framework to cause the workflow framework to execute the business logic. The message consumption component subscribes to messages of the distributed message middleware. And after the AOP intercepts the event, the message is produced, and then the message consumption component promotes the processing of the flow according to the content of the message.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes: and inserting the event information into a database, and reading the event information in the database by using an automatic task server so as to enable the workflow framework to execute the business logic. And controlling the flow based on the database table, and reading the event information of the database and promoting the flow of the flow by inserting the event information into the database and utilizing the automatic task server.
According to the AOP-based non-invasive asynchronous event workflow framework, the control of pushing the workflow according to different events can be realized in the form of kafka, ActiveMq or a database table according to different deployment forms, and the workflow circulation based on event driving is realized.
Therefore, the embodiment of the invention can decouple the process engine from the actual logic code through the event.
And 103, receiving an execution result returned by the workflow framework, wherein the execution result carries an event type.
And after the workflow framework executes the service logic, returning an execution result, wherein the execution result carries the event type. The driver flow can continue according to the execution results returned by the workflow framework.
Step 104, matching out a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic; or, the execution result is transmitted to the business process.
Similar to step 102, after matching out the corresponding service logic according to the event type, sending an execution message to a workflow framework, so that the workflow framework asynchronously executes the service logic.
And if no node to be processed exists subsequently, transmitting the execution result of the workflow framework to the business process.
According to the various embodiments described above, it can be seen that the technical means of the embodiments of the present invention, by matching out the corresponding service logic according to the event type and sending the execution message to the workflow framework, so as to enable the workflow framework to execute the service logic, solves the technical problem of strong coupling between the service flow and the control flow in the prior art. The embodiment of the invention improves the real-time performance through the AOP and the event mechanism, realizes the decoupling with the business process with the maximum force, realizes the separation and the mapping of the business process control and the technical process through the definition of various events, and realizes the workflow circulation based on the event drive by adopting the technical means of kafka, ActiveMq or a database table and the like.
Fig. 5 is a schematic diagram of a main flow of a method of processing a business flow according to a referential embodiment of the present invention. As another embodiment of the present invention, as shown in fig. 5, the method for processing a business process may include:
step 501, receiving an event notification transmitted by a service flow, where the event notification carries an event type.
In this step, an event notification delivered by the service flow is received, where the event notification carries an event type. The embodiment of the invention divides events into three types, which are respectively as follows: a process starting event, an internal event of a process execution link and a token (token) event for driving the process flow to the next step.
The workflow can be divided into automatic nodes and manual nodes. Where artificial nodes tend to bind executed workflow actions to specific business logic. In order to solve the problem, in the process of the business logic circulation, an interceptor must be configured for each link which may generate the creation, circulation and termination of the workflow. And intercepting the business process, namely intercepting the manually intervened nodes through AOP configuration, and triggering the process flow to the next step through an interceptor after the business logic execution of the manual nodes is finished.
Optionally, the process starting event is triggered by an application entry of the business process; the internal event is triggered by a pre-event of the workflow framework; the token event is triggered by an automatic task invocation of the business logic.
Step 502, matching out a corresponding service logic according to the event type, and sending an execution message to a workflow frame, so that the workflow frame executes the service logic.
And after matching the corresponding service logic according to the event type, sending an execution message to a workflow frame so as to enable the workflow frame to asynchronously execute the service logic.
Optionally, executing the business logic includes:
creating a flow based on business logic corresponding to a flow starting event, wherein the flow comprises a plurality of nodes;
if the next node is an automatic node, triggering the business logic corresponding to the internal event;
if the next node is a manual intervention node, waiting for the completion of the execution of the manual node service logic;
automatically triggering a token event.
On the asynchronous mechanism of events, the embodiment of the invention is mainly based on kafka distributed message middleware (a high-throughput distributed publish-subscribe message system), ActiveMQ (an open-source message middleware) and multiple implementation modes of data asynchronous tasks.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes: based on the distributed message middleware, sending an execution message to a workflow framework to enable the workflow framework to execute the business logic. The execution message may be sent to a distributed message middleware that buffers the synchronization data and then asynchronously synchronizes the execution message into the process processing system.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes: based on the message consumption component, an execution message is sent to the workflow framework to cause the workflow framework to execute the business logic. The message consumption component subscribes to messages of the distributed message middleware. And after the AOP intercepts the event, the message is produced, and then the message consumption component promotes the processing of the flow according to the content of the message.
Optionally, sending an execution message to a workflow framework to cause the workflow framework to execute the business logic includes: and inserting the event information into a database, and reading the event information in the database by using an automatic task server so as to enable the workflow framework to execute the business logic. And controlling the flow based on the database table, and reading the event information of the database and promoting the flow of the flow by inserting the event information into the database and utilizing the automatic task server.
According to the AOP-based non-invasive asynchronous event workflow framework, the control of pushing the workflow according to different events can be realized in the form of kafka, ActiveMq or a database table according to different deployment forms, and the workflow circulation based on event driving is realized.
Step 503, receiving an execution result returned by the workflow framework, where the execution result carries an event type.
And after the workflow framework executes the service logic, returning an execution result, wherein the execution result carries the event type. The driver flow can continue according to the execution results returned by the workflow framework.
Step 504, matching out a corresponding service logic according to the event type, and sending an execution message to a workflow framework to enable the workflow framework to execute the service logic.
Similar to step 502, after matching out the corresponding service logic according to the event type, sending an execution message to a workflow framework, so that the workflow framework asynchronously executes the service logic.
And step 505, transmitting the execution result to the business process.
And if no node to be processed exists subsequently, transmitting the execution result of the workflow framework to the business process.
In addition, in a reference embodiment of the present invention, the detailed implementation content of the method for processing business process is already described in detail in the above-mentioned method for processing business process, so the repeated content is not described again.
Fig. 6 is a schematic diagram of main modules of an apparatus for processing a business process according to an embodiment of the present invention, and as shown in fig. 6, the apparatus 600 for processing a business process includes a first receiving module 601, a first sending module 602, a second receiving module 603, and a second sending module 604; the first receiving module 601 is configured to receive an event notification transmitted by a service flow, where the event notification carries an event type; the first sending module 602 is configured to match a corresponding service logic according to the event type, and send an execution message to a workflow framework, so that the workflow framework executes the service logic; the second receiving module 603 receives an execution result returned by the workflow framework, where the execution result carries an event type; the second sending module 604 matches a corresponding service logic according to the event type, and sends an execution message to a workflow frame, so that the workflow frame executes the service logic; or, the execution result is transmitted to the business process.
Optionally, the event types include a process starting event, an internal event of a process execution link, and a token event for driving the next step of the process flow.
Optionally, the process starting event is triggered by an application entry of the business process; the internal event is triggered by a pre-event of the workflow framework; the token event is triggered by an automatic task invocation of the business logic.
Optionally, executing the business logic includes:
creating a flow based on business logic corresponding to a flow starting event, wherein the flow comprises a plurality of nodes;
if the next node is an automatic node, triggering the business logic corresponding to the internal event;
if the next node is a manual intervention node, waiting for the completion of the execution of the manual node service logic;
automatically triggering a token event.
Optionally, the first sending module 602 is further configured to:
based on the distributed message middleware, sending an execution message to a workflow framework to enable the workflow framework to execute the business logic.
Optionally, the second sending module 604 is further configured to:
based on the distributed message middleware, sending an execution message to a workflow framework to enable the workflow framework to execute the business logic.
Optionally, the first sending module 602 is further configured to:
based on the message consumption component, an execution message is sent to the workflow framework to cause the workflow framework to execute the business logic.
Optionally, the second sending module 604 is further configured to:
based on the message consumption component, an execution message is sent to the workflow framework to cause the workflow framework to execute the business logic.
Optionally, the first sending module 602 is further configured to:
and inserting the event information into a database, and reading the event information in the database by using an automatic task server so as to enable the workflow framework to execute the business logic.
Optionally, the second sending module 604 is further configured to:
and inserting the event information into a database, and reading the event information in the database by using an automatic task server so as to enable the workflow framework to execute the business logic.
According to the various embodiments described above, it can be seen that the technical means of the embodiments of the present invention, by matching out the corresponding service logic according to the event type and sending the execution message to the workflow framework, so as to enable the workflow framework to execute the service logic, solves the technical problem of strong coupling between the service flow and the control flow in the prior art. The embodiment of the invention improves the real-time performance through the AOP and the event mechanism, realizes the decoupling with the business process with the maximum force, realizes the separation and the mapping of the business process control and the technical process through the definition of various events, and realizes the workflow circulation based on the event drive by adopting the technical means of kafka, ActiveMq or a database table and the like.
It should be noted that, in the implementation of the apparatus for processing business process according to the present invention, the method for processing business process described above has been described in detail, and therefore, the repeated content is not described herein.
Fig. 7 illustrates an exemplary system architecture 700 of a method of processing a business process or an apparatus for processing a business process to which embodiments of the invention may be applied.
As shown in fig. 7, the system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 serves to provide a medium for communication links between the terminal devices 701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. The terminal devices 701, 702, 703 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only).
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 705 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 701, 702, 703. The background management server may analyze and otherwise process the received data such as the item information query request, and feed back a processing result (for example, target push information, item information — just an example) to the terminal device.
It should be noted that the method for processing the business process provided by the embodiment of the present invention is generally executed by the server 705, and accordingly, the apparatus for processing the business process is generally disposed in the server 705. The method for processing the service flow provided by the embodiment of the present invention may also be executed by the terminal devices 701, 702, and 703, and accordingly, the apparatus for processing the service flow may be disposed in the terminal devices 701, 702, and 703.
It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 801.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer programs according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a first receiving module, a first sending module, a second receiving module, and a second sending module, where the names of the modules do not in some cases constitute a limitation on the modules themselves.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, implement the method of: receiving an event notification transmitted by a service flow, wherein the event notification carries an event type; matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic; receiving an execution result returned by the workflow framework, wherein the execution result carries an event type; matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic; or, the execution result is transmitted to the business process.
According to the technical scheme of the embodiment of the invention, because the technical means of matching the corresponding service logic according to the event type and sending the execution message to the workflow framework so as to enable the workflow framework to execute the service logic is adopted, the technical problem of strong coupling between the service flow and the control flow in the prior art is solved. The embodiment of the invention improves the real-time performance through the AOP and the event mechanism, realizes the decoupling with the business process with the maximum force, realizes the separation and the mapping of the business process control and the technical process through the definition of various events, and realizes the workflow circulation based on the event drive by adopting the technical means of kafka, ActiveMq or a database table and the like.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for processing a business process, comprising:
receiving an event notification transmitted by a service flow, wherein the event notification carries an event type;
matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic;
receiving an execution result returned by the workflow framework, wherein the execution result carries an event type;
matching a corresponding service logic according to the event type, and sending an execution message to a workflow frame to enable the workflow frame to execute the service logic; or, the execution result is transmitted to the business process.
2. The method of claim 1, wherein the event types include a process initiation event, an internal event of a process execution link, and a token event for driving a next step of a process flow.
3. The method of claim 2, wherein the process initiation event is triggered by an application portal of the business process; the internal event is triggered by a pre-event of the workflow framework; the token event is triggered by an automatic task invocation of the business logic.
4. The method of claim 3, wherein executing the business logic comprises:
creating a flow based on business logic corresponding to a flow starting event, wherein the flow comprises a plurality of nodes;
if the next node is an automatic node, triggering the business logic corresponding to the internal event;
if the next node is a manual intervention node, waiting for the completion of the execution of the manual node service logic;
automatically triggering a token event.
5. The method of claim 1, wherein sending an execution message to a workflow framework to cause the workflow framework to execute the business logic comprises:
based on the distributed message middleware, sending an execution message to a workflow framework to enable the workflow framework to execute the business logic.
6. The method of claim 1, wherein sending an execution message to a workflow framework to cause the workflow framework to execute the business logic comprises:
based on the message consumption component, an execution message is sent to the workflow framework to cause the workflow framework to execute the business logic.
7. The method of claim 1, wherein sending an execution message to a workflow framework to cause the workflow framework to execute the business logic comprises:
and inserting the event information into a database, and reading the event information in the database by using an automatic task server so as to enable the workflow framework to execute the business logic.
8. An apparatus for processing a business process, comprising:
the first receiving module is used for receiving an event notification transmitted by a service process, wherein the event notification carries an event type;
the first sending module is used for matching out a corresponding service logic according to the event type and sending an execution message to a workflow frame so as to enable the workflow frame to execute the service logic;
the second receiving module is used for receiving an execution result returned by the workflow framework, and the execution result carries an event type;
the second sending module is used for matching out corresponding service logic according to the event type and sending an execution message to a workflow frame so as to enable the workflow frame to execute the service logic; or, the execution result is transmitted to the business process.
9. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
the one or more programs, when executed by the one or more processors, implement the method of any of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010620833.3A CN111831461A (en) | 2020-07-01 | 2020-07-01 | Method and device for processing business process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010620833.3A CN111831461A (en) | 2020-07-01 | 2020-07-01 | Method and device for processing business process |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111831461A true CN111831461A (en) | 2020-10-27 |
Family
ID=72899976
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010620833.3A Pending CN111831461A (en) | 2020-07-01 | 2020-07-01 | Method and device for processing business process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111831461A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112884447A (en) * | 2021-03-12 | 2021-06-01 | 中国民用航空总局第二研究所 | Civil aviation airport data cooperation method and system |
| CN113435859A (en) * | 2021-07-12 | 2021-09-24 | 建信金融科技有限责任公司 | Letter processing method and device, electronic equipment and computer readable medium |
| CN113672205A (en) * | 2021-08-25 | 2021-11-19 | 广州方舟信息科技有限公司 | Workflow framework based on business event driving |
| CN117093384A (en) * | 2023-08-23 | 2023-11-21 | 北京志凌海纳科技有限公司 | Universal back-end reliable execution method, system, equipment and readable medium |
-
2020
- 2020-07-01 CN CN202010620833.3A patent/CN111831461A/en active Pending
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112884447A (en) * | 2021-03-12 | 2021-06-01 | 中国民用航空总局第二研究所 | Civil aviation airport data cooperation method and system |
| CN113435859A (en) * | 2021-07-12 | 2021-09-24 | 建信金融科技有限责任公司 | Letter processing method and device, electronic equipment and computer readable medium |
| CN113672205A (en) * | 2021-08-25 | 2021-11-19 | 广州方舟信息科技有限公司 | Workflow framework based on business event driving |
| CN113672205B (en) * | 2021-08-25 | 2022-06-03 | 广州方舟信息科技有限公司 | Workflow framework based on business event driving |
| CN117093384A (en) * | 2023-08-23 | 2023-11-21 | 北京志凌海纳科技有限公司 | Universal back-end reliable execution method, system, equipment and readable medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111831461A (en) | Method and device for processing business process | |
| CN112860451A (en) | Multi-tenant data processing method and device based on SaaS | |
| CN111427701A (en) | Workflow engine system and business processing method | |
| CN111198751A (en) | Service processing method and device | |
| CN109918191B (en) | Method and device for preventing frequency of service request | |
| CN111277639A (en) | Method and device for maintaining data consistency | |
| KR20220151585A (en) | Business data processing method, apparatus, electronic apparatus, storage media and computer program | |
| CN112612467A (en) | Method and device for processing micro front-end architecture based on qiankun | |
| CN110389976B (en) | Multi-interface data scheduling method and device | |
| CN112084042A (en) | Message processing method and device | |
| CN114500481A (en) | Service request processing method, system and device | |
| CN112819638A (en) | Transaction weight judging method, device, equipment and computer readable medium | |
| CN113760924A (en) | Distributed transaction processing method and device | |
| CN111881392A (en) | Page display method and device | |
| CN112948138A (en) | Method and device for processing message | |
| CN110764769A (en) | Method and device for processing user request | |
| CN113779122B (en) | Method and device for exporting data | |
| CN111125503A (en) | Method and apparatus for generating information | |
| CN114756227A (en) | Resource release processing method and device | |
| CN113296829A (en) | Method, device, equipment and computer readable medium for processing service | |
| CN113760487A (en) | Service processing method and device | |
| CN113448960A (en) | Method and device for importing form file | |
| CN113672671A (en) | Method and device for realizing data processing | |
| CN113572704A (en) | Information processing method, production end, consumption end and server | |
| CN112559001A (en) | Method and device for updating application |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220921 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right |