Event processing method and device, computer equipment and storage medium
By connecting nodes in the event processing process and utilizing standardized interfaces, the service demands of cross-system collaboration are solved, the configuration efficiency and scalability of the event processing process are improved, and the rapid service is quickly launched.
Patent Information
- Application Number
- CN202311842830.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-28
- Publication Date
- 2025-07-08
AI Technical Summary
In the prior art, the event processing process is a black box because the collaboration department is a black box, and the event model and state machine cannot detect the complete event processing link, resulting in inefficient configuration and poor cross-system coordination and scalability.
By connecting nodes in the event processing process to the event processing link, using standardized APIs and SPI interfaces, combining process driver engines and node definitions, it provides cross-level and cross-department service collaboration, and realizes flexible configuration and rapid launch of event processing processes.
It improves the configuration efficiency of event processing processes, enhances scalability, realizes rapid service launch, and reduces development costs and resource waste.
Smart Images
Figure CN120276880A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular, to an event processing method, apparatus, computer device, and storage medium. Background Art
[0002] In the related art, through an event model and a state machine, the collaborating departments on an event can be continuously updated and bound, and the event processing process can be configured in combination with the event state to implement the event processing process. However, since the states of each collaborating department are black boxes, the event model and the state machine cannot detect the complete event processing link of the collaborating departments, so the collaboration between the collaborating departments cannot be configured, reducing the configuration efficiency of the event processing process. Summary of the Invention
[0003] Embodiments of this application provide an event processing method, apparatus, computer device, and storage medium, which can improve the configuration efficiency of the event processing process and enhance scalability.
[0004] According to a first aspect of the embodiments of this application, an event processing method is provided, including:
[0005] Receiving a first input from a user for a first node in a configuration interface, where the first node is used to perform any behavior in the event processing process;
[0006] In response to the first input, according to the node attribute of the first node, connecting the first node to an event processing link corresponding to the event processing process to obtain an event processing flow chart, where the node attribute includes the node type of the first node and the state of the first node when performing the first behavior under the node type;
[0007] Performing an event processing operation according to the connection order of the nodes in the event processing flow chart.
[0008] According to a second aspect of the embodiments of this application, an event processing apparatus is provided, including:
[0009] A receiving module, configured to receive a first input from a user for a first node in a configuration interface, where the node is used to perform any behavior in the event processing process;
[0010] A processing module, configured to, in response to the first input, connect the first node to an event processing link corresponding to the event processing process according to the node attribute of the first node to obtain an event processing flow chart, where the node attribute is used to represent the node type of the first node and the state of the first node when performing the first behavior under the node type;
[0011] An execution module, configured to perform an event processing operation according to the connection order of the nodes in the event processing flow chart.
[0012] According to a third aspect of the embodiments of the present application, a computer device is provided, including: a memory and a processor;
[0013] The memory is used to store a computer program;
[0014] The processor is used to execute the computer program stored in the memory. When the computer program runs, the processor is caused to execute the steps of the event processing method as shown in the first aspect.
[0015] According to a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided. A program or instruction is stored on the computer-readable storage medium. When the program or instruction is executed by a computer device, the computer device is caused to execute the steps of the event processing method as shown in the first aspect.
[0016] According to a fifth aspect of the embodiments of the present application, a computer program product is provided, including a computer program. When the computer program is executed by a computer device, the computer device is caused to execute the steps of the event processing method as shown in the first aspect.
[0017] In the embodiments of the present application, for the event processing method, device, computer device, and storage medium, a first input of a user to a first node in a configuration interface is received. The first node is used to execute any behavior in the event processing process. According to the node attributes of the first node, the first node is concatenated into an event processing link corresponding to the event processing process to obtain an event processing flowchart. The node attributes include the node type of the first node and the state of the first node when executing the first behavior under the node type; and the operations of event processing are executed according to the connection order of the nodes in the event processing flowchart. In this way, through the atomic ability of the node to execute any one of multiple behaviors in the event processing process, each node of the event processing is concatenated into the event processing process flow to control it, effectively solving the service requirement of cross-system collaboration. Thus, the configuration efficiency of the event processing flow can be improved, the scalability can be enhanced, and then rapid service rapid online can be realized. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The present application can be better understood from the following description of the specific embodiments of the present application in conjunction with the accompanying drawings. Among them, the same or similar reference numerals represent the same or similar features.
[0019] Figure 1 is a schematic structural diagram of an event processing system showing an embodiment;
[0020] Figure 2 is a schematic interface diagram of an event processing system showing an embodiment;
[0021] Figure 3It is a flowchart showing a method for event processing according to an embodiment;
[0022] Figure 4 It is one of the interface diagrams showing a method for event processing according to an embodiment;
[0023] Figure 5 It is the second of the interface diagrams showing a method for event processing according to an embodiment;
[0024] Figure 6 It is the third of the interface diagrams showing a method for event processing according to an embodiment;
[0025] Figure 7 It is the fourth of the interface diagrams showing a method for event processing according to an embodiment;
[0026] Figure 8 It is a structural diagram showing an event processing device according to an embodiment;
[0027] Figure 9 It is a hardware structural diagram of a computer device according to an embodiment. Detailed Embodiments
[0028] The features and exemplary embodiments of various aspects of the present application will be described in detail below. For the purpose of making the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only configured to explain the present application and are not configured to limit the present application. For those skilled in the art, the present application can be implemented without some of these specific details. The following description of the embodiments is only provided to provide a better understanding of the present application by showing examples of the present application.
[0029] It should be noted that in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover a non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, elements defined by the statement "comprising..." do not exclude the presence of additional identical elements in the process, method, article or device comprising the elements.
[0030] During the implementation of the event handling pre - plan process in the integrated construction of the urban operation center, Independent Software Vendors (ISVs) were initially unable to develop the event management function independently. Moreover, the delivered cloud computing operating system (Platform as a Service, PaaS) was too abstract to start with. With the assistance of the server - side, if one wanted to build a complete event handling process, a large amount of time would be required for development work. Facing new demands from the user side, it was usually necessary to reconstruct the event handling process. Each reconstruction iteration cycle took a long time, and as the complexity of the pre - plan increased, each change cycle became longer, reducing the configuration efficiency of the event handling process. Here, a pre - plan refers to a processing process pre - set for a certain type of event, with coordination among single or multiple departments.
[0031] In related technologies, the event handling process can be implemented by means of an event model plus a state machine, by continuously updating and binding the collaborating departments on the event and combining the event status. However, since the event handling process and the collaborating departments are black boxes, the event model and the state machine cannot detect the complete event handling link of the collaborating departments. Therefore, event handling standardization cannot be achieved, the configuration efficiency of the event handling process is reduced, and the overall expandability of the event model and the state machine is affected. Additionally, although it is possible to implement the management of industry event handling methods based on the process - driving ability and the abstract behavior of defined nodes, since this method does not have a process - driving engine with industry attributes, ISVs need to enable all the capabilities on all process nodes to achieve the basic process - driving ability. Thus, resources are wasted, and data synchronization across any levels and departments cannot be achieved.
[0032] To solve the above problems, the embodiments of the present application provide an event processing method based on PaaS, which can solve the problems of high maintenance cost and difficult iteration of the service system caused by the variable event processing process in the unified management industry with the greatest flexibility. At the same time, the rich department routing strategy can support service collaboration across levels and departments in multiple scenarios. By integrating the standardized interface services (APIs) provided by software developers and the interface specifications defined by software developers for invocation, and the (SPI) definitions implemented by the access parties, and cooperating with the rapid orchestration of the main process and sub-processes, the service provider can quickly build its own event processing link. Different from the low scalability of the previous event processing method formed only by the event model and state machine, starting from the explicit event processing process plan, it not only precipitates the atomic service processing capabilities of the unified management industry, but also provides high scalability with standardized APIs; it can not only carry personalized processes in the event processing link in the main plan process (the personalized process can be implemented by nodes or sub-event processing links), but also solidify the event processing link with clear powers and responsibilities as a sub-process into data assets; through the scheduling application of the event processing system, connect other operating systems, combine functional packages to precipitate the capabilities of the management industry, and abstract an event plan, which serves as the connection of the event center and the precondition of matter matching, and completes the form of the main and sub-processes. In this way, there is both version management of the main plan and the ability to quickly launch new services without perception by continuously adding matter sub-processes; at the same time, as a collaborative product solution for the unified management industry, it realizes intelligent collaboration, which can not only improve the configuration efficiency of the event processing process but also reduce the development cost.
[0033] Based on this, the following will separately combine Figures 1 to 8 to illustrate the event processing method.
[0034] First, Figure 1 is a schematic structural diagram showing an event processing system according to an embodiment.
[0035] As Figure 1 shown, the event processing system 10 may include a server 101 and an external server 102. Exemplarily, the event processing system 10 may specifically be PaaS.
[0036] Among them, the server 101 may include at least one operating system, which can be used to define a configuration domain. The configuration domain can be used to provide functions such as matter process definition, multi-cross collaborative matter process definition, graph definition, line rule definition, node definition, time limit definition, dispatching department definition, dispatcher definition, service operation definition, special topic protocol definition, event source association relationship definition, pre-plan debugging, pre-plan implementation guidance, and node operation configuration. Here, each function can be configured as a node, and these nodes can be used to perform any behavior in the event processing process. And, in some embodiments, the server 101 may include the first operating system in the embodiments of the present application.
[0037] The external server 102 can be a third-party server for data transmission with the server 101. Here, in some instances, the external server 102 in the embodiments of the present application may include a second operating system.
[0038] Among them, the external server 102 may include a view domain, an operation domain, and a scheduling domain. Further, the view domain can be used to provide services such as work order list, work order details, work order handling process, task details, associated task query, etc. The operation domain can be used to provide services such as task marking, distribution withdrawal, direct rejection, custom task creation, order cancellation cancellation, suspension, transfer, custom task completion, direct case closure, recovery, extension application, event merging, evaluation, inventory handling process synchronization, assignment, receipt, etc. The scheduling domain can be used to provide services such as asynchronous start of pre-plan, asynchronous retry scheduling, expected reminder scheduling, asynchronous algorithm index synchronization, etc. Similarly, each function can be configured as a node, and these nodes can be used to perform any behavior in the event processing process.
[0039] Based on this, as Figure 2 shown, the server 101 can provide node definition services, such as defining the node name "matter department handling", defining the node attribute "waiting for distribution node", node operation configuration "whether the node can be skipped", executable operations "select function package" or "self-select node operation", function package service selection, etc. The user can browse the event processing flow chart 20 through the view domain provided by the external server 102, draw the event processing flow chart 20 through the configuration domain provided by the server 101 and the view domain provided by the external server 102, and dispatch relevant interfaces (such as API, SPI) through the scheduling domain provided by the external server 102, as well as the operation domain, and execute the operations of processing events according to the connection order of the nodes in the event processing flow chart 20 (such as start - carrier branch - specified department handling - carrier review - end).
[0040] In this way, based on the open-source process-driven engine, it is possible to complete the pre-plan definition from the configuration domain, and achieve a complete closed-loop of the pre-plan running state in the running domain and the view domain, providing the industry with collaborative capabilities with industry attributes. ISVs can directly use the rich configuration capabilities of the event handling pre-plan from the perspective of developers. By combining drawing with the line rules and node definitions with industry attributes in this solution, for functional department personnel, ISVs only need to integrate the relevant capabilities of the view domain and the running domain to achieve a closed-loop of event handling. In addition, the event handling system also carries some highlight capabilities with strong industry attributes (such as deferral and notification), and naturally integrates intelligent algorithm capabilities, providing a high-quality service experience with almost no cost for the SaaS layer.
[0041] Next, based on the above event handling system, combined with Figure 3 , the embodiments of the present application will elaborate on the event handling method in detail.
[0042] Figure 3 It is a flowchart showing an event handling method according to an embodiment.
[0043] As Figure 3 shown, the event handling method provided by the embodiments of the present application may include:
[0044] Step 310, receiving a first input from the user for a first node in the configuration interface, where the first node is used to perform any behavior in the event handling process; Step 320, in response to the first input, according to the node attributes of the first node, connecting the first node to an event handling link corresponding to the event handling process to obtain an event handling flowchart, where the node attributes include the node type of the first node and the state of the first node when performing the first behavior under the node type. Step 330, performing the operations of event handling according to the connection order of the nodes in the event handling flowchart.
[0045] In this way, through the atomic ability of the node to perform any one of multiple behaviors in the event handling process, each node of the event handling is connected to the event handling process flow to control it, effectively solving the service requirements for cross-system collaboration. In this way, it is possible to improve the configuration efficiency of the event handling process, enhance scalability, and thus achieve rapid service go-live.
[0046] The above steps will be elaborated in detail below, as specifically shown below.
[0047] First, regarding Step 310, the embodiments of the present application aggregate the atomic capabilities provided by different operating systems or servers into nodes, and these nodes can possess the minimum behaviors of the event handling process, that is, they are used to perform any one of multiple behaviors in the event handling process. For example, 'dispatching' a certain event to a certain department, and the department has 'accepted' it, etc.
[0048] Therefore, the embodiments of the present application provide a variety of atomic capabilities, saving a lot of research and development work, and can modularly access the required capabilities to enrich services.
[0049] Here, in the embodiment of the present application, the node types of nodes can be divided into the following four types: basic nodes, initial nodes, extended nodes and scene nodes.
[0050] Furthermore, basic nodes are nodes related to the iconic processing flow links of the management industry service attributes, such as waiting for allocation, waiting for disposal, waiting for review, etc. Initial nodes are nodes with basic functions provided to users, which facilitate users to configure parameters on the initial nodes to obtain extended nodes, which are user-defined nodes. Scenario nodes are nodes that wait for other nodes to synchronize in some specific scenarios, and can be synchronized with the event processing scenario.
[0051] Also, it should be noted that the event in the embodiment of the present application refers to the abstraction of something that happens in the real world; the matter is an abstract carrier used to standardize such information after the relevant operating system and departments have clarified the processing coordination mechanism for a certain type of event.
[0052] Next, step 320 is involved. In one or more possible embodiments of the present application, step 320 may include step 3201 and step 3202, as shown below.
[0053] Step 3201, in response to a first input, determining, according to a node attribute of a first node, a first behavior of the first node in executing an event processing process.
[0054] Exemplarily, if the node type of the first node in the embodiment of the present application is a basic node, the state of the first node when executing the first behavior under the node type can be waiting for distribution, distributing, or completing distribution. At this time, the first behavior can be data distribution.
[0055] Step 3202, according to the processing order of the first behavior in the event processing process, the first node is connected in series to the event processing link to obtain an event processing flow chart.
[0056] Exemplarily, if data distribution is the first step in the event processing process, the first node can be serially connected to the first step of the event processing link to obtain an event processing flow chart.
[0057] In one or more possible embodiments of the present application, step 320 may include steps 3203 to 3205 .
[0058] Step 3203: In response to the first input, obtain the first operating system corresponding to the first node according to the node attributes of the first node.
[0059] Exemplarily, if the node type of the first node in the embodiments of the present application is an expandable node, and the state when the first node executes the first behavior under the node type can be the data configuration phase, at this time, based on the foregoing content, the configuration end of the data configuration can be determined as the first operating system, or the node providing end that provides the first node can be determined as the first operating system.
[0060] Step 3204: Obtain the second node that performs data transmission with the first operating system according to the scheduling information of the first operating system.
[0061] Exemplarily, the scheduling information may include the node information controlled by the first operating system. In this way, the node corresponding to the node information can be obtained based on the node information, and at this time, the node can be determined as the second node.
[0062] Step 3205: Connect the first node and the second node in series to the event processing link corresponding to the event processing process to obtain the event processing flow chart.
[0063] Based on this, step 3203 may specifically include steps 32031 to 32033.
[0064] Step 32031: In response to the first input, display at least two operating systems corresponding to the first node according to the node attributes of the first node.
[0065] Exemplarily, if the node type of the first node in the embodiments of the present application is an expandable node, and the state when the first node executes the first behavior under the node type can be the data configuration phase, at this time, based on the foregoing content, the configuration end of the data configuration can be determined as the first operating system, or the node providing end that provides the first node can be determined as the first operating system.
[0066] Step 32032: In the case of receiving the user's selection of the second operating system from at least two operating systems, obtain at least two nodes that perform data transfer with the second operating system according to the scheduling information of the second operating system.
[0067] Exemplarily, the scheduling information may include the interface information for the first operating system to transfer data with at least one other operating system. These interface information can be used to indicate that these operating systems have established connections with the first operating system. In this way, the nodes managed by these other operating systems can be determined as the second nodes.
[0068] Step 32033: Determine the node selected by the user from at least two nodes as the second node.
[0069] Here, it can be combined with Figure 4 to elaborate on steps 32031 to 32033 in detail.
[0070] Exemplarily, as Figure 4 shown, at least two nodes in the embodiments of the present application may include a "carrier branch - basic node" and a "carrier branch - initial node". If it is the commonly used node after the first node, i.e., the "carrier branch - basic node", the user can determine the "carrier branch - basic node" as the second node among the at least two nodes.
[0071] Based on this, for any one of the above two possible embodiments, the first node can be used to execute the first action in the event processing process, the second node can be used to execute the second action in the event processing process, and step 3205 may specifically include step 32051 and step 32052.
[0072] Step 32051, arrange the order of the first node and the second node according to the sequence of the first action and the second action in the event processing process to obtain the node arrangement order;
[0073] Step 32052, connect the first node and the second node to the event processing link according to the node arrangement order to obtain the event processing flow chart.
[0074] Exemplarily, still referring to Figure 4 , according to the node attribute of the first node, such as a basic node, display at least one candidate operating system associated with the first node attribute, such as specified by the previous node, i.e., "carrier branch", the department passed down by the use of the dispatching node, or a certain department available in the current event processing system, etc. Based on this, after determining the "matter partial processing" node and the operating system, an event processing link can be constructed based on at least two nodes, such as "carrier branch" - "matter partial disposal" and the data flow direction from "carrier branch" to "matter partial disposal", and an event processing flow chart 40 can be constructed and displayed based on another event processing link, such as "start" - "carrier branch" - "specified partial disposal" - "carrier review" - "end" for display to the user.
[0075] Then, regarding step 330, the node attributes in the embodiments of the present application can affect the attributes of the operations to be performed hereinafter, that is, when it is an extended node and involves data of an external server, different interfaces may be called to perform corresponding operations.
[0076] Based on this, in one or more possible embodiments, the scheduling information includes first interface information, and the first interface corresponding to the first interface information is used to transmit data between the first node and the second node. In the event processing process, the first action is executed before the second action. Specifically, step 330 may include:
[0077] When the first action result of the first node executing the first action is obtained, through the first interface, the first action result of the first node executing the first action is transmitted to the second node.
[0078] Exemplarily, both the first node and the second node may be nodes within the first operating system. Based on this, as Figure 5 shown in (1) below, if all the nodes in the event processing flow chart are the operating systems or departments within the server itself and there is no need to perform data interaction with the operating system of the external server, the operating systems corresponding to the nodes can be scheduled according to the connection order of the nodes through the first interface API1 corresponding to the first interface information to perform the operation of processing events in the connection order of the target nodes in the event processing link in the event processing flow chart. For example, "Start" → "Task to be judged" → "Not accepted" → "End".
[0079] In another or more possible embodiments, the scheduling information includes second interface information, and the second interface corresponding to the second interface information is used to transmit data between the first operating system and the second operating system connected to the first operating system. In the event processing process, the first action is executed before the second action. Specifically, step 330 may include:
[0080] When the first operating system obtains the first action result of the first node executing the first action, through the second interface, the first action result of the first node executing the first action is transmitted to the second operating system;
[0081] Through the second operating system, the first action result is transmitted to the second node;
[0082] Wherein, the first operating system is the system that manages and executes the event processing process; the second operating system is at least one of the following: the operating systems corresponding to the first node and the second node, the operating system designated by the dispatching node in the first operating system.
[0083] Exemplarily, the scheduling information includes second interface information provided by the server, and the second interface information is used for data exchange between the server and the external server. The external server includes at least one external operating system, as Figure 5As shown in (2), when the operating systems of the nodes in the event processing flow chart can include both the operating systems or departments within the server itself and the operating systems or departments of the external connected servers, the operating systems corresponding to the nodes can be scheduled according to the connection order of the nodes through the interface SPI corresponding to the second interface information, so as to realize the data interaction between the server and the external connected server, and then execute the operation of processing events according to the connection order of the target nodes in the event processing link of the event processing flow chart. For example, if the general disposal function package needs to be executed by an external processor to automatically reprocess when the review task fails, then, "Start" → "General Disposal Function Package" → "Pending Review Task" → "Automatically Reprocess when Review Fails" → Call the "General Disposal Function Package" through SPI to reprocess.
[0084] Here, based on the function package method combined with process configuration, the richness of industry PaaS is realized.
[0085] Thus, in addition to the atomic capabilities, the embodiments of the present application can also connect different servers or different operating systems or departments of the same server to the process through different interfaces such as API and SPI for control. And, data of external operating systems and departments can be obtained by calling external connected servers through SPI nodes, which improves the expandability of the event processing method.
[0086] In this way, through the atomic capabilities of the nodes for performing any one of multiple behaviors in the event processing process, the platforms corresponding to each node of the event processing are connected to the event processing process for control, effectively solving the service requirements for cross-system collaboration. And, through the event processing process configuration method of explicit process plans in the present application, users can intuitively view the event processing link, so as to facilitate users to adjust the processing link. There is no need to re-code according to the adjusted event processing link, only the connection relationship of each node needs to be adjusted, or nodes are added to the event processing link to add item sub-processes. In this way, the configuration efficiency of the event processing process can be improved, the expandability can be enhanced, and then rapid service can be quickly launched.
[0087] And, before step 330, the node type of the first node is the initial node, and the status is waiting for distribution, waiting for disposal or waiting for review. Based on this, the event processing method can further include:
[0088] Receiving a sixth input for configuring the initial node;
[0089] In response to the sixth input, adjusting the node type of the first node from the basic node to the extended node; and adjusting the status to distribution, disposal or review.
[0090] Exemplarily, based on the content in the foregoing step 310, it can be known that there are various node attributes in the embodiments of the present application. Thus, in one example, the node attributes of the basic nodes can be determined according to the processing status of each process stage in the process of processing the event, such as waiting for sorting, waiting for handling, or waiting for review. In this way, the obtained nodes are nodes such as waiting for sorting, waiting for handling, or waiting for review. Thus, after the initial nodes are configured, their node types and statuses will also change. Thus, the node attributes of the nodes will be adjusted based on this method.
[0091] In another or multiple possible embodiments, the node includes an initial node and an extended node. Based on this, before step 320, the event processing method may further include:
[0092] Receiving a third input for configuring the initial node;
[0093] In response to the third input, determining the configured initial node as an extended node; and determining the configuration end of the configured initial node as the operating system of the extended node, and determining the scheduling information of the configuration end as the configuration end of the extended node.
[0094] At this time, in this embodiment, the operating system is the operating system indicated by the event source of the event.
[0095] Exemplarily, the initial node is a node with basic functions provided for the user, which facilitates the user to configure parameters on the initial node to obtain an extended node, and the extended node is the node customized by the user.
[0096] In addition, after step 330, nodes can be added to the event processing flow chart. Based on this, the event processing method may further include steps 3401 to 3404.
[0097] Step 3401, displaying the event processing flow chart and candidate nodes, where the candidate nodes are used to perform any behavior in the process of event processing;
[0098] Step 3402, receiving a second input from the user to select a third node from the candidate nodes;
[0099] Step 3403, in response to the second input, obtaining the third behavior executed by the third node in the process of event processing;
[0100] Step 3404, connecting the third node to the event processing flow chart in the order of the third behavior in the process of event processing, and updating the event processing flow chart.
[0101] Exemplarily, such as Figure 6As shown, when adding a new node to the event processing flowchart, the initial event processing flowchart can be updated according to the node type of the new node and the state when the node performs an action under the node type. Among them, in this example, a new node is added to the event processing flowchart 60. Based on this, if, after receiving the user's input, a "carrier review" node is added after "matter department handling", then based on the user's input of adding a new node to the initial event processing flowchart, the new node such as "carrier review" can be reconfigured, and the configured event processing flowchart 61 can be displayed. That is, referring to Figure 6 , after "matter department handling", if "carrier review" is added, then the connection information between the operating systems of "matter department handling" and "carrier review" can be updated, and the scheduling information from the operating system of "matter department handling" → "end" can be updated to the operating system of "matter department handling" → the operating system of "carrier review" → "end".
[0102] Here, it should be noted that in addition to updating the attributes of the new node, the scheduling information of the operating system corresponding to the new node can also be updated.
[0103] Similarly, the embodiment of the present application also provides for deleting a node in the event processing flowchart 60, and the deleted event processing flowchart can also be updated again. Based on this, after step 330, a node can be deleted from the event processing flowchart. Based on this, the event processing method may further include steps 3501 to 3504.
[0104] Step 3501, display the event processing flowchart;
[0105] Step 3502, receive a fourth input from the user to remove a first node from the event processing flowchart;
[0106] Step 3503, in response to the fourth input, obtain a target node connected to the first node from the event processing flowchart;
[0107] Step 3504, when the target node is one and the target node is a node upstream of the first node, use the execution result of the fourth action in the event processing process executed by the target node as the execution result output by the event processing link where the first node is located.
[0108] Exemplarily, still referring to Figure 6 61 in, if "carrier review" is deleted after "matter department handling", then the connection information between the operating systems of "matter department handling" and "carrier review" can be updated, and the scheduling information can be updated from the operating system of "matter department handling" → the operating system of "carrier review" → "end" to the operating system of "matter department handling" → "end".
[0109] Therefore, the embodiments of the present application can design explicit process plans, enabling users to intuitively feel the event processing link. Moreover, through continuous iteration and upgrade, the plan gradually matures and can provide derivative value as a data asset for customers. For the adjustment of the processing link, there is no need for hard coding. Only by adjusting the line rules or creating a sub-process for a new event type can rapid service go live be achieved.
[0110] Here, it should be noted that the update in the embodiments of the present application refers to updating the connection order of nodes in the event processing link, performing operations on the nodes in the event processing link, and the operating system information and scheduling information of every two connected nodes.
[0111] Further, after step 3503, the event processing method may further include step 3505 and step 3506.
[0112] Step 3505, in the case where the target node is at least two target nodes, respectively obtain a first target node upstream of the first node and a second target node downstream of the second node from the at least two target nodes;
[0113] Step 3506, transmit the execution result of the fifth action in the event processing process executed by the first target node to the second target node.
[0114] Exemplarily, with reference to Figure 4 , the first node in the embodiments of the present application may be designated partial disposal. Then, the first target node may be carrier branch line, and the second target node may be carrier review. At this time, if the first node is removed, the execution result output by the carrier branch line node will be input to the carrier review node.
[0115] Or, after step 330, nodes can be replaced in the event processing flow chart. Based on this, the event processing method may further include step 3601 to step 3604.
[0116] Step 3601, display the event processing flow chart and the fourth node, where the fourth node is used to execute the first action in the event processing process;
[0117] Step 3602, receive the fifth input from the user to replace the first node with the fourth node;
[0118] Step 3603, in response to the fifth input, transmit the execution result of the node upstream of the first node to the fourth node;
[0119] Step 3604, transmit the execution result of the fourth node executing the first action to the node downstream of the first node.
[0120] Exemplarily, as Figure 7As shown, to reduce the user's input, the event processing flowchart 50 can be displayed to the user according to the user's historical behavior information, preset templates, or the time processing flowchart generated last time. The user can make changes to the event processing flowchart 50, such as adjusting the positions of the nodes "Disposal by Designated Department" and "Disposal by Matter Department". At this time, based on the input of the user adjusting the positions of the nodes in the initial event processing flowchart, the adjusted nodes such as "Disposal by Matter Department" (or "Disposal by Designated Department") can be reconfigured as Figure 2 shown, so that the configured event processing flowchart 51 can be displayed.
[0121] Here, it should be noted that for the operating system corresponding to the adjusted node in this example, it can be recommended to the user based on the adjusted event processing link or automatically selected by the user, which is not limited here.
[0122] Thus, for multiple departments, multi-dimensional calculation strategies are provided, integrating event information and process operation context into the transfer rules, improving the process orchestration ability, providing a way based on the main plan process and matter process, decoupling the collaborative end and handling end of the overall management industry handling service, and providing reliability for the incremental iteration of the service.
[0123] Here, it should be noted that based on the above three situations, namely addition, deletion, or replacement, based on this, after step 3204, the event processing method can further include:
[0124] Taking the event processing flowchart as the initial event processing flowchart for the next time.
[0125] In this way, the database of the initial event processing flowchart can be updated to provide a graphical basis for the next configuration.
[0126] In summary, the event processing method provided by the embodiments of this application can complete scenario definition through the configuration domain, and implement scenario operation through the operation domain and the view domain. An ISV can directly use the rich configuration capabilities of the event handling scenario from the perspective of a developer. By combining drawing with the line rules and node definitions with industry attributes in this solution, for personnel in functional departments, the ISV only needs to integrate the relevant capabilities of the view domain and the operation domain to achieve a closed-loop event processing. Moreover, through the atomic capability of the node to execute any one of the multiple behaviors in the event processing process, each node of the event processing and the corresponding operating system are connected to the event processing process flow to control it, effectively solving the service requirement of cross-system collaboration. In addition, through the event processing process configuration method of the explicit process scenario in this application, users can intuitively view the event processing link, so as to facilitate users to adjust the processing link. There is no need to re-code according to the adjusted event processing link, but only need to adjust the connection relationship of each node, or add nodes in the event processing link to add sub-processes of matters. In this way, the configuration efficiency of the event processing process can be improved, the scalability can be enhanced, and then rapid service can be quickly launched.
[0127] It should be clear that this application is not limited to the specific configurations and processes described in the above embodiments and shown in the figures. For the convenience and brevity of description, the detailed description of known methods is omitted here, and the specific working processes of the systems, modules, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be repeated here.
[0128] Based on the same inventive concept, the embodiments of this application provide an event processing device corresponding to the event processing method described above. Specifically, it will be described in detail in combination with Figure 8 for detailed description.
[0129] Figure 8 is a schematic structural diagram showing an event processing device according to an embodiment.
[0130] As Figure 8 shown, the event processing device 80 may specifically include:
[0131] A receiving module 801, configured to receive a first input of a user to a first node in a configuration interface, where the node is used to execute any one of the behaviors in the event processing process;
[0132] A processing module 802, configured to, in response to the first input, connect the first node to an event processing link corresponding to the event processing process according to the node attribute of the first node to obtain an event processing flow chart, where the node attribute is used to characterize the node type of the first node and the state of the first node when executing the first behavior under the node type;
[0133] An execution module 803, configured to perform event processing operations in the connection order of nodes in the event processing flow chart.
[0134] Based on this, the event processing device 80 provided in the embodiments of the present application will be described in detail below.
[0135] In one or more possible embodiments, the processing module 802 in the embodiments of the present application may specifically be configured to, in response to a first input, determine a first behavior for executing an event processing process according to the node attribute of a first node.
[0136] Connect the first node to an event processing link in the processing order of the first behavior in the event processing process to obtain an event processing flow chart.
[0137] In another or more possible embodiments, the processing module 802 in the embodiments of the present application may specifically be configured to, in response to a first input, obtain a first operating system corresponding to the first node according to the node attribute of the first node.
[0138] Obtain a second node for data transmission with the first operating system according to the scheduling information of the first operating system.
[0139] Connect the first node and the second node to an event processing link corresponding to the event processing process to obtain an event processing flow chart.
[0140] In still another or more possible embodiments, the event processing device 80 provided in the embodiments of the present application may further include a first display module; wherein,
[0141] The first display module is configured to, in response to a first input, display at least two operating systems corresponding to the first node according to the node attribute of the first node.
[0142] The processing module 802 in the embodiments of the present application may further be configured to, when receiving a user's selection of a second operating system from at least two operating systems, obtain at least two nodes for data transfer with the second operating system according to the scheduling information of the second operating system; and determine the node selected by the user from the at least two nodes as the second node.
[0143] In yet another or more possible embodiments, the processing module 802 in the embodiments of the present application may specifically be configured to, when the first node is used to execute a first behavior in the event processing process and the second node is used to execute a second behavior in the event processing process, arrange the order of the first node and the second node according to the sequence of the first behavior and the second behavior in the event processing process to obtain a node arrangement order.
[0144] Connect the first node and the second node to the event processing link in the order of node arrangement to obtain an event processing flow chart.
[0145] In yet another or multiple possible embodiments, the event processing apparatus 80 provided in the embodiments of the present application may further include a first transmission module; wherein,
[0146] The first transmission module is configured to, when the scheduling information includes first interface information, and the first interface corresponding to the first interface information is used to transmit data between the first node and the second node, and in the event processing process, a first action is executed before a second action, and when the first action result of the first node executing the first action is obtained, transmit the first action result of the first node executing the first action to the second node through the first interface.
[0147] In yet another or multiple possible embodiments, the event processing apparatus 80 provided in the embodiments of the present application may further include a second transmission module; wherein,
[0148] The second transmission module is configured to, when the scheduling information includes second interface information, and the second interface corresponding to the second interface information is used to transmit data between the first operating system and the second operating system connected to the first operating system, and in the event processing process, a first action is executed before a second action, and when the first operating system obtains the first action result of the first node executing the first action, transmit the first action result of the first node executing the first action to the second operating system through the second interface;
[0149] Transmit the first action result to the second node through the second operating system;
[0150] Wherein, the first operating system is a system for managing the execution of the event processing process; the second operating system is at least one of the following: the operating systems corresponding to the first node and the second node, and the operating system designated by the dispatching node in the first operating system.
[0151] In yet another or multiple possible embodiments, the event processing apparatus 80 provided in the embodiments of the present application may further include a second display module; wherein,
[0152] The second display module is configured to display an event processing flow chart and candidate nodes, and the candidate nodes are used to execute any action in the event processing process;
[0153] The receiving module 801 may further be configured to receive a second input from the user to select a third node from the candidate nodes;
[0154] The processing module 802 can also be used to obtain the third behavior executed by the third node during the event processing in response to the second input; and, connect the third node to the event processing flow chart in the order of the third behavior during the event processing, and update the event processing flow chart.
[0155] In yet another or multiple possible embodiments, the event processing device 80 provided by the embodiments of the present application may further include a third display module; wherein,
[0156] The third display module is used to display the event processing flow chart;
[0157] The receiving module 801 can also be used to receive a fourth input from the user to remove the first node from the event processing flow chart;
[0158] The processing module 802 can also be used to, in response to the fourth input, obtain the target node connected to the first node from the event processing flow chart; and, in the case where the target node is one and the target node is a node upstream of the first node, use the execution result of the fourth behavior executed by the target node during the event processing as the execution result output by the event processing link where the first node is located.
[0159] In yet another or multiple possible embodiments, the event processing device 80 provided by the embodiments of the present application may further include an acquisition module and a third transmission module; wherein,
[0160] The acquisition module is used to, in the case where the target node is at least two target nodes, respectively obtain the first target node upstream of the first node and the second target node downstream of the second node from the at least two target nodes;
[0161] The third transmission module is used to transmit the execution result of the fifth behavior executed by the first target node during the event processing to the second target node.
[0162] In yet another or multiple possible embodiments, the event processing device 80 provided by the embodiments of the present application may further include a fourth display module and a fourth transmission module; wherein,
[0163] The fourth display module is used to display the event processing flow chart and the fourth node, and the fourth node is used to execute the first behavior during the event processing;
[0164] The receiving module 801 can also be used to receive a fifth input from the user to replace the first node with the fourth node;
[0165] The fourth transmission module is used to, in response to the fifth input, transmit the execution result of the node upstream of the first node to the fourth node; and transmit the execution result of the fourth node executing the first behavior to the node downstream of the first node.
[0166] In yet another or multiple possible embodiments, the event processing device 80 provided by the embodiments of the present application may further include an adjustment module; wherein,
[0167] The receiving module 801 may also be used to receive a sixth input for configuring the initial node when the node type of the first node is an initial node and the status is waiting for distribution, waiting for disposal, or waiting for review.
[0168] The adjustment module is used to, in response to the sixth input, adjust the node type of the first node from a basic node to an extended node; and adjust the status to distribution, disposal, or review.
[0169] Thus, in the embodiments of the present application, the event processing device can connect each node of the event processing and the platform corresponding to the node to the event processing process flow through the atomic ability of the node to perform any one of multiple behaviors in the event processing process to control it, effectively solving the service requirements for cross-system collaboration. Moreover, through the event processing process configuration method of explicit process plans in the present application, users can intuitively view the event processing flow chart, so as to facilitate users to adjust the processing link in the event processing flow chart. There is no need to re-code according to the adjusted event processing link, and only the connection relationship of each node needs to be adjusted, or new nodes are added to the event processing link to add item sub-processes. In this way, the configuration efficiency of the event processing process can be improved, the scalability can be enhanced, and rapid service can be launched quickly.
[0170] Figure 9 It is a schematic diagram of the hardware structure of a computer device according to an embodiment.
[0171] As Figure 9 shown, the computer device 900 includes an input device 901, an input interface 902, a processor 903, a memory 904, an output interface 905, and an output device 906.
[0172] The input interface 902, the processor 903, the memory 904, and the output interface 905 are connected to each other through a bus 910. The input device 901 and the output device 906 are respectively connected to the bus 910 through the input interface 902 and the output interface 905, and then connected to other components of the computer device 900. Specifically, the input device 901 receives external input information and transmits the input information to the processor 903 through the input interface 902; the processor 903 processes the input information based on computer-executable instructions stored in the memory 904 to generate output information, stores the output information temporarily or permanently in the memory 904, and then transmits the output information to the output device 906 through the output interface 905; the output device 906 outputs the output information to the outside of the computer device 900 for user use.
[0173] In one embodiment, Figure 9 The computer device 900 shown can be implemented as an event processing device or an object matching device. The event processing device may include: a memory configured to store programs; a processor configured to run the programs stored in the memory to execute the event processing method described in the above embodiments. The object matching device may include: a memory configured to store programs; a processor configured to run the programs stored in the memory to execute the object matching method described in the above embodiments.
[0174] According to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer-readable storage medium. For example, an embodiment of the present application includes a computer-readable storage medium that stores programs or instructions on the computer-readable storage medium. When the programs or instructions are executed by a computer device, the computer device is caused to execute the steps of the above event processing method.
[0175] According to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product that includes a computer program tangibly embodied on a machine-readable medium. The computer program includes program code for performing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network and / or installed from a removable storage medium.
[0176] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When they run on a computer, the computer is caused to execute the methods described in the above respective embodiments. When loading and executing the computer program instructions on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available medium can be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, solid state drive), etc.
[0177] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative effort.
[0178] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. An event processing method, comprising: Receiving a first input from a user for a first node in a configuration interface, where the first node is used to perform any behavior in an event processing process; In response to the first input, according to the node attributes of the first node, connecting the first node in series to an event processing link corresponding to the event processing process to obtain an event processing flow chart, where the node attributes include the node type of the first node and the state of the first node when performing the first behavior under the node type; Performing an event processing operation according to the connection order of the nodes in the event processing flow chart.
2. The method according to claim 1, wherein The step of, in response to the first input, according to the node attributes of the first node, connecting the first node in series to an event processing link corresponding to the event processing process to obtain an event processing flow chart, includes: In response to the first input, according to the node attributes of the first node, determining that the first node is used to perform a first behavior in the event processing process; Connecting the first node in series to the event processing link according to the processing order of the first behavior in the event processing process to obtain an event processing flow chart.
3. The method according to claim 1, wherein The step of, in response to the first input, according to the node attributes of the first node, connecting the first node in series to an event processing link corresponding to the event processing process to obtain an event processing flow chart, includes: In response to the first input, according to the node attributes of the first node, obtaining a first operating system corresponding to the first node; According to the scheduling information of the first operating system, obtaining a second node for data transmission with the first operating system; Connecting the first node and the second node in series to an event processing link corresponding to the event processing process to obtain an event processing flow chart.
4. The method according to claim 3, wherein, The step of, in response to the first input, according to the node attributes of the first node, obtaining a second node, includes: In response to the first input, according to the node attributes of the first node, displaying at least two operating systems corresponding to the first node; In the case of receiving a user's selection of a second operating system from the at least two operating systems, obtaining at least two nodes for data transfer with the second operating system according to the scheduling information of the second operating system; Determining the node selected by the user from the at least two nodes as the second node.
5. The method according to claim 3 or 4, wherein, The first node is used to perform a first behavior in the event processing process, and the second node is used to perform a second behavior in the event processing process; The step of connecting the first node and the second node in series to an event processing link corresponding to the event processing process to obtain an event processing flow chart, includes: Arranging the order of the first node and the second node according to the sequence of the first behavior and the second behavior in the event processing process to obtain a node arrangement order; Connecting the first node and the second node in series to the event processing link according to the node arrangement order to obtain an event processing flow chart.
6. The method according to claim 5, wherein The scheduling information includes first interface information, and a first interface corresponding to the first interface information is used to transmit data between the first node and the second node, and the first action is performed before the second action during the event processing; The operation of performing event processing according to the connection sequence of nodes in the event processing flowchart includes: When the first action result of the first node performing the first action is obtained, the first action result of the first node performing the first action is transmitted to the second node through the first interface.
7. The method according to claim 5, wherein, The scheduling information includes second interface information, and a second interface corresponding to the second interface information is used to transmit data between the first operating system and a second operating system connected to the first operating system, and the first action is performed before the second action during the event processing; The operation of performing event processing according to the connection sequence of nodes in the event processing flowchart includes: When the first operating system obtains the first action result of the first node performing the first action, the first action result of the first node performing the first action is transmitted to the second operating system through the second interface; The first action result is transmitted to the second node through the second operating system; Wherein, the first operating system is a system for managing the execution of the event processing process; the second operating system is at least one of the following: an operating system corresponding to the first node and the second node, an operating system designated by a dispatching node in the first operating system.
8. The method according to claim 1, wherein, The method further includes: Displaying the event processing flowchart and candidate nodes, where the candidate nodes are used to perform any action during the event processing process; Receiving a second input from the user to select a third node from the candidate nodes; In response to the second input, obtaining a third action performed by the third node during the event processing process; According to the sequence of the third action in the event processing process, connecting the third node to the event processing flowchart and updating the event processing flowchart.
9. The method according to claim 1, wherein, The method further includes: Displaying the event processing flowchart; Receiving a fourth input from the user to remove the first node from the event processing flowchart; In response to the fourth input, obtaining a target node connected to the first node from the event processing flowchart; When the target node is one and the target node is a node upstream of the first node, using the execution result of the fourth action performed by the target node during the event processing process as the execution result output by the event processing link where the first node is located.
10. The method according to claim 9, wherein, After obtaining the target node connected to the first node from the event processing flowchart, the method further includes: When the target node is at least two target nodes, respectively obtaining a first target node upstream of the first node and a second target node downstream of the second node from the at least two target nodes; Transmit the execution result of the fifth action in the event handling process executed by the first target node to the second target node.
11. The method according to claim 1, wherein, The method further includes: Display the event handling flow chart and the fourth node, where the fourth node is used to execute the first action in the event handling process; Receive a fifth input from the user to replace the first node with the fourth node; In response to the fifth input, transmit the execution result of the node upstream of the first node to the fourth node; Transmit the execution result of the fourth node executing the first action to the node downstream of the first node.
12. The method according to claim 1, wherein, The node type of the first node is an initial node, and the status is waiting for distribution, waiting for disposal, or waiting for review; before performing the operation of executing event handling according to the connection order of the nodes in the event handling flow chart, the method further includes: Receive a sixth input for configuring the initial node; In response to the sixth input, adjust the node type of the first node from the basic node to an extended node; and adjust the status to distribution, disposal, or review.
13. An event handling device, comprising: A receiving module, configured to receive a first input from the user for a first node in a configuration interface, where the node is used to execute any action in the event handling process; A processing module, configured to, in response to the first input, connect the first node to an event handling link corresponding to the event handling process according to the node attributes of the first node, to obtain an event handling flow chart, where the node attributes are used to characterize the node type of the first node and the status of the first node when executing the first action under the node type; An execution module, configured to perform the operation of event handling according to the connection order of the nodes in the event handling flow chart.
14. A computer device, comprising: A memory and a processor, The memory is configured to store a computer program; The processor is configured to execute the computer program stored in the memory, and when the computer program runs, the processor is caused to execute the steps of the event handling method according to any one of claims 1 to 12.
15. A computer-readable storage medium, where a program or instruction is stored on the computer-readable storage medium, and when the program or instruction is executed by a computer device, the computer device is caused to execute the steps of the event handling method according to any one of claims 1 to 12.