Electronic form file processing method and device capable of recording log data
By recording the input attribute data of the form field in the electronic form file, the problem of failure to record the generation and change process of form field data in the prior art is solved, and the credential characteristics and convenient information query and exchange of the electronic form file are realized.
Patent Information
- Application Number
- CN202010546546.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-06-16
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-06-16
AI Technical Summary
Existing electronic form files fail to record the generation and change process of form field data, resulting in the lack of credential characteristics and inconvenient query and exchange of numerical changes in form field.
During the process of processing electronic form files, the input attribute data related to the generation and changes of form field data is collected and recorded, and the input attribute data is recorded in the electronic form file, including the entry time, personnel information, original value, new value, and filling in program information. wait.
Make the electronic form file have the credential characteristics of recording the generation and change of form field data, making it convenient for querying and exchanging form field numerical change information.
Smart Images

Figure CN113807061B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a method and device for processing electronic form files. Background Art
[0002] An electronic form file is a form-based electronic file, such as a PDF form or other electronic file with form definitions and descriptions. It is currently widely used in electronic file processing in various application fields, such as electronic documents commonly used in online reporting, approval, internal office work, government information collection, and reporting in the field of e-government.
[0003] Current electronic form file recording still has some shortcomings. For example, PDF, HTML, and other files contain definitions of forms and form fields, but the files only store the generated results of the electronic form file and do not describe the transformation process of the form field values. Although PDF and other files support the description and definition of forms and form fields and can be digitally signed multiple times, they do not record the changes in the form field filling process, such as the filling time of each record, the filling person's information, the original value of the form field, the value of the form field after filling, the filling program information used, the source information of the filled form field value, and other filling parameter information. Moreover, form fields do not have file attribute information, such as the last filling time of the form field, the last filling person information, the last filling program used, the last filling data source information, and other filling parameter information.
[0004] In most applications, the form field values and value change information of HTML forms are stored in the system database as application logs, resulting in the form field value change information being stored outside the electronic form file, which is not conducive to the query and exchange of form field value change information.
[0005] Since the electronic form file does not contain information describing the transformation process of the form field data, it cannot provide information about the generation and change history of the form field data. Therefore, the electronic form file itself does not have the voucher feature of recording the generation and change process of the form field data. Summary of the Invention
[0006] The object of the present invention is to provide a method and apparatus for processing an electronic form file, which can record input attribute data of form fields during the process of processing the electronic form file.
[0007] An embodiment of the present invention provides a method for processing an electronic form file, comprising: during the processing of the electronic form file, collecting input attribute data related to the generation and change of form field data in the electronic form file; and recording the input attribute data in the electronic form file.
[0008] An embodiment of the present invention also provides a device for processing an electronic form file, comprising: a data acquisition module for collecting input attribute data related to the generation and change of form field data in the electronic form file during the processing of the electronic form file; and a data recording module for recording the input attribute data in the electronic form file.
[0009] An embodiment of the present invention also provides a device for processing an electronic form file, comprising: a memory for storing instructions; and a processor coupled to the memory, wherein the instructions, when executed by the processor, cause the processor to execute the method for processing an electronic form file described in an embodiment of the present invention.
[0010] An embodiment of the present invention further provides a computer-readable storage medium storing instructions, which, when executed by a processor of a computer, enable the processor to execute the method for processing an electronic form file according to an embodiment of the present invention.
[0011] The embodiments of the present invention record the input attribute data of form fields during the processing of electronic form files, so that the electronic form files themselves can have the voucher feature of recording the process of form field data generation and change, and facilitate the query and exchange of form field value change information. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1 A flow chart of a method for processing an electronic form file according to an embodiment of the present invention is shown;
[0013] Figure 2 An example of an electronic form file used in the embodiment is shown;
[0014] Figure 3 A schematic diagram illustrating forming multiple modified versions of an electronic form file during the generation and modification process of the electronic form file according to an embodiment of the present invention;
[0015] Figure 4 A schematic diagram illustrating forming a plurality of modified versions of a modification log of an electronic form file during a modification process of the electronic form file according to an embodiment of the present invention; and
[0016] Figure 5 A structural block diagram of an apparatus for processing electronic form files according to an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0017] The embodiments of the present invention are further described below with reference to the accompanying drawings.
[0018] An electronic form file is a file containing an electronic form description. An electronic form file is generated after being designed using a form design program. An electronic form file can be filled out once or multiple times to create an electronic form file record. An electronic form is a computer program version of a paper form. In addition to eliminating the cost of printing, storing, and distributing preprinted forms, users can use electronic form files to fill out electronic forms more quickly because the form-related program can automatically format, calculate, search, and validate information. An electronic form generally contains a description of the form and form fields' appearance, form business logic definitions, form field definitions, and the data stored in the form fields. Form fields typically include text fields, single-choice fields, checkbox fields, combo boxes, date fields, time fields, file fields, signature fields, etc. Form field definitions include the form field's location, type, format, and field name. The electronic form file used in embodiments of the present invention includes multiple form fields that can interactively collect data information as form field data (also known as form field values). Examples include two types of interactive form files in PDF form files: the PDF-based AcroForm and the independent form description XMLForms Architecture (XFA). However, the present invention is not limited to these examples. The present invention is applicable to any other electronic form files containing form fields.
[0019] An electronic form can be completed by one or more operators on a client, and upon completion, signed by the operator or a reviewer. This can involve the operator filling in a portion of the data and signing in the signature field or in a blank space on the electronic form. Alternatively, others can fill in a portion of the data, with the operator's signature signed. Alternatively, a reviewer can sign and approve the operator's completed electronic form. This signature is achieved using the signatory's digital certificate, digitally signing the entire electronic form. This digital signature serves to validate the final results of the electronic form and the entry log.
[0020] Figure 1 A flowchart of a method for processing an electronic form file according to an embodiment of the present invention is shown. Method 100 includes: during processing of the electronic form file, collecting input attribute data related to the generation and modification of form field data in the electronic form file (step 101); and recording the input attribute data in the electronic form file (step 102).
[0021] In an embodiment of the present invention, the input attribute data includes a collection of input attribute data generated and changed in multiple processing processes of the electronic form file (such as the data entry process, the form filling process, the data modification process, etc.), forming an input log. For example, when entering an electronic form, an input log with the input attribute data is automatically recorded; when the user manually fills out the electronic form file on the computer, or uses an automatic data entry device to enter data into the form field of the electronic form file, the relevant attribute data of each form field is recorded in the input log after each effective filling is completed. After multiple form fillings, an electronic file record with a full log of form field entries will be formed in the electronic form file, wherein each form field in the electronic form file has a detailed filling record evidence chain, and the entire electronic form file has a complete input log evidence chain. According to the electronic form file processing method of the embodiment of the present invention, all input logs of all form fields of the electronic form file can be completely saved, wherein the saved input attribute data has the characteristics of evidence chain and traceability.
[0022] In an embodiment of the present invention, the input attribute data includes at least one of the following: entry time, entry person information, review person information, original value of the form field, new value of the form field, program information for processing electronic form files, client information for processing the electronic form files, input data source information (such as information of the direct purchase equipment used as the data source, manual keyboard entry by the user, etc.), information of the entry program for automatically entering form field data, physical environment information of the input attribute data, and other input parameter information.
[0023] During the creation process of an electronic form file, the operator information, program system information, project information, file parameter information, etc. of the electronic form file can be recorded in the entry log of the electronic form file; during the filling process of the electronic form file, each valid data filled in for each form field is recorded in the entry log, where the entry attribute data includes the filling time, the filling person information, the original value of the form field, the new value of the form field after filling, the filling program information used, the client information, the data source information (such as direct purchase equipment information, manual keyboard entry), and other filling parameter information. These entry attribute data are used to generate a form field entry log, and the entry log is written into the electronic form file.
[0024] Each time a form field is filled in, the time entered includes, but is not limited to, the year, month, day, hour, minute, second, and time zone. When multiple users fill out an electronic form remotely via a network server, prior time calibration is required to ensure timeline accuracy. For example, multiple users can calibrate to Beijing Time, the system server, or an enterprise time server. Clients can also consistently calibrate their time to a standard time server or system time service using the Network Time Protocol (NTP) service. Personnel information generally refers to information that uniquely identifies the person filling in the form, including but not limited to the user's account number, name, role, or title (e.g., research physician, nurse, etc.). The original value of a form field refers to the value of the form field before the current entry, and the new value of a form field refers to the value of the form field after the current entry. The application information used refers to the application information used for the current entry, including but not limited to the application name and version. A filling program refers to a program used to fill in electronic forms (for example, Adobe Acrobat 7.0 Professional, a software program used to generate and process PDF files); however, the filling program here should be able to connect to system environment information, collect client information, etc., and can also be used to open electronic form files for data filling. In the case where multiple users use the network to process electronic form files, the input attribute data can be collected online or offline in step 101. When multiple users collect data online, certain mechanisms should be used, such as file locks, to avoid file conflicts and ensure the order in which electronic form files are collected and saved, so as to ensure the temporal nature of the entry log of the final electronic form file.
[0025] Client information refers to the client host identifier and computer name used by the user to fill out the form. Data source information refers to the source of the data being filled out, primarily including the entry method and device model. For example, if the data is collected by a direct acquisition device, the application directly connects to the device to provide the data. If the operator uses a sphygmomanometer to measure blood pressure, the data source information may include the device information, model, unit, and normal range of blood pressure values. Of course, this data can also be entered manually by the user filling out the form, such as by typing or copying and pasting. Data source information can indicate whether the data was entered manually or automatically into a spreadsheet file. For example, when collecting electrocardiogram (ECG) data, after the ECG is taken, the data is automatically entered into the spreadsheet opened by the client application. Other entry parameter information within the entry attribute data may include entry instructions, such as environmental information (indoors or outdoors, temperature, humidity, etc.).
[0026] In an embodiment of the present invention, method 100 further includes: adding a digital signature to a signature field in the electronic form file. By adding a digital signature to the signature field in the electronic form file, the operator ensures that the entire processed electronic form file (including the input attribute data written therein) is protected by the digital signature.
[0027] In an embodiment of the present invention, the input attribute data may be log data in the Extensible Markup Language (XML) format or the JSON (JavaScript Object Notation) format. Each time a form field is validly filled in when a file is saved, a form field entry log record is generated and stored in the metadata of the electronic form file. The log record also updates the last fill-in time, last filler information, final value, last fill-in program used, final data source information, and other fill-in parameter information for the relevant form field.
[0028] In an embodiment of the present invention, when an electronic form file is saved or a digital signature is affixed to a signature field in the electronic form file, the entered attribute data is written as an entry log into the metadata of the electronic form file. In this embodiment, the entered attribute data can be saved as a file modification log data item in the metadata of the electronic form file, and the value of this data item can be log data in XML or JSON format.
[0029] The timing for writing the entry log into the electronic form file is after completing the valid filling of the form fields, including when saving the electronic form file after each filling, or when a digital signature is affixed. However, the present invention is not limited thereto.
[0030] Valid filling refers to filling that changes the value of the form field. The software system has a set of rules to determine whether the user's filling is valid. For example, when a user enters text in a text field in an electronic form file, the cursor flashes in the text field after entering focus mode. The user can now enter text in it. At this time, the input text field is in focus mode. Similarly, other form fields have focus modes, but the effects are different. For example, the focus mode of the date field will pop up a date selection dialog box. As long as the form field is in focus mode, the user can continue to enter, enter or modify data in the form field, and the form field has not yet been effectively filled. When the user completes the form field and presses the Enter key on the keyboard, it can be determined that the focus mode has been exited; if the value of the form field changes at this time, the form field is filled in effectively; if the value of the form field does not change, it is considered invalid. Other rules for determining valid entries are: if the form field cannot pass the illegal verification logic, it is not a valid entry; if the user fills in a form field and the form calculation logic causes the value of another form field to change, then the passive filling record of the other form field will be counted as the user who filled it in; the entry record takes effect when the file is saved, and the signature operation of the signature field will also indirectly trigger the file save operation. If the user fills in data in a single form field multiple times before a single save operation, only the last entry is valid when saving, and the original value of the form field is the initial value of the form field before the single save. For example, the original value of the address field in the electronic form file is "Beijing". The user enters "Shanghai", presses the Enter key to exit the focus mode, enters "Guangzhou" again, presses the Enter key to exit the focus mode, and clicks Save. The value of the entry record changes from "Beijing" to "Guangzhou".
[0031] After each form field is filled with a valid value, the recorded form field log data can be stored in a cache without actually being written to the electronic form file. All form field log data in the cache is written to the electronic form file only when the electronic form file is saved or electronically signed. By caching the recorded form field log data, erroneous data entered due to incorrect or unintentional input can be filtered out. For example, the form field value "Shanghai" described above may have been entered by the user unintentionally; it will be filtered out and not written as log data to the electronic form file.
[0032] In an embodiment of the present invention, when a digital signature is affixed to the signature field of an electronic form file, the digest algorithm and digest value of the entry log are written into the signature dictionary of the electronic form file. For example, by using a digital certificate to digitally sign the signature field of the electronic form file, the operator can protect the entire completed electronic form file, including the entry log for the form field. After the operator signs, the entry log for the form field is written into the metadata of the electronic form file, and the entry log is associated with the entry log, and the digest of the entry log and the digest algorithm are written into the signature dictionary. However, the present invention is not limited to writing the entry log into the metadata of the electronic form file. The entry log for all form field value changes clearly records all relevant parameters of the change, the person who entered the entry, the original value before the entry, the new value after the entry, the time of entry, the reason for the change, the modified client information, the modified system environment information, and the modified program information. The digest algorithm and digest value of the entry log are written into the signature dictionary of the electronic form file as part of the signature extension information. This allows for the attribution of responsibility for the entry log for the form field, facilitating the subsequent tracing of the responsibility of the person who filled in or entered the data. Furthermore, digital signatures can also protect electronic documents from tampering. Once an electronic document is published, it's subject to various modifications. If the document is tampered with, the operator's digital signature will fail verification, alerting the user to the tampering, thus providing tamper protection.
[0033] In an embodiment of the present invention, the method 100 further includes: before entering the form field data, collecting information about the electronic form file processing program, the client, hardware and software information related to the entry operation, and environmental information in the entry attribute data.
[0034] Entering form field data involves generating and modifying form data. In one example, before entering form field data, when an electronic form file is opened, a specific form filling program is first executed to collect client host information (such as client host identification, machine name, etc.), system information of the electronic form file processing program, user identity information, server time information, information about the filling program, ambient temperature and humidity, etc. However, the collection of this information is not limited to before entering form field data. When any form field is filled in or the form status is modified during the processing of the electronic form file, the entry log not only simply records the form field value change, but also records the system environment parameter changes corresponding to the form field value. This specific form filling program is a form filling and information collection program that can be used to obtain all system environment parameters (including client information, data source information, system environment information, etc.); this specific form filling program will collect as many system parameters and environment parameters as possible related to form field value changes for subsequent audit and inspection of the electronic form file. After the specific form filling program collects and loads the system information and environment information, the electronic form file is opened for form filling, and log data related to the form field filling or modification is generated during the filling process. The specific form filling program may exist in various forms, such as a mobile app, a desktop application, and a browser plug-in, etc. The specific form filling program may not be embedded in the electronic form processing program.
[0035] System environment information may include the system URL, system name, project name, etc. User identity information may include account ID, account name, account role, etc. Client information may include client host information, client IP address, etc. Collection program version information may include the name and version of the collection program, etc.
[0036] In another example, all clients are required to register in advance to obtain client information, synchronize their time, and adjust each client's time according to a designated clock if necessary. When processing electronic form files, user authentication can be performed by logging into the system with an account to obtain the identity and role information of the person filling out the form. Hardware devices used to process electronic form files can be connected to directly collect parameter information related to the hardware devices. During the processing of electronic form files, system business scripts can be loaded to implement intelligent form filling. System business scripts include initialization scripts, logic control scripts, logic verification scripts, automatic calculation scripts, and form field-related operation scripts. An entry log can also record information about the system business scripts used during the electronic form file processing process. In another example, a specific form filling program can be used to switch entry operators by switching user accounts. Alternatively, multiple people can co-sign within a single interactive interface. Digital signatures must be verified, such as by fingerprint verification or entering the signer's password. User information of the switched operator or multiple co-signers can also be collected.
[0037] User information and reviewer information belong to the file processing system. In the client collection program, the user and reviewer identities can be confirmed through the user and reviewer login operations, and the user identity information and reviewer identity information can be obtained.
[0038] Figure 2 An example of an electronic form file used in the embodiment is shown. The electronic form file 200 shown in the figure is a subject screening form in a clinical trial, including a screening form header 210 and a basic information form 220. The screening form header 210 includes form fields such as the protocol number, study period, subject's initials, and screening number. The basic information form 220 includes form fields such as the collection date (date field), name (single-choice field), gender, date of birth (date field), age, ethnicity (single-choice field), ID number, phone number, emergency contact and phone number, recorder's signature (signature field), alternative (single-choice field), and reviewer (signature field). When the electronic form file 200 is filled out, each form field has a new value, and the input attribute data at least includes the new value of the form field and the last time it was filled out. The valid digital signatures of the recorder's signature and the reviewer indicate that the signed document has been legally modified, the signer's identity has been verified, and the impression has been verified. When the electronic form file 200 is modified later, the original new value in the form field becomes the original value, and the current modified value becomes the new value; the original value, new value and the last filling time of all form fields are saved as input attribute data.
[0039] If the electronic form file 200 resides on a client and is generated or modified on the client, the entry attribute data will be written into the electronic form file 200 on the client. If the electronic form file 200 resides on a network server and can be generated or modified by multiple clients on the network, the entry attribute data will be written into the electronic form file 200 on the server. The entry attribute data may also include at least information about the client used to process the electronic form file 200, such as information about the client that modified data in a particular form field (e.g., the "reviewer" signature). The entry attribute data may be generated on the client during file processing and then transmitted and stored in the electronic form file or database on the server.
[0040] Figure 3 Schematic diagram showing the formation of multiple modified versions of an electronic form file during the generation and modification process of an electronic form file according to an embodiment of the present invention. Figure 3 As shown, the initial version of an electronic form file includes the electronic file body, electronic file metadata, and a digital signature. The body includes descriptions of the document, page, resource, script, and more, but most importantly, the electronic form. An electronic form contains one or more form fields, which are distributed across one or more pages of the electronic form file and, along with background text, describe the electronic file. Electronic file metadata includes information such as the author and modification time. An authentication signature can be optionally affixed to the electronic form file to indicate subsequent permissions, whether form filling is permitted, and whether signatures are permitted.
[0041] After the electronic form file is modified multiple times (such as N times), it will form Figure 3 Each modification, shown in revisions 1 to N, includes incremental modifications to the main text and incremental modifications to the metadata. Incremental modifications to the main text primarily refer to the value entry of form fields in electronic forms, while incremental modifications to metadata refer to all changes made to the file each time it is saved (the form field entry log). If a file save action is executed during file processing, the incremental modification is performed directly without signing. If a signature action is executed during file processing, operator identity verification is performed and a digital signature is affixed. Signature protection is applied to the incremental form entry of the main text and the incremental file modification log of the metadata, with the digest algorithm and digest value entered into the log being written into the signature dictionary.
[0042] Figure 4 A schematic diagram illustrating multiple modified versions of a modification log of an electronic form file generated during a modification process of the electronic form file according to an embodiment of the present invention is shown.
[0043] When modifying an electronic form file, when the form field value changes, the user information, time information, original form field value, new form field value, filling program information, client information, system information, data source information, etc. of the modification are read, and an electronic file modification log containing this information is generated and written into the file modification log cache. When saving an electronic form file or stamping a digital signature on an electronic form file, the file modification log cache is written into the electronic form file as an incremental modification. Incremental modification means writing all electronic file incremental modification and signature data to the end of the original electronic form file while keeping the old version file unchanged, and updating the file structure index to display the new version file, see Figure 3 and Figure 4 When the digital signature is affixed and the electronic form file is saved, the digest algorithm and digest value of the recorded log are written into the signature dictionary of the electronic form file.
[0044] Each time you save an electronic form file or add a digital signature, a new version will be added to the electronic form file modification log (such as Figure 4 Modified version 1, modified version 2, ..., modified version N), each modified version has multiple entry logs (such as Figure 4 As shown in the form field modification log 1, form field modification log 2, ..., form field modification log M), each log contains as many log parameters as possible.
[0045] See also Figure 4 The file modification log is a two-dimensional entity. The first-level directory is modification versions 1 to N, each of which may or may not be digitally signed. The second-level directory is the form field data item modification log (i.e., form field modification log 1, form field modification log 2, ..., form field modification log M). When using the modification version information and form data item modification information, a series of modification versions are obtained, along with information about the person who saved them, the time they were saved, whether they were signed, the client information when they saved them, and the form filling program information. When viewing a specific modification version, a log of all form field value changes for that version is displayed, including the person who filled in the changes, the time they filled in the changes, the client information, and the form filling program information. Furthermore, if the version information is ignored and only the second-level form field modification information for the entire file is viewed, a modification log listing all form field value changes from the original version to the final version is displayed, including the person who filled in the changes, the time they filled in the changes, the client information, and the form filling program information. If the log protected by a digital signature is modified, the form filling program will indicate that the file has been modified and that signature verification failed, prompting the user to proceed with the form filling operation with caution or to stop.
[0046] Figure 5A block diagram of the structure of an apparatus for processing electronic form files according to an embodiment of the present invention is shown. Apparatus 500 includes: a data collection module 510 for collecting input attribute data related to the generation and modification of form field data in the electronic form file during the processing of the electronic form file; and a data recording module 520 for recording the input attribute data collected by data collection module 510 in the electronic form file.
[0047] Those skilled in the art will appreciate that device 500 can implement the various embodiments of the method for processing electronic form files of the present invention as described above. Those skilled in the art will also appreciate that a computer or similar file processing device including a memory and a processor can be implemented as the device for processing electronic form files of the present invention, and can implement the various embodiments of the method for processing electronic form files of the present invention as described above. Those skilled in the art will also appreciate that by storing program instructions that enable a computer to execute the method for processing electronic form files of the present invention on a computer-readable storage medium and combining it with a computer or similar device, the device for processing electronic form files of the present invention can be implemented, and the various embodiments of the method for processing electronic form files of the present invention as described above can be implemented.
[0048] The above embodiments are exemplary and the present invention is not limited to these embodiments. Based on the teachings of the above embodiments, those skilled in the art may make various modifications or adjustments to the above embodiments without departing from the principles of the present invention. The technical solutions of these modifications or adjustments shall still fall within the scope of patent protection of the present invention.
Claims
1. A method for processing an electronic form file, include: During the processing of the electronic form file, collecting input attribute data related to the generation and change of form field data in the electronic form file, wherein the input attribute data includes a collection of input attribute data generated and changed during multiple processing of the electronic form file to form an input log; as well as recording the input attribute data in the electronic form file, The step of recording the input attribute data in the electronic form file comprises: After each form field is filled in effectively, the collected input attribute data of the form field is placed in the cache as a form field modification log, wherein the input attribute data at least includes the original value of the form field, the new value of the form field, and the last filling time; When saving an electronic form file or affixing a digital signature, all form field modification logs in the cache are written into the electronic form file in an incremental modification manner as file modification logs. Incremental modification refers to writing all electronic file incremental modification and signature data at the end of the original electronic form file while maintaining the old version file unchanged, and updating the file structure index. The first-level directory of the file modification log includes each modification version, and the second-level directory includes each form field modification log under each modification version. The version of the file modification log is increased each time the electronic form file is saved or the digital signature is affixed.
2. The method according to claim 1, in, The input attribute data includes at least one of the following: Entry time, entry person information, review person information, program information for processing electronic form files, client information for processing the electronic form files, entry data source information, information about the entry program for automatically entering form field data, physical environment information for entering attribute data, and other entry parameter information.
3. The method according to claim 1, further comprising: include: A digital signature is stamped in the signature field in the electronic form file.
4. The method according to claim 1, in, The input attribute data is log data in XML format or JSON format.
5. The method according to any one of claims 1 to 4, in, When the electronic form file is saved or a digital signature is stamped in the signature field of the electronic form file, the entry attribute data is written into the metadata of the electronic form file as an entry log.
6. The method according to claim 5, in, When a digital signature is stamped in the signature field in the electronic form file, the digest algorithm and digest value of the entry log are written into the signature dictionary of the electronic form file.
7. The method according to claim 1, further comprising: include: Before entering the form field data, the electronic form file processing program, the client, the hardware and software information related to the entry operation, and the environment information in the entry attribute data are collected.
8. A device for processing electronic form files, include: A data collection module, used for collecting input attribute data related to the generation and change of form field data in the electronic form file during the processing of the electronic form file, wherein the input attribute data includes a collection of input attribute data generated and changed during multiple processing of the electronic form file to form an input log; as well as A data recording module, used to record the input attribute data in the electronic form file, The data recording module is used to store the collected input attribute data of each form field as a form field modification log in the cache after each form field is effectively filled in, wherein the input attribute data at least includes the original value of the form field, the new value of the form field, and the last filling time; When saving an electronic form file or affixing a digital signature, all form field modification logs in the cache are written into the electronic form file in an incremental modification manner as file modification logs. Incremental modification refers to writing all electronic file incremental modification and signature data at the end of the original electronic form file while maintaining the old version file unchanged, and updating the file structure index. The first-level directory of the file modification log includes each modification version, and the second-level directory includes each form field modification log under each modification version. The version of the file modification log is increased each time the electronic form file is saved or the digital signature is affixed.
9. A device for processing electronic form files, include: a memory for storing instructions; as well as A processor coupled to the memory, the instructions, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 7.
10. A computer-readable storage medium having stored thereon instructions, which, when executed by a processor of a computer, cause the processor to perform the method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Method and device for recording trace information of electronic file
CN102541825A
Configurable data change flow monitoring method
CN106651092A
Form data marking method, device, storage medium and electronic equipment
CN108133015A
