CN116484813A - Service application data importing method, computing device and storage medium - Google Patents

Abstract

The disclosure relates to service application data importing and provides a data importing method, which comprises the following steps: receiving a template customized for an electronic form column; storing template information of the templates to a common template table; receiving and analyzing the uploaded electronic form filled in data according to the template rule; performing unified data verification on the parsed electronic forms based on the public template table; and uniformly storing the data subjected to uniform data verification. The present disclosure also provides computing devices and non-transitory computer-readable storage media for data importation.

Description

Service application data importing method, computing device and storage medium

Technical Field

The present disclosure relates to service application data importation, and more particularly, to importation of service application data using templates.

Background

In the insurance industry, a great number of service application operations exist in the actual operation process of services such as contract, security, claim settlement, renewal and the like, and the service application involves a large service field difference of service data due to different services and different application parties. In order to be able to cope with such differences, it is necessary to complete a standardized process of differences in business operations, so that the handling of business applications can be completed.

At present, such a technology can be found on the market to process the application of insurance business, but different degrees of custom development work exist. Along with the increase of the data volume and the difference of the service application, the development workload for completing the customization of the personalized template is correspondingly increased, so that the prior art cannot meet the increasing service application, and even the business application handling efficiency is affected to different degrees.

Fig. 1 shows a flow chart of a first service application data importing method 100. According to the method 100 of fig. 1, a developer sorts out required data structures according to different service scenarios, namely, a service scenario one … service scenario n, to define an import template, corresponding import templates one and two … import templates n, and writes corresponding processing logic one and processing logic two … processing logic n according to the corresponding import templates one and two … import templates n respectively, so as to realize verification and storage of data, and later-stage service personnel perform related service operations on the basis that the developer realizes service functions.

For example, to implement two different import templates, the developer uses the first business application data import method shown in fig. 1 as follows:

1. according to the first service scene and the second service scene, the developer sorts out two import templates, namely, an import template I and an import template II, wherein the import template I is used for importing insurance contract information, the template II is used for importing insurance security information, and the template I and the template II are respectively shown in the following table 1:

。

2. because the data types and the data meanings in the first template and the second template cannot be stored by using the same table, a developer needs to create two tables in a database according to the data structures corresponding to the first template and the second template to store the data structures respectively, and the two tables storing the data structures of the first template and the second template are shown in the following table 2 respectively:

。

3. after two table data structures are created and two template data are read, a developer needs to write two sections of processing logic to respectively process data, specifically, data verification is performed for two sections of different template data, and two sections of different data objects are returned. This step is illustrated as method 200 in fig. 2. The method comprises the steps of firstly reading two template data into two table data structures by using an analysis template program, then checking the imported template data by using corresponding check template logic I and check template logic II respectively, and then providing two sections of different return template objects I and II according to checking results.

4. After the analysis and verification are finished, the data are stored in a database corresponding table, and the stored data are shown in the following table 3:

。

the first service application data importing method 100 shown in fig. 1 uses different processing logic of different templates to conduct data importing and finally generates data storage with different data structures. However, the method 100 requires customizing different data structures for different templates, which is inconvenient for later unified queries and unified management. Moreover, developers need to develop different processing logic for different templates, and code reusability is extremely low. In addition, the developer also needs to complete the development of relevant template customization functions, and the service personnel can only import data into the system, so that the time period is long, and the development of specific services cannot be immediately supported.

Fig. 3 shows a flow of a second service application data importing method 300. The method 300 of fig. 3 is identical to the method 100 of fig. 1 except that the processing logic n of the processing logic one and the processing logic two … of the flowchart of fig. 1 are replaced by a common processing logic for data processing, i.e., the developer still needs to sort out the import templates corresponding to the custom data structures according to different business scenarios, and then store the data structures of the import templates into the same data template configuration table, where the stored information includes table names, field names, and field types and field lengths. After the electronic form analysis is completed, the same common processing logic can be used for processing, so that a data structure of a corresponding data template configuration table is obtained, and data is checked and stored. After professional developers process the template data structure customization and import the template configuration table, relevant business import operation can be performed.

Taking two templates to be imported in the second service application data importing method 300 as an example:

1. the first template is used for importing insurance contract information, the second template is used for importing insurance security information, and the templates are shown in the following table 1:

。

2. the insurance contract template (QY 001) and the security (BQ 001) template are respectively customized in the same data template configuration table, and as shown in the following table 4, when the contract template is processed, the data structure of the contract can be queried, the contract data is processed according to the whole data structure of the contract, when the security template is processed, the security data can be queried according to the whole data structure of the security.

3. The parsed data is stored in the database mapping table structure, and the data structure stored in contract QYList and security BQList is the same as the data structure shown in table 3 derived by the first method 100.

The flow chart of the second business application importation method 300 of fig. 3 utilizes different templates for data importation using the same processing logic, storing different data structures. The second service application importing method 300 does not need to develop different processing logic for different templates, and codes can be multiplexed, but still needs to customize different data structures by developers, so that later unified query and unified management are inconvenient. In addition, according to the second service application importing method 300, a developer is still required to complete the development of the relevant template customization function, and the service personnel can import the data into the system, so that the development time period is long, and the development of the specific service cannot be immediately supported.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the disclosed invention and thus may include information that does not form the prior art that is already known to those of ordinary skill in the art.

Disclosure of Invention

In view of the technical defects existing in the background art, it is necessary to provide a general technical scheme for applying for service data import, so as to reduce development workload, reduce development period, and improve data import efficiency, thereby shortening development period of specific services. The technical solution of the present disclosure uses the same import processing logic and the same data structure storage for different import templates. By using the technical scheme of the disclosure, a business person can autonomously define an import template within a specified range, select a corresponding basic data verification rule, and can conduct business data import without intervention of a developer after customization is completed, so that development work is reduced or even eliminated, a development period is shortened, data import efficiency is improved, and a development period of specific business is shortened.

In a first aspect of the disclosure, there is provided a data import method, including: receiving a template customized for an electronic form column; storing template information of the templates to a common template table; receiving and analyzing the uploaded electronic form filled in data according to the template rule; performing unified data verification on the parsed electronic forms based on the public template table; and uniformly storing the data subjected to uniform data verification.

Preferably, the data importing method according to the first aspect, wherein customizing the template for the electronic form column comprises: receiving the input column number and column name matched with the electronic form as the column number and column name of the template; receiving a verification rule selected for each column name; and storing the column number and the column name and the verification rule as template information into a public template table.

Preferably, the data importing method according to the first aspect, wherein uniformly storing the data subjected to uniform data verification includes: uniformly storing the data which does not pass through uniform data verification into a public error data table; and uniformly storing the data passing through uniform data verification into a common column type template intermediate data table.

Preferably, the data importing method according to the first aspect, wherein receiving the template customized for the electronic form column includes: receiving a first template customized for a first electronic form column; and receiving a second template customized for a second electronic form column.

Preferably, the data importing method according to the first aspect, wherein performing unified data check on the parsed electronic form based on the common template table includes: inquiring column check rule codes stored in the public template table according to the template codes in the public template table, and performing unified data check on the parsed electronic form by using a corresponding basic rule check method.

Preferably, the data import method according to the first aspect, wherein before receiving the templates customized for the electronic form, it is queried whether there is a template matching the electronic form in the database.

Preferably, the data import method according to the first aspect, wherein the entered column names are selected from a predefined vocabulary pool or are newly entered column names and/or the verification rules are selected from a set of data verification rules.

In a second aspect of the disclosure, there is provided a computing device comprising: the template configuration unit is used for customizing templates for the electronic form columns; the verification configuration unit is used for customizing corresponding data verification rules for each column name of the customized template; the data analysis unit is used for carrying out data analysis on the electronic form table filled with data according to the template rule; the data unified checking unit is used for carrying out unified data checking on the electronic forms subjected to data analysis; and the unified storage unit is used for uniformly storing the electronic forms subjected to unified data verification.

Preferably, the computing device according to the second aspect performs the data import method according to the first aspect.

In a third aspect of the disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement a data import method according to the first aspect.

According to the technical scheme, the data template and the analysis program are decoupled through the column-type data storage scheme and the configuration data verification, the data verification is flexible and variable, and the business processing logic and the data importing are thoroughly isolated. By adopting the technical scheme disclosed by the invention, the same data structure is used for storing different template data, so that the later inquiry and management are simplified. By adopting the technical scheme of the present disclosure, different templates use the same import processing logic, and codes are completely multiplexed. By adopting the technical scheme, the data can be imported into the system without the need of a developer to complete the development of related customized template functions, the time period is short, and the development of specific services can be rapidly supported.

Drawings

Fig. 1 is a flowchart of a first service application data importing method.

Fig. 2 is a flowchart of data processing in the first service application data importing method.

Fig. 3 is a flowchart of a second service application data importing method.

Fig. 4 is a diagram of an example application scenario of the present disclosure.

Fig. 5 is a diagram of an example computing device of the present disclosure.

FIG. 6 is a flow chart illustrating an example method for service application data importation

Fig. 7 is a diagram of a page of import business application data operations using an example method of the present disclosure.

Fig. 8 is a block diagram of an example computing device of the present disclosure.

Like reference numerals designate similar, but not necessarily identical, elements throughout the figures. Moreover, the accompanying drawings provide examples and/or implementations consistent with the specification; however, the description is not limited to the examples and/or implementations provided in the drawings.

Detailed Description

In order to make the objects, technical solutions and advantages of the present disclosure more apparent, embodiments of the present disclosure will be further described below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present disclosure. Reference in the specification to "an example" or similar language means that a particular feature, structure, or characteristic described in connection with that example is included in the manner described, but may not be included in other examples.

Fig. 4 is a diagram of an example application scenario 400 of the present disclosure. The example application scenario 400 includes a plurality of electronic forms 402 to be imported by business personnel, clients 404 used by business personnel to import the electronic forms 402, servers 406 (e.g., to serve as a security core business system), and a database 408 for storing various data, including electronic form data.

Electronic form 402 may be an Excel-type electronic form for Microsoft, a VisiCalc electronic form for apple type II computers, a Numbers electronic form for Mac OS X, and a Calc electronic form in OpenOffice and LibreOffice that may run on a variety of platforms. Examples of the present disclosure use Excel-type electronic forms as examples only, but examples of the present disclosure are not limited to implementation using Excel electronic forms only.

Client 404 is not limited to a mobile phone, a personal digital assistant, a tablet computer, and any networked computing device that can process data. Business personnel may process data using clients 404 and may log into server 406 using clients 404 to import business application data in electronic form 402.

Example server 406 of the present disclosure may perform the methods, functions, other processes, etc. described herein by a processor or other hardware processing circuitry, etc. described herein. These methods, functions, and other processes may be embodied as machine-readable instructions stored on a computer-readable medium, which may be non-transitory, such as a hardware storage device (e.g., random access memory RAM, read-only memory ROM, erasable programmable ROM-EPROM, electrically erasable programmable ROM-EEPROM, hard disk drive, flash memory, etc.). Server 406 may be a desktop computer, a general-purpose server, or a computer terminal associated with a cloud service (e.g., cloud computing, cloud storage). The server 406 includes a processor that may implement or execute machine-readable instructions that perform some or all of the methods, functions, and other processes described herein. The server 406 also includes memory (not shown) to store the instructions, electronic forms, templates, data structures, and other data locally, either non-volatile or non-volatile. The server 406 may include input output (I/O) devices (not shown), such as a keyboard, mouse, display, etc., so that business personnel may also use the server 406 to operate locally to import business application data in the electronic form 402. The server 406 may include a network interface (not shown) for connecting to a network to communicate over the network with the clients 404, the server 408, the database 408, and the computing cloud or storage cloud. Other known electronic components in server 406 may be added or substituted.

The server 406 may comprise a plurality of servers that may be distributed in a distributed configuration to be distributed across different office locations of an organization to facilitate near access by business personnel using the local clients 404. In addition, the plurality of servers 406 may be redundant with each other and store backup data to prevent data loss.

In the example application scenario 400, one or more business people have multiple electronic forms 402 and need to import business application data in the electronic forms 402 to a server 406, where the data structures of the application business for each of the multiple electronic forms 402 may be different.

Business personnel use clients 404 to log in to a server 406, such as an insurance core business system, over a network and enter a data import page to import business application data in electronic form 402 to server 406 for storage and/or statistics. The business person may also enter the data import page of the server 406 locally at the server 406 to import the business application data in the electronic form 402 to the server 406.

In one example, a business person first queries in server 406 whether there is already an import template matching the structure of electronic form 402. If a matching import template already exists, the matching import template is used to import the data in electronic form 402 to server 406. In one example, the matched import template may be an import template that the business person or other business person has generated and stored when importing data with respect to the electronic form 402 of the same structure. In another example, the matched import template may also be an existing import template imported by server 406 from other servers into database 408.

If there is no import template in the server 406 that matches the structure of the electronic form 402, the business person enters a corresponding template customization page on the display of the server 406, customizing the corresponding import template for the structure of the electronic form 402. The business person enters the number of columns of matching electronic forms in the template customization page, for example, according to the page hint, selects the meaning (i.e., column name) of each column in the table from a vocabulary pool (e.g., predefined common insurance vocabulary) and stores, and then selects the underlying data check rule to be performed on each column for the selected column name column by column. The service person then stores the selected information as template information in a common template table. The business person then fills in the data to be imported in the electronic form 402 according to the rules of the template, or perfects or modifies the filled-in data in the electronic form 402 to conform to the rules selected and customized in the template, and then uploads the filled-in electronic form. If there is another electronic form to be imported without a corresponding import template, the business person then orders the corresponding import template by repeating the above operations and stores the template information thereof as a public template table. The business person then fills out and uploads another electronic form. Server 406 parses the uploaded electronic form or forms and then queries the column check rule codes stored in the public template table according to the template codes. Server 406 then queries the data verification rule table for a specific base rule verification method based on the column verification rule code, and performs a unified data verification on the parsed one or more electronic forms cell by cell using the queried specific base rule verification method. After the unified data check is completed, the server 406 stores the data that fails the check (i.e., the data that failed the check) in the common error data table and records the cause of the error. The server 406 uniformly stores the data checked by the basic rule into the common column type template intermediate data table according to the row number, the column number and the cell content corresponding to the cells, and then invokes specific service processing logic to integrate the data stored in the common column type template intermediate data table into normal service data, and then stores the normal service data into the database 408 for the subsequent service personnel to develop services.

The unified data verification, storage, etc. performed by the server 406 may be performed locally or by cloud computing. After the local or cloud computing completes the unified data processing such as unified data verification, storage, etc., the server 406 may also store the processed data locally, in the database 408, or remotely to the storage cloud in the same data structure manner.

Fig. 5 is a block diagram of an example computing device 500 of the present disclosure. The computing device 500 may implement a business application data importation. The disclosed embodiments are illustrated with example computing device 500 as an example, but are not representative of the disclosure as such. The computing device 500 for service application data importation may be used, for example, for data importation for general insurance applications. In one example, computing device 500 may be a server, workstation, or computer platform, which may be implemented as example server 406 in FIG. 4.

In one example, computing device 500 may include processing units 502-510. As described herein, the processing units 502-508 may be any combination of hardware and programming to implement the functionality of the respective processing units 502-510. In some examples described herein, a combination of hardware and programming may be implemented in a number of different ways to implement the processing units 502-510. For example, the programming of the processing units 502-510 may be processor executable instructions stored on a non-transitory machine readable storage medium, and the hardware for the processing units 502-510 may include processing resources to execute those instructions.

In these examples, a computing device implementing such processing units 502-510 may include a machine-readable storage medium to store instructions and processing resources to execute the instructions, or the machine-readable storage medium may be stored and accessed separately by computing device 500 and processing resources. In some examples, processing units 502-510 may be implemented with circuitry. Furthermore, the processing resources used to implement processing units 502-510 may include one or more central processing units CPUs, one or more graphics processing units GPUs, one or more application specific integrated circuits ASICs, and/or other such types of logic components that may be implemented for data processing.

The computing device 500 includes a template configuration unit 502 for columnar template customization. Column template customization performs template configuration in a column definition (customizing column number, column meaning, and column check) manner in terms of data import template configuration, rather than a conventional configuration manner of a specific template data structure. When business personnel take a plurality of electronic watch data with different structures to conduct importing, the business personnel need to judge how many columns of data are needed by the templates. The business person then logs into a server system, such as an insurance core business system, for determinant template customization. In one example, the template configuration unit 502 receives the number of columns entered by a practitioner for customizing the template, and provides a plurality of column names (e.g., policy numbers, security numbers, names, birthdays, certificate types, certificate numbers, etc.) from a vocabulary pool (e.g., predefined common insurance vocabularies) for selection by the practitioner. In another example, business personnel may also enter multiple column names corresponding to the structure of the electronic form and store a vocabulary pool on the display page. The template configuration unit 502 then receives the business person input and/or the selected multiple column names of the structure of the corresponding electronic form and saves as a template table to enable template customization.

The computing device 500 further includes a verification configuration unit 504 for customizing data verification rules for column name selection of the customized templates. And in a template table of the column template, performing verification coding configuration on columns needing verification, and adopting unified verification logic after configuration. The check configuration unit 504 provides a set of data check rules for the business personnel to select the corresponding check rule for the column name. In one example, verification configuration unit 504 provides a set of data verification rules in a drop down menu for business personnel to select the corresponding verification rule. The business person then selects a corresponding underlying data verification rule for each of the entered and/or selected plurality of column names to be executed thereon. The verification configuration unit 504 further receives basic data verification rules that are respectively selected for execution thereon for the plurality of column names. In one example, the verification configuration unit 504 stores the plurality of column names saved by the template configuration unit 502 and the base data verification rule selected for each column name into a common template table.

The computing device 500 further includes a data parsing unit 506 for data parsing one or more electronic forms that fill in data according to the template rules. After the templates are customized, the business personnel fill in data in the electronic form according to the template rules, or modify the business personnel or perfect the data in the electronic form and upload the electronic form filled in the data. The data parsing unit 506 receives and parses the uploaded one or more electronic forms.

The computing device 500 further includes a data unification verification unit 508 for unifying data verification of the data parsed one or more electronic forms. The data unification verification unit 508 searches for the verification rule customized by the verification configuration unit 504, and then performs unification data verification on the one or more electronic forms analyzed by the data according to the searched customized verification rule.

The computing device 500 further includes a data unification storage unit 510 for unifying data storage of data in one or more electronic forms that have undergone unification data verification. In response to the data unification verification unit 508 performing unified data verification on the data in the one or more electronic forms subjected to data parsing, the data unification storage unit 508 performs unified data storage on the data subjected to unified data verification. The data after the unified data check may include abnormal imported data or successfully imported data. In one example, the data unified storage unit 508 records the erroneous and abnormal imported data into a common error data structure in the database in the same data structure manner, and stores the normal and successful imported data into a common correct data structure in the database in the same data structure manner for use by subsequent service personnel to develop the service. The business personnel can later conduct subsequent business processing according to the correct imported data and the incorrect imported data to consider whether to modify.

Fig. 6 is a flow chart illustrating an example method 600 for service application data importation. In one example, the example method 600 corresponds to an example of its construction as described in detail above for the server 406 for business application data importation or the computing device 500 for business application data importation. The method 600 may be implemented by way of example and not limitation in the server 406 for service application data importation shown in fig. 4, or in the computing device 500 for service application data importation shown in fig. 5. The method 600 may also be implemented in other devices, such as in a remote computing cloud.

The method 600 begins at step 602, where a business person needs to import data in one or more electronic forms (e.g., group risk person name list, etc.) into a database.

The method 600 then proceeds to step 604, where the business person queries, for example, the computing device, whether there is already an import template matching the structure of the electronic form, or in another example, the computing device queries the business person for an import template name to be used, and the computing device then looks up the import template name from the database and returns a result to inform the business person of whether there is an import template matching the electronic form. If there is already a matching import template, the method 600 proceeds to step 612. If there is no matching import template, the method 600 proceeds to step 606. In step 606, the business system automatically displays the template customization page in one example, or in one example, the business person selects to enter the template customization page as prompted.

The method 600 then proceeds to step 608 to customize the header for the custom template column by column. The business personnel inputs the column number of the corresponding electronic form in the template customization page according to the page prompt, selects the column name of each column in the form from a vocabulary pool (such as a predefined common insurance vocabulary) as a table header and stores the column name. In one example, if there is no column name in the vocabulary pool that is structured in the electronic form, the business person itself or the business person is authorized to enter a new column name in the vocabulary pool and save it. In response, the business system receives a plurality of column names of structures of corresponding electronic forms entered and/or selected by business personnel and stores in a common template table.

The method 600 then proceeds to step 610 to customize the underlying data verification rules column by column. In step 610, the business person selects and saves, column by column, the underlying data check rule to be performed on each of the selected plurality of column names in the template customization page. After input and selection via steps 608 and 610 of method 600, a page screen shot of a display of the business system is shown in FIG. 7. Such as the size of the data length, the type and style of date format, the certificate number format, etc. After completing the selection of each column name and the basic data verification rule associated with each column name for the structure of the electronic form in the template customization page, the service personnel stores the selected information into the template information. The business system receives the basic data verification rule selected by the business personnel for each column name and stores the basic data verification rule as template information into the same public template table. At this point, if the business person has an electronic form in addition to the custom template, the business person repeats steps 606-610 to customize and save the new template and save the template information for the new template to the public template table. The business system also stores the updated template table in a database. After one or more templates are customized, relevant template information is stored in the same database template table (LDExcelModel), the storage structure of the database template table is shown in the following table 5, and the table 5 stores template information of a client information import template (QY) and a security application information import template (BQ):

。

the method 600 then proceeds to step 612 to fill in the electronic form data according to the template rules. In step 612, the business person fills in the data to be imported in the electronic form according to the template rules. In other words, the business person needs to check whether the data in the electronic form meets the template rule according to the template rule, and if not, correction is needed. If there is data left unfilled, it is also necessary to supplement the filling. If a plurality of electronic forms exist, the business personnel fill in data in different electronic forms and store the data. The business system receives all of the one or more electronic forms filled in with the imported data.

The method 600 then proceeds to step 614 to upload and parse the electronic form of the fill-in data. In step 614, the business person uploads the data filled electronic form or forms for the computing device to parse the data filled electronic form. The business system of the computing device uploads one or more electronic forms filled with data in response to uploading input of business personnel, and then invokes a parsing program to parse the data of the uploaded one or more electronic forms. After the data parsing is complete, the computing device then performs data processing, without regard to the specifics, data reading, checksum storage using unified data processing logic, processing as described below in steps 616 and 618.

The method 600 then proceeds to step 616 for data verification on a cell-by-cell basis according to the configuration. In step 616, the computing device queries the column check rule codes stored in the common template table for a template code, and queries a data check rule table (ldexcel checkfilled) such as shown in table 6 below for a corresponding specific base rule check method based on the column check rule codes. The computing device uses, for example, a reflection mechanism to invoke a corresponding specific underlying rule verification method in the tool class, unifying verification of the parsed data of the one or more electronic forms on a cell-by-cell basis, the data in each cell. The data storage structure in the data check rule table (ldexcel checkfile) is shown in table 6 below, and each check rule code has a corresponding check method:

。

after all data verification is complete, the method 600 then proceeds to step 618 to store the row number and column number and content for each cell, unifying the stored data. In step 618, the computing device uniformly stores the data that fails the basic rule verification (i.e., the data that fails the verification) into the same common error data table (ldbatch importerrordata) without distinguishing which template the data belongs to, and records the error cause, which can be exported to the business personnel for problem modification according to specific requirements. The memory structure of the common error data table in which the data of the verification failure is stored is as shown in the following table 7, and each error serial number records the error cause:

。

in step 618, the computing device also stores the data that passed the base rule check uniformly into the same common columnar template intermediate data table ((ldbatch importerdata)) without distinguishing which template the data belongs to, according to the row number, column number, and cell content to which the cells correspond, and records the data processing state as 0.

。

And subsequently, processing the imported data according to the specific business scene, and updating the data processing state of the column type template intermediate data table by the computing equipment. All the data needing to be imported define the same data storage structure of the same success or failure data, and the success and failure data are uniformly stored after the data importing processing is finished.

After the data is uniformly stored in the same column template middle data table, the method 600 then proceeds to step 620. In step 620, the computing device invokes specific business processing logic to integrate the data stored in the corresponding column template middle data table into normal business data for use by subsequent business personnel to develop business.

The method 600 then proceeds to step 622. At step 622, the service application data import ends and the method 600 ends.

In a preferred embodiment, the method 600 further includes a verification step after step 620. In the checking step, if the business person finds that there is an error in the business data integrated as normal, the computing device may proceed to step 612 to modify the data input in error in response to the business person's input, and then repeat steps 614-620 until the data import is completed.

In a preferred embodiment, the method 600 further includes a checking step after step 620, and if the service personnel find that there is an error in the service data integrated as normal, manually correct the error and save the error.

Fig. 7 is a screen shot of a page 700 of an import business application data operation using an example method of the present disclosure. Business personnel perform business application data importation operations on, for example, computing devices using the example method 600 of the present disclosure. The business person logs into the server 406 shown in fig. 4 or using the computing device 500 described in fig. 5 or similar computing apparatus capable of implementing the example techniques of this disclosure, and enters the template customization page displayed on the display of these computing apparatus, such as shown by the template customization page 700 of the screen shot. The template customization page 700 supports template customization and, within certain limits, the user to autonomously customize the number of columns, column names, and corresponding verification rules that are imported into the template.

The business person classifies templates to be customized, such as contract templates (QY), in the template type of page 700, then enters a template code, such as 001, in the template code field, which is a new template, and enters a template name, such as "customer information import template", in the template name field. The business person then enters the number of columns used in the template, the column names, such as the policy number, the credential type, the document number, the name, etc., and then selects the corresponding verification rules, such as the 1-policy number verification, the 2-credential type verification, the 3-credential number verification, and the 4-special character verification, for these column names from the verification rule pool. And inputting a column name for the new template by service personnel, selecting a verification rule corresponding to each column name, and storing the customized template. In one example, the business person may also call out the saved customized template to modify the column names and corresponding check rules, may add new column names and select corresponding check rules, or may delete column names that have been selected or entered.

After the business personnel complete the custom of the client information import template. If the business person has a second template to customize, for example, a security application information import template, the business person may reenter the page 700 and select the number of columns, column names, and corresponding verification rules for the security application information import template to customize the security application information import template in a manner similar to that for customizing, for example, the customer information import template. After the customization of the security application information import template is completed, the business personnel stores the customization information of the security application information import template.

After the business person stores the customized client information import template and the security application information import template, the template information of both the customized client information import template and the security application information import template is stored in the same database template table (LDExcelModel) as shown in table 5 above.

The business personnel then fill in data in the corresponding electronic forms according to the customized template rules of the client information import template and the security application information import template respectively. The business person then uploads the electronic form of the filled data for unified data parsing by the computing device. The computing device then performs a unified data check on the parsed data. And after the data is subjected to unified data verification, the computing equipment performs unified data storage on the data subjected to unified data verification. The data after the unified data check may include abnormal imported data or successfully imported data. The computing device records the erroneous exception-import data into the same common error data structure in the database, which is a common error data table as shown in table 7 above. The computing device then stores the normal successful import data into the same correct data structure in the database, which is the same columnar template intermediate data table as shown in table 8 above. The business personnel can later conduct subsequent business processing according to the correct data and the error data to consider whether to modify.

Fig. 8 is a block diagram of an example computing device 800 of the present disclosure. Examples of computing device 800 include a computer platform, a workstation, a smart device, a server, a processing node of a server, a data center comprising a plurality of servers, and/or any other such data processing device.

The above-described methods, processing units of the present application may be implemented on one or more computers or servers or similar devices using computer processors, memory units, storage devices, computer software and other components. A high-level block diagram of such a computer or server is illustrated in fig. 8 as computing device 800. Computing device 800 includes a processor 806, and processor 806 controls the operation of computing device 800 by executing computer program instructions that define overall operation. The computer program instructions may be stored in a storage device 808 (e.g., disk) and loaded into memory 810 when execution of the computer program instructions is desired. In the examples described herein, the processor 806 may include one processor or multiple processors, where the processor 806 may be configured in a single computing device 800 or distributed across multiple computing devices connected locally and/or remotely. For example, the processor 806 may include a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), and/or other such configuration of logic components for data processing.

Accordingly, the steps of the method of fig. 6 may be defined by computer program instructions stored in memory 810 and/or storage device 808 and controlled by processor 806 executing the computer program instructions. Computing device 800 also includes one or more network interfaces 802 for communicating with other devices (e.g., business person clients, databases, storage clouds, or computing clouds) via a network. Computing device 800 also includes other input/output I/O interfaces 804 (e.g., display, keyboard, mouse, speakers, buttons, etc.) that enable a user to interact with computing device 800.

Storage 808 and memory 810 each comprise a tangible, non-transitory computer-readable storage medium. Storage 808 and memory 810 may each comprise high-speed random access memory, such as dynamic random access memory DRAM, static random access memory SRAM, double data rate synchronous dynamic random access memory DDR RAM, or other random access solid state memory devices, and may comprise non-volatile memory, such as one or more magnetic disk storage devices (such as internal hard disks and removable magnetic disks), magneto-optical disk storage devices, flash memory devices, semiconductor memory devices (such as erasable programmable read only memory EPROM, electrically erasable programmable read only memory EEPROM), compact disc read only memory CD-ROM, digital versatile disc read only memory DVD-ROM disc, or other non-volatile solid state memory devices.

The foregoing description has been presented to illustrate and describe examples of the principles described. The description is not intended to be exhaustive or to limit the examples to any precise form disclosed. It is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the present description. Accordingly, alternatives, modifications, and variations made in accordance with the present specification are intended to embrace all such alternatives, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims (10)

1. A data importing method, comprising:

receiving a template customized for an electronic form column;

storing template information of the templates to a common template table;

receiving and analyzing the uploaded electronic form filled in data according to the template rule;

performing unified data verification on the parsed electronic forms based on the public template table; and

and uniformly storing the data subjected to uniform data verification.

2. The method of claim 1, wherein customizing templates for electronic forms comprises:

receiving the input column number and column name matched with the electronic form as the column number and column name of the template;

receiving a verification rule selected for each column name;

and storing the column number and the column name and the verification rule as template information into a public template table.

3. The method of claim 1, wherein uniformly storing the uniformly data verified data comprises:

uniformly storing the data which does not pass through uniform data verification into a public error data table;

and uniformly storing the data passing through uniform data verification into a common column type template intermediate data table.

4. The method of any of claims 1-3, wherein receiving a template customized for an electronic form column comprises:

receiving a first template customized for a first electronic form column; and

a second template customized for a second electronic form column is received.

5. The method of any of claims 1-3, wherein performing unified data verification on the parsed electronic forms based on the common template table comprises:

inquiring column check rule codes stored in the public template table according to the template codes in the public template table, and performing unified data check on the parsed electronic form by using a corresponding basic rule check method.

6. A method according to any of claims 1-3, wherein prior to receiving the templates customized for the electronic form, querying a database for the presence of templates matching the electronic form.

7. The method of claim 2, wherein the entered column name is selected from a predefined vocabulary pool or is a newly entered column name and/or the verification rule is selected from a set of data verification rules.

8. A computing device, comprising:

the template configuration unit is used for customizing templates for the electronic form columns;

the verification configuration unit is used for customizing corresponding data verification rules for each column name of the customized template;

the data analysis unit is used for carrying out data analysis on the electronic form table filled with data according to the template rule;

the data unified checking unit is used for carrying out unified data checking on the electronic forms subjected to data analysis; and

and the unified storage unit is used for uniformly storing the electronic forms subjected to unified data verification.

9. The computing device of claim 8, wherein the computing device performs the method of any of claims 1-7.

10. A non-transitory computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the method of any of claims 1-7.