CN111080459B - Configuration file configuration method and device and readable storage medium - Google Patents
Configuration file configuration method and device and readable storage medium Download PDFInfo
- Publication number
- CN111080459B CN111080459B CN201911151580.3A CN201911151580A CN111080459B CN 111080459 B CN111080459 B CN 111080459B CN 201911151580 A CN201911151580 A CN 201911151580A CN 111080459 B CN111080459 B CN 111080459B
- Authority
- CN
- China
- Prior art keywords
- field
- configuration
- configuration file
- target storage
- storage field
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the invention provides a configuration method and device of a configuration file and a readable storage medium. The method comprises the following steps: receiving each first front-end field and configuration data corresponding to each first front-end field sent by a client, determining a target storage field corresponding to each first front-end field, and configuring configuration files associated with the target storage field according to the configuration data corresponding to each first front-end field, so that configuration files associated with the target storage field corresponding to each first front-end field sent by the client are configured, automatic configuration of the configuration files is realized, the problems that time required for screening and configuring the configuration files by manpower is relatively long, and mismatching exists are solved effectively.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for configuring a configuration file, and a readable storage medium.
Background
Currently, in order to meet the requirement of customers for obviously increasing the requirements of a certain type of dangerous seeds, new products aiming at the requirements of the dangerous seeds are often required to be pushed out in a short time, and more configuration files are required to be configured for developing new products.
At present, a developer who has a relatively understandable technology is required to configure the configuration files, and because the total configuration files are more in number, the developer is required to configure which configuration files, and the screened configuration files are sequentially configured, however, the manual screening and configuration have the problems of low selection omission and configuration efficiency and easy error.
Disclosure of Invention
The embodiment of the invention provides a configuration method, a configuration device and a readable storage medium for configuration files, which are used for solving the problems that the configuration efficiency is low and errors are easy to occur due to the fact that more configuration files are manually configured at present.
In a first aspect of an embodiment of the present invention, a configuration method for a configuration file is provided, including:
receiving each first front-end field sent by a client and configuration data corresponding to each first front-end field; the configuration data are data input by a user in an input area of a front-end page, and each input area corresponds to one first front-end field;
determining a target storage field corresponding to each first front-end field; wherein each first front-end field corresponds to a different target storage field;
And configuring the configuration file associated with the target storage field according to the configuration data corresponding to each first front-end field.
In a second aspect of the embodiment of the present invention, a configuration device for a configuration file is provided, including:
the receiving module is used for receiving each first front-end field sent by the client and the configuration data corresponding to each first front-end field; the configuration data are data input by a user in an input area of a front-end page, and each input area corresponds to one first front-end field;
the determining module is used for determining a target storage field corresponding to each first front-end field; wherein each first front-end field corresponds to a different target storage field;
and the configuration module is used for configuring the configuration file associated with the target storage field according to the configuration data corresponding to each first front-end field.
In a third aspect of the embodiments of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the configuration method of the configuration file described above.
In a fourth aspect of the embodiment of the present invention, an electronic device is provided, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor, where the computer program when executed by the processor implements the configuration method of the configuration file described above.
Aiming at the prior art, the invention has the following advantages:
according to the configuration method of the configuration file, the configuration data of each first front-end field and the configuration data corresponding to each first front-end field sent by the client are received, the target storage field corresponding to each first front-end field is determined, and the configuration of the configuration file associated with the target storage field is carried out according to the configuration data corresponding to each first front-end field, so that the configuration file is configured only by configuring the configuration file associated with the target storage field corresponding to each first front-end field sent by the client, the configuration file is automatically configured, the problems that the time required by screening and configuring the configuration file manually is relatively long and mismatching exists can be effectively solved. And because the configuration data corresponding to the first front-end field is the data input by the user in the input area of the front-end page, and the front-end page provided by the client is more visual, a developer who does not need to know the technology very much is not required to input the data in the front-end page, thereby reducing the service requirement on the personnel inputting the configuration data, reducing the difficulty of inputting the configuration data by the user, and improving the accuracy of inputting the configuration data by the user. And if the user does not input configuration data in the input area of the front-end page, that is, the input area of the front-end page does not input configuration data, the first front-end field corresponding to the input area of the user does not input configuration data does not correspond to the configuration data, configuration files associated with the storage field corresponding to the first front-end field corresponding to the input area of the non-input configuration data are not required to be configured, and automatic configuration file screening is realized, so that development personnel for comparing the technology are not required to screen the configuration files, and configuration is performed on the screened configuration files, and accordingly configuration efficiency and configuration accuracy of the configuration files are improved.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 is a schematic diagram of a configuration file in a risk core system;
FIG. 2 is a flowchart illustrating a method for configuring a configuration file according to an embodiment of the present invention;
FIG. 3 is a schematic interface diagram of a front page according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an interface of another front-end page according to an embodiment of the present invention;
FIG. 5 is a schematic interface diagram of a front page according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of an interface of a front-end page according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of an interface of a front-end page according to an embodiment of the present invention;
fig. 8A is a schematic diagram of a process of converting a first front-end field and configuration data corresponding to the first front-end field into a configuration file through a conversion model according to an embodiment of the present invention;
fig. 8B is a schematic diagram of correspondence between a front-end field and a back-end storage field according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a configuration device for a configuration file according to an embodiment of the present invention.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description.
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to FIG. 1, FIG. 1 is a schematic diagram of a configuration file in an risk core system. As shown in fig. 1, in the prior art, since the commercial operating system developed earlier is different from the microsoft windows operating system Microsoft Windows operating system, the configuration file itself is in the form shown in fig. 1, and the configuration process of the configuration file is complex, that is, the core system architecture is limited by the form of the prior configuration file, so that a developer who has to understand the technology needs to configure the configuration file. For example, the configuration for the premium calculation method shown in fig. 1, the configuration for the refund calculation, the configuration for the loan method, and the like all require professional developers to perform the configuration. And because the total configuration files are more, the configuration files need to be configured, and a developer is also required to screen the configuration files, and the screened configuration files are sequentially configured, because the interface of the configuration files shown in fig. 1 is not simple and visual, the workload is also large, the configuration files need longer time, people are easy to be trapped in the configuration process, and the problem of mismatching in the configuration process is caused. Moreover, manual screening and configuration have the problem of low efficiency of missed screening and configuration.
In order to solve the technical problems, the embodiment of the invention provides a configuration method of a configuration file. Referring to fig. 2, fig. 2 is a flowchart illustrating steps of a configuration method of a configuration file according to an embodiment of the present invention, where the configuration method of the configuration file according to the embodiment is applicable to a case where the configuration file is automatically filtered and configured without manually filtering the configuration file and configuring the filtered configuration file. The method of the embodiment comprises the following steps:
step 201, each first front-end field sent by the client and configuration data corresponding to each first front-end field are received.
The configuration data are data input by a user in input areas of the front-end page, and each input area corresponds to one first front-end field.
The front-end page is, for example, a page shown in fig. 3, fig. 4, fig. 5, fig. 6, and fig. 7, where fig. 3 is an interface schematic diagram of one front-end page provided in an embodiment of the present invention, fig. 4 is an interface schematic diagram of another front-end page provided in an embodiment of the present invention, fig. 5 is an interface schematic diagram of another front-end page provided in an embodiment of the present invention, fig. 6 is an interface schematic diagram of another front-end page provided in an embodiment of the present invention, and fig. 7 is an interface schematic diagram of another front-end page provided in an embodiment of the present invention. The front page 1 shown in fig. 3 is a front page of general product data, and the input area of the front page 1 is, for example, a rectangular frame located behind the dangerous code, and the area in the rectangular frame is the input area, and similarly, each rectangular frame shown in the front page 1 represents one input area.
The front page 2 shown in fig. 4 is a front page of the red-out data, and the input area of the front page 2 is, for example, a rectangular frame located behind the bonus principal calculation method, and the area in the rectangular frame is the input area, and similarly, each rectangular frame shown in the front page 2 represents one input area. The front page 3 shown in fig. 5 is the front page of the omnipotent/join data. The front page 4 shown in fig. 6 is the front page of the gold/annuity data. The front page 5 shown in fig. 7 is a front page of claim data. The input areas of the front page shown in fig. 5, 6 and 7 are similar to those of the front page 1 and the front page 2, and will not be described here again.
After the user configures one front-end page to be configured, the user can click on the input information, so that the client sends configuration data input by the input area of the front-end page (because the input area corresponds to the first front-end field, the configuration data in the input area corresponds to the first front-end field, and the configuration data is the configuration data corresponding to the first front-end field) and the first front-end field to the server. Correspondingly, the server may receive the first front-end field sent by the client and the configuration data corresponding to the first front-end field. Taking the example of configuration data input in the input area of the front page as shown in fig. 3, 4, 5, 6 and 7. After clicking the general product data, the user inputs configuration data in the input area corresponding to each first front-end field shown in fig. 3, as shown in fig. 3. When the configuration of the front page shown in fig. 3 is completed, the red data may be clicked, so that the configuration may be performed on the front page shown in fig. 4. Similarly, the front-end pages shown in fig. 5, 6 and 7 can be configured, and when the user can click to enter information every time the user completes configuring one front-end page, the client can send the configuration data input by the user through the front-end page to the server. Correspondingly, the server receives the first front-end field sent by the client and the configuration data corresponding to the first front-end field.
Step 202, determining a target storage field corresponding to each first front-end field; wherein each first front-end field corresponds to a different target storage field.
Determining the target storage field corresponding to each first front-end field may be accomplished in two ways:
the first mode is as follows: determining a target storage field corresponding to each first front-end field according to the configuration file associated with each second front-end field and the storage field associated with the configuration file; wherein the storage field associated with the configuration file is a field corresponding to the second front-end field.
If all the front-end pages provided by the client are the front-end pages shown in fig. 3, 4, 5, 6 and 7, the second front-end field includes all the first front-end fields corresponding to the input areas in the front-end pages shown in fig. 3, 4, 5, 6 and 7, i.e., the second front-end field includes the first front-end fields corresponding to the input areas of all the front-end pages.
Each second front-end field is associated with a configuration file and the configuration file is associated with a storage field. And taking 15 second front end fields (the first front end fields corresponding to the front end page 1 are the front end field 1, the front end field 2 and the front end field 3, the first front end fields corresponding to the front end page 2 are the front end field 4 and the front end field 5, the first front end fields corresponding to the front end page 3 are the front end field 6, the front end field 7, the front end field 8 and the front end field 9, the first front end fields corresponding to the front end page 4 are the front end field 10, the front end field 11 and the front end field 12, and the first front end fields corresponding to the front end page 5 are the front end field 13, the front end field 14 and the front end field 15, wherein the first front end fields corresponding to each front end page comprise the first front end fields corresponding to each input area of the front end page.
TABLE 1
Wherein, according to the configuration file associated with each second front-end field and the storage field associated with the configuration file, determining the target storage field corresponding to each first front-end field, for example, according to the association relationship among the second front-end field, the configuration file, and the storage field shown in table 1, the first front-end field received in step 201 includes: the first front end field corresponding to the front end page 1, the first front end field corresponding to the front end page 3, and the first front end field corresponding to the front end page 5 are exemplified by 3 first front end fields corresponding to the front end page 1 (for example, including the front end field 1, the front end field 2, and the front end field 3), 4 first front end fields corresponding to the front end page 3 (for example, including the front end field 6, the front end field 7, the front end field 8, and the front end field 9), 3 first front end fields corresponding to the front end page 5 (for example, including the front end field 13, the front end field 14, and the front end field 15), that is, if the configuration data is input only in the input area corresponding to the first front end fields corresponding to the front end page 1, the front end page 3, and the front end page 5, the target storage field corresponding to the front end field 1 is the storage field 1, the target storage field corresponding to the front end field 2 is the storage field 2, and the target storage field 3 corresponding to the front end field 3 is the storage field 3, as shown in the above table 1. Similarly, the target storage field corresponding to the front-end field 6 is the storage field 6, the target storage field corresponding to the front-end field 7 is the storage field 7, the target storage field corresponding to the front-end field 8 is the storage field 8, and the target storage field corresponding to the front-end field 9 is the storage field 9. In order to avoid redundancy, the target storage fields corresponding to the other first front-end fields are not described in detail herein.
The second mode is as follows: and determining a target storage field corresponding to each first front-end field according to the association between each second front-end field and the storage field stored by the server.
It should be noted that, in this implementation manner, the association between each second front-end field and the storage field stored in the server is directly established, so that the target storage field corresponding to each first front-end field can be determined according to the association between each second front-end field and the storage field stored in the server.
Step 203, configuring a configuration file associated with the target storage field according to the configuration data corresponding to each first front-end field.
When in step 202, if the implementation determines the target storage field corresponding to each first front-end field in a manner, this step may be implemented as follows:
and filling configuration data corresponding to each first front-end field into the target storage field corresponding to the first front-end field so as to complete the configuration of the configuration file associated with the target storage field.
The storage field stored in the server is a backend field stored in the backend. According to the configuration files associated with each second front-end field and the storage fields associated with the configuration files, determining a target storage field corresponding to each first front-end field, filling configuration data corresponding to each first front-end field into the target storage field corresponding to the first front-end field to complete configuration of the configuration files associated with the target storage field (namely, through a conversion model stored in the back end, a back-end target field corresponding to each first configuration type can be determined, and filling configuration data corresponding to each first front-end field into a target back-end field corresponding to the first front-end field to complete configuration of the configuration files associated with the target back-end field). For example, referring to fig. 8A, fig. 8A is a schematic process diagram of converting a first front-end field and configuration data corresponding to the first front-end field into a configuration file through a conversion model according to an embodiment of the present invention. Configuration data a (data input by the user through the front-end page, for example, the termination age is 60 years) corresponding to the termination age and the first front-end field (termination age) from the front-end page can be stored into a target back-end field corresponding to the termination age in a configuration file T5687 by a conversion model, and T5687 is, for example, a configuration file name. Configuration data B (data input by the user through the front-end page, for example, the application age is 30 years old) corresponding to the first front-end field (application age) and the application age from the front-end page are stored in a target back-end field corresponding to the application age in the configuration file T5606 through the conversion model, and configuration data C (data input by the user through the front-end page, for example, the application age is ZPM1 shown in fig. 1) corresponding to the first front-end field (premium calculation method) and the premium calculation method from the front-end page are stored in a target back-end field corresponding to the premium calculation method in the configuration file T5606 through the conversion model. Meanwhile, referring to fig. 8B, fig. 8B is a schematic diagram of a correspondence between a front-end field and a back-end storage field according to an embodiment of the present invention. For example, a first front field is shown on the left of the thick horizontal line in fig. 8B, a corresponding field (i.e., a storage field) of the configuration file is shown on the right of the thick horizontal line, each storage field includes a prefix or suffix, and the prefix or suffix may be a configuration file name, so that the configuration file may be associated with the storage field, for example, for the storage field T6640-zcshdimmth, the configuration file T6640 may be associated with the storage field.
Here, the configuration data corresponding to the received first front-end field includes: configuration data 1 corresponding to front end field 1, configuration data 2 corresponding to front end field 2, configuration data 3 corresponding to front end field 3, configuration data 6 corresponding to front end field 6, configuration data 7 corresponding to front end field 7, configuration data 8 corresponding to front end field 8, configuration data 9 corresponding to front end field 9, configuration data 13 corresponding to front end field 13, configuration data 14 corresponding to front end field 14, and configuration data 15 corresponding to front end field 15 are exemplified, configuration data 1 is filled into storage field 1, configuration data 2 is filled into storage field 2, and configuration data 3 is filled into storage field 3, and then configuration of configuration file 1 is completed accordingly, as shown in table 1. Configuration of configuration file 3 and configuration file 5 may be accomplished as well. To avoid redundancy, it is not described here one by one.
For example, the data (for example, ZPM 1) input by the user in the input area after the premium calculation method shown in fig. 3 is filled into the calculation method shown in fig. 1, and the data (for example, FAKE) input by the user in the input area after the refund calculation method shown in fig. 3 is filled into the TK refund field shown in fig. 1.
The configuration files associated with the target storage fields are configured according to the configuration data corresponding to each first front-end field by determining the target storage field corresponding to each first front-end field, and the configuration data corresponding to the first front-end field are data input by a user in an input area of a front-end page, and the front-end page provided by a client is simple and visual, so that a developer does not need to know about the technology to input the data in the front-end page, the service requirement on the personnel inputting the configuration data is reduced, the working difficulty is reduced, and the configuration accuracy can be improved to a certain extent. And if the user does not input configuration data in the input area of the front-end page, that is, the input area of the front-end page does not input configuration data, the first front-end field corresponding to the input area of the user does not input configuration data does not correspond to the configuration data, the configuration data corresponding to the first front-end field corresponding to the input area of the non-input configuration data is not required to be filled into the storage field, and the storage field is the storage field corresponding to the first front-end field corresponding to the input area of the non-input configuration data, so that configuration files associated with the storage field are not required to be configured, automatic configuration file screening is realized, therefore, a developer who is not required to compare the technology is not required to screen the configuration files, and the configuration efficiency and the configuration accuracy of the configuration files are improved. For example, the above example does not need to filter the configuration file 2 and the configuration file 4, so that the configuration file 2 and the configuration file 4 are automatically filtered, that is, only the configuration file associated with the target storage field is configured. In practical application, the number of existing configuration files is huge, for example, hundreds of configuration files, so if the time required for screening and configuring the configuration files by a developer of a relatively understandable technology in the prior art is relatively long, and the problems of miss-matching and mismatch exist. The embodiment of the invention can automatically screen the configuration files, so that a developer who has no need of comparing the technology to screen the configuration files is not needed, and the screened configuration files are configured, thereby improving the configuration efficiency and the accuracy of configuring the configuration files.
It should be noted that, when in step 202, if the target storage field corresponding to each first front-end field is determined in the second implementation, this step may be implemented as follows:
filling configuration data corresponding to each first front-end field into a target storage field corresponding to the first front-end field according to the storage field associated with the second front-end field, wherein each second front-end field is associated with a different storage field;
and configuring the configuration file associated with the target storage field according to the association of the storage field and the configuration file stored by the server.
In the implementation manner provided by the second mode, because the configuration data corresponding to each first front-end field can be directly filled into the target storage field corresponding to the first front-end field according to the storage field associated with the second front-end field, compared with the first mode, the configuration data received from the client can be stored into the target storage field faster because the configuration data is not required to be associated to the target storage field through the configuration file, and after the configuration data is successfully stored into the target storage field, the server can immediately return a prompt message to the client, so that the time for the client to wait for the prompt message is saved. And, since the server target storage field associates which configuration files, configuration of the configuration files can be realized. For example, the target storage field is determined to be storage field 1, storage field 2, storage field 3 and storage field 4, where storage field 1, storage field 2 and storage field 3 are all associated with configuration file 1, then the server may sequentially read configuration data corresponding to each of storage field 1, storage field 2 and storage field 3, and write the read configuration data into positions corresponding to each of storage field 1, storage field 2 and storage field 3 in the configuration file, so as to implement configuration of configuration file 1.
Optionally, before step 201, each first front-end field sent by the client and the configuration data corresponding to each first front-end field are received, the method may further include the following steps:
an association between the second front-end field and the configuration file is established, and an association between the configuration file and the storage field is established, or,
an association of the second front-end field with the storage field is established, and an association of the storage field with the server-stored configuration file is established.
The association between the second front-end fields and the configuration files and the association between the configuration files and the storage fields are established, so that each second front-end field is associated with one configuration file, and one storage field is associated with the configuration file, therefore, the received first front-end field of the client can be corresponding to one storage field, configuration data corresponding to the first front-end field can be filled into the storage field corresponding to the first front-end field, and configuration of the configuration file associated with the storage field is completed, so that manual configuration of the configuration file is not needed.
Or, by establishing the association between the second front-end field and the storage field and the association between the storage field and the configuration file stored by the server, the first front-end field can be quickly associated with the target storage field, so that the configuration data corresponding to the first front-end field can be quickly stored into the target storage field corresponding to the first front-end field.
Optionally, the front page is selected by the user according to the page identifier of the front page. For example, the general product data shown in fig. 3, 4, 5, 6 and 7 is the page identifier of the front page 1, the red data is the page identifier of the front page 2, the universal/throw-in data is the page identifier of the front page 3, the survival/annuity data is the page identifier of the front page 4, and the claim data is the page identifier of the front page 5. The page identifier is used to identify the front-end page, and the page identifier may also identify a front-end page with other identifiers, such as numbers, etc. The page identifications shown in fig. 3, 4, 5, 6 and 7 are identifying the front page by data type, e.g. front page 1 indicates that the data type is general product data.
It should be noted that, the user may determine which front end pages need to be configured according to the page identifier of the front end pages. Taking all front-end pages provided by the client as examples, the front-end pages shown in fig. 3, 4, 5, 6 and 7 are taken as examples. The user inputs data in the input area of only a part of the front-end pages according to the actual product requirements and the page identification of the front-end pages. For example, if the user clicks the general product data according to the page identification (general product data, bonus data, omnipotence/throw data, survival/annuity data, claim data) as shown in fig. 3, the configuration data may be input in the input area corresponding to the first front field corresponding to the front page 1 corresponding to the general product data. The user can determine which pages need to be marked on the input area of the corresponding front page to input configuration data according to the actual demand of the product. For example, product 1 is a service program for heavy risks, product 2 is a service program for red risks, for product 1, the user may not input configuration data through the input area corresponding to the first front end field provided by front end page 2, and for product 2, the user may input configuration data through the input area corresponding to the first front end field provided by front end page 2.
Optionally, the page identifier is determined according to a data type corresponding to the input area of the front page. Since the terms of insurance companies are formed according to responsibility combinations, the data of different responsibility requirements are different, and therefore, the front-end page is customized according to the difference of the data, for example, the difference between general product data, red data, universal/throw-in data, survival gold/annuity data and claim settlement data, so that the data are divided into different data types, and the data of the same data type can be configured through the same front-end page. For example, the data type is used as the page identifier of the front end page, that is, the page identifier may be determined according to the data type corresponding to the input area of the front end page, for example, for the front end page 1 shown in fig. 3, the data type corresponding to the input area of the front end page is all general product data, so that the general product data is used as the page identifier of the front end page 1, and a configurator may determine that the configuration data about the general product data type may be input through the input area provided by the front end page 1 according to the page identifier of the front end page 1. Therefore, a configurator of the configuration data determines which configuration pages need to be configured according to the page identification, and the difficulty of screening which configuration pages to configure by the configurator is reduced through the page identification.
Since in the prior art, a developer who has a relatively understandable technology needs to screen the configuration files, the screened configuration files need to be configured, for example, the configuration files about the red data need to be screened out from a plurality of configuration files to be configured. In this embodiment, the user may select the front end page according to the page identifier of the front end page, so that configuration data is input in the input area of the selected front end page, and since the front end page displayed by the client is intuitive, the user may determine which front end pages input the configuration data through the page identifier, so that a developer who has no need to understand the technology can configure the first front end field.
In practical application, the number of existing configuration files is huge, for example, hundreds of configuration files, so if the time required for screening and configuring the configuration files by a developer of a relatively understandable technology in the prior art is relatively long, and the problems of miss-matching and mismatch exist. In this embodiment, the user may select the front end page according to the page identifier of the front end page, so as to input configuration data in the input area of the selected front end page, and further fill the configuration data corresponding to each first front end field into the target storage field corresponding to the first front end field, so as to complete the configuration of the configuration file associated with the target storage field. Therefore, the configuration method of the configuration file improves configuration efficiency and configuration accuracy of the configuration file.
Optionally, after configuring the configuration file associated with the target storage field according to the configuration data corresponding to each of the first front-end fields in step 203, the method may further include the following steps:
receiving a verification request sent by the client;
responding to the verification request, judging whether the configuration of the configuration file associated with the target storage field is completed or not;
under the condition that the configuration of the configuration file associated with the target storage field is not completed is determined, failure prompt information is sent to the client side so that the client side can display the failure prompt information;
and sending success prompt information to the client for the client to display the success prompt information under the condition that the configuration of the configuration file associated with the target storage field is determined to be completed.
It should be noted that, the failure prompt information may be used to prompt which configuration data corresponding to the first front-end field is not successfully filled into the target storage field corresponding to the first front-end field, and a failure reason (for example, the configuration data does not conform to the format requirement and results in failure), so that the user may be prompted to input the configuration data corresponding to the first front-end field that is not filled successfully. The success prompt information may be used to prompt the user that the configuration of the configuration file associated with the target storage field is successful, and thus, by displaying the success prompt information or the failure prompt information, a user-friendly prompt may be implemented.
Referring to fig. 9, fig. 9 is a schematic structural diagram of a configuration device for a configuration file according to an embodiment of the present invention, where the device 900 includes:
a receiving module 910, configured to receive each first front-end field sent by a client and configuration data corresponding to each first front-end field; the configuration data are data input by a user in an input area of a front-end page, and each input area corresponds to one first front-end field;
a determining module 920, configured to determine a target storage field corresponding to each first front-end field; wherein each first front-end field corresponds to a different target storage field;
and a configuration module 930, configured to configure a configuration file associated with the target storage field according to configuration data corresponding to each of the first front-end fields.
The configuration device of the configuration file provided in this embodiment has the same technical effects as those of the method embodiment shown in fig. 2, and will not be described herein again.
Optionally, the determining module 920 is specifically configured to determine, according to a configuration file associated with each second front-end field and a storage field associated with the configuration file, a target storage field corresponding to each first front-end field; wherein the storage field associated with the configuration file is a field corresponding to the second front-end field.
Correspondingly, the configuration module 930 is specifically configured to fill the configuration data corresponding to each of the first front-end fields into the target storage field corresponding to the first front-end field, so as to complete the configuration of the configuration file associated with the target storage field.
Optionally, the determining module 920 is specifically configured to determine, according to an association between each second front-end field and a storage field stored in the server, a target storage field corresponding to each first front-end field;
correspondingly, the configuration module 930 is specifically configured to fill, according to the storage fields associated with the second front-end fields, configuration data corresponding to each of the first front-end fields into a target storage field corresponding to the first front-end field, where each of the second front-end fields is associated with one of the storage fields that are different from each other;
and configuring the configuration file associated with the target storage field according to the association of the storage field and the configuration file stored by the server.
Optionally, the method may further include:
an establishing module for establishing the association between the second front-end field and the configuration file and the association between the configuration file and the storage field, or,
And establishing an association of the second front-end field and the storage field, and an association of the storage field and the configuration file stored by the server.
Optionally, the front page is selected by the user according to the page identifier of the front page.
Optionally, the page identifier is determined according to a data type corresponding to the input area of the front page.
Optionally, the receiving module is specifically configured to receive, through the BO interface of the service object layer, each first front-end field sent by the client, and configuration data corresponding to each first front-end field.
Optionally, the method may further include:
the verification request receiving module is used for receiving the verification request sent by the client;
the judging module is used for responding to the verification request and judging whether the configuration of the configuration file associated with the target storage field is completed or not;
the prompt module is used for sending failure prompt information to the client for the client to display the failure prompt information under the condition that the configuration of the configuration file which is not completely associated with the target storage field is determined;
and the prompt module is also used for sending success prompt information to the client side so that the client side can display the success prompt information under the condition that the configuration of the configuration file associated with the target storage field is determined to be completed.
In addition, the embodiment of the present invention further provides a configuration device for a configuration file, where the configuration device for a configuration file includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, where the computer program when executed by the processor implements each process of the configuration method embodiment for a configuration file in the foregoing embodiment, and the process can achieve the same technical effect, and for avoiding repetition, a description is omitted herein.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the processes of the configuration method embodiment of the configuration file, and can achieve the same technical effects, so that repetition is avoided, and no further description is provided herein. The computer readable storage medium may be a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or the like.
The embodiment of the invention also provides a computer program which can be stored on a cloud or local storage medium. The computer program is for performing the respective steps of the configuration method of the configuration file of the embodiment of the invention when the computer program is run by a computer or a processor, and for realizing the respective modules in the configuration device of the configuration file according to the embodiment of the invention.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
As will be readily appreciated by those skilled in the art: any combination of the above embodiments is possible, and thus is an embodiment of the present invention, but the present specification is not limited by the text.
The configuration methods of the configuration files provided herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with the teachings herein. The required structure for a system constructed with aspects of the present invention will be apparent from the description above. In addition, the present invention is not directed to any particular programming language. It will be appreciated that the teachings of the present invention described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the claims, any of the claimed embodiments may be used in any combination.
Various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that some or all of the functions of some or all of the components in the configuration method of the configuration file according to an embodiment of the present invention may be implemented in practice using a microprocessor or Digital Signal Processor (DSP). The present invention can also be implemented as an apparatus or device program (e.g., a computer program and a computer program product) for performing a portion or all of the methods described herein. Such a program embodying the present invention may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
Claims (9)
1. A method for configuring a configuration file, which is executed on a server, includes:
receiving each first front-end field sent by a client and configuration data corresponding to each first front-end field; the configuration data are data input by a user in an input area of a front-end page, and each input area corresponds to one first front-end field;
Determining a target storage field corresponding to each first front-end field; wherein each first front-end field corresponds to a different target storage field;
configuring a configuration file associated with the target storage field according to configuration data corresponding to each first front-end field;
the determining a target storage field corresponding to each first front-end field includes:
determining a target storage field corresponding to each first front-end field according to a configuration file associated with each second front-end field and a storage field associated with the configuration file; wherein the storage field associated with the configuration file is a field corresponding to the second front-end field;
the configuring the configuration file associated with the target storage field according to the configuration data corresponding to each first front-end field includes:
and filling configuration data corresponding to each first front-end field into a target storage field corresponding to the first front-end field so as to complete configuration of a configuration file associated with the target storage field.
2. The method of claim 1, wherein said determining a target storage field corresponding to each of said first front-end fields comprises:
Determining a target storage field corresponding to each first front-end field according to the association between each second front-end field and the storage field stored by the server;
the configuring the configuration file associated with the target storage field according to the configuration data corresponding to each first front-end field includes:
filling configuration data corresponding to each first front-end field into a target storage field corresponding to the first front-end field according to the storage field associated with the second front-end field, wherein each second front-end field is associated with one storage field which is different from the other storage field;
and configuring the configuration file associated with the target storage field according to the association of the storage field and the configuration file stored by the server.
3. The method according to claim 1 or 2, further comprising, before each first front-end field sent by the receiving client and the configuration data corresponding to each first front-end field:
establishing an association between the second front-end field and the configuration file, and an association between the configuration file and the storage field, or,
And establishing an association of the second front-end field and the storage field, and an association of the storage field and the configuration file stored by the server.
4. A method according to claim 1 or 2, wherein the front page is selected by the user based on a page identity of the front page.
5. The method of claim 4, wherein the page identification is determined based on a data type corresponding to an input area of the front page.
6. The method according to claim 1 or 2, further comprising, after said configuring the configuration file associated with the target storage field according to the configuration data corresponding to each of the first front-end fields:
receiving a verification request sent by the client;
responding to the verification request, judging whether the configuration of the configuration file associated with the target storage field is completed or not;
under the condition that the configuration of the configuration file associated with the target storage field is not completed is determined, failure prompt information is sent to the client side so that the client side can display the failure prompt information;
and sending success prompt information to the client for the client to display the success prompt information under the condition that the configuration of the configuration file associated with the target storage field is determined to be completed.
7. A configuration device for a configuration file, comprising:
the receiving module is used for receiving each first front-end field sent by the client and the configuration data corresponding to each first front-end field; the configuration data are data input by a user in an input area of a front-end page, and each input area corresponds to one first front-end field;
the determining module is used for determining a target storage field corresponding to each first front-end field; wherein each first front-end field corresponds to a different target storage field;
the configuration module is used for configuring the configuration file associated with the target storage field according to the configuration data corresponding to each first front-end field;
the determining module is used for determining a target storage field corresponding to each first front-end field according to the configuration file associated with each second front-end field and the storage field associated with the configuration file; wherein the storage field associated with the configuration file is a field corresponding to the second front-end field;
the configuration module is used for filling configuration data corresponding to each first front-end field into a target storage field corresponding to the first front-end field so as to complete configuration of a configuration file associated with the target storage field.
8. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements a configuration method of a configuration file according to any of claims 1 to 6.
9. An electronic device comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, which when executed by the processor implements a configuration method of a configuration file according to any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911151580.3A CN111080459B (en) | 2019-11-21 | 2019-11-21 | Configuration file configuration method and device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911151580.3A CN111080459B (en) | 2019-11-21 | 2019-11-21 | Configuration file configuration method and device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111080459A CN111080459A (en) | 2020-04-28 |
| CN111080459B true CN111080459B (en) | 2023-08-25 |
Family
ID=70311714
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911151580.3A Active CN111080459B (en) | 2019-11-21 | 2019-11-21 | Configuration file configuration method and device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111080459B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111652744B (en) * | 2020-05-28 | 2023-09-12 | 泰康保险集团股份有限公司 | Health insurance product configuration method, device, medium and equipment |
| CN113610603B (en) * | 2021-08-09 | 2024-04-16 | 京东科技控股股份有限公司 | Page information processing method and device, electronic equipment and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7685412B1 (en) * | 2003-10-30 | 2010-03-23 | Microsoft Corporation | Configuration settings |
| JP2016014915A (en) * | 2014-06-30 | 2016-01-28 | キヤノン株式会社 | Document generation system, control method thereof, and program |
| WO2017148295A1 (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | Data processing method and device |
| CN107909494A (en) * | 2017-12-08 | 2018-04-13 | 中国平安财产保险股份有限公司 | Collocation method, device, computer equipment and the storage medium of insurance data information |
| CN109388397A (en) * | 2018-09-26 | 2019-02-26 | 中国平安财产保险股份有限公司 | Product page generation method, system, computer equipment and storage medium |
| CN109445762A (en) * | 2018-10-22 | 2019-03-08 | 中国平安人寿保险股份有限公司 | Insurance products are insured page configuration method, apparatus, medium and computer equipment |
| CN109460527A (en) * | 2018-09-25 | 2019-03-12 | 中国平安人寿保险股份有限公司 | Product data configuration method, device, computer equipment and storage medium |
| CN109558404A (en) * | 2018-10-19 | 2019-04-02 | 中国平安人寿保险股份有限公司 | Date storage method, device, computer equipment and storage medium |
| CN109558440A (en) * | 2018-10-18 | 2019-04-02 | 平安科技（深圳）有限公司 | Batch data processing method, device, computer equipment and storage medium |
| CN109739914A (en) * | 2018-12-25 | 2019-05-10 | 斑马网络技术有限公司 | Processing method, device, equipment and the computer readable storage medium of multi-data source |
| CN109815276A (en) * | 2018-12-14 | 2019-05-28 | 中国平安财产保险股份有限公司 | Method, apparatus, computer equipment and the storage medium of declaration form extraction data |
| CN110020381A (en) * | 2018-02-23 | 2019-07-16 | 中国平安财产保险股份有限公司 | Method of calibration, device, equipment and computer storage medium based on configuration file |
| CN110362800A (en) * | 2019-06-19 | 2019-10-22 | 深圳壹账通智能科技有限公司 | Configuration method, device, electronic equipment and the medium of product information |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104216992B (en) * | 2014-09-09 | 2017-12-15 | 百度在线网络技术（北京）有限公司 | A kind of information processing method and device |
-
2019
- 2019-11-21 CN CN201911151580.3A patent/CN111080459B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7685412B1 (en) * | 2003-10-30 | 2010-03-23 | Microsoft Corporation | Configuration settings |
| JP2016014915A (en) * | 2014-06-30 | 2016-01-28 | キヤノン株式会社 | Document generation system, control method thereof, and program |
| WO2017148295A1 (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | Data processing method and device |
| CN107909494A (en) * | 2017-12-08 | 2018-04-13 | 中国平安财产保险股份有限公司 | Collocation method, device, computer equipment and the storage medium of insurance data information |
| CN110020381A (en) * | 2018-02-23 | 2019-07-16 | 中国平安财产保险股份有限公司 | Method of calibration, device, equipment and computer storage medium based on configuration file |
| CN109460527A (en) * | 2018-09-25 | 2019-03-12 | 中国平安人寿保险股份有限公司 | Product data configuration method, device, computer equipment and storage medium |
| CN109388397A (en) * | 2018-09-26 | 2019-02-26 | 中国平安财产保险股份有限公司 | Product page generation method, system, computer equipment and storage medium |
| CN109558440A (en) * | 2018-10-18 | 2019-04-02 | 平安科技（深圳）有限公司 | Batch data processing method, device, computer equipment and storage medium |
| CN109558404A (en) * | 2018-10-19 | 2019-04-02 | 中国平安人寿保险股份有限公司 | Date storage method, device, computer equipment and storage medium |
| CN109445762A (en) * | 2018-10-22 | 2019-03-08 | 中国平安人寿保险股份有限公司 | Insurance products are insured page configuration method, apparatus, medium and computer equipment |
| CN109815276A (en) * | 2018-12-14 | 2019-05-28 | 中国平安财产保险股份有限公司 | Method, apparatus, computer equipment and the storage medium of declaration form extraction data |
| CN109739914A (en) * | 2018-12-25 | 2019-05-10 | 斑马网络技术有限公司 | Processing method, device, equipment and the computer readable storage medium of multi-data source |
| CN110362800A (en) * | 2019-06-19 | 2019-10-22 | 深圳壹账通智能科技有限公司 | Configuration method, device, electronic equipment and the medium of product information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111080459A (en) | 2020-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11361291B2 (en) | Enterprise resource planning (ERP) integrator system and method | |
| CN111240653B (en) | Interface document generation method, device and readable storage medium | |
| US10839455B2 (en) | Systems and methods for managing a loan application | |
| CN111080459B (en) | Configuration file configuration method and device and readable storage medium | |
| AU2003300142A1 (en) | Knowledge-management systems for law firms | |
| US20050131818A1 (en) | Method for performing Due diligence and legal, financial and other types of audits | |
| CN110727580A (en) | Response data generation method, full-flow interface data processing method and related equipment | |
| CN110807499A (en) | Method and system for solving parking of temporary license plate vehicle and applying preferential benefit | |
| CN113344523A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN110347657B (en) | Data generation method, device, electronic equipment and storage medium | |
| EP3651106A1 (en) | Systems and methods for generating a digital identity of equipment on an equipment online marketplace platform | |
| CN111145143A (en) | Problem image determination method and device, electronic equipment and storage medium | |
| CN113741947B (en) | Method and system for solving island problem | |
| US7739678B2 (en) | Managing updates in an object oriented software system | |
| CN111857670B (en) | Application architecture determining method and device | |
| CN106570004B (en) | Data management method and device | |
| CN110942394A (en) | Method and device for determining claim settlement application area, electronic equipment and storage medium | |
| CN109614314B (en) | Performance test method, device, server and readable storage medium | |
| US11762875B2 (en) | Machine assisted data aggregation | |
| KR102616410B1 (en) | Service system and method for automating contract signing for tax agency | |
| CN114416585A (en) | Automatic testing method and device | |
| CN117311776A (en) | Heterogeneous language service gateway routing-based method, heterogeneous language service gateway routing-based system and electronic equipment | |
| JP2022072465A (en) | Deposit processing device, deposit processing method, and deposit processing program | |
| CN112686757A (en) | Method and device for processing security business data, electronic equipment and storage medium | |
| CN116483769A (en) | Multi-U-shield check-in-free testing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |