Structured document data consistency full-link management and control system and method, storage medium and computer program product

Abstract

The invention provides a structured document data consistency full-link management and control system and method, a storage medium and a computer program product. The system comprises a structured document template creation module, a field mapping table construction module, a structured document instance generation module, a dynamic data storage module and an approval module. According to the method and the device, standardization and normalization of structured document creation can be realized, document creation efficiency is improved, through structuring of key fields of the document, time for manual document approval is shortened, approval efficiency is improved, and data consistency of a whole chain is realized.

Description

Technical Field

[0001] This invention belongs to the field of document management technology, specifically relating to a structured document data consistency end-to-end control system, method, storage medium, and computer program product. Background Technology

[0002] Structured documents such as contracts, official documents, reports, agreements, and archives are normative documents with a clear purpose. Data consistency is one of their core elements. Only when all parties agree and the content has not been tampered with can their validity, legal effect, or decision-making reference value be guaranteed. If there are inconsistencies or changes in the content of structured documents, the documents may become invalid, disputes may arise, or the accuracy of decision-making may be affected.

[0003] However, traditional structured document processing methods often suffer from the pain point of data inconsistency. For example, structured documents are edited offline using Word or PDF, requiring manual data entry into the business system. The data has two sources: the document text and the system input, which can easily lead to data deviations and require a lot of manpower for consistency verification. At the same time, manually edited documents lack a unified data verification standard and are easily tampered with, further exacerbating the risk of data inconsistency.

[0004] In this context, there is an urgent need for a structured document data consistency management solution that can achieve data collection once and reuse throughout the entire process by building a unified data flow link, thus ensuring the data consistency of structured documents from the source. Summary of the Invention

[0005] To address the aforementioned problems in the background technology, this invention proposes a structured document data consistency end-to-end management system, method, storage medium, and computer program product.

[0006] A structured document data consistency end-to-end management system for achieving one of the objectives of this invention is characterized by comprising:

[0007] Structured document template creation module: used to create structured document templates according to structured document types; the structured document template includes a structured document template and a structured document form. The structured document template is used to store fixed data that will not change, and reserves blank spaces for storing dynamic data that will change. Each blank space is set with a unique bookmark code; the structured document form is used to collect the dynamic data.

[0008] Field mapping table construction module: Used to construct a field mapping table based on bookmark codes to represent the mapping relationship between structured document form fields, bookmark codes, and database fields storing dynamic data;

[0009] The structured document instance generation module is used to fill the blank positions with collected dynamic data based on bookmark codes, generate structured document instances with a set format, and bind the structured document instances with document identifiers that uniquely identify document instances and document types to the document server. In this invention, a database table is designed for each structured document type. The correspondence between document types and database tables can be predefined directly in the program, or the correspondence table can be stored in the database table. There is no limitation on this.

[0010] Dynamic data storage module: Used to store all collected dynamic data into database tables of corresponding types according to field mapping tables.

[0011] Furthermore, it also includes an approval module, which uses document identifiers as indexes to extract dynamic data corresponding to document identifiers from a database table, fills the corresponding approval process form fields according to a predefined mapping relationship, and generates an approval process form; it extracts the structured document instance corresponding to the document identifier from the document server as an attachment to the approval process form for approval; when the approval process form is approved, the status corresponding to the dynamic data is changed to "approved," and the approved structured document instance is archived and stored. It can be understood that a database table can store multiple records (or instance records), each record corresponding to all dynamic data of a document; each record includes a status identifier: such as "approved," "approved," "confirmed," or "not confirmed."

[0012] Furthermore, it also includes a collaborative confirmation module, which uses document identifiers as indexes to extract instance records with an approved status from the database table and populates them into the corresponding confirmation process form fields to generate a confirmation process form; it then sends the structured document instances corresponding to the instance records with an approved status from the document server as attachments to the confirmation process form to the other party for collaborative confirmation, modifies the status of the collaboratively confirmed instance records to confirmed, and archives and stores the confirmed structured document instances.

[0013] Furthermore, it also includes an electronic signature module, which uses document identifiers as indexes to extract structured document instances with document identifier statuses of confirmed or approved from the document server, transmits them to the electronic signature system to complete the electronic signature operation, and archives and stores the signed structured document instances.

[0014] Furthermore, in the dynamic data storage module, the complete dynamic data collected from a structured document form corresponds to an instance in the database table, and each instance uses the document identifier as the primary key.

[0015] Furthermore, the database table also includes a document type identifier field, which forms a composite index with the instance records that use the document identifier as the primary key.

[0016] Furthermore, the database table contains the fields and data type constraints required for this document type, and the fields of the database table correspond one-to-one with the corresponding bookmark codes.

[0017] Furthermore, the naming rules for the bookmark code include document type and field semantics, and the corresponding document type can be obtained by parsing the bookmark code.

[0018] Furthermore, it also includes a metadata dictionary, used to record the bookmark code, the corresponding dynamic field name, the field data type, and the field constraint rules; the field mapping table is associated with the metadata dictionary, and when the field attributes in the metadata dictionary are modified, the field mapping table is triggered to be updated synchronously.

[0019] Furthermore, when structured document forms collect dynamic data, they use bookmark codes to call constraint rules in the metadata dictionary to validate user input data, including: required field validation, format validation, and value range validation. Only data that passes the validation can be submitted.

[0020] Furthermore, methods for generating structured document instances include:

[0021] Obtain the dynamic data filled in by the user, and perform format validation on the dynamic data according to the field constraint rules in the metadata dictionary;

[0022] After successful verification, the dynamic data is written into the database table corresponding to the structured document type according to the field mapping table.

[0023] Based on the bookmark codes in the field mapping table, the corresponding dynamic data is extracted from the database table and filled into the corresponding bookmark positions of the structured document template to generate a structured document instance with a set format.

[0024] Furthermore, the method for synchronizing the field mapping table and the metadata dictionary includes: when a field attribute in the metadata dictionary is modified, a preset trigger is triggered; the trigger automatically updates the attribute configuration of the corresponding field in the field mapping table according to the modified field attribute; after the update is completed, an update success flag is returned; if the update fails, an alarm log is generated and the administrator is notified, and the modification permission of the metadata dictionary is locked until the update is completed.

[0025] The technical advantages of separating the field mapping table from the structured document metadata dictionary include: It enables the separation of data routing management and data attribute rule management. The two are linked through bookmark codes. The field mapping table focuses on establishing the correspondence between form fields, bookmark codes, and database fields, while the metadata dictionary focuses on recording the data types and constraint rules corresponding to the bookmark codes. This clear logical boundary facilitates quick identification of the causes of data flow anomalies. Adjustments to data constraint rules only require modification of the metadata dictionary, without altering the field mapping table, reducing rule change costs. Furthermore, the same rule can be reused in mapping relationships across different document types, avoiding data redundancy and ensuring consistency across the entire process. Data can be validated throughout the entire process by calling the unified rules of the metadata dictionary through bookmark codes, ensuring data consistency from the source.

[0026] A method for end-to-end control of structured document data consistency to achieve the second objective of this invention includes:

[0027] A structured document template is created based on the structured document type. The structured document template includes a structured document template and a structured document form. The structured document template is used to store fixed data that will not change, and reserves blank spaces for storing dynamic data that will change. Each blank space is set with a unique bookmark code. The structured document form is used to collect the dynamic data.

[0028] A field mapping table is constructed based on bookmark codes to represent the mapping relationship between structured document form fields, bookmark codes, and database table fields storing dynamic data;

[0029] All collected dynamic data is stored in database tables of corresponding types according to field mapping tables;

[0030] Based on the bookmark code, the collected dynamic data is filled into the blank position to generate a structured document instance with a set format, and the structured document instance is bound and stored with a document identifier that uniquely identifies the document instance.

[0031] A non-transitory computer-readable storage medium storing a computer program is provided to achieve the third objective of the present invention. The computer program, when executed by a processor, implements the steps of the structured document data consistency end-to-end control method.

[0032] A computer program product for achieving the fourth objective of the present invention includes a computer program / instruction that, when executed by a processor, implements the steps of the structured document data consistency end-to-end management method.

[0033] The beneficial effects of this invention include:

[0034] This invention enables the standardization and normalization of structured document creation, improves document creation efficiency, reduces the time for manual document approval by structuring key document fields, improves approval efficiency, and achieves data consistency across the entire chain. Attached Figure Description

[0035] Figure 1 This is a structural schematic diagram of an embodiment of the system described in this invention. Detailed Implementation

[0036] The following detailed embodiments are provided to explain the technical solutions of the present invention, so that those skilled in the art can understand the present invention. The scope of protection of the present invention is not limited to the following specific embodiments. Any modifications or improvements made by those skilled in the art that incorporate the technical solutions of the present invention but differ from the following detailed embodiments are also within the scope of protection of the present invention.

[0037] This invention provides a method for end-to-end control of structured document data consistency, including structured document creation, structured document approval, structured document collaborative confirmation, and electronic structured document stamping. The structured document can be a contract, or a fixed-format work report, official document, agreement, etc.

[0038] This method embodiment includes the following steps:

[0039] Step S1: Create a structured document.

[0040] Different structured document templates are created based on different structured document types (such as official documents, reports, agreements, archives, etc.). The structured document templates include structured document templates and structured document forms. The structured document templates are used to store fixed data that will not change, such as the format clauses of official documents and the header structure of reports, and reserve blank spaces for storing dynamic data that will change. Each blank space is assigned a unique bookmark code. The structured document forms are used to collect the dynamic data, such as the issuing unit of official documents and the specific values ​​of reports. The dynamic data is collected through an H5 page (i.e., a web interface based on HTML5 technology). A structured document with a set document format, such as PDF format, is generated based on the structured document templates and the dynamic data.

[0041] A field mapping table is constructed based on bookmark codes to represent the mapping relationship between structured document form fields, bookmark codes, and database fields storing dynamic data; as shown in Table 1 below:

[0042] Table 1

[0043] Structured document form fields Bookmark code Database table (ht) fields Company Name of Party A HT_JFGSMC companyA_name Company A's address HT_JFGSDZ companyA_addr Company Name of Party B HT_YFGSMC companyB_name Company address of Party B HT_YFGSDZ companyB_addr Contract subject matter quantity HT_BDSL contract_quantity Total contract amount HT_ZJE total_amount

[0044] In one embodiment, the structured document interface program collects the field values ​​filled in by the user on the H5 page in real time, and stores the dynamic data into the corresponding fields of the data table in the document database according to the database field names associated with the field mapping table; at the same time, based on the bookmark code, the collected dynamic data is filled into the blank positions reserved in the structured document template to generate a structured document instance with a set format, and the structured document instance is bound to a document identifier that uniquely identifies the document instance and the document type and stored in the document server;

[0045] The generated structured document instance is bound to the document identifier and stored in the specified directory of the document server.

[0046] The structured document interface program uses the RESTful protocol to implement data transmission and supports data collection, verification, storage, and query functions. Specifically, it uses JSON format to transmit data, and the request parameters include document identifier, document type identifier, and dynamic field data. The response status includes: success, parameter error, and server error. The timeout retry count is set to 3 times, with each retry interval set to 1 second. The number of retry counts and the interval time can be adjusted according to actual needs.

[0047] In one embodiment, the directory structure of the document server is: / document type identifier / creation year / creation month / , such as the contract document storage path being / HT / 2026 / 01 / ; the interface program accesses the system via key authentication, and the key is stored in the system configuration file.

[0048] In one embodiment, the method for generating the structured document template includes:

[0049] The process involves processing the structured document template in Word format. For content that changes within the document, Word bookmarks are created, each with a globally unique bookmark code. The naming convention for these bookmark codes is the document type abbreviation plus a dynamic field semantic abbreviation, ensuring that bookmark codes for different structured document types are unique. Once all bookmarks for the document are created, they are imported into the system's structured document template library to form a standardized structured document template. Simultaneously, the bookmark codes, document database field names, and structured document form fields are entered into a field mapping table, completing the association configuration among the three.

[0050] In one embodiment, the structured document template library is an independent storage module of the system, which uses folders to classify and store different types of WORD templates, and supports the addition, modification and deletion of templates.

[0051] In one embodiment, the method further includes constructing a metadata dictionary for constraining the data, the construction method comprising:

[0052] Bookmark codes, corresponding dynamic field names, field data types, and field constraint rules are entered into the metadata dictionary to form a globally unified structured document data standard. The field constraint rules include the value range restrictions for numeric fields, the format requirements for date fields, the length constraints for character fields, and the required attribute identifiers for fields.

[0053] In one embodiment, the field mapping table is associated with the metadata dictionary. When a field attribute in the metadata dictionary is modified, the field mapping table is triggered to update synchronously. The synchronization update is implemented through a trigger. After the field attribute in the metadata dictionary is modified, the trigger automatically updates the attribute configuration of the corresponding field in the field mapping table. After the synchronization is completed, an update success flag is returned for system verification. If the synchronization fails, the system generates an alarm log and notifies the administrator, while locking the metadata dictionary modification permission until the synchronization is completed.

[0054] In one embodiment, based on the standard and field mapping table of the metadata dictionary, different database tables are designed for each type of structured document, following the principle of one table per type. Each document type corresponds to one database table, and the fields of each database table correspond one-to-one with the bookmark codes of the corresponding document type.

[0055] The naming convention for each data table includes: t_document type identifier_doc;

[0056] Each data table uses the document identifier as the primary key, and each field corresponds to the bookmark code bound in the field mapping table. The field types are consistent with the field attributes defined in the metadata dictionary. At the same time, a composite index is created for the document type identifier field and the primary key to improve the efficiency of subsequent data extraction by document identifier and document type identifier.

[0057] Based on the above database table design, an adapted H5 structured document page is developed for each document type. The page fields correspond one-to-one with the fields in the corresponding database table, ensuring that the dynamic data entered by the user can be accurately written into the corresponding database table.

[0058] The structured document interface program achieves data transmission routing adaptation through document type identifiers. These document type identifiers are preset letter codes, such as "HT" for contracts, "GW" for official documents, "BB" for reports, "XY" for agreements, and "DA" for personnel files. The H5 structured document page is adapted for both PC and mobile browsers, uniformly retaining data saving, preview, submission, and draft storage functions. The document type identifier is bound to the document identifier and stored in the document metadata table of the document database, forming a one-to-one mapping between document identifiers and document type identifiers, for internal use by the interface program in subsequent stages. The fields in the document metadata table include doc_id (which is the same as the structured document identifier and serves as the primary key of this table), type_code (document type identifier), and create_time (creation time), with field types consistent with the doc_id field in the corresponding database sub-table.

[0059] In one embodiment, after a user fills in dynamic data and submits it on an H5 structured document page, the structured document interface program performs format validation on the data according to the field constraint rules of the metadata dictionary. The validation includes mandatory field prompts, data format validation, and value range validation. If the validation fails, error messages are provided in real time. After the validation passes, the structured document interface program writes the dynamic data into the database table of the corresponding document type.

[0060] In one embodiment, the method further includes deploying the H5 structured document page to the application server, the document database to the data server, and the structured document interface program to the service middleware.

[0061] In one embodiment, the method for generating structured document instances includes:

[0062] Step 1: The user fills in dynamic data and submits it through the H5 structured document page. The structured document interface program performs format validation on the dynamic data according to the field constraint rules in the metadata dictionary.

[0063] Step 2: After the verification is successful, the structured document interface program writes the dynamic data into the database table corresponding to the structured document type according to the field mapping table;

[0064] Step 3: The structured document interface program calls the template engine. Based on the bookmark code in the field mapping table, the template engine extracts the corresponding dynamic data from the database table and fills it into the corresponding bookmark position of the structured document template to generate a complete structured document instance in PDF format.

[0065] In one embodiment, the template engine is Freemarker, which connects with the structured document interface program through function calls to achieve data filling; if the extracted data is missing, the template engine automatically fills in the empty values ​​and records the logs, which are stored in the system log server.

[0066] Step 4: Bind the structured document instance to its unique identifier (document identifier) ​​and store it in the document database.

[0067] In one embodiment, step 4 is followed by step 5: calculating the hash value of the structured document instance in PDF format, binding the hash value with the unique identifier (document identifier) ​​of the structured document instance, and storing them together in the document database. The hash value algorithm is such as SHA-256, but is not limited to it.

[0068] In another embodiment, if the structured document is a contract, a contract type is selected based on the business requirements, H5 contract page fields are compiled, the system's template application function is used to select and apply the corresponding contract template, and a PDF version of the contract file is generated. The contract interface program collects the values ​​of the H5 contract page fields and saves them to the corresponding fields in the contract database, and collects the PDF version of the contract file and saves it to the contract file server.

[0069] In one embodiment, the method further includes step S2: structured document approval. Using a structured document interface program based on the RESTful protocol, and indexed by the document identifier, the associated document type identifier is first obtained from the document metadata table. Based on the document type identifier, dynamic data is extracted from the document database from the corresponding document type's dedicated data table and automatically populated into the corresponding fields of the approval process form. One approval process form corresponds to one document type. Simultaneously, through a file access interface, the bound PDF version of the structured document is extracted from the document server based on the document identifier and uploaded as an attachment to the approval process form. The approval process form is permanently bound to the document identifier, ensuring that the dynamic data and attachment files in the approval process form are completely consistent with the original data when the structured document was created. After logging into the system, the approver only needs to perform business logic approval on the content of the approval process form; no manual review of the consistency between the form data and the attachment files is required. After approval, the system automatically updates the structured document status to "approved" and records information such as the approver, approval time, and approval comments.

[0070] In one embodiment, when the structured document is a contract, the contract approval steps are as follows: Dynamic data from the contract form is extracted through an internal system interface and transmitted to the approval process form; the contract file is extracted and transmitted as an attachment to the approval process form, ensuring that the data in the approval process form and the contract file data are consistent with the data at the time of contract creation. The approver approves the contract approval process form without requiring manual verification of the consistency between the contract form and the contract file data. After approval, the contract status is marked as approved.

[0071] In one embodiment, the method further includes step S3: collaborative confirmation of structured documents. Using a structured document interface program and indexed by a document identifier, approved dynamic data is extracted from the document database, and the corresponding PDF version of the structured document instance is extracted from the document server as an attachment to the confirmation process form, which is then transmitted to the counterparty for collaborative confirmation. The counterparty must pass a system-preset authentication mechanism (such as account password verification, mobile phone verification code verification, or digital certificate verification) before obtaining confirmation permissions for the corresponding structured document instance. They can only view the dynamic data and PDF file and cannot perform any modification operations. After verification, the counterparty submits a confirmation command, automatically updating the status of the structured document instance record to "confirmed," and storing the confirmation record (including the confirmer and confirmation time) in the document database along with the document identifier, ensuring data traceability in the confirmation process.

[0072] In one embodiment, if the structured document is a contract, the approved contract is sent to the other party for confirmation. The system's internal contract interface program extracts field values ​​from the contract database table and transmits them to the other party's contract confirmation process. These values ​​include, for example, the contract name, contract amount, Party A, and Party B. The contract interface program also extracts a PDF version of the contract file from the contract file server and transmits it as an attachment to the confirmation process form. Because the data in the confirmation flow originates from both the document database and the document server, it ensures that the data in the confirmation process form and the contract file data are consistent with the data at the time of contract creation. The other party need not worry about inconsistencies between the data in the confirmation process and the actual PDF contract data.

[0073] In one embodiment, the structured document pushed to the counterparty can only be viewed, not modified. If the counterparty verifies that everything is correct, they confirm the document, ensuring that the data in the confirmation process form and the contract document data are consistent with those at the time of contract creation. If the counterparty finds data inconsistencies during verification, they can submit an objection request through the system. The objection request submission entry is the system's preset objection feedback module, which requires filling in the objection field name, objection description, and supporting materials, and is then pushed to the initiating party for review. The initiating party receives the objection notification through system messages and can only modify the fields of the dynamic data involved in the objection. After modification, the system automatically synchronizes the changes to the database table and file server, recalculates the file hash value, and then initiates the confirmation process again, ensuring that data consistency and controllability are maintained throughout the entire process.

[0074] In one embodiment, the method further includes step S4: stamping the electronic structured document. Using a standardized electronic signature interface (supporting nationally recognized electronic signature technology standards, such as GB / T35275-2023), the system extracts the confirmed PDF version of the structured document from the document server, indexed by the document identifier, and transmits it to the electronic signature system. After receiving the file, the electronic signature system verifies whether the file hash value matches the original hash value stored in the document database, ensuring that the file received by the electronic signature system is identical to the original file at the time of creation. After both parties complete identity verification (such as UKey verification or facial recognition verification) through the electronic signature system, they obtain the structured document instance to be signed and sequentially complete the electronic signature operation. After all parties have signed, the system automatically updates the status of the structured document instance to "stamped," binds the signed complete document with the document identifier, re-archives it to the corresponding directory on the document server, and simultaneously records full traceability data such as the signature version number, signatory information of each party, and signing time in the document database, ensuring that the consistency between the electronically signed document and the originally created document is verifiable.

[0075] The standardized electronic signature interface input parameters include: document identifier and signer identity identifier; output parameters include: signature success identifier and signature file storage path; authentication is achieved by calling the electronic signature system's SDK. UKey verification requires the device number to be passed in, and face recognition requires the face image byte stream to be passed in.

[0076] In one embodiment, when the structured document is a contract, the steps for electronic contract stamping are as follows: the confirmed contract document is extracted through the internal interface of the system and transmitted to the electronic signature system to ensure that the contract document in the electronic signature system is consistent with the created contract document. Both parties to the contract obtain the contract to be signed through the electronic signature system, and after they stamp it, the contract status is marked as stamped.

[0077] In one embodiment, for the structured document to be stamped that is pushed to the other party, the other party can only browse it and cannot modify it. If the other party verifies that it is correct, then the document is stamped, ensuring that the structured file data in the stamping process is consistent with the structured document when it was created.

[0078] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0079] This invention also provides a structured document data consistency end-to-end management system, such as... Figure 1 As shown, it includes: Structured document template creation module: used to create structured document templates according to structured document types; the structured document template includes a structured document template and a structured document form. The structured document template is used to store fixed data that will not change, and reserves blank spaces for storing dynamic data that will change. Each blank space is set with a unique bookmark code; the structured document form is used to collect the dynamic data. Field mapping table construction module: Used to construct a field mapping table based on bookmark codes to represent the mapping relationship between structured document form fields, bookmark codes, and database table fields storing dynamic data; Dynamic data storage module: used to store all collected dynamic data into database tables of corresponding types according to the field mapping table; Structured document instance generation module: Based on bookmark codes, it fills the blank positions with the collected dynamic data to generate a structured document instance with a set format, and binds and stores the structured document instance with a document identifier that uniquely identifies the document instance.

[0080] In one embodiment, the system further includes an approval module, which is used to extract dynamic data corresponding to the document identifier from a database table using the document identifier as an index, fill the corresponding approval process form fields according to a predefined mapping relationship, and generate an approval process form; extract the structured document instance corresponding to the document identifier from the document server as an attachment to the approval process form for approval; when the approval process form is approved, change the status corresponding to the dynamic data to "approved", and archive and store the approved structured document instance.

[0081] In one embodiment, the system further includes a collaborative confirmation module, which uses a document identifier as an index to extract dynamic data with an approved status from a database table and populates it into the corresponding confirmation process form fields to generate a confirmation process form; it then sends the structured document instance corresponding to the dynamic data with an approved status from the document server as an attachment to the confirmation process form to the other party for collaborative confirmation, modifies the status of the collaboratively confirmed dynamic data to confirmed, and archives and stores the confirmed structured document instance.

[0082] In one embodiment, the system further includes an electronic signature module, which uses a document identifier as an index to extract structured document instances whose document identifier status is confirmed or approved from the document server, transmits them to the electronic signature system to complete the electronic signature operation, and archives and stores the signed structured document instances.

[0083] This invention also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the various steps of the method described in this invention.

[0084] This invention also provides a non-transitory computer-readable storage medium storing a computer program. The computer program includes program instructions that, when executed by a processor, implement the various steps of the method described in this invention, which will not be elaborated further here.

[0085] The computer-readable storage medium can be the data transmission apparatus or the internal storage unit of a computer device provided in any of the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium can also be the external storage device of the computer device, such as the plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc. equipped on the computer device.

[0086] Furthermore, the computer-readable storage medium may include both internal storage units and external storage devices of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium may also be used to temporarily store data that is to be output or has already been output.

[0087] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0088] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0089] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0090] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0091] The contents not described in detail in this specification are existing technologies known to those skilled in the art.

Claims

1. A structured document data consistency end-to-end management system, characterized in that, include: Structured document template creation module: Used to create structured document templates based on structured document types; The structured document template includes a structured document template and a structured document form. The structured document template is used to store fixed data that will not change, and reserves blank spaces for storing dynamic data that will change. Each blank space is set with a unique bookmark code. The structured document form is used to collect the dynamic data. Field mapping table construction module: Used to construct a field mapping table based on bookmark codes to represent the mapping relationship between structured document form fields, bookmark codes, and database table fields storing dynamic data; Dynamic data storage module: used to store all collected dynamic data into database tables of corresponding types according to the field mapping table; Structured document instance generation module: Based on bookmark codes, it fills the blank positions with the collected dynamic data to generate a structured document instance with a set format, and binds and stores the structured document instance with a document identifier that uniquely identifies the document instance.

2. The structured document data consistency end-to-end management system as described in claim 1, characterized in that, It also includes an approval module, which uses the document identifier as an index to extract dynamic data corresponding to the document identifier from the database table, and fills it into the corresponding approval process form fields according to the predefined mapping relationship to generate the approval process form. The structured document instance corresponding to the document identifier is extracted from the document server and used as an attachment to the approval process form for approval. After the approval process form is approved, the status corresponding to the dynamic data is changed to "approved" and the approved structured document instance is archived and stored.

3. The structured document data consistency end-to-end management system as described in claim 2, characterized in that, It also includes a collaborative confirmation module, which uses the document identifier as an index to extract dynamic data with the status of approval from the database table and populates it into the corresponding confirmation process form fields to generate a confirmation process form. The structured document instance corresponding to the dynamic data whose status is "approved" is sent from the document server as an attachment to the confirmation process form to the other party for collaborative confirmation. The status of the dynamic data that has passed collaborative confirmation is changed to "confirmed", and the confirmed structured document instance is archived and stored.

4. The structured document data consistency end-to-end management system as described in claim 2 or 3, characterized in that, It also includes an electronic signature module, which uses document identifiers as indexes to extract structured document instances with document identifier status of confirmed or approved from the document server, transmits them to the electronic signature system to complete the electronic signature operation, and archives and stores the signed structured document instances.

5. The structured document data consistency end-to-end management system as described in claim 3, characterized in that, It also includes an electronic signature module, which uses document identifiers as indexes to extract structured document instances with document identifier status of confirmed or approved from the document server, transmits them to the electronic signature system to complete the electronic signature operation, and archives and stores the signed structured document instances.

6. The structured document data consistency end-to-end management system as described in any one of claims 1, 2, 3, and 5, characterized in that, It also includes a metadata dictionary, which records the bookmark code, the corresponding dynamic field name, the field data type, and the field constraint rules; the field mapping table is associated with the metadata dictionary, and when the field attributes in the metadata dictionary are modified, the field mapping table is triggered to be updated synchronously.

7. The structured document data consistency end-to-end management system as described in claim 6, characterized in that, Methods for generating structured document instances include: Obtain the dynamic data filled in by the user, and perform format validation on the dynamic data according to the field constraint rules in the metadata dictionary; After successful verification, the dynamic data is written into the database table corresponding to the structured document type according to the field mapping table. Based on the bookmark codes in the field mapping table, the corresponding dynamic data is extracted from the database table and filled into the corresponding bookmark positions of the structured document template to generate a structured document instance with a set format.

8. A method for end-to-end control of structured document data consistency in the system as described in claim 1, characterized in that, include: Create structured document templates based on structured document types; The structured document template includes a structured document template and a structured document form. The structured document template is used to store fixed data that will not change, and reserves blank spaces for storing dynamic data that will change. Each blank space is set with a unique bookmark code. The structured document form is used to collect the dynamic data. A field mapping table is constructed based on bookmark codes to represent the mapping relationship between structured document form fields, bookmark codes, and database table fields storing dynamic data; All collected dynamic data is stored in database tables of corresponding types according to field mapping tables; Based on the bookmark code, the collected dynamic data is filled into the blank position to generate a structured document instance with a set format, and the structured document instance is bound and stored with a document identifier that uniquely identifies the document instance.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the structured document data consistency end-to-end management method as described in claim 8.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the structured document data consistency end-to-end control method as described in claim 8.

Images