Product attribute configuration method and system

Abstract

The invention relates to the technical field of scheme configuration, in particular to a product attribute configuration method and system, and the method comprises the steps: determining at least one target product attribute of a to-be-configured product in a JSP page; and obtaining attribute information of each target product attribute, so that a back end performs attribute configuration on the to-be-configured product according to the attribute information of each target product attribute. According to the method, dynamic expansion of product attributes can be realized, and front-end interface parameters and back-end logic do not need to be frequently adjusted, so that the product development period is remarkably shortened. And meanwhile, new functions and attributes can be quickly added according to continuously changing requirements, so that the flexibility of product attribute configuration is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of solution configuration, and in particular to a product attribute configuration method and system. Background Art

[0002] The existing platform design pattern is basically to design the table structure according to the product form. As the product form becomes more and more abundant, product attributes will be frequently added. At this time, the front end needs to adjust the page layout and call interface parameters, and the back end needs to add table fields to store new product attributes and interface logic, which greatly slows down the progress of product development.

[0003] The existing platform design pattern divides the table structure by product attributes, which has limitations. If you want to display product features in a centralized manner, you need to query multiple tables to piece together the data objects required for front-end display. Not only is the back-end interface logic complex, but interface timeouts may also occur. At the same time, the front-end display page is slow and the customer experience is poor.

[0004] Therefore, it is urgent to provide a technical solution to solve the above problems. Summary of the invention

[0005] In order to solve the above technical problems, the present invention provides a product attribute configuration method and system.

[0006] In a first aspect, the present invention provides a product attribute configuration method, which is applied to a front end. The technical solution of the method is as follows:

[0007] In the JSP page, determine at least one target product attribute of the product to be configured;

[0008] The attribute information of each target product attribute is obtained, so that the back end performs attribute configuration on the product to be configured according to the attribute information of each target product attribute.

[0009] The beneficial effects of a product attribute configuration method of the present invention are as follows:

[0010] The method of the present invention can realize the dynamic expansion of product attributes without frequent adjustment of front-end interface parameters and back-end logic, thereby significantly shortening the product development cycle. At the same time, it can also quickly add new functions and attributes according to changing needs, thereby improving the flexibility of product attribute configuration.

[0011] Based on the above solution, a product attribute configuration method of the present invention can also be improved as follows.

[0012] In an optional manner, the attribute information includes at least one of: product risk information, product type information, liability option information, tax preferential identification information, product term information, benefit type information, payment method information, sales channel information, product status information, product cost information, investment direction information and applicable population information.

[0013] In the above optional methods, by including a variety of product attribute information, it is possible to support richer and more diverse product attribute configurations, thereby enhancing the flexibility and scalability of the configuration and meeting the complex needs of different products.

[0014] In an optional manner, the JSP page includes at least one page area corresponding to an attribute type, and each page area includes a plurality of preset product attributes.

[0015] In the above optional method, by dividing the JSP page into multiple page areas, each area corresponds to a different attribute type and contains multiple preset product attributes, a more intuitive and orderly user interface layout can be achieved, which facilitates users to quickly select and configure product attributes and improves the convenience and efficiency of user operations.

[0016] In an optional manner, in the JSP page, the step of determining at least one target product attribute of the product to be configured includes:

[0017] At least one preset product attribute of the product to be configured is selected from at least one page area, and each selected preset product attribute is determined as a target product attribute.

[0018] In the above optional method, by selecting preset product attributes from the page area and determining the selected preset product attributes as target product attributes, the process of product attribute selection is simplified, the workload of manual input and configuration is reduced, and the accuracy and efficiency of the operation are improved.

[0019] In an optional manner, the method further includes:

[0020] The acquired attribute information of each target product attribute is encapsulated to obtain encapsulated data in a structured data format, and the encapsulated data is sent to the back end via an HTTP request.

[0021] In the above optional method, by encapsulating the attribute information and sending it to the backend in a structured data format, the integrity and consistency of data transmission are ensured, while the complexity of backend parsing and processing data is reduced, and the stability of the overall configuration process is improved.

[0022] In a second aspect, the present invention provides a product attribute configuration method, which is applied to a backend. The technical solution of the method is as follows:

[0023] According to the attribute information of each target product attribute of the product to be configured, the attribute of the product to be configured is configured; wherein the front end determines at least one target product attribute of the product to be configured in the JSP page, and obtains the attribute information of each target product attribute.

[0024] The beneficial effects of a product attribute configuration method of the present invention are as follows:

[0025] The method of the present invention can realize the dynamic expansion of product attributes without frequent adjustment of front-end interface parameters and back-end logic, thereby significantly shortening the product development cycle. At the same time, it can also quickly add new functions and attributes according to changing needs, thereby improving the flexibility of product attribute configuration.

[0026] In a third aspect, the present invention provides a product attribute configuration system, the technical solution of which is as follows:

[0027] The product attribute configuration system includes: a front end and a back end;

[0028] The front end is used to: determine at least one target product attribute of the product to be configured in the JSP page, and obtain attribute information of each target product attribute;

[0029] The backend is used to configure the attributes of the product to be configured according to the attribute information of each target product attribute.

[0030] The beneficial effects of a product attribute configuration system of the present invention are as follows:

[0031] The system of the present invention can realize dynamic expansion of product attributes without frequent adjustment of front-end interface parameters and back-end logic, thereby significantly shortening the product development cycle. At the same time, it can also quickly add new functions and attributes according to changing needs, thereby improving the flexibility of product attribute configuration.

[0032] Based on the above solution, a product attribute configuration system of the present invention can also be improved as follows.

[0033] In an optional manner, the attribute information includes at least one of: product risk information, product type information, liability option information, tax preferential identification information, product term information, benefit type information, payment method information, sales channel information, product status information, product cost information, investment direction information and applicable population information.

[0034] In the above optional methods, by including a variety of product attribute information, it is possible to support richer and more diverse product attribute configurations, thereby enhancing the flexibility and scalability of the configuration and meeting the complex needs of different products.

[0035] In an optional manner, the JSP page includes at least one page area corresponding to an attribute type, and each page area includes a plurality of preset product attributes.

[0036] In the above optional method, by dividing the JSP page into multiple page areas, each area corresponds to a different attribute type and contains multiple preset product attributes, a more intuitive and orderly user interface layout can be achieved, which facilitates users to quickly select and configure product attributes and improves the convenience and efficiency of user operations.

[0037] In an optional manner, the front end is specifically used for:

[0038] At least one preset product attribute of the product to be configured is selected from at least one page area, and each selected preset product attribute is determined as a target product attribute.

[0039] In the above optional method, by selecting preset product attributes from the page area and determining the selected preset product attributes as target product attributes, the process of product attribute selection is simplified, the workload of manual input and configuration is reduced, and the accuracy and efficiency of the operation are improved.

[0040] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:

[0042] Figure 1 A schematic diagram of a flow chart of a first embodiment of a method for configuring product attributes of the present invention;

[0043] Figure 2 A schematic diagram of a flow chart of a second embodiment of a method for configuring product attributes of the present invention;

[0044] Figure 3 A flow chart showing the interaction between the front-end and the back-end;

[0045] Figure 4 Flowchart diagram added for product attributes;

[0046] Figure 5 It is a flowchart of the database storage process;

[0047] Figure 6 A schematic diagram of the structure of an embodiment of a product attribute configuration system of the present invention; DETAILED DESCRIPTION

[0048] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.

[0049] Figure 1 FIG. 1 is a flow chart showing a first embodiment of a method for configuring product attributes provided by the present invention, which is executed by a front end. Figure 1 As shown, the following steps are included:

[0050] S110. In the JSP page, determine at least one target product attribute of the product to be configured. In S110:

[0051] 1) JSP pages are dynamic web pages generated using Java Server Pages (JSP) technology. JSP pages can embed Java code into HTML pages to achieve dynamic content generation on the server side. JSP pages can contain static HTML content as well as dynamically generated content, and process business logic and data interaction by embedding Java code. Furthermore, JSP pages are mainly used for front-end display and user interaction. By embedding Java code, JSP pages call back-end services to obtain attribute information of each target product and display it to users. Users can select and configure product attributes on JSP pages. Due to the embedded nature of JSP pages, Java code can be directly embedded in HTML to achieve dynamic content rendering and page logic expansion. Therefore, JSP pages can flexibly handle the display and configuration requirements of target product attributes while simplifying development and maintenance work.

[0052] 2) Products to be configured refer to products that are in the configuration stage on the JSP page. The properties of products to be configured have not yet been configured, and the corresponding target product properties need to be selected and set according to user needs. Products to be configured are the core objects of front-end page operations. At least one target product property of the product to be configured is selected through the JSP page, and the selected target product property is customized according to needs. The existence of products to be configured can support the dynamic configuration of a variety of different products to meet business needs in different scenarios.

[0053] 3) The target product attributes are the attributes selected from the product to be configured and need to be configured. Each product has multiple attributes, and the target product attributes are the specific configuration items selected from the multiple attributes. The target product attributes are the basic unit of product configuration. On the JSP page, the product to be configured is customized by selecting and setting the target product attributes, and subsequent attribute configuration and data processing are performed based on the target product attributes. The selection and determination of the target product attributes can flexibly support the diverse needs of different products, while simplifying the operation process of the front-end page.

[0054] Specifically, the front end determines at least one target product attribute of the product to be configured in the JSP page.

[0055] S120, acquiring attribute information of each target product attribute, so that the back end performs attribute configuration on the product to be configured according to the attribute information of each target product attribute. In S120:

[0056] 1) Attribute information is specific data or metadata related to the attributes of the target product. Attribute information describes the specific characteristics and configuration options of the product. Attribute information is the core data of product configuration. By obtaining and processing attribute information, the front end can send the processed data to the back end, and the back end performs specific configuration and processing on the product based on the data received from the front end. The existence of attribute information can support complex product attribute configuration and provide a high degree of flexibility and scalability.

[0057] Specifically, the front end further obtains attribute information of each target product attribute, so that the back end performs attribute configuration on the product to be configured according to the attribute information of each target product attribute.

[0058] The technical solution of this embodiment can realize the dynamic expansion of product attributes without frequent adjustment of front-end interface parameters and back-end logic, thereby significantly shortening the product development cycle. At the same time, it can also quickly add new functions and attributes according to changing needs, improving the flexibility of product attribute configuration.

[0059] In an optional manner, the JSP page includes at least one page area corresponding to an attribute type, and each page area includes a plurality of preset product attributes.

[0060] In the JSP page, the step of determining at least one target product attribute of the product to be configured includes:

[0061] At least one preset product attribute of the product to be configured is selected from at least one page area, and each selected preset product attribute is determined as a target product attribute.

[0062] It should be noted that the page area is the page structure defined by the form tag, div tag, and td tag. Each page area is organized by at least one of the div tag and the td tag, and the tags are used to group and display different attributes of the product. A form tag contains a group of related preset product attributes, and each div tag or td tag corresponds to a specific area on the page for displaying and selecting preset product attributes. For example, a div tag can contain options related to product liability, and the td tag specifically displays the detailed information of a certain liability option.

[0063] The product to be configured is the product that the user is selecting and configuring, which is specifically reflected in the product being configured through the form and attribute selection operation on the page. The product to be configured refers to the product for which the user is selecting attributes on the page and is preparing to submit the configuration. The user gradually completes the product configuration process by selecting preset product attributes as target product attributes in different page areas (form tags, div tags, td tags) of the page. For example, the user selects preset product attributes such as risk level and liability options of a product on a JSP page as target product attributes. Therefore, the selected target product attributes constitute the specific attributes of the product to be configured.

[0064] The preset product attributes correspond to the attribute options displayed in the page area through the div tag or td tag, as well as the attributes loaded through the back-end database node configuration. The preset product attributes are optional attributes of the product displayed on the page, such as the risk level of the product, whether it is a tax-preferred product, etc. The preset product attributes are displayed to the user through the div tag or td tag, and the user selects from them and determines the selected preset product attributes as the target product attributes. In the back-end database, the preset product attributes correspond to the node configuration in the platform product information table. There is no need to add database fields for each new attribute. The attribute expansion can be achieved by adjusting the page tags and database nodes.

[0065] In this embodiment, according to the design of the JSP page, a platform product information table is designed in the back-end database. The primary key of the platform product information table is composed of three tags: form tag, div tag, td tag, and insurance type number. The three tags are used to organize and display different attributes of the product in the page area, and the insurance type number is used to distinguish different insurance products. Each form tag corresponds to an independent product configuration form, each div tag is used to group related product attributes, and the td tag specifically displays each attribute value.

[0066] When you need to add a description of the attributes of similar products, you only need to add a div tag or a td tag in the JSP page. For example, if you want to add a new responsibility option, add a new div tag in the corresponding position and define the type of the div tag to distinguish other options. Through the above steps to add the description of the attributes of similar products, there is no need to add new data fields in the backend database. You only need to add the corresponding node configuration in the database table to achieve flexible expansion of existing product attributes.

[0067] At the same time, by flexibly adding form tags, div tags, and td tags on the JSP page, the target product attributes can be dynamically added. For example, in the JSP page, a new HTML tag can be inserted at the corresponding position to display the attribute options of the new target product attributes. Using the dynamic characteristics of the JSP page, the newly added different tags can be automatically identified and loaded, so there is no need to change the field structure of the backend database, and only the corresponding node information needs to be configured in the platform product information table.

[0068] The display of dynamic content is achieved by embedding Java code in JSP pages. For example, the <% %> tag is used to embed Java code to process the logical judgment and data assembly of the target product attributes. By embedding Java code in HTML, dynamic pages can be separated from static pages, making the expansion and maintenance of JSP pages easier.

[0069] When adding the target product attributes of the product to be configured (such as whether the product has optional liability, whether it is a tax-preferred product, etc.), code layout is performed in the corresponding page area of ​​the XXXInput.jsp page file according to the attribute type of the target product attribute. For example, for optional liability attributes, a check box can be added to the corresponding div tag, and the default value and status of the check box can be set through Java code. Use the XXX.js file to interact with the back-end database and obtain the product attribute details required for the page through JavaScript. For example, obtain the product risk level enumeration value through AJAX request and dynamically fill in the drop-down selection box, thereby realizing dynamic rendering of the XXXInput.jsp page (ie, JSP page).

[0070] In the JSP page, the user selects at least one preset product attribute of the product to be configured from at least one page area. The page area is composed of div or td tags, and each page area displays one or more preset product attributes. After the user makes a selection, JavaScript will determine each selected preset product attribute as the target product attribute.

[0071] Specifically, the front end further selects at least one preset product attribute of the product to be configured from at least one page area, and determines each selected preset product attribute as a target product attribute.

[0072] In an optional manner, the method further includes:

[0073] The acquired attribute information of each target product attribute is encapsulated to obtain encapsulated data in a structured data format, and the encapsulated data is sent to the backend through an HTTP request.

[0074] It should be noted that before encapsulation, the front end can perform basic verification on the acquired attribute information to ensure the validity and integrity of the data. For example, verify whether the required items have been filled in, whether the values ​​are within the allowable range, whether the format is correct, etc. At the same time, some attribute information can also be processed to a certain extent. For example, format the text entered by the user, or convert the displayed text of the option into the data value required by the back end (for example, convert "high risk" into the corresponding enumeration value or code).

[0075] In this embodiment, in order to facilitate transmission and back-end parsing, the acquired attribute information needs to be encapsulated into a structured data format, and the structured data format is JSON format or XML format. Each attribute information during encapsulation will be organized in the form of a key-value pair, and multiple attribute information are combined into a complete object. In the encapsulation process, the corresponding XXXSave.jsp file is called by using the method in XXX.js for encapsulation. In the XXXSave.jsp file, the embedded characteristics of the JSP page language are used to embed Java code, call the submitData method of the XXXBL.java class, and transmit the entity object (i.e., encapsulated data) with the attribute information attached as a parameter to the back end.

[0076] Depending on the amount of data and the type of operation, the front end can choose to use a GET request or a POST request. For the submission of product attributes, the POST request is selected by default, and the POST request can carry a larger data load. When sending an HTTP request, you need to set the request header to ensure that the back end can correctly parse the sent data. For example, if the JSON format is used, you need to set the request header to Content-Type:application / json. In the process of sending to the back end, the encapsulated structured data (i.e., the encapsulated data) is sent to the back end as the body of the request. The front end can use methods such as JavaScript fetch or XMLHttpRequest to construct and send HTTP requests.

[0077] Figure 2FIG. 2 is a flow chart showing a second embodiment of a method for configuring product attributes provided by the present invention, which is executed by a backend. Figure 2 As shown, the following steps are included:

[0078] S210. Perform attribute configuration on the product to be configured according to the attribute information of each target product attribute of the product to be configured; wherein the front end determines at least one target product attribute of the product to be configured in the JSP page, and obtains the attribute information of each target product attribute.

[0079] In this embodiment, the module that receives and processes HTTP requests in the back end is XXXBL.java. XXXBL.java can first extract the JSON object passed by the front end from the HTTP request. By using a JSON parsing library (such as Jackson or Gson), XXXBL.java can map and parse the JSON object into a corresponding Java entity object, ensuring that each attribute field can be correctly converted into the format required by the back end.

[0080] After parsing is completed, XXXBL.java can immediately perform a series of validation operations on the data in the Java entity object. Validation operations include but are not limited to: data type checking, required field verification, field length verification, and specific verification of business logic (for example, whether the attribute value is within the allowed range). If any data is found to not meet the predefined rules or database storage requirements, the backend will immediately return an error message to the frontend to prompt the user to make corrections.

[0081] After verification, XXXBL.java can repackage the data from the Java entity object into a data object format suitable for persistence layer operations according to the needs of database storage. Repackaging can be achieved by converting the Java entity object into a data access object (DAO), or by mapping the object to the corresponding record in the database table (i.e., the platform product information table) using an ORM framework (such as Hibernate or MyBatis). The above repackaging process ensures that the data object can be seamlessly connected to the structure of the database table, facilitating subsequent storage operations.

[0082] Next, XXXBL.java can call the corresponding persistence layer method, obtain the database connection through the database connection pool, and execute SQL statements or call stored procedures to insert or update the repackaged data into the corresponding tables and fields in the database. At the same time, the transaction management mechanism can also be enabled to ensure the atomicity and consistency of data operations. If any errors occur during the operation, the transaction will be rolled back to prevent data inconsistency.

[0083] Finally, after the repackaged data is successfully saved to the database, XXXBL.java can record the relevant operation logs and return the operation results to the front end. The front end updates the user interface based on the returned results, prompting the user whether the attribute configuration operation is successfully completed, thereby realizing the complete product attribute configuration process.

[0084] Specifically, the backend further performs attribute configuration on the product to be configured according to the attribute information of each target product attribute of the product to be configured.

[0085] Figure 3 The schematic diagram of the process of front-end and back-end interaction is shown. The overall process is as follows: After the program starts, XXXInput.jsp first displays the layout of the static page. Then, XXX.js is used to render dynamic data into the front-end page. When the user operates, XXXSave.jsp is used to connect the front-end and back-end for interactive data transmission. Subsequently, XXXBL.java receives the request and processes the specific business logic. After the processing is completed, the program ends.

[0086] Figure 4 A flowchart of adding product attributes is shown. The overall process is as follows: the process of adding product attributes begins with adding new parameter inputs on the front-end page. Subsequently, the back-end provides a unified saving interface for receiving attribute information data transmitted by the front-end. Finally, the attribute information data will be saved in the OB database to complete the addition of product attributes.

[0087] Figure 5 A flow chart of the database storage process is shown. The overall process is: the database storage process starts with searching the product information configuration table. After determining the database table (i.e., the product information configuration table) through query, new product attributes are added to the database table, thereby ensuring that the product attributes are correctly stored in the database to complete the configuration of the product attributes and make the data persistent.

[0088] Figure 6 FIG. 3 is a schematic diagram showing a structure of an embodiment of a product attribute configuration system 300 provided by the present invention. Figure 6 As shown, the system 300 includes a front end 310 and a back end 320 .

[0089] The front end 310 is used to: determine at least one target product attribute of the product to be configured in the JSP page, and obtain attribute information of each target product attribute;

[0090] The backend 320 is used to perform attribute configuration on the product to be configured according to the attribute information of each target product attribute.

[0091] In an optional manner, the attribute information includes at least one of: product risk information, product type information, liability option information, tax preferential identification information, product term information, income type information, payment method information, sales channel information, product status information, product cost information, investment direction information and applicable population information.

[0092] In an optional manner, the JSP page includes at least one page area corresponding to an attribute type, and each page area includes a plurality of preset product attributes.

[0093] In an optional manner, the front end 310 is specifically used for:

[0094] At least one preset product attribute of the product to be configured is selected from at least one page area, and each selected preset product attribute is determined as a target product attribute.

[0095] The technical solution of this embodiment can realize the dynamic expansion of product attributes without frequent adjustment of front-end interface parameters and back-end logic, thereby significantly shortening the product development cycle. At the same time, it can also quickly add new functions and attributes according to changing needs, improving the flexibility of product attribute configuration.

[0096] The above parameters and steps for each module to implement corresponding functions in the product attribute configuration system 300 of this embodiment can refer to the parameters and steps in the embodiment of the product attribute configuration method above, and will not be repeated here.

[0097] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects and represent the definition of a specific order or sequence. The order of use of similar objects can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than the order shown or described.

[0098] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.

Claims

1. A product attribute configuration method, applied to the front end, characterized in that: include: In the JSP page, determine at least one target product attribute of the product to be configured; The attribute information of each target product attribute is obtained, so that the back end performs attribute configuration on the product to be configured according to the attribute information of each target product attribute.

2. The product attribute configuration method according to claim 1, characterized in that: The attribute information includes: at least one of: product risk information, product type information, liability option information, tax preferential identification information, product term information, income type information, payment method information, sales channel information, product status information, product cost information, investment direction information and applicable population information.

3. The product attribute configuration method according to claim 1, characterized in that: The JSP page includes at least one page area corresponding to an attribute type, and each page area includes a plurality of preset product attributes.

4. The product attribute configuration method according to claim 3, characterized in that: In the JSP page, the step of determining at least one target product attribute of the product to be configured includes: At least one preset product attribute of the product to be configured is selected from at least one page area, and each selected preset product attribute is determined as a target product attribute.

5. The product attribute configuration method according to claim 1, characterized in that: Also includes: The acquired attribute information of each target product attribute is encapsulated to obtain encapsulated data in a structured data format, and the encapsulated data is sent to the back end via an HTTP request.

6. A product attribute configuration method, applied to the back end, characterized in that: include: According to the attribute information of each target product attribute of the product to be configured, the attribute of the product to be configured is configured; wherein the front end determines at least one target product attribute of the product to be configured in the JSP page, and obtains the attribute information of each target product attribute.

7. A product attribute configuration system, characterized in that: include: Front-end and back-end; The front end is used to: determine at least one target product attribute of the product to be configured in the JSP page, and obtain attribute information of each target product attribute; The backend is used to configure the attributes of the product to be configured according to the attribute information of each target product attribute.

8. The product attribute configuration system according to claim 7, characterized in that: The attribute information includes: at least one of: product risk information, product type information, liability option information, tax preferential identification information, product term information, income type information, payment method information, sales channel information, product status information, product cost information, investment direction information and applicable population information.

9. The product attribute configuration system according to claim 7, characterized in that: The JSP page includes at least one page area corresponding to an attribute type, and each page area includes a plurality of preset product attributes.

10. The product attribute configuration system according to claim 9, characterized in that: The front end is specifically used for: At least one preset product attribute of the product to be configured is selected from at least one page area, and each selected preset product attribute is determined as a target product attribute.

Images