Document information processing method and computer equipment

Abstract

The embodiment of the invention relates to the field of document information processing, in particular to a document information processing method and computer equipment. A specific embodiment of the method comprises the following steps: for each to-be-processed user information document, executing the following processing steps: performing field analysis processing on the to-be-processed user information document, and storing a user information field group into a user information field table; performing signature processing on the to-be-processed user information document according to the signature information corresponding to the to-be-processed user information document; storing the to-be-processed user information document, the user information field table and the signature user information document into a document information database; reading corresponding user document information from a document information database; and generating feedback information corresponding to the user document information according to an information format request included in the document information reading request. According to the embodiment, user information documents can be uniformly managed, and repeated storage of information is avoided.

Description

Technical Field

[0001] The 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, or further processed such as filling, format conversion, signing, etc. For example, in the insurance business platform, different business systems have different operation requirements. If they are implemented separately in each system, there will be problems such as duplicate information storage, scattered resources, and user privacy cannot be managed uniformly. Summary of the invention

[0003] The content of this application is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this application is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[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 technology section.

[0005] In a first aspect, some embodiments of the present application provide a document information processing method, the method comprising: in response to receiving at least one user information document to be processed, for each user information document to be processed, executing the following processing steps: performing field parsing processing on the above-mentioned user information document to be processed to generate a user information field group, and storing the above-mentioned user information field group in a pre-set user information field table to obtain a user information field table; performing 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; storing the above-mentioned user information document to be processed, the above-mentioned user information field table and the above-mentioned signed user information document in 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 above-mentioned document information database; generating 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 sending the above-mentioned feedback information to the above-mentioned user terminal.

[0006] In a second aspect, the present application also provides a computer device, comprising 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 method described in any implementation of the first aspect is implemented.

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

[0008] The above-mentioned 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 a document information database. Thus, when different user terminals read document information, they can be read according to the permission classification of the user terminal, and information in the corresponding format can be fed back according to the needs of different user terminals. Thus, user information documents can be managed uniformly to avoid repeated storage of information. In addition, since user information documents are centrally stored and managed, and permission settings are performed on user terminals, the confidentiality of user information documents is also improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above and other features, advantages and aspects of the embodiments of the present application will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components 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; Figure 2 It is a schematic diagram of the structure of a computer device suitable for implementing some embodiments of the present application. DETAILED DESCRIPTION

[0011] Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not intended to limit the scope of protection of the present application.

[0012] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0013] It should be noted that the concepts such as "first" and "second" 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.

[0014] It should be noted that the modifications of "one" and "plurality" mentioned in the present application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

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

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

[0017] Figure 1 The process 100 of some embodiments of the document information processing method according to the present application is shown. The document information processing method comprises the following steps: Step 101, 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: Step 1011, 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.

[0018] In some embodiments, the execution subject (e.g., computing device) of the document information processing method 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 needs to be filled, format converted, signed, and further processed. For example, the user information document to be processed may be an information document of a user who needs to be insured (insurance), and may include: user name, user insurance selection information (selected insurance parameters), insured object information, user historical insurance information, etc. For another example, the user information document to be processed may be document information of various insured products (insurance products) for users to browse and select, and may include: product name, product business scope (e.g., insurance items involved), insurance price, compensation cycle, 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, so as to facilitate field extraction and parsing. Document types may include, but are not limited to: user information document, user browsing product information document, and product information push document.

[0019] As an example, first, the document type of the user information document to be processed can be determined. Then, according to the field information extraction table corresponding to the document type, each user information field in the corresponding field information extraction table is extracted from the user information document to be processed as a user information field group. For example, the corresponding user information field can be extracted according to each field name recorded in the field information extraction table.

[0020] Step 1012: based on 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.

[0021] In some embodiments, the execution subject may sign 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. The signature information may include but is not limited to: user number, digital certificate, etc. For example, the signature included in the signature information may be filled in the user information document to be processed to generate a signed user information document.

[0022] In an actual application scenario, the execution subject may perform a signature process on the user information document to be processed through the following steps to generate a signed user information document: The first step is to display the user information document to be processed in the user information document signature interface. The user information document signature interface can be an interface for displaying the user information document to be processed.

[0023] In the second step, a scrolling operation on the document display window in the user information document signature interface is detected, and 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. 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 undisplayed content. The scrolling operation may be an up and down scrolling operation. When the displayed content in the document display window is hidden in the horizontal direction, the scrolling operation may also be a left and right scrolling operation. The document display window may display: documents, images. The displayed content in the document display window may be displayed by projecting the screen in the user information document signature interface. The scrolling operation information corresponding to the scrolling operation may be information recording various data in the scrolling process. For example, the scrolling operation information may include: scrolling direction, current scrolling distance, and scrolling speed. The current scrolling distance may be the height of the document display window scrolled by executing the scrolling operation. The signature window may be a window for displaying signature content. The signature window is transparently superimposed on the upper layer of the document display window. The interactive operation may penetrate the signature window and act on the document display window.

[0024] The third step is to detect the signature operation acting on the document display content in the above document display window, and display the signature corresponding to the above signature operation and the above user information document to be processed in the above signature window according to the above signature information. The above signature operation can be an operation to sign the document display content in the document display window. The signature operation can include: drawing operation and input operation. The drawing content can include the signature drawn by the user. The input content can include the signature input by the user. For example, the above execution subject can synchronously display the signature content corresponding to the above signature operation and the above document display content in the above document display window during the signature operation.

[0025] The fourth step is to determine the window vertex coordinates corresponding to the document display window as the document screenshot vertex coordinates. The window vertex coordinates may be any coordinate on the upper boundary of all document display contents in the document display window. For example, the window vertex coordinates may be the coordinates of the left vertex of the upper boundary. The document screenshot vertex coordinates may be used to calibrate the upper boundary of each screenshot.

[0026] The fifth step is to take screenshots of the document display window and the signature window according to the vertex coordinates of the document screenshot and the operation information corresponding to each detected scrolling operation, and obtain a window screenshot group. Each window screenshot displays the document display content in the document display window and the signature in the signature window. At the location where there is a signature, the corresponding window screenshot simultaneously displays the document display content in the document display window and the signature in the signature window. At the location where there is no signature, the corresponding window screenshot may only display the display content in the document display window. The image height of each window screenshot may be greater than or equal to the display window height of the document display window.

[0027] The execution subject may perform the following screenshot steps based on the document screenshot vertex coordinates: 1. Determine the operation information that meets the preset scrolling condition in the operation information corresponding to the above-mentioned scrolling operations as the target operation information, and obtain the target operation information group. The above-mentioned preset scrolling condition 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 scrolling in the up and down directions. When the scrolling operation is scrolling down, the current scrolling distance included in the operation information can be a positive number. When the scrolling operation is scrolling up, the current scrolling distance included in the operation information can be a negative number.

[0028] 2. Generate a scroll distance corresponding to the vertex coordinates of the document screenshot according to the target operation information group. The sum of each current scroll distance included in each target operation information can be determined as the scroll distance corresponding to the vertex coordinates of the document screenshot.

[0029] 3. In response to determining that the scroll distance is greater than or equal to the display window height of the document display window, the document display window and the signature window are screenshotted according to the document screenshot vertex coordinates and the display window height to obtain a window screenshot. For example, the execution subject may first determine the sum of the display window height and the preset height as the screenshot height. The preset height may be 0 or a height set to prevent missed screenshots. Then, the document display window and the signature window may be screenshotted from the height corresponding to the screenshot vertex downward to obtain the window screenshot.

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

[0031] Step 6. Fill each window screenshot in the window screenshot group into the blank document in order to obtain a signed user information document.

[0032] The sixth step may include: Sub-step 1: splice the above-mentioned window screenshots into an initial window screenshot image in sequence according to the screenshot order of each window screenshot. The above-mentioned execution subject can splice the above-mentioned window screenshots up and down in sequence according to the screenshot order of each window screenshot obtained to obtain the initial window screenshot image.

[0033] Sub-step 2: For each screenshot stitching boundary area in the above initial window screenshot image, perform the following deduplication processing: 1. Determine whether there is a pixel-repeating area in the screenshot stitching boundary area. The screenshot stitching boundary area may be an image area that extends upward and downward from the stitching boundary of the initial window screenshot image by a preset extension height. There is no limitation on the setting of the preset extension height. The pixel-repeating area may be an image area in a window screenshot that has pixels that repeat in the stitching boundary area with an adjacent window screenshot.

[0034] 2. In response to determining that there is a pixel duplication region in the screenshot stitching boundary region, deduplication processing is performed on the pixel duplication boundary region.

[0035] Sub-step 3, filling the initial window screenshot image obtained after deduplication processing into a blank document to obtain a signed user information document.

[0036] 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 scrolls synchronously with the document display window, dynamic signature can be achieved. In addition, automatic screenshots can be taken as the window scrolls, so that the obtained signature file can record the complete document display content and the complete signature content.

[0037] Step 1022, storing the user information document to be processed, the user information field table and the signed user information document into a document information database.

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

[0039] Step 103: in response to receiving a document information reading request sent by the user terminal, reading corresponding user document information from the document information database.

[0040] In some embodiments, the execution subject may read the corresponding user document information from the document information database in response to receiving a document information reading request sent by a user terminal. The user terminal may be an access terminal for reading document information. The document information reading request may refer to a reading request carried by the user terminal with a document information identifier. There is a document information identifier for each user document information.

[0041] Step 104: 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.

[0042] In some embodiments, the execution subject may generate feedback information corresponding to the user document information according to the information format request included in the document information reading request, and send the feedback information to the user terminal. The information format request may indicate a format request for the feedback information required by the user terminal. For example, the information format request may refer to a request for feedback information in a picture format or a PDF format, etc.

[0043] In an actual application scenario, the execution subject may generate feedback information corresponding to the user document information through the following steps: The first step is to determine whether the user terminal has the document information access right. That is, it can be determined whether the terminal identification of the user terminal has the document information access right. This can be queried in a pre-set terminal access right table. The terminal access right table can be a mapping table of each user terminal that can access the document information.

[0044] In the second step, in response to determining that the user terminal has document information access rights, determine the document information type corresponding to the document information read request. The document information type can indicate the type of document information being accessed. The document information type can include a public document type and a private document type. The public document type indicates that the document information of this type can be accessed. The private document type indicates that the document information of this type requires permission to be accessed.

[0045] In a third step, in response to determining that the document information type represents a public document type, the user document information is rendered according to the information format request to generate rendered user document information.

[0046] In a fourth step, in response to determining that the document information type represents a private document type, determining whether the document information access permission has a private document access permission.

[0047] In a fifth step, in response to determining that the document information access right has a private document access right, the user document information is rendered according to the information format request to generate rendered user document information.

[0048] The sixth step is to generate an access address corresponding to the rendered user document information as feedback information corresponding to the above user document information. That is, the access address may refer to a link address of the rendered user document information.

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

[0050] Furthermore, in response to receiving the update configuration information corresponding to the user information field table, the to-be-updated field data corresponding to the to-be-updated field information is read from the user information field table.

[0051] In some embodiments, the execution subject may read the to-be-updated field data corresponding to the to-be-updated field information from the user information field table in response to receiving the update configuration information corresponding to the user information field table. 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 multiple update field variables, and the update mode information corresponds to the update field variables among the multiple update field variables. The update configuration information may be pre-configured configuration item related information when updating the user information field table. The update configuration information may be stored in a structured file. For example, the structured file may be a yml file. The to-be-updated field information may be configuration information for locating a position or data in the to-be-updated user information field table. For example, the to-be-updated field information may include row and column positioning conditions. The row and column positioning conditions may be used to locate cells to be updated. The update field variable information may be configuration information for locating data in the user information field table corresponding to the updated field variable. The update field variable information may correspond to at least one update field variable. The update field variable information may include variable row and column positioning conditions corresponding to each update field variable. The update mode information may be configuration information for the update mode. The update mode information corresponds to the update field variable in the at least one update field variable, and it can be understood that the update mode information can be constructed based on the update field variables. For example, the update mode information can be an arithmetic expression constructed using the update field variables.

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

[0053] Furthermore, the above field data to be updated is added to a list of field data to be updated.

[0054] In some embodiments, the execution subject may add the field data to be updated to a list of field data to be updated. The list of field data to be updated may be a list for storing located field data to be updated. The list of field data to be updated may be predefined, and in the list of field data to be updated, data is stored in the form of key-value pairs.

[0055] Furthermore, according to the user information field table, update field data corresponding to the update field variable information is determined, and the update field data is added to the update field data list.

[0056] In some embodiments, the execution entity may determine the update field data corresponding to the update field variable information according to the user information field table, and add the update field data to the update field data list.

[0057] In an actual application scenario, the above execution subject can determine the update field data corresponding to the update field variable information through the following steps: In the first step, in response to determining that the update configuration information includes external field table information, the update field variable corresponding to the external field table information is determined as the external update field variable. The external field table information may be a file identifier of an external table file configured for the update field variable that is different from the user information field table, and may indicate that the update field variable needs to be assigned table data from the external table file.

[0058] In the second step, for each of the multiple update field variables, the following processing steps are performed: 1. In response to determining that the update field variable is an external update field variable, determine the external field table corresponding to the external field table information of the update field variable as the external field table.

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

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

[0061] The third step is to determine each determined external field variable data as the updated field data corresponding to the above-mentioned updated field variable information.

[0062] Furthermore, based on the updated list of field data to be updated, the list of updated field data and the above-mentioned update mode information, the above-mentioned user information field table is updated.

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

[0064] Therefore, because the update method information directly corresponds to the update field variable, the required data can be directly located from the update field data list according to the update field variable corresponding to the update method information, and then after determining the update content according to the update method information, the user information field table update table that needs to be updated can be updated according to the field data list to be updated. Therefore, the process of updating the user information field table can be decoupled into the process of update configuration, update method configuration, and data location configuration, which improves the flexibility when developing the user information field table update method. The present application also provides a computer device 200. Figure 2 As 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 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computer device 200.

[0065] The bus 201 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2 The bus 201 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).

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

[0067] 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).

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

[0069] 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.

[0070] An embodiment of the present application also 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 above-mentioned document information processing method.

[0071] The embodiment of the present application also provides a computer-readable storage medium. The above-mentioned 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 containing one or more available media. The above-mentioned available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid-state hard disk). The computer-readable storage medium includes instructions, and the above-mentioned instructions instruct the computing device to execute the above-mentioned document information processing method.

[0072] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0073] 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 aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions 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