Process approval method and system based on field version snapshot comparison

Abstract

The invention belongs to the technical field of data processing. The invention provides a process approval method and system based on field version snapshot comparison, and the method comprises the steps: reading a rejection rule of a current approval node and a key field snapshot value in the currently rejected approval request when the approval request is rejected at the current approval node, and returning the approval request to a target node; when the modified approval request is resubmitted from the target node, obtaining the rejection rule, and if the return of the rejection rule is set as sequential circulation, directly submitting the modified approval request to the next point of the target node; if the return of the rejection rule is set to return to the current approval node, reading the key field of the modified approval request and comparing the key field with the snapshot value of the key field, if the key field is consistent with the snapshot value of the key field, returning to the current approval node, and if the key field is inconsistent with the snapshot value of the key field, directly submitting the modified approval request to the next point of the target node; and the accuracy and the consistency of the data are enhanced.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular, to a process approval method and system based on field version snapshot comparison. Background Art

[0002] The statements in this section merely provide background art related to the present invention and do not necessarily constitute prior art.

[0003] In the current field of enterprise process management and approval automation, the traditional process flow mode is that when a document is rejected by a certain approval node and requires modification, after the modification is completed and resubmitted, it is necessary to re-review from the rejected node according to the flowchart. For example, for a process with four nodes A→B→C→D, when it is rejected from node D to node A, after node A is modified and resubmitted, nodes B, C, and D need to be re-reviewed in sequence.

[0004] To improve the process operation efficiency, the current enterprise process approval system provides two resubmission methods in the rejection scenario: sequential flow, re-flowing according to the process definition path (such as A→B→C→D); returning to the original node, directly jumping back to the original rejection node to continue the approval. Although this method improves the efficiency, there is a risk that the key fields are not re-reviewed after modification (for example, directly skipping the subsequent approval nodes after modifying the "application amount").

[0005] In summary, the current automated approval process has the following problems: (1) The imbalance between efficiency and risk. The mechanism of returning to the original node sacrifices the audit integrity of key data changes; (2) The fragmentation of static process and dynamic data. The process path decision is not dynamically associated with the field modification status; (3) The conflict between formal integrity and substantial effectiveness. The change of key fields may bypass the necessary approval links. Summary of the Invention

[0006] To solve the deficiencies of the prior art, the present invention provides a process approval method and system based on field version snapshot comparison, which solves the problems of lack of effective monitoring and lack of mandatory re-review mechanism after modification of key fields in the rejection jump scenario of the existing enterprise process approval system, can significantly improve the rigor and efficiency of the approval process, reduce the approval risk and the possibility of data inconsistency, and enhance the accuracy and consistency of data.

[0007] To achieve the above object, the present invention adopts the following technical solutions: In the first aspect, the present invention provides a process approval method based on field version snapshot comparison.

[0008] A process approval method based on field version snapshot comparison includes the following processes: When the approval request is rejected at the current approval node, read the rejection rule of the current approval node and the snapshot value of the key fields in the currently rejected approval request, and return the approval request to the target node; When the modified approval request is resubmitted from the target node, obtain the rejection rule. If the return setting of the rejection rule is sequential transfer, directly submit the modified approval request to the next point of the target node; If the return setting of the rejection rule is to return to the current approval node, read the key fields of the modified approval request and compare them with the snapshot value of the key fields. If the comparison is consistent, return to the current approval node; if the comparison is inconsistent, directly submit the modified approval request to the next point of the target node.

[0009] As a further limitation of the first aspect of the present invention, the key fields are fields pre-configured in the approval workflow, and the target node is the default rejection node or the target node selected by the approver of the current approval node.

[0010] As a further limitation of the first aspect of the present invention, if the comparison is consistent and return to the current approval node, it includes: If the key fields are not modified, the attribute of returning to this node on the current approval node remains valid, and directly submit the modified approval request to the current approval node.

[0011] As a further limitation of the first aspect of the present invention, if the comparison is inconsistent and directly submit the modified approval request to the next point of the target node, it includes: If the key fields are modified, the attribute of returning to this node on the current approval node becomes invalid, and directly submit the modified approval request to the next point of the target node.

[0012] As a further limitation of the first aspect of the present invention, after reading the rejection rule of the current approval node, if the return setting of the rejection rule is to return to the current approval node, record the information of the current approval node for the return of the modified approval request.

[0013] As a further limitation of the first aspect of the present invention, use the latest intermediate snapshot recorded at the time of rejection as the reference snapshot, where is the index of the last intermediate snapshot before rejection; Read the key field values of the modified approval request to obtain the current value set where , and are the values of the modified key fields , and ; For each key field , compare the modified value with the corresponding value in the baseline snapshot ; Define a comparison function such that when , it indicates that the field has not been modified; when , it indicates that the field has been modified; Statistically analyze the comparison results of all key fields and calculate the number of modified fields ; If , that is, if there is a modified key field, the return attribute of the current approval node becomes invalid and is submitted to the next node in the process; If , that is, if all key fields have not been modified, use the return attribute of the current approval node as the criterion and directly jump to the current approval node to continue the approval process.

[0014] As a further limitation of the first aspect of the present invention, when the number of key fields is greater than a set threshold, a parallel comparison method is adopted. The key fields are divided into multiple subsets and compared on different threads or processors, and finally the comparison results are summarized.

[0015] In a second aspect, the present invention provides a process approval system based on field version snapshot comparison.

[0016] A process approval system based on field version snapshot comparison, comprising: A data reading unit configured to: when an approval request is rejected at the current approval node, read the rejection rule of the current approval node and the key field snapshot values in the currently rejected approval request, and return the approval request to the target node; A first judgment unit configured to: when the modified approval request is resubmitted from the target node, obtain the rejection rule. If the return setting of the rejection rule is sequential transfer, directly submit the modified approval request to the next point of the target node; A second judgment unit configured to: if the return setting of the rejection rule is to return to the current approval node, read the key fields of the modified approval request and compare them with the key field snapshot values. If the comparison is consistent, return to the current approval node; if the comparison is inconsistent, directly submit the modified approval request to the next point of the target node.

[0017] In a third aspect, the present invention provides a process approval system based on field version snapshot comparison.

[0018] A process approval system based on field version snapshot comparison, comprising: A process definition module, configured to: define and configure key fields, and set rejection rules; A snapshot management module, configured to: save the field snapshots before and after the modification of the approval request; A dynamic routing engine, configured to: execute the process approval method based on field version snapshot comparison described in the first aspect of the present invention.

[0019] In a fourth aspect, the present invention provides a computer device, comprising: a processor and a computer-readable storage medium; A processor, adapted to execute a computer program; A computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by the processor, the process approval method based on field version snapshot comparison described in the first aspect of the present invention is implemented.

[0020] Compared with the prior art, the beneficial effects of the present invention are: 1. The present invention innovatively proposes a process approval method based on field version snapshot comparison. If the return setting of the rejection rule is set to sequential transfer, the modified approval request is directly submitted to the next point of the target node. If the return setting of the rejection rule is set to return to the current approval node, the key fields of the modified approval request are read and compared with the keyword snapshot values. If the comparison is consistent, the current approval node is returned. If the comparison is inconsistent, the modified approval request is directly submitted to the next point of the target node, solving the problems of lack of effective monitoring and lack of a mandatory re-review mechanism after the modification of key fields in the existing enterprise process approval system in the rejection jump scenario, significantly improving the rigor and efficiency of the approval process, reducing the approval risk and the possibility of data inconsistency, and enhancing the accuracy and consistency of data.

[0021] 2. The key fields of the present invention are fields pre-configured in the approval workflow. By pre-configuring the key fields, it can be ensured that throughout the approval workflow, consistent standards are adopted for those fields that are important and require special attention, which helps to reduce approval differences or errors caused by inconsistent understandings of the importance of fields by different approval personnel or different approval links; the pre-configured key fields support custom changes and can be flexibly adjusted according to actual business needs. When the business process changes or new fields that require special attention are added, the pre-configured key field list can be easily updated, realizing the flexible configuration of the approval process.

[0022] 3. The present invention innovatively proposes a process approval method based on field version snapshot comparison. When the key fields are not modified, returning to the current approval node can ensure that the approvers can continue to process based on the previous approval context without having to re-understand or confirm the basic information of the approval request, which helps to maintain the coherence and consistency of the approval process. If the user only modifies the non-key fields while the key fields remain unchanged, then the user expects the approval request to quickly return to the current approval node for processing instead of being transferred to other unnecessary nodes, which helps to improve the user experience and reduce the user's waiting time.

[0023] 4. The present invention innovatively proposes a process approval method based on field version snapshot comparison. If the key fields are modified, the attribute of returning to this node on the current approval node becomes invalid, and the modified approval request is directly submitted to the next point of the target node, ensuring that when these key information are modified, the approval process can adapt to this dynamic change, no longer return to the current approval node, but continue to flow to the next node to adapt to the new approval requirements or conditions, avoiding repeated approval or invalid approval that may be caused by the modification of key fields.

[0024] Advantages of additional aspects of the present invention will be partly given in the following description, partly will become obvious from the following description, or will be learned through the practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The specification drawings forming a part of the present invention are used to provide a further understanding of the present invention. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation to the present invention.

[0026] Figure 1 Schematic diagram of the process approval method based on field version snapshot comparison provided for an exemplary embodiment of the present invention; Figure 2 Schematic diagram of the process approval system based on field version snapshot comparison provided for an exemplary embodiment of the present invention; Figure 3 Schematic diagram of the process approval system based on field version snapshot comparison provided for another exemplary embodiment of the present invention; Figure 4 Schematic diagram of the computer device provided for an exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0027] The present invention will be further described below in conjunction with the drawings and embodiments.

[0028] It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which the present invention belongs.

[0029] The present invention proposes a process approval method based on field version snapshot comparison, aiming to solve the problems in the existing enterprise process approval system that there is a lack of effective monitoring and mandatory re-review mechanism after keyword fields are modified, resulting in potential risks and data inconsistencies in the approval process; through intelligent monitoring means, it is ensured that every modification of the keyword fields can be promptly approved and confirmed, thereby maintaining the rigor of the process approval and the accuracy of the data. As Figure 1 shown, it includes the following processes: S101: When the approval request is rejected at the current approval node, read the rejection rule of the current approval node and the keyword field snapshot value in the currently rejected approval request, and return the approval request to the target node; S102: When the modified approval request is resubmitted from the target node, obtain the rejection rule. If the return setting of the rejection rule is sequential flow, directly submit the modified approval request to the next point of the target node; S103: If the return setting of the rejection rule is to return to the current approval node, read the keyword fields of the modified approval request and compare them with the keyword field snapshot value. If the comparison is consistent, return to the current approval node; if the comparison is inconsistent, directly submit the modified approval request to the next point of the target node.

[0030] Before step S101 of this embodiment, it also includes: the keyword field definition and configuration process. Specifically, it includes: In the process model defined in the workflow, add the attribute of "keyword field". In the process configuration interface, users can set which fields are keyword fields according to actual needs, such as "application amount"; it should be noted that users can modify the "keyword field" at any time and customize it.

[0031] It can be understood that in some other implementation manners, the system can also actively identify the "specific fields" preset in the resource library. Once a field matching the "specific fields" is identified in the document of the approval request, it is directly used as the "specific field" or pushed to the user for selection.

[0032] In step S101 of this embodiment, specifically, it includes: When a document is rejected at a current approval node (such as the financial approval node) (at this time, this approval node is the rejection node), the system first reads the rejection rule on the current approval node (financial approval node) in the process. If "return to this node" (that is, return to the rejection node, which is also the aforementioned current approval node) is enabled in the return setting of the rejection rule, the original rejection node information is recorded, and the document is returned to the target node (the default rejection node or the target node manually selected by the approver); meanwhile, the configuration data of the "key fields" attribute in the workflow definition is read, and snapshots of the values of each key field at the current time period are recorded based on this configuration.

[0033] In step S102 of this embodiment, specifically, it includes: When the person being rejected has finished modifying and resubmits, first obtain the rejection rule of the original rejection node. If the return setting is "sequential transfer", it is directly submitted to the next node in the flowchart.

[0034] In step S103 of this embodiment, specifically, it includes: If the return setting is "return to this node", then re-evaluate the transfer method after resubmission, read the configuration of the "key fields" attribute in the workflow definition, and parse the modified values of each key field based on this configuration. Then, compare the modified values of each key field with the snapshot of the key field values before modification recorded at the time of rejection. The comparison process is as follows: If a key field is modified, the attribute of "return to this node" on the original rejection node becomes invalid, and it is submitted to the next node in the flowchart; if the key field is not modified, based on the attribute of "return to this node" on the original rejection node, the system directly jumps to the original rejection node to continue the approval process when submitting.

[0035] More specifically, this embodiment proposes a precise comparison strategy for multi-version snapshots, which is as follows: S1031: Use the latest intermediate snapshot recorded at the time of rejection as the benchmark snapshot, where is the index of the last intermediate snapshot before rejection; S1032: Read the values of the key fields of the modified approval request to obtain the current value set , where , and are the values of the modified key fields , and ; S1033: For each key field , compare the modified value with the corresponding value in the benchmark snapshot ; Define a comparison function , when , , it means that this field has not been modified; when , , it means that this field has been modified; S1034: Statistically compare the results of all key fields and calculate the number of modified fields ; S1035: If , that is, there is a key field that has been modified, then the attribute of "return to this node" on the original rejection node becomes invalid, and the system submits to the next node in the flowchart; if , that is, all key fields have not been modified, then based on the attribute of "return to this node" on the original rejection node, the system directly jumps to the original rejection node to continue the approval process when submitting.

[0036] It can be understood that in some other implementation methods, when the approval request first enters the approval process, the system automatically records the initial snapshot of the approval request. The initial snapshot includes the initial values of all key fields and the recording timestamp; at each key node (such as the approval node, rejection node, etc.) in the approval process, the system automatically records the snapshot of the current approval request. The intermediate snapshot also includes the current values of the key fields and the recording timestamp; in order to reduce the use of storage space, an incremental storage method can be used to record the snapshot, that is, only store the modified part of each version snapshot relative to the previous version snapshot, rather than storing the entire snapshot data. By incrementally storing all snapshots, it is possible to better trace the modifications while ensuring a relatively small storage footprint.

[0037] It can be understood that in some other implementation methods, when the number of key fields is greater than the set threshold, a parallel comparison method can be used to divide the key fields into multiple subsets, and perform comparisons on different threads or processors respectively, and finally summarize the comparison results.

[0038] Calculate the hash value for the value of each key field, and determine whether the field has been modified by comparing the hash values. Hash comparison can quickly determine whether the field value has changed, reducing the time overhead of directly comparing data. More specifically, it includes:[[]] Calculate the hash value and , define the hash comparison function ; When , , it means that this field may not have been modified; When , , indicating that the field has been modified. For the case of hash collision, further data comparison and confirmation are performed.

[0039] In summary, by introducing the intelligent monitoring of key fields and the forced re-review mechanism, the present invention significantly improves the rigor and efficiency of enterprise process approval, effectively reduces the risks caused by un-reviewed changes of key information, and enhances the accuracy and consistency of data at the same time.

[0040] Based on the above method, Figure 2 Fig. shows a process approval system based on field version snapshot comparison provided by an exemplary embodiment of the present invention, including: A data reading unit 201, configured to: when an approval request is rejected at the current approval node, read the rejection rule of the current approval node and the keyword field snapshot value in the currently rejected approval request, and return the approval request to the target node; A first judgment unit 202, configured to: when the modified approval request is resubmitted from the target node, obtain the rejection rule, and if the return setting of the rejection rule is sequential flow, directly submit the modified approval request to the next point of the target node; A second judgment unit 203, configured to: if the return setting of the rejection rule is to return to the current approval node, read the keyword fields of the modified approval request and compare them with the keyword field snapshot value. If the comparison is consistent, return to the current approval node; if the comparison is inconsistent, directly submit the modified approval request to the next point of the target node.

[0041] It can be understood that the above-mentioned units can be separately or all combined into one or several other units to form, or some of them can be further split into multiple smaller units with functional division to form, which can achieve the same operation without affecting the implementation of the technical effects of the embodiments of the present application. The above units are divided based on logical functions. In actual applications, the function of one unit can also be realized by multiple units, or the functions of multiple units can be realized by one unit. In other embodiments of the present application, the system may also include other units. In actual applications, these functions can also be assisted by other units and can be realized by the cooperation of multiple units.

[0042] According to another embodiment of the present application, the system described in this embodiment can be constructed, and the approval method of the present application can be implemented by running a computer program (including program code) capable of executing the respective steps involved in the corresponding method described in Embodiment 1 on a general computing device such as a computer including processing elements and storage elements such as a Central Processing Unit (CPU), a Random Access Memory (RAM), and a Read-Only Memory (ROM). The computer program can be recorded on a computer-readable recording medium, for example, and loaded into the above computing device through the computer-readable recording medium and run therein.

[0043] Based on the above method, Figure 3 FIG. shows a process approval system based on field version snapshot comparison provided by an exemplary embodiment of the present invention, including: A process definition module 301, configured to: Provide a process designer for graphical modeling, support the definition and configuration of key fields, and users can set which fields are key fields on the process configuration interface, such as "application amount"; Set rejection rules in the attribute list of the approval activity, including the default rejection node, whether to allow the approver to select the target node, the optional range of the target node, and the return setting (sequential transfer or return to this node); The rejection rule includes the following configuration items: (1) The default rejection node; (2) Whether to allow the approver to select the target node; (3) The optional range of the target node; (4) Return setting: sequential transfer, return to this node; a) Sequential transfer: Re-transfer according to the path defined by the process; b) Return to this node: When resubmitting after modification, usually directly jump back to the original rejection node to continue the approval process.

[0044] A snapshot management module 302, configured to: A field version memory based on a time stamp, used to save the field snapshots before and after modification, and these snapshots are used for subsequent comparison and analysis.

[0045] A dynamic routing engine 303, configured to: Dynamically calculate the process path according to the snapshot version comparison result and the return setting of the original rejection node; if "return to this node" is enabled and the key field is modified, submit it to the next node for sequential transfer; otherwise, jump back to the original rejection node or transfer sequentially according to the return setting. The specific process is as follows: If "return to this node" is enabled; If the key field is modified, submit it to the next node and flow in sequence; otherwise, jump back to the original rejection node. If "return to this node" is not enabled, submit it to the next node and flow in sequence.

[0046] Figure 4 An electronic device provided by an exemplary embodiment of the present invention is shown. The electronic device includes a processor 401, a communication interface 402, and a computer-readable storage medium 403. Among them, the processor 401, the communication interface 402, and the computer-readable storage medium 403 can be connected through a bus or other means.

[0047] Among them, the communication interface 402 is used to receive and send data. The computer-readable storage medium 403 can be stored in the memory of the electronic device. The computer-readable storage medium 403 is used to store a computer program. The computer program includes program instructions. The processor 401 is used to execute the program instructions stored in the computer-readable storage medium 403.

[0048] The processor 401 is the computing core and control core of the electronic device. It is adapted to implement one or more instructions, and is specifically adapted to load and execute one or more instructions to implement the corresponding method flow or corresponding function.

[0049] The processor 401 is configured to execute the following process: When the approval request is rejected at the current approval node, read the rejection rule of the current approval node and the snapshot value of the key field in the currently rejected approval request, and return the approval request to the target node. When the modified approval request is resubmitted from the target node, obtain the rejection rule. If the return setting of the rejection rule is sequential flow, directly submit the modified approval request to the next point of the target node. If the return setting of the rejection rule is to return to the current approval node, read the key field of the modified approval request and compare it with the snapshot value of the key field. If the comparison is consistent, return to the current approval node; if the comparison is inconsistent, directly submit the modified approval request to the next point of the target node.

[0050] Those of ordinary skill in the art can realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed in the present application, they can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but this implementation should not be considered to exceed the scope of the present application.

[0051] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted through a computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (e.g., coaxial cable, optical fiber, digital line) or a wireless manner (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data processing device such as a server or a data center that includes one or more integrated available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0052] The foregoing are only the preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A process approval method based on field version snapshot comparison, characterized in that It includes the following processes: When the approval request is rejected at the current approval node, read the rejection rule of the current approval node and the keyword field snapshot value in the currently rejected approval request, and return the approval request to the target node; When the modified approval request is resubmitted from the target node, obtain the rejection rule. If the return setting of the rejection rule is sequential transfer, directly submit the modified approval request to the next point of the target node; If the return setting of the rejection rule is to return to the current approval node, read the keyword fields of the modified approval request and compare them with the keyword field snapshot value. If the comparison is consistent, return to the current approval node; if the comparison is inconsistent, directly submit the modified approval request to the next point of the target node.

2. The process approval method based on field version snapshot comparison according to claim 1, wherein The keyword fields are fields pre-configured in the approval workflow, and the target node is the default rejection node or the target node selected by the approver of the current approval node.

3. The process approval method based on field version snapshot comparison according to claim 1, wherein If the comparison is consistent and return to the current approval node, it includes: if the keyword fields are not modified, the attribute of returning to this node on the current approval node remains valid, and directly submit the modified approval request to the current approval node.

4. The process approval method based on field version snapshot comparison according to claim 1, wherein If the comparison is inconsistent and directly submit the modified approval request to the next point of the target node, it includes: if the keyword fields are modified, the attribute of returning to this node on the current approval node becomes invalid, and directly submit the modified approval request to the next point of the target node.

5. The process approval method based on field version snapshot comparison according to claim 1, wherein After reading the rejection rule of the current approval node, if the return setting of the rejection rule is to return to the current approval node, record the information of the current approval node for the return of the modified approval request.

6. The process approval method based on field version snapshot comparison according to any one of claims 1-5, wherein Using the latest intermediate snapshot recorded at the time of rejection as the reference snapshot, where is the index of the last intermediate snapshot before rejection; Read the keyword field values of the modified approval request to obtain the current value set , where , and are the values of the modified keyword fields , and ; For each key field , compare the modified value with the corresponding value in the baseline snapshot ; Define a comparison function When then it means that this field has not been modified; when then it means that this field has been modified; Count the comparison results of all key fields and calculate the number of modified fields ; If , that is, if there is a modification to the key field, the attribute of the current approval node that returns to this node becomes invalid, and it is submitted to the next node in the process; If , that is, if all key fields have not been modified, then based on the attributes of returning to this node on the current approval node, directly jump to the current approval node to continue the approval process.

7. The process approval method based on field version snapshot comparison according to any one of claims 1-5, wherein When the number of keyword fields is greater than the set threshold, adopt a parallel comparison method, divide the keyword fields into multiple subsets, perform comparisons on different threads or processors respectively, and finally summarize the comparison results.

8. A process approval system based on field version snapshot comparison, characterized in that, It includes: A data reading unit, configured to: when the approval request is rejected at the current approval node, read the rejection rule of the current approval node and the keyword field snapshot value in the currently rejected approval request, and return the approval request to the target node; A first judgment unit, configured to: when the modified approval request is resubmitted from the target node, obtain the rejection rule. If the return setting of the rejection rule is sequential transfer, directly submit the modified approval request to the next point of the target node; The second judgment unit is configured to: if the return setting of the rejection rule is set to return the current approval node, read the keyword fields of the modified approval request and compare them with the keyword field snapshot values. If the comparison is consistent, return the current approval node; if the comparison is inconsistent, directly submit the modified approval request to the next point of the target node.

9. A process approval system based on field version snapshot comparison, characterized in that, It includes: A process definition module, configured to: perform keyword field definition and configuration, and set the rejection rule; A snapshot management module, configured to: save the field snapshots before and after the modification of the approval request; A dynamic routing engine, configured to: execute the process approval method based on field version snapshot comparison according to any one of claims 1-7.

10. A computer device, characterized in that, It includes: A processor and a computer-readable storage medium; The processor is adapted to execute a computer program; The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, it implements the process approval method based on field version snapshot comparison according to any one of claims 1 to 7.

Images