CN116307661A - Workflow state reverse recovery method, device, computer equipment and storage medium - Google Patents

Abstract

The invention discloses a workflow state reverse order recovery method, a workflow state reverse order recovery device, computer equipment and a storage medium, and relates to the technical field of workflow management. The method is characterized in that all tables before and after the change of the workflow state are respectively inquired and stored, corresponding newly added, updated and/or deleted data are compared and determined for each table after the change, then the newly added, updated and/or deleted data of each table after the change are packaged and are bound together with an execution time stamp to be stored as one piece of flow operation record information, a stack pressing-like process is realized, finally when a workflow state recovery request is received, all current tables are inquired and obtained, and the flow operation record information sequences obtained based on the reverse arrangement of the execution time stamp are combined, so that the workflow is gradually recovered to the workflow target state, a stack-off-like process is realized, and the maintainability, the reliability and the performance of a workflow management system can be greatly improved.

Description

Workflow state reverse recovery method, device, computer equipment and storage medium

technical field

The invention belongs to the technical field of workflow management, and in particular relates to a workflow state reverse recovery method, device, computer equipment and storage medium.

Background technique

Workflow management refers to the systematic realization of the approval and management of the company's daily office work flow, including administrative, financial, personnel and procurement approval processes. Through the information management of the work flow, the work efficiency of the enterprise can be improved.

The existing method for gradually restoring the workflow state (also referred to as the workflow state) to the previous historical state is to perform logical calculations based on the workflow state data to determine whether recovery is possible. If recovery is possible, first calculate the previous state. An operation action, and then calculate the affected data according to the change logic of the operation action, and finally restore the state based on this part of the affected data. However, since each retraction (that is, the process of restoring to the previous historical state) requires a lot of calculations and depends on the existing data and the logic of the last operation action, if the logic of the operation action changes in a certain version , you need to make corresponding judgments and compatibility in the retraction logic, otherwise it will lead to the failure of the retraction, cause data confusion, and cause great invariance and confusion to the user, which will lead to the following problems in the workflow management system: (1 ) has poor performance, that is, a large number of data operations are required to restore to the previous state each time, and as the version is updated more and more complex, the longer the recovery time is; (2) the reliability is poor, that is, Since the change of the logic of the operation action will affect the calculation logic of the retraction, the newly added action also needs to be compatible, so every time there is a change in other places, the logic there needs to be adjusted synchronously, otherwise it will lead to data confusion; ( 3) Poor maintainability, that is, due to the large number of calculations involved, if there is a slight deviation between the data and logic of an action, it will also lead to recovery failure and data confusion.

Contents of the invention

The object of the present invention is to provide a method, device, computer equipment, and computer-readable storage medium for reversing workflow state recovery, so as to solve the problem of maintainability, reliability, and performance in the state recovery process of existing workflow management systems. Relatively poor question.

In order to achieve the above object, the present invention adopts the following technical solutions:

In the first aspect, a method for reversing workflow state recovery is provided, including:

When a workflow status change request is received, query and store all pre-change tables involving process status data;

Executing the operation action logic in response to the workflow state change request to change the workflow state;

After the workflow status is changed, query and store all post-change tables related to process state data, wherein all the post-change tables correspond to all the pre-change tables one by one;

For each post-change table among all the post-change tables, determine the corresponding new data, update data and/or delete data according to the data comparison result with the corresponding pre-change table;

Combining the newly added data, updated data and/or deleted data of each changed table into a data package, and binding the data package with the execution time stamp of the operation action logic as a process operation record information storage In the process operation record table;

When receiving a workflow state recovery request, query to obtain all current tables related to process state data, and reversely arrange at least one piece of process operation record information in the process operation record table based on the execution time stamp, to obtain the sequence of process operation record information ;

According to all the current tables and the information sequence of the process operation record, the workflow is gradually rolled back to restore to the workflow target state requested in the workflow state restoration request.

Based on the content of the above invention, a new workflow state recovery scheme similar to the method of pushing and popping is provided, that is, before and after each workflow state change, all pre-change tables and all changes involving process state data are queried and stored After the table, and then for each post-change table among all the post-change tables, according to the data comparison result with the corresponding pre-change table, determine the corresponding new data, update data and/or delete data, and then add all The newly added data, updated data, and/or deleted data of each table after each change are packaged, and bound together with the execution time stamp of the operation action logic as a process operation record information stored in the process operation record table, to achieve a stack-like Finally, when receiving the workflow state recovery request, query to obtain all the current tables related to the process state data, and combine the process operation record information sequence based on the reverse order of the execution time stamp, so that the workflow can be gradually rolled back and restored to the state in The workflow target state requested in the workflow state recovery request realizes a process similar to popping, so that a large amount of calculation and action logic may not be involved in the recovery process, and the maintainability of the workflow management system can be greatly improved The reliability, reliability and performance are convenient for practical application and promotion.

In one possible design, all pre-change tables involving process state data are queried and stored, including:

Query in sequence to obtain all pre-change tables involving process state data;

Based on the MAP data structure containing the key name KEY and the key value VALUE, the table data of each pre-change table in the above-mentioned all pre-change tables is obtained as follows: first use the key name KEY as the column name and the key value VALUE as the column value, simulating the column data of each row in the table before each change, and obtaining the row data of each row in a MAP data structure, then using the key name KEY as the row data primary key ID and the key value VALUE as The mode of row data, simulates each row in the table before described each change, obtains the table data of the table before described each change;

Put the table data of each pre-alteration table into a linked list LIST data structure sequentially according to the query sequence, and obtain the first linked list LIST for storing all the pre-alteration tables.

In one possible design, all post-change tables that involve process state data are queried and stored, including:

Query and obtain all the changed tables related to the process state data in sequence according to the query sequence, wherein, all the changed tables correspond to all the pre-changed tables one by one;

Based on the linked list LIST data structure and the MAP data structure that includes the key name KEY and the key value VALUE, the table data of each changed table in the described all changed tables is obtained as follows: first adopt the key name KEY as the column name and The key value VALUE is the mode of the column value, simulates the column data of each row in the table after each change, obtains the row data of each row and is in the MAP data structure, and then adopts the linked list LIST data structure to store in the described The row data of each row in each changed table is obtained to obtain the table data of each changed table;

The table data of each changed table is sequentially put into another linked list LIST data structure according to the query sequence, and a second linked list LIST for storing all changed tables is obtained.

In a possible design, for each post-change table among all the post-change tables, according to the data comparison result with the corresponding pre-change table, determine the corresponding new data, update data and/or delete data, including :

Traversing the table data in the second linked list LIST and the table data in the first linked list LIST synchronously and sequentially according to the query sequence;

For the currently traversed second table data in the second linked list LIST and the first table data in the first linked list LIST, follow any one of the following methods (A) to (C) or their Any combination of determines the corresponding new data, updated data and/or deleted data:

(A) For each second row data in the second table data and in the MAP data structure, search whether there is a primary key identifier for the row data in the first table data according to the corresponding row data primary key ID If the key name KEY of the ID does not exist, the corresponding second row of data is used as a piece of newly added data corresponding to the second table data and the first table data;

(B) For each second row data in the second table data and in the MAP data structure, according to the corresponding row data primary key ID, search whether there is a primary key ID for the row data in the first table data If the key name KEY of the ID exists, then obtain the first key value VALUE corresponding to the key name KEY that identifies the ID for the row data primary key from the first table data;

For each of the second rows of data, determine the corresponding different data in the following manner: For each column in the first key value VALUE, compare the key value VALUE of the column with that in the second row of data and with the column The key value VALUE corresponding to the key name KEY, if the comparison result of the two key values VALUE is different, then the key name KEY and key value VALUE of the column will be used as a different data of the second row of data;

Using the different data of each second row of data as a piece of update data corresponding to the second table data and the first table data;

(C) For each first row data in the first table data and in the MAP data structure, according to the corresponding row data primary key ID, search whether there is a primary key ID for the row data in the second table data If the key name KEY of the ID does not exist, the corresponding first row of data is used as a piece of deleted data corresponding to the second table data and the first table data.

In a possible design, the newly added data, updated data and/or deleted data of each changed table are combined into one data package, including:

Merge the newly added data, updated data and/or deleted data of each changed table into a JSON data format to obtain a data package.

In a possible design, according to all the current tables and the information sequence of the process operation record, the workflow is gradually rolled back to recover to the workflow target state requested in the workflow state recovery request, including There are the following steps S70-S76:

S70. Initialize the sorting number K to 1, and then execute step S71, wherein K represents a positive integer and is less than or equal to the total number of information of the at least one process operation record information;

S71. Use all the current tables as all changed tables obtained after the latest Kth historical workflow state update and involving process state data, and then perform step S72;

S72. Obtain the K-th process operation record information in the process operation record information sequence, and analyze the data packet in the K-th process operation record information, and obtain the latest K-th historical workflow status The newly added data, updated data and/or deleted data obtained after the update and each changed table, and then step S73 is executed;

S73. According to the newly added data, updated data and/or deleted data of all the changed tables and each changed table obtained after the latest Kth historical workflow state update and involving the process state data, restore the obtained Describe all tables before the change of the latest Kth historical workflow state before updating and involving process state data, and then execute step S74;

S74. Judging whether the latest K-th historical workflow state is the workflow target state requested in the workflow state recovery request, if so, execute step S76, otherwise execute step S75;

S75. Use all pre-change tables that are related to process state data before the latest Kth historical workflow state update as all tables that are obtained after the latest K+1th historical workflow state update and involve process state data Change the back table, and make the sorting number K self-increment by 1, and then return to execute step S72;

S76. Restoring the workflow to the workflow target state according to all pre-change tables involving process state data before the latest Kth historical workflow state update.

In a possible design, after recovering and obtaining all pre-change tables involving process state data before the latest Kth historical workflow state update and before performing step S74, the method further includes:

Judging whether there is any abnormality in all pre-change tables involving process state data before the latest Kth historical workflow state update, if yes, terminate the workflow state and restore in reverse order, otherwise execute step S74.

In the second aspect, a workflow state reverse sequence restoration device is provided, including a data query storage module, a state change response module, a data comparison module before and after, a data packaging and recording module, a state restoration response module, and a state rollback restoration module;

The data query storage module is used to query and store all pre-change tables related to process state data when a workflow state change request is received;

The state change response module is communicatively connected to the data query storage module, and is used to execute operation logic in response to the workflow state change request to change the workflow state;

The data query storage module is also used to query and store all the changed tables related to the process state data after the workflow state is changed, wherein, all the changed tables are in one-to-one correspondence with all the pre-changed tables;

The before and after data comparison module is communicatively connected to the data query storage module, and is used to determine the corresponding newly added data, update data and/or delete data;

The data packaging and recording module is connected to the front and rear data comparison module by communication, and is used to combine the new data, update data and/or delete data of each table after the change into a data package, and combine the data package and The execution timestamp binding of the operation action logic is stored in the process operation record table as a process operation record information;

The state recovery response module is connected to the data packaging and recording module by communication, and is used to query and obtain all current tables related to process state data when receiving a workflow state recovery request, and arrange them in reverse order based on the execution time stamp in the process Operating at least one piece of process operation record information in the record table to obtain a sequence of process operation record information;

The state rollback restoration module is communicatively connected to the state restoration response module, and is used for recording information sequences according to all the current tables and the process operation, so that the work flow can be gradually rolled back to restore to the state in the state of the work flow The workflow target state requested to be restored in the request.

In a third aspect, the present invention provides a computer device, including a memory, a processor, and a transceiver connected in sequence, wherein the memory is used to store computer programs, the transceiver is used to send and receive data, and the processor uses After reading the computer program, execute the workflow state reverse order recovery method as described in the first aspect or any possible design in the first aspect.

In a fourth aspect, the present invention provides a computer-readable storage medium, where instructions are stored on the computer-readable storage medium, and when the instructions are run on a computer, any possible Design the reverse order recovery method of the workflow state described above.

In the fifth aspect, the present invention provides a computer program product containing instructions. When the instructions are run on a computer, the computer is made to execute the workflow state described in the first aspect or any possible design in the first aspect. Reverse order recovery method.

The beneficial effect of above-mentioned scheme:

(1) The present invention creatively provides a new workflow state recovery scheme similar to the way of pushing and popping the stack, that is, before and after each change of the workflow state, query and store all the pre-change tables and all table after change, and then for each table after change among all the tables after change, according to the data comparison result with the corresponding table before change, determine the corresponding new data, update data and/or delete data, and then The newly added data, updated data, and/or deleted data of each changed table are packaged and bound together with the execution time stamp of the operation action logic as a process operation record information stored in the process operation record table to achieve a similar push Finally, when receiving the workflow state recovery request, query to obtain all the current tables related to the process state data, and combine the process operation record information sequence based on the reverse order of the execution time stamp, so that the workflow can be gradually rolled back and restored to The workflow target state requested in the workflow state restoration request realizes a process similar to popping, so that a large number of calculations and action logic may not be involved in the recovery process, and the reliability of the workflow management system can be greatly improved. Maintainability, reliability and performance, easy for practical application and promotion;

(2) Since the scheme adopts a method similar to pushing and popping the stack, it only verifies the operation on the top of the stack and does not involve a lot of calculations, so the performance is high;

(3) Since this solution adopts generalized data changes, similar to push and pop processing, even if the action logic is changed, it will not affect the recovery logic, so the maintainability is high;

(4) Since each recovery of this scheme takes out the data change set of the last operation from the top of the similar stack, and then restores the update without involving calculations, it can ensure that the recovery can be successful every time, so the reliability is also high .

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic flowchart of a method for restoring a workflow state in reverse order provided by an embodiment of the present application.

FIG. 2 is a schematic structural diagram of an apparatus for restoring a reverse order of a workflow state provided by an embodiment of the present application.

FIG. 3 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the present invention will be briefly introduced below in conjunction with the accompanying drawings and the description of the embodiments or the prior art. Obviously, the following description about the structure of the accompanying drawings is only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work. It should be noted here that the descriptions of these embodiments are used to help understand the present invention, but are not intended to limit the present invention.

It will be understood that, although the terms first and second etc. may be used herein to describe various objects, these objects should not be limited by these terms. These terms are only used to distinguish one object from another. For example, a first object could be termed a second object, and, similarly, a second object could be termed a first object, without departing from the scope of example embodiments of the present invention.

It should be understood that for the term "and/or" that may appear in this article, it is only an association relationship describing associated objects, which means that there may be three relationships, for example, A and/or B may mean: there is A alone, There are three situations such as B alone or A and B at the same time; another example, A, B and/or C, can mean that there is any one of A, B and C or any combination of them; for possible occurrences in this article The term "/and" describes another relationship between associated objects, which means that there may be two relationships, for example, A/ and B, which can mean: there are two situations such as A alone or A and B at the same time; in addition, for The character "/" that may appear in this article generally indicates that the contextual objects are an "or" relationship.

Example:

As shown in Figure 1, the workflow state reverse order recovery method provided by the first aspect of this embodiment can be executed by, but not limited to, a computer device with certain computing resources, such as a platform server, a personal computer (PersonalComputer, PC, refers to A multipurpose computer of a size, price, and performance suitable for personal use; desktops, laptops to small notebooks and tablets, and ultrabooks are all personal computers), smartphones, Personal Digital Assistants (PDAs) ) or electronic devices such as wearable devices. As shown in FIG. 1 , the method for restoring the reverse order of the workflow state may include, but is not limited to, steps S1 to S7 as follows.

S1. When a workflow state change request is received, query and store all pre-change tables involving process state data.

In the step S1, the workflow state change request is routinely generated and sent to the local when the user operates on the workflow and triggers a state change action. All the pre-change tables are used to record the workflow state before the change. Specifically, all the pre-change tables related to the process state data are queried and stored, including but not limited to the following steps S11-S13.

S11. Query in sequence to obtain all tables before the change involving process state data.

In the step S11, the specific query acquisition method of all the tables before the change is an existing conventional method.

S12. Based on the MAP data structure comprising the key name KEY and the key value VALUE, obtain the table data of each table before the change in all the tables before the change as follows: first adopt the key name KEY as the column name and the key value VALUE In the way of column values, simulate the column data of each row in the table before each change, obtain the row data of each row and in the MAP data structure, and then use the key name KEY as the row data primary key identification ID and key value VALUE is in the form of row data, simulating each row in each table before change to obtain table data of each table before change.

In the step S12, the MAP data structure is an existing data structure similar to a set of key-value pairs, that is, the key name KEY and the key value VALUE form a key-value pair, wherein the key value VALUE can store any data type ; For example, the row data of a certain row in the MAP data structure is [column name 1: column value 1; column name 2: column value 2; column name 3: column value 3; ...]. Through the aforementioned step S12, the pre-change table data can be obtained, which is convenient for subsequent comparison of the table data before and after the change. For example, it can be directly judged according to the primary key ID of the row data whether there is a new record, or there may be an updated or deleted record.

S13. Put the table data of each pre-change table into a linked list LIST data structure sequentially according to the query sequence, and obtain the first linked list LIST for storing all the pre-change tables.

In the step S13, the linked list LIST data structure is also a common basic data structure, which is a linear table, but does not store data in a linear order, but stores it in each node until the next A node pointer (Pointer). Through the aforementioned step S13, subsequent traversal can be facilitated.

S2. Execute operation action logic in response to the workflow state change request to change the workflow state.

In the step S2, there are existing technical means in the specific response execution process, which will not be repeated here.

S3. After the workflow status is changed, query and store all post-change tables related to process state data, wherein all the post-change tables are in one-to-one correspondence with all the pre-change tables.

In the step S3, all the changed tables are used to record the changed workflow status. Specifically, all the changed tables related to the process status data are queried and stored, including but not limited to the following steps S31-S33: S31. Query and obtain all the changed tables related to the process state data in sequence according to the query sequence, wherein, all the changed tables are in one-to-one correspondence with all the pre-changed tables; S32. Based on the linked list LIST data structure and containing The MAP data structure of the key name KEY and the key value VALUE is obtained as follows in the table data of each changed table in all the changed tables: first, the key name KEY is used as the column name and the key value VALUE is the column value , simulating the column data of each row in the table after each change, obtaining the row data of each row and in the MAP data structure, and then using the linked list LIST data structure to sequentially store each row in the table after the change row data of each changed table to obtain the table data of each changed table; S33. put the table data of each changed table into another linked list LIST data structure in turn according to the query order, and obtain the data structure for storing all Describe the second linked list LIST of all changed tables.

S4. For each post-change table among all the post-change tables, determine the corresponding new data, update data and/or delete data according to the data comparison result with the corresponding pre-change table.

In the step S4, the newly added data may specifically refer to the newly added content in the table after the change relative to the table before the change, and the updated data may specifically refer to the content in the table before the change relative to the table after the change For the updated content, the deleted data may specifically refer to the deleted content in the table before the change relative to the table after the change. At the same time, specifically, for each post-change table in all the post-change tables, according to the data comparison results with the corresponding pre-change tables, determine the corresponding new data, update data and/or delete data, including but not limited to There are the following steps S41 to S42.

S41. Traversing the table data in the second linked list LIST and the table data in the first linked list LIST synchronously and sequentially according to the query sequence.

S42. For the currently traversed second table data in the second linked list LIST and the first table data in the first linked list LIST, follow any of the following methods (A) to (C) Or any combination thereof to determine corresponding added data, updated data and/or deleted data.

(A) For each second row data in the second table data and in the MAP data structure, search whether there is a primary key identifier for the row data in the first table data according to the corresponding row data primary key ID If the key name KEY of the ID does not exist, the corresponding second row of data is used as a new piece of data corresponding to the second table data and the first table data. In addition, if both exist, there will be no new data corresponding to the second table data and the first table data.

(B) For each second row data in the second table data and in the MAP data structure, according to the corresponding row data primary key ID, search whether there is a primary key ID for the row data in the first table data The key name KEY of ID, if exist, then obtain from described first table data and be the first key value VALUE corresponding to the key name KEY of identification ID of this row data primary key; For described each second row data, according to as follows Determine the corresponding different data: For each column in the first key value VALUE, compare the key value VALUE of the column with the key value VALUE in the second row of data and corresponding to the key name KEY of the column, if If the comparison result of the two key values VALUE is different, then the key name KEY and key value VALUE of the column are used as a different data of the second row of data; Update data corresponding to the second table data and the first table data. The aforementioned first key value VALUE is a row data in a MAP data structure, so there will be key names KEY and key values VALUE of each column. If the comparison results of the two key values VALUE are different, it indicates that the corresponding column has changed when it is changed, and vice versa. The updated content of the table after the change. In addition, if there is no different data in each second row of data, there will be no update data corresponding to the second table data and the first table data.

(C) For each first row data in the first table data and in the MAP data structure, according to the corresponding row data primary key ID, search whether there is a primary key ID for the row data in the second table data If the key name KEY of the ID does not exist, the corresponding first row of data is used as a piece of deleted data corresponding to the second table data and the first table data. In addition, if both exist, there will be no delete data corresponding to the second table data and the first table data.

S5. Combine the newly added data, updated data and/or deleted data of each changed table into a data package, and bind the data package with the execution time stamp of the operation action logic as a process operation record The information is stored in the process operation log table.

In the step S5, in order to achieve the purpose of lightweight records, preferably, the newly added data, updated data and/or deleted data of each changed table are combined into one data package, including but not limited to: The newly added data, updated data and/or deleted data of each changed table are combined into a JSON data format to obtain a data package. The aforementioned JSON data format is a lightweight existing data interchange format. In addition, the process operation record information may also include, but is not limited to, specific content such as process ID, operator, and operation action.

S6. When receiving the workflow state recovery request, query and obtain all current tables related to the process state data, and at least one piece of process operation record information arranged in the process operation record table in reverse order based on the execution time stamp, to obtain the process operation record information sequence.

In the step S6, the workflow state recovery request is also routinely generated and sent to the local when the user operates on the workflow and triggers a state retraction action, which needs to be specific but not limited to include the requested workflow target state. The all current tables are used to record the current workflow state, that is, all changed tables obtained after the latest first historical workflow state update and involving process state data. In addition, when receiving the workflow state recovery request, it is also possible to judge whether the recovery is allowed through various authority checks based on the conventional authority check method, and if so, perform the subsequent step S7, otherwise terminate the reverse order recovery of the workflow state .

S7. According to all the current tables and the information sequence of the process operation record, the workflow is gradually rolled back to restore to the workflow target state requested in the workflow state restoration request.

In the step S7, specifically, it includes but not limited to the following steps S70-S76.

S70. Initialize the sort number K to 1, and then perform step S71, wherein K represents a positive integer and is less than or equal to the total number of information of the at least one piece of process operation record information.

S71. All the current tables are used as all changed tables obtained after the latest Kth historical workflow state update and involving process state data, and then step S72 is executed.

S72. Obtain the K-th process operation record information in the process operation record information sequence, and analyze the data packet in the K-th process operation record information, and obtain the latest K-th historical workflow status Step S73 is performed after updating the newly added data, updated data and/or deleted data of each changed table.

S73. According to the newly added data, updated data and/or deleted data of all the changed tables and each changed table obtained after the latest Kth historical workflow state update and involving the process state data, restore the obtained All tables before the change of the latest Kth historical workflow state before updating and involving process state data, and then execute step S74.

In the step S73, the specific restoration process is opposite to the aforementioned step S42, that is, for the newly added data, a delete statement is generated and the corresponding data deletion action is executed in the changed table; for the updated data, an update statement is generated and Execute the corresponding data update action in the table; for deleting data, generate an insert statement and execute the corresponding data insertion action in the table after the change; thus, through the aforementioned data deletion action, data update action and data insertion action, you can restore the data before the update surface. In addition, in order to discover and deal with the existing recovery abnormality in time, preferably, after recovering and obtaining all pre-change tables related to process state data before the latest Kth historical workflow state update and before performing step S74, The method also includes: judging whether there is any abnormality in all tables before the change of the latest Kth historical workflow state and involving process state data (the specific abnormality judgment method is an existing conventional method, such as a certain column The value should be an integer, but a decimal is recovered, which can be judged as an abnormal situation), if so, terminate the workflow state and restore in reverse order, otherwise execute step S74.

S74. Judging whether the latest Kth historical workflow state is the workflow target state requested in the workflow state recovery request, if yes, execute step S76, otherwise execute step S75.

S75. Use all pre-change tables that are related to process state data before the latest Kth historical workflow state update as all tables that are obtained after the latest K+1th historical workflow state update and involve process state data Change the back table, and make the sorting number K self-increment by 1, and then return to execute step S72;

S76. Restoring the workflow to the workflow target state according to all pre-change tables involving process state data before the latest Kth historical workflow state update.

The aforementioned steps S70-S76 can specifically start a transaction (the primary key auto-growth of the table corresponding to this operation needs to be turned off at this time) and submit the transaction to complete the workflow recovery when the workflow is restored to the workflow target state, Finally, the recovery result is fed back to the user interface for notification.

Therefore, based on the reverse order recovery method of the workflow state described in the aforementioned steps S1-S7, a new workflow state recovery scheme similar to the method of pushing and unstacking is provided, that is, query and query before and after each workflow state change. Store all pre-change tables and all post-change tables related to process state data, and then, for each post-change table in all the post-change tables, determine the corresponding new data according to the data comparison result with the corresponding pre-change table , update data and/or delete data, and then package the new data, update data and/or delete data of each changed table, and bind them together with the execution time stamp of the operation action logic as a piece of process operation record information Stored in the process operation record table to implement a process similar to pushing the stack. Finally, when receiving a workflow state recovery request, query to obtain all current tables involving process state data, and combine the process operation records based on the reverse order of the execution timestamp Information sequence, so that the workflow can be gradually rolled back to restore the workflow target state requested in the workflow state restoration request, and realize a process similar to popping, so that a large number of calculations and action logic may not be involved in the retraction process , which can greatly improve the maintainability, reliability and performance of the workflow management system, which is convenient for practical application and promotion.

As shown in Fig. 2, the second aspect of this embodiment provides a virtual device for realizing the reverse order recovery method of the workflow state described in the first aspect, including a data query storage module, a status change response module, a data comparison module before and after, Data packaging and recording module, status recovery response module and status rollback recovery module;

The data query storage module is used to query and store all pre-change tables related to process state data when a workflow state change request is received;

The state change response module is communicatively connected to the data query storage module, and is used to execute operation logic in response to the workflow state change request to change the workflow state;

The data query storage module is also used to query and store all the changed tables related to the process state data after the workflow state is changed, wherein, all the changed tables are in one-to-one correspondence with all the pre-changed tables;

The before and after data comparison module is communicatively connected to the data query storage module, and is used to determine the corresponding newly added data, update data and/or delete data;

The data packaging and recording module is connected to the front and rear data comparison module by communication, and is used to combine the new data, update data and/or delete data of each table after the change into a data package, and combine the data package and The execution timestamp binding of the operation action logic is stored in the process operation record table as a process operation record information;

The state recovery response module is connected to the data packaging and recording module by communication, and is used to query and obtain all current tables related to process state data when receiving a workflow state recovery request, and arrange them in reverse order based on the execution time stamp in the process Operating at least one piece of process operation record information in the record table to obtain a sequence of process operation record information;

The state rollback restoration module is communicatively connected to the state restoration response module, and is used for recording information sequences according to all the current tables and the process operation, so that the work flow can be gradually rolled back to restore to the state in the state of the work flow The workflow target state requested to be restored in the request.

For the working process, working details, and technical effects of the foregoing devices provided in the second aspect of this embodiment, reference may be made to the method for restoring the reverse order of the workflow state described in the first aspect, and details are not repeated here.

As shown in FIG. 3 , the third aspect of this embodiment provides a computer device for realizing the reverse order recovery method of the workflow state as described in the first aspect, including a memory, a processor, and a transceiver that are sequentially connected by communication, wherein, The memory is used to store a computer program, the transceiver is used to send and receive data, and the processor is used to read the computer program and execute the workflow state reverse order recovery method as described in the first aspect. For example, the memory may include, but is not limited to, random access memory (Random-Access Memory, RAM), read-only memory (Read-Only Memory, ROM), flash memory (Flash Memory), first-in-first-out memory (First Input First Output, FIFO) and/or first-in-last-out memory (First Input Last Output, FILO) and the like.

For the working process, working details and technical effects of the foregoing computer equipment provided in the third aspect of this embodiment, please refer to the method for restoring the workflow state in reverse order described in the first aspect, and details are not repeated here.

The fourth aspect of this embodiment provides a computer-readable storage medium that stores instructions including the workflow state reverse order recovery method as described in the first aspect, that is, the computer-readable storage medium stores instructions, when the When the instruction is run on the computer, the workflow state reverse order recovery method as described in the first aspect is executed. Wherein, the computer-readable storage medium refers to a carrier for storing data, which may, but is not limited to, include computer-readable storage media such as floppy disks, optical disks, hard disks, flash memory, USB flash drives and/or memory sticks (Memory Stick), and the computer may It is a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

For the working process, working details and technical effects of the aforementioned computer-readable storage medium provided in the fourth aspect of this embodiment, please refer to the method for restoring the reverse order of the workflow state as described in the first aspect, and details are not repeated here.

The fifth aspect of this embodiment provides a computer program product containing instructions, and when the instructions are run on a computer, the computer is made to execute the method for restoring the reverse order of the workflow state as described in the first aspect. Wherein, the computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices.

Finally, it should be noted that: the above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A method for reverse order restoration of workflow status, comprising:

when a workflow status change request is received, querying and storing all pre-change tables related to the flow status data;

executing operation action logic in response to the workflow status change request to change the workflow status;

After the workflow state is changed, inquiring and storing all changed tables related to the flow state data, wherein all the changed tables are in one-to-one correspondence with all the tables before changing;

determining corresponding newly added data, updated data and/or deleted data according to the data comparison result of the tables before the change aiming at each table after the change in all tables after the change;

combining the new data, the updated data and/or the deleted data of each changed table into a data packet, and binding the data packet and the execution time stamp of the operation action logic as a piece of flow operation record information to be stored in a flow operation record table;

when a workflow state recovery request is received, inquiring and acquiring all current tables related to flow state data, and according to at least one piece of flow operation record information arranged in the flow operation record table in a description mode based on an execution time stamp, obtaining a flow operation record information sequence;

and gradually rollback the workflow to the workflow target state requested to be restored in the workflow state restoration request according to the current tables and the flow operation record information sequence.

2. The workflow status reverse recovery method of claim 1 wherein querying and storing all pre-change tables relating to flow status data comprises:

sequentially inquiring and acquiring all pre-change tables related to flow state data;

based on the MAP data structure containing KEY name KEY and KEY VALUE, table data of each of the pre-change tables is obtained as follows: firstly, simulating column data of each row in each pre-change table by adopting a mode that a KEY name KEY is a column name and a KEY VALUE is a column VALUE to obtain row data of each row and in a MAP data structure, and then simulating each row in each pre-change table by adopting a mode that the KEY name KEY is a row main KEY identification ID and the KEY VALUE is row data to obtain table data of each pre-change table;

and sequentially placing the table data of each pre-change table into a linked LIST data structure according to the query sequence to obtain a first linked LIST for storing all the pre-change tables.

3. The workflow status reverse recovery method of claim 2 wherein querying and storing all post-change tables relating to flow status data comprises:

Sequentially inquiring and acquiring all changed tables related to flow state data according to the inquiring sequence, wherein all the changed tables are in one-to-one correspondence with all the changed tables;

based on the linked LIST data structure and the MAP data structure containing KEY name KEY and KEY VALUE, table data of each changed table in the all changed tables is obtained as follows: simulating column data of each row in each changed table by adopting a mode that a KEY name KEY is a column name and a KEY VALUE is a column VALUE to obtain row data of each row and in a MAP data structure, and then sequentially storing the row data of each row in each changed table by adopting a linked LIST LIST data structure to obtain table data of each changed table;

and sequentially placing the table data of each changed table into another linked LIST data structure according to the query sequence to obtain a second linked LIST for storing all the changed tables.

4. A workflow status reverse recovery method according to claim 3, wherein determining corresponding newly added data, updated data and/or deleted data for each of the post-change tables based on a data comparison with the corresponding pre-change table comprises:

Synchronously traversing the table data in the second linked LIST and the table data in the first linked LIST in sequence according to the query sequence;

for the second table data currently traversed and in the second linked LIST and the first table data in the first linked LIST, determining corresponding newly added data, updated data and/or deleted data according to any one of the following modes (a) - (C) or any combination thereof:

(A) For each second row of data in the second table data and in the MAP data structure, searching whether a KEY name KEY which is the data main KEY identification ID exists in the first table data according to the corresponding data main KEY identification ID, and if not, taking the corresponding second row of data as a piece of newly-added data corresponding to the second table data and the first table data;

(B) For each second row of data in the second table data and in the MAP data structure, searching whether a KEY name KEY which is the row of data main KEY identification ID exists in the first table data according to the corresponding row of data main KEY identification ID, and if so, acquiring a first KEY VALUE corresponding to the KEY name KEY which is the row of data main KEY identification ID from the first table data;

For each second row of data, corresponding distinct data is determined as follows: for each column in the first KEY VALUE, comparing the KEY VALUE of the column with the KEY VALUE corresponding to the KEY name KEY in the second row data, and if the comparison result of the two KEY VALUEs is different, taking the KEY name KEY and the KEY VALUE of the column as different data of one piece of second row data;

taking the different data of each second row data as update data corresponding to the second table data and the first table data;

(C) For each first row of data in the first table data and in the MAP data structure, searching whether a KEY name KEY which is the data main KEY identification ID exists in the second table data according to the corresponding data main KEY identification ID, and if not, taking the corresponding first row of data as a piece of deletion data which corresponds to the second table data and the first table data.

5. The method according to claim 1, wherein merging the new data, the updated data and/or the deleted data of each changed table into one data packet comprises:

And merging the newly added data, the updated data and/or the deleted data of each changed table into a JSON data format to obtain a data packet.

6. The method for reverse order restoration of workflow status according to claim 1, wherein the step of gradually reverting the workflow back to the workflow target status requested to be restored in the workflow status restoration request according to the all current table and the sequence of flow operation record information comprises the steps of S70 to S76:

s70, initializing a sequence number K to be 1, and then executing a step S71, wherein K represents a positive integer and is smaller than or equal to the total number of the at least one piece of flow operation record information;

s71, taking all the current tables as all changed tables which are obtained after the latest K-th historical workflow state is updated and relate to flow state data, and then executing step S72;

s72, obtaining the K-th flow operation record information in the flow operation record information sequence, analyzing a data packet in the K-th flow operation record information, obtaining new data, updated data and/or deleted data of each changed table obtained after the latest K-th historical workflow state is updated, and executing step S73;

S73, recovering all the tables before the latest K historical workflow state is updated and related to the flow state data according to all the tables after the latest K historical workflow state is updated and the new data, the updated data and/or the deleted data of all the tables after the latest K historical workflow state is updated and related to the flow state data, and executing step S74;

s74, judging whether the latest K historical workflow state is a workflow target state requested to be restored in the workflow state restoration request, if so, executing a step S76, otherwise, executing a step S75;

s75, taking all the tables before the latest K-th historical workflow state update and related to the flow state data as all the tables after the latest K+1st historical workflow state update and related to the flow state data, adding the ranking number K by 1, and then returning to execute the step S72;

s76, restoring the workflow to the workflow target state according to all the tables before the latest Kth historical workflow state update and related to the flow state data.

7. The method of claim 6, wherein after recovering all pre-change tables that were prior to the last kth historical workflow state update and that relate to flow state data and before executing step S74, the method further comprises:

And judging whether all the tables before the latest Kth historical workflow state update and related to the flow state data are abnormal, if so, stopping the reverse order restoration of the workflow state, otherwise, executing step S74.

8. The workflow state reverse sequence recovery device is characterized by comprising a data query storage module, a state change response module, a front-back data comparison module, a data packaging and recording module, a state recovery response module and a state rollback recovery module;

the data query storage module is used for querying and storing all pre-change tables related to the flow state data when receiving a workflow state change request;

the state change response module is in communication connection with the data query storage module and is used for responding to the workflow state change request to execute operation action logic so as to change the workflow state;

the data query storage module is further used for querying and storing all tables related to the flow state data after the workflow state is changed, wherein all tables correspond to all tables one by one;

the front-back data comparison module is in communication connection with the data query storage module and is used for determining corresponding newly-added data, updated data and/or deleted data according to the data comparison result of the corresponding front-change table aiming at each of the all the changed tables;

The data packaging and recording module is in communication connection with the front-back data comparison module and is used for combining the newly added data, the updated data and/or the deleted data of each changed table into a data packet, and binding the data packet and the execution time stamp of the operation action logic as a piece of flow operation record information to be stored in a flow operation record table;

the state recovery response module is in communication connection with the data packaging and recording module and is used for inquiring and acquiring all current tables related to flow state data when a workflow state recovery request is received, and at least one piece of flow operation record information arranged in the flow operation record table is described based on an execution time stamp to obtain a flow operation record information sequence;

and the state rollback recovery module is in communication connection with the state recovery response module and is used for gradually rollback recovering the workflow to the workflow target state requested to be recovered in the workflow state recovery request according to the current tables and the flow operation record information sequence.

9. A computer device comprising a memory, a processor and a transceiver in communication connection in sequence, wherein the memory is configured to store a computer program, the transceiver is configured to transmit and receive data, and the processor is configured to read the computer program and perform the workflow status reverse recovery method according to any one of claims 1 to 7.

10. A computer readable storage medium having instructions stored thereon which, when executed on a computer, perform the workflow status reverse order restoration method of any of claims 1-7.

Images