Process approval method and system based on field version snapshot comparison

Abstract

The present invention belongs to the field of data processing technology. A process approval method and system based on field version snapshot comparison is provided. When an approval request is rejected at the current approval node, the rejection rule of the current approval node and the key field snapshot value in the currently rejected approval request are read, and the approval request is returned to the target node; when the modified approval request is resubmitted from the target node, the rejection rule is obtained. If the return setting of the rejection rule is sequential flow, the modified approval request is directly submitted to the next point of the target node; if the return setting of the rejection rule is to return to the current approval node, the key field of the modified approval request is read and compared with the key field snapshot value. 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; thereby enhancing the accuracy and consistency of the data.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, 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 method is that after a document is rejected by a certain approval node and requires modification, when it is resubmitted after the modification is completed, it needs to be re-examined from the rejected node according to the flowchart. For example, if a process containing four nodes A→B→C→D is rejected from node D to node A, after node A is modified and resubmitted, nodes B, C, and D need to be re-examined in sequence.

[0004] To improve process efficiency, the current enterprise process approval system provides two resubmission methods in rejection scenarios: sequential flow, which re-circulates according to the process definition path (such as A→B→C→D); and return to the current node, which directly jumps back to the original rejection node for continued approval. Although this method improves efficiency, there is a risk of not re-approving after modifying key fields (for example, directly skipping subsequent approval nodes after modifying the "application amount").

[0005] In summary, the current automated approval process has the following problems: (1) Imbalance between efficiency and risk. The return-to-this-node mechanism sacrifices the audit integrity of key data changes; (2) The separation of static processes and dynamic data. The process path decision is not dynamically linked to the field modification status; (3) The conflict between formal integrity and substantive effectiveness. Changes to key fields may bypass necessary approval links. Summary of the Invention

[0006] In order to address the shortcomings of the existing technology, 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-examination mechanism after modification of key fields in rejection jump scenarios in existing enterprise process approval systems. It 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] In order to achieve the above object, the present invention adopts the following technical solutions:

[0008] In a first aspect, the present invention provides a process approval method based on field version snapshot comparison.

[0009] A process approval method based on field version snapshot comparison includes the following steps:

[0010] When an approval request is rejected at the current approval node, the rejection rule of the current approval node and the snapshot value of the key field in the rejected approval request are read, and the approval request is returned to the target node;

[0011] When the modified approval request is resubmitted from the target node, the rejection rule is obtained. If the return setting of the rejection rule is sequential flow, the modified approval request is directly submitted to the next point of the target node;

[0012] If the return 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 snapshot values ​​of the key fields. 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.

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

[0014] As a further limitation of the first aspect of the present invention, if the comparison is consistent, returning the current approval node includes:

[0015] If the key field is not modified, the attribute of returning to the current node on the current approval node remains valid, and the modified approval request is directly submitted to the current approval node.

[0016] As a further limitation of the first aspect of the present invention, if the comparison is inconsistent, directly submitting the modified approval request to the next point of the target node includes:

[0017] If the key field is modified, the attribute of returning to the current node on the current approval node becomes invalid, and the modified approval request is directly submitted to the next point of the target node.

[0018] 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 of the rejection rule is set to return to the current approval node, the information of the current approval node is recorded for use in returning the modified approval request.

[0019] As a further limitation of the first aspect of the present invention, the latest intermediate snapshot recorded at the time of rejection As a baseline snapshot, where The index of the last intermediate snapshot before rejection;

[0020] Read the modified key field values ​​of the approval request and get the current value set ,in 、 and Modified key fields 、 and The value of

[0021] For each key field , the modified value With the benchmark snapshot The corresponding value in Make a comparison;

[0022] Define the comparison function ,when hour, , indicating that the field has not been modified; when hour, , indicating that the field has been modified;

[0023] Count the comparison results of all key fields and calculate the number of modified fields ;

[0024] if , that is, if a key field is modified, the attribute of returning to this node of the current approval node becomes invalid and is submitted to the next node in the process;

[0025] if , that is, all key fields have not been modified, then the attribute of returning to this node on the current approval node shall prevail, and the process shall be directly jumped to the current approval node to continue the approval process.

[0026] 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 to divide the key fields into multiple subsets, which are compared on different threads or processors respectively, and finally the comparison results are summarized.

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

[0028] A process approval system based on field version snapshot comparison, including:

[0029] The data reading unit is configured to: when an approval request is rejected at a 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;

[0030] The first judgment unit is 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;

[0031] The second judgment unit is configured to: 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.

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

[0033] A process approval system based on field version snapshot comparison, including:

[0034] The process definition module is configured to: define and configure key fields and set rejection rules;

[0035] The snapshot management module is configured to: save snapshots of fields before and after modification of the approval request;

[0036] The dynamic routing engine is configured to: execute the process approval method based on field version snapshot comparison described in the first aspect of the present invention.

[0037] In a fourth aspect, the present invention provides a computer device comprising: a processor and a computer-readable storage medium;

[0038] a processor adapted to execute a computer program;

[0039] A computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the process approval method based on field version snapshot comparison as described in the first aspect of the present invention is implemented.

[0040] Compared with the prior art, the present invention has the following beneficial effects:

[0041] 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 sequential flow, the modified approval request is directly submitted to the next point of the target node. If the return setting of the rejection rule is to return to the current approval node, the key fields of the modified approval request are read and compared with the key field 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. This solves the problems of lack of effective monitoring and forced re-examination mechanism after modification of key fields in the rejection jump scenario in 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 the data.

[0042] 2. The key fields of the present invention are fields pre-configured in the approval workflow. By pre-configuring key fields, it can be ensured that consistent standards are adopted for those fields that are important and require special attention throughout the approval workflow. This helps to reduce approval differences or errors caused by inconsistent understanding of the importance of fields by different approvers or different approval links; 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 flexible configuration of the approval process.

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

[0044] 4. The present invention innovatively proposes a process approval method based on field version snapshot comparison. If the key field is modified, the attribute of returning to the current node on the current approval node becomes invalid, and the modified approval request is directly submitted to the next point of the target node. This ensures that when these key information is modified, the approval process can adapt to such dynamic changes, no longer returns to the current approval node, but continues to flow to the next node to adapt to the new approval requirements or conditions, avoiding repeated approvals or invalid approvals that may be caused by key field modifications.

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

[0046] The accompanying drawings, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0047] Figure 1 A flowchart of a process approval method based on field version snapshot comparison provided by an exemplary embodiment of the present invention;

[0048] Figure 2 A schematic diagram of a process approval system based on field version snapshot comparison provided by an exemplary embodiment of the present invention;

[0049] Figure 3 A schematic diagram of a process approval system based on field version snapshot comparison provided by another exemplary embodiment of the present invention;

[0050] Figure 4 A schematic diagram of a computer device is provided for an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0051] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0052] It should be noted that the following detailed descriptions are exemplary and 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 skilled in the art to which the present invention belongs.

[0053] This invention proposes a process approval method based on field version snapshot comparison, which aims to solve the problem in existing enterprise process approval systems that there is a lack of effective monitoring and mandatory re-examination mechanism after key fields are modified, resulting in potential risks and data inconsistency in the approval process; through intelligent monitoring means, it ensures that every modification of key fields can be approved and confirmed in a timely manner, thereby maintaining the rigor of process approval and the accuracy of data. Figure 1 As shown, the following process is included:

[0054] S101: When an approval request is rejected at the current approval node, the rejection rule of the current approval node and the snapshot value of the key field in the currently rejected approval request are read, and the approval request is returned to the target node;

[0055] S102: When the modified approval request is resubmitted from the target node, the rejection rule is obtained. If the return setting of the rejection rule is sequential flow, the modified approval request is directly submitted to the next point of the target node;

[0056] S103: If the return setting of the rejection rule is to return to the current approval node, the key fields of the modified approval request are read and compared with the snapshot values ​​of the key fields. 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.

[0057] Before step S101 of this embodiment, the process further includes: a key field definition and configuration process, specifically including:

[0058] In the process model defined by the workflow, add the attribute of "key field". In the process configuration interface, users can set which fields are key fields according to actual needs, such as "application amount". It should be noted that users can customize the modification of "key fields" at any time.

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

[0060] In step S101 of this embodiment, specifically, the following steps are included:

[0061] When a document is rejected at a current approval node (such as the financial approval node) (in this case, this approval node is the rejection node), the system first reads the rejection rule on the current approval node (the financial approval node) in the process. If "Return to Current Node" is enabled in the return setting of the rejection rule (i.e., return to the rejection node, which is also the current approval node mentioned above), the system records the original rejection node information and returns the document to the target node (the default rejection node or the target node manually selected by the approver). At the same time, the system reads the configuration data of the "Key Fields" attribute in the workflow definition and, based on this configuration, records a snapshot of the key field values ​​for the current time period.

[0062] In step S102 of this embodiment, specifically, the following steps are included:

[0063] When the person whose application is rejected finishes the modification and resubmits, the rejection rule of the original rejection node is obtained first. If the return setting is "sequential flow", it is directly submitted to the next node in the flowchart.

[0064] In step S103 of this embodiment, specifically, the following steps are included:

[0065] If the return setting is "Return to this node", the flow method after the resubmission will be re-evaluated, the configuration of the "Key Field" attribute in the workflow definition will be read, and the modified key field values ​​will be parsed based on this configuration. The modified key field values ​​will then be compared with the snapshot of the key field values ​​before the modification recorded at the time of rejection. The comparison process is as follows:

[0066] If the key field is modified, the "Return to this node" attribute on the original rejection node will become invalid and the application will be submitted to the next node in the flowchart. If the key field is not modified, the "Return to this node" attribute on the original rejection node will prevail, and the system will directly jump to the original rejection node to continue the approval process when submitting.

[0067] More specifically, this embodiment proposes a precise comparison strategy for multi-version snapshots, as follows:

[0068] S1031: The latest intermediate snapshot recorded at the time of rejection As a baseline snapshot, where The index of the last intermediate snapshot before rejection;

[0069] S1032: Read the modified key field values ​​of the approval request and obtain the current value set ,in 、 and Modified key fields 、 and The value of

[0070] S1033: For each key field , the modified value With the benchmark snapshot The corresponding value in Make a comparison;

[0071] Define the comparison function ,when hour, , indicating that the field has not been modified; when hour, , indicating that the field has been modified;

[0072] S1034: Count the comparison results of all key fields and calculate the number of modified fields ;

[0073] S1035: If , that is, if a key field is modified, the "return to this node" attribute 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, the "Return to this node" attribute on the original rejection node shall prevail, and the system will directly jump to the original rejection node to continue the approval process when submitted.

[0074] It is understandable that in some other implementations, when an approval request first enters the approval process, the system automatically records the initial snapshot of the approval request, which includes the initial values ​​of all key fields and the recording timestamp. At each key node in the approval process (such as the approval node, the rejection node, etc.), the system automatically records a snapshot of the current approval request. Intermediate snapshots also include the current values ​​of key fields and the recording timestamp. To reduce storage space usage, snapshots can be recorded using incremental storage, that is, only the modified parts of each version snapshot relative to the previous version snapshot are stored, rather than the entire snapshot data. By incrementally storing all snapshots, modifications can be better traced while ensuring a smaller storage footprint.

[0075] It is understandable that in some other implementations, when the number of key fields is greater than a set threshold, a parallel comparison method can be used to divide the key fields into multiple subsets, which are compared on different threads or processors, and finally the comparison results are summarized.

[0076] Calculate a hash value for each key field value and compare the hash value to determine whether the field has been modified. Hash comparison can quickly determine whether the field value has changed, reducing the time overhead of directly comparing data. More specifically, it includes:

[0077] Calculating the hash value and , define the hash comparison function ;

[0078] when hour, , indicating that the field may not be modified;

[0079] when hour, , indicating that the field has been modified. In the case of hash conflicts, further data comparison and confirmation is performed.

[0080] In summary, the present invention significantly improves the rigor and efficiency of enterprise process approval by introducing intelligent monitoring of key fields and a mandatory review mechanism, effectively reduces the risks caused by unreviewed changes to key information, and enhances the accuracy and consistency of data.

[0081] Based on the above method, Figure 2 A process approval system based on field version snapshot comparison provided by an exemplary embodiment of the present invention is shown, including:

[0082] The data reading unit 201 is configured to: when an 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;

[0083] The first judgment unit 202 is 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;

[0084] The second judgment unit 203 is configured to: 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 key 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.

[0085] It is understandable that each of the above-mentioned units can be separately or completely combined into one or several other units to constitute, or one (or some) of the units can be further divided into multiple functionally smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In actual applications, the functions of one unit can also be implemented by multiple units, or the functions of multiple units can be implemented 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 implemented with the assistance of other units, and can be implemented by the collaboration of multiple units.

[0086] According to another embodiment of the present application, the system described in this embodiment and the approval method of the present application can be constructed by running a computer program (including program code) capable of executing the steps involved in the corresponding method described in Example 1 on a general-purpose computing device such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM). The computer program can be recorded on, for example, a computer-readable recording medium, and loaded into the above-mentioned computing device through the computer-readable recording medium and run therein.

[0087] Based on the above method, Figure 3 A process approval system based on field version snapshot comparison provided by an exemplary embodiment of the present invention is shown, including:

[0088] The process definition module 301 is configured as follows:

[0089] Provides a graphical modeling process designer that supports the definition and configuration of key fields. Users can set which fields are key fields on the process configuration interface, such as "application amount";

[0090] Set rejection rules in the property list of the approval activity, including the default rejection node, whether the approver is allowed to select the target node, the target node selection range, and the return setting (sequential flow or return to the current node);

[0091] The rejection rule includes the following configuration items:

[0092] (1) Default rejection node;

[0093] (2) Whether the approver is allowed to select the target node;

[0094] (3) Target node selection range;

[0095] (4) Return settings: sequential flow, return to this node; a) Sequential flow: re-flow according to the path defined by the process; b) Return to this node: when the modification is completed and resubmitted, it usually jumps directly back to the original rejection node to continue the approval process.

[0096] The snapshot management module 302 is configured to:

[0097] The timestamp-based field version storage is used to save snapshots of fields before and after modification. These snapshots are used for subsequent comparison and analysis.

[0098] The dynamic routing engine 303 is configured to:

[0099] The process path is dynamically calculated based on the snapshot version comparison results and the return settings of the original rejected node. If "Return to this node" is enabled and the key field is modified, it is submitted to the next node and flows in sequence. Otherwise, it jumps back to the original rejected node or flows in sequence according to the return settings. The specific process is as follows:

[0100] If "Return to this node" is enabled;

[0101] If the key field is modified, it is submitted to the next node and flows in sequence. Otherwise, it jumps back to the original rejection node.

[0102] If "Return to current node" is not enabled, the request will be submitted to the next node and flowed sequentially.

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

[0104] 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 computer programs, the computer programs include program instructions, and the processor 401 is used to execute the program instructions stored in the computer-readable storage medium 403.

[0105] The processor 401 is the computing core and control core of the electronic device, which is suitable for implementing one or more instructions, and is specifically suitable for loading and executing one or more instructions to implement corresponding method processes or corresponding functions.

[0106] The processor 401 is configured to perform the following process:

[0107] When an approval request is rejected at the current approval node, the rejection rule of the current approval node and the snapshot value of the key field in the rejected approval request are read, and the approval request is returned to the target node;

[0108] When the modified approval request is resubmitted from the target node, the rejection rule is obtained. If the return setting of the rejection rule is sequential flow, the modified approval request is directly submitted to the next point of the target node;

[0109] If the return 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 snapshot values ​​of the key fields. 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.

[0110] Those skilled in the art will appreciate that the units and algorithmic steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technical personnel may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0111] The above embodiments can be implemented in whole or in part using software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. A computer program product comprises 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 device. The computer instructions can be stored in a computer-readable storage medium or transmitted via 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 via wired (e.g., coaxial cable, optical fiber, digital line) or wireless (e.g., infrared, wireless, microwave, etc.) means. 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 data center that integrates one or more available media. Available media can include magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives).

[0112] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A process approval method based on field version snapshot comparison, characterized in that: The following processes are included: When an approval request is rejected at the current approval node, the rejection rule of the current approval node and the snapshot value of the key field in the rejected approval request are read, and the approval request is returned to the target node; When the modified approval request is resubmitted from the target node, the rejection rule is obtained. If the return setting of the rejection rule is sequential flow, the modified approval request is directly submitted to the next point of the target node; If the return of the rejection rule is set to return to the current approval node, the key field of the modified approval request is read and compared with the snapshot value of the key field. 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. The key field supports custom configuration or supports active recognition of specific fields preset in the resource library as key fields; The intermediate snapshot contains the current value of the key field and the record timestamp. The snapshot is recorded in an incremental storage manner, and only the modified part of each version snapshot relative to the previous version snapshot is stored. The latest intermediate snapshot recorded at the time of rejection As a baseline snapshot, where The index of the last intermediate snapshot before rejection; Read the modified key field values ​​of the approval request and get the current value set ,in 、 and Modified key fields 、 and The value of For each key field , the modified value With the benchmark snapshot The corresponding value in Make a comparison; Define the comparison function ,when hour, , indicating that the field has not been modified; when hour, , indicating that the field has been modified; Count the comparison results of all key fields and calculate the number of modified fields ; if , that is, if a key field is modified, the attribute of returning to this node of the current approval node becomes invalid and is submitted to the next node in the process; if , that is, all key fields have not been modified, then the attribute of returning to this node on the current approval node shall prevail, and the process will be directly jumped to the current approval node to continue the approval process; When the number of key fields exceeds the set threshold, a parallel comparison method is used to divide the key fields into multiple subsets, which are then compared on different threads or processors, and the comparison results are finally summarized. Calculate the hash value for each key field value and compare the hash value to determine whether the field has been modified: Calculating the hash value and , define the hash comparison function ; when hour, , indicating that the field may not be modified; when hour, , indicating that the field has been modified. In the case of hash conflicts, further data comparison and confirmation is performed.

2. The process approval method based on field version snapshot comparison according to claim 1 is characterized in that: The key field is a field pre-configured in the approval workflow, and the target node is a default rejection node or a 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 is characterized in that: If the comparison is consistent, the current approval node is returned, including: if the key field is not modified, the attribute of returning to this node on the current approval node remains valid, and the modified approval request is directly submitted to the current approval node.

4. The process approval method based on field version snapshot comparison according to claim 1 is characterized in that: If the comparison is inconsistent, the modified approval request is directly submitted to the next point of the target node, including: if the key field is modified, the attribute of returning to the current node on the current approval node is invalid, and the modified approval request is directly submitted to the next point of the target node.

5. The process approval method based on field version snapshot comparison according to claim 1 is characterized in that: After reading the rejection rule of the current approval node, if the return of the rejection rule is set to return to the current approval node, the information of the current approval node is recorded for use in returning the modified approval request.

6. A process approval system based on field version snapshot comparison, adopting the process approval method based on field version snapshot comparison according to any one of claims 1 to 5, characterized in that: include: The data reading unit is configured to: when an approval request is rejected at a 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; The first judgment unit is 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; The second judgment unit is configured to: 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.

7. A process approval system based on field version snapshot comparison, characterized in that: include: The process definition module is configured to: define and configure key fields and set rejection rules; The snapshot management module is configured to: save snapshots of fields before and after modification of the approval request; The dynamic routing engine is configured to: execute the process approval method based on field version snapshot comparison according to any one of claims 1 to 5.

8. A computer device, characterized in that: include: a processor and a computer-readable storage medium; a processor adapted to execute a computer program; A computer-readable storage medium having a computer program stored therein, wherein when the computer program is executed by the processor, the process approval method based on field version snapshot comparison according to any one of claims 1 to 5 is implemented.

Images