Verification method of auditing process, electronic equipment, storage medium and program product
By building sequentially executed nodes in the content publishing platform and using the verification rule base to verify the audit actions, the problem of missed behavior in manual audit is solved, and the standardization and security of the audit process are achieved.
Patent Information
- Application Number
- CN202411265427.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-10
- Publication Date
- 2025-01-10
AI Technical Summary
Manual review is prone to missed behavior in content publishing platforms, resulting in increased risks. It is mainly due to the auditor being too fast or the auditing action is not performed properly, and the existing technology is difficult to effectively monitor and correct.
By building a node to be reviewed that is executed sequentially, collecting audit action data, and using the tree structure rule tree in the verification rule library to verify the audit action to ensure that the audit process complies with the specifications.
Effectively monitor and correct the auditor's audit behavior, ensure that the audit process complies with the verification rules, reduce missed behavior, and improve the quality and safety of the audit.
Smart Images

Figure CN119294997A_ABST
Abstract
Description
Technical Field
[0001] One or more embodiments of the present application relate to the field of computer software technology, and in particular, to a verification method for an audit process, an electronic device, a storage medium, and a program product. Background Art
[0002] A content publishing platform may refer to a communication medium such as an application program or a website that allows users to publish content on their own and transmit the published content to other users for browsing.
[0003] For content publishing platforms, in order to prevent users from posting non-standard content, auditors can manually review the content to be published.
[0004] However, manual review mainly relies on the personal experience of the auditor, so omissions often occur. Omissions refer to the behavior of auditors mistakenly reviewing non-standard content as standard. Omissions will bring immeasurable risks to applications, websites or platforms, and omissions need to be avoided.
[0005] In reviewing the cases of omissions, it was found that most of the cases were related to auditors reviewing too quickly and failing to perform the audit actions properly. Summary of the invention
[0006] In view of this, one or more embodiments of the present application provide a verification method for an audit process, an electronic device, a computer-readable storage medium, and a computer program product. By verifying the audit action data in the audit process through verification rules, it is possible to discover non-standard audit actions in the audit process, thereby ensuring that the auditor can perform the audit in accordance with the standardized audit actions.
[0007] To achieve the above objectives, one or more embodiments of the present application provide the following technical solutions:
[0008] According to a first aspect of one or more embodiments of the present application, a verification method for an audit process is proposed, the method comprising:
[0009] Based on a number of audit contents in the target audit object to be audited, a number of audit nodes to be executed in sequence are constructed; wherein the number of audit nodes correspond to different audit contents respectively, and the execution order of the number of audit nodes corresponds to the audit order of the number of audit contents in the target audit object respectively;
[0010] Determining the plurality of nodes to be audited as execution nodes in sequence according to the execution order, and acquiring audit action data collected during the audit of audit contents corresponding to the execution nodes;
[0011] The verification rule corresponding to the execution node is matched from a rule tree of a tree structure constructed based on a verification rule library, and the audit action data is verified according to the verification rule.
[0012] Optionally, matching the verification rule corresponding to the execution node from a rule tree of a tree structure constructed based on a verification rule base includes:
[0013] The audit content corresponding to the execution node is used as the input of the root node in the rule tree, so as to traverse the rule tree starting from the root node, find the leaf node corresponding to the execution node based on the audit content, and determine the verification rule associated with the found leaf node as the verification rule corresponding to the execution node.
[0014] Optionally, the verification rule is composed of at least one behavior group rule, the behavior group rule is composed of at least one action rule, and the action rule includes at least one action achievement condition that complies with the standard audit procedure;
[0015] The tree structure of the rule tree includes a root node, the root node is connected to a first-level node corresponding to the verification rule, the first-level node is connected to at least one second-level node corresponding to at least one behavior group rule constituting the verification rule, the second-level node is connected to at least one leaf node corresponding to at least one action rule constituting the behavior group rule, and the leaf node is associated with at least one action achievement condition included in the action rule that complies with the standard audit procedure.
[0016] Optionally, the leaf node corresponding to the audit content and the ancestor node of the leaf node both record the unique identifier of the node to be audited corresponding to the audit content;
[0017] The step of using the audit content corresponding to the execution node as the input of the root node in the rule tree, traversing the rule tree from the root node, searching for a leaf node corresponding to the execution node based on the audit content, and determining the verification rule associated with the found leaf node as the verification rule corresponding to the execution node includes:
[0018] The unique identifier corresponding to the execution node is used as the input of the root node in the rule tree, so as to traverse the rule tree starting from the root node, find the leaf node corresponding to the execution node based on the unique identifier, and determine the action fulfillment condition associated with the found leaf node as the verification rule corresponding to the execution node.
[0019] Optionally, the audit content tracking in the target audit object includes a tracking program; the tracking program is triggered and executed by an audit action for the audit content, and the tracking program is used to collect audit action data related to the audit action;
[0020] The obtaining of the audit action data collected during the audit of the audit content corresponding to the execution node includes:
[0021] Acquire the audit action data collected by the tracking program during the process of auditing the audit content corresponding to the execution node.
[0022] Optionally, the data structure corresponding to the node to be audited includes an action field for storing the audit action data;
[0023] After obtaining the audit action data collected during the audit of the audit content corresponding to the execution node, the method further includes:
[0024] The audit action data is used as the field value of the action field and stored in the data structure corresponding to the execution node;
[0025] The verifying the audit action data according to the verification rule includes:
[0026] According to the verification rule, the audit action data recorded in the action field in the data structure corresponding to the execution node is verified.
[0027] Optionally, the data structure further includes a status field for recording a verification result; and the method further includes:
[0028] The verification result of the verification rule on the audit action data is used as the field value of the status field and stored in the data structure corresponding to the node to be executed.
[0029] Optionally, the data structure further includes a location field for recording the location of the audit content in the target audit object; the method further includes:
[0030] Monitoring data write events for the data structure corresponding to the execution node;
[0031] If the verification result of the verification field record in the data structure corresponding to the execution node is monitored to be a verification failure, the position of the verification field record in the data structure corresponding to the execution node is obtained, and a prompt for indicating the verification failure is output at the position in the target audit object in the audit content corresponding to the execution node.
[0032] Optionally, the data structure further includes a location field for recording the location of the audit content in the target audit object; the method further includes:
[0033] If it is monitored that the verification result recorded in the verification field in the data structure corresponding to the execution node is a successful verification, then based on the execution order, determine the next node to be reviewed of the execution node;
[0034] The position of the position field record in the data structure of the next node to be audited is obtained, and the audit content corresponding to the execution node displayed in the audit operation interface is jumped to the audit content corresponding to the next node to be audited corresponding to the position.
[0035] Optionally, the review operation interface displays the number of remaining unexecuted nodes to be reviewed and a trigger control for jumping to the next node to be reviewed;
[0036] In response to the triggering operation of the triggering control, based on the execution order, determining the next node to be reviewed of the execution node;
[0037] The position of the position field record in the data structure of the next node to be audited is obtained, and the audit content corresponding to the execution node displayed in the audit operation interface is jumped to the audit content corresponding to the next node to be audited corresponding to the position.
[0038] Optionally, the target audit object to be audited includes a target text to be audited;
[0039] The method of constructing a plurality of audited nodes to be executed sequentially based on a plurality of audited contents in the target audit object to be audited includes:
[0040] Based on the text segments in the target text, a plurality of to-be-audited nodes corresponding to different text segments are constructed and executed in sequence.
[0041] According to a second aspect of one or more embodiments of the present application, an electronic device is provided, including:
[0042] processor;
[0043] a memory for storing processor-executable instructions;
[0044] The processor implements the verification method of the audit process described in any one of the above items by running the executable instructions.
[0045] According to a third aspect of one or more embodiments of the present application, a computer-readable storage medium is proposed, on which computer instructions are stored. When the instructions are executed by a processor, the steps of the verification method of the audit process described in any of the above items are implemented.
[0046] According to a fourth aspect of one or more embodiments of the present application, a computer program product is proposed, including a computer program, which, when executed by a processor, implements the steps of the verification method of the audit process described in any of the above items.
[0047] The technical solution provided by the embodiments of the present application may have the following beneficial effects:
[0048] A general verification scheme for the audit process is provided. By constructing audit nodes that correspond to the audit content of the target audit object and are executed sequentially, the audit action data generated by the auditor during the audit of the audit content corresponding to the audit node is collected, and the audit action data is verified in combination with the verification rules corresponding to the audit node in the tree-structured rule tree constructed by the verification rule library. In this way, whether the audit process is standardized is determined based on the audit actions actually performed by the auditor, ensuring that the auditor's audit process meets the requirements of the verification rules for the audit actions.
[0049] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] Figure 1 It is a system architecture diagram of a content review system provided by an exemplary embodiment.
[0051] Figure 2 It is a flowchart of a verification method for an audit process provided by an exemplary embodiment.
[0052] Figure 3 It is a schematic diagram of a data structure of a node to be reviewed and a tree structure of a rule tree provided by an exemplary embodiment.
[0053] Figure 4 It is an overall flow chart of the verification process provided by an exemplary embodiment.
[0054] Figure 5 It is a schematic diagram of an audit operation interface provided by an exemplary embodiment.
[0055] Figure 6 It is a schematic structural diagram of an electronic device provided by an exemplary embodiment. DETAILED DESCRIPTION
[0056] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of the present application. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of the present application as detailed in the appended claims.
[0057] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this application. In some other embodiments, the steps included in the method may be more or less than those described in this application. In addition, a single step described in this application may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this application may also be combined into a single step for description in other embodiments.
[0058] See also Figure 1 , a system architecture diagram of a content review system is provided, which includes a server 100 and at least one client 200.
[0059] The server 100 may be a program installed in a backend device to provide audit services to auditors. Figure 1 As shown, the background device can be a server, which can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.
[0060] The client 200 may be a program installed in a user terminal to provide audit services to auditors. The client 200 includes but is not limited to an application APP, a web page, a small program, a plug-in or a component. Figure 1 As shown, the user terminal includes but is not limited to smart phones, personal digital assistants, tablet computers, personal computers, laptops, virtual reality terminal devices, augmented reality terminal devices, etc.
[0061] The server 100 may be integrated or independent with the content publishing platform. In the latter case, it may be connected through an internal network or a dedicated network, or may be connected through an encrypted public network. In particular, when it is an integrated relationship, a connection in the form of an internal bus with higher efficiency and faster transmission speed may be adopted.
[0062] When the content publishing platform generates content to be published by the user, the server 100 sends the content to be published as the target review object to at least one client 200, and the reviewer of the client 200 reviews it. During the review process, the client 200 can implement the verification method of the review process provided in the embodiment of the present application locally, or can implement the verification method of the review process provided in the embodiment of the present application with the help of the server 100.
[0063] The following is an exemplary description of the verification method for the audit process provided in the embodiment of the present application by using any client in the verification system: Figure 2 , Figure 2 A flow chart of a verification method for an audit process is shown, the method comprising:
[0064] Step 210, based on a number of audit contents in the target audit object to be audited, construct a number of audited nodes to be executed sequentially; wherein the number of audited nodes correspond to different audit contents respectively, and the execution order of the number of audited nodes corresponds to the sorting order of the number of audit contents in the target audit object.
[0065] The target audit object may refer to an object assigned to an auditor and required to be audited by the auditor, such as an article, a video, an audio, an image, etc.
[0066] Taking an article as an example, the target review object to be reviewed may include a target text to be reviewed;
[0067] The above step 210 can construct a number of to-be-audited nodes corresponding to different text segments that are executed in sequence based on the text segments in the target text.
[0068] For example, an article can be divided into several text segments according to paragraphs. According to the sequence of the paragraphs, a corresponding node to be reviewed can be constructed for each paragraph, and the execution order of these nodes to be reviewed corresponds to the sequence of the paragraphs.
[0069] Step 220, determining the plurality of nodes to be audited as execution nodes in sequence according to the execution order, and obtaining audit action data collected during the process of auditing the audit contents corresponding to the execution nodes.
[0070] Taking the review of articles as an example, when reviewing articles, auditors usually need to read the article content thoroughly; then the review action data such as the movement trajectory, hovering position, and hovering duration of the reading indicator (such as the cursor) can be regarded as the basis for judging whether the auditor has performed the review. In addition, the auditor's facial features, especially the eye features, can be collected with the help of motion capture equipment, and the focus trajectory of the eyes can be used as the basis for judging whether the auditor has performed the review.
[0071] In an exemplary embodiment, the audit content tracking in the target audit object includes a tracking program; the tracking program is triggered to be executed by an audit action for the audit content, and the tracking program is used to collect audit action data related to the audit action;
[0072] Correspondingly, the above step 220 can obtain the audit action data collected by the tracking program during the process of auditing the audit content corresponding to the execution node.
[0073] Taking the review of articles as an example, when reviewers review articles, they usually need to read through the article content. Then the movement trajectory, hovering position, and hovering duration of the reading indicator (such as the cursor) can be used as review action data. For example, when the reading indicator moves to a certain paragraph and the hovering duration reaches the preset duration, the execution of the tracking program for the paragraph can be triggered, thereby collecting the review action data such as the hovering position of the current reading indicator, the hovering duration of the continuous hovering, the end of the hovering, and the movement trajectory.
[0074] In this way, the audit actions performed by the auditor during the audit content audit process are monitored through the tracking program, and the collected audit action data related to the audit action is reported to the client, so that the client can perceive the audit actions actually performed by the auditor.
[0075] In order to improve data usage efficiency, a data structure with data storage capacity can be built for each node to be reviewed. Figure 3 Schematic diagram of the data structure StepData of the node to be reviewed is shown in . The data structure is used to store data related to the node to be reviewed, for example, to store the initial data of the node to be reviewed. The initial data can be content data related to the review content extracted by the client when constructing the node to be reviewed, such as the review object identifier, review content identifier, location of the review content, etc. corresponding to the node to be reviewed.
[0076] Similarly, the data structure can also be used to store the above-mentioned audit action data. In order to facilitate distinction, the data structure can pre-define different fields, and different fields are used to store different data, such as the name field eventName is used to store the audit action name, the content field contentID is used to store the audit content identifier, the object field taskId is used to store the audit object identifier, the location field itemID is used to store the location of the audit content in the audit object, the action field action is used to store the audit action data, and so on.
[0077] Based on this, after the review action data is obtained in the above step 220, the following may also be included:
[0078] The audit action data is used as the field value of the action field and stored in the data structure corresponding to the execution node.
[0079] Correspondingly, the subsequent step 230 can verify the audit action data recorded in the action field in the data structure corresponding to the execution node according to the verification rule.
[0080] Since the client can continuously receive the audit action data reported by different nodes to be audited, by timely storing the received audit action data in the data structure of the corresponding node to be audited, it can not only release the content resources occupied by the received audit action data, but also avoid the problem of being unable to distinguish the corresponding nodes to be audited after mixing different audit action data.
[0081] Step 230, matching the verification rule corresponding to the execution node from the rule tree of the tree structure constructed based on the verification rule library, and verifying the audit action data according to the verification rule.
[0082] The verification rule library may contain several different verification rules. Since the verification rules in the verification rule library are usually in the form of natural language, the verification rules in natural language are converted into a tree-structured rule tree, so that the structured rule tree can be used to quickly match the verification rules corresponding to the execution nodes.
[0083] Exemplarily, the matching of the verification rule corresponding to the execution node from the rule tree of the tree structure constructed based on the verification rule library may include:
[0084] The audit content corresponding to the execution node is used as the input of the root node in the rule tree, so as to traverse the rule tree starting from the root node, find the leaf node corresponding to the execution node based on the audit content, and determine the verification rule associated with the found leaf node as the verification rule corresponding to the execution node.
[0085] After matching the verification rules, the audit action data can be verified according to the verification rules; if the audit action data does not meet the action achievement conditions configured in the verification rules, it can be determined that the verification has failed; if the audit action data meets the action achievement conditions configured in the verification rules, it can be determined that the verification has succeeded.
[0086] Still taking the review of articles as an example, the action achievement condition configured in the verification rule may include that the hovering time of the reading indicator is greater than or equal to the preset time. That is, only when the hovering time of the reading indicator on the review content corresponding to the current execution node is greater than or equal to the preset time, can it be determined that the review process of the current execution node meets the action achievement condition configured in the verification rule.
[0087] By constructing audited nodes that correspond to the audit content of the target audit object and are executed sequentially, the audit action data generated by the auditor in the process of auditing the audit content corresponding to the audited nodes is collected, and the audit action data is verified in combination with the verification rules corresponding to the audit nodes in the tree-like structured rule tree constructed by the verification rule library. In this way, the audit process is determined to be standardized based on the audit actions actually performed by the auditor, ensuring that the auditor's audit process meets the requirements of the verification rules for the audit actions.
[0088] Exemplarily, the verification rule may be a rule (SOPRule) configured in a standard operating procedure (SOP) for judging whether the audit process is standardized.
[0089] In content review, standard review procedures can refer to a set of standard review procedures used to regulate all reviewers. The use of standard review procedures can allow different reviewers to follow the same review standards and unified review process as much as possible, thereby improving review efficiency, reducing errors, and helping the review team to work together better.
[0090] Since a standard audit procedure can include a variety of different audit objects, the standard audit procedure can be configured with different standard rules for different audit objects.
[0091] In an exemplary embodiment, the verification rule may be composed of at least one behavior group rule (GroupRule), the behavior group rule is composed of at least one action rule (StepRule), and the action rule contains at least one action achievement condition that complies with the standard audit procedure.
[0092] Still taking the review of articles as an example, the verification rules may include behavior group rules related to reading indicator marks and behavior group rules related to eye features; and the behavior group rules related to reading indicator marks may further include action rules related to the hovering of reading indicator marks and action rules related to the movement trajectory of reading indicator marks. Furthermore, for the action rules related to hovering, the action achievement conditions included may include the hovering time of the reading indicator mark being greater than or equal to the preset time. That is, only when the hovering time of the reading indicator mark on the review content corresponding to the current execution node is greater than or equal to the preset time, can it be determined that the review process of the current execution node complies with the action rules related to the hovering time.
[0093] The tree structure of the rule tree constructed based on the verification rule base may include a root node, the root node is connected to a first-level node corresponding to the verification rule, the first-level node is connected to at least one second-level node corresponding to at least one behavior group rule constituting the verification rule, the second-level node is connected to at least one leaf node corresponding to at least one action rule constituting the behavior group rule, and the leaf node is associated with at least one action achievement condition included in the action rule that complies with the standard audit procedure.
[0094] Please combine the following Figure 3 Schematic diagram of the tree structure of the rule tree shown in , which is constructed by transforming the verification rules of the standard audit procedure (SOPRule).
[0095] Assume that the standard audit procedure is configured with 2 verification rules, corresponding to Figure 3 The first-level nodes SOPRule-1 and SOPRule-2 are connected under the root node. The first-level nodes can have AND and OR logic. Since different standard rules correspond to different audit objects, the default logic can be OR, that is, the verification process only needs to match one first-level node. These two verification rules are composed of two behavior group rules, corresponding to Figure 3 The second-level nodes GroupRule-1 and GroupRule-2 connected to the first-level node SOPRule-1, and the second-level nodes GroupRule-3 and GroupRule-4 connected to the first-level node SOPRule-2. The second-level nodes can also have the logic of AND and OR. Since they belong to the same validation rule, the behavior group rules under the same first-level node can have the logic of AND by default. Taking GroupRule-2 as an example, the behavior group rule can be composed of 2 action rules, corresponding to Figure 3 The leaf nodes StepRule-1 and StepRule-2 are connected under the second-level node GroupRule-2. The leaf nodes can also have the logic of AND and OR. Since they belong to the same behavior group rule, the action rules under the same second-level node can have the logic of AND by default. Taking StepRule-1 as an example, the leaf node StepRule-1 can be associated with at least one of the action achievement conditions and attribute achievement conditions contained in the action rule.
[0096] Regarding the action achievement conditions, taking the aforementioned hover-related action rules as an example, the hover duration requirements for different text lengths can be configured according to the text length of the article paragraph. For example, when the text length is 1 to 100 words, the hover duration is x seconds, when the text length is 100 to 200 words, the hover duration is 2x seconds, and so on.
[0097] Taking the action rules related to click actions as an example, assuming that the configured action achievement condition is 5 times, then each time the click action is received to trigger the verification, if the value recorded in the cumulative number field measuer in the data structure corresponding to the execution node is less than 5, the cumulative number field measuer can be accumulated (starting from 0 and adding 1 each time) until the cumulative number recorded in the measuer reaches 5, the action achievement condition can be met.
[0098] Since the action fulfillment conditions are for the same action, the relationship between different action fulfillment conditions can be logically OR. Regarding the attribute fulfillment conditions, they are generally defined as the satisfaction conditions other than the behavior action. For example, the current auditor needs to meet the specific auditor.
[0099] Since the matching resources of the rule tree are limited, there may be a risk of response delay or even crash when many auditors access the rule tree at the same time; therefore, it is necessary to improve the matching efficiency of the rule tree and reduce the matching resources required for a single rule match, so as to cope with more access needs.
[0100] In this regard, an exemplary embodiment may record the unique identifier of the node to be reviewed corresponding to the review content in the leaf node corresponding to the review content and the ancestor node of the leaf node;
[0101] In this way, the audit content originally corresponding to the execution node is changed to be the input of the root node in the rule tree, and the unique identifier corresponding to the execution node is used as the input of the root node in the rule tree, so as to traverse the rule tree starting from the root node, find the leaf node corresponding to the execution node based on the unique identifier, and determine the action achievement condition associated with the found leaf node as the verification rule corresponding to the execution node.
[0102] In the previous embodiment, since only leaf nodes in the rule tree have a corresponding relationship with the audit content, in the previous embodiment, after the audit content is input, all nodes in the rule tree need to be traversed, resulting in a large amount of resource consumption;
[0103] By recording the unique identifier of the node to be audited corresponding to the audit content in the leaf node corresponding to the audit content and the ancestor node of the leaf node, an effect of "coloring" all nodes is achieved; in this way, after the unique identifier corresponding to the execution node is passed in, only the nodes that hit the unique identifier are retrieved at each level, without traversing other nodes that do not hit the unique identifier and all child nodes of other nodes.
[0104] For example, Figure 3As shown in , the unique identifier may be composed of an audit object identifier (taskID), an audit content identifier (contentID) and an audit action name (eventName).
[0105] Below Figure 3 Take the rule tree shown as an example, assuming that the leaf node to be matched is GroupRule-4 under SOPRule-2, and StepRule-X under GroupRule-4 (not shown in the figure). In the previous embodiment, it is necessary to traverse the rule tree, match SOPRule-1, GroupRule-1, all leaf nodes under GroupRule-1 under the root node in turn (no match), then match all leaf nodes under GroupRule-2 (no match), return to the first-level node, match all leaf nodes of GroupRule-3 under SOPRule-2 (still no match), and finally match all leaf nodes of GroupRule-4 under SOPRule-2, only then can StepRule-X be matched.
[0106] In this embodiment, by "coloring" the nodes in the rule tree, for StepRule-X, since it and its ancestor nodes (GroupRule-4, SOPRule-2, and the root node) all record the corresponding audit content, the unique identifier of the corresponding node to be audited is assumed to be Y;
[0107] Therefore, when the node to be audited of the audit content is used as the node to be executed, it is only necessary to pass in the unique identifier Y. The existence of Y in the root node indicates that there is a verification rule in the rule tree that matches the node to be audited. Further, in the first-level node, since SOPRule-1 does not record Y, but SOPRule-2 records Y, it indicates that there is a verification rule under SOPRule-2 that matches the node to be audited. Therefore, there is no need to traverse the nodes under SOPRule-1 (reducing matching resources). Furthermore, in the second-level node, since only GroupRule-4 under SOPRule-1 records Y, there is no need to traverse the nodes under GroupRule-3 (reducing matching resources again). Finally, StepRule-X can be matched from GroupRule-4.
[0108] After introducing the rule tree, let's combine Figure 4 The overall flow chart of the verification process shown provides a detailed description of the verification implementation example of the audit process.
[0109] like Figure 4 As shown, the verification process of the client can be abstracted into three modules, namely, the verification module, the execution module and the prompt module.
[0110] Among them, the execution module is used to construct a number of nodes to be audited that are executed sequentially based on a number of audit contents in the target audit object to be audited; and, in accordance with the execution order, the several nodes to be audited are determined as execution nodes in sequence, and the audit action data collected during the audit of the audit content corresponding to the execution nodes is obtained.
[0111] Specifically, after obtaining the audit content of the target audit object, the client can trigger the execution module to construct a node to be audited, and register a behavior monitor for the node to be audited to monitor the audit action data collected by the audit content tracking program. In addition, the execution module can generate a guide box (invisible by default) at the location of each audit content based on the position of the audit content in the target audit object. The auditor will perform audit operations on the audit content that needs to be audited in turn based on the execution order of the aforementioned nodes to be audited. The audit actions performed by the auditor will trigger the tracking program to collect and report the audit action data; after the execution module monitors the audit action data, it can write the audit action data into the data structure of the node to be audited corresponding to the audit content, and at the same time trigger the verification module to perform verification.
[0112] In response to the verification triggered by the execution module, the verification module reads the action field from the data structure of the current execution node to record the audit action data written by the execution module based on the current execution node; on the other hand, based on the unique identifier of the current execution node, it matches the corresponding verification rule from the rule tree. In this way, the matched verification rule can be used to verify the read audit action data.
[0113] In a possible embodiment, the data structure corresponding to the node to be audited may also include a status field (such as Figure 3 status field shown in); after step 230, the verification result of the verification rule on the audit action data can also be used as the field value of the status field and stored in the data structure corresponding to the node to be executed.
[0114] In a possible embodiment, the data structure corresponding to the node to be audited may further include a location field for recording the location of the audit content in the target audit object; the method further includes:
[0115] Monitoring data write events for the data structure corresponding to the execution node;
[0116] If the verification result of the verification field record in the data structure corresponding to the execution node is monitored to be a verification failure, the position of the verification field record in the data structure corresponding to the execution node is obtained, and a prompt for indicating the verification failure is output at the position in the target audit object in the audit content corresponding to the execution node.
[0117] Exemplarily, the prompt for indicating verification failure may be to highlight the location of the audit content, thereby intuitively reminding the auditor that the highlighted audit content has not passed the verification.
[0118] Continue to refer Figure 4 As shown, the verification module can write the verification result into the data structure of the current execution node, and the execution module can monitor the verification field in the data structure of the execution node.
[0119] When the execution module detects that the verification of the current execution node has failed, a prompt of verification failure can be output at the location of the target audit object according to the location recorded in the data structure. The prompt can refer to modifying the invisible guide box generated above to be visible, so as to highlight the audit content. When the auditor sees the highlighted guide box, he can immediately perceive that the audit content in the guide box has not been audited in accordance with the audit requirements and needs to be audited again.
[0120] In a possible embodiment, if it is monitored that the verification result of the verification field record in the data structure corresponding to the execution node is successful, then based on the execution order, the next node to be reviewed of the execution node is determined;
[0121] The position of the position field record in the data structure of the next node to be audited is obtained, and the audit content corresponding to the execution node displayed in the audit operation interface is jumped to the audit content corresponding to the next node to be audited corresponding to the position.
[0122] Continue to refer Figure 4 As shown, when the execution module detects that the verification of the current execution node is successful, it will switch to the next node to be reviewed, and position the displayed content in the review operation interface to the review content corresponding to the next node to be reviewed, so as to facilitate the auditor to quickly review the next review content without the need for the auditor to manually adjust the displayed content.
[0123] In a possible embodiment, the audit operation interface displays the number of remaining unexecuted nodes to be audited and a trigger control for jumping to the next node to be audited;
[0124] In response to the triggering operation of the triggering control, based on the execution order, determining the next node to be reviewed of the execution node;
[0125] The position of the position field record in the data structure of the next node to be audited is obtained, and the audit content corresponding to the execution node displayed in the audit operation interface is jumped to the audit content corresponding to the next node to be audited corresponding to the position.
[0126] Combine the following Figure 5 The schematic diagram of the audit operation interface shown in FIG. 1 includes a prompt area and a content display area. The prompt area can display the number of remaining unexecuted nodes to be audited, as well as a trigger control for jumping to the next node to be audited ( Figure 5 The content display area is used to display the audit content corresponding to the current execution node. When the auditor clicks the "Next" control, the audit content displayed in the content display area can automatically jump from the audit content N corresponding to the current execution node to the audit content N+1 corresponding to the next node to be audited.
[0127] It should be noted that when jumping to the audit content corresponding to the next node to be audited, the next node to be audited needs to be determined as a new execution node, so as to repeat the audit process of the audit content corresponding to the new execution node in the aforementioned embodiment to verify.
[0128] As the auditor executes the nodes to be audited in sequence, when all the audit contents corresponding to the nodes to be audited are completed, the auditor can submit the audit. Figure 4 As shown in the figure, after the auditor submits the audit, the client can query the verification module for the verification status of all the nodes to be audited of the target audit object; if the verification status of all the nodes to be audited is successful, it means that the audit process for the target audit object is standardized, and the audit results are allowed to be submitted. The data related to the audit results (such as audit results, auditors, audit time, audit objects, etc.) are stored in the data storage, and the audit process for the target audit object ends. If the verification status of the nodes to be audited is not successful, it means that there are nodes to be audited that need to be executed. At this time, the prompt module needs to obtain those nodes to be audited that need to be executed from the verification module, and the aforementioned Figure 4 The audit operation interface shown displays the number of audited nodes that need to be executed, and provides trigger controls so that the auditor can locate the audit content corresponding to the audited nodes that need to be executed in sequence and then conduct the audit.
[0129] In some embodiments, an embodiment of the present application further provides an electronic device, comprising: a processor; a memory for storing processor executable instructions; wherein the processor implements any of the above methods by running the executable instructions.
[0130] For example, Figure 6is a schematic structural diagram of a device provided by an exemplary embodiment. Figure 6 At the hardware level, the device includes a processor 1802, an internal bus 1804, a network interface 1806, a memory 1808, and a non-volatile memory 1810, and may also include hardware required for other scenarios. One or more embodiments of the present application can be implemented based on software, such as the processor 1802 reading the corresponding computer program from the non-volatile memory 1810 into the memory 1808 and then running it. Of course, in addition to the software implementation, one or more embodiments of the present application do not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.
[0131] In some embodiments, the embodiments of the present application further provide a computer-readable storage medium on which computer instructions are stored, and when the instructions are executed by a processor, the steps of any of the methods described above are implemented.
[0132] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
[0133] In some embodiments, the embodiments of the present application further provide a computer program product, including a computer program, which implements the steps of any of the methods described above when executed by a processor.
[0134] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0135] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0136] The terms used in one or more embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present application. The singular forms of "a", "said" and "the" used in one or more embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0137] The above description is merely a preferred embodiment of one or more embodiments of the present application and is not intended to limit one or more embodiments of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present application shall be included in the scope of protection of one or more embodiments of the present application.
Claims
1. A verification method for an audit process, characterized in that: The method comprises: Based on a number of audit contents in the target audit object to be audited, a number of audit nodes to be executed in sequence are constructed; wherein the number of audit nodes correspond to different audit contents respectively, and the execution order of the number of audit nodes corresponds to the audit order of the number of audit contents in the target audit object respectively; Determining the plurality of nodes to be audited as execution nodes in sequence according to the execution order, and acquiring audit action data collected during the audit of audit contents corresponding to the execution nodes; The verification rule corresponding to the execution node is matched from a rule tree of a tree structure constructed based on a verification rule library, and the audit action data is verified according to the verification rule.
2. The method according to claim 1, characterized in that The matching of the verification rule corresponding to the execution node from the rule tree of the tree structure constructed based on the verification rule base includes: The audit content corresponding to the execution node is used as the input of the root node in the rule tree, so as to traverse the rule tree starting from the root node, find the leaf node corresponding to the execution node based on the audit content, and determine the verification rule associated with the found leaf node as the verification rule corresponding to the execution node.
3. The method according to claim 2, characterized in that The verification rule is composed of at least one behavior group rule, the behavior group rule is composed of at least one action rule, and the action rule includes at least one action achievement condition that complies with the standard audit procedure; The tree structure of the rule tree includes a root node, the root node is connected to a first-level node corresponding to the verification rule, the first-level node is connected to at least one second-level node corresponding to at least one behavior group rule constituting the verification rule, the second-level node is connected to at least one leaf node corresponding to at least one action rule constituting the behavior group rule, and the leaf node is associated with at least one action achievement condition included in the action rule that complies with the standard audit procedure.
4. The method according to claim 3, characterized in that The leaf node corresponding to the audit content and the ancestor node of the leaf node both record the unique identifier of the node to be audited corresponding to the audit content; The step of using the audit content corresponding to the execution node as the input of the root node in the rule tree, traversing the rule tree from the root node, searching for a leaf node corresponding to the execution node based on the audit content, and determining the verification rule associated with the found leaf node as the verification rule corresponding to the execution node includes: The unique identifier corresponding to the execution node is used as the input of the root node in the rule tree, so as to traverse the rule tree starting from the root node, find the leaf node corresponding to the execution node based on the unique identifier, and determine the action fulfillment condition associated with the found leaf node as the verification rule corresponding to the execution node.
5. The method according to claim 1, characterized in that The audit content tracking in the target audit object includes a tracking program; the tracking program is triggered and executed by the audit action for the audit content, and the tracking program is used to collect audit action data related to the audit action; The obtaining of the audit action data collected during the audit of the audit content corresponding to the execution node includes: Acquire the audit action data collected by the tracking program during the process of auditing the audit content corresponding to the execution node.
6. The method according to claim 1, characterized in that The data structure corresponding to the node to be audited includes an action field for storing the audit action data; After obtaining the audit action data collected during the audit of the audit content corresponding to the execution node, the method further includes: The audit action data is used as the field value of the action field and stored in the data structure corresponding to the execution node; The verifying the audit action data according to the verification rule includes: According to the verification rule, the audit action data recorded in the action field in the data structure corresponding to the execution node is verified.
7. The method according to claim 6, characterized in that The data structure also includes a status field for recording the verification result; the method also includes: The verification result of the verification rule on the audit action data is used as the field value of the status field and stored in the data structure corresponding to the node to be executed.
8. The method according to claim 6, characterized in that The data structure also includes a location field for recording the location of the audit content in the target audit object; the method also includes: Monitoring data write events for the data structure corresponding to the execution node; If the verification result of the verification field record in the data structure corresponding to the execution node is monitored to be a verification failure, the position of the verification field record in the data structure corresponding to the execution node is obtained, and a prompt for indicating the verification failure is output at the position in the target audit object in the audit content corresponding to the execution node.
9. The method according to claim 7, characterized in that: The data structure also includes a location field for recording the location of the audit content in the target audit object; the method also includes: If it is monitored that the verification result recorded in the verification field in the data structure corresponding to the execution node is a successful verification, then based on the execution order, determine the next node to be reviewed of the execution node; The position of the position field record in the data structure of the next node to be audited is obtained, and the audit content corresponding to the execution node displayed in the audit operation interface is jumped to the audit content corresponding to the next node to be audited corresponding to the position.
10. The method according to claim 9, characterized in that The review operation interface displays the number of remaining unexecuted nodes to be reviewed and a trigger control for jumping to the next node to be reviewed; In response to the triggering operation of the triggering control, based on the execution order, determining the next node to be reviewed of the execution node; The position of the position field record in the data structure of the next node to be audited is obtained, and the audit content corresponding to the execution node displayed in the audit operation interface is jumped to the audit content corresponding to the next node to be audited corresponding to the position.
11. The method according to claim 1, characterized in that: The target audit object to be audited includes the target text to be audited; The method of constructing a plurality of audited nodes to be executed sequentially based on a plurality of audited contents in the target audit object to be audited includes: Based on the text segments in the target text, a plurality of to-be-audited nodes corresponding to different text segments are constructed and executed in sequence.
12. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor implements the method according to any one of claims 1 to 11 by running the executable instructions.
13. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the instruction is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.
14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.