Form field component configuration method and device, equipment and medium

Abstract

The invention relates to the technical field of computers, can be applied to business management program systems in the medical field and the financial field, and discloses configuration, device, equipment and medium of a form field component. The configuration method comprises the steps that the corresponding field component is obtained according to a form structure, and the component type of the field component is determined, the field component comprises an input box component, a pull-down component, a cascade component, a time and date component, a single-choice component, a multi-choice component and a text field component; constructing a corresponding container for the field component, and generating a structure identifier in the container according to the component type; determining corresponding field function features according to the structure identifier and the component type, wherein the field function features comprise a search mode, a display logic, a binding strategy and a style requirement; and in response to a received instruction of confirming to load the component configuration interface by the user, executing a configuration operation of the field component in the component configuration interface based on the field function characteristics. The development threshold can be obviously reduced, and the delivery efficiency and stability of the system are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a configuration method, device, equipment and medium for a form field component. Background Art

[0002] In recent years, with the widespread adoption of front-end and back-end separation architectures and the rapid development of front-end technology, the front-end's role in overall software systems has continued to rise. This is particularly true in specialized fields such as healthcare, elderly care services, and finance, where front-end systems not only display data but also carry an increasing amount of interaction and business logic. In home-based elderly care systems, form components have become a high-frequency and core component of front-end development, as they involve multi-dimensional scenarios such as user health information, service configuration, and appointment management. In financial systems, form components are also widely used in key processes such as account opening, product configuration, transaction entry, and risk assessment. The flexibility of form configuration, verification accuracy, and controllability directly impact the efficiency and security of business processes.

[0003] However, while existing mainstream general-purpose component platforms (such as ElementUI) provide certain basic capabilities, they often fail to carefully optimize form components to adapt to diverse business needs such as healthcare, scientific research, and financial operations. This leads to problems such as code duplication, cumbersome configuration, and difficulty in reuse. This not only limits development efficiency but also places a heavy burden on version maintenance and cross-team collaboration. Therefore, it is necessary to propose a configuration method for form field components that can significantly lower the development threshold and improve system delivery efficiency and stability. Summary of the Invention

[0004] The present invention provides a configuration method, device, computer equipment and medium for a form field component to solve technical problems in related technologies such as high threshold for developing form components, code duplication, and cumbersome configuration.

[0005] In a first aspect, a method for configuring a form field component is provided, comprising:

[0006] Obtain the corresponding field component according to the form structure and determine the component type of the field component, wherein the field component includes an input box component, a drop-down component, a cascade component, a time and date component, a single-select component, a multiple-select component, and a text field component;

[0007] Constructing a corresponding container for the field component, and generating a structure identifier in the container according to the component type;

[0008] Determining corresponding field functional characteristics according to the structure identifier and the component type, the field functional characteristics including search mode, display logic, binding strategy and style requirements;

[0009] In response to receiving a user confirmation instruction to load the component configuration interface, configuration operations of the field component are performed in the component configuration interface based on the field functional characteristics, wherein the configuration operations include adding operations, deleting operations, renaming operations, and refactoring operations.

[0010] In a second aspect, a configuration device for a form field component is provided, comprising:

[0011] An acquisition module is used to acquire corresponding field components according to the form structure and determine the component type of the field components. The field components include input box components, drop-down components, cascade components, time and date components, single-select components, multiple-select components, and text field components.

[0012] A construction module, configured to construct a corresponding container for the field component and generate a structure identifier in the container according to the component type;

[0013] a determination module, configured to determine corresponding field functional characteristics according to the structure identifier and the component type, wherein the field functional characteristics include search mode, display logic, binding strategy, and style requirements;

[0014] A configuration module is used to respond to receiving a user's instruction to confirm loading a component configuration interface, and to perform configuration operations of the field component based on the field functional characteristics in the component configuration interface, wherein the configuration operations include adding operations, deleting operations, renaming operations, and reconstructing operations.

[0015] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned method for configuring the form field component when executing the computer program.

[0016] In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-mentioned method for configuring form field components. In the scheme implemented by the above-mentioned method, apparatus, computer device, and storage medium for configuring form field components, corresponding field components can be obtained based on the form structure, and the component type of the field component can be determined. Field components include input box components, drop-down components, cascade components, time and date components, single-select components, multiple-select components, and text field components. Furthermore, a corresponding container can be constructed for the field component, and a structure identifier can be generated within the container based on the component type. The corresponding field functional characteristics can be determined based on the structure identifier and the component type. The field functional characteristics include search mode, display logic, binding strategy, and style requirements. Thus, in response to receiving a user confirmation instruction to load the component configuration interface, field component configuration operations can be performed in the component configuration interface based on the field functional characteristics, where configuration operations include adding, deleting, renaming, and reconstructing operations. In the present invention, by performing structured identification and configuration of form field components, the flexibility and reusability of form configuration are significantly improved. By automatically deriving field components based on the form structure and generating structure identifiers based on component types, this solution enables rapid component location and unified naming management, reducing human error. Furthermore, field functionality is automatically generated based on structure identifiers, enabling components with search, display, and binding capabilities, eliminating the need for manual configuration coding by developers and significantly reducing development workload. Fields can be added, deleted, renamed, and restructured through the configuration interface, supporting visual and dynamic management and improving system maintainability and real-time responsiveness. This solution is particularly effective in healthcare and home-based elderly care systems, where form fields contain complex and frequently changing content such as patient information, service items, and appointment data. This solution effectively supports personalized, multi-dimensional configuration requirements, improving system stability and rollout efficiency, reducing operational risks, and ensuring data security and compliance. In the financial sector, this solution enhances the flexibility and reusability of form configuration, meeting the dynamic field adjustment requirements of various business operations, such as account opening, trading, and risk management, and enhancing system compliance and maintainability. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0018] Figure 1 This is a schematic diagram of an application environment of a configuration method of a form field component in one embodiment of the present invention;

[0019] Figure 2 It is a flowchart of a method for configuring a form field component in one embodiment of the present invention;

[0020] Figure 3 yes Figure 1 A schematic flow chart of a specific implementation of step S10;

[0021] Figure 4 It is a structural diagram of a configuration device for form field components in one embodiment of the present invention;

[0022] Figure 5 is a structural diagram of a computer device in one embodiment of the present invention;

[0023] Figure 6 FIG. 2 is another structural diagram of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0025] The configuration method of the form field component provided by the embodiment of the present invention can be applied to Figure 1In an application environment, the client communicates with the server through a network. The server can obtain the corresponding field component according to the form structure through the client, and determine the component type of the field component, wherein the field component includes an input box component, a drop-down component, a cascade component, a time and date component, a single-choice component, a multiple-choice component and a text field component; construct a corresponding container for the field component, and generate a structure identifier in the container according to the component type; determine the corresponding field function characteristics according to the structure identifier and the component type, wherein the field function characteristics include search mode, display logic, binding strategy and style requirements; in response to receiving the user's instruction to confirm loading the component configuration interface, perform the configuration operation of the field component based on the field function characteristics in the component configuration interface, wherein the configuration operation includes adding operation, deleting operation, renaming operation and reconstructing operation. In the present invention, the flexibility and reusability of the form configuration are significantly improved by structurally identifying and configuring the form field components. By automatically obtaining the field components according to the form structure and generating the structure identifier based on the component type, the rapid positioning and unified naming management of the components can be achieved, thereby reducing human errors. At the same time, field functionality is automatically generated based on structure identifiers, enabling components with search, display, and binding capabilities, eliminating the need for developers to manually code and configure, significantly reducing development workload. Field addition, deletion, renaming, and reconstruction operations are implemented through a configuration interface, supporting visual and dynamic management and improving system maintainability and real-time responsiveness. In particular, in healthcare and home-based elderly care systems, form fields involve complex and frequently changing content, such as patient information, service items, and appointment data. This solution effectively supports these personalized, multi-dimensional configuration requirements, improving system stability and rollout efficiency, reducing operational risks, and ensuring data security and compliance. In the financial sector, this solution can enhance the flexibility and reusability of form configuration, meeting the dynamic field adjustment requirements of various business types such as account opening, trading, and risk control, thereby enhancing system compliance and maintainability. The client can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The server can be implemented as a standalone server or a server cluster consisting of multiple servers. The present invention is described in detail below through specific embodiments.

[0026] See also Figure 2 As shown, Figure 2 A flowchart of a method for configuring a form field component provided in an embodiment of the present invention includes the following steps:

[0027] S10: Acquire a corresponding field component according to the form structure, and determine the component type of the field component.

[0028] The field components include input box components, drop-down components, cascade components, time and date components, single-select components, multiple-select components and text field components.

[0029] For example, the above form structure consists of multiple fields, and each field presents different input forms according to business needs, such as text input, option selection, date selection, etc. In order to improve development efficiency and system maintainability, the form structure can be parsed to extract the identifier, attribute definition, data type and other information of each field item, and automatically mapped to the corresponding component type based on the purpose and interactive characteristics of the field. For example, user input fields will be matched as input box components, drop-down selection items will be matched as drop-down components, data with hierarchical structures such as regions and service categories will be matched as cascade components, those involving time ranges will be matched as time and date components, and single-choice and multiple-choice requirements such as gender and service methods will be matched as single-choice components and multiple-choice components respectively. For scenarios where long text is input, they will be matched as text field components.

[0030] Through this step, structured and automated binding between form fields and front-end components can be achieved, laying the foundation for subsequent component container generation, functional feature configuration and other operations, reducing the workload of manual judgment and repetitive coding, while ensuring the consistency and standardization of component selection.

[0031] Among them, such as Figure 3 As shown, in step S10, that is, obtaining the corresponding field component according to the form structure and determining the component type of the field component, the following steps are included:

[0032] S11: Acquire a field definition area in the form structure, and extract the field component in the field definition area.

[0033] S12: Extracting a field identifier from the field component, and determining a component type of the field component according to the field identifier.

[0034] In step S11, the entire form structure data can be scanned to locate key areas containing field configuration information. In a form configuration file or data structure, the field definition area is an array of objects or a collection of structures that describe the fields contained in the form, as well as each field's attributes, labels, data source, validation rules, and other information. In this step, the starting position and structural format of this area can be identified, and the field component data can be extracted sequentially.

[0035] For step S12, a field identifier can be obtained from each extracted field component. The identifier is usually the unique key name of the field (such as fieldKey, prop or name), which represents the business meaning and data binding point of the field in the form. The purpose of the field can be further analyzed through the field identifier, and the corresponding component type can be determined in combination with the attributes attached to the field (such as type, widget, options, etc.). For example, if the field identifier is "serviceType" and the type attribute is "select", it can be determined that it corresponds to a drop-down component; if it is "appointmentDate" and the type is "date", it is identified as a time and date component.

[0036] Through steps S11 and S12, not only are all field definitions abstracted from the form, but the most suitable front-end component type is also automatically determined and matched, enabling intelligent component binding. This process avoids manual configuration errors and improves the standardization and automation of front-end component development.

[0037] S20: Construct a corresponding container for the field component, and generate a structure identifier in the container according to the component type.

[0038] For example, a wrapper structure container can be created for each identified field component, typically a div or custom tag element containing layout information. This container not only hosts the component itself on the page but also handles styling, event binding, and rendering configuration. Subsequently, a unique and standardized structure identifier can be generated within the container based on the field component type (e.g., input box, drop-down box, date selection, etc.).

[0039] It should be noted that the structural identifier is generally generated based on the component type, combined with dimensional codes such as field identification and component function, to mark the purpose, location and associated logic of the container. The generation of structural identifiers not only makes it easier for developers to manage and debug components, but also provides a key reference basis for subsequent automated configuration, functional feature mapping and dynamic rendering, thereby achieving a strong binding relationship between field components and their business roles. This step is particularly important in medical systems with a large number of form fields or frequent scene switching, which helps to improve the maintainability and flexibility of the overall page structure.

[0040] In some embodiments, constructing a container for the field component and generating a structure identifier in the container according to the component type includes: determining a structure container element corresponding to the field component and constructing the container based on the structure container element; generating the structure identifier based on the component type and writing the structure identifier into the structure container element.

[0041] For example, to achieve structured management of form components, the first step is to determine the structural container element corresponding to each field component. This step is usually determined based on the component's position on the page, layout rules, or configuration template. For example, a one-line container is assigned to an input box, and a wrapping container is assigned to a multiple-select component. Based on the preset container template, the container structure used to wrap the field component can be dynamically constructed to ensure good display and scalability. This containerized design not only improves the visual presentation of the component, but also provides a structural foundation for subsequent function binding and style isolation.

[0042] Furthermore, after building the container, a corresponding structure identifier can be generated based on the type of the field component as the unique semantic identifier of the container. Structure identifiers are usually generated using standardized naming rules, for example, by adding a component type prefix and a field identifier suffix (e.g., yl-select_suppl ierType). The generated identifier will be written into the structure container element and exist as a custom attribute or class name of the container, used for subsequent configuration item rendering, feature mapping, style control, and dynamic association with the data model.

[0043] This step is particularly suitable for scenarios with a wide variety of form components and complex configuration rules, such as those in the healthcare and elderly care industries, and can significantly improve the system's automation level and maintenance efficiency.

[0044] S30: Determine corresponding field functional characteristics according to the structure identifier and the component type.

[0045] The field functional features include search mode, display logic, binding strategy and style requirements.

[0046] For example, the field's contextual information in the form is first located using a structural identifier. Then, based on the field's component type (e.g., drop-down, single-select, time and date), corresponding configuration rules are extracted from a predefined library of functional templates. These rules are categorized as field functional features, including search mode (e.g., whether to enable remote search or fuzzy matching), display logic (e.g., visibility conditions, disabled status), binding strategy (e.g., bound data source path, whether to link with other fields), and style requirements (e.g., width, alignment, responsive layout, etc.).

[0047] This step can automatically complete field function configuration, avoid repeated manual coding, improve development efficiency and configuration standardization, and is especially suitable for application scenarios such as medical fields with complex fields and variable configurations.

[0048] In some embodiments, determining the corresponding field function characteristics based on the structure identifier and the component type includes: searching for a matching field function template based on the structure identifier; extracting corresponding function configuration items from the field function template based on the component type; establishing a binding relationship between the function configuration items and the field component to obtain the field function characteristics.

[0049] For example, in order to achieve automatic configuration and behavior reuse of field functions, the first step is to search for matching function templates in the preset field function template library based on the structure identifier of the field component. These templates are usually indexed by structure identifiers and encapsulate a set of standard function configurations suitable for different business scenarios. Then, based on the type of field component, the function configuration items corresponding to the type are extracted from the matched function template. For example, for a drop-down component, its remote search, default value setting, and option linkage rules are extracted. Finally, a binding relationship is established between the extracted function configuration items and the field component, so that the function configuration and component behavior are linked to form the final field function characteristics.

[0050] This step achieves the decoupling and reuse of component configuration and functional logic, improves the intelligence and standardization of form development, and is particularly suitable for medical information systems with many types of fields and complex interactions.

[0051] S40: In response to receiving a user instruction to confirm loading a component configuration interface, performing a configuration operation of the field component based on the field functional characteristics in the component configuration interface.

[0052] The configuration operations include adding operations, deleting operations, renaming operations, and refactoring operations.

[0053] In some embodiments, in response to receiving an instruction from the user to confirm loading the component configuration interface, the configuration operation of the field component is performed in the component configuration interface based on the field functional characteristics, including: receiving the user's instruction on the configuration item, and determining the user's configuration result based on the instruction; updating the attribute configuration of the field component based on the configuration result and the field functional characteristics, and synchronizing the updated attribute configuration to the component configuration interface.

[0054] For example, based on the structure identifier and component type generated in the previous step, the corresponding functional feature template can be extracted from the preset field function mapping library, and adjusted and completed in combination with the business context of the current form to generate a complete set of field functional features. The field functional features generally include: search mode (such as fuzzy search, remote search), display logic (such as field visibility, disable conditions), binding strategy (such as binding data source path, dynamic linkage rules) and style requirements (such as alignment, width control, responsive layout rules), etc.

[0055] This automated matching mechanism can significantly reduce the workload of manually configuring field behaviors and improve configuration consistency and accuracy. It is particularly suitable for medical form systems with complex field functions and frequent interactions.

[0056] In some embodiments, the method further includes: generating a template file containing functional features of the current field; sending the template file to the cloud for remote batch configuration to obtain a configured file; parsing the configured file and extracting field configuration data.

[0057] For example, to achieve the automatic generation of functional features of field components, you can first use the structure identifier as the key index to search for a matching functional template from the field function template library. The template usually presets functional configuration rules associated with specific business scenarios. Subsequently, based on the type of field component, the corresponding functional configuration items can be extracted from the template, such as remote search, option linkage, default value logic, etc. for drop-down components. Finally, these functional configuration items can be bound to the current field component to form a field functional feature set, which is used to drive the dynamic behavior of the component in the form.

[0058] This step achieves the decoupling and reuse of field functions and component structures, improves the standardization and automation of form function configuration, and is particularly suitable for complex and frequently changing medical information systems.

[0059] In some embodiments, the method further includes: triggering verification logic after completing the configuration operation to read the configuration items of the field component; judging whether the data type of the field component is consistent based on the configuration items of the field component; if the data type of the field component is inconsistent, determining that there are illegal configuration items in the field component and generating an error prompt.

[0060] For example, to ensure the correctness of the field component configuration and data consistency, the method will automatically trigger the verification logic after completing the field configuration operation. First, the various configuration parameters of the configured field component will be read, including its bound data field, type definition, and expected value format; then, based on these configuration items, it will be determined whether the data type of the field component is consistent with the definition in its bound data source or form model. For example, if a multi-select component is incorrectly bound to a single string value, or a date component is bound to a Boolean type, it will be identified as a type inconsistency. When such a mismatch is detected, it can be marked as an illegal configuration item, and a clear error message can be generated to feedback to the user, thereby avoiding runtime exceptions or data anomalies caused by configuration errors. This verification mechanism can effectively improve the reliability of form component configuration, and is particularly suitable for system scenarios such as medical care that have extremely high requirements for data accuracy.

[0061] As can be seen, the above solution significantly improves the flexibility and reusability of form configuration through structured identification and configuration of form field components. By automatically obtaining field components based on the form structure and generating structure identifiers based on component types, components can be quickly located and uniformly named, reducing human error. Furthermore, field functionality is automatically generated based on structure identifiers, enabling components with search, display, and binding capabilities, eliminating the need for manual configuration by developers and significantly reducing development workload. Field addition, deletion, renaming, and refactoring are supported through the configuration interface, enabling visual and dynamic management and improving system maintainability and real-time responsiveness. This solution is particularly effective in healthcare and home-based elderly care systems, where form fields contain complex and frequently changing content such as patient information, service items, and appointment data. This solution effectively supports personalized, multi-dimensional configuration requirements, improving system stability and rollout efficiency, reducing operational risks, and ensuring data security and compliance. In the financial sector, this solution can enhance the flexibility and reusability of form configuration, meeting the dynamic field adjustment requirements of various business operations such as account opening, trading, and risk management, thereby enhancing system compliance and maintainability.

[0062] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0063] In one embodiment, a configuration device for a form field component is provided, and the configuration device for the form field component corresponds one-to-one with the configuration method for the form field component in the above embodiment. Figure 4 As shown, the configuration device of the form field component includes an acquisition module 101, a construction module 102, a determination module 103, and a configuration module 104. The detailed description of each functional module is as follows:

[0064] The acquisition module 101 is used to obtain the corresponding field component according to the form structure and determine the component type of the field component. The field component includes an input box component, a drop-down component, a cascade component, a time and date component, a single-select component, a multiple-select component, and a text field component;

[0065] A construction module 102 is configured to construct a corresponding container for the field component and generate a structure identifier in the container according to the component type;

[0066] A determination module 103 is configured to determine corresponding field functional characteristics according to the structure identifier and the component type, wherein the field functional characteristics include search mode, display logic, binding strategy, and style requirements;

[0067] The configuration module 104 is used to respond to receiving the user's instruction to confirm loading the component configuration interface, and perform the configuration operation of the field component based on the field functional characteristics in the component configuration interface, wherein the configuration operation includes adding operation, deleting operation, renaming operation and reconstructing operation.

[0068] In one embodiment, the acquisition module 101 is specifically configured to:

[0069] Obtaining a field definition area in the form structure, and extracting the field component in the field definition area;

[0070] A field identifier in the field component is extracted, and a component type of the field component is determined according to the field identifier.

[0071] In one embodiment, the construction module 102 is specifically configured to:

[0072] Determine a structural container element corresponding to the field component, and construct the container based on the structural container element;

[0073] The structure identifier is generated based on the component type and written into the structure container element.

[0074] In one embodiment, the determination module 103 is further configured to:

[0075] Searching for a matching field function template based on the structure identifier;

[0076] Extracting corresponding function configuration items from the field function template according to the component type;

[0077] A binding relationship is established between the functional configuration item and the field component to obtain the field functional characteristics.

[0078] In one embodiment, the configuration module 104 is specifically configured to:

[0079] receiving an instruction from the user for the configuration item, and determining a configuration result of the user according to the instruction;

[0080] The attribute configuration of the field component is updated according to the configuration result and the field functional characteristics, and the updated attribute configuration is synchronized to the component configuration interface.

[0081] In one embodiment, the acquisition module 101 is specifically configured to:

[0082] Sending the template file to the cloud for remote batch configuration to obtain the configured file;

[0083] The configured file is parsed and the field configuration data is extracted.

[0084] In one embodiment, the acquisition module 101 is specifically configured to:

[0085] After completing the configuration operation, the verification logic is triggered to read the configuration items of the field component;

[0086] Determining whether the data types of the field components are consistent based on the configuration items of the field components;

[0087] If the data types of the field components are inconsistent, it is determined that there are illegal configuration items in the field components and an error prompt is generated.

[0088] The present invention provides a configuration device for form field components, which can significantly improve the flexibility and reusability of form configuration by performing structured identification and configuration of form field components. By automatically obtaining field components according to the form structure and generating structure identifiers based on the component types, rapid positioning and unified naming management of components can be achieved, reducing human errors. At the same time, field functional features are automatically generated based on the structure identifier, so that the components have the ability to search, display, bind, etc., without the need for developers to manually code and configure, greatly reducing the development workload. The addition, deletion, renaming and reconstruction of fields are realized through the configuration interface, supporting visual and dynamic management, and improving the maintainability and real-time response capabilities of the system. Especially in medical and home-based elderly care systems, form fields involve a large amount of patient information, service items, appointment data and other complex and frequently changing content. This solution can effectively support their personalized and multi-dimensional configuration needs, improve system stability and online efficiency, reduce operational risks, and ensure data security and compliance.

[0089] The specific definition of the form field component configuration device can be found in the definition of the form field component configuration method above and will not be repeated here. The various modules in the above-mentioned form field component configuration device can be implemented in whole or in part through software, hardware, or a combination thereof. The above-mentioned modules can be embedded in or independent of the processor of the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each of the above modules.

[0090] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 5As shown. The computer device includes a processor, memory, network interface and database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, it implements the functions or steps on the server side of a configuration method for a form field component.

[0091] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor, memory, network interface, display screen and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps on the client side of a configuration method of a form field component.

[0092] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are performed:

[0093] Obtain the corresponding field component according to the form structure and determine the component type of the field component, wherein the field component includes an input box component, a drop-down component, a cascade component, a time and date component, a single-select component, a multiple-select component, and a text field component;

[0094] Constructing a corresponding container for the field component, and generating a structure identifier in the container according to the component type;

[0095] Determining corresponding field functional characteristics according to the structure identifier and the component type, the field functional characteristics including search mode, display logic, binding strategy and style requirements;

[0096] In response to receiving a user confirmation instruction to load the component configuration interface, configuration operations of the field component are performed in the component configuration interface based on the field functional characteristics, wherein the configuration operations include adding operations, deleting operations, renaming operations, and refactoring operations.

[0097] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0098] Obtain the corresponding field component according to the form structure and determine the component type of the field component, wherein the field component includes an input box component, a drop-down component, a cascade component, a time and date component, a single-select component, a multiple-select component, and a text field component;

[0099] Constructing a corresponding container for the field component, and generating a structure identifier in the container according to the component type;

[0100] Determining corresponding field functional characteristics according to the structure identifier and the component type, the field functional characteristics including search mode, display logic, binding strategy and style requirements;

[0101] In response to receiving a user confirmation instruction to load the component configuration interface, configuration operations of the field component are performed in the component configuration interface based on the field functional characteristics, wherein the configuration operations include adding operations, deleting operations, renaming operations, and refactoring operations.

[0102] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can be found in the relevant descriptions of the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0103] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchl ink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0104] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0105] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should all be included in the scope of protection of the present invention.

Claims

1. A method for configuring a form field component, characterized in that: The method comprises: Obtain the corresponding field component according to the form structure and determine the component type of the field component, wherein the field component includes an input box component, a drop-down component, a cascade component, a time and date component, a single-select component, a multiple-select component, and a text field component; Constructing a corresponding container for the field component, and generating a structure identifier in the container according to the component type; Determining corresponding field functional characteristics according to the structure identifier and the component type, the field functional characteristics including search mode, display logic, binding strategy and style requirements; In response to receiving a user confirmation instruction to load the component configuration interface, configuration operations of the field component are performed in the component configuration interface based on the field functional characteristics, wherein the configuration operations include adding operations, deleting operations, renaming operations, and refactoring operations.

2. The method according to claim 1, characterized in that The obtaining of the corresponding field component according to the form structure and determining the component type of the field component includes: Obtaining a field definition area in the form structure, and extracting the field component in the field definition area; A field identifier in the field component is extracted, and a component type of the field component is determined according to the field identifier.

3. The method according to claim 1, characterized in that The step of constructing a container for the field component and generating a structure identifier in the container according to the component type includes: Determine a structural container element corresponding to the field component, and construct the container based on the structural container element; The structure identifier is generated based on the component type and written into the structure container element.

4. The method according to claim 1, wherein The determining of corresponding field functional characteristics according to the structure identifier and the component type includes: Searching for a matching field function template based on the structure identifier; Extracting corresponding function configuration items from the field function template according to the component type; A binding relationship is established between the functional configuration item and the field component to obtain the field functional characteristics.

5. The method according to claim 1, wherein In response to receiving a user confirmation instruction to load a component configuration interface, performing a configuration operation of the field component based on the field functional characteristics in the component configuration interface includes: receiving an instruction from the user for the configuration item, and determining a configuration result of the user according to the instruction; The attribute configuration of the field component is updated according to the configuration result and the field functional characteristics, and the updated attribute configuration is synchronized to the component configuration interface.

6. The method according to claim 1, characterized in that The method further comprises: Generate a template file containing the functional characteristics of the current field; Sending the template file to the cloud for remote batch configuration to obtain the configured file; The configured file is parsed and the field configuration data is extracted.

7. The method according to claim 1, characterized in that The method further comprises: After completing the configuration operation, the verification logic is triggered to read the configuration items of the field component; Determining whether the data types of the field components are consistent based on the configuration items of the field components; If the data types of the field components are inconsistent, it is determined that there are illegal configuration items in the field components and an error prompt is generated.

8. A configuration device for a form field component, characterized in that: include: An acquisition module is used to acquire corresponding field components according to the form structure and determine the component type of the field components. The field components include input box components, drop-down components, cascade components, time and date components, single-select components, multiple-select components, and text field components. A construction module, configured to construct a corresponding container for the field component and generate a structure identifier in the container according to the component type; a determination module, configured to determine corresponding field functional characteristics according to the structure identifier and the component type, wherein the field functional characteristics include search mode, display logic, binding strategy, and style requirements; A configuration module is used to respond to receiving a user's instruction to confirm loading a component configuration interface, and to perform configuration operations of the field component based on the field functional characteristics in the component configuration interface, wherein the configuration operations include adding operations, deleting operations, renaming operations, and reconstructing operations.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method for configuring the form field component according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method for configuring the form field component according to any one of claims 1 to 7 are implemented.

Images