A document management information adjustment updating method, system and storage medium

Abstract

The application discloses a document management information adjustment updating method and system and a storage medium. After a target word document to be filled is acquired and filling configuration information of the target word document is inquired, first to-be-filled data is acquired from target word document attribute information, corresponding second to-be-filled data is acquired from the approval process data according to a to-be-filled data name in the filling configuration information, third to-be-filled data is formed by adjusting and verifying the first to-be-filled data according to corresponding verification data acquired from the approval process data, and finally, the third to-be-filled data and the second to-be-filled data are filled into to-be-updated target domain elements of the target word document to form a final document, so that the accuracy of automatic information filling in a file management system is greatly improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, system, and storage medium for adjusting and updating document management information. Background Technology

[0002] Document management systems can comprehensively record relevant information about internal quality control documents, enabling users to track, manage, and understand these documents. Currently, most document management systems update document information manually or automatically. However, regardless of the method, the diverse types of documents and varying enterprise requirements and settings often lead to errors in information retrieval during updates, reducing the accuracy of document records. This can result in users obtaining incorrect information during subsequent tracking, causing immeasurable consequences. Summary of the Invention

[0003] This invention addresses the shortcomings of existing technologies by disclosing a method for adjusting and updating document management information, comprising the following steps:

[0004] S1, obtain the target Word document to be filled, and query the filling configuration information of the target Word document, the filling configuration information including the name of the data to be filled;

[0005] S2, obtain the first data to be filled from the attribute information of the target Word document. The first data to be filled includes, but is not limited to, the file name, file version or file number. Query the corresponding approval process data from the file management system according to the file name of the target Word document.

[0006] S3, collect the corresponding second data to be filled from the approval process data according to the name of the data to be filled. The second data to be filled includes, but is not limited to, the drafting information, review information or approval information of the target Word document.

[0007] S4. Obtain corresponding verification data from the approval process data according to the name of the data to be filled. After verifying and adjusting the first data to be filled according to the verification data, a third data to be filled is formed. The third data to be filled and the second data to be filled are used to fill the target field element to be updated in the target Word document to form the final document.

[0008] Preferably, step S4 specifically includes:

[0009] Multiple node data groups for each approval node are obtained from the approval process data as verification data. The node data group includes the file name, file version and node creation time of the node.

[0010] The file names of each approval node in the verification data are compared with the file names in the first data to be filled. If they are inconsistent, the file names of each approval node are compared. If the file names of each approval node are consistent, they are used as the file names in the third data to be filled. If the file names of each approval node are inconsistent, the file names in the first data to be filled are retained as the file names in the third data to be filled.

[0011] Preferably, step S4 specifically includes:

[0012] Check if the first data to be filled contains a file version. If it does, check if the file versions of each approval node in the validation data are the same. If they are the same, obtain the file version as the file version in the third data to be filled.

[0013] If they are different, compare whether the file version of each node is higher than or equal to the file version of the previous node. If so, determine whether the file version in the first data to be filled is higher than or equal to the highest file version in each node. If it is higher than or equal to, retain the file version in the first data to be filled as the file version in the third data to be filled. Otherwise, issue a file version verification reminder.

[0014] If the first data to be filled does not contain a file version, then the file version in the last node data group will be used as the file version in the third data to be filled.

[0015] Preferably, step S4 further includes:

[0016] Parse all field elements in the target Word document and filter out the target field elements that need to be populated and updated based on the text content contained in each field element;

[0017] After obtaining all the target field element information that needs to be filled, the collected second and third data to be filled are used to fill the corresponding target field elements, and the final document is updated.

[0018] This invention also discloses a document management information adjustment and update system, comprising: a configuration information acquisition module, used to acquire a target Word document to be filled, and query the filling configuration information of the target Word document, the filling configuration information including the name of the data to be filled; a first filling data acquisition module, used to acquire first data to be filled from the attribute information of the target Word document, the first data to be filled including but not limited to file name, file version or file number, and query the corresponding approval process data from the file management system according to the file name of the target Word document; a second filling data acquisition module, used to collect and acquire corresponding second data to be filled from the approval process data according to the name of the data to be filled, the second data to be filled including but not limited to drafting information, review information or approval information of the target Word document; and a data verification module, used to acquire corresponding verification data from the approval process data according to the name of the data to be filled, verify and adjust the first data to be filled according to the verification data to form a third data to be filled, and fill the third data to be filled and the second data to be filled into the target field element to be updated of the target Word document to form the final document.

[0019] Preferably, the data verification module includes: a verification data acquisition module, used to acquire multiple node data groups of each approval node from the approval process data as verification data, wherein the node data group includes the file name, file version and node creation time of the node; and a verification data comparison module, used to compare the file names of each approval node in the verification data with the file names in the first data to be filled, and if they are inconsistent, compare the file names of each approval node; if the file names of each approval node are consistent, use them as the file names in the third data to be filled, and if the file names of each approval node are inconsistent, retain the file names in the first data to be filled as the file names in the third data to be filled.

[0020] Preferably, the verification data comparison module is further configured to check whether the first data to be filled contains a file version. If it does, it determines whether the file versions of each approval node in the verification data are the same. If they are the same, it obtains the file version as the file version in the third data to be filled. If they are different, it compares whether the file version corresponding to each node is higher than or equal to the file version of the previous node. If so, it determines whether the file version in the first data to be filled is higher than or equal to the highest file version in each node. If it is higher than or equal to, it retains the file version in the first data to be filled as the file version in the third data to be filled; otherwise, it issues a file version verification reminder. If the first data to be filled does not contain a file version, it uses the file version in the last node data group as the file version in the third data to be filled.

[0021] Preferably, the verification data comparison module is further configured to parse all field elements in the target Word document, and filter out the target field elements that need to be filled and updated based on the text content contained in each field element; after obtaining all the target field element information to be filled, the collected second and third data to be filled are used to fill the corresponding target field elements to update and form the final document.

[0022] The present invention also discloses a document control information adjustment and update device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of any of the document control information adjustment and update methods described above.

[0023] The present invention also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the document control information adjustment and update method as described above.

[0024] The document management information adjustment and update method, system, and storage medium disclosed in this invention, after obtaining the target Word document to be filled and querying the filling configuration information of the target Word document, obtains the first data to be filled from the attribute information of the target Word document, and collects the corresponding second data to be filled from the approval process data according to the name of the data to be filled in the filling configuration information. Then, the first data to be filled is verified and adjusted according to the corresponding verification data obtained from the approval process data to form a third data to be filled. Finally, the third data to be filled and the second data to be filled are filled into the target field element to be updated in the target Word document to form the final document. That is, by obtaining the first data to be filled and the second data to be filled from the file attribute information and the approval process and verifying the first and second data to be filled, the accuracy of automatically filled information in the Word document is greatly improved.

[0025] 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

[0026] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0027] Figure 1 This is a flowchart illustrating a document control information adjustment and update method disclosed in an embodiment of the present invention.

[0028] Figure 2This is a schematic diagram of the specific process of step S4 disclosed in an embodiment of the present invention.

[0029] Figure 3 This is another specific flowchart illustrating step S4 disclosed in an embodiment of the present invention.

[0030] Figure 4 This is a structural block diagram of a document management information adjustment and update system disclosed in another embodiment of the present invention. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the described embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0032] Unless otherwise defined, the technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this invention pertains. The terms “first,” “second,” and similar terms used in this patent application specification do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, the terms “an” or “a” and similar terms do not indicate a quantity limitation, but rather indicate the presence of at least one.

[0033] In this embodiment, as shown in the appendix Figure 1 As shown, a method for adjusting and updating document control information is disclosed, which may include the following:

[0034] Step S1: Obtain the target Word document to be filled, and query the filling configuration information of the target Word document, which includes the name of the data to be filled.

[0035] Specifically, under user instructions, the file management system calls the file filling component, uses Jacob to create an ActiveXComponent object, and uses the Documents property to obtain and open the target Word document to be filled.

[0036] Step S1 further includes identifying and obtaining the document category of the target Word document, querying the template database according to the document category to obtain the corresponding standard document template, parsing the standard document template to obtain the filling configuration information, the filling configuration information including the name of the data to be filled.

[0037] Step S2: Obtain the first data to be filled from the attribute information of the target Word document. The first data to be filled includes, but is not limited to, the file name, file version or file number. Query the corresponding approval process data from the file management system based on the file name of the target Word document.

[0038] Step S3: Collect the corresponding second data to be filled from the approval process data according to the name of the data to be filled. The second data to be filled includes, but is not limited to, the drafting information, review information or approval information of the target Word document.

[0039] Specifically, the names and data to be filled are stored in the filling database in the form of a map data structure. The first data to be filled is obtained directly by the system based on document attribute values, while the second data is obtained by querying the approval process based on the first data to be filled. By obtaining the first and second data to be filled from document attribute information and the approval process respectively, the system can comprehensively and clearly obtain the data required for filling, providing a basis for subsequent verification and correction.

[0040] Step S3 can also collect corresponding second data to be filled from the approval process data based on other information in the first data to be filled. Furthermore, the system can also customize the acquisition of other types of data as needed. For example, it can collect corresponding fourth data to be filled from the permission database based on the name of the data to be filled, the fourth data to be filled including but not limited to access permissions, editing permissions, or movement permissions of the target Word document. It can also collect corresponding fifth data to be filled from the access history based on the name of the data to be filled, the fifth data to be filled including but not limited to access records, visitors, or access history of the target Word document.

[0041] Step S4: Obtain corresponding verification data from the approval process data according to the name of the data to be filled; verify and adjust the first data to be filled according to the verification data to form the third data to be filled; fill the third data to be filled and the second data to be filled into the target field element to be updated in the target Word document to form the final document.

[0042] Specifically, the first data to be filled is obtained by the system by querying the attribute information saved during the last update of the document. However, during the modification and approval process, the relevant attribute information of the document, such as the file name and file version, may change. Therefore, the attribute information needs to be corrected to ensure the accuracy of the first data to be filled during this update.

[0043] In this embodiment, as shown in the appendix Figure 2 As shown, step S4 may specifically include the following:

[0044] Step S41: Obtain multiple node data groups of each approval node from the approval process data as verification data. The node data group includes the file name, file version and node creation time of the node.

[0045] Specifically, step S41 further includes obtaining multiple node data groups of each approval node within a preset time period from the approval process data based on the file number as verification data. The preset time period is configured to start from the last fill update time of the target Word document and extend to the current time. The file number of the target Word document is unique and unchanging, automatically generated by the system according to preset rules, such as file number 20230620004, which is automatically generated according to the preset file numbering rule "year + month + day + number of files created on that day".

[0046] Step S42: Compare the file names of each approval node in the verification data with the file names in the first data to be filled. If they are inconsistent, compare the file names of each approval node. If the file names of each approval node are consistent, use them as the file names in the third data to be filled. If the file names of each approval node are inconsistent, retain the file names in the first data to be filled as the file names in the third data to be filled.

[0047] Specifically, if the first data to be filled is consistent with the file name of each approval node, it means that the file name has not been modified and can be used. If the first data to be filled is inconsistent with the file name of each approval node, then when the file names of each approval node are consistent, the file name in each approval node is taken as the final file name. This means that the file name has been modified. If the file names of each approval node are inconsistent, it means that the file name may have been incorrect during the approval process. In this case, the file name in the original first data to be filled is selected as the final file name.

[0048] If the file names are inconsistent across different approval stages, or if the file names are modified during the approval process, the file names can be further selected based on the order of the approval stages. The specific steps are as follows:

[0049] Step S101: If the file names in each approval node are inconsistent, determine whether the file name corresponding to each node is consistent with the file name of the previous node.

[0050] Step S102: Obtain the number of times the file name corresponding to each node is inconsistent with the file name corresponding to the previous node. If it is greater than or equal to 2, retain the file name in the first data to be filled; if it is equal to 1, retain the file name corresponding to the last node.

[0051] As attached Figure 3As shown, step S4 further includes:

[0052] Step S201: Check if the first data to be filled contains a file version. If it does, determine if the file versions of each approval node in the verification data are the same. If they are the same, obtain the file version as the file version in the third data to be filled.

[0053] Step S202: If they are not the same, compare whether the file version corresponding to each node is higher than or equal to the file version of the previous node. If so, determine whether the file version in the first data to be filled is higher than or equal to the highest file version in each node. If it is higher than or equal to, retain the file version in the first data to be filled as the file version in the third data to be filled. Otherwise, issue a file version verification reminder.

[0054] Step S203: If the first data to be filled does not contain a file version, then the file version in the last node data group is used as the file version in the third data to be filled.

[0055] Specifically, document versions may change after each approval process, thus requiring version correction. If the document version in the first data entry is the same as the document versions at each node, the first data entry can be used. If the document version in the first data entry is different from the document versions at each node, it can be checked and modified according to the order of the nodes and the document version level within each node. Since documents are approved sequentially from beginning to end with each approval node, under normal circumstances, the document version in a later approval process may be higher than the document version in a previous approval process; otherwise, it is an error and can be ignored. When the document version in a later approval process is higher than the document version in a previous approval process, since the document version in the first data entry is the version saved from the previous update, the current update may only result in a document version higher than or equal to the document version in the first data entry. In this case, further judgment is made on the relationship between the highest-level document version in the retained approval process and the document version in the first data entry to eliminate abnormal situations and retain the highest-level version. Through two comparisons, abnormal situations can be eliminated more accurately, improving the accuracy of the system in obtaining document versions.

[0056] Step S43: Parse all field elements in the target Word document, and filter out the target field elements that need to be populated and updated based on the text content contained in each field element.

[0057] Specifically, the target Word document contains various types of field elements. Screening these field elements to select the required ones can help reduce the system's workload, improve response efficiency, and avoid errors caused by irrelevant field elements being modified during the filling process.

[0058] Step S43 further includes: parsing all field elements in the target Word document, iterating through each field element, and determining whether the field element is a field code by checking if the Type attribute in the field element is of type wdFieldRef. If the field element is a field code, the text content of the field code is obtained and parsed according to the requirements in the fill configuration information. The name to be filled is matched with the text content of each identified field element. If the text content matches at least one name to be filled, the corresponding field element is taken as the target field element to be filled and updated.

[0059] Furthermore, if some of the data names to be filled in the target Word document's fill configuration information fail to match the text content of the identified field elements in the target Word document, then these data names need to be added to the target Word file by creating a new field or inserting a field. Then, the data names to be filled that have not yet been matched can be defined as the first keyword, and the data names to be filled that have been matched can be defined as the second keyword. Then, step S3 also includes the following content.

[0060] Determine whether each primary keyword has an associated keyword in the secondary keyword group. This associated keyword is configured as a keyword with a relationship. The secondary keyword group contains all secondary keywords. If an associated keyword exists in the secondary keyword group, the primary keyword is inserted into the domain element containing the associated keyword. If no associated keyword exists in the secondary keyword group, a new domain element is created, and the primary keyword is populated into the new domain element.

[0061] Furthermore, if there are multiple first keywords that are not related to the second keyword group, it is determined whether there is a relationship between these first keywords. If there is a relationship, a new domain is created and the first keywords with the relationship are inserted into the same new domain.

[0062] The association relationships between different keywords can be obtained through pre-setting or by determining the association probability value between two keywords. When the association probability value between two keywords exceeds a first preset value, the two keywords are considered to be associated. The association probability value can be obtained by analyzing and calculating other filled Word documents stored in the file management system, as follows:

[0063] Retrieve all filler Word documents stored in the file management system. Parse all field elements in each filler Word document and extract the text content within the field elements. Record the parsed text content from each filler Word document as keywords and their corresponding field elements in the process database. Set the initial association probability value between any two keywords to 0. Iterate through all keywords stored in the process database. If two keywords appear once in the same field element, increment the initial probability value between the two keywords by 1.

[0064] Step S44: After obtaining all the target field element information to be filled, the collected second and third data to be filled are used to fill the corresponding target field elements to update and form the final document.

[0065] Specifically, after filling the target field elements with the second and third fill information to form the final document, `forceSaveAs` is called to save the file as a PDF file. Because of compatibility issues with DOC files, if file corruption is detected during processing, a warning dialog box will pop up to prompt the user whether to try to repair the document, causing the program to block and fail to execute normally. Therefore, a compatibility approach is adopted for different Word formats such as DOC and DOCX: when the document is opened, the repair dialog box is disabled, macros are enabled, password protection is not enabled, and the document converter is disabled.

[0066] Step S44 may also include the following:

[0067] Step S441: After associating all the collected data to be filled with the target field elements to be filled, the data to be filled is then filled into the corresponding target field elements. The presence of table-type data in the target Word document is determined based on the Columns attribute located in the target Word document.

[0068] Step S442: If table-type data exists, the document encoding is parsed, and the table location area in the target Word document is located based on the Columns attribute information to determine whether there is a target field element in the table location area.

[0069] Step S443: If a target field element exists in the table position area, obtain the header row carrying the corresponding target field element information, obtain the number of columns to be filled according to the number of header elements, and traverse row by row according to the number of columns to obtain the corresponding attribute name, attribute value and cell correspondence of the data to be filled.

[0070] Step S444: Insert table rows into the table type data and set cell styles. Fill the corresponding data to be filled into the inserted table rows according to the cell correspondence, and update to form the final document.

[0071] Specifically, if the string ends with "Array", the corresponding file approval information will be filled with newlines; if the string ends with "Str", the corresponding file approval information will be filled with commas.

[0072] Step S44 further includes: if there is no table type data, or if there is table type data but the target field element is found to be outside the table position area after locating the table position area in the target Word document based on the Columns attribute information, then the collected data to be filled is directly filled into the corresponding target field element to update and form the final document.

[0073] The document control information adjustment and update method disclosed in this invention involves obtaining a target Word document to be filled and querying the filling configuration information of the target Word document. First, data to be filled is obtained from the attribute information of the target Word document. Second, data to be filled is collected from the approval process data according to the name of the data to be filled in the filling configuration information. Then, the first data to be filled is verified and adjusted based on the corresponding verification data obtained from the approval process data to form third data to be filled. Finally, the third data to be filled and the second data to be filled are used to fill the target field elements to be updated in the target Word document to form the final document. In other words, by obtaining the first and second data to be filled from the file attribute information and the approval process and verifying the first and second data to be filled, the accuracy of automatically filled information in the Word document is greatly improved.

[0074] In another embodiment, as shown in the appendix Figure 4As shown, a document management information adjustment and update system is also disclosed, including a configuration information acquisition module 1, a first fill data acquisition module 2, a second fill data acquisition module 3, and a data verification module 4. The configuration information acquisition module 1 is used to acquire the target Word document to be filled and query the fill configuration information of the target Word document, including the name of the data to be filled. The first fill data acquisition module 2 is used to acquire the first data to be filled from the attribute information of the target Word document. The first data to be filled includes, but is not limited to, file name, file version, or file number. Based on the file name of the target Word document, it queries the corresponding approval process data from the document management system. The second fill data acquisition module 3 is used to collect the corresponding second data to be filled from the approval process data based on the name of the data to be filled. The second data to be filled includes, but is not limited to, the drafting information, review information, or approval information of the target Word document. The data verification module 4 is used to acquire the corresponding verification data from the approval process data based on the name of the data to be filled. Based on the verification data, the first data to be filled is verified and adjusted to form a third data to be filled. The third data to be filled and the second data to be filled are then used to fill the target field elements of the target Word document to form the final document.

[0075] In this embodiment, the data verification module 2 includes a verification data acquisition module and a verification data comparison module. The verification data acquisition module is used to acquire multiple node data groups for each approval node from the approval process data as verification data. Each node data group includes the file name, file version, and node creation time of the node. The verification data comparison module is used to compare the file names of each approval node in the verification data with the file names in the first data to be filled. If they are inconsistent, the file names of each approval node are compared. If the file names of all approval nodes are consistent, they are used as the file names in the third data to be filled. If the file names of all approval nodes are inconsistent, the file names in the first data to be filled are retained as the file names in the third data to be filled.

[0076] In this embodiment, the verification data comparison module is further configured to check whether the first data to be filled contains a file version. If it does, it determines whether the file versions of each approval node in the verification data are the same. If they are the same, it obtains the file version as the file version in the third data to be filled. If they are different, it compares whether the file version corresponding to each node is higher than or equal to the file version of the previous node. If so, it determines whether the file version in the first data to be filled is higher than or equal to the highest file version in each node. If it is higher than or equal to, it retains the file version in the first data to be filled as the file version in the third data to be filled; otherwise, it issues a file version verification reminder. If the first data to be filled does not contain a file version, it uses the file version in the last node data group as the file version in the third data to be filled.

[0077] In this embodiment, the verification data comparison module is further configured to parse all field elements in the target Word document, and filter out the target field elements that need to be filled and updated based on the text content contained in each field element; after obtaining all the target field element information that needs to be filled, the collected second and third data to be filled are used to fill the corresponding target field elements to update and form the final document.

[0078] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar parts between embodiments can be referred to interchangeably. Regarding the document control information adjustment and update system disclosed in the embodiments, since it corresponds to the document control information adjustment and update method disclosed in the embodiments, the description is relatively simple, and relevant parts can be referred to the foregoing method section.

[0079] In other embodiments, a document control information adjustment and update apparatus is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the various steps of the document control information adjustment and update method described in the above embodiments. The server may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that the schematic diagrams are merely examples of a server and do not constitute a limitation on the server. The server may include more or fewer components than illustrated, or combine certain components, or use different components.

[0080] If the document control information adjustment and update device is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the above-described document control information adjustment and update method embodiments. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory, random access memory, electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0081] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

[0082] In summary, the above description is only a preferred embodiment of the present invention. All equivalent changes and modifications made within the scope of the claims of the present invention should be covered by the present invention.

Claims

1. A method for adjusting and updating document management information, characterized in that, Includes the following steps: S1, obtain the target Word document to be filled, and query the filling configuration information of the target Word document, the filling configuration information including the name of the data to be filled; S2, obtain the first data to be filled from the attribute information of the target Word document. The first data to be filled includes, but is not limited to, the file name, file version or file number. Query the corresponding approval process data from the file management system according to the file name of the target Word document. S3, collect the corresponding second data to be filled from the approval process data according to the name of the data to be filled. The second data to be filled includes, but is not limited to, the drafting information, review information or approval information of the target Word document. S4, obtain corresponding verification data from the approval process data according to the name of the data to be filled, verify and adjust the first data to be filled according to the verification data to form the third data to be filled, and fill the third data to be filled and the second data to be filled into the target field element to be updated in the target Word document to form the final document. Multiple node data groups for each approval node are obtained from the approval process data as verification data. The node data group includes the file name, file version and node creation time of the node. Compare the file names of each approval node in the verification data with the file names in the first data to be filled. If they are inconsistent, compare the file names of each approval node. If the file names of each approval node are consistent, use them as the file names in the third data to be filled. If the file names of each approval node are inconsistent, retain the file names in the first data to be filled as the file names in the third data to be filled. Check if the first data to be filled contains a file version. If it does, check if the file versions of each approval node in the verification data are the same. If they are the same, obtain the file version as the file version in the third data to be filled. If they are different, compare whether the file version corresponding to each node is higher than or equal to the file version of the previous node. If so, check whether the file version in the first data to be filled is higher than or equal to the highest file version in each node. If it is higher than or equal to, retain the file version in the first data to be filled as the file version in the third data to be filled. Otherwise, issue a file version verification reminder. If the first data to be filled does not contain a file version, then the file version in the last node data group will be used as the file version in the third data to be filled.

2. The document control information adjustment and update method according to claim 1, characterized in that, Step S4 further includes: Parse all field elements in the target Word document and filter out the target field elements that need to be populated and updated based on the text content contained in each field element; After obtaining all the target field element information that needs to be filled, the collected second and third data to be filled are used to fill the corresponding target field elements, and the final document is updated.

3. A document management information adjustment and update system, characterized in that, include: The configuration information acquisition module is used to acquire the target Word document to be filled and query the filling configuration information of the target Word document, wherein the filling configuration information includes the name of the data to be filled; The first data acquisition module is used to acquire the first data to be filled from the attribute information of the target Word document. The first data to be filled includes, but is not limited to, the file name, file version or file number. The module queries the corresponding approval process data from the file management system based on the file name of the target Word document. The second data acquisition module is used to collect and obtain the corresponding second data to be filled from the approval process data according to the name of the data to be filled. The second data to be filled includes, but is not limited to, the drafting information, review information or approval information of the target Word document. The data verification module is used to obtain corresponding verification data from the approval process data according to the name of the data to be filled, verify and adjust the first data to be filled according to the verification data to form the third data to be filled, and fill the third data to be filled and the second data to be filled into the target field element to be updated in the target Word document to form the final document. Multiple node data groups for each approval node are obtained from the approval process data as verification data. The node data group includes the file name, file version and node creation time of the node. The file names of each approval node in the verification data are compared with the file names in the first data to be filled. If they are inconsistent, the file names of each approval node are compared again. If the file names of each approval node are consistent, they are used as the file names in the third data to be filled. If the file names of each approval node are inconsistent, the file names in the first data to be filled are retained as the file names in the third data to be filled. The system checks whether the first data to be filled contains a file version. If it does, it checks whether the file versions of each approval node in the verification data are the same. If they are the same, the file version of that file is obtained as the file version in the third data to be filled. If they are different, it compares whether the file version corresponding to each node is higher than or equal to the file version of the previous node. If so, it checks whether the file version in the first data to be filled is higher than or equal to the highest file version in each node. If it is higher than or equal to, the file version in the first data to be filled is retained as the file version in the third data to be filled. Otherwise, a file version verification reminder is issued. If the first data to be filled does not contain a file version, then the file version in the last node data group will be used as the file version in the third data to be filled.

4. A document management information adjustment and update device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1-2.

5. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-2.

Images