A method and system for bi-directional tracing of audit files

Abstract

The application discloses a kind of two-way tracing method and system of auditing file, belong to enterprise internal auditing management field.The field configuration is received by dynamic form engine, it includes associated draft field name and type identification;When rendering upload component, according to associated draft field name, dynamically generate draft file option list and show;In response to user selection target draft file, its identification is bound to audit problem material associated field, and two-way association is established;When submitting audit implementation stage data, check whether all audit problem materials have bound draft file, if not bound, then prevent submission and prompt.The present application solves the problem that draft and problem material association rely on manual work and are easy to miss, realizes automatic association and integrity check of evidence chain, and improves the accuracy and efficiency of audit data management.

Description

Technical Field

[0001] This invention relates to the field of enterprise internal audit management, and in particular to a two-way traceability method and system for audit documents. Background Technology

[0002] In the field of internal audit management, an audit project typically encompasses multiple stages, including application, preparation, implementation, rectification, and completion, each involving different information collection forms and documentation. Currently, existing audit management systems suffer from the following technical deficiencies: First, the form processing methods are rigid and lack scalability. Existing systems mostly use hard-coded forms for each stage, requiring modification of the front-end code and redeployment when the audit process changes or new steps are added, resulting in long development cycles and high maintenance costs. Although dynamic form solutions exist, they are all general-purpose designs and not optimized for the specific business needs of the audit industry, especially lacking core capabilities such as audit material classification management and working paper traceability.

[0003] Secondly, there is a lack of structured connection between audit working papers and issue materials. On-site audit working papers and issue materials generated during the audit implementation phase are typically managed independently in the existing system. This makes it impossible to trace audit issues back to the original inspection records, resulting in an incomplete chain of evidence. Furthermore, if working papers are mistakenly deleted, the corresponding issues lose supporting materials, making it difficult to quickly locate the original basis for the issues during the rectification phase.

[0004] Third, document type management is rudimentary. Existing systems mostly use a single attachment upload method, failing to categorize documents according to audit stage and purpose. This makes it difficult to effectively distinguish between more than seven categories of documents of varying nature, including audit notices, incoming materials, on-site audit working papers, issue materials, rectification plan attachments, rectification result reports and supporting materials, and lacks a unified classification management mechanism. These deficiencies urgently need to be addressed. Summary of the Invention

[0005] The present invention aims to at least partially solve one of the technical problems in the related art.

[0006] To address this issue, this invention proposes a two-way traceability method for audit documents. This method receives field configurations via a dynamic form engine, including associated working paper field names and type identifiers. During the rendering and upload component, a list of working paper file options is dynamically generated and displayed based on the associated working paper field names. In response to a user selecting a target working paper file, its identifier information is bound to the associated fields of the audit issue materials, establishing a two-way association. When submitting audit implementation data, it verifies whether all issue materials are bound to working paper files; if not, submission is blocked and a prompt is displayed. This invention solves the problem of manual reliance and potential omissions in associating working papers with issue materials, achieving automatic evidence chain association and integrity verification, and improving the accuracy and efficiency of audit data management.

[0007] Another objective of this invention is to propose a two-way traceability system for audit documents.

[0008] To achieve the above objectives, the present invention provides a two-way traceability method for audit documents, comprising: The field configuration is received through the dynamic form engine. The field configuration includes the associated working paper field name used to identify the audit issue material field and the type identifier used to identify the working paper file type. When rendering the upload component for audit issue materials, a list of document file options is dynamically generated from the corresponding document field based on the associated document field name and displayed in the upload component; In response to the user's selection of a target working paper file from the working paper file option list, the identification information of the target working paper file is bound to the associated field of the audit issue material, establishing the association between the audit issue material and the working paper file; When submitting data during the audit implementation phase, verify that all audit issue materials are bound to working papers. If any audit issue materials are not bound, prevent submission and prompt the system with the information of the unbound materials.

[0009] The bidirectional traceability method for audit documents according to an embodiment of the present invention may also have the following additional technical features: In one embodiment of the present invention, receiving field configurations via a dynamic form engine includes: Receive JSON metadata configuration containing field configuration, grouping configuration, form data and validation rules; wherein the field configuration is a two-dimensional array structure, each subarray represents a row of the form, and each element is a complete description object of a field. The complete description object includes field binding name, field display label, field type, grid ratio, whether it is editable, file category identifier, associated draft field name and associated draft file type identifier.

[0010] In one embodiment of the present invention, the field types include eight audit scenario-specific field types: single-line text, multi-line text, single selection of organizational personnel, multiple selection of organizational personnel, multi-file upload, department tree selection, user selection, and date selection; among which, the multi-file upload type is used to support file upload operations associated with working papers.

[0011] In one embodiment of the present invention, a list of draft file options is dynamically generated from the corresponding draft field, including: Read the list of document file IDs and the list of document file names stored in the document field, merge the list of document file IDs and the list of document file names into an option array containing labels and values ​​according to the corresponding positions, and set the option array as a calculated attribute so that it can be automatically recalculated when the document file is changed.

[0012] In one embodiment of the present invention, binding the identification information of the target working paper to the associated field of the audit issue material includes: Based on the file ID of the selected target working paper file, search for the corresponding file record with the type identifier of working paper file in the unified file array, obtain the file name of the corresponding file record, and write the file ID and the file name into the associated working paper file ID field and the associated working paper file name field of the audit issue material, respectively.

[0013] In one embodiment of the present invention, it further includes: When an operation to delete working paper files is detected, the system iterates through all records in the unified file array that are identified as audit issue materials and checks if there is a record with a working paper file ID equal to the working paper file ID to be deleted. If such a record exists, the deletion operation is disabled; otherwise, deletion is allowed.

[0014] In one embodiment of the present invention, it further includes: When the file list changes, an association information mapping table for existing files is constructed using the file ID as the key. All old file records of the same type in the unified file array are removed. File records are regenerated based on the current file ID list. The associated draft file ID and associated draft file name of the existing file records are restored from the association information mapping table.

[0015] In one embodiment of the present invention, the dynamic form engine implements segmented rendering of the form through group configuration. The group configuration includes group titles and a subset of fields referenced by slices from the field configuration. Each group is rendered separately by a title bar with visual identifiers.

[0016] In one embodiment of the present invention, the dynamic form engine is reused between the audit application stage, the audit implementation stage, and the audit rectification stage. Forms for different audit stages are generated by modifying field configurations and grouping configurations without the need to write additional form code.

[0017] To achieve the above objectives, another aspect of the present invention proposes a two-way traceability system for audit documents, comprising: The configuration parsing module is used to receive field configurations through the dynamic form engine. The field configurations include the associated working paper field name used to identify the audit issue material field and the type identifier used to identify the working paper file type. The dynamic rendering module is used to dynamically generate a list of document file options from the corresponding document field based on the associated document field name when rendering the upload component for audit issue materials, and display it in the upload component. The association binding module is used to respond to the user's operation of selecting a target working paper file from the working paper file option list, and bind the identification information of the target working paper file to the association field of the audit issue material, thereby establishing the association relationship between the audit issue material and the working paper file; The submission verification module is used to verify whether all audit issue materials have been bound to the working paper files when submitting data during the audit implementation phase. If there are unbound audit issue materials, the submission will be blocked and the unbound material information will be displayed.

[0018] This invention discloses a method and system for bidirectional traceability of audit documents. It receives field configurations through a dynamic form engine, dynamically generates a list of document options based on the associated document field names, and binds the target document identifier to the associated fields of the audit issue material in response to user selection, establishing a bidirectional association. Upon submission, the system verifies the integrity of the binding to prevent the submission of unbound materials. This effectively solves the problem of broken or missing evidence chains caused by independent management and manual association of documents and issue materials in existing audit systems. It achieves integrated traceability management throughout the entire process, from field configuration parsing, dynamic rendering of the option list, and association binding to submission integrity verification, significantly improving the integrity and traceability of the audit evidence chain and enhancing the adaptability and engineering practical value of the audit system in complex, multi-stage business processes.

[0019] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0020] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart of a bidirectional traceability method for audit documents according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the structure of a two-way traceability system for audit documents according to an embodiment of the present invention. Detailed Implementation

[0021] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0022] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0023] The following describes a bidirectional traceability method and system for audit documents according to an embodiment of the present invention, with reference to the accompanying drawings.

[0024] The core idea of ​​this invention is to address the issues of broken evidence chains and missing connections caused by the independent management of audit working papers and problematic materials. This is achieved by constructing a bidirectional traceability method covering the entire process of "configuration parsing—dynamic rendering—association binding—submission verification." First, a dynamic form engine receives field configurations containing the names and type identifiers of associated working papers. During the rendering and upload component, a list of working paper file options is dynamically generated based on these field names. In response to user selections, the target working paper identifier is bound to the associated field of the problematic material, establishing a bidirectional association. Upon submission, it is verified whether all problematic materials have been bound; if not, the submission is blocked and a prompt is displayed. Through this technical path that integrates dynamic configuration-driven, automatic association binding, and integrity verification, this invention transforms the traditional loose traceability relying on manual intervention into an intelligent method capable of automatically establishing and verifying evidence chains, significantly improving the accuracy and efficiency of audit data management.

[0025] The following describes a bidirectional traceability method and system for audit documents according to an embodiment of the present invention, with reference to the accompanying drawings.

[0026] like Figure 1 As shown, a bidirectional traceability method for audit documents according to the present invention includes the following steps: S1 receives field configurations through the dynamic form engine. The field configurations include the associated working paper field name used to identify the audit issue material field and the type identifier used to identify the working paper file type.

[0027] In one embodiment of the present invention, field configuration is first received through a dynamic form engine. This field configuration is a set of structured descriptive information defining the attributes and behaviors of each field in the form. Its core function is to provide metadata support for subsequent form rendering and business logic processing. Specifically, the field configuration includes at least an associated working paper field name for identifying the audit issue material field and a type identifier for identifying the working paper file type. The associated working paper field name establishes a logical mapping relationship between audit issue materials and working paper files at the field level, indicating the working paper field that should be associated with the audit issue material field. The type identifier distinguishes different types of files, particularly identifying the file type used as a working paper, thus providing a basis for accurately filtering and locating working paper files in the file set. By receiving and parsing this field configuration, the dynamic form engine can determine which fields are involved in working paper-related business and the associated target file type, thereby laying the foundation for dynamically generating associated options during the rendering phase, establishing binding relationships during the data interaction phase, and performing integrity checks during the submission phase. As one implementation, the field configuration can be provided in the form of metadata in JSON format, where the configuration item for the audit issue material field includes an attribute pointing to the working paper field (such as relatedField) and an attribute identifying the working paper file type (such as relatedFieldPublicType). The dynamic form engine can identify the fields that need to be associated with the working paper and their associated targets by parsing these attributes.

[0028] Furthermore, the dynamic form engine component receives a JSON metadata configuration object, which contains four core parts: field configuration, grouping configuration, form data, and validation rules. The field configuration is a two-dimensional array structure, where each subarray represents a row of the form, and each element is a complete description object for a field. This field description object includes: a field binding name (prop), used for two-way binding with attributes in the form data object; a field display label (label), used to display the field name in the form interface; a field type (type), used to specify the type of component to be rendered; a grid width (span), ranging from 0 to 24, used to control the layout width of the field within the row; an editable attribute (editable), used to control the interactive state of the field; a file type identifier (fileType), used to identify the audit file type to which the uploaded file belongs; a related field name (relatedField), used to point to the audit field to generate audit dropdown options; and a related field file type identifier (relatedFieldPublicType), used to find audit file records in the unified file array. The grouping configuration is an array structure, with each element containing a group title (groupTitle) and a subset (datas) referenced from slices in the field configuration, used for segmented form rendering. Form data is a reactive data object, bidirectionally bound to the prop attribute in the field configuration. Validation rules are form validation rule objects, following asynchronous validation specifications. In one possible implementation, field types include eight audit-specific field types: single-line text (input), multi-line text (textarea), single-selection of organization / personnel (org), multi-selection of organization / personnel (multiOrg), multi-file upload (multiUpload), department tree selection (deptSelect), user selection (userSelect), and date selection (datePicker). The multi-file upload type supports file upload operations associated with working papers. When the field type is multiUpload, the fileType attribute in the field description object identifies the audit category of the uploaded file, and the relatedField and relatedFieldPublicType attributes configure the working paper association logic.For example, in the field configuration during the audit implementation phase, line 3 configures the document upload field, with prop set to "auditMaterialFiles", type set to "multiUpload", and fileType set to 3; line 4 configures the audit problem material upload field, with prop set to "auditProblemFiles", type set to "multiUpload", relatedField set to "auditMaterialFiles", relatedFieldPublicType set to 3, and fileType set to 4. The dynamic form engine renders the corresponding upload component based on this field configuration and automatically generates a list of document file options based on the relatedField attribute, allowing the user to select and associate them.

[0029] S2, when rendering the upload component for audit issue materials, dynamically generate a list of document file options from the corresponding document field based on the associated document field name, and display it in the upload component.

[0030] In one embodiment of the present invention, when the upload component for rendering audit issue materials is used, the system dynamically extracts the document information from the file data maintained by the corresponding document field based on the associated document field name pre-defined in the field configuration, and generates a list of selectable document files in real time based on this information. This list is then displayed in the upload component for the user to make an associated selection. Specifically, during initialization or data update, the upload component parses the associated document field name in the field configuration. This field name points to a document field used to store document file identifiers and names. The system reads the currently maintained set of file identifiers and file names in this document field, combines them according to their correspondence, and thus constructs an option list containing the identifiers and display names of each document file. This option list is not static data, but is dynamically associated with the file data in the document field. When the file data in the document field is added, deleted, or changed, the option list is updated synchronously to ensure that the user can always make a selection based on the latest document file status. As one implementation method, the system can parse the file identifier string and file name string in the draft field according to a preset delimiter to generate an identifier array and a name array of equal length, and then merge the two into an array of option objects containing the correspondence between identifiers and names. This array is bound to the draft field as a calculated attribute, thereby realizing the real-time dynamic generation and display of the option list.

[0031] Furthermore, firstly, when the dynamic form engine renders the upload component for audit issue materials, it detects that the field configuration contains an attribute related to the document field name, such as the document field "auditMaterialFiles". At this point, the engine reads the document file identification information stored in this document field. Specifically, the data structure of this document field contains a list of document file IDs and a list of document file names. For example, the document file ID list is the string "file001,file002", and the document file name list is the string "document A.pdf, document B.pdf". The engine parses these two strings into two equal-length arrays separated by commas: an array of document file IDs and an array of document file names. Subsequently, the engine merges these two arrays at corresponding positions to generate an array of options containing labels and values. Each option object's label is the document file name, and its value is the corresponding document file ID. For example, the generated option array is [{label: "document A.pdf", value: "file001"}, {label: "document B.pdf", value: "file002"}]. The option array is set as a computed property, and its calculation logic depends on the data source of the "Document" field. When a user adds or deletes a document file in the document upload component, the document file ID list and document file name list in the document field are updated in real time, triggering the automatic recalculation of this computed property. This ensures that the document file option list in the audit issue material upload component is updated synchronously without requiring the user to manually refresh or reload the page. Through the above processing, the engine converts the raw data of the document field into structured option data that can be directly used in the dropdown selection component, and ensures the real-time consistency between the option list and changes to the document files.

[0032] S3, in response to the user's operation of selecting a target working paper file from the working paper file option list, binds the identification information of the target working paper file to the associated field of the audit issue material, and establishes the association between the audit issue material and the working paper file.

[0033] In one embodiment of the present invention, after receiving a selection operation made by the user from a dynamically generated list of working paper options, the system responds to the selection operation by binding the identification information of the target working paper file specified by the user with the audit issue material to be processed, thereby establishing a structured association between the two. Specifically, this association is established by writing the unique identification information of the target working paper file into the association field corresponding to the audit issue material. This association field is used to store the mapping relationship between the working paper file and the working paper file. As one implementation method, when the user selects a working paper file from the working paper option list in the audit issue material upload component, the system searches for the working paper file record corresponding to the selected identification information in the working paper file list according to the selection operation, and writes the identification information (such as file ID) and file name of the working paper file into the preset association field in the audit issue material file record, such as the associated working paper file identification field and associated working paper file name field of the issue file record, thereby completing the binding of the association. Through the above technical means, the accurate association between audit issue materials and working paper files is realized, providing a data foundation for subsequent traceability and verification.

[0034] Furthermore, when a user selects a target working paper file from the dynamically generated list of working paper file options in the audit issue material upload component, the system first obtains the file ID of that target working paper file. Then, using this file ID as the query key, the system searches the `auditInfoFile` array, which stores all audit files, for the corresponding file record whose type identifier (`type`) equals the associated working paper file type identifier (`relatedFieldPublicType`). For example, if the value of `relatedFieldPublicType` is 3, the system filters all records in the `auditInfoFile` array where `type` equals 3, and matches the record whose file ID matches the target working paper file ID. If a match is found, the system extracts the corresponding file name from that record. Next, the system writes the obtained file ID and file name of the target working paper file into the associated working paper file ID field (`problemBindFileId`) and the associated working paper file name field (`problemBindFileName`) of the current audit issue material file record, respectively. Through the above processing, the system establishes a structured relationship between audit issue materials and working paper files. This relationship is persistently stored in the auditInfoFile array, providing a data foundation for subsequent working paper deletion protection, mandatory verification upon submission, and incremental retention of related information.

[0035] S4. When submitting data during the audit implementation phase, verify whether all audit issue materials have been bound to working papers. If there are unbound audit issue materials, prevent submission and prompt the user with information about the unbound materials.

[0036] In one embodiment of the present invention, when submitting data during the audit implementation phase, the system performs a completeness check on the association between audit issue materials and working papers. This check aims to ensure that all uploaded audit issue materials have established a valid association with their corresponding working papers, thereby guaranteeing the integrity and traceability of the audit evidence chain. Specifically, after receiving a submission request, the system first identifies and retrieves all audit issue material records involved in the current audit implementation phase. These records are typically stored in an audit file array with a unified data structure and distinguished by specific type identifiers. Subsequently, the system checks each audit issue material record one by one to see if it contains identification information indicating its associated working paper. This identification information can be a unique identifier or storage path of the working paper, or other data that can uniquely identify the working paper. If any audit issue material record lacks this association identification information, it indicates that the material has not yet been associated with any working paper, and the system determines that the check has failed and prevents the current submission operation from proceeding. At the same time, the system generates and outputs a prompt message, which at least includes the name or identifier of the audit issue materials that are not bound to working papers, so that the user can clearly know which materials need to be associated. The system only allows submission to proceed if all audit issue material records contain valid associated identification information. As one implementation, upon submission, the system iterates through the audit file array, checking each record identified as an audit issue material and verifying that its associated working paper file identifier field is empty. If an empty value is found, submission is blocked, and the system displays the specific filename.

[0037] Furthermore, the two-way traceability and association mechanism for audit documents and problematic materials includes five sub-mechanisms: dynamic generation of association options, binding of association relationships, protection against document deletion, mandatory validation upon submission, and incremental retention of association information. In the dynamic generation of association options, when the form engine renders the upload component for audit problematic materials, it checks whether the field configuration contains the `relatedField` attribute. If it exists, a corresponding document column is automatically added to the file list. The document field pointed to by `relatedField`, such as `auditMaterialFiles`, is read, and its `ids` and `names` fields are parsed. Specifically, the `ids` field stores a list of document file IDs, such as "file001,file002", and the `names` field stores a list of document file names, such as "document A.pdf, document B.pdf". The two strings are split into two equal-length arrays by a comma, and then merged into an array of options containing labels and values, for example, `[{label: "document A.pdf", value: "file001"}, {label: "document B.pdf", value: "file002"}]`. This array of options is set as a computed property and updates in real time as the document file is uploaded or deleted. In the association binding process, when a user selects a working paper file in the corresponding working paper column of the audit issue materials, the system searches for the corresponding file record with the type identifier of working paper file type (type equal to 3) in the unified file array based on the selected working paper file ID, and obtains the file name of that record. Then, the working paper file ID and file name are written into the problemBindFileId and problemBindFileName fields of the issue file record, respectively. This triggers the data synchronization process, synchronizing the updated association relationships to the unified auditInfoFile array. In the working paper deletion protection process, when a user attempts to delete a working paper file, the system performs a reference check. It iterates through all records in the auditInfoFile array with type equal to 4 (audit issue materials) and checks if there is a record with problemBindFileId equal to the working paper file ID to be deleted. If a reference relationship exists, the delete button for that working paper file is disabled, preventing the deletion operation. If no reference relationship exists, deletion is allowed. In the mandatory validation upon submission, a working paper association integrity check is performed upon submission during the audit implementation phase. Filter all audit issue material records in `auditInfoFile` with `type` equal to 4, and check if `problemBindFileId` is empty for each record. If any issue material is not associated with working papers, prevent submission and display the specific filename. Submission is only allowed after all audit issue materials have been associated with working papers. In incremental retention of association information, incremental updates are performed via a data synchronization function when the file list changes. A mapping table of association information for existing files is constructed using `fileId` as the key; this mapping table is a Map structure.Remove all old file records of the same type from the unified file array. Regenerate file records based on the current file ID list, and restore the problemBindFileId and problemBindFileName of existing file records from the association information mapping table. The association information for newly added file records is empty by default, waiting for user binding.

[0038] Additionally, the method in this embodiment of the invention further includes: Step 1: Build a metadata configuration-driven dynamic form engine.

[0039] Design a dynamic form engine component (BasicFormItem) based on JSON metadata configuration, which accepts the following configuration parameters: (1) Field configuration (fields) `fields` is a two-dimensional array structure, where each subarray represents a row of the form, and each element is a complete description object for a field. The field description object contains the following properties: prop: Field binding name; label: Field display label; type: Field type; span: Grid ratio (0-24); editable: Whether it is editable; fileType: File category identifier (file upload type only); relatedField: Related draft field name (problem material type only); relatedFieldPublicType: Related draft file type identifier; disablePastDate: Whether to disable historical dates (date type only); width: Component width.

[0040] The `type` parameter supports eight field types specific to different audit scenarios: `input` — single-line text (for read-only display of audit objects, responsible units, etc.); `textarea` — multi-line text (for large blocks of text such as audit rectification suggestions); `org` — single selection of organizational personnel (for selection of audit team leaders and approvers); `multiOrg` — multiple selection of organizational personnel (for selection of audit team members); `multiUpload` — multiple file upload (core type, supports document association); `deptSelect` — department tree selection (for selection of audit object departments); `userSelect` — user selection (for selection of personnel associated with departments); `datePicker` — date selection (for setting rectification completion deadlines).

[0041] (2) Group configuration (groups).

[0042] The `groups` array structure contains: `groupTitle`: group title (e.g., "Rectification Assignment Information", "Material Upload"); `datas`: a subset referenced from slices of `fields`; the group configuration enables segmented rendering of the form, with each group separated by a title bar with visual identifiers.

[0043] (3) Form Data and Validation Rules `formData` is a reactive data object that is two-way bound to the `prop` attribute in the field configuration. `formRules` is a form validation rule object that follows asynchronous validation specifications.

[0044] Step 2: Establish a classification management system for audit documents.

[0045] Design a 7-level classification system for audit documents based on type identifiers (type). Each file record uses a unified data structure: auditInfoId: Audit project ID; fileId: File storage ID; fileName: File name; type: File type identifier (1-7); problemBindFileId: Associated working paper file ID; problemBindFileName: Associated working paper file name; uploader: Uploader; uploadTime: Upload time.

[0046] All file types are stored uniformly in the `auditInfoFile` array, with the `type` field distinguishing the categories. The front end automatically categorizes and displays the files based on the configuration.

[0047] Step 3: Implement a two-way traceability and association mechanism between the draft and the problematic materials.

[0048] (3.1) Associated options are dynamically generated.

[0049] When the form engine renders the "Audit Issue Materials" upload component, it checks whether the field configuration contains the relatedField attribute. If it does, it automatically adds a "Corresponding Document" column to the file list. It reads the document field (such as auditMaterialFiles) pointed to by relatedField, parses its ids and names fields, and generates a document drop-down list. The document option list is a computed property that updates in real time as document files are uploaded or deleted.

[0050] (3.2) Binding of association relationships.

[0051] When a user selects a working paper file in the "Corresponding Working Paper" column of the audit issue materials: based on the selected working paper fileId, the corresponding file record is found in the working paper file list (type=3); the working paper fileId and fileName are written into the problemBindFileId and problemBindFileName fields of the issue file record; the data synchronization process is triggered to synchronize the updated association to the unified auditInfoFile array.

[0052] (3.3) Draft deletion protection mechanism.

[0053] When a user attempts to delete a working document file, the system performs a reference check: it iterates through all records in the auditInfoFile array with type=4 (audit issue materials); checks if there is a record where problemBindFileId is equal to the fileId of the working document to be deleted; if a reference relationship exists, the delete button for that working document file is disabled, preventing the deletion operation; if no reference relationship exists, deletion is allowed.

[0054] (3.4) Forced validation upon submission.

[0055] When submitting during the audit implementation phase, perform a working paper association integrity check: filter all audit issue material records with type=4 in auditInfoFile; check if the problemBindFileId of each record is empty; if there are issue materials that are not associated with working papers, prevent submission and prompt for the specific file name; only after all audit issue materials have been associated with working papers can submission be allowed.

[0056] (3.5) Incremental retention of related information.

[0057] When the file list changes (files are added or deleted), incremental updates are performed through the data synchronization function syncAuditInfoFileFromProp: a mapping table (Map structure) of association information for existing files is built using fileId as the key; old records of the same type of file are removed; file records are regenerated based on the current file ID list, and existing association information (problemBindFileId, problemBindFileName) is restored from the mapping table; the association information for newly added file records is empty by default, waiting for user binding.

[0058] Step 4: Enable the reuse of form configurations across audit phases.

[0059] Through the configurable design of the dynamic form engine, the same engine component can be reused for forms at different stages of an audit project: Audit application stage: Use the BasicFormItem component to configure basic information fields (project name, type, object, planned time, etc.) and pre-audit material upload fields (audit notification type=1, on-site materials type=2); Audit implementation stage: Use the BasicFormItem component to configure implementation information fields (responsible unit, rectification deadline, etc.) and implementation material upload fields (on-site audit materials type=3, audit issue materials type=4, including working paper association configuration); Audit rectification stage: Use the BasicFormItem component to configure rectification plan / result fields and rectification material upload fields (rectification plan attachment type=5, rectification result report type=6, supporting materials type=7).

[0060] The three stages reuse the same form engine, and different forms can be generated simply by modifying the fields and groups configuration, without writing any additional form code.

[0061] The method of this invention, compared to the shortcomings of existing technologies that lack structured association between audit working papers and problem materials and rely on manual memory for tracing, receives field configurations containing associated working paper field names and working paper file type identifiers through a dynamic form engine. When rendering the audit problem material upload component, it dynamically generates a list of working paper file options from the corresponding working paper fields based on the associated working paper field names and displays it in the upload component. In response to user selection operations, it binds the target working paper file identifier to the associated field of the audit problem material, establishing a structured association between the two. When submitting audit implementation data, it forcibly verifies whether all audit problem materials are bound to working paper files. If any are not bound, it blocks submission and prompts the user with information about the unbound materials. This method achieves automatic generation and real-time updating of working paper association options through configuration-driven implementation. Combined with deletion protection, submission verification, and incremental retention mechanisms, it forms a complete traceability closed loop from field configuration, dynamic rendering, association binding to submission verification. This effectively eliminates omissions and errors caused by manual association, significantly improves the automation level and evidence chain integrity of audit working paper tracing, and enhances the data consistency and engineering practicality of the audit system in complex project scenarios.

[0062] In addition, the system of the present invention embodiment has an overall architecture that, from top to bottom, includes a front-end page layer, a dynamic form engine, a document classification and manuscript traceability module, and a back-end audit service interface layer.

[0063] The front-end page layer includes an audit application page, an implementation page, and a rectification page, corresponding to the three stages of the entire audit project process. Each page communicates with a dynamic form engine (BasicFormItem), which receives four input parameters: a two-dimensional array of fields (fields), grouping configuration (groups), a form data object (formData), and a validation rule object (formRules). It supports eight field types: input, textarea, org, multiOrg, multiUpload, deptSelect, userSelect, and datePicker, and dynamically renders visual form components according to the configuration.

[0064] The engine output connects to the document classification and working paper traceability module. This module maintains a unified file array (auditInfoFile), which distinguishes audit notices, incoming materials, on-site audit materials (working papers), audit issue materials, rectification plan attachments, rectification result reports, and supporting materials through type identifier fields (type=1 to 7). Among them, on-site audit materials (type=3) and audit issue materials (type=4) are bound together by the association field (problemBindFileId), allowing audit issues to be traced back to the original working papers, forming an evidence chain index.

[0065] The backend audit service provides six core API interfaces: create audit information ( / createAuditInfo), modify audit information ( / modifyAuditInfo), query audit details ( / queryAuditInfoById), submit audit implementation ( / subProjectImplementation), submit remediation plan ( / subProjectRemedicationAction), and submit remediation result ( / subProjectRemedicationResult), covering the complete data operations of an audit project from project initiation to rectification closure.

[0066] The system in this embodiment of the invention achieves multi-scenario adaptation through parameterized form configuration without modifying the front-end code; eliminates the problem of scattered files through unified file classification management; enables automatic traceability of working papers through associated fields, ensuring the integrity of the evidence chain; and improves scalability through interface decoupling. This architecture effectively enhances the flexibility, traceability, and maintenance efficiency of the audit system.

[0067] Furthermore, this invention takes the audit implementation stage as an example to describe in detail the specific implementation of the above-mentioned two-way traceability method for audit documents, but the scope of protection of this invention is not limited thereto.

[0068] First, the form structure for the audit implementation phase is defined through a field configuration array. This array is a two-dimensional structure, with each row containing several field description objects. The "Document Upload" field is configured with multiple file upload types and a file category identifier (type=3) for uploading on-site audit materials. The "Audit Issue Material Upload" field is also configured with multiple file upload types, and additionally configured with a related document field name and a related document file type identifier (type=3). The former points to the document field, and the latter is used to filter document records from a unified file array. Simultaneously, the system receives a grouping configuration array, dividing the fields into two areas: "Rectification Assignment Information" and "Material Upload," which are then rendered in segments by the dynamic form engine based on the grouping.

[0069] During the form rendering phase, when the engine processes the audit issue material upload component, it detects that the field configuration contains a related working paper field name, thus triggering the dynamic generation logic of the working paper association options. The engine reads the file identifier list and file name list stored in the pointed-to working paper field, parses them into equal-length arrays by the delimiter, and then merges them into an array of option objects. This array is set as a computed property and is automatically updated as working paper files are added or deleted, thereby ensuring the real-time consistency between the option list and the working paper data status.

[0070] When a user selects the target working paper file in the corresponding working paper drop-down box in the upload component for audit issue materials, the system responds to this selection operation by locating the current issue material record and the target working paper record in the unified file array, and writes the file identifier and file name of the target working paper into the associated fields (problemBindFileId and problemBindFileName) of the issue material record, thereby establishing a structured association between the issue material and the working paper.

[0071] When a user attempts to delete a working paper file, the system performs a pre-deletion reference check. It iterates through all audit issue material records in the unified file array, verifying whether the associated working paper file identifier is equal to the identifier of the working paper to be deleted. If a reference exists, the delete button is disabled, preventing the deletion operation. The user must first unlink or delete the referenced issue material before deleting the working paper, thus maintaining the consistency of associated references.

[0072] During the audit implementation phase, when data is submitted, the system performs a working paper association integrity check, filtering all audit issue material records and checking whether their associated working paper file identifiers are empty. If there are records without associated working papers, submission is blocked and the specific name of the unassociated material is displayed. Submission is only allowed after all issue materials have been associated.

[0073] Furthermore, the system implements an incremental retention mechanism for associated information. When the list of working papers or problem materials changes (additions or deletions), a data synchronization function constructs a mapping table of associated information for existing files using file identifiers as keys. Then, old records of the same type are removed, and new records are regenerated based on the current file list. Simultaneously, existing associated information is restored from the mapping table. Newly added records are left with empty associations by default. This process ensures that other types of file records are unaffected, and existing binding relationships are seamlessly migrated when the list is updated.

[0074] The above implementation methods cover the complete process from field configuration, dynamic rendering, association binding, deletion protection, submission verification to incremental retention, which fully verifies the effectiveness and reliability of the method of the present invention in achieving bidirectional traceability of working papers and problem materials during the audit implementation stage.

[0075] To achieve the above invention, such as Figure 2 As shown, this embodiment also provides a two-way traceability system 10 for audit documents, which includes: The configuration parsing module 100 is used to receive field configurations through the dynamic form engine. The field configurations include the associated working paper field name used to identify the audit issue material field and the type identifier used to identify the working paper file type.

[0076] The dynamic rendering module 200 is used to dynamically generate a list of document file options from the corresponding document field based on the associated document field name when rendering the upload component for audit issue materials, and display it in the upload component.

[0077] The association binding module 300 is used to respond to the user's operation of selecting a target working paper file from the working paper file option list, bind the identification information of the target working paper file to the association field of the audit issue material, and establish the association relationship between the audit issue material and the working paper file.

[0078] The submission verification module 400 is used to verify whether all audit issue materials have been bound to the working paper files when submitting data during the audit implementation phase. If there are unbound audit issue materials, the submission will be blocked and the unbound material information will be displayed.

[0079] The system of this invention effectively eliminates omissions and errors caused by manual correlation, significantly improves the completeness and reliability of audit working paper traceability, and enhances the data consistency and engineering practical value of the audit system in complex project scenarios.

[0080] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0081] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

Claims

1. A method for bidirectional traceability of audit documents, characterized in that, include: The field configuration is received through the dynamic form engine. The field configuration includes the associated working paper field name used to identify the audit issue material field and the type identifier used to identify the working paper file type. When rendering the upload component for audit issue materials, a list of document file options is dynamically generated from the corresponding document field based on the associated document field name and displayed in the upload component; In response to the user's selection of a target working paper file from the working paper file option list, the identification information of the target working paper file is bound to the associated field of the audit issue material, establishing the association between the audit issue material and the working paper file; When submitting data during the audit implementation phase, verify that all audit issue materials are bound to working papers. If any audit issue materials are not bound, prevent submission and prompt the system with the information of the unbound materials.

2. The method as described in claim 1, characterized in that, Receive field configurations via a dynamic form engine, including: Receive JSON metadata configuration containing field configuration, grouping configuration, form data and validation rules; wherein the field configuration is a two-dimensional array structure, each subarray represents a row of the form, and each element is a complete description object of a field. The complete description object includes field binding name, field display label, field type, grid ratio, whether it is editable, file category identifier, associated draft field name and associated draft file type identifier.

3. The method as described in claim 2, characterized in that, The field types include eight special field types for audit scenarios: single-line text, multi-line text, single selection of organization personnel, multiple selection of organization personnel, multiple file upload, department tree selection, user selection, and date selection. The multiple file upload type is used to support file upload operations associated with drafts.

4. The method as described in claim 1, characterized in that, Dynamically generate a list of draft file options from the corresponding draft fields, including: Read the list of document file IDs and the list of document file names stored in the document field, merge the list of document file IDs and the list of document file names into an option array containing labels and values ​​according to the corresponding positions, and set the option array as a calculated attribute so that it can be automatically recalculated when the document file is changed.

5. The method as described in claim 1, characterized in that, Bind the identification information of the target working papers to the associated fields of the audit issue materials, including: Based on the file ID of the selected target working paper file, search for the corresponding file record with the type identifier of working paper file in the unified file array, obtain the file name of the corresponding file record, and write the file ID and the file name into the associated working paper file ID field and the associated working paper file name field of the audit issue material, respectively.

6. The method as described in claim 1, characterized in that, Also includes: When an operation to delete working paper files is detected, the system iterates through all records in the unified file array that are identified as audit issue materials and checks if there is a record with a working paper file ID equal to the working paper file ID to be deleted. If such a record exists, the deletion operation is disabled; otherwise, deletion is allowed.

7. The method as described in claim 1, characterized in that, Also includes: When the file list changes, an association information mapping table for existing files is constructed using the file ID as the key. All old file records of the same type in the unified file array are removed. File records are regenerated based on the current file ID list. The associated draft file ID and associated draft file name of the existing file records are restored from the association information mapping table.

8. The method as described in claim 1, characterized in that, The dynamic form engine uses grouping configuration to render forms in segments. Grouping configuration includes group titles and subsets of fields referenced by slices from field configuration. Each group is rendered with a title bar that has a visual identifier.

9. The method as described in claim 1, characterized in that, The dynamic form engine can be reused across the audit application, audit implementation, and audit rectification phases. It generates forms for different audit phases by modifying field and group configurations, without the need to write additional form code.

10. A two-way traceability system for audit documents, characterized in that, include: The configuration parsing module is used to receive field configurations through the dynamic form engine. The field configurations include the associated working paper field name used to identify the audit issue material field and the type identifier used to identify the working paper file type. The dynamic rendering module is used to dynamically generate a list of document file options from the corresponding document field based on the associated document field name when rendering the upload component for audit issue materials, and display it in the upload component. The association binding module is used to respond to the user's operation of selecting a target working paper file from the working paper file option list, and bind the identification information of the target working paper file to the association field of the audit issue material, thereby establishing the association relationship between the audit issue material and the working paper file; The submission verification module is used to verify whether all audit issue materials have been bound to the working paper files when submitting data during the audit implementation phase. If there are unbound audit issue materials, the submission will be blocked and the unbound material information will be displayed.

Images