Backend-based product page field-level dynamic generation method, device and system

Abstract

The application discloses a product page field level dynamic generation method, device and system based on a backend, relates to the technical field of page configuration, and achieves field level dynamic configuration generation of a product page and flexible adaptation of multi-scene page construction requirements through the following steps: defining the definitions of commodity configuration, field configuration, rule configuration and resource configuration in a background management system, constructing a cache key by multi-dimensional parameter combination for strategy matching, adopting a configuration and resource separated storage architecture and dynamically assembling page configuration data through database association query, and simultaneously performing real-time verification and linkage verification on user input data according to the verification rules of field configuration by using a general component library and a rendering engine to parse configuration and dynamically generate a page.

Description

Technical Field

[0001] This invention relates to the field of page configuration technology, specifically to a method, apparatus, and system for dynamically generating product page fields based on the backend. Background Technology

[0002] In today's digital business environment, the display and interaction of product pages play a crucial role in user experience and business conversion. As businesses continue to expand and diversify, the requirements for product pages are becoming increasingly complex. They not only need to display rich product information, but also need to have flexible and varied form fields, reasonable page layouts, and rich interactive functions to meet the diverse needs of different user groups, different business scenarios, and different channels. At the same time, in order to ensure the accuracy and consistency of data, higher requirements are also placed on the validation of user input data.

[0003] In existing technologies, product pages are mainly customized based on specific business scenarios. Each product and each channel requires front-end developers to write dedicated page code. The provision of page fields, permission restrictions, and validation rules are all implemented through hard coding. This development model has many drawbacks. First, the page is not flexible in responding to requirements. When product information changes, sales channels are adjusted, or user needs change, the code needs to be rewritten and modified, resulting in long development cycles, high costs, and an inability to quickly adapt to market changes. Second, product modifications may affect the overall core files. Due to the hard-coded nature of the code, a change in one place may trigger a chain reaction, causing other related functions to malfunction, increasing system risk and maintenance difficulty. Third, it is not conducive to page layout adjustments. Adjustments to the page layout for different products or channels require redevelopment, making it impossible to achieve unified layout management and flexible configuration, and making it difficult to meet diverse display needs. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of existing technologies and provide a method, apparatus, and system for dynamically generating product page fields based on the backend. It can uniformly define product configuration, field configuration, rule configuration, and resource configuration in the backend management system, construct cache keys using multi-dimensional parameter combinations for strategy matching, adopt a configuration and resource separation storage architecture, and dynamically assemble page configuration data through database association queries. The frontend uses a general component library and rendering engine to parse the configuration and dynamically generate the page. Simultaneously, it performs real-time and linked verification of user input data based on the validation rules of the field configuration, thus realizing the dynamic generation of product page field-level configurations and flexibly adapting to the page construction needs of multiple scenarios.

[0005] To solve the above-mentioned technical problems, the present invention provides the following technical solution: Firstly, a method for dynamically generating product page fields based on a backend, the method comprising the following specific steps:

[0006] S1: Define product configuration, field configuration, rule configuration, and resource configuration uniformly in the backend management system;

[0007] S2: Construct a multi-dimensional parameter combination, generate a unique cache key based on the parameter combination, and query the corresponding configuration in the cache through the cache key;

[0008] S3: Adopts a configuration and resource separation storage architecture. It uses the product code included in the product dimension parameter of the multi-dimensional parameter combination to associate the configuration table and resource table in the database, and assembles the complete page configuration data through association query;

[0009] S4: The front-end uses a general component library and rendering engine to parse page configuration data to dynamically select components and set attributes, generating form fields, page layouts and interactive components;

[0010] S5: Based on the preset validation rules in the field configuration, perform real-time validation and linkage validation on user input data to ensure data legality and consistency.

[0011] Further, in step S1, the product configuration is used to define the basic information of the product, the field configuration is used to define the configuration information of the form fields, the rule configuration is used to define the business rules, and the resource configuration is used to define the resource file; wherein the field configuration includes field type configuration, field attribute configuration, and field rule configuration: the field type configuration supports basic types, composite types, and custom types; the field attribute configuration includes display attributes, validation attributes, interaction attributes, and linkage attributes; the field rule configuration includes basic rules, business rules, and linkage rules.

[0012] Furthermore, in step S2, the parameter combination includes product dimension parameters, permission dimension parameters, channel dimension parameters, and plan dimension parameters. The product dimension parameters include product code and template type; the permission identifier is used to query channel permissions and user permissions; the channel dimension parameters are obtained by querying channel permissions through the permission identifier; and the plan dimension parameters include plan code.

[0013] Furthermore, in step S2, the specific steps for generating a unique cache key based on this parameter combination and prioritizing the query of the corresponding configuration in the cache using this cache key are as follows: The product code, template type, permission identifier, and plan code are concatenated into strings in a preset fixed order, and a unique delimiter is added to avoid confusion between different parameter values, generating a globally unique cache key. The query process prioritizes calling a preset cache middleware, using this cache key to check if the corresponding valid configuration data is stored. If a matching configuration exists in the cache, it is directly read from the cache and returned. If the cache misses or the cached data has expired, a conditional query logic is constructed using MyBatis-Plus's LambdaQueryChainWrapper, with the product code, template type, permission identifier, and plan code as the core query conditions. Related data tables, including the product configuration table and rule configuration table, are queried to extract the corresponding configuration information. After the query is completed, the obtained configuration data is associated with the generated cache key and stored in the cache middleware, and a preset cache validity period is set to complete the update of the cached data.

[0014] Furthermore, in step S3, an architecture design that separates the storage of configuration information and resource files is adopted. The basic information of the product, the configuration of product functions, and the configuration of product rules are classified and stored in the product configuration table and the rule configuration table. The field configuration is standardized and defined through the BaseType class data structure, which clarifies the field name, field type, validation rules, and display attribute elements. The product text resources, image resources, and rich text resource files are centrally stored in the product text table, and a unique association relationship is established through the product code and text type enumeration. After receiving the front-end request, the back-end uses the product code as the core association identifier and synchronously retrieves the product configuration table and the product text table through the database association query mechanism to extract the matching configuration data and corresponding resource files. After integration and binding, complete page configuration data containing the component configuration, attribute parameters, resource references, and rule associations required for page construction is generated.

[0015] Furthermore, in step S3, the specific technical solution for establishing a unique association relationship through product code and text type enumeration is as follows: the product code serves as the globally unique identifier of the product, and together with the preset text type enumeration, constitutes the core association of the product text table. The text type enumeration standardizes and classifies resource types and assigns unique identifier values, including text resources, image resources, and rich text resource categories. A product code field and a text type enumeration field are specifically set in the product text table, and the two are configured as a joint unique index. When a related query is required, all resource records of the corresponding product are locked through the product code of the target product, and then the required type of resources under the product are filtered out by combining the specific text type enumeration value, so as to achieve precise binding between product configuration and corresponding resource files. At the same time, it supports the reuse of the same resource across products through association with different product codes, and the association of the same product with multiple types of resources through different text type enumeration values.

[0016] Furthermore, in step S4, an architecture is adopted in which a front-end general component library and a rendering engine work together. The front-end pre-deploys a standard component library covering basic, composite, and custom types. The components in the component library are universal and not bound to specific business logic. Only attribute configuration interfaces are reserved. The rendering engine receives complete page configuration data transmitted from the back-end through a preset interface. After parsing the component selection instructions, attribute parameters, and layout rule information contained in the complete page configuration data, it selects the appropriate component from the component library according to the component identifier in the page configuration data. Then, it assigns the corresponding display, interaction, and linkage attributes to the component through an attribute passing mechanism. At the same time, it arranges the selected components in an orderly manner according to the layout rules defined in the configuration, and completes the integration and presentation of form fields, page layout, and interactive components to form a complete insurance product application page that meets the configuration requirements.

[0017] Furthermore, in step S5, real-time verification is triggered by a component state change event. When user input data or component state changes, a preset verification method is automatically invoked to perform real-time verification of the input data according to the verification rules of the corresponding form fields and provide feedback on the results. Linked verification is initiated when the form field values ​​change. A preset trigger method is used to invoke the form reorganization mechanism to reorganize the form structure and extract the associated linked fields. After collecting all relevant verification rules, unified verification is performed.

[0018] Secondly, a backend-based product page field-level dynamic generation device, the device comprising:

[0019] Configuration definition module: Configured to define product configuration, field configuration, rule configuration, and resource configuration in the backend management system;

[0020] The strategy matching module is configured to query and match the corresponding configuration based on the product code, template type, permission identifier, and plan code through parameter combinations.

[0021] Dynamic assembly module: Configured to assemble matched configurations and resources through database join queries to generate complete page configuration data;

[0022] Dynamic rendering module: Configured so that the front end can use a general component library and rendering engine to parse the configuration based on the page configuration data, dynamically select components and set their properties, and generate form fields, page layouts and interactive components;

[0023] Validation module: Configured to perform real-time and linked validation on user input based on the validation rules configured in the fields.

[0024] Thirdly, a backend-based product page field-level dynamic generation system, which includes...

[0025] Terminal equipment: used to receive user operations and display dynamically generated insurance application pages;

[0026] Server: Deploys dynamic generation devices and executes configuration definition, strategy matching, dynamic assembly, rendering control, and verification logic;

[0027] Database: Used to separately store configuration information and resource files, supporting join queries and data reuse.

[0028] Compared with existing technologies, this backend-based method, device, and system for dynamically generating product page fields have the following advantages:

[0029] This invention unifies the configuration definition of products, fields, rules, and resources through a backend management system, enabling centralized management and flexible adjustment of configurations. This effectively improves the response speed of page requirements. The strategy matching step uses multi-dimensional parameter combinations to construct cache keys, prioritizing cache queries to improve query efficiency and accurately match configuration information. The dynamic assembly step adopts a configuration and resource separation storage architecture, assembling complete page configuration data through database association queries, achieving accurate matching and efficient reuse of configurations and resources. The dynamic rendering step deploys a general component library and rendering engine on the front end, dynamically generating pages based on configurations without requiring customized development for each product and channel, reducing development workload and improving the flexibility of page layout adjustments. The verification step performs real-time and linked verification of user input data to ensure data consistency and legality, improving data quality. This achieves field-level dynamic configuration generation for product pages, adapting to multi-scenario page construction needs, improving development efficiency, and reducing maintenance costs.

[0030] Other advantages, objectives and features of the invention will be set forth in part in the description which follows, and in part will be apparent to those skilled in the art from the following examination or study, or may be learned from the practice of the invention. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0032] Figure 1 To dynamically generate the system's structural diagram at the field level of the product page based on the backend;

[0033] Figure 2 A flowchart illustrating the method for dynamically generating product page fields based on the backend;

[0034] Figure 3 This is a structural diagram of a backend-based product page field-level dynamic generation device. Detailed Implementation

[0035] To further illustrate the technical means and effects of the present invention in achieving its intended purpose, the following detailed description of the specific implementation methods, structures, features, and effects of the present invention, in conjunction with the accompanying drawings and preferred embodiments, is provided below.

[0036] This invention provides a method, apparatus, and system for dynamically generating product page fields at the backend level. By uniformly defining product configuration, field configuration, rule configuration, and resource configuration in the backend management system, and constructing cache keys for strategy matching using multi-dimensional parameter combinations, a configuration and resource separation storage architecture is adopted, and page configuration data is dynamically assembled through database association queries. The frontend uses a general component library and rendering engine to parse the configuration and dynamically generate the page. At the same time, user input data is validated in real time and linked to validation according to the validation rules of the field configuration. This realizes the field-level dynamic configuration generation of product pages, which can flexibly adapt to the page construction needs of multiple scenarios.

[0037] like Figure 1As shown, the system of this invention includes a terminal device, a server, and a database. The terminal device can be a common smart terminal, on which a client application with insurance application functionality is installed. This application pre-integrates an interface for communication with the server and the runtime environment required for front-end rendering, supporting user input, page display, and data feedback. The server adopts a cluster deployment mode, deploying a backend management system, a dynamic generation device, and related service components. The backend management system provides a visual operation interface for administrators to define various configurations. The functional modules of the dynamic generation device are integrated into the server as service plug-ins, and data interaction between modules is achieved through internal interfaces. The server and the terminal device communicate via a network. A stable network connection is established to support real-time data transmission. The database is initialized according to the principle of separating configuration and resource storage, creating core data tables such as the product configuration table, rule configuration table, and product text table. The product configuration table stores basic product information and function configurations, the rule configuration table stores various verification rules and business rules, and the product text table specifically stores resource files such as text, images, and rich text required for the page. At the same time, a product code field and a text type enumeration field are set in the product text table, and both are configured as a joint unique index to ensure the uniqueness and relevance of data storage. The database also needs to pre-configure the indexes required for related queries to improve data retrieval efficiency.

[0038] like Figure 2 As shown, the configuration definition steps are completed through the visual interface of the backend management system. After logging into the backend management system, the administrator enters the configuration management module and performs the definition work of product configuration, field configuration, rule configuration and resource configuration in sequence.

[0039] When defining product configurations, managers input basic product information based on the product's actual attributes, clarifying core content such as applicable scenarios and sales channel scope. This provides a foundation for subsequent configuration matching. Field configuration definitions need to be expanded in three dimensions: field type configuration, field attribute configuration, and field rule configuration. In field type configuration, managers can choose the appropriate type from the system's preset basic types, composite types, and custom types. Basic types cover common input and selection fields, composite types are composed of multiple basic types, and custom types support the creation of exclusive field forms according to specific business needs. In field attribute configuration, display attributes are set for each field, such as the field's display name, position, and visibility on the page. Validation attributes clarify whether the field needs data validation. Interaction attributes define the field's operation method, such as whether it is editable and whether it supports multi-selection. Linkage attributes indicate the relationship between the field and other fields. In field rule configuration, basic rules are used to define general validation standards such as data format and input length. Business rules are set in conjunction with the product's business requirements, such as the insured age range and coverage limits. Linkage rules clarify the status or data of other fields that need to be adjusted synchronously when the value of this field changes.

[0040] The definition of the rule configuration must correspond one-to-one with the field configuration. For each defined field, the administrator selects or creates the corresponding validation rule and binds the rule to the field to ensure that all fields displayed on the page can trigger the corresponding validation logic. The content of the rule must clearly define the validation conditions and the feedback information when the conditions are not met. The definition of the resource configuration is to upload the various resource files required by the page to the backend management system. The system automatically stores the resource files in the product text table of the database and automatically matches the corresponding text type enumeration value according to the resource type, while associating the corresponding product code to complete the binding of resources and products.

[0041] When a user initiates an insurance application through the client application on their terminal device, the client application first extracts the core information related to the user's operation, including the identifier of the currently selected product, the type of page template required by the user, the permission information of the user account, and the identifier of the selected plan. This information together constitutes the basis for strategy matching.

[0042] The client application encapsulates the above query criteria and sends it to the server. Upon receiving the request, the server's strategy matching module organizes the query criteria, constructing a multi-dimensional parameter combination including product, permission, and channel dimensions. Subsequently, the strategy matching module generates a unique cache key based on this parameter combination and queries the server's local cache using this cache key. The cache pre-stores frequently queried configuration information. If the configuration information corresponding to the cache key exists in the cache, it is directly retrieved from the cache and quickly fed back to subsequent modules. If no matching configuration information is found in the cache, the strategy matching module sends a query request to the database. The database, based on the criteria in the parameter combination, jointly queries relevant data tables such as the product configuration table and rule configuration table to filter out configuration information that completely matches the parameter combination. After the query is completed, the configuration information is returned to the server. At the same time, the strategy matching module stores the configuration information and the corresponding cache key in its local cache for quick retrieval in subsequent similar requests.

[0043] During the configuration matching process, channel-level information is obtained through association queries with permission-level information. That is, based on the user's permission identifier, the channel configuration corresponding to that permission is queried from the database to ensure that the matched configuration information is compatible with the user's channel and to meet the requirement of displaying different page configurations for different channels.

[0044] After receiving the matching configuration information transmitted by the strategy matching module, the dynamic assembly module initiates the integration process of configuration and resources. First, the dynamic assembly module sends a correlation query request to the database with the product code as the core association identifier. It extracts the product configuration, field configuration, rule configuration and other information corresponding to the product code from the product configuration table, and extracts all resource files associated with the product code from the product text table. The extraction of resource files is achieved through joint filtering of product code and text type enumeration to ensure that all kinds of text, image and rich text resources required by the product are obtained.

[0045] Subsequently, the dynamic assembly module integrates the extracted configuration information and resource files: binding field configurations with corresponding rule configurations to clarify the validation rules triggered by each field; associating field configurations with corresponding resource files, such as matching text resources to the display name, prompt information, etc. of the field, and matching image resources to the specified display area of ​​the page; at the same time, according to the page structure requirements defined in the product configuration, all fields are sorted to determine the display order, layout method, and association relationship of each field on the page. After integration, the dynamic assembly module generates a complete page configuration data, which contains all the information required for page construction, including field types, attributes, rules, associated resources, layout order, etc., providing comprehensive data support for front-end rendering.

[0046] During the data integration process, the same resource file can be reused across products through association with different product codes, meaning that the same image resource can be referenced by multiple product pages. At the same time, the same product can be associated with multiple resource files through different text type enumeration values, ensuring that product pages can load various resources as needed.

[0047] After the front-end client application receives the page configuration data transmitted by the server, the rendering engine starts the parsing and rendering process. The pre-deployed general component library in the front end contains various standard components corresponding to the field types. These components are all general-purpose designs, not bound to specific business logic, and only reserve attribute configuration interfaces. The functions can be flexibly adjusted according to the received configuration information.

[0048] The rendering engine first parses the page configuration data layer by layer, extracting key information such as field identifiers, component types, attribute parameters, and layout rules. Based on the parsed component types, it selects the corresponding components from the general component library. For example, when parsing a basic input type field, it selects the basic input component from the component library; when parsing a composite selection type field, it selects the composite selection component from the component library. Subsequently, the rendering engine assigns the attribute parameters from the page configuration data to the selected component through an attribute passing mechanism. This includes setting the component's display name, input restrictions, interaction methods, and linked fields, enabling the component to have functionality adapted to business requirements.

[0049] After the components are configured, the rendering engine arranges all the configured components in an orderly manner on the page according to the layout rules defined in the page configuration data. It determines the position, spacing, line break rules, etc. of each component, and integrates the overall style of the page to ensure that the page layout is beautiful and conforms to user operation habits. Finally, through the processing of the rendering engine, a complete product insurance page is generated in the client application of the terminal device. This page contains all the configured form fields, corresponding interactive components and page layout, and supports users to perform operations such as inputting and selecting insurance information.

[0050] The verification module's verification logic runs synchronously with the front-end rendering process to ensure the legality and consistency of user input data. When a user performs input operations on the insurance application page of the terminal device, the real-time verification function is triggered: each field component on the page integrates an event listener. When the user inputs content or modifies a field value, the listener immediately captures the operation and calls the verification rules bound to that field to validate the input data. For example, when a user enters their insurance age, the verification rules will automatically verify whether the input content is a valid numeric type and whether it is within the preset age range. If the input data does not conform to the rules, the page will display the corresponding prompt information in real time, informing the user of the reason for the error and guiding the user to correct the input.

[0051] The linked verification function is triggered when a field value changes and that field has a linked relationship: When a user modifies the value of a field with a linked attribute, the front end will notify the verification module through a preset trigger mechanism. The verification module will extract the linked rules corresponding to the field, determine the linked fields that need to be verified synchronously, call the form reorganization method to re-integrate the configuration information and verification rules of the linked fields, and perform unified verification on the current value of the linked fields. For example, after a user modifies the insured amount, if the insured amount and the premium have a linked calculation relationship, the verification module will synchronously verify whether the value of the premium field matches the insured amount. If they do not match, a prompt will be triggered to ensure the data consistency of the linked fields. All verification processes are completed in real time on the front end without waiting for server feedback, improving the user experience. At the same time, the verification results will be synchronously stored in the user's operation data to provide a basis for the submission and review of the subsequent insurance application process.

[0052] like Figure 3 As shown, the dynamic generation device of the present invention includes a configuration definition module, a strategy matching module, a dynamic assembly module, a dynamic rendering module, and a verification module: the configuration definition module receives operation instructions from the backend management system and stores various configuration information defined by the administrator in the database; when the server receives an insurance application request from the terminal device, the strategy matching module extracts the core parameters in the request and completes configuration query and matching; the dynamic assembly module integrates configuration and resources based on the matching results to generate page configuration data; the dynamic rendering module transmits the configuration data to the terminal device through the front-end interface and guides the front-end to complete page rendering; the verification module monitors user operations throughout the process and performs real-time verification and linkage verification.

[0053] After receiving a user's insurance application request, the terminal device transmits the request parameters to the server via the network. The dynamic generation device in the server processes the request according to the above process, generates page configuration data, and returns it to the terminal device. The client application on the terminal device generates the insurance application page through the rendering engine and displays it to the user. When the user enters information on the page, the terminal device executes the verification logic in real time and provides feedback on the result. After the user completes the insurance application information and submits it, the terminal device transmits the user data to the server. The server combines the configuration information in the database to perform subsequent business processing. The database continuously provides data storage and query support for configuration and resources throughout the entire process, ensuring stable system operation.

[0054] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A method for dynamically generating product page fields based on a backend, characterized in that, The method includes the following specific steps: S1: Define product configuration, field configuration, rule configuration, and resource configuration uniformly in the backend management system; S2: Construct a multi-dimensional parameter combination, generate a unique cache key based on the parameter combination, and query the corresponding configuration in the cache through the cache key; S3: Adopts a configuration and resource separation storage architecture. It uses the product code included in the product dimension parameter of the multi-dimensional parameter combination to associate the configuration table and resource table in the database, and assembles the complete page configuration data through association query; S4: The front-end uses a general component library and rendering engine to parse page configuration data to dynamically select components and set attributes, generating form fields, page layouts and interactive components; S5: Based on the preset validation rules in the field configuration, perform real-time validation and linkage validation on user input data to ensure data legality and consistency.

2. The method for dynamically generating product page fields based on the backend according to claim 1, characterized in that, In step S1, the product configuration is used to define the basic information of the product, the field configuration is used to define the configuration information of the form fields, the rule configuration is used to define the business rules, and the resource configuration is used to define the resource files. The field configuration includes field type configuration, field attribute configuration, and field rule configuration: field type configuration supports basic types, composite types, and custom types; field attribute configuration includes display attributes, validation attributes, interaction attributes, and linkage attributes; field rule configuration includes basic rules, business rules, and linkage rules.

3. The method for dynamically generating product page fields based on the backend according to claim 1, characterized in that, In step S2, the parameter combination includes product dimension parameters, permission dimension parameters, channel dimension parameters, and plan dimension parameters. The product dimension parameters include product code and template type; the permission dimension parameters include permission identifier, which is used to query channel permissions and user permissions; the channel dimension parameters are obtained by querying channel permissions through the permission identifier; and the plan dimension parameters include plan code.

4. The method for dynamically generating product page fields based on the backend according to claim 3, characterized in that, In step S2, the specific steps for generating a unique cache key based on the parameter combination and prioritizing the query of the corresponding configuration in the cache using this cache key are as follows: The product code, template type, permission identifier, and plan code are concatenated into strings in a preset fixed order, and a unique separator is added to avoid confusion between different parameter values, generating a globally unique cache key. The query process prioritizes calling a preset cache middleware, using this cache key to check if corresponding valid configuration data is stored. If a matching configuration exists in the cache, it is directly read from the cache and returned. If the cache misses or the cached data has expired, a conditional query logic is constructed, using the product code, template type, permission identifier, and plan code as the core query conditions, and related data tables including the product configuration table and rule configuration table are queried to extract the corresponding configuration information. After the query is completed, the obtained configuration data is associated with the generated cache key and stored in the cache middleware, and a preset cache validity period is set to complete the update of the cached data.

5. The method for dynamically generating product page fields based on the backend according to claim 1, characterized in that, In step S3, an architecture design is adopted that separates the storage of configuration information and resource files. The basic information of the product, the configuration of product functions, and the configuration of product rules are classified and stored in the product configuration table and the rule configuration table. The field configuration is standardized and defined through the BaseType class data structure, which clarifies the field name, field type, validation rules, and display attribute elements. The product text resources, image resources, and rich text resource files are centrally stored in the product text table, and a unique association relationship is established through the product code and text type enumeration. After receiving the front-end request, the back-end uses the product code as the core association identifier and synchronously retrieves the product configuration table and the product text table through the database association query mechanism to extract the matching configuration data and corresponding resource files. After integration and binding, complete page configuration data containing the component configuration, attribute parameters, resource references, and rule associations required for page construction is generated.

6. The method for dynamically generating product page fields based on the backend according to claim 5, characterized in that, In step S3, the specific technical solution for establishing a unique association relationship through product code and text type enumeration is as follows: the product code serves as the globally unique identifier of the product, and together with the preset text type enumeration, constitutes the core association of the product text table. The text type enumeration standardizes and classifies resource types and assigns unique identifier values, including text resources, image resources, and rich text resource categories. A product code field and a text type enumeration field are specifically set in the product text table, and the two are configured as a joint unique index. When a related query is required, all resource records of the corresponding product are locked by the product code of the target product, and then the required type of resources under the product are filtered out by combining the specific text type enumeration value, so as to achieve precise binding between product configuration and corresponding resource files.

7. The method for dynamically generating product page fields based on the backend according to claim 1, characterized in that, In step S4, an architecture is adopted in which a front-end general component library and a rendering engine work together. The front-end pre-deploys a standard component library covering basic, composite, and custom types. The components in the component library are universal and not bound to specific business logic. Only attribute configuration interfaces are reserved. The rendering engine receives complete page configuration data transmitted from the back-end through a preset interface. After parsing the component selection instructions, attribute parameters, and layout rule information contained in the complete page configuration data, it selects the appropriate component from the component library according to the component identifier in the page configuration data. Then, it assigns the corresponding display, interaction, and linkage attributes to the component through an attribute passing mechanism. At the same time, it arranges the selected components in an orderly manner according to the layout rules defined in the configuration, and completes the integration and presentation of form fields, page layout, and interactive components to form a complete product page that meets the configuration requirements.

8. The method for dynamically generating product page fields based on the backend according to claim 1, characterized in that, In step S5, real-time verification is triggered by the component's state change event. When the user inputs data or the component's state changes, the preset verification method is automatically called to perform real-time verification of the input data according to the verification rules of the corresponding form field and to provide feedback on the result. Linked validation is initiated when the values ​​of form fields change. It calls the form reorganization mechanism through a preset trigger method, reorganizes the form structure, extracts the associated linked fields, and performs unified validation after collecting all relevant validation rules.

9. A backend-based product page field-level dynamic generation device, the device being used to implement the backend-based product page field-level dynamic generation method according to any one of claims 1-8, characterized in that, The device includes: Configuration definition module: Configured to define product configuration, field configuration, rule configuration, and resource configuration in the backend management system; The strategy matching module is configured to query and match the corresponding configuration based on the product code, template type, permission identifier, and plan code through parameter combinations. Dynamic assembly module: Configured to assemble matched configurations and resources through database join queries to generate complete page configuration data; Dynamic rendering module: Configured so that the front end can use a general component library and rendering engine to parse the configuration based on the page configuration data, dynamically select components and set their properties, and generate form fields, page layouts and interactive components; Validation module: Configured to perform real-time and linked validation on user input based on the validation rules configured in the fields.

10. A backend-based product page field-level dynamic generation system, wherein the system is used to deploy the backend-based product page field-level dynamic generation device as described in claim 9, characterized in that, The system includes Terminal equipment: used to receive user operations and display dynamically generated insurance application pages; Server: Deploys dynamic generation devices and executes configuration definition, strategy matching, dynamic assembly, rendering control, and verification logic; Database: Used to separate and store configuration information and resource files, supporting related queries and data reuse.

Images