A Stack-Based Event Single Handling Method and Apparatus

Abstract

This application provides a stack-based event order processing method and apparatus. The method includes: inserting a new event order processing flow into a flow table and inserting a new element into a stack element table; when the flow status of the new event order processing flow is "issued," issuing the event order processing task represented by the new element to the processing organization corresponding to the organization number according to the position of the new element in the stack element table and the organization number of the event order processing task represented by the new element; when the flow status of the new event order processing flow is "feedback," receiving feedback from the event order processing task represented by the new element in the stack element table in reverse order of the issuance order of the event order processing task represented by the new element. This method avoids the problems of increased complexity and maintenance difficulty in the backend system due to the introduction of third-party workflow tools, and the inability to adapt and use third-party workflow tools.

Description

Technical Field

[0001] This application relates to event single-processing technology, and more particularly to an event single-processing method and apparatus based on a stack implementation. Background Technology

[0002] In enterprise management, a large number of incident tickets are generated daily. The people who create these tickets are usually not the frontline staff resolving the issues. For example, in bank management, the back-end system generates incident tickets based on customer complaints, while the front-end staff are responsible for resolving these complaints. Therefore, after creating an incident ticket, a workflow needs to be implemented to process it, cascading the ticket down to the front-end staff. Sometimes, after processing, the incident ticket needs to be fed back to the back-end system along the same path, where the back-end system records the event processing status.

[0003] Several workflow tools have been developed in the prior art, such as Activiti and Flowable BPMN software, which provide general methods for handling event tickets. However, if these workflow tools are directly introduced into the backend system, it may increase the complexity of the backend system, increase the difficulty of maintaining the backend system, and the workflow tools may also become unusable during use because they cannot adapt to specific event ticket handling scenarios.

[0004] Therefore, how to create a workflow that can process event tickets based on the backend system remains a problem that needs to be solved. Summary of the Invention

[0005] This application provides a stack-based event order processing method and apparatus, which is used to create a workflow that can process event orders based on a backend system, avoiding the problems of increased complexity and maintenance difficulty of the backend system due to the introduction of third-party workflow tools, and the inability of third-party workflow tools to be adapted and used.

[0006] On one hand, this application provides a stack-based event order processing method applied to a backend server. The backend server has a process table and a stack element table. The process table records the event order processing flow, and each event order processing flow records the processing flow of at least one event order processing task. Each event order processing flow also has a process state. An element in the stack element table represents an event order processing task, and each event order processing task has a corresponding processing mechanism. When an element is only at the top of the stack, the event order processing task corresponding to that element is a task that can be sent down or feedback. The method includes:

[0007] When the process status of a new event order processing flow is "issued", the event order processing task represented by each element is issued to the corresponding processing agency in sequence according to the position of the elements in the stack element table.

[0008] When the process status of the new event order processing flow is feedback, the feedback order of the event order processing tasks is the reverse of the order in which the event order processing tasks are issued in the stack element table, and the feedback of each event order processing task is received.

[0009] Optionally, when the process status of the new event single processing flow is "issued", the method further includes:

[0010] Before inserting a new element into the stack element table, update the position of the existing elements in the stack element table.

[0011] When the new element is inserted into the stack element table, the position of the new element in the stack element table is updated to the top of the stack.

[0012] Optionally, updating the position of an existing element in the stack element table includes:

[0013] When the number of elements in the stack element table is equal to 1, update the position of one element in the stack element table to the bottom of the stack;

[0014] When the number of elements in the stack element table is greater than 1, update the position of the element in the stack element table to be in the stack.

[0015] Optionally, the method further includes:

[0016] When the event task corresponding to the element at the top of the stack element table is sent to the corresponding processing mechanism, the position of the element in the stack element table is updated to the top of the stack, and the position of the element at the bottom of the stack element table is updated to the middle of the stack.

[0017] Optionally, the backend server also includes a historical process table for storing user operation records, and the method further includes:

[0018] The user operation records in the new event order processing flow are stored, and the user operation records include the operator of the event order processing task and the corresponding operation.

[0019] Optional, also includes:

[0020] The response process creation operation creates the current event handling process and the process state of the current event handling process;

[0021] When a process status update operation is detected, the process status of the current event handling process is updated according to the process status update operation.

[0022] On the other hand, a stack-based event processing device is applied to a backend server. The backend server has a process table and a stack element table. The process table records the event processing flow, and each event processing flow records the processing flow of at least one event processing task. Each event processing flow also has a flow state. An element in the stack element table represents an event processing task, and each event processing task has a corresponding processing mechanism. When an element is only at the top of the stack, the event processing task corresponding to that element is a task capable of being sent down or feedback. The device includes:

[0023] The dispatch module is used to dispatch the event order processing task represented by each element to the corresponding processing agency in the order of the position of the elements in the stack element table when the process status of the new event order processing flow is dispatch.

[0024] The feedback module is used to receive feedback from each event processing task when the process status of the new event processing flow is feedback, with the feedback order of the event processing tasks being the reverse of the order in which they were issued in the stack element table.

[0025] On the other hand, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0026] The memory stores computer-executed instructions;

[0027] The processor executes computer execution instructions stored in the memory to implement the stack-based single-processing method as described in the first aspect.

[0028] On the other hand, this application provides a computer-readable storage medium storing computer-executable instructions that, when executed, cause the computer to perform the stack-based event single-processing method as described in the first aspect.

[0029] On the other hand, this application provides a computer program product, including a computer program that, when executed by a processor, implements the stack-based event single-processing method as described in the first aspect.

[0030] This application provides a stack-based event order processing method that creates a process table and a stack element table in the backend server. The process table records the event order processing flow and its state. The inherent operable nature of the stack element table restricts the processing order of the event order tasks represented by the elements in the stack element table, achieving the effect of returning event order tasks based on the order of issuance (returning based on the order of issuance means feedback in reverse order). Therefore, this method does not introduce third-party workflow tools. Instead, it creates a stack element table in the backend server and utilizes the last-in-first-out (LIFO) characteristic of the stack data structure to implement the issuance and feedback of event order processing tasks. Therefore, compared to existing technologies, this application not only meets the event order processing requirements but also avoids the problem of introducing third-party workflow tools due to event order processing needs. It solves the problems of increased backend system complexity, increased maintenance difficulty, or incompatibility with third-party workflow tools caused by their introduction. Attached Figure Description

[0031] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0032] Figure 1 This is a schematic diagram illustrating an application scenario of the stack-based event single-handling method provided in this application.

[0033] Figure 2 This is a flowchart illustrating an event single-processing method based on a stack implementation, provided as an embodiment of this application.

[0034] Figure 3 A flowchart illustrating a stack-based event single-processing method provided for another embodiment of this application.

[0035] Figure 4 This is a schematic diagram of the stack-based event single-processing method provided in another embodiment of this application.

[0036] Figure 5 This is a schematic diagram of the pop logic in a stack-based event single-processing method provided in another embodiment of this application.

[0037] Figure 6 This is a schematic diagram of a stack-based event single-processing device provided as an embodiment of this application.

[0038] Figure 7 A schematic diagram of an electronic device provided for one embodiment of this application.

[0039] The accompanying drawings have illustrated specific embodiments of this disclosure, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0040] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0041] First, let's explain the terms used in this application:

[0042] Workflow refers to the automation of part or all of a business process in a computer application environment. It is an abstract and generalized description of a workflow and the business rules governing its various operational steps. The main problem that workflow addresses is: to achieve a specific business goal by automatically transferring documents, information, or tasks among multiple participants according to predetermined rules using computers.

[0043] BPMN is an abbreviation for Business Process Modeling Notation, which is one of the modeling and annotation methods for workflows. BPMN defines a set of general and easy-to-understand elements that users can combine to easily describe the various stages within a business process, as well as the sequence and branching logical relationships between these stages.

[0044] Stack: A stack is a linear data structure with restricted operations, where insertion and deletion operations are limited to one end of the list. This operational end is called the top of the stack, and the other end is called the bottom of the stack. Inserting a new element into a stack is called pushing onto the stack. Deleting an element from a stack is called popping from the stack.

[0045] Event Ticket: In this application, an event ticket refers to the details of an event entered from a business perspective (such as a production event ticket, complaint event ticket, or leave event ticket). A process instance, on the other hand, is a workflow instance from a technical perspective, and an event ticket is associated with a specific process instance. The process instance determines which department or user should handle the event ticket.

[0046] User task: A commonly used element in BPMN, representing a node in the process that requires user intervention. User groups, candidates, and other parameters can be configured to restrict which users have the necessary permissions.

[0047] User groups: User groups are formed by categorizing users into different groups according to certain rules. For example, users can be grouped according to their organization, and user groups are used to define which organization or department is responsible for a particular user's task.

[0048] Executor: The system user who completes each "user task" within the "workflow".

[0049] Workflow is a commonly used management tool in enterprise management, used to plan and process tasks generated within the enterprise. In enterprise management, a large number of event tickets are generated daily. The people who create these event tickets are usually not the frontline staff resolving the issues. For example, in bank management, the back-end system generates complaint event tickets based on customer complaints, while the front-end staff are responsible for resolving these complaints. Therefore, after creating an event ticket, a workflow is needed to process it, cascading the event ticket down to the front-end staff. Sometimes, after processing, the event ticket needs to be fed back to the back-end system along the same path, where the back-end system records the event processing status.

[0050] Several workflow tools have been developed in the prior art, such as Activiti and Flowable BPMN software, which provide general methods for handling event tickets. However, directly introducing these workflow tools into backend systems may increase the complexity and maintenance difficulty of the backend system, especially for some smaller, simpler backend systems, where introducing third-party workflow tools may cause system overload. Furthermore, workflow tools may become unusable during use because they are not adapted to specific event ticket handling scenarios.

[0051] Based on this, this application provides an event order processing method and apparatus based on a stack. This method creates a process table and a stack element table in the backend server. The process table records the event order processing flow and its state. The inherent operable nature of the stack element table restricts the processing order of the event order tasks represented by the elements in the stack element table, achieving the effect of returning event order tasks based on the order of issuance (returning based on the order of issuance means feedback in reverse order). Therefore, this method does not introduce third-party workflow tools. Instead, it creates a stack element table in the backend server and utilizes the last-in-first-out (LIFO) characteristic of the stack data structure to implement the issuance and feedback of event order processing tasks. Therefore, compared to existing technologies, this application not only meets the event order processing requirements but also avoids the problem of introducing third-party workflow tools due to event order processing needs. It solves the problems of increased backend system complexity, increased maintenance difficulty, or incompatibility of third-party workflow tools caused by their introduction.

[0052] The stack-based event handling method provided in this application is applied to electronic devices, such as backend servers and computers. Figure 1 This diagram illustrates the application of the stack-based event order processing method provided in this application. The electronic device includes a process table and a stack element table. When an event order processing task is initiated, a new event order processing flow needs to be inserted into the process table, and a new element and its corresponding organization number need to be inserted into the stack element table. When the status of the new event order processing flow is "issued," the event order processing task corresponding to the new element is issued to the corresponding processing organization based on the stack element table. When the status of the new event order processing flow is "feedback," the feedback from the event order processing task represented by the new element is received based on the stack element table.

[0053] Please see Figure 2 One embodiment of this application provides a stack-based event order processing method applied to a backend server. The backend server has a process table and a stack element table. The process table records the event order processing flow, which records at least one event order processing task's processing flow. Each event order processing flow has a process state. Each element in the stack element table represents an event order processing task, and each event order processing task has a corresponding processing mechanism. When an element is at the top of the stack, the event order processing task corresponding to that element is a task that can be sent down or feedback. The method includes:

[0054] S210, insert a new event order processing flow into the process table, and insert a new element and the organization number of the event order processing task represented by the new element into the stack element table. The new event order processing flow is used to record the processing flow of the event order processing task represented by the new element.

[0055] The process table stores the processing flow for all event tickets, as shown in Table 1. The fields in the process table include the process instance number (ID), the process instance status (STATUS, coded as PROCESS_SRTATUS), and the event ticket detail number (DTL_ID, which allows you to find the specific event ticket). Please refer to Table 2. The coded values ​​for PROCESS_SRTATUS include "PUSH", "POP", "FINISH", and "INT". "PUSH" represents a process instance status of "issued", "POP" represents a process instance status of "feedback", "FINISH" represents a process instance status of "normal termination", and "INT" represents a process instance status of "abnormal termination".

[0056] The stack element table is used to store event order processing tasks that need to be completed but have not yet been completed within the process. The element at the top of the stack represents the event order processing task currently pending, while elements at other positions represent tasks to be processed in the future. That is, as described above, when an element is only at the top of the stack element table, the corresponding event order processing task is a task that can be issued or responded to; when an element is not at the top of the stack, the corresponding event order processing task is a task that can be issued or responded to in the future. As shown in Table 1, the fields contained in the stack element include stack element number (ID), process instance number (PROCESS_ID), user group (USER_GROUP), executor (ASSIGNER), and element position (LOC, corresponding to the code STACK_ITEM_LOG). Please refer to Table 2; the coded values ​​of STACK_ITEM_LOG include "TOP", "MID", and "BIM", where "TOP" represents the top of the stack, "MID" represents the middle of the stack, and "BIM" represents the bottom of the stack.

[0057] Optionally, the backend server also maintains a historical process table to store all user operation records. As shown in Table 1, the historical process table includes fields such as the record number (ID) of the historical operation, the operator (OPERATOR), and the operation (OPERATION, coded as HISTORY_OPERATION). Please refer to Table 2; the coded values ​​for HISTORY_OPERATION include "START", "DISPATCH", "REPLY", and "FINISH". "START" indicates that the user initiated the process, "DISPATCH" indicates that the user distributed the task downwards, "REPLY" indicates that the user reported the processing status upwards, and "FINISH" indicates that the process ended.

[0058] Table 1 (Table Fields):

[0059]

[0060] Table 2 (Field Code Value Table):

[0061]

[0062] Backend system staff can create new event order processing flows, the status of new event order processing flows, and new elements in the stack element table. Correspondingly, the backend server responds with flow creation and element creation operations, inserts the new event order processing flow into the flow table, and inserts the new element and the organization number of the event order processing task represented by the new element into the stack element table.

[0063] S220, when the process status of the new event order processing flow is "issued", the event order processing task represented by the new element is issued to the processing organization corresponding to the organization number according to the position of the new element in the stack element table and the organization number of the event order processing task represented by the new element.

[0064] Please see Figure 3 The method provided in this embodiment, when inserting a new event order processing flow (or a new event order processing task) into the process table, first determines whether the flow status of the new event order processing flow is "issued". If the flow status of the new event order processing flow is "issued", then step S220 is executed, that is, the push logic is executed. If the flow status of the new event order processing flow is not "issued" but "feedback", then step S230 is executed, that is, the pop logic is executed.

[0065] In other words, when the backend server determines that the process status of a new event order processing flow is "issued," it executes the stack logic for pushing the event order processing task represented by the new element in the stack element table onto the stack, so that the event order processing task represented by the new element can be issued again. The following is a combination of... Figure 4 To explain.

[0066] like Figure 4 As shown, first, the executor (ASSIGNER) of the new element (event order processing task) to be inserted into the stack element table is obtained as A, and the subordinate organization number is obtained as B. The executor A can be specified by a backend worker or by the backend server. The subordinate organization number is a field value of a user group, used to create the event order processing task, indicating that the event order processing task is executed by the user group corresponding to this subordinate organization number. After obtaining A and B, the executor of the element currently at the top of the stack element table is updated to A.

[0067] Before inserting a new element into the stack element list, the positions of the existing elements in the stack element list need to be updated to make room at the top of the stack for the new element. The position of an element in the stack element list is then retrieved.

[0068] Optionally, when updating the position of an existing element in the stack element table, it is necessary to first determine if the current number of elements in the stack element table is 1. When the number of elements in the stack element table is equal to 1, the position of this element in the stack element table is definitely the top of the stack (TOP), and the position of one element in the stack element table (i.e., the top element) is updated to the bottom of the stack (BTM). When the number of elements in the stack element table is greater than 1, the position of the elements in the stack element table is updated to the middle of the stack (MID). In this way, when a new element is inserted into the stack element table, its position will be directly updated to the top of the stack (TOP). Optionally, a Structured Query Language (SQL) can be used to query and retrieve all elements at the top of the stack element table, i.e., the currently pending event processing tasks, in order to monitor the progress of all event processing tasks. When inserting a new element into the stack element table, the corresponding subordinate organization number B is inserted together with the new element. The LOC field value of the new element is taken as "TOP", that is, the new element is at the top of the stack.

[0069] After inserting the new element into the stack element table, if the new event order processing flow is still in the process of being sent out (i.e., no flow status update operation has been detected), the event order processing task represented by the new element is sent out to the user group corresponding to the lower-level organization number B, based on the lower-level organization number corresponding to the new element. At this time, the new element remains in the push mode. If the backend server detects a flow status update operation, it will update the status of the current event processing flow according to the flow status update operation. For example... Figure 4 As shown, the process first determines whether the detected process status update operation is to update the process status code of the new event order processing flow to "POP" (representing feedback). If the detected process status update operation is to update the process status code of the new event order processing flow to "POP", then the process status code of the new event order processing flow is updated to "POP", and the push of the new element onto the stack ends. At this time, the new element is in pop mode. If the detected process status update operation is not to update the process status code of the new event order processing flow to "POP", then the event order processing task represented by the new element continues to be issued.

[0070] Each element in this stack represents an event order processing task with a corresponding processing organization (organization number). When issuing event order processing tasks for each element in this stack, the tasks must be issued sequentially according to their positions in the stack. As described above, the position of a new element in the stack is the top of the stack, and the remaining elements are either the bottom (equal to 1 element) or the middle (equal to more than 1 element). When the event order task corresponding to the top element in the stack is issued to the corresponding processing organization, the position of the middle element in the stack is updated to the top, and the position of the bottom element is updated to the middle. Since only the top element in the stack can be issued or processed, by continuously updating the element positions, the event order processing tasks corresponding to each element can be issued sequentially.

[0071] Optional, such as Figure 4 As shown, it is also necessary to insert the downward dispatch operation record into the historical process table, that is, insert the record where the operator is A and the operation is "DISPATCH". Figure 4 Only one method of inserting a downward dispatch operation record into the history process table is shown, namely, updating the history process table before updating the executor of the top element of the stack. However, the timing of inserting the downward dispatch operation record into the history process table can be any time after executor A performs a downward dispatch operation.

[0072] S230, when the process status of the new event order processing flow is feedback, the feedback of the event order processing task represented by the new element is received in the reverse order of the event order processing task issued by the new element in the stack element table.

[0073] The current event single-process flow status can be changed from "issued update" to "feedback" after responding to the flow status update operation described in step S220, or it can be automatically triggered by the status switching trigger logic set in the backend system, changing the flow status of the new event single-process to "feedback". This status switching trigger logic can be pre-set by backend staff and not changed, or it can be made available to users in lower-level organizations, who can trigger it as needed.

[0074] As described in step S220, when the flow state of the current event single is feedback, the stack logic is popped from the stack for the event single processing task represented by the new element in the stack element table, so as to complete the recording of the processing flow of the event single processing task represented by the new element. The following is combined with... Figure 5 To explain.

[0075] like Figure 5As shown, first, the executor of the new element (event order processing task) is obtained as A, and then the number of elements in the stack element table is checked. When the number of elements in the stack element table is equal to 1, it means that the new element is the last task in the new event order processing flow and needs to be terminated. Optionally, executor A can be inserted into the history flow table, and then a "FINISH" operation record can be inserted to indicate that the user has ended the new event order processing flow. When the top element of the stack element table is popped, it means that the current event order flow is completely completed. At this time, the flow instance status in the flow table is updated to "FINISH" to indicate that the flow has ended.

[0076] When the number of elements in the stack element table is greater than 1, it indicates that the new element is an intermediate task in the new event single processing flow, and the stack element needs to be popped according to its position. Optionally, insert executor A into the history flow table, and then insert the operation record "REPLY" to indicate that the user has performed feedback processing. After the top element in the stack element table is popped, change the position of the new top element to the top of the stack. When all elements at the top of the stack element table are popped, it indicates that the current event single flow is completely completed. At this time, update the flow instance status in the flow table to "FINISH" to indicate that the flow has ended.

[0077] When a new event order processing flow is in the feedback stage, the positions of the elements in the stack element table are reversed compared to when the new event order processing flow was in the sending stage. Therefore, when processing event order tasks, the feedback order is the reverse of the sending order order in the stack element table. For example, if element 1 is at the top of the stack element table when the new event order processing flow is in the sending stage, then it will be at the bottom of the stack element table when the new event order processing flow is in the feedback stage.

[0078] Based on the descriptions of steps S210 and S220, the order of elements pushed onto and popped from the stack element table is reversed, achieving the original feedback of event single processing tasks. For example, in this new event single processing flow, there are 3 event single processing tasks, corresponding to 3 elements (element a, element b, and element c) in the stack element table. Element a is located at the top of the stack element table, element b is located in the middle of the stack element table, and element c is located at the bottom of the stack element table. During the distribution, elements a, b, and c are pushed onto the stack in the order they appear. This distribution is similar to "putting on a hat," with element b "putting on" element a and element c "putting on" element b. During feedback, it can be imagined as "removing the hat," that is, element c, located at the top of the stack element table, is popped first, then element b is popped, and then element a, located at the bottom of the stack element table, is popped.

[0079] In summary, this embodiment provides a stack-based event order processing method that creates a process table and a stack element table in the backend server. The process table records the event order processing flow and its state. The inherent operable nature of the stack top in the stack element table restricts the processing order of the event order processing tasks represented by the elements in the stack element table, achieving the effect of returning event order processing tasks based on the order of issuance (returning based on the order of issuance means feedback in reverse order). Therefore, this method does not introduce third-party workflow tools. Instead, it creates a stack element table in the backend server and utilizes the last-in-first-out (LIFO) characteristic of the stack data structure to implement the issuance and feedback of event order processing tasks. Therefore, compared to existing technologies, this application not only meets the event order processing requirements but also avoids the problem of introducing third-party workflow tools due to event order processing needs. It solves the problems of increased backend system complexity, increased maintenance difficulty, or incompatibility with third-party workflow tools caused by their introduction.

[0080] Please see Figure 6 One embodiment of this application provides an event single processing device 10 based on a stack, applied to a backend server. The backend server is provided with a process table and a stack element table. The process table is used to record the event single processing process, and the event single processing process is used to record the processing process of at least one event single processing task. Each event single processing process also has a process state. An element in the stack element table represents an event single processing task, and each event single processing task has a corresponding processing mechanism. When the element is at the top of the stack, the event single processing task corresponding to the element is a task that can be sent down or feedback.

[0081] The device 10 includes:

[0082] The task creation module 11 is used to insert a new event order processing flow into the process table, and to insert a new element and the organization number of the event order processing task represented by the new element into the stack element table. The new event order processing flow is used to record the processing flow of the event order processing task represented by the new element.

[0083] The dispatch module 12 is used to dispatch the event order processing task represented by the new element to the processing organization corresponding to the organization number when the process status of the new event order processing flow is dispatched, according to the position of the new element in the stack element table and the organization number of the event order processing task represented by the new element.

[0084] Feedback module 13 is used to receive feedback from each event processing task when the process status of the new event processing flow is feedback, with the feedback order of the event processing tasks being the reverse order of the event processing task issuance order in the stack element table.

[0085] When the process status of the new event ticket processing flow is "issued", it also includes:

[0086] The position update module 14 is used to update the position of the original element in the stack element table.

[0087] The task creation module 11 is specifically used to insert a new element into the stack element table and update the position of the new element in the stack element table to the top of the stack.

[0088] Specifically, the position update module 14 is used to update the position of an element in the stack element table to the bottom of the stack when the number of elements in the stack element table is equal to 1; and to update the position of an element in the stack element table to the middle of the stack when the number of elements in the stack element table is greater than 1.

[0089] The backend server is also configured with a historical process table, which is used to store user operation records. The device 10 also includes:

[0090] User operation record storage module 15 is used to store user operation records in the new event order processing flow. The user operation records include the operator of the event order processing task and the corresponding operation.

[0091] Please see Figure 7 One embodiment of this application provides an electronic device 20, which includes a processor 21 and a memory 22 communicatively connected to the processor. The memory 22 stores computer-executable instructions, and the processor 21 executes the computer-executable instructions stored in the memory to implement the stack-based event single-processing method as described in any of the preceding embodiments.

[0092] This application also provides a computer-readable storage medium storing computer-executable instructions that, when executed, cause the computer-executable instructions to be executed by a processor to implement the stack-based event single-processing method provided in any of the preceding embodiments.

[0093] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the stack-based event single-processing method provided in any of the preceding embodiments.

[0094] It should be noted that the aforementioned computer-readable storage media can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc. It can also be various electronic devices that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0095] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0096] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0097] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0098] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0099] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0100] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0101] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A stack-based event single-handling method, characterized in that, Applied to a backend server, the backend server is configured with a process table and a stack element table. The process table is used to record the event order processing process, and the event order processing process is used to record the processing process of at least one event order processing task. Each event order processing flow has a flow state; one element in the stack element table represents an event order processing task, and each event order processing task has a corresponding processing mechanism. When an element is at the top of the stack, the event order processing task corresponding to that element is a task that can be sent down or feedback; the method includes: Insert a new event order processing flow into the process table, and insert a new element and the organization number of the event order processing task represented by the new element into the stack element table. The new event order processing flow is used to record the processing flow of the event order processing task represented by the new element. When the process status of the new event order processing flow is "issued", the event order processing task represented by the new element is issued to the processing organization corresponding to the organization number according to the position of the new element in the stack element table and the organization number of the event order processing task represented by the new element. When the process status of the new event order processing flow is feedback, the feedback of the event order processing task represented by the new element in the stack element table is received in reverse order of the event order processing task issuance order. After inserting a new element into the stack element table, if a process status update operation is detected when the process status of the new event order processing flow is issued, the process status of the new event order processing flow is updated to feedback according to the process status update operation.

2. The method according to claim 1, characterized in that, Before inserting a new element into the stack element table, the process also includes: Update the position of the existing elements in the stack element table; Inserting a new element into the stack element table includes: Insert a new element into the stack element table, and simultaneously update the position of the new element in the stack element table to the top of the stack.

3. The method according to claim 2, characterized in that, Updating the position of an existing element in the stack element table includes: When the number of elements in the stack element table is equal to 1, update the position of one element in the stack element table to the bottom of the stack; When the number of elements in the stack element table is greater than 1, update the position of the element in the stack element table to be in the stack.

4. The method according to claim 1, characterized in that, The backend server is also configured with a historical process table, which is used to store user operation records. The method further includes: The user operation records in the new event order processing flow are stored, and the user operation records include the operator of the event order processing task and the corresponding operation.

5. An event single-processing device based on a stack implementation, characterized in that, Applied to a backend server, the backend server is configured with a process table and a stack element table. The process table records the event order processing flow, and each event order processing flow records the processing flow of at least one event order processing task. Each event order processing flow also has a process state. An element in the stack element table represents an event order processing task, and each event order processing task has a corresponding processing mechanism. When an element is at the top of the stack, the event order processing task corresponding to that element is a task that can be sent down or feedback. The device includes: The task creation module is used to insert a new event order processing flow into the process table, and to insert a new element and the organization number of the event order processing task represented by the new element into the stack element table. The new event order processing flow is used to record the processing flow of the event order processing task represented by the new element. The dispatch module is used to dispatch the event order processing task represented by the new element to the processing organization corresponding to the organization number when the process status of the new event order processing flow is dispatched, according to the position of the new element in the stack element table and the organization number of the event order processing task represented by the new element. The feedback module is used to receive feedback from each event processing task when the process status of the new event processing flow is feedback, with the feedback order of the event processing tasks in the reverse order of the event processing task issuance order in the stack element table as the feedback order. After inserting a new element into the stack element table, if a process status update operation is detected when the process status of the new event order processing flow is issued, the process status of the new event order processing flow is updated to feedback according to the process status update operation.

6. The apparatus according to claim 5, characterized in that, Also includes: The position update module is used to update the position of the original element in the stack element table. The task creation module is specifically used for: Insert a new element into the stack element table, and simultaneously update the position of the new element in the stack element table to the top of the stack.

7. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the stack-based event single-processing method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, cause the computer to perform the stack-based event single-processing method as described in any one of claims 1-4.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the stack-based event single-processing method as described in any one of claims 1-4.

Images