Form verification method and related equipment

Abstract

The embodiment of the invention discloses a form verification method and related equipment, and relates to the technical field of computers. In the specification, a submission request for submitting a form for processing a transaction is received, the form is provided with a plurality of form items, and the plurality of form items respectively correspond to item data; in response to the submission request, synchronously receiving the form and asynchronously checking at least one piece of target project data in the plurality of pieces of project data, a target form project corresponding to the target project data is irrelevant to the field to which the transaction belongs, that is, in the pre-checking process before the form is put into the library, the form is synchronously received, and at least one piece of target project data is asynchronously checked; only checking whether target project data corresponding to a target form project irrelevant to the field to which the transaction belongs on the form is legal and compliant or not; and further, when it is determined that the at least one piece of target project data is successfully verified according to the verification result, the form is stored in a field verification database for subsequent field verification.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular, to a form verification method and related devices. Background Art

[0002] A page form can be understood as a form on a page such as an HTML page for collecting information input by users. Users can input corresponding data through multiple items on the form, and these data can then be submitted to the server for processing. In other words, the page form is an important bridge for front-end data to reach the server backend.

[0003] Generally speaking, a page form will contain multiple data items and various data types. The more common types include custom text, date, number, etc. For multiple data submitted through the page form, sufficient pre-submission verification checks are often required before they can be received and processed by the server backend. During the pre-submission verification check of data, it can be divided into front-end pre-verification check and backend acceptance verification check. The purpose of front-end pre-verification is to reduce the error submission rate and the pressure on the backend server. It usually only includes simple format verifications, such as required field verification, text length verification, data format verification, etc. Backend acceptance verification is an essential verification to ensure the accuracy of data. On the basis of front-end pre-verification, it usually includes transaction consistency verification. This part of the verification is usually related to transaction logic and often involves third-party service dependency verification, with characteristics such as complex logic, complex dependencies, and uncontrollable time consumption. When there are many such complex and time-consuming verification items, the response time of backend acceptance verification will become longer, bringing a bad experience to users. Summary of the Invention The embodiments of this specification provide a form verification method and related devices, which can solve the above problems. The technical solutions are as follows: In a first aspect, the embodiments of this specification provide a form verification method, and the method includes: Receiving a submission request for a form for processing a transaction; wherein, the form includes item data corresponding to multiple form items; In response to the submission request, synchronously receiving the form and asynchronously verifying at least one target item data among the multiple item data; wherein, the target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs; When it is determined that all the at least one target item data pass the verification according to the verification result, determining to store the form in the domain verification database.

[0004] In a second aspect, the embodiments of this specification provide a form verification device, and the device includes: A form receiving module, configured to receive a submission request for a form for processing a transaction; wherein, the form includes item data corresponding to multiple form items respectively; An asynchronous verification module, configured to synchronously receive the form in response to the submission request, and asynchronously verify at least one target item data among the multiple item data; wherein, the target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs; A form storage module, configured to determine that when all the at least one target item data are verified successfully according to the verification result, store the form into a field verification database.

[0005] In a third aspect, an embodiment of this specification provides a computer storage medium, which stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the above method steps.

[0006] In a fourth aspect, an embodiment of this specification provides a computer program product, which stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the above method steps.

[0007] In a fifth aspect, an embodiment of this specification provides an electronic device, which may include: a processor and a memory; wherein, the memory stores a computer program, and the computer program is suitable for being loaded and executed by the processor to perform the above method steps.

[0008] The beneficial effects brought by the technical solutions provided by some embodiments of this specification at least include: In this specification, a submission request for submitting a certain form is received. The form for processing a certain transaction is provided with multiple form items, and the submission request carries the item data corresponding to the multiple form items respectively. Further, in response to the submission request, the form is synchronously received and at least one target item data among the multiple item data is asynchronously verified. The target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs. In other words, during the pre-verification process before storing the form in the database, only the legality and compliance of the target item data corresponding to the target form item that has nothing to do with the field to which the transaction belongs on the form are verified, ensuring a clear boundary of responsibilities between the pre-verification before storing the form in the database and the field verification after storing the form in the database.

[0009] Further, when it is determined that all at least one target item data passes the verification according to the verification result, the form is stored in the domain verification database for subsequent domain verification. In this specification, by asynchronously transforming the pre-verification and synchronously receiving the form, the efficiency of the front-end device submitting the form can be avoided from being affected. At the same time, multiple target item data on the form are asynchronously verified, and based on the verification result, the front-end device is supported to modify the target item data that fails the verification on the form multiple times until the verification is successful, thereby improving the success rate of the form being stored in the database, solving the problem of high time consumption for form submission, and ensuring a good submission experience for the users of the front-end device. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of this specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0011] Figure 1 is a schematic structural diagram of a form verification method provided by an embodiment of this specification; Figure 2 is a schematic flowchart of a form verification method provided by an embodiment of this specification; Figure 3 is a schematic flowchart of a form verification method provided by an embodiment of this specification; Figure 4 is a schematic flowchart of a process for obtaining and verifying target item data provided by an embodiment of this specification; Figure 5 is a schematic flowchart of a process for processing target item data provided by an embodiment of this specification; Figure 6 is a schematic flowchart of a form verification method provided by an embodiment of this specification; Figure 7 is a schematic flowchart of a form verification method provided by an embodiment of this specification; Figure 8 is a schematic structural diagram of a form verification device provided by an embodiment of this specification; Figure 9 is a schematic structural diagram of an electronic device provided by an embodiment of this specification. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0012] The following will clearly and completely describe the technical solutions in the embodiments of this specification with reference to the accompanying drawings in the embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this specification.

[0013] In the description of this specification, it should be understood that terms such as "first", "second", etc. are only used for descriptive purposes and cannot be construed as indicating or implying relative importance. In the description of this specification, it should be noted that unless otherwise clearly defined and limited, "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products, or devices. For those of ordinary skill in the art, the specific meanings of the above terms in this specification can be understood in specific situations. In addition, in the description of this specification, unless otherwise stated, "a plurality of" means two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0014] The following will specifically describe this specification with reference to specific embodiments.

[0015] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions. For example, the features, information, and data involved in this specification are all obtained under full authorization.

[0016] As Figure 1 shown, Figure 1 is a schematic flowchart of a form verification method provided by an embodiment of this specification. Figure 1 It at least includes a server 1010 that executes the form verification method, and also includes multiple electronic devices for uploading submission requests for the form. The multiple electronic devices at least include electronic device 1021, electronic device 1022, and electronic device 1023. It can be understood that Figure 1The number of servers and electronic devices shown is for illustration only, and the embodiments of this specification do not impose any restrictions on this.

[0017] The above-mentioned server 1010 can be a single server device, such as: a rack-mounted, blade, tower, or cabinet-style server device, or a hardware device with strong computing capabilities such as a workstation or a mainframe computer; it can also be a server cluster composed of multiple servers. The servers in the service cluster can be composed symmetrically, where each server is functionally equivalent and has an equivalent status in the transaction link, and each server can provide services externally independently. Providing services independently can be understood as not requiring the assistance of another server.

[0018] For example, the server is multiple physical servers, and the multiple physical servers are independent in terms of hardware. Or, the server is multiple virtual servers, and the multiple virtual servers are deployed in the same hardware resource pool. The deployment methods of virtual servers include but are not limited to: VMware, Virtual Box, and Virtual PC.

[0019] It can be understood that the server 1010 also has other service capabilities and functions to complete the tasks in the following embodiments. For example, the server 1010 also provides portal services, resource management services, and CI / CD services, etc.

[0020] The types of the electronic device 1021, the electronic device 1022, and the electronic device 1023 include but are not limited to: wearable devices, handheld devices, personal computers, tablet computers, in-vehicle devices, smartphones, computing devices, or other processing devices connected to a wireless modem, etc. In different networks, the electronic device can be called by different names, such as: user equipment, access terminal, user unit, user station, mobile station, mobile terminal, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, cellular phone, cordless phone, personal digital assistant (PDA), electronic device in a 5G network or a future evolved network, etc.

[0021] In the embodiments of this specification, display devices may also be installed on electronic devices such as electronic device 1021, electronic device 1022, and electronic device 1023. The display device may be various devices capable of implementing a display function. For example, the display device may be a cathode ray tube display (CR for short), a light-emitting diode display (LED for short), an electronic ink screen, a liquid crystal display (LCD for short), a plasma display panel (PDP for short), etc. For example, a user may use the display device on electronic device 1021 to send a submission request for a certain form to server 1010, and this form is used to process a certain transaction.

[0022] Communication can be carried out between multiple electronic devices and server 1010 through a communication link established by a communication protocol. For example, the network can be a wireless network or a wired network. The wireless network includes but is not limited to a cellular network, a wireless local area network, an infrared network, or a Bluetooth network. The wired network includes but is not limited to Ethernet, a universal serial bus (USB), or a controller area network. In one or more embodiments of the specification, technologies and / or formats including Hyper Text Mark-up Language (HTML), Extensible Markup Language (XML), etc. are used to represent data (such as a target compressed package) exchanged through the network. In addition, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), and Internet Protocol Security (IPsec) can be used to encrypt all or some of the links. In other embodiments, customized and / or dedicated data communication technologies can also be used to replace or supplement the above data communication technologies.

[0023] In one embodiment, as Figure 2 shown, it is a schematic flowchart of a form verification method provided by the embodiments of this specification. This method can be implemented depending on a computer program and can run on a form verification device based on the von Neumann architecture. This computer program can be integrated in an application or run as an independent tool-class application.

[0024] Specifically, this form verification method includes: S101. Receive a submission request for a form used to process a transaction.

[0025] A form can be understood as an interactive page element for receiving data and submitting it to a server. Multiple form items are set on the form. A form item (Form Items) refers to each independent input item in the form. Each form item corresponds to a specific input control for receiving data of a specific type and specific content. For example, a text field where the user inputs single-line text data such as name, address, etc., and a password field: used to input a password, and the content is masked during input.

[0026] Taking a Web form as an example, a form is an HTML element containing various input fields (such as text fields, radio buttons, checkboxes, dropdown menus, etc.) and a submit button. The user inputs data corresponding to different form items through the form and selects to submit the form. Subsequently, the server will receive the submission request for this form.

[0027] Forms are usually used for transactions such as login, registration, search, orders, etc. For example, if the transaction is consumer finance fund transfer, multiple form items are set on this form to collect relevant data, so as to complete the consumer finance fund transfer for the user.

[0028] S102. In response to the submission request, synchronously receive the form and asynchronously verify at least one target item data among multiple item data.

[0029] Change the work of receiving and verifying the form that was originally carried out synchronously to asynchronously verifying the form, that is, change the way that originally needed to wait for all pre-verifications to be completed before proceeding to the next stage of verification or returning the form when submitting the form, to verifying in an asynchronous manner.

[0030] Asynchronous verification means that when the user sends a submission application, the server will immediately start receiving the form, but will not immediately verify the multiple form items included in the form and generate a verification result. The verification task for the form will be submitted to the message queue or background task in the server background, allowing the user to continue with other operations or receive feedback.

[0031] In this specification, when asynchronously verifying at least one target item data among multiple item data, the target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs. The verification for form items related to the field is domain validation. Domain validation refers to ensuring that the input data meets the requirements of a specific transaction field or logic. It is not just verifying data formats (such as email format, phone number format, etc.), but judging whether the input data meets the constraints of the transaction logic according to the requirements and rules of the actual application.

[0032] For example, this form is used to handle the affairs of consumer finance financial allocation. The multiple form items included in this form may include name, address, mobile phone number, email address, appointment time interval, minimum account balance, payment summary, interest rate agreement, etc., and may also include form items such as asset certificates and guarantor identification documents. Among them, the above form items such as name, address, mobile phone number, email address, appointment time interval, minimum account balance, payment summary, interest rate agreement, etc. are the target form items to be verified in the pre-verification stage, and form items such as asset certificates and guarantor identification documents are the form items to be verified in the domain verification stage, and are not the target form items for this verification.

[0033] As Figure 3 shown, Figure 3 is a schematic flowchart of a form verification method provided by an embodiment of this specification. In response to the submission request 104, the form is synchronously received. At least form item A, form item B, form item C, form item D, form item E, and form item F are set on the form. Form item A corresponds to the item data a input by the user, form item B corresponds to item data b, form item C corresponds to item data c, form item D corresponds to item data d, form item E corresponds to item data e, and form item F corresponds to item data f.

[0034] The target form items irrelevant to the domain are form item A, form item B, form item C, and form item D. Asynchronously verify whether the item data a, item data b, item data c, and item data d corresponding to form item A, form item B, form item C, and form item D are legal and compliant.

[0035] S103. When it is determined that all at least one target item data is verified successfully according to the verification result, determine to store the form in the domain verification database.

[0036] Asynchronously verifying whether each target item data is legal and compliant may include verifying whether the item data conforms to the range corresponding to the form item. For example, the input identity document number must be 18 digits, or the input price cannot be less than 0. It may also be verifying whether the item data conforms to the field dependency relationship of the form item. For example, the "end date" must be later than the "start date". It may also be verifying the item data corresponding to some form items based on a third-party service. For example, verifying whether the item data corresponding to form items such as appointment time interval, minimum account balance, payment summary, and interest rate agreement are legal and compliant.

[0037] As Figure 3As shown, asynchronous verification is performed on the target project data corresponding to the target form items such as form item A and form item B, and the verification result 105 is obtained. After determining that all the above-mentioned multiple target form items have passed the verification according to the verification result 105, the form is stored in the domain verification database 106 so that the server can perform domain verification on the project data corresponding to the form items related to the domain, such as form item E and form item F. In addition, the verification result 105 can be notified to the user in a timely manner. For example, the verification result 105 is sent to the device corresponding to the submission request 104 through real-time notification, page polling, WebSocket, or asynchronous API call, etc.

[0038] In one embodiment, in response to a submission request, after synchronously receiving a form and asynchronously verifying at least one target project data among multiple project data, it further includes: when it is detected during the asynchronous verification process that there is target project data with verification failure, generating verification failure detail information according to the verification failure result, and sending the verification failure details to the device corresponding to the submission request.

[0039] Verification failure can be understood as that the project data corresponding to a certain form item does not meet the regulations or does not meet the conditions set for the form item. The verification failure details represent the target form item with verification failure and its corresponding target form data, and the verification failure details can include one or more target form items with verification failure, and can also include guidance information for guiding the user to fill in the target form item with verification failure, so as to improve the success rate of user filling.

[0040] For example, during the asynchronous verification process, it is detected that form item A and form item B have passed the verification, but there is target project data c corresponding to the target form item C with verification failure. Then, verification failure details are generated to represent that the target project data c corresponding to the target form item C has verification failure, and further, the verification failure details are sent to the device corresponding to the submission request through real-time notification, page polling, WebSocket, or asynchronous API call, etc.

[0041] In this specification, a submission request for submitting a certain form is received. Multiple form items are set on the form for processing a certain transaction, and the project data corresponding to the multiple form items are carried in the submission request. Further, in response to the submission request, the form is synchronously received and at least one target project data among multiple project data is asynchronously verified, and the target form item corresponding to the target project data has nothing to do with the domain to which the transaction belongs. In other words, during the pre-verification process before storing the form in the database, only the legality and compliance of the target project data corresponding to the target form items on the form that have nothing to do with the domain to which the transaction belongs are verified, so as to ensure a clear boundary of responsibilities between the pre-verification before storing the form in the database and the domain verification after storing the form in the database.

[0042] Further, when it is determined that all at least one target item data passes the verification according to the verification result, the form is stored in the domain verification database for subsequent domain verification. In this specification, by asynchronously transforming the pre-verification and synchronously receiving the form, the efficiency of the front-end device submitting the form can be avoided from being affected. At the same time, multiple target item data on the form are asynchronously verified, and based on the verification result, the front-end device is supported to modify the target item data that fails the verification on the form multiple times until the verification is successful, thereby improving the success rate of the form being stored in the database, solving the problem of high time consumption for form submission, and ensuring a good submission experience for the users of the front-end device.

[0043] Based on Figure 2 - Figure 3 the embodiments shown, please also refer to Figure 4 shown. Figure 4 FIG. is a schematic flow chart of obtaining and verifying target item data provided by an embodiment of this specification. S102 includes the following steps: S201. In response to a submission request, synchronously receive the form.

[0044] Based on the submission request for the form, immediately receive the item data corresponding to multiple form items set on the form.

[0045] S202. Asynchronously determine at least one target form item from multiple form items, and obtain and verify the target item data corresponding to the target form item.

[0046] Asynchronously verify at least one target item data among multiple item data. The target form item corresponding to the target item data has nothing to do with the domain to which the transaction belongs. The item data corresponding to the form item related to the domain meets the requirements of a specific transaction domain or logic and is related to the requirements and rules of the actual application.

[0047] For example, the form is used to handle the transaction of consumer finance transfer. The multiple form items included in the form may include name, address, mobile phone number, email address, appointment time interval, minimum account balance, payment summary, interest rate agreement, etc., and may also include form items such as asset certificate and guarantor identification. Among them, the above form items such as name, address, mobile phone number, email address, appointment time interval, minimum account balance, payment summary, interest rate agreement, etc. are the target form items that need to be verified in the pre-verification stage, and the form items such as asset certificate and guarantor identification are the form items that need to be verified in the domain verification stage and are not the target form items for this verification.

[0048] In one embodiment, at least one target form item is determined asynchronously from multiple form items, and the target item data corresponding to the target form item is obtained and verified, including: determining at least one target form item asynchronously from multiple form items according to a preset form item screening rule and the identifiers respectively corresponding to the multiple form items, and obtaining and verifying the target item data corresponding to the target form item.

[0049] Each form item corresponds to a unique identifier, which is used to distinguish different form items in the system. For example, in the background logic of a database or a server, a field name (such as name, phone) or an ID (such as "field_1") can be used as the identifier corresponding to the form item.

[0050] The form item screening rule refers to the criteria or conditions for screening form items, and the purpose is to find target form items that meet specific rules from multiple form items. In this embodiment, the specific rule is that the target form item has nothing to do with the field to which the transaction belongs.

[0051] In this embodiment, at least one target form item is determined asynchronously according to the identifiers respectively corresponding to the multiple form items, and the at least one target form item is used to be verified in the pre-detection of the first stage, which can improve the accuracy and efficiency of determining the target form item.

[0052] Based on Figure 2 - Figure 3 the embodiments shown, please also refer to Figure 5 . Figure 5 FIG. is a schematic flow chart of a process for processing target item data provided by an embodiment of this specification. S102 includes the following steps: S301. In response to a submission request, receive the form synchronously.

[0053] Based on the submission request for the form, immediately receive the item data respectively corresponding to the multiple form items set on the form.

[0054] S302. Asynchronously determine at least one target form item from the multiple form items and classify it into at least one simple form item and complex form item, and verify the target item data respectively corresponding to the simple form item and the complex form item based on a preset processing order.

[0055] In this embodiment, the target form items include simple form items and complex form items, and the time required to process the item data of complex form items is greater than that of simple form items. The simple form items and complex form items can be distinguished according to the expected time required to verify the form items. For example, when the expected time required to verify a certain form item exceeds the preset value, it is determined that the form item is a complex form item, and vice versa. The simple form items and complex form items can be distinguished according to whether the verification of the form item depends on a third-party service. For example, when the verification of a certain form item requires dependence on a third-party service, it is determined that the form item is a complex form item.

[0056] For example, the multiple form items included in the form can include name, address, mobile phone number, email address, appointment time interval, minimum account balance, payment summary, interest rate agreement, etc. Among them, the form items such as name, address, mobile phone number, and email address are simple form items, and the form items such as injection appointment time interval, minimum account balance, payment summary, and interest rate agreement are complex form items.

[0057] In this embodiment, in order to ensure the verification efficiency and improve the real-time feedback of the verification results to the user, for the simple form items and complex form items on the form, the target item data corresponding to the simple form items and complex form items are verified based on the preset processing order.

[0058] In one embodiment, the processing order includes one or more of the following orders: giving priority to verifying simple form items, screening out the first number of simple form items and the second number of complex form items and packing them into a group of verification tasks for verification.

[0059] In this embodiment, simple form items can be verified first, so that when a simple form item with verification failure is detected during the verification process, the verification result can be timely fed back to the user, improving the user's perception of the pre-verification process of the form. For example, based on Figure 3 As shown, form item A and form item C are simple form items, and form item A and form item C are verified first.

[0060] The processing order can also be to screen out the first quantity of simple form items and the second quantity of complex form items and package them into a group of verification tasks for verification. In this embodiment, in the background task, the simple form items and the complex form items are packaged into a group of verification tasks, and then multiple groups of verification tasks are verified in sequence. For example, form item A and form item C are simple form items, and form item B and form item D are complex form items. Package form item A and form item B into a group of verification tasks, and package form item C and form item D into a group of verification tasks. The difference between the times corresponding to each group of verification tasks is less than a preset difference. When a verification task that fails the verification is detected during the verification process, the verification result is promptly fed back to the user.

[0061] In this embodiment, the verification order for verifying multiple form items is optimized. The probability of simple form items going wrong is usually higher. For example, the frequency of problems with required fields or fields with incorrect formats is higher than that of complex fields. By preferentially verifying these simple form items, problems can be discovered early and quickly feedback can be provided. Users can gradually correct the form items with errors in the form. And by packaging verification tasks to process multiple simple form items and complex form items simultaneously, excessive rollbacks and reprocessing can be avoided, the verification process can be optimized, and the verification efficiency can be improved.

[0062] In one embodiment, as Figure 6 shown, it is a schematic flowchart of a form verification method provided by an embodiment of this specification. This method can be implemented depending on a computer program and can run on a form verification device based on the von Neumann architecture. This computer program can be integrated in an application or run as an independent tool class application.

[0063] Specifically, this form verification method includes: S401. Receive a submission request for a form for processing a transaction.

[0064] Refer to the above S101, which will not be elaborated here.

[0065] S402. In response to the submission request, synchronously receive the form and store it in the pre-verification database.

[0066] The pre-verification database is used to store the information required in the verification of the first stage. For example, multiple forms are stored in the pre-verification database, as well as at least one verification failure detail for each form. The verification failure detail represents the target form item that fails the verification and its corresponding target form data. And the verification failure detail can include one or more target form items that fail the verification, and can also include guidance information for guiding the user to fill in the target form item that fails the verification, so as to improve the success rate of the user's filling.

[0067] As Figure 7 shownFigure 7 This is a schematic flowchart of a form verification method provided by an embodiment of this specification. The pre-verification driver 4030 synchronously receives the form 4010 based on the submission request and stores the form 4010 in the pre-verification database 4020.

[0068] S403: Asynchronously load at least one target item data from the pre-verification database and verify it.

[0069] The pre-verification driver 4030 asynchronously loads at least one target item data from the pre-verification database 4020 and verifies it. The at least one target item data may include non-domain item 4041, non-domain item 4042, and non-domain item 4043.

[0070] S404: When it is detected during the asynchronous verification process that there is target item data with verification failure, generate at least one verification failure detail according to the verification failure result, and store the at least one verification failure detail in the pre-verification database.

[0071] Verification failure can be understood as the item data corresponding to a certain form item not being compliant or not meeting the conditions set for the form item. For example, during the asynchronous verification process, if it is detected that the item data corresponding to the form item "Name" is in pinyin, it is determined that there is a target form item with verification failure during the asynchronous verification process, generate a verification failure detail indicating an error in this form item, and store the verification failure detail in the pre-verification database. And further continue to verify other form items in the form. For example, if it is continuously detected that the item data corresponding to the form item "Start Time" is non-numeric data, it is determined that this form item is a form item with verification failure, and continue to generate a verification failure detail and store it in the pre-verification database.

[0072] It can be understood that the verification failure detail may also include multiple target form items with verification failure.

[0073] S405: Poll the pre-verification database to check if there is any verification failure detail? The server polls to detect whether there is any verification failure detail in the pre-verification database. If there is a verification failure detail corresponding to the form in the pre-verification database, it indicates that there is a target form item with verification failure during the asynchronous verification process. In this embodiment, the server polls to detect whether there is any verification failure detail in the verification database through a task queue, and this task queue is different from the task queue used for asynchronous verification.

[0074] S406: When there is a verification failure detail in the pre-verification database, send the verification failure detail to the device corresponding to the submission request.

[0075] In this embodiment, the modified data for the target item data with verification failures in the verification failure details is synchronously received and stored in the pre-verification database; at least one target item data and the modified data are asynchronously loaded from the pre-verification database and verified.

[0076] After the verification failure details are sent to the device corresponding to the submission request, the user can view the verification failure details through this device and understand the target form items with verification failures. The user sends the modified data for the target form items with verification failures through the device. For example, the item data corresponding to the target form item "Name" with verification failure is in pinyin, and the modified data submitted by the user is in Chinese characters.

[0077] The pre-verification driver 4030 synchronously receives the modified data and stores it in the pre-verification database 4020 after storing it in the database. The pre-verification driver 4030 asynchronously detects and loads at least one target item data and at least one modified data from the pre-verification database 4020 to continue the verification, and determines whether at least one target item data and at least one modified data are legal and compliant.

[0078] In this embodiment, by polling to detect whether there are verification failure details in the pre-verification database, and sending the verification failure details to the device corresponding to the submission request, the user is allowed to submit the modified data for the target form items with verification failures multiple times until the item data corresponding to the target form item passes the verification. And by synchronously receiving, asynchronously verifying the form, and polling the pre-verification database, the execution of tasks among the three task queues does not affect each other, improving the user experience of submitting and modifying the form.

[0079] S407. When it is determined that all the at least one target item data pass the verification according to the verification result or when there are no verification failure details in the pre-verification database, it is determined that the form is stored in the domain verification database.

[0080] As Figure 7 shown, after it is determined according to the verification result that all the form items on the form 4010 that are non-domain items pass the verification, the form 4010 is stored in the domain verification database 4050 after being stored in the database. Further, the domain verification driver 4040 loads the form items related to the domain included in each form in the domain verification database 4050 for domain verification.

[0081] In this specification, further, in response to a form submission request, the form is synchronously received and at least one target item data among multiple item data is asynchronously verified. The target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs. In other words, during the pre-verification process before storing the form in the database, only the target item data corresponding to the target form item that has nothing to do with the field to which the transaction belongs on the form is verified for legality and compliance, ensuring a clear boundary of responsibilities between the pre-verification before storing the form in the database and the field verification after storing the form in the database. Further, when it is determined that all of the at least one target item data pass the verification according to the verification result, the form is stored in the field verification database for subsequent field verification. In this specification, by asynchronously transforming the pre-verification, synchronously receiving the form can avoid affecting the efficiency of the front-end device submitting the form. At the same time, multiple target item data on the form are asynchronously verified, and based on the verification result, the front-end device is supported to modify the target item data that fails the verification on the form multiple times until the verification is successful, thereby improving the success rate of storing the form in the database, solving the problem of high time consumption for form submission, and ensuring a good submission experience for the users of the front-end device.

[0082] The following is an apparatus embodiment of this specification, which can be used to execute the method embodiment of this specification. For details not disclosed in the apparatus embodiment of this specification, please refer to the method embodiment of this specification.

[0083] Please refer to Figure 8 , which shows a schematic structural diagram of a form verification apparatus provided by an exemplary embodiment of this specification. The form verification apparatus can be implemented as all or a part of the apparatus through software, hardware, or a combination of both. The apparatus includes a form receiving module 501, an asynchronous verification module 502, and a form storage module 503.

[0084] The form receiving module 501 is configured to receive a submission request for a form for processing a transaction; wherein, the form includes item data corresponding to multiple form items respectively; The asynchronous verification module 502 is configured to, in response to the submission request, synchronously receive the form, and asynchronously verify at least one target item data among the multiple item data; wherein, the target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs; The form storage module 503 is configured to, when it is determined that all of the at least one target item data pass the verification according to the verification result, determine to store the form in the field verification database.

[0085] In one embodiment, the asynchronous verification module 502 includes: The first synchronization unit is configured to, in response to the submission request, synchronously receive the form and store it in the pre-verification database; The first asynchronous unit is used to asynchronously load and verify at least one target item data from the pre-check database; wherein, the multiple item data includes at least one target item data.

[0086] In one embodiment, the asynchronous verification module 502 includes: The second synchronization unit is configured to synchronously receive the form in response to the submission request. The second asynchronous unit is used to asynchronously determine at least one target form item from the multiple form items, obtain and verify the target item data corresponding to the target form item.

[0087] In one embodiment, the second asynchronous unit includes: The asynchronous determination subunit is configured to asynchronously determine at least one target form item from the multiple form items according to the preset form item screening rules and the identifiers respectively corresponding to the multiple form items, obtain and verify the target item data corresponding to the target form item.

[0088] In one embodiment, the target form items include simple form items and complex form items, and the time required to process the item data of the complex form items is longer than that of the simple form items. The asynchronous verification module 502 includes: The third synchronization unit is configured to synchronously receive the form in response to the submission request. The third asynchronous unit is configured to asynchronously determine at least one target form item from the multiple form items and classify them into at least one simple form item and complex form item, and verify the target item data corresponding to the simple form item and the complex form item based on the preset processing order.

[0089] In one embodiment, the processing order includes one or more of the following orders: preferentially verifying simple form items, screening out a first quantity of simple form items and a second quantity of complex form items and packaging them into a group of verification tasks for verification.

[0090] In one embodiment, the form verification device further includes: The first form verification module is configured to generate verification failure detail information according to the verification failure result when it is detected that there is target item data with verification failure during the asynchronous verification process, and send the verification failure details to the device corresponding to the submission request.

[0091] In one embodiment, the form verification device further includes: The second form verification module is used to generate at least one verification failure detail information according to the verification failure result when detecting target item data with verification failure during the asynchronous verification process, and store at least one of the verification failure details in the pre-verification database; The detail polling module is used to poll whether the verification failure details exist in the pre-verification database; The detail sending module is used to send the verification failure details to the device corresponding to the submission request when the verification failure details exist in the pre-verification database.

[0092] In one embodiment, the form verification device further includes: The modification receiving module is used to synchronously receive modification data for the target item data with verification failure in the verification failure details, and store the modification data in the pre-verification database; The modification verification module is used to asynchronously load the at least one target item data and the modification data from the pre-verification database and verify them.

[0093] In this specification, further, in response to a form submission request for submitting a certain form, a form is synchronously received and at least one target item data among multiple item data is asynchronously verified. The target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs. In other words, during the pre-verification process before the form is stored in the database, only the target item data corresponding to the target form item that has nothing to do with the field to which the transaction belongs on the form is verified for legality and compliance to ensure a clear boundary of responsibilities between the pre-verification before the form is stored in the database and the field verification after the form is stored in the database. Further, when it is determined that all at least one target item data pass the verification according to the verification result, the form is stored in the field verification database for subsequent field verification. In this specification, by asynchronously transforming the pre-verification, synchronously receiving the form can avoid affecting the efficiency of the front-end device submitting the form. At the same time, asynchronously verifying multiple target item data on the form and supporting the front-end device to modify the target item data with verification failure on the form multiple times until the verification is successful based on the verification result, thereby improving the success rate of the form being stored in the database, solving the problem of high time consumption for form submission, and ensuring a good submission experience for the users of the front-end device.

[0094] It should be noted that when the form verification device provided in the above embodiment executes the form verification method, only the above division of each functional module is used for illustration. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the form verification device provided in the above embodiment and the form verification method embodiment belong to the same concept, and the implementation process is detailed in the method embodiment, which will not be repeated here.

[0095] The serial numbers of the embodiments in this specification are only for description purposes and do not represent the superiority or inferiority of the embodiments.

[0096] The embodiments of this specification also provide a computer storage medium, which can store multiple instructions. The instructions are suitable for being loaded and executed by a processor to perform the form verification method of the embodiments as described above Figure 1 - Figure 7 shown. For the specific execution process, reference can be made to Figure 1 - Figure 7 the specific description of the embodiments shown, which will not be elaborated here.

[0097] This specification also provides a computer program product, which stores at least one instruction. The at least one instruction is loaded and executed by a processor to perform the form verification method of the embodiments as described above Figure 1 - Figure 7 shown. For the specific execution process, reference can be made to Figure 1 - Figure 7 the specific description of the embodiments shown, which will not be elaborated here.

[0098] Please refer to Figure 9 , which is a schematic structural diagram of an electronic device provided by the embodiments of this specification. As Figure 9 shown, the electronic device 600 may include: at least one processor 601, at least one network interface 604, a user interface 603, a memory 605, and at least one communication bus 602.

[0099] Among them, the communication bus 602 is used to implement connection communication between these components.

[0100] Among them, the user interface 603 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 603 may further include a standard wired interface and a wireless interface.

[0101] Among them, the network interface 604 may optionally include a standard wired interface and a wireless interface (such as a Wi-Fi interface).

[0102] Among them, the processor 601 may include one or more processing cores. The processor 601 connects various parts within the entire server 600 through various interfaces and circuits. By running or executing instructions, programs, code sets, or instruction sets stored in the memory 605, and by calling the data stored in the memory 605, it performs various functions of the server 600 and processes data. Optionally, the processor 601 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 601 may integrate a combination of one or several of a central processing unit (CPU), a graphics processing unit (GPU), and a modem, etc. Among them, the CPU mainly processes the operating system, user interface, application programs, etc.; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 601 and may be implemented separately by a single chip.

[0103] Among them, the memory 605 may include random access memory (RAM) and may also include read-only memory. Optionally, the memory 605 includes a non-transitory computer-readable storage medium. The memory 605 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 605 may include a program storage area and a data storage area. Among them, the program storage area may store instructions for implementing the operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store the data involved in the above-mentioned method embodiments. Optionally, the memory 605 may also be at least one storage device located far from the aforementioned processor 601. As Figure 9 shown, the memory 605, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a form verification application program.

[0104] In Figure 9 ]>In the electronic device 600 shown, the user interface 603 is mainly used to provide an interface for the user to input and obtain the data input by the user; and the processor 601 can be used to call the form verification application program stored in the memory 605 and specifically perform the following operations: Receive a submission request for a form for processing a transaction; wherein, the form includes item data corresponding to a plurality of form items respectively; In response to the submission request, synchronously receive the form, and asynchronously verify at least one target item data among the plurality of item data; wherein, the target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs; When it is determined that all of the at least one target item data pass the verification according to the verification result, determine to store the form in the domain verification database.

[0105] In one embodiment, when the processor 601 executes the operation of in response to the submission request, synchronously receiving the form, and asynchronously verifying at least one target item data among the plurality of item data, it specifically executes: In response to the submission request, synchronously receive the form and store it in the pre-verification database; Asynchronously load at least one target item data from the pre-verification database and verify it; wherein, the plurality of item data includes at least one target item data.

[0106] In one embodiment, when the processor 601 executes the operation of in response to the submission request, synchronously receiving the form, and asynchronously verifying at least one target item data among the plurality of item data, it specifically executes: In response to the submission request, synchronously receive the form; Asynchronously determine at least one target form item from the plurality of form items, and obtain and verify the target item data corresponding to the target form item.

[0107] In one embodiment, when the processor 601 executes the operation of asynchronously determining at least one target form item from the plurality of form items, and obtaining and verifying the target item data corresponding to the target form item, it specifically executes: According to the preset form item screening rule and the identifiers corresponding to the plurality of form items respectively, asynchronously determine at least one target form item from the plurality of form items, and obtain and verify the target item data corresponding to the target form item.

[0108] In one embodiment, the target form item includes a simple form item and a complex form item, and the time required to process the item data of the complex form item is longer than that of processing the item data of the simple form item; The processor 601 executes the steps of synchronously receiving the form in response to the submission request, and asynchronously verifying at least one target item data among the multiple item data, and specifically executes the following steps: Synchronously receive the form in response to the submission request; Asynchronously determine at least one target form item from the multiple form items, distinguish them into at least one simple form item and complex form item, and verify the target item data corresponding to the simple form item and the complex form item respectively based on a preset processing order.

[0109] In one embodiment, the processing order includes one or more of the following orders: preferentially verify the simple form items, screen out a first quantity of simple form items and a second quantity of complex form items, and package them into a group of verification tasks for verification.

[0110] In one embodiment, after the processor 601 executes the steps of synchronously receiving the form in response to the submission request, and asynchronously verifying at least one target item data among the multiple item data, it further executes the following steps: When it is detected that there is target item data with verification failure during the asynchronous verification process, generate verification failure detail information according to the verification failure result, and send the verification failure details to the device corresponding to the submission request.

[0111] In one embodiment, after the processor 601 executes the steps of synchronously receiving the form in response to the submission request, and asynchronously verifying at least one target item data among the multiple item data, it further executes the following steps: When it is detected that there is target item data with verification failure during the asynchronous verification process, generate at least one verification failure detail information according to the verification failure result, and store at least one of the verification failure details in the pre-verification database; Poll whether the verification failure details exist in the pre-verification database; When the verification failure details exist in the pre-verification database, send the verification failure details to the device corresponding to the submission request.

[0112] In one embodiment, after the processor 601 executes the step of sending the verification failure details to the device corresponding to the submission request when the verification failure details exist in the pre-verification database, it further executes the following steps: Synchronously receive modification data for the target item data with verification failure in the verification failure details, and store the modification data in the pre-verification database; Asynchronously load the at least one target item data and the modification data from the pre-verification database and verify them.

[0113] In this specification, further, in response to a form submission request, the form is synchronously received and at least one target item data among multiple item data is asynchronously verified. The target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs. In other words, during the pre-verification process before storing the form in the database, only the target item data corresponding to the target form items that have nothing to do with the field to which the transaction belongs on the form is verified for legality and compliance, ensuring a clear boundary of responsibilities between the pre-verification before storing the form in the database and the field verification after storing the form in the database. Further, when it is determined that all the at least one target item data pass the verification based on the verification result, the form is stored in the field verification database for subsequent field verification. In this specification, by asynchronously transforming the pre-verification, synchronously receiving the form can avoid affecting the efficiency of the front-end device in submitting the form. At the same time, multiple target item data on the form are asynchronously verified, and based on the verification result, the front-end device is supported to modify the target item data that fails the verification on the form multiple times until the verification is successful, thereby improving the success rate of storing the form in the database, solving the problem of high time consumption for form submission, and ensuring a good submission experience for the users of the front-end device.

[0114] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The programs corresponding to the above methods can be stored in a computer-readable storage medium. When the programs are executed, they can include the processes of the embodiments of the above methods. Among them, the storage medium of the electronic device 600 can be a magnetic disk, an optical disc, a read-only memory, or a random access memory, etc.

[0115] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise 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 to be within the scope described in this specification.

[0116] The above-disclosed content is only the preferred embodiments of this specification. Of course, it cannot be used to limit the scope of rights of this specification. Therefore, equivalent changes made according to the claims of this specification still fall within the scope covered by this specification.

Claims

1. A form verification method, characterized in that, The method includes: Receiving a submission request for a form for processing a transaction; wherein, the form includes item data corresponding to a plurality of form items respectively; In response to the submission request, synchronously receiving the form and asynchronously validating at least one target item data among the plurality of item data; wherein, the target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs; When it is determined that all of the at least one target item data pass the validation according to the validation result, determining to store the form in the field validation database.

2. The form verification method according to claim 1, wherein The step of, in response to the submission request, synchronously receiving the form and asynchronously validating at least one target item data among the plurality of item data includes: In response to the submission request, synchronously receiving the form and storing it in the pre-validation database; Asynchronously loading at least one target item data from the pre-validation database and validating it; wherein, the plurality of item data includes at least one target item data.

3. The form verification method according to claim 1, wherein The step of, in response to the submission request, synchronously receiving the form and asynchronously validating at least one target item data among the plurality of item data includes: In response to the submission request, synchronously receiving the form; Asynchronously determining at least one target form item from the plurality of form items, obtaining and validating the target item data corresponding to the target form item.

4. The form verification method according to claim 3, wherein The step of asynchronously determining at least one target form item from the plurality of form items, obtaining and validating the target item data corresponding to the target form item includes: Asynchronously determining at least one target form item from the plurality of form items according to a preset form item screening rule and the identifiers corresponding to the plurality of form items respectively, obtaining and validating the target item data corresponding to the target form item.

5. The form verification method according to claim 1, wherein The target form items include simple form items and complex form items, and the time required to process the item data of the complex form items is longer than the time required to process the item data of the simple form items; The step of, in response to the submission request, synchronously receiving the form and asynchronously validating at least one target item data among the plurality of item data includes: In response to the submission request, synchronously receiving the form; Asynchronously determining at least one target form item from the plurality of form items and classifying them into at least one simple form item and complex form item, and validating the target item data corresponding to the simple form item and the complex form item respectively based on a preset processing order.

6. The form verification method according to claim 5, wherein The processing order includes one or more of the following orders: preferentially validating simple form items, screening out a first quantity of simple form items and a second quantity of complex form items and packaging them into a group of validation tasks for validation.

7. The form verification method according to claim 1, characterized in that, After the step of, in response to the submission request, synchronously receiving the form and asynchronously validating at least one target item data among the plurality of item data, it further includes: When it is detected during the asynchronous validation process that there is target item data that fails the validation, generating validation failure detail information according to the validation failure result, and sending the validation failure details to the device corresponding to the submission request.

8. The form verification method according to claim 2, wherein After synchronously receiving the form and asynchronously verifying at least one target item data among the multiple item data in response to the submission request, the following steps are further included: When it is detected that there is target item data with verification failure during the asynchronous verification process, generate at least one verification failure detail information according to the verification failure result, and store at least one of the verification failure details in the pre-verification database; Poll whether there is the verification failure detail in the pre-verification database; When there is the verification failure detail in the pre-verification database, send the verification failure detail to the device corresponding to the submission request.

9. The form verification method according to claim 8, wherein, After sending the verification failure detail to the device corresponding to the submission request when there is the verification failure detail in the pre-verification database, the following steps are further included: Synchronously receive modification data for the target item data with verification failure in the verification failure detail, and store the modification data in the pre-verification database; Asynchronously load the at least one target item data and the modification data from the pre-verification database and verify them.

10. A form verification device, characterized in that, The device includes: A form receiving module, configured to receive a submission request for a form for processing a transaction; wherein, the form includes item data corresponding to multiple form items respectively; An asynchronous verification module, configured to synchronously receive the form and asynchronously verify at least one target item data among the multiple item data in response to the submission request; wherein, the target form item corresponding to the target item data has nothing to do with the field to which the transaction belongs; A form storage module, configured to determine that the form is stored in the domain verification database when it is determined that all the at least one target item data pass the verification according to the verification result.

11. A computer storage medium, characterized in that, The computer storage medium stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the method steps of any one of claims 1 to 9.

12. A computer program product, characterized in that, The computer program product stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the method steps of any one of claims 1 to 9.

13. An electronic device, characterized in that, It includes: A processor and a memory; wherein, the memory stores a computer program, and the computer program is suitable for being loaded and executed by the processor to perform the method steps of any one of claims 1 to 9.

Images