Document Information Processing Method, Computer Device

Abstract

Embodiments of the present application relate to the field of document information processing, and specifically to a document information processing method and a computer device. A specific implementation of the method includes: for each user information document to be processed, perform the following processing steps: perform field parsing processing on the user information document to be processed, and store the user information field group in a user information field table; perform signature processing on the user information document to be processed according to the signature information corresponding to the user information document to be processed; store the user information document to be processed, the user information field table, and the signed user information document in a document information database; read the corresponding user document information from the document information database; generate feedback information corresponding to the user document information according to the information format request included in the document information read request. This implementation can uniformly manage user information documents and avoid duplicate storage of information.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of document information processing, and specifically to a document information processing method and a computer device. Background Art

[0002] When storing document information, there are often various PDF (Portable Document Format) documents that need to be displayed, filled, format-converted, signed, etc. For example, in an insurance business platform, different business systems have different operation requirements. If implemented separately in each system, problems such as duplicate information storage, scattered resources everywhere, and inability to uniformly manage user privacy will occur. Summary of the Invention

[0003] The content part of the present application is used to briefly introduce concepts, which will be described in detail in the specific implementation part later. The content part of the present application is not intended to identify the key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0004] Some embodiments of the present application propose a document information processing method, a computer device, and a computer-readable storage medium to solve one or more of the technical problems mentioned in the above background art part.

[0005] In a first aspect, some embodiments of the present application provide a document information processing method, which includes: in response to receiving at least one user information document to be processed, for each user information document to be processed, performing the following processing steps: performing field parsing processing on the user information document to be processed to generate a user information field group, and storing the user information field group into a pre-set user information field table to obtain a user information field table; performing signature processing on the user information document to be processed according to the signature information corresponding to the user information document to be processed to generate a signed user information document; storing the user information document to be processed, the user information field table, and the signed user information document into a document information database; in response to receiving a document information reading request sent by a user terminal, reading the corresponding user document information from the document information database; generating feedback information corresponding to the user document information according to the information format request included in the document information reading request, and sending the feedback information to the user terminal.

[0006] In a second aspect, the present application further provides a computer device, which includes a processor, a memory, and a computer program stored on the memory and executable by the processor. When the computer program is executed by the processor, it implements the method described in any implementation manner of the first aspect above.

[0007] In a third aspect, the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method described in any implementation manner of the first aspect is implemented.

[0008] The above-mentioned various embodiments of the present application have the following beneficial effects: The user information document to be processed can be subjected to field extraction and signature processing, and the processed document information can be stored in the document information database. Thus, when the document information is read on different user terminals, it can be read according to the permission classification of the user terminals, and information in a corresponding format can be fed back according to the requirements of different user terminals. Thus, the user information documents can be uniformly managed to avoid duplicate storage of information. In addition, due to the centralized storage management of the user information documents and the permission setting for the user terminals, the confidentiality of the user information documents is also improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages and aspects of the embodiments of the present application will become more apparent. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the elements and elements are not necessarily drawn to scale.

[0010] Figure 1 is a flowchart of some embodiments of the document information processing method according to the present application;

[0011] Figure 2 is a schematic structural diagram of a computer device suitable for implementing some embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0012] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not used to limit the protection scope of the present application.

[0013] It should also be noted that, for the sake of convenience of description, only parts related to the relevant invention are shown in the drawings. Without conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0014] It should be noted that the concepts such as "first", "second", etc. mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0015] It should be noted that the modifications of "one" and "multiple" mentioned in this application are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".

[0016] The names of the messages or information exchanged between multiple devices in the embodiments of this application are only for illustrative purposes, and are not used to limit the scope of these messages or information.

[0017] The present application will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0018] Figure 1 Flow 100 of some embodiments of a document information processing method according to the present application is shown. The document information processing method includes the following steps:

[0019] Step 101, in response to receiving at least one user information document to be processed, for each user information document to be processed, perform the following processing steps:

[0020] Step 1011, perform field parsing processing on the above-mentioned user information document to be processed to generate a user information field group, and store the above-mentioned user information field group in a pre-set user information field table to obtain a user information field table.

[0021] In some embodiments, the execution subject of the document information processing method (e.g., a computing device) may perform field parsing processing on the above-mentioned user information document to be processed to generate a user information field group, and store the above-mentioned user information field group in a pre-set user information field table to obtain a user information field table. The user information document to be processed may refer to a user information PDF document that needs to be displayed, or further processed such as filled, format-converted, signed, etc. For example, the user information document to be processed may be an information document of a user who needs to apply for insurance, and may include: user name, user insurance selection information (selected insurance parameters), insured object information, user's historical claim information, etc. As another example, the user information document to be processed may be the document information of each insurance product (insurance product) for the user to browse and select, and may include: product name, product business scope (e.g., involved insurance items), insurance price, claim period, etc. One user information document to be processed corresponds to one document type. The document type may indicate which type of document the user information document to be processed belongs to, facilitating field extraction and parsing. The document type may include but is not limited to: user information document, user browsing product information document, product information push document.

[0022] As an example, first, the document type of the user information document to be processed may be determined. Secondly, according to the field information extraction table corresponding to the document type, each user information field corresponding to the field information extraction table is extracted from the above-mentioned user information document to be processed as a user information field group. For example, the corresponding user information fields may be extracted according to each field name recorded in the field information extraction table.

[0023] Step 1012, perform signature processing on the above-mentioned user information document to be processed according to the signature information corresponding to the above-mentioned user information document to be processed to generate a signed user information document.

[0024] In some embodiments, the above-mentioned execution subject may perform signature processing on the above-mentioned user information document to be processed according to the signature information corresponding to the above-mentioned user information document to be processed to generate a signed user information document. The signature information may include but is not limited to: user number, digital certificate, etc. For example, the signature information may be filled in the user information document to be processed to generate a signed user information document.

[0025] In an actual application scenario, the above-mentioned execution subject may perform signature processing on the above-mentioned user information document to be processed through the following steps to generate a signed user information document:

[0026] The first step is to display the above-mentioned user information document to be processed in the user information document signature interface. The above-mentioned user information document signature interface may be an interface for displaying the user information document to be processed.

[0027] In the second step, a scrolling operation acting on the document display window in the user information document signature interface is detected. According to the operation information corresponding to the scrolling operation, the document display window and the signature window corresponding to the document display window are synchronously scrolled in the user information document signature interface. Among them, the signature window is superimposed on the document display window. The scrolling operation may be an operation of scrolling the document display window to view the content that is not displayed. The scrolling operation may be an up and down scrolling operation. When there is content hidden horizontally in the display content in the document display window, the scrolling operation may also be a left and right scrolling operation. The document display window may display: documents, images. The display content in the document display window may be projected and displayed in the user information document signature interface. The scrolling operation information corresponding to the scrolling operation may be information for recording various data during the scrolling process. For example, the scrolling operation information may include: scrolling direction, current scrolling distance, scrolling speed. The current scrolling distance may be the height of the document display window scrolled by performing the scrolling operation. The signature window may be a form for displaying signature content. The signature window is transparently superimposed on the upper layer of the document display window. Interaction operations can penetrate the signature window and act on the document display window.

[0028] In the third step, a signature operation acting on the document display content in the document display window is detected. According to the signature information, the signature corresponding to the signature operation and the to-be-processed user information document is displayed in the signature window. Among them, the signature operation may be an operation of signing the document display content of the document display window. The signature operation may include: drawing operation, input operation. The drawn content may include the signature drawn by the user. The input content may include the signature input by the user. For example, the execution subject may synchronously display the signature content corresponding to the signature operation and the document display content in the document display window during the signature operation.

[0029] In the fourth step, the window vertex coordinates corresponding to the document display window are determined as the document screenshot vertex coordinates. Among them, the form vertex coordinates may be any coordinate on the upper boundary of all the document display content in the document display window. For example, the form vertex coordinates may be the coordinates of the left vertex of the upper boundary. The document screenshot vertex coordinates can be used to calibrate the upper boundary of each screenshot.

[0030] Step 5: Based on the vertex coordinates of the document screenshot and the operation information corresponding to each detected scrolling operation, perform screenshot processing on the above-mentioned document display window and the above-mentioned signature window to obtain a group of window screenshots. Each window screenshot shows the document display content in the document display window and the signature in the above-mentioned signature window. At the position where there is a signature, the corresponding window screenshot shows both the document display content in the document display window and the signature in the above-mentioned signature window. At the position where there is no signature, the corresponding window screenshot may only show the display content in the document display window. The image height of each window screenshot can be greater than or equal to the display window height of the above-mentioned document display window.

[0031] Among them, the above-mentioned execution entity can perform the following screenshot steps based on the vertex coordinates of the document screenshot:

[0032] 1. Determine the operation information that meets the preset scrolling conditions in the operation information corresponding to each of the above-mentioned scrolling operations as the target operation information to obtain a group of target operation information. The above-mentioned preset scrolling conditions can be that the scrolling start position corresponding to the scrolling operation is below the vertex coordinates of the document screenshot, and the scrolling operation is a vertical scrolling. When the scrolling operation is a downward scroll, the current scrolling distance included in the operation information can be a positive number. When the scrolling operation is an upward scroll, the current scrolling distance included in the operation information can be a negative number.

[0033] 2. Generate a scrolling distance corresponding to the vertex coordinates of the document screenshot according to the above-mentioned group of target operation information. The sum of the current scrolling distances included in each of the target operation information can be determined as the scrolling distance corresponding to the vertex coordinates of the document screenshot.

[0034] 3. In response to determining that the scrolling distance is greater than or equal to the display window height of the above-mentioned document display window, perform screenshot processing on the above-mentioned document display window and the above-mentioned signature window according to the vertex coordinates of the document screenshot and the above-mentioned display window height to obtain a window screenshot. For example, the above-mentioned execution entity can first determine the sum of the above-mentioned display window height and a preset height as the screenshot height. The preset height can be 0 or a height set to prevent missing screenshots. Then, it can perform a screenshot of the above-mentioned document display window and the above-mentioned signature window from the height corresponding to the screenshot vertex downward by the above-mentioned screenshot height to obtain a window screenshot.

[0035] 4. Update the vertex coordinates of the document screenshot according to the vertex coordinates of the document screenshot and the above-mentioned display window height, and based on the updated vertex coordinates of the document screenshot, perform the above-mentioned screenshot steps again. The ordinate of the vertex coordinates of the document screenshot can be determined as the ordinate of the updated vertex coordinates of the document screenshot by adding the sum of the ordinate of the vertex coordinates of the document screenshot and the display window height to update the vertex coordinates of the document screenshot.

[0036] Step 6: Fill each window screenshot in the group of window screenshots into a blank document in sequence to obtain a signed user information document.

[0037] Among them, the above-mentioned sixth step may include:

[0038] Sub-step 1: Arrange the above window screenshots in sequence according to the screenshot sequence of each window screenshot, and splice the above window screenshots into an initial window screenshot image in turn. The above execution entity may splice the above window screenshots vertically in sequence according to the screenshot sequence of the obtained window screenshots to obtain an initial window screenshot image.

[0039] Sub-step 2: For each screenshot splicing boundary area in the above initial window screenshot image, perform the following duplicate removal process:

[0040] 1. Determine whether there is a pixel duplicate area in the above screenshot splicing boundary area. Among them, the screenshot splicing boundary area may be an image area that extends a preset extension height upward and downward from the splicing boundary of the initial window screenshot image. There is no limitation on the setting of the preset extension height. The pixel duplicate area may be an image area in a window screenshot where the pixels are duplicated with an adjacent window screenshot within the splicing boundary area.

[0041] 2. In response to determining that there is a pixel duplicate area in the above screenshot splicing boundary area, perform duplicate removal processing on the boundary area with duplicate pixels.

[0042] Sub-step 3: Fill the initial window screenshot image obtained after duplicate removal processing into a blank document to obtain a signed user information document.

[0043] Thus, when signing the document display content in the document display window, the signature content can be displayed in the signature window. Also, because the signature window is transparent, the user can directly view the document display content in the document display window through the signature window. Also, because the signature window and the document display window scroll synchronously, dynamic signature can be achieved. In addition, automatic screenshot can be performed following the scrolling of the window, so that the obtained signature file records the complete document display content and the complete signature content.

[0044] Step 1022: Store the above to-be-processed user information document, the above user information field table, and the above signed user information document in the document information database.

[0045] In some embodiments, the above execution entity may store the above to-be-processed user information document, the above user information field table, and the above signed user information document in the document information database. The document information database may refer to a database for storing document information. For example, the above to-be-processed user information document, the above user information field table, and the above signed user information document may be mapped to document information. Then, the document information is stored in the document information database.

[0046] Step 103: In response to receiving a document information reading request sent by a user terminal, read the corresponding user document information from the above-mentioned document information database.

[0047] In some embodiments, the above-mentioned execution entity may, in response to receiving a document information reading request sent by a user terminal, read the corresponding user document information from the above-mentioned document information database. The user terminal may be an access terminal for reading document information. The document information reading request may refer to a reading request in which the user terminal carries a document information identifier. Each user document information has a document information identifier.

[0048] Step 104: Generate feedback information corresponding to the above-mentioned user document information according to the information format request included in the above-mentioned document information reading request, and send the above-mentioned feedback information to the above-mentioned user terminal.

[0049] In some embodiments, the above-mentioned execution entity may generate feedback information corresponding to the above-mentioned user document information according to the information format request included in the above-mentioned document information reading request, and send the above-mentioned feedback information to the above-mentioned user terminal. The information format request may represent the format request of the feedback information required by the user terminal. For example, the information format request may refer to a request that the feedback information is in picture format, or in PDF format, etc.

[0050] In an actual application scenario, the above-mentioned execution entity may generate feedback information corresponding to the above-mentioned user document information through the following steps:

[0051] The first step: Determine whether the above-mentioned user terminal has document information access rights. That is, it can be determined whether the terminal identifier of the user terminal has document information access rights. It can be queried in a pre-set terminal permission access table. The terminal permission access table may be a mapping table of each user terminal that can access document information.

[0052] The second step: In response to determining that the above-mentioned user terminal has document information access rights, determine the document information type corresponding to the above-mentioned document information reading request. The document information type may represent the type of the accessed document information. The document information type may include a public document type and a private document type. The public document type indicates that all document information of this type can be accessed. The private document type indicates that document information of this type requires permissions to be accessed.

[0053] The third step: In response to determining that the above-mentioned document information type represents the public document type, render the above-mentioned user document information according to the above-mentioned information format request to generate rendered user document information.

[0054] The fourth step: In response to determining that the above-mentioned document information type represents the private document type, determine whether the above-mentioned document information access rights have private document access rights.

[0055] In the fifth step, in response to determining that the above-mentioned document information access permission has private document access permission, render the above-mentioned user document information according to the above-mentioned information format request to generate rendered user document information.

[0056] In the sixth step, generate an access address corresponding to the rendered user document information as feedback information corresponding to the above-mentioned user document information. That is, the access address can refer to the link address of the rendered user document information.

[0057] Thus, when the user terminal accesses information, the diversity and compatibility of information feedback are improved, and the reading requirements of various terminals can be met.

[0058] Further, in response to receiving update configuration information for the corresponding user information field table, read the to-be-updated field data corresponding to the to-be-updated field information from the above-mentioned user information field table.

[0059] In some embodiments, the above-mentioned execution subject can, in response to receiving update configuration information for the corresponding user information field table, read the to-be-updated field data corresponding to the to-be-updated field information from the above-mentioned user information field table. Among them, the above-mentioned update configuration information includes: to-be-updated field information, update field variable information, and update method information. The above-mentioned update field variable information corresponds to multiple update field variables, and the above-mentioned update method information corresponds to the update field variables among the above-mentioned multiple update field variables. The above-mentioned update configuration information can be configuration item-related information for pre-configuring the update of the user information field table. The above-mentioned update configuration information can be stored in a structured file. For example, the structured file can be a yml file. The to-be-updated field information can be configuration information for positioning the position or data in the user information field table to be updated. For example, the to-be-updated field information can include row and column positioning conditions. The row and column positioning conditions can be used to locate the cells that need to be updated. The above-mentioned update field variable information can be configuration information for positioning the data in the user information field table corresponding to the updated field variables. The above-mentioned update field variable information can correspond to at least one update field variable. The above-mentioned update field variable information can include variable row and column positioning conditions corresponding to each update field variable. The above-mentioned update method information can be configuration information for the update method. The above-mentioned update method information corresponds to the update field variables among the above-mentioned at least one update field variable, and it can be understood that the update method information can be based on the construction of the participating update field variables. For example, the update method information can be an arithmetic expression constructed using the update field variables.

[0060] As an example, the execution subject can read cell data from the above-mentioned user information field table according to the above-mentioned row and column positioning conditions to obtain at least one cell data as the to-be-updated field data corresponding to the above-mentioned to-be-updated field information.

[0061] Further, add the above-mentioned data of the fields to be updated to the list of data of the fields to be updated.

[0062] In some embodiments, the above-mentioned execution entity may add the above-mentioned data of the fields to be updated to the list of data of the fields to be updated. Among them, the above-mentioned list of data of the fields to be updated may be a list for storing the data of the fields to be updated for positioning. The list of data of the fields to be updated may be predefined, and in the list of data of the fields to be updated, the data is stored in the form of key-value pairs.

[0063] Further, according to the above-mentioned user information field table, determine the data of the fields to be updated corresponding to the information of the variables of the fields to be updated, and add the above-mentioned data of the fields to be updated to the list of data of the fields to be updated.

[0064] In some embodiments, the above-mentioned execution entity may determine the data of the fields to be updated corresponding to the information of the variables of the fields to be updated according to the above-mentioned user information field table, and add the above-mentioned data of the fields to be updated to the list of data of the fields to be updated.

[0065] In an actual application scenario, the above-mentioned execution entity may determine the data of the fields to be updated corresponding to the information of the variables of the fields to be updated through the following steps:

[0066] First step, in response to determining that the above-mentioned update configuration information includes external field table information, determine the update field variable corresponding to the above-mentioned external field table information as an external update field variable. Among them, the above-mentioned external field table information may be the file identifier of an external table file configured for the update field variable and different from the above-mentioned user information field table, and may represent that the update field variable needs to assign table data from the external table file.

[0067] Second step, for each of the above-mentioned multiple update field variables, perform the following processing steps:

[0068] 1. In response to determining that the above-mentioned update field variable is an external update field variable, determine the external field table corresponding to the external field table information of the above-mentioned update field variable as the external field table.

[0069] 2. Read the external field variable data corresponding to the above-mentioned update field variable from the above-mentioned external field table.

[0070] 3. In response to determining that the above-mentioned update field variable is not an external update field variable, read the external field variable data corresponding to the above-mentioned update field variable from the above-mentioned user information field table.

[0071] Third step, determine the determined external field variable data as the data of the fields to be updated corresponding to the above-mentioned information of the variables of the fields to be updated.

[0072] Further, based on the updated list of fields to be updated, the list of updated fields, and the above update method information, update the above user information field table.

[0073] In some embodiments, the above execution entity may update the above user information field table based on the updated list of fields to be updated, the list of updated fields, and the above update method information. In practice, first, the above execution entity may input the above update method information into a pre-encapsulated update method to obtain table update data. The above update method may be a method that takes the update method information as a method input parameter and outputs the determined table update data to execute the update method corresponding to the update method information. The above update method may directly read the updated field data from the above list of updated fields. For example, the update method may be expressed as CalRuleHandler.cal(). Then, the above execution entity may update the table update data to the cell position corresponding to the field data to be updated stored in the column of fields to be updated in the user information field table to update the above user information field table.

[0074] Thus, because the update method information directly corresponds to the updated field variables, the data to be used can be directly located from the list of updated fields according to the updated field variables corresponding to the update method information. Furthermore, after determining the update content according to the update method information, the user information field table can be updated according to the fields in the list of fields to be updated that need to be updated. Thus, the process of updating the user information field table can be decoupled into a process of update configuration, update method configuration, and data location configuration, improving the flexibility in developing the update method of the user information field table.

[0075] This application also provides a computer device 200. As Figure 2 shown, the computer device 200 includes: a bus 201, a processor 202, a memory 203, and a communication interface 204. The processor 202, the memory 203, and the communication interface 204 communicate with each other through the bus 201. The computer device 200 may be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computer device 200.

[0076] The bus 201 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2It is represented by only one line, but it does not mean that there is only one bus or one type of bus. The bus 201 may include a path for transmitting information between various components of the computer device 200 (for example, the memory 203, the processor 202, and the communication interface 204).

[0077] The processor 202 may include any one or more of processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0078] The memory 203 may include a volatile memory, such as a random access memory (RAM). The memory 203 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0079] The memory 203 stores executable program codes, and the processor 202 executes the executable program codes to respectively implement the functions of the foregoing acquisition module, sampling module, determination module, and mixing module, so as to implement the method for processing the foregoing document information. That is, the memory 203 stores instructions for executing the method for processing the foregoing document information.

[0080] The communication interface 204 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computer device 200 and other devices or a communication network.

[0081] An embodiment of this application further provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to execute the method for processing the foregoing document information.

[0082] The embodiment of the present application also provides a computer-readable storage medium. The above computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center including one or more available media. The above available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid-state drive), etc. The computer-readable storage medium includes instructions that direct the computing device to execute the method for processing the above document information.

[0083] The technical features of the above-described embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0084] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A document information processing method, comprising: In response to receiving at least one user information document to be processed, for each user information document to be processed, the following processing steps are performed: Performing field parsing processing on the user information document to be processed to generate a user information field group, and storing the user information field group in a preset user information field table to obtain a user information field table; According to the signature information corresponding to the user information document to be processed, the user information document to be processed is signed to generate a signed user information document; Storing the to-be-processed user information document, the user information field table and the signed user information document in a document information database; In response to receiving a document information reading request sent by a user terminal, reading corresponding user document information from the document information database; According to the information format request included in the document information reading request, feedback information corresponding to the user document information is generated, and the feedback information is sent to the user terminal.

2. The document information processing method according to claim 1, wherein: The step of generating feedback information corresponding to the user document information according to the information format request included in the document information reading request includes: Determining whether the user terminal has document information access permission; In response to determining that the user terminal has document information access rights, determining a document information type corresponding to the document information reading request; In response to determining that the document information type represents a public document type, rendering the user document information according to the information format request to generate rendered user document information; In response to determining that the document information type represents a private document type, determining whether the document information access right has a private document access right; In response to determining that the document information access permission has a private document access permission, rendering the user document information according to the information format request to generate rendered user document information; An access address corresponding to the rendered user document information is generated as feedback information corresponding to the user document information.

3. The document information processing method according to claim 1, wherein: The method further comprises: In response to receiving update configuration information corresponding to the user information field table, reading the to-be-updated field data corresponding to the to-be-updated field information from the user information field table, wherein the update configuration information includes: to-be-updated field information, update field variable information and update mode information, the update field variable information corresponds to a plurality of update field variables, and the update mode information corresponds to an update field variable among the plurality of update field variables; Add the field data to be updated to the field data to be updated list; According to the user information field table, determining the update field data corresponding to the update field variable information, and adding the update field data to the update field data list; The user information field table is updated based on the updated to-be-updated field data list, the updated field data list and the update mode information.

4. The document information processing method according to claim 3, wherein: The step of determining the update field data corresponding to the update field variable information according to the user information field table includes: In response to determining that the update configuration information includes external field table information, determining the update field variable corresponding to the external field table information as the external update field variable; For each update field variable in the plurality of update field variables, the following processing steps are performed: In response to determining that the update field variable is an external update field variable, determining the external field table corresponding to the external field table information of the update field variable as the external field table; Reading external field variable data corresponding to the update field variable from the external field table; In response to determining that the update field variable is not an external update field variable, reading external field variable data corresponding to the update field variable from the user information field table; The determined external field variable data are determined as update field data corresponding to the update field variable information.

5. A computer device, wherein: The computer device comprises a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 4 are implemented.

6. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images