CN106327140B - Method and device for monitoring data modification - Google Patents
Method and device for monitoring data modification Download PDFInfo
- Publication number
- CN106327140B CN106327140B CN201510358754.9A CN201510358754A CN106327140B CN 106327140 B CN106327140 B CN 106327140B CN 201510358754 A CN201510358754 A CN 201510358754A CN 106327140 B CN106327140 B CN 106327140B
- Authority
- CN
- China
- Prior art keywords
- audit
- data block
- task
- auditing
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Testing And Monitoring For Control Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
the embodiment of the invention discloses a method and a device for monitoring data modification, which are used for acquiring a process task and a corresponding task identifier, and judging whether a historical audit record of the process task is stored or not according to the task identifier; if yes, determining that the process task is the process task which is submitted for the Nth time, obtaining the corresponding relation among the data content, the auditing result and the user identification of the audited data block of the process task in the auditing process of submitting the audit for the Nth-1 th time according to the historical auditing record, determining the same data block in the process tasks which are submitted for the Nth time and the audited for the Nth-1 th time, and comparing whether the data content is the same; if the data blocks are the same, in the Nth audit of the process task, the corresponding audit result is given to the same data blocks on the name of the corresponding user identifier, so that when the process task is submitted to the audit again, the unmodified data blocks are not required to be sent to the user for audit again, and the audit efficiency of the audit again is improved.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a method and an apparatus for monitoring data modification.
background
In the process of auditing the flow tasks, the data of the flow tasks can be divided into one or more data blocks, and the data blocks are audited by corresponding users to determine whether the data blocks meet the requirements. If a flow task comprises a plurality of data blocks, if one data block meets the auditing requirement, the data block is approved, but if any data block in the task flow does not meet the auditing requirement, the whole flow task is rejected and returned to the initiator of the flow task. The initiator can modify the data blocks which do not meet the auditing requirement, and submit the modified flow tasks for auditing again.
When the modified flow task is reviewed again, the conventional method is to divide each data block of the flow task into corresponding users for reviewing again, and since the initiator may only modify a part of the data blocks in the flow task under a general condition, the data blocks which are not modified in the flow task also need to be reviewed again by the users in the reviewing process, thereby wasting time and slowing down the overall reviewing speed, and causing low efficiency of reviewing again.
disclosure of Invention
In order to solve the technical problem, the invention provides a method and a device for monitoring data modification, so that when a flow task is re-audited, an audit result of the previous audit is given to an unmodified data block in the flow task, and the efficiency of the re-audit is improved.
The embodiment of the invention discloses the following technical scheme:
a method of monitoring data modifications, the method comprising:
Acquiring a flow task and a corresponding task identifier, wherein the flow task comprises at least one data block;
Judging whether historical audit records of the process tasks are saved or not according to the task identifiers;
If yes, determining that the process task is the process task which submits the audit for the Nth time, and obtaining the corresponding relation among the data content, the audit result and the user identification of the audited data block of the process task in the audit process of submitting the audit for the Nth-1 th time according to the historical audit record, wherein the user identification is used for identifying the user who makes the audit result on the data block, and N is an integer more than or equal to 2;
determining the same data block in the flow task submitted for the Nth time and the flow task submitted for the (N-1) th time according to the data block identifier of the audited data block, and comparing whether the data content of the same data block is the same or not;
If the data blocks are the same, acquiring corresponding auditing results and user identifications from the corresponding relation of the historical auditing records according to the data block identifications of the audited data blocks, and endowing the same data blocks with the corresponding auditing results on the name of the corresponding user identifications in the Nth auditing of the process task.
Optionally, the determining, according to the data block identifier of the audited data block, that the same data block is in the flow task that submits the audit for the nth time and the flow task that submits the audit for the (N-1) th time, and comparing whether the data content of the same data block is the same, further includes:
if not, determining a checking user or a checking user group for checking the same data block in the Nth checking process of the process task according to the checking setting of the process task and the data block identifier of the checked data block;
And sending the same data block to the auditing user or the auditing user group for auditing.
optionally, in the process of checking the process task N-1 times, if the checking result of the first data block included in the process task is that the checking is not passed, in the process of submitting the process task N times, the same data block in the process task submitting the checking N times and the process task submitting the checking N-1 times is determined according to the data block identifier of the checked data block, and the comparison result is compared to determine whether the data content of the same data block is the same, including:
if the comparison results of the data contents of the first data block in the N-1 th audit and the nth audit are the same, acquiring a corresponding audit result and a user identifier from the corresponding relation of the historical audit record according to the data block identifier of the audited data block, and in the nth audit of the process task, giving the corresponding audit result to the same data block on the name of the corresponding user identifier, including:
Acquiring an auditing result of the first data block corresponding to the data content of the first data block and a first user identifier from the corresponding relation in the historical auditing record according to the data block identifier of the first data block;
And assigning an audit result that the audit is not passed to the first data block on the name of the first user identification.
optionally, in the process of checking the process task N-1 times, if the result of checking the second data block included in the process task passes the checking, in the process of submitting the process task N times, determining the same data block in the process task submitting the checking N times and the process task submitting the checking N-1 times according to the data block identifier of the checked data block, and comparing whether the data content of the same data block is the same includes:
if the comparison result of the data content of the second data block in the (N-1) th audit and the Nth audit is different, the process task is determined to be an audit user or an audit user group for auditing the same data block in the Nth audit process of the process task according to the audit setting of the process task and the data block identifier of the audited data block, and the process comprises the following steps:
And determining an auditing user or an auditing user group for auditing the second data block according to the auditing setting of the process task and the data block identifier of the second data block.
optionally, before the acquiring the flow task and the corresponding task identifier, the method further includes:
And when the (N-1) th audit of the process task is failed, updating the corresponding relation of the data content, the audit result and the user identification of the audited data block of the process task in the (N-1) th audit process into the historical audit record in a covering manner.
optionally, if the result of the examination of the nth examination of the process task is that the examination does not pass, the method further includes:
and updating the corresponding relation among the data content of the audited data block, the audit result and the user identifier of the process task in the nth audit process into the historical audit record in a covering manner.
a monitoring device for data modification, the device comprising:
The system comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for acquiring a flow task and a corresponding task identifier, and the flow task comprises at least one data block;
the judging unit is used for judging whether the historical audit record of the flow task is stored or not according to the task identifier; if yes, determining the process task as an Nth process task for submitting the audit, and triggering a second obtaining unit;
the second obtaining unit is configured to obtain, according to the historical review record, a corresponding relationship between data content of a reviewed data block, a review result, and a user identifier of the process task in an N-1 th review process of submitting review, where the user identifier is used to identify a user who makes the review result for the data block, and N is an integer greater than or equal to 2;
A comparison unit, configured to determine, according to the data block identifier of the checked data block, that a flow task that submits the check for the nth time is the same as the flow task that submits the check for the (N-1) th time, and compare whether the data contents of the same data block are the same; if the two are the same, triggering an auditing unit;
And the auditing unit is used for acquiring a corresponding auditing result and a corresponding user identifier from the corresponding relation of the historical auditing records according to the data block identifier of the audited data block, and endowing the same data block with the corresponding auditing result on the name of the corresponding user identifier in the Nth auditing of the process task.
Optionally, the method further includes:
A determining unit, configured to determine, according to the audit setting of the process task and the data block identifier of the audited data block, an audit user or an audit user group for auditing the same data block in an nth audit process of the process task if the comparison results of the comparing unit are different;
And the sending unit is used for sending the same data block to the auditing user or the auditing user group for auditing.
optionally, in the N-1 th audit process of the process task, if the audit result of the first data block included in the process task is that the audit is not passed, in the nth submission process of the process task, the method includes:
if the comparison results of the comparison units are the same, the auditing unit is specifically configured to obtain, according to the data block identifier of the first data block, an auditing result of the first data block and a first user identifier, which correspond to the data content of the first data block, from the corresponding relationship in the historical auditing record; and assigning an audit result that the audit is not passed to the first data block on the name of the first user identification.
optionally, in the N-1 th audit process of the process task, if the audit result of the second data block included in the process task is that the audit is passed, in the nth submission process of the process task, the method includes:
If the comparison results of the comparison units are different, the third obtaining unit is specifically configured to obtain, according to the data block identifier of the second data block, a second user identifier corresponding to the data content of the second data block from the corresponding relationship in the historical audit record;
The sending unit is specifically configured to send the second data block to the second user for auditing according to the second user identifier.
Optionally, the method further includes:
and the updating unit is used for updating the corresponding relation among the data content of the audited data block, the audit result and the user identifier of the process task in the process of the (N-1) th audit into the historical audit record in a covering manner before the first obtaining unit is triggered and when the (N-1) th audit of the process task is failed.
optionally, if the result of the nth audit of the process task is that the audit is not passed, the updating unit is further configured to update the historical audit record with the corresponding relationship among the data content of the audited data block of the process task in the nth audit process, the audit result, and the user identifier.
according to the technical scheme, the historical audit record of the process task when the audit is not passed is saved, if the process task is judged to have the historical audit record according to the task identifier corresponding to the obtained process task, the process task can be determined to be a process and a task which are not subjected to the audit submission for the first time, the corresponding relation among the data content, the audit result and the user identifier of the audited data block in the process of the audit submission of the process task for the last time, namely the audit submission for the Nth-1 th time is obtained according to the historical audit record, the same data block in the process task which is subjected to the audit submission for the Nth time and the process task which is subjected to the audit submission for the Nth-1 th time is determined according to the data block identifier of the audited data block, whether the data content of the same data block is identical or not is compared, and when the comparison result is identical, the corresponding data block identifier of the audited data block is obtained from the corresponding relation of And in the Nth audit of the process task, endowing the same data block with the corresponding audit result in the name of the corresponding user identifier. Therefore, when the process task re-submits the audit, the unmodified data blocks discovered by comparing the data contents can be directly endowed with the audit result of the last audit without being sent to the user for auditing again, the audit time is saved, and the audit efficiency of the re-audit is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of a method for monitoring data modification according to an embodiment of the present invention;
Fig. 2 is a flowchart of a method for monitoring data modification according to an embodiment of the present invention;
FIG. 3 is a diagram of a monitoring device for data modification according to an embodiment of the present invention;
fig. 4 is a device structure diagram of a monitoring device for modifying data according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some embodiments, but not all embodiments, of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
When the flow task is rejected, the initiator of the flow task can modify the data blocks which do not meet the auditing requirement, and submit the modified flow task for auditing again. In the conventional review, each data block of the flow task is divided into corresponding users for review, and since an initiator may only modify a part of the data blocks in the flow task under a general condition, the data blocks which are not modified in the flow task also need to be reviewed by the users again in the review process, thereby wasting time and slowing down the overall review speed, and causing low review efficiency.
therefore, the embodiment of the invention provides a method and a device for monitoring data modification, which are used for storing a historical audit record of a process task when the process task is not approved, determining that the process task is a process and a task which are not submitted for the first time if the process task is judged to have the historical audit record according to a task identifier corresponding to the obtained process task, obtaining a corresponding relation among data content, audit results and user identifiers of audited data blocks in the process that the process task is submitted for the last time of audit, namely the audit process is submitted for the (N-1) th time of audit according to the historical audit record, determining the same data blocks in the process task submitted for the (N) th time and the process task submitted for the (N-1) th time of audit according to the data block identifier of the audited data blocks, and comparing whether the data content of the same data blocks is the same or not, and when the comparison result is the same, acquiring a corresponding audit result and a corresponding user identifier from the corresponding relation of the historical audit record according to the data block identifier of the audited data block, and endowing the same data block with the corresponding audit result on the name of the corresponding user identifier in the Nth audit of the process task. Therefore, when the process task re-submits the audit, the unmodified data blocks discovered by comparing the data contents can be directly endowed with the audit result of the last audit without being sent to the user for auditing again, the audit time is saved, and the audit efficiency of the re-audit is improved.
example one
Fig. 1 is a flowchart of a method for monitoring data modification according to an embodiment of the present invention, where the method includes:
S101: the method comprises the steps of obtaining a flow task and a corresponding task identifier, wherein the flow task comprises at least one data block.
for example, the task identifiers correspond to the flow tasks one to one. And even if the flow task does not pass the verification at a certain time and is not returned to the initiator of the flow task, the initiator submits the modified flow task to the verification again after modifying the flow task, and the task identifier of the modified flow task is the same as the task identifier of the flow task before modification. That is to say, even if the same flow task is rejected after being returned for many times, the task identifier of the flow task is not changed when the audit is submitted again after modification, or even when the audit is submitted again without modification.
the data blocks may be understood as pre-sorted data sets, and different data blocks may comprise different types of data sets. For example, flow task 1 may include financial data blocks that may include the finance-related data set of flow task 1 and legal data blocks that may include the legal-related data set of flow task 1. The data in the flow task can even belong to both data block 1 and data block 2. The process task may be divided into different data blocks in different ways according to different requirements, which is not limited by the present invention. Taking the example that the process task 1 may include a financial data block and a legal data block, the financial data block may be sent to a financial staff for review, the legal data block may be sent to a legal staff for review, and the whole process task is rejected and returned to the initiator of the process task 1 if any one data block fails to be reviewed.
S102: and judging whether the historical audit record of the flow task is saved or not according to the task identifier. If yes, go to step S103.
For example, in the embodiment of the present invention, when the process task fails to be audited due to some reason in an auditing process of a time, an auditing record that the process task has completed in the auditing process of the time is saved in a history auditing record, where the history auditing record includes related data of a data block that has been audited.
That is, when a process task is found to have a history of reviews, the process task belongs to a process task that is not the first time a review is submitted. If the historical audit record of the process task is judged not to be stored according to the task identifier, the process task can be confirmed to be a process task for submitting audit for the first time, a data block can be sent to different audit users for audit according to the traditional processing mode of the process task submitted for the first time and the audit setting of the process task, and the specific process is not repeated here.
s103: and determining that the process task is the process task which submits the audit for the Nth time, and acquiring the corresponding relation among the data content, the audit result and the user identification of the audited data block of the process task in the audit process of submitting the audit for the Nth-1 th time according to the historical audit record, wherein the user identification is used for identifying the user who makes the audit result on the data block, and N is an integer more than or equal to 2.
And determining that the process task is a process task which is not submitted for the first time because the process task has a corresponding historical review record. For the historical audit record, optionally, before performing S101, the method further includes:
And when the (N-1) th audit of the process task is failed, updating the corresponding relation of the data content, the audit result and the user identification of the audited data block of the process task in the (N-1) th audit process into the historical audit record in a covering manner.
that is, what is saved in the history audit record is the audit content that was last audited and completed before the audit is not passed. For example, the flow task 2 includes 10 data blocks, and when the first audit is performed, after 4 data blocks, for example, the data blocks 1 to 4, are audited, the audit is not passed when the data block 5 is audited. It should be noted that it is not limited to whether the user reviewing different data blocks is different, for example, the user 1 is reviewing the data blocks 1 and 2, and the user 2 is reviewing the data blocks 3 to 5. The history audit record 2 corresponding to the process task 2 may include five corresponding relationships corresponding to five audited data blocks, which are corresponding relationships 1: the data content and the auditing result of the data block 1 are the user identification of the user 1 and the data block passing; correspondence relationship 2: the data content and the auditing result of the data block 2 are the user identification of the user 1 and the passing; correspondence relationship 3: the data content and the auditing result of the data block 3 are the user identification of the user 2 and the pass; correspondence relationship 4: the data content and the auditing result of the data block 4 are the user identification of the user 2 and the pass; correspondence relationship 5: the data content of the data block 5, the auditing result are failed and the user identification of the user 2.
In the nth review of the process task, it may occur that a data block included in the process task is not reviewed in the N-1 st review of the process task. For such data blocks, the auditing can be executed according to the auditing setting of the process task in the nth auditing of the process task, which is not described in detail herein. In the above example that the flow task 2 includes 10 data blocks, when the first audit is completed, 4 data blocks, such as data blocks 1 to 4, are audited, and then the audit is not passed when the data block 5 is audited. Then, when the process task 2 is reviewed for the second time, as the data blocks 6 to 10 are not recorded in the historical review record 2, processing can be performed according to the review setting of the process task 2, and the data blocks 6 to 10 are distributed to corresponding review users or review user groups for review.
It should also be noted that, in the embodiment of the present invention, the user identified by the user identifier may be an audit user corresponding to an audited process task, or may be an audit user in an audit user group corresponding to an audited process task. For example, the flow task 3 includes a data block a, a data block b, and a data block c, and in the auditing link, the data block a and the data block b are audited by a group of users including a user a, a user b, and a user c. The data block c is audited by user c and user d. It can be understood that, the data block a may be audited by any one of the user a, the user b, and the user c as a representative of the group of users, and an audit result is obtained, if the user a audits the data block a, the audit result of the data block a is passed and the user identified by the user identifier is the user a. The user c can represent the user group of the user a, the user b and the user c to check the data block a or the data block b and obtain a check result respectively, and the user c can also represent the user group of the user c and the user d to check the data block c and obtain a check result.
S104: and determining the same data block in the flow task submitted for the Nth time and the flow task submitted for the (N-1) th time according to the data block identifier of the audited data block, and comparing whether the data content of the same data block is the same. If so, go to step S105.
s105: and acquiring a corresponding audit result and a corresponding user identifier from the corresponding relation of the historical audit record according to the data block identifier of the audited data block, and endowing the same data block with the corresponding audit result on the name of the corresponding user identifier in the Nth audit of the process task.
for example, the data block identifiers of the data blocks correspond to the data blocks one to one. Even if the flow task fails to pass the verification at a certain time and is not returned to the initiator of the flow task, the initiator submits the modified flow task to the verification again after modifying the data content of the data block in the flow task, and the data block identifier of the modified data block is the same as the data block identifier of the data block before modification. That is, even if the same data block in the flow task is modified or not modified for many times in the process of being returned for many times, the data block identifier of the data block will not change when the flow task to which the data block belongs is resubmitted for review.
Continuing with the example of the review process task 2, when the process task 2 is reviewed for the second time, a comparison operation is performed according to the data block identifiers of the five reviewed data blocks recorded in the historical review record 2. Four different alignment situations may occur, and in this embodiment, two of the situations will be described.
For the first case, for example, the data content of the data block 1 in the second audit is the same as that of the data block 1 in the first audit, that is, there is no modification, then the data block 1 in the second audit can be directly given the audit result that the audit is passed on the name of the user 1.
in the first case, the data block that has passed the previous audit and is not modified this time can be directly subjected to the audit result that passed the audit. And the audit does not need to be carried out again, so that the time for the second audit is saved.
For the second case, for example, the data content of the data block 5 in the second audit is the same as that of the data block 5 in the first audit, that is, there is no modification, then the data block 5 in the second audit can be directly given an audit result that the audit fails on behalf of the user 2.
in the second case, it can be quickly found that the initiator of the flow task 2 does not perform any adaptive modification on the data block 5 with the problem in the last audit, so that the data block 5 is directly given an audit result that the audit does not pass, and a process of re-auditing the data block 5 is omitted. Therefore, the process task 2 does not need to be continuously checked for the second time, and the process task 2 is returned to the initiator of the process task due to the failure of the second check. The auditing efficiency of the second auditing is improved.
It should be noted that, even in the case that the flow task includes only one data block, if the N-1 th audit of the flow task fails, when the N-th audit finds that the initiator does not modify the only one data block of the flow task through comparison, it may be directly determined that the N-th audit of the flow task fails, so that the process of sending the only one data block to the user for re-audit is omitted, and the efficiency of re-audit is improved.
To sum up, a history audit record of the process task when the audit is not passed is saved, if the process task is judged to have the history audit record according to the task identifier corresponding to the obtained process task, the process task can be determined to be a process and a task which are not subjected to the audit submission for the first time, the corresponding relation of the data content, the audit result and the user identifier of the audited data block in the audit process of the process task which is subjected to the audit submission for the last time, namely the audit submission for the (N-1) time is obtained according to the history audit record, the same data block in the process task which is subjected to the audit submission for the Nth time and the process task which is subjected to the audit submission for the (N-1) time is determined according to the data block identifier of the audited data block, whether the data content of the same data block is the same or not is compared, and when the comparison result is the same, the corresponding audit result and the user identifier of the audited data block are And marking, in the Nth audit of the process task, the corresponding audit result is given to the same data block on the name of the corresponding user mark. Therefore, when the process task re-submits the audit, the unmodified data blocks discovered by comparing the data contents can be directly endowed with the audit result of the last audit without being sent to the user for auditing again, the audit time is saved, and the audit efficiency of the re-audit is improved.
Example two
In the embodiment S104 shown in fig. 1, except that the same alignment result may be present, alignment results with different alignments may also be present.
On the basis of the embodiment corresponding to fig. 1, fig. 2 is a flowchart of a method for monitoring data modification according to an embodiment of the present invention, where the method includes:
S201: the method comprises the steps of obtaining a flow task and a corresponding task identifier, wherein the flow task comprises at least one data block.
S202: and judging whether the historical audit record of the flow task is saved or not according to the task identifier. If yes, go to step S203.
S203: and determining that the process task is the process task which submits the audit for the Nth time, and acquiring the corresponding relation among the data content, the audit result and the user identification of the audited data block of the process task in the audit process of submitting the audit for the Nth-1 th time according to the historical audit record, wherein the user identification is used for identifying the user who makes the audit result on the data block, and N is an integer more than or equal to 2.
s204: and determining the same data block in the flow task submitted for the Nth time and the flow task submitted for the (N-1) th time according to the data block identifier of the audited data block, and comparing whether the data content of the same data block is the same. If so, go to S205. If not, go to step S206.
s205: and acquiring a corresponding audit result and a corresponding user identifier from the corresponding relation of the historical audit record according to the data block identifier of the audited data block, and endowing the same data block with the corresponding audit result on the name of the corresponding user identifier in the Nth audit of the process task.
S206: and determining an auditing user or an auditing user group for auditing the same data block in the Nth auditing process of the process task according to the auditing setting of the process task and the data block identifier of the audited data block.
S207: and sending the same data block to the auditing user or the auditing user group for auditing.
continuing to explain by taking the example of the auditing process task 2 in the first embodiment as an example, when the process task 2 is audited for the second time, a comparison operation is performed according to the data block identifiers of the five audited data blocks recorded in the historical auditing record 2. For four different comparison cases that may occur, two cases have been described in the first embodiment, and the rest two cases will be described in this embodiment.
For a third situation, for example, the data content of the data block 3 in the second audit is different from that of the data block 3 in the first audit, that is, the data block is modified, then an audit user or an audit user group for auditing the data block 3 is determined according to the audit setting of the process task 2 in the second audit, and the data block 3 is sent to the determined audit user or audit user group for auditing.
In a third case, an "extra" modification of the data block 3 that was not in question last by the originator of the flow task 2 can be quickly discovered. Thereby avoiding the occurrence of a crash that may result from the modified data block 3 in a second audit. The safety of reexamination is effectively improved.
for a fourth situation, for example, the data content of the data block 5 in the second audit is different from that of the data block 5 in the first audit, that is, the data block is modified, then an audit user or an audit user group for auditing the data block 5 is determined according to the audit setting of the process task 2 in the second audit, and the data block 5 is sent to the determined audit user or audit user group for auditing.
in the fourth situation, it can be quickly found that the initiator of the process task 2 has modified the data block 5 that has a problem in the last audit, and sends the modified data block 5 to the audit user or the audit user group corresponding to the data block 5, so that whether the modified data block 5 meets the audit requirements can be audited. Thereby effectively promoting the performance of the second audit.
It should be noted that, optionally, if the result of the examination of the nth examination of the process task is that the examination fails, the method further includes:
s208: and updating the corresponding relation among the data content of the audited data block, the audit result and the user identifier of the process task in the nth audit process into the historical audit record in a covering manner.
Before S208 is executed, the historical audit record stores the corresponding relationship between the data content, the audit result, and the user identifier of the audited data block of the process task in the audit process of the N-1 th audit submission, and after S208 is executed, the historical audit record stores the corresponding relationship between the data content, the audit result, and the user identifier of the audited data block of the process task in the audit process of the nth audit submission due to the operation type of the coverage update. That is, what is saved in the history audit record is the audit that the latest audit result is the audit that is not passed, and the audit content that has been completed before the audit is not passed.
It can be seen from the above embodiments that, by comparing the data content of the same data block in the flow task submitted for the N-th audit and the flow task submitted for the N-1 st audit, the modification to the data block that has passed the audit, or the modification that should not occur, can be found, thereby providing the security in the re-audit process. And when the data block which does not pass the audit in the (N-1) th audit is modified, the data block is sent to the user for audit, so that the non-first audit is effectively promoted.
EXAMPLE III
Fig. 3 is a block diagram of a monitoring device for modifying data according to an embodiment of the present invention, where the monitoring device includes:
a first obtaining unit 301, configured to obtain a flow task and a corresponding task identifier, where the flow task includes at least one data block.
For example, the task identifiers correspond to the flow tasks one to one. And even if the flow task does not pass the verification at a certain time and is not returned to the initiator of the flow task, the initiator submits the modified flow task to the verification again after modifying the flow task, and the task identifier of the modified flow task is the same as the task identifier of the flow task before modification. That is to say, even if the same flow task is rejected after being returned for many times, the task identifier of the flow task is not changed when the audit is submitted again after modification, or even when the audit is submitted again without modification.
The data blocks may be understood as pre-sorted data sets, and different data blocks may comprise different types of data sets. For example, flow task 1 may include financial data blocks that may include the finance-related data set of flow task 1 and legal data blocks that may include the legal-related data set of flow task 1. The data in the flow task can even belong to both data block 1 and data block 2. The process task may be divided into different data blocks in different ways according to different requirements, which is not limited by the present invention. Taking the example that the process task 1 may include a financial data block and a legal data block, the financial data block may be sent to a financial staff for review, the legal data block may be sent to a legal staff for review, and the whole process task is rejected and returned to the initiator of the process task 1 if any one data block fails to be reviewed.
A judging unit 302, configured to judge whether a history audit record of the process task is saved according to the task identifier; if yes, the process task is determined to be the process task submitted for the nth time, and the second obtaining unit 303 is triggered.
for example, in the embodiment of the present invention, when the process task fails to be audited due to some reason in an auditing process of a time, an auditing record that the process task has completed in the auditing process of the time is saved in a history auditing record, where the history auditing record includes related data of a data block that has been audited.
that is, when a process task is found to have a history of reviews, the process task belongs to a process task that is not the first time a review is submitted. If the historical audit record of the process task is judged not to be stored according to the task identifier, the process task can be confirmed to be a process task for submitting audit for the first time, a data block can be sent to different audit users for audit according to the traditional processing mode of the process task submitted for the first time and the audit setting of the process task, and the specific process is not repeated here.
The second obtaining unit 303 is configured to obtain, according to the historical review record, a corresponding relationship between data content of a reviewed data block, a review result, and a user identifier of the process task in an N-1 th review process of submitting a review, where the user identifier is used to identify a user who makes the review result for the data block, and N is an integer greater than or equal to 2.
and determining that the process task is a process task which is not submitted for the first time because the process task has a corresponding historical review record. For the history audit record, optionally, on the basis of the embodiment corresponding to fig. 3, fig. 4 is a device structure diagram of a monitoring device for modifying data according to an embodiment of the present invention, including:
an updating unit 401, configured to update, before triggering the first obtaining unit 301, a correspondence between data content of an audited data block, an audit result, and a user identifier of the process task in the N-1 th audit process to the historical audit record in a covering manner when the audit of the process task is failed for the N-1 th audit.
That is, what is saved in the history audit record is the audit content that was last audited and completed before the audit is not passed. For example, the flow task 2 includes 10 data blocks, and when the first audit is performed, after 4 data blocks, for example, the data blocks 1 to 4, are audited, the audit is not passed when the data block 5 is audited. It should be noted that it is not limited to whether the user reviewing different data blocks is different, for example, the user 1 is reviewing the data blocks 1 and 2, and the user 2 is reviewing the data blocks 3 to 5. The history audit record 2 corresponding to the process task 2 may include five corresponding relationships corresponding to five audited data blocks, which are corresponding relationships 1: the data content and the auditing result of the data block 1 are the user identification of the user 1 and the data block passing; correspondence relationship 2: the data content and the auditing result of the data block 2 are the user identification of the user 1 and the passing; correspondence relationship 3: the data content and the auditing result of the data block 3 are the user identification of the user 2 and the pass; correspondence relationship 4: the data content and the auditing result of the data block 4 are the user identification of the user 2 and the pass; correspondence relationship 5: the data content of the data block 5, the auditing result are failed and the user identification of the user 2.
In the nth review of the process task, it may occur that a data block included in the process task is not reviewed in the N-1 st review of the process task. For such data blocks, the auditing can be executed according to the auditing setting of the process task in the nth auditing of the process task, which is not described in detail herein. In the above example that the flow task 2 includes 10 data blocks, when the first audit is completed, 4 data blocks, such as data blocks 1 to 4, are audited, and then the audit is not passed when the data block 5 is audited. Then, when the process task 2 is reviewed for the second time, as the data blocks 6 to 10 are not recorded in the historical review record 2, processing can be performed according to the review setting of the process task 2, and the data blocks 6 to 10 are distributed to corresponding review users or review user groups for review.
It should also be noted that, in the embodiment of the present invention, the user identified by the user identifier may be an audit user corresponding to an audited process task, or may be an audit user in an audit user group corresponding to an audited process task. For example, the flow task 3 includes a data block a, a data block b, and a data block c, and in the auditing link, the data block a and the data block b are audited by a group of users including a user a, a user b, and a user c. The data block c is audited by user c and user d. It can be understood that, the data block a may be audited by any one of the user a, the user b, and the user c as a representative of the group of users, and an audit result is obtained, if the user a audits the data block a, the audit result of the data block a is passed and the user identified by the user identifier is the user a. The user c can represent the user group of the user a, the user b and the user c to check the data block a or the data block b and obtain a check result respectively, and the user c can also represent the user group of the user c and the user d to check the data block c and obtain a check result.
A comparing unit 304, configured to determine, according to the data block identifier of the checked data block, that a same data block in the flow task that submits the check N time and the flow task that submits the check N-1 time is identical, and compare whether the data content of the same data block is identical; if the same, the audit unit 305 is triggered.
The auditing unit 305 is configured to obtain a corresponding auditing result and a corresponding user identifier from the corresponding relationship of the historical auditing record according to the data block identifier of the audited data block, and in the nth auditing of the process task, assign the corresponding auditing result to the same data block under the name of the corresponding user identifier.
For example, the data block identifiers of the data blocks correspond to the data blocks one to one. Even if the flow task fails to pass the verification at a certain time and is not returned to the initiator of the flow task, the initiator submits the modified flow task to the verification again after modifying the data content of the data block in the flow task, and the data block identifier of the modified data block is the same as the data block identifier of the data block before modification. That is, even if the same data block in the flow task is modified or not modified for many times in the process of being returned for many times, the data block identifier of the data block will not change when the flow task to which the data block belongs is resubmitted for review.
Continuing with the example of the review process task 2, when the process task 2 is reviewed for the second time, a comparison operation is performed according to the data block identifiers of the five reviewed data blocks recorded in the historical review record 2. Four different alignment situations may occur, and in this embodiment, two of the situations will be described.
For the first case, for example, the data content of the data block 1 in the second audit is the same as that of the data block 1 in the first audit, that is, there is no modification, then the data block 1 in the second audit can be directly given the audit result that the audit is passed on the name of the user 1.
In the first case, the data block that has passed the previous audit and is not modified this time can be directly subjected to the audit result that passed the audit. And the audit does not need to be carried out again, so that the time for the second audit is saved.
For the second case, for example, the data content of the data block 5 in the second audit is the same as that of the data block 5 in the first audit, that is, there is no modification, then the data block 5 in the second audit can be directly given an audit result that the audit fails on behalf of the user 2.
In the second case, it can be quickly found that the initiator of the flow task 2 does not perform any adaptive modification on the data block 5 with the problem in the last audit, so that the data block 5 is directly given an audit result that the audit does not pass, and a process of re-auditing the data block 5 is omitted. Therefore, the process task 2 does not need to be continuously checked for the second time, and the process task 2 is returned to the initiator of the process task due to the failure of the second check. The auditing efficiency of the second auditing is improved.
It should be noted that, even in the case that the flow task includes only one data block, if the N-1 th audit of the flow task fails, when the N-th audit finds that the initiator does not modify the only one data block of the flow task through comparison, it may be directly determined that the N-th audit of the flow task fails, so that the process of sending the only one data block to the user for re-audit is omitted, and the efficiency of re-audit is improved.
To sum up, a history audit record of the process task when the audit is not passed is saved, if the process task is judged to have the history audit record according to the task identifier corresponding to the obtained process task, the process task can be determined to be a process and a task which are not subjected to the audit submission for the first time, the corresponding relation of the data content, the audit result and the user identifier of the audited data block in the audit process of the process task which is subjected to the audit submission for the last time, namely the audit submission for the (N-1) time is obtained according to the history audit record, the same data block in the process task which is subjected to the audit submission for the Nth time and the process task which is subjected to the audit submission for the (N-1) time is determined according to the data block identifier of the audited data block, whether the data content of the same data block is the same or not is compared, and when the comparison result is the same, the corresponding audit result and the user identifier of the audited data block are And marking, in the Nth audit of the process task, the corresponding audit result is given to the same data block on the name of the corresponding user mark. Therefore, when the process task re-submits the audit, the unmodified data blocks discovered by comparing the data contents can be directly endowed with the audit result of the last audit without being sent to the user for auditing again, the audit time is saved, and the audit efficiency of the re-audit is improved.
Example four
The comparison unit 304 can generate comparison results for comparing Xiong with Xiong.
As shown in fig. 4:
A determining unit 402, configured to determine, according to the review setting for the process task and the data block identifier of the reviewed data block, a review user or a review user group that reviews the same data block in the nth review process of the process task if the comparison result of the comparing unit 304 is different.
a sending unit 403, configured to send the same data block to the audit user or the audit user group for audit.
continuing to explain by taking the example of the auditing process task 2 in the first embodiment as an example, when the process task 2 is audited for the second time, a comparison operation is performed according to the data block identifiers of the five audited data blocks recorded in the historical auditing record 2. For four different comparison cases that may occur, two cases have been described in the first embodiment, and the rest two cases will be described in this embodiment.
for a third situation, for example, the data content of the data block 3 in the second audit is different from that of the data block 3 in the first audit, that is, the data block is modified, then an audit user or an audit user group for auditing the data block 3 is determined according to the audit setting of the process task 2 in the second audit, and the data block 3 is sent to the determined audit user or audit user group for auditing.
In a third case, an "extra" modification of the data block 3 that was not in question last by the originator of the flow task 2 can be quickly discovered. Thereby avoiding the occurrence of a crash that may result from the modified data block 3 in a second audit. The safety of reexamination is effectively improved.
For a fourth situation, for example, the data content of the data block 5 in the second audit is different from that of the data block 5 in the first audit, that is, the data block is modified, then an audit user or an audit user group for auditing the data block 5 is determined according to the audit setting of the process task 2 in the second audit, and the data block 5 is sent to the determined audit user or audit user group for auditing.
In the fourth situation, it can be quickly found that the initiator of the process task 2 has modified the data block 5 that has a problem in the last audit, and sends the modified data block 5 to the audit user or the audit user group corresponding to the data block 5, so that whether the modified data block 5 meets the audit requirements can be audited. Thereby effectively promoting the performance of the second audit.
It should be noted that, optionally, if the result of the nth audit on the process task is that the audit is not passed, the updating unit 401 is further configured to update the corresponding relationship between the data content of the audited data block, the audit result, and the user identifier of the process task in the nth audit process to the historical audit record in a covering manner.
Before the updating unit 401 is triggered to update the data content of the audited data block in the nth auditing process of the process task to the history auditing record in a covering manner, the history auditing record stores the corresponding relationship among the data content of the audited data block, the auditing result and the user identifier in the auditing process of the process task submitted to auditing in the (N-1) th time. After the updating unit 401 is triggered to execute the above actions, due to the operation type of the coverage update, the corresponding relationship among the data content of the audited data block, the audit result and the user identifier of the process task in the audit process of the nth audit submission is stored in the history audit record. That is, what is saved in the history audit record is the audit that the latest audit result is the audit that is not passed, and the audit content that has been completed before the audit is not passed.
It can be seen from the above embodiments that, by comparing the data content of the same data block in the flow task submitted for the N-th audit and the flow task submitted for the N-1 st audit, the modification to the data block that has passed the audit, or the modification that should not occur, can be found, thereby providing the security in the re-audit process. And when the data block which does not pass the audit in the (N-1) th audit is modified, the data block is sent to the user for audit, so that the non-first audit is effectively promoted.
As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by software plus a general hardware platform. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a media gateway, etc.) to execute the method according to the embodiments or some parts of the embodiments.
it should be noted that, in the present specification, all the embodiments are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus and system embodiments, since they are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only for the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. It should be noted that, for those skilled in the art, without departing from the principle of the present invention, several improvements and modifications can be made, and these improvements and modifications should also be construed as the protection scope of the present invention.
Claims (12)
1. A method for monitoring data modification, the method comprising:
Acquiring a flow task and a corresponding task identifier, wherein the flow task comprises at least one data block;
judging whether historical audit records of the process tasks are saved or not according to the task identifiers;
If yes, determining that the process task is the process task which submits the audit for the Nth time, and obtaining the corresponding relation among the data content, the audit result and the user identification of the audited data block of the process task in the audit process of submitting the audit for the Nth-1 th time according to the historical audit record, wherein the user identification is used for identifying the user who makes the audit result on the data block, and N is an integer more than or equal to 2;
Determining the same data block in the flow task submitted for the Nth time and the flow task submitted for the (N-1) th time according to the data block identifier of the audited data block, and comparing whether the data content of the same data block is the same or not;
If the data blocks are the same, acquiring corresponding auditing results and user identifications from the corresponding relation of the historical auditing records according to the data block identifications of the audited data blocks, and endowing the same data blocks with the corresponding auditing results on the name of the corresponding user identifications in the Nth auditing of the process task.
2. The method according to claim 1, wherein the determining, according to the data block identifier of the audited data block, whether the data content of the same data block is the same in the flow task that is submitted and audited for the nth time and the flow task that is submitted and audited for the N-1 th time is compared, further comprises:
If not, determining a checking user or a checking user group for checking the same data block in the Nth checking process of the process task according to the checking setting of the process task and the data block identifier of the checked data block;
and sending the same data block to the auditing user or the auditing user group for auditing.
3. The method according to claim 1, wherein in the N-1 th audit process of the process task, if the audit result of the first data block included in the process task is that the audit does not pass, in the nth submission audit process of the process task, the method determines, according to the data block identifier of the audited data block, the same data block in the process task submitted for the nth audit and the process task submitted for the N-1 th audit, and compares whether the data content of the same data block is the same, includes:
If the comparison results of the data contents of the first data block in the N-1 th audit and the nth audit are the same, acquiring a corresponding audit result and a user identifier from the corresponding relation of the historical audit record according to the data block identifier of the audited data block, and in the nth audit of the process task, giving the corresponding audit result to the same data block on the name of the corresponding user identifier, including:
Acquiring an auditing result of the first data block corresponding to the data content of the first data block and a first user identifier from the corresponding relation in the historical auditing record according to the data block identifier of the first data block;
And assigning an audit result that the audit is not passed to the first data block on the name of the first user identification.
4. The method according to claim 2, wherein in the N-1 th audit process of the process task, if the audit result of the second data block included in the process task passes the audit, in the nth submission audit process of the process task, the method determines, according to the data block identifier of the audited data block, a same data block in the process task submitted with the audit for the nth and the process task submitted with the audit for the N-1 th time, and compares whether the data content of the same data block is the same, includes:
If the comparison result of the data content of the second data block in the (N-1) th audit and the Nth audit is different, the process task is determined to be an audit user or an audit user group for auditing the same data block in the Nth audit process of the process task according to the audit setting of the process task and the data block identifier of the audited data block, and the process comprises the following steps:
and determining an auditing user or an auditing user group for auditing the second data block according to the auditing setting of the process task and the data block identifier of the second data block.
5. the method of claim 1, further comprising, prior to the obtaining the flow task and the corresponding task identifier:
and when the (N-1) th audit of the process task is failed, updating the corresponding relation of the data content, the audit result and the user identification of the audited data block of the process task in the (N-1) th audit process into the historical audit record in a covering manner.
6. the method according to any one of claims 1 to 5, wherein if the result of the review on the nth review of the process task is that the review fails, the method further comprises:
and updating the corresponding relation among the data content of the audited data block, the audit result and the user identifier of the process task in the nth audit process into the historical audit record in a covering manner.
7. A monitoring device for data modification, the device comprising:
The system comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for acquiring a flow task and a corresponding task identifier, and the flow task comprises at least one data block;
the judging unit is used for judging whether the historical audit record of the flow task is stored or not according to the task identifier; if yes, determining the process task as an Nth process task for submitting the audit, and triggering a second obtaining unit;
The second obtaining unit is configured to obtain, according to the historical review record, a corresponding relationship between data content of a reviewed data block, a review result, and a user identifier of the process task in an N-1 th review process of submitting review, where the user identifier is used to identify a user who makes the review result for the data block, and N is an integer greater than or equal to 2;
A comparison unit, configured to determine, according to the data block identifier of the checked data block, that a flow task that submits the check for the nth time is the same as the flow task that submits the check for the (N-1) th time, and compare whether the data contents of the same data block are the same; if the two are the same, triggering an auditing unit;
and the auditing unit is used for acquiring a corresponding auditing result and a corresponding user identifier from the corresponding relation of the historical auditing records according to the data block identifier of the audited data block, and endowing the same data block with the corresponding auditing result on the name of the corresponding user identifier in the Nth auditing of the process task.
8. The apparatus of claim 7, further comprising:
A determining unit, configured to determine, according to the audit setting of the process task and the data block identifier of the audited data block, an audit user or an audit user group for auditing the same data block in an nth audit process of the process task if the comparison results of the comparing unit are different;
and the sending unit is used for sending the same data block to the auditing user or the auditing user group for auditing.
9. the apparatus according to claim 7, wherein in the N-1 th audit process on the process task, if the audit result of the first data block included in the process task is that the audit is not passed, in the nth submission of the process task, the method includes:
if the comparison results of the comparison units are the same, the auditing unit is specifically configured to obtain, according to the data block identifier of the first data block, an auditing result of the first data block and a first user identifier, which correspond to the data content of the first data block, from the corresponding relationship in the historical auditing record; and assigning an audit result that the audit is not passed to the first data block on the name of the first user identification.
10. The apparatus according to claim 8, wherein in the N-1 th audit process on the process task, if the audit result of the second data block included in the process task is that the audit is passed, in the nth submission audit process of the process task, the method includes:
If the comparison results of the comparison units are different, the auditing unit is specifically configured to obtain a second user identifier corresponding to the data content of the second data block from the corresponding relationship in the historical auditing record according to the data block identifier of the second data block;
The sending unit is specifically configured to send the second data block to the second user for auditing according to the second user identifier.
11. The apparatus of claim 7, further comprising:
And the updating unit is used for updating the corresponding relation among the data content of the audited data block, the audit result and the user identifier of the process task in the process of the (N-1) th audit into the historical audit record in a covering manner before the first obtaining unit is triggered and when the (N-1) th audit of the process task is failed.
12. The apparatus according to any one of claims 7 to 11, wherein if the result of the review of the nth review of the process task is that the review does not pass, the updating unit is further configured to update the history review record with the correspondence relationship among the data content of the reviewed data block, the result of the review, and the user identifier of the process task in the nth review process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510358754.9A CN106327140B (en) | 2015-06-25 | 2015-06-25 | Method and device for monitoring data modification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510358754.9A CN106327140B (en) | 2015-06-25 | 2015-06-25 | Method and device for monitoring data modification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106327140A CN106327140A (en) | 2017-01-11 |
| CN106327140B true CN106327140B (en) | 2019-12-06 |
Family
ID=57729124
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510358754.9A Active CN106327140B (en) | 2015-06-25 | 2015-06-25 | Method and device for monitoring data modification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106327140B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110659875B (en) * | 2019-09-18 | 2022-04-12 | 联宝(合肥)电子科技有限公司 | Information processing method and system |
| CN110895745B (en) * | 2019-12-02 | 2023-04-18 | 深圳前海环融联易信息科技服务有限公司 | Method and device for polling to obtain task, computer equipment and storage medium |
| CN111538748A (en) * | 2020-04-30 | 2020-08-14 | 中国银行股份有限公司 | Service page modification method and device |
| CN111598540B (en) * | 2020-05-14 | 2023-04-07 | 云账户技术(天津)有限公司 | Method and device for auditing items and computer-readable storage medium |
| CN112001691A (en) * | 2020-07-01 | 2020-11-27 | 北京车行一六八信息技术有限公司 | Page auditing method and device, computer equipment and storage medium |
| CN114640606A (en) * | 2020-12-01 | 2022-06-17 | 中移物联网有限公司 | Abnormity processing method and controller for Internet of things card terminal |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101000667A (en) * | 2006-01-12 | 2007-07-18 | 鸿富锦精密工业（深圳）有限公司 | System and method of dynamic examining procedure |
| CN103677813A (en) * | 2013-11-29 | 2014-03-26 | 广州视源电子科技股份有限公司 | Automatic configuration auditing method and automatic auditing system |
| CN103885964A (en) * | 2012-12-20 | 2014-06-25 | 北京新媒传信科技有限公司 | Content checking method and system |
| CN104133910A (en) * | 2014-08-08 | 2014-11-05 | 平安养老保险股份有限公司 | System and method for outputting medical insurance reimbursement document audit result |
-
2015
- 2015-06-25 CN CN201510358754.9A patent/CN106327140B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101000667A (en) * | 2006-01-12 | 2007-07-18 | 鸿富锦精密工业（深圳）有限公司 | System and method of dynamic examining procedure |
| CN103885964A (en) * | 2012-12-20 | 2014-06-25 | 北京新媒传信科技有限公司 | Content checking method and system |
| CN103677813A (en) * | 2013-11-29 | 2014-03-26 | 广州视源电子科技股份有限公司 | Automatic configuration auditing method and automatic auditing system |
| CN104133910A (en) * | 2014-08-08 | 2014-11-05 | 平安养老保险股份有限公司 | System and method for outputting medical insurance reimbursement document audit result |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106327140A (en) | 2017-01-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106327140B (en) | Method and device for monitoring data modification | |
| JP2020510331A5 (en) | ||
| US10609087B2 (en) | Systems and methods for generation and selection of access rules | |
| CN110070445B (en) | Transaction processing method and device based on blockchain system | |
| CN111382164B (en) | Service processing method based on block chain network | |
| CN109543891B (en) | Method and apparatus for establishing capacity prediction model, and computer-readable storage medium | |
| CN110059981B (en) | Trust degree evaluation method and device and terminal equipment | |
| CN110088744A (en) | A kind of database maintenance method and its system | |
| CN103440460A (en) | Application system change validation method and system | |
| JP2019504545A (en) | Method and apparatus for recognizing service request for changing mobile phone number | |
| CN111010282B (en) | Block chain-based information processing method, related device and storage medium | |
| CN111694652A (en) | Task dynamic scheduling method and device, computer equipment and storage medium | |
| CN111026737A (en) | Task processing method and device | |
| CN110942314A (en) | Abnormal account supervision method and device | |
| US10614518B1 (en) | Techniques for audit management | |
| CN113535449B (en) | Abnormal event restoration processing method and device, computer equipment and storage medium | |
| CN110471966B (en) | Information data verification method, device, computer equipment and storage medium | |
| CN110674532B (en) | Tamper-proof method and device for evidence file | |
| CN110489208B (en) | Virtual machine configuration parameter checking method, system, computer equipment and storage medium | |
| CN114078049A (en) | Data processing method and device for supply chain financial credit-information service | |
| US20170149831A1 (en) | Apparatus and method for verifying detection rule | |
| CN108446882B (en) | Insurance policy processing method and device | |
| CN115639972B (en) | Data migration method and device, electronic equipment and storage medium | |
| CN116015785B (en) | Information security protection method, electronic equipment and storage medium | |
| US9996691B1 (en) | Using signals from developer clusters |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20211110 Address after: Room 101, warehouse 1, No. 88, Jingbin Avenue, Jingbin Industrial Park, Wuqing District, Tianjin Patentee after: Alibaba Huabei Technology Co., Ltd Address before: P.O. Box 847, 4th floor, capital building, Grand Cayman, British Cayman Islands Patentee before: Alibaba Group Holdings Limited |