Dynamic entity input method and device based on low-code development platform, storage medium and terminal equipment

Abstract

The embodiment of the application discloses a dynamic entity input method and device based on a low-code development platform, a storage medium and a terminal device, and relates to the field of data processing. The embodiment of the application enhances the flexibility and adaptability of the data model by constructing a base class model and its attribute information and creating a subclass model, effectively responds to changes in business scenario requirements, reduces repeated configuration, and improves modeling efficiency. With the help of a scene and a reference operation template configuration interface, multiple subclass models can be easily created and managed on an interface for operation, the subclass model is bound to a specific scene, and intuitive display and interaction of data are realized. The entity input interface is bound to the model attribute, the dynamic and intelligent data input during the running period is realized, the user can display the entity input interface by triggering the attribute input box, and select and input data. After data input, the corresponding input box is automatically filled in, the work efficiency is improved, and the data accuracy is ensured.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a dynamic entity input method, apparatus, storage medium and terminal device based on a low-code development platform. Background Art

[0002] In modern software development, low-code development platforms, with their graphical interfaces and simple configuration, have become a key tool for improving development efficiency and lowering technical barriers to entry. These platforms enable developers to quickly create applications through intuitive configuration without in-depth coding. However, despite their impressive performance in streamlining the development process, low-code platforms still face significant challenges in handling complex and ever-changing business needs.

[0003] Traditional low-code platforms are primarily designed to support the configuration of single-entity pages, which falls short in providing users with an intuitive and consistent data manipulation experience. Because low-code platforms' core goal is to simplify development and lower barriers to entry, their original design didn't fully consider the dynamic interactions and complex layouts across multiple entities. Consequently, when business requirements involve the interaction of multiple entities and complex layouts, the graphical interfaces and configuration methods of low-code platforms often prove insufficient.

[0004] This limitation forces developers to perform additional programming to compensate for the configuration deficiencies of low-code platforms when handling dynamic interactions between multiple entities. This not only defeats the original purpose of low-code platforms, which is to reduce coding workload, but also increases the burden on developers and reduces development efficiency. Therefore, how to maintain the ease of use of low-code platforms while addressing their limitations in handling complex business needs has become a pressing issue in the current low-code development field. Summary of the Invention

[0005] The embodiments of the present application provide a dynamic entity input method, apparatus, storage medium, and terminal device based on a low-code development platform, which can solve the problem of low development efficiency of entity input in the low-code platform in the prior art. The technical solution is as follows:

[0006] In a first aspect, an embodiment of the present application provides a dynamic entity input method based on a low-code development platform, the method comprising:

[0007] Configuring a base class model in a data modeling interface, wherein the base class model includes description information of the base class model;

[0008] Selecting a base class model in the data modeling interface, and configuring attribute information for the selected base class model in the base class model configuration interface;

[0009] In the data modeling interface, a sub-model is configured, and the sub-model includes attribute information of the sub-model, which is inherited from attribute information of an associated base model;

[0010] In the scene configuration interface, a scene of the sub-model is configured, and the scene includes format information configured by a format wizard based on a plurality of scenes, and in the scene configuration interface, a scene of the base model is configured, and the scene includes format information configured by an operation template of the format wizard based on the scene;

[0011] An operation template of the format wizard is configured, in which one or more sub-models of the base model are selected, and a scene interface is bound to each selected sub-model based on a scene of the sub-model, and each sub-model corresponds to an entity;

[0012] An element type and an element layout mode are set for the bound scene interface, and the entity input interface configuration is bound to a specified model attribute;

[0013] When a triggering action of a user on a certain model attribute is detected in an application running period, an entity input interface is displayed according to an entity input interface configuration associated with the model attribute, and the entity input interface includes an entity list and a list page;

[0014] After receiving a selection instruction of the user on a certain entity in the entity list, an element corresponding to the entity is rendered in the list page according to a layout mode pre-configured for the entity;

[0015] Entity data is input in the rendered list page, and the entity data is filled into a model attribute input box.

[0016] In the second aspect, an embodiment of the present application provides a dynamic entity input device based on a low-code development platform, and the device includes:

[0017] A configuration unit is configured to configure a base model in a data modeling interface, and the base model includes description information of the base model;

[0018] A selection unit is configured to select a base model in the data modeling interface, and configure attribute information of the selected base model in a base model configuration interface;

[0019] The configuration unit is further configured to configure a sub-model in the data modeling interface, and the sub-model includes attribute information of the sub-model, which is inherited from attribute information of an associated base model;

[0020] The configuration unit is further configured to configure a scene of a sub-model on a scene configuration interface, wherein the scene includes format information of multiple scenes configured based on a format wizard, and to configure a scene of a base class model on a scene configuration interface, wherein the scene includes format information of the scene configured based on an operation template of the format wizard;

[0021] A binding unit configured to configure an interface based on an operation template of a format wizard, wherein one or more sub-models that inherit a base class model are selected in the operation template, and a scene interface is bound to each selected sub-model based on the sub-model scene, wherein each sub-model corresponds to an entity;

[0022] The binding unit is further used to set the element type and element layout for the bound scene interface, and to bind the above entity input interface configuration with the specified model attribute;

[0023] A detection unit, configured to detect a user triggering an action on a model attribute during application runtime and display an entity input interface according to an entity input interface configuration associated with the model attribute; the entity input interface includes an entity list and a list page;

[0024] a rendering unit, configured to, after receiving a user's selection instruction for an entity in the entity list, render a corresponding element in the list page according to a pre-configured layout of the entity;

[0025] The filling unit is used to enter entity data in the rendered list page and fill the entity data into the model attribute input box.

[0026] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0027] In a fourth aspect, an embodiment of the present application provides a terminal device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0028] The beneficial effects of the technical solutions provided by some embodiments of the present application include at least:

[0029] By configuring a list of base class models and their attributes, and creating sub-models based on them, data model design becomes more flexible, easily adapting to changing requirements in different business scenarios. Sub-class models inherit the attributes of the base class model, reducing the workload of repeated configuration and improving modeling efficiency.

[0030] Through the scene configuration interface, multiple scene interfaces can be conveniently created and managed, and sub-models can be bound to specific scene interfaces, with each sub-model corresponding to an entity. This scene-based configuration method makes data display and interaction more intuitive and in line with business needs. Meanwhile, by binding the entity input interface configuration to the model attribute input box, dynamic and intelligent data input is achieved.

[0031] Users can trigger the model attribute input box to display the corresponding entity input interface, which includes an entity list and a list page, facilitating users to select entities and input data. Meanwhile, according to the pre-configured layout of the entity, the corresponding elements are rendered in the list page, making the data input process smoother and more efficient.

[0032] After users input entity data in the rendered list page, the data can be automatically filled into the corresponding model attribute input box, avoiding errors and tediousness of manual input. This automated data input method not only improves work efficiency, but also ensures data accuracy and consistency.

[0033] This technical solution provides strong support for data management in complex business scenarios through flexible data modeling, scene-based configuration, intelligent entity input interface, and automated data filling. Whether it is data display, interaction, or input, it can meet business needs and improve data management efficiency and accuracy. BRIEF DESCRIPTION OF DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor based on these drawings.

[0035] Figure 1 is a network architecture schematic diagram provided by the embodiments of the present application;

[0036] Figure 2 is a flowchart of a dynamic entity input method based on a low-code development platform provided by the embodiments of the present application;

[0037] Figure 3 is a schematic diagram of a data modeling interface provided by the embodiments of the present application;

[0038] Figure 4 is a schematic diagram of a base class model configuration interface provided by the embodiments of the present application;

[0039] Figure 5 is a schematic diagram of a sub-model configuration interface provided by the embodiments of the present application;

[0040] Figure 6 is a schematic diagram of a scene configuration interface provided in an embodiment of the present application;

[0041] Figure 7 and Figure 8 is a schematic diagram of the format wizard interface provided in an embodiment of the present application;

[0042] Figure 9 is a schematic diagram of a physical input interface provided in an embodiment of the present application;

[0043] Figure 10 This is a structural diagram of a dynamic entity input device based on a low-code development platform provided by this application;

[0044] Figure 11 This is a structural diagram of a terminal device provided by this application. DETAILED DESCRIPTION

[0045] In order to make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

[0046] like Figure 1 As shown, the system architecture may include: a terminal device 101 and a server 102. The terminal device 101 and the server 102 may communicate via a network, which is used as a medium for providing communication links between the above-mentioned units. The network may include various types of wired communication links or wireless communication links, for example: wired communication links include optical fibers, twisted pairs, or coaxial cables, and wireless communication links include Bluetooth communication links, wireless fidelity (Wi-Fi) communication links, or microwave communication links.

[0047] It should be noted that the terminal device 101 and the server 102 can be hardware or software. When the terminal device 101 and the server 102 are hardware, they can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the terminal device 101 and the server 102 are software, they can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, without specific limitation herein.

[0048] Various communication client applications can be installed on the terminal device of this application, such as: video recording applications, video playback applications, voice interaction applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0049] The terminal device can be hardware or software. When the terminal device is hardware, it can be various terminal devices with a display screen, including but not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, and the like. When the terminal device is software, it can be installed in the terminal devices listed above. It can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, which is not specifically limited here.

[0050] When the terminal device is hardware, a display device and a camera can also be installed thereon. The display device can be various devices that can realize a display function, and the camera is used to collect a video stream. For example, the display device can be a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), and the like. A user can use the display device on the terminal device to view displayed text, pictures, videos, and the like.

[0051] It should be understood that Figure 1 The number of terminal devices, networks, and servers in the above is only illustrative. According to the needs of implementation, there can be any number of terminal devices, networks, and servers.

[0052] The following will be described in detail with reference to the accompanying drawings. Figure 2 The dynamic entity input method based on the low-code development platform provided by the embodiments of the present application will be described in detail. The dynamic entity input device based on the low-code development platform in the embodiments of the present application can be the terminal device shown in Figure 1

[0053] Please refer to Figure 2 A flowchart of a dynamic entity input method based on a low-code development platform is provided by the embodiments of the present application. As shown in Figure 2 The method of the embodiments of the present application can include the following steps:

[0054] S201, configuring a base class model in a data modeling interface.

[0055] The terminal device first loads a data modeling interface, which provides an area for displaying a base class model list. The terminal device reads the description information of the base class model from the local storage or the remote server, which includes the model name, the attribute structure, and the like. The terminal device displays these description information in the form of a list in the specified area of the data modeling interface for the user to select and view. ​

[0056] In some embodiments of this application, see Figure 3 The schematic diagram of the data modeling interface shown in the figure shows that the terminal device loads the data modeling interface, which provides an area dedicated to displaying and managing the base class model list. Base class model description information: The description information of the base class model includes but is not limited to: Model name: a name used to uniquely identify the base class model. Category: Indicates the category or field to which the base class model belongs, which helps users quickly find and filter models according to categories. Version number: records the version information of the base class model, which is used to distinguish different versions of models and ensure data consistency and compatibility. Release status: indicates whether the base class model has been released. The release status can be "released", "unreleased", "disabled", etc., which is used to control the availability and visibility of the model.

[0057] Data rows correspond to base class models: In the base class model list, each data row corresponds to a base class model. The data row is used to store and display the description information of the base class model, including the model name, category, version number, and release status.

[0058] Interface control buttons: The data modeling interface also provides a series of control buttons for users to manage and operate base class models, including: Add button: allows users to create a new base class model and enter its description information.

[0059] Modify button: allows users to select an existing base class model and modify its description information. Delete button: allows users to delete base class models that are no longer needed. Open button: allows users to open and view the details or configuration of a published base class model. Disable button: allows users to set a published base class model to a disabled state, making it no longer available. Restore button: allows users to restore a disabled base class model to an available state. Display base class model list: based on the above information, the terminal device displays the base class models and their description information in a list format in the designated area of ​​the data modeling interface. Users can quickly find and locate the required base class model by scrolling, filtering, or searching.

[0060] S202: Select a base class model in the data modeling interface, and configure attribute information for the selected base class model in the base class model configuration interface.

[0061] The user selects a base class model from a list of base class models. In response to the user's selection, the terminal device jumps to the base class model configuration interface. This interface provides input fields and options, allowing the user to configure attribute information for the selected base class model, such as attribute name, data type, and default value. After the user completes the configuration, the terminal device saves the configuration information to local storage or a remote server.

[0062] In some embodiments of this application, see Figure 4 The following diagram shows a base class model configuration interface. In the base class model list, the user selects a specific base class model to configure its properties. In response to the user's selection, the terminal device loads the base class model configuration interface. This interface is specifically used to configure and manage the properties of the selected base class model.

[0063] In the base class model configuration interface, there is a base class model attribute list, which is used to display and edit the attribute information of the selected base class model. Each data row corresponds to an attribute in the list. The attribute information stored in the data row includes: Item Title: A short title or label of the attribute, used to identify the attribute on the interface. Item Name: The formal name of the attribute, used to uniquely identify the attribute in the code or database. Item Description: A detailed description of the attribute, explaining its purpose, constraints or business logic, etc. Data Type: The data type of the attribute, such as integer, floating point number, string, date, etc. Reference Definition: If the attribute is a reference to other models or entities, the referenced target model or entity is defined here. Length: For attributes of string type, specify its maximum length. Decimal Places: For attributes of numeric type, specify the number of digits in its decimal part. Field Name: The name of the field used to store the attribute in the database or code.

[0064] Interface control buttons: The base class model configuration interface also provides a series of control buttons for users to manage and operate properties, including: Add button: allows users to add new properties to the property list and enter its property information. Insert button: allows users to insert a new property before the currently selected property. Copy button: allows users to copy the currently selected property and generate a new property (users may need to modify certain property information to avoid duplication). Delete button: allows users to delete the currently selected property. Save button: allows users to save changes made to the property list and save the updated property information to local storage or a remote server. Edit property information: Users can modify the property information by clicking the data row or related editing control in the property list. The terminal device will update the interface in real time to reflect the user's changes.

[0065] Validate attribute information: Before saving the attribute information, the terminal device will validate the attribute information entered by the user to ensure that it meets the constraints such as data type, length, decimal places, etc. If the validation fails, the terminal device will display an error message and prompt the user to make corrections.

[0066] S203. Configure the sub-model in the data modeling interface.

[0067] The terminal device loads a sub-model configuration interface, which provides an area to display a list of sub-models. For each sub-model, the terminal device inherits its attribute information based on the base class model selected by the user. The user can add additional attributes or modify inherited attributes for each sub-model in the sub-model configuration interface. The terminal device generates a unique identifier for each sub-model and associates it with an entity (such as a record in a database or a business object). After configuration is complete, the list of sub-models and their attribute information is saved to local storage or a remote server.

[0068] In some embodiments of the present application, referring to the sub-model configuration interface shown in Figure 5 After completing the configuration of the base class model, the user can enter the sub-model configuration interface through navigation or menu. This interface is specifically designed to display and manage the list of sub-models. In the sub-model configuration interface, each data row corresponds to a sub-model. These data rows not only display the attribute information of the sub-model, but also point to specific entities (such as database tables, business objects, etc.) through association relationships.

[0069] Each sub-model inherits from a base class model, so most of the fields stored in its data row are inherited from the associated base class model. These fields include all attributes of the base class model, but the sub-model can also add or override specific attributes.

[0070] In addition to the attributes inherited from the base class model, the sub-model also has its own attribute information, including: model name: a name used to uniquely identify the sub-model. Belonging category: indicates the classification or field to which the sub-model belongs, which helps users quickly find and filter sub-models according to categories. Version number: records the version information of the sub-model, used to distinguish different versions of the sub-model, ensuring data consistency and compatibility. Release status: indicates whether the sub-model has been released, and the release status can be "released", "not released", "disabled", etc., used to control the availability and visibility of the sub-model.

[0071] Interface control buttons: the sub-model configuration interface also provides a series of control buttons to allow users to manage and operate sub-models, including: add button: allows users to create a new sub-model based on the selected base class model and input its specific attribute information. Modify button: allows users to select an existing sub-model and modify its attribute information, including adding or overriding attributes inherited from the base class model. Delete button: allows users to delete sub-models that are no longer needed.

[0072] When creating or modifying a submodel, users need to specify an entity to associate with the submodel. This entity can be a database table, a business object, or any other data structure that can be recognized and processed by the system. After modifying or adding a submodel, the terminal device will validate the attribute information entered by the user to ensure that it complies with constraints such as data type and length and is consistent with the associated base model. After verification, the user can save the submodel configuration.

[0073] S204. Configure the scene of the sub-model in the scene configuration interface. The scene includes format information of multiple scenes configured based on the format wizard. Configure the scene of the base class model in the scene configuration interface. The scene includes format information of the scene configured based on the operation template of the format wizard.

[0074] The terminal device loads the scene configuration interface, which provides an area for displaying a list of scenes. Users can create new scenes or edit existing ones. Each scene contains multiple scene interface attributes, such as interface layout and element types. The terminal device saves the user-configured scene information to local storage or a remote server.

[0075] In some embodiments of this application, see Figure 6 The following diagram shows a scene configuration interface. Users access the scene configuration interface through navigation or menus. This interface is used to display and manage the scene list. In the scene configuration interface, each data row corresponds to a scene interface. The data row stores the scene interface's attribute information, which describes the scene interface's basic characteristics and configuration.

[0076] The attribute information of the scenario interface includes but is not limited to: Scenario name: a name used to uniquely identify the scenario interface, which is convenient for user identification and management. Category: indicates the category or field to which the scenario interface belongs, such as "Configuration Center" or "Input". These categories help users quickly find and filter scenario interfaces according to business needs. Type ID: used to distinguish different types of scenario interfaces, which may be a unique identifier used internally. Introduced model: represents the name of the sub-model introduced in the scenario interface. The sub-model provides data structure and business logic support for the scenario interface. Version number: records the version information of the scenario interface, which is used to distinguish different versions of the scenario interface and ensure data consistency and compatibility. Release status: indicates whether the scenario interface has been released. The release status can be "released", "unreleased", "disabled", etc., which is used to control the availability and visibility of the scenario interface.

[0077] The scene configuration interface also provides a series of control buttons for the user to manage and operate the scene interface, which can include: an add button that allows the user to create a new scene interface and input its attribute information. A modify button that allows the user to select an existing scene interface and modify its attribute information, such as changing the scene name, category, and introducing models. A delete button that allows the user to delete a scene interface that is no longer needed.

[0078] When creating or modifying a scene interface, the user needs to specify one or more sub-models as the data source or business logic support of the scene interface. These sub-models interact with the interface elements in the scene interface through specific means such as data binding, event handling, etc. After modifying or adding a scene interface, the terminal device will verify the attribute information input by the user to ensure that it meets the data type, length, and other constraint conditions, and is consistent with the introduced sub-models. After verification, the user can save the configuration information of the scene interface. In order to facilitate the user to view and verify the actual effect of the scene interface, the scene configuration interface can also provide a preview function. The user can view the layout, style, and sub-model data display effect of the scene interface by clicking the preview button.

[0079] S205, based on the format guide, the operation template configuration interface, in the operation template, select one or more sub-models of the base class model, and respectively bind a scene interface for each selected sub-model based on the sub-model scene, each sub-model corresponds to an entity.

[0080] Among them, the terminal device loads the format guide interface, which allows the user to select multiple sub-models from the sub-model list.

[0081] After the user selects the sub-model, the terminal device provides options for the user to select a scene interface from the scene list to bind each sub-model. The binding process involves associating the identifier of the sub-model with the identifier of the scene interface for subsequent use. The binding information is saved to the local storage or remote server.

[0082] For example, referring to the schematic diagram of the format guide interface shown in Figure 7 and Figure 8 , the format guide interface is provided with two tabs: the main area tab and the modal window button tab. After the user clicks the tab of the main area, the interface shown in Figure 7 is displayed. The user sets multiple sub-models on this page and binds scenes for each sub-model, i.e., configures the content and display style of the entity list. After the user clicks the modal window button tab, the interface shown in Figure 8 is displayed. The user configures the elements and display style in the list page in this interface.

[0083] S206: Setting element types and element layout for the bound scene interface, and binding the above entity input interface configuration to the specified model attributes.

[0084] For each bound scene interface, the terminal device allows the user to set the element type (such as text box, drop-down menu, etc.) and the element layout method (such as grid layout, linear layout, etc.). The user can also bind the entity input interface configuration (such as field mapping, validation rules, etc.) to the specified model attribute input box. The terminal device saves the configuration information to local storage or a remote server for use when rendering the scene interface.

[0085] In some embodiments of the present application, a data table containing data to be filtered is loaded into a data modeling or data analysis tool. The data table should contain multiple columns (fields) and rows (records), where each column represents an attribute and each row represents a data entity. Based on business needs or analysis objectives, a series of preset filtering conditions are set. These conditions can be set based on any column (field) in the data table, including but not limited to numerical ranges, text matching, date ranges, etc. The filtering conditions should be set to ensure that data rows that meet specific requirements can be accurately filtered out. Preset filtering conditions are applied to the data table. This can usually be achieved through the filtering function in the data modeling tool or data analysis software. The user simply enters or selects the corresponding filtering conditions according to the prompts, and the system automatically filters out the data rows that meet the conditions. After filtering out the data rows that meet the conditions, the user needs to further specify the model attribute input box. This typically involves the following steps: Select the columns (fields) of interest from the filtered data rows. These columns may contain data that the user needs to further analyze or manipulate. Locate the specific data row in the selected columns. This can be achieved by scrolling through the data table, using the search function, or based on specific attributes of the data row (such as date, ID, etc.). Determine the specified model attribute input box in the selected column and the located data row. The model attribute input box should contain the data value that the user needs to extract, modify or analyze.

[0086] S207 . When a user trigger action on a model attribute is detected during application runtime, an entity input interface is displayed according to the entity input interface configuration associated with the model attribute; the entity input interface includes an entity list and a list page.

[0087] When a user triggers a model attribute input box (e.g., by clicking or double-clicking), the terminal device detects this action. Based on the entity input interface configuration associated with the model attribute input box, the terminal device loads the corresponding entity input interface from local storage or a remote server. The entity input interface includes an entity list and a list page. The entity list displays available entities, and the list page is used to enter entity data. The terminal device displays the entity input interface to the user.

[0088] For example, when the user clicks the model attribute input box, it displays Figure 9 The entity input interface shown in the figure has an entity list on the left side, which includes 6 entities. Each entity corresponds to a sub-model. The right side of the entity input interface is a list page. The list page has preset input box elements, cancel elements, and confirm elements. Click different entities in the entity list to switch to different list pages.

[0089] S208: After receiving a user selection instruction for an entity in the entity list, render the corresponding element in the list page according to the pre-configured layout of the entity.

[0090] When a user selects an entity from the entity list, the terminal device receives the selection. Based on the preconfigured layout and element types for that entity, the terminal device loads the corresponding elements from local storage or a remote server. The terminal device then renders these elements on the list page so that the user can enter entity data.

[0091] S209: Input entity data in the rendered list page, and fill the entity data into the model attribute input box.

[0092] The user enters entity data in the rendered list page. The terminal device monitors the user's input and verifies the validity of the data (such as data type and format) in real time. When the user completes the input and submits the data, the terminal device fills the entity data into the model attribute input box that triggered the action.

[0093] The embodiments of the present application specifically include the following beneficial effects:

[0094] By configuring a list of base class models and their attributes, and creating sub-models based on them, data model design becomes more flexible, easily adapting to changing requirements in different business scenarios. Sub-class models inherit the attributes of the base class model, reducing the workload of repeated configuration and improving modeling efficiency.

[0095] The scenario configuration interface allows you to easily create and manage multiple scenario interfaces and bind sub-models to specific scenario interfaces, with each sub-model corresponding to an entity. This scenario-based configuration approach makes data display and interaction more intuitive and in line with business needs. Furthermore, by binding the entity input interface configuration to the model attribute input box, data input becomes dynamic and intelligent.

[0096] The user can display the corresponding entity input interface by triggering the model attribute input box, which includes an entity list and a list page, to facilitate the user to select an entity and input data. At the same time, according to the pre-configured layout mode of the entity, the corresponding elements are rendered in the list page, so that the data input process is more smooth and efficient.

[0097] After the user inputs entity data in the rendered list page, the data can be automatically filled into the corresponding model attribute input box, avoiding manual input errors and tediousness. This automated data input method not only improves work efficiency, but also ensures data accuracy and consistency.

[0098] The technical solution provides powerful support for data management in complex business scenarios through flexible data modeling, scenario-based configuration, intelligent entity input interface, and automated data filling. Whether it is data display, interaction, or input, it can meet business needs and improve data management efficiency and accuracy.

[0099] The following is an embodiment of the device of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0100] Please refer to Figure 10 , which shows the structure of the dynamic entity input device based on the low-code development platform provided by an exemplary embodiment of the present application, hereinafter referred to as device 10. The device 10 can be realized by software, hardware or a combination of the two to become all or part of a terminal device. The device 10 includes a configuration unit 1001, a selection unit 1002, a binding unit 1003, a detection unit 1004, a rendering unit 1005, and a filling unit 1006.

[0101] The configuration unit 1001 is configured to configure a base class model in a data modeling interface, wherein the base class model includes description information of the base class model.

[0102] The selection unit 1002 is configured to select a base class model in the data modeling interface, and configure attribute information for the selected base class model in a base class model configuration interface.

[0103] The configuration unit 1001 is further configured to configure a sub-model in the data modeling interface, wherein the sub-model includes attribute information of a plurality of sub-models, and the attribute information of the sub-model is inherited from the attribute information of the associated base class model.

[0104] The configuration unit 1001 is further configured to configure a scene of a sub-model in a scene configuration interface, the scene comprising format information configured by a format guide of the scene, and configure a scene of a base class model in the scene configuration interface, the scene comprising format information configured by an operation template of the format guide of the scene.

[0105] The binding unit 1003 is configured to configure an operation template of the format guide in an operation template configuration interface, select one or more sub-models of the base class model in the operation template, and bind a scene interface to each of the selected sub-models based on a scene of the sub-model, each sub-model corresponding to an entity.

[0106] The binding unit 1003 is further configured to set an element type and a layout mode of an element for the bound scene interface, and bind the entity input interface configuration to a specified model attribute.

[0107] The detection unit 1004 is configured to display an entity input interface according to an entity input interface configuration associated with a model attribute when detecting a triggering action of the model attribute by a user during an application running period; the entity input interface comprises an entity list and a list page.

[0108] The rendering unit 1005 is configured to render an element corresponding to an entity in the list page according to a layout mode pre-configured for the entity after receiving a selection instruction of the entity in the entity list by a user.

[0109] The filling unit 1006 is configured to input entity data in the rendered list page, and fill the entity data into a model attribute input box.

[0110] In one or more possible embodiments, the description information of the base class model comprises a model name, the category, a version number, and a release state, each data row in the base class model list corresponds to a base class model, and the data row is used to store the description information of the base class model; the data modeling interface further comprises an add button, a modify button, a delete button, an open button, a disable button, and a restore button.

[0111] In one or more possible embodiments, the base class model configuration interface comprises a base class model attribute list, each data row of the base class model attribute list stores attribute information of a base class model, and the attribute information comprises a project title, a project name, a project description, a data type, a reference definition, a length, a decimal place, and a field name; the base class model configuration interface is provided with an add button, an insert button, a copy button, a delete button, and a save button.

[0112] In one or more possible embodiments, each data row of the sub-model list corresponds to a word model, each sub-model is associated with an entity, and the data row stores fields inherited from the associated base class model; the attribute information of the sub-model includes: model name, belonging category, version number, and release status; the sub-model configuration interface is provided with an add button, a modify button, and a delete button.

[0113] In one or more possible embodiments, each data row of the scene list corresponds to a scene interface, and the attribute information of the scene interface includes: scene name, belonging category, type ID, introduced model, version number, and release status, the introduced model represents the name of the introduced sub-model, and the belonging category includes configuration center / inputter.

[0114] In one or more possible embodiments, a specified model attribute input box is determined in the data table according to a preset filtering condition.

[0115] In one or more possible embodiments, the entity data is subjected to data verification, and the entity data that passes the verification is filled into the model attribute input box.

[0116] It should be noted that the device 10 provided in the above embodiments, when performing the dynamic entity input method based on the low-code development platform, is only taken as an example for the division of the above functional modules, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above functions. In addition, the dynamic entity input device based on the low-code development platform and the dynamic entity input method based on the low-code development platform provided in the above embodiments belong to the same concept, and the implementation process is detailed in the method embodiments, which will not be repeated here.

[0117] The serial numbers of the above embodiments of the present application are only for description, and do not represent the advantages or disadvantages of the embodiments.

[0118] The embodiments of the present application also provide a computer storage medium, which can store a plurality of instructions, the instructions being suitable for being loaded and executed by a processor to implement the method steps of the method embodiments as shown in the above Figure 2 The specific implementation process can be referred to the specific description of the embodiments as shown in Figure 2 Here, no further description is given.

[0119] The present application also provides a computer program product, which stores at least one instruction, the at least one instruction being loaded and executed by the processor to implement the dynamic entity input method based on the low-code development platform as described in each of the above embodiments.

[0120] Please refer to Figure 11, provides a schematic diagram of the structure of a terminal device according to an embodiment of the present application. Figure 11 As shown, the terminal device 1100 may include: at least one processor 1101 , at least one network interface 1104 , a user interface 1103 , a memory 1105 , and at least one communication bus 1102 .

[0121] The communication bus 1102 is used to implement the connection and communication between these components.

[0122] The user interface 1103 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 1103 may also include a standard wired interface and a wireless interface.

[0123] The network interface 1104 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0124] The processor 1101 may include one or more processing cores. The processor 1101 utilizes various interfaces and circuits to connect various components within the entire terminal device 1100. It executes various functions and processes data for the terminal device 1100 by running or executing instructions, programs, code sets, or instruction sets stored in the memory 1105, as well as accessing data stored in the memory 1105. Optionally, the processor 1101 may be implemented using at least one hardware form selected from the group consisting of a digital signal processing (DSP), a field-programmable gate array (FPGA), and a programmable logic array (PLA). The processor 1101 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU primarily processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content displayed on the display screen; and the modem handles wireless communications. It is understood that the modem may not be integrated into the processor 1101 and may be implemented as a separate chip.

[0125] Among them, the memory 1105 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 1105 includes a non-transitory computer-readable storage medium. The memory 1105 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1105 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 1105 may also be optionally at least one storage device located away from the aforementioned processor 1101. As Figure 11 As shown, the memory 1105 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program.

[0126] exist Figure 11 In the terminal device 1100 shown, the user interface 1103 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 1101 can be used to call the application stored in the memory 1105 and specifically execute the following Figure 2 The specific process can be referred to the method shown in Figure 2 As shown, no further details are given here.

[0127] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory, or a random access memory.

[0128] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A dynamic entity input method based on a low-code development platform, characterized in that: include: Configure a base class model on the data modeling interface. The base class model includes description information of the base class model, including model name, category, version number, and release status. Each data row in the base class model list corresponds to a base class model, and the data row is used to store the description information of the base class model. The data modeling interface also includes a add button, a modify button, a delete button, an open button, a disable button, and a restore button. Selecting a base class model in the data modeling interface, and configuring attribute information for the selected base class model in the base class model configuration interface; A submodel is configured on the data modeling interface. The submodel includes: attribute information of multiple submodels, which is inherited from the attribute information of the associated base class model; a submodel list is displayed on the submodel configuration interface, where each data row in the submodel list corresponds to a submodel, each submodel is associated with an entity, and the fields stored in the data row are inherited from the associated base class model; the attribute information of the submodel includes: model name, category, version number, and release status; the submodel configuration interface is provided with a add button, a modify button, and a delete button; Configuring a sub-model scene in the scene configuration interface, wherein the scene includes format information configured by a format wizard for multiple scenes; configuring a base class model scene in the scene configuration interface, wherein the scene includes format information configured by an operation template of the format wizard; An operation template configuration interface based on a format wizard, in which one or more sub-models that inherit the base class model are selected, and a scene interface is bound to each selected sub-model based on the sub-model scene, with each sub-model corresponding to an entity; Set the element type and layout for the bound scene interface, and bind the entity input interface configuration to the specified model attribute; When a user triggers a model attribute during application runtime, an entity input interface is displayed according to the entity input interface configuration associated with the model attribute; the entity input interface includes an entity list and a list page; After receiving a user selection instruction for an entity in the entity list, rendering a corresponding element in the list page according to a pre-configured layout mode of the entity; Enter entity data in the rendered list page and fill the entity data into the model attribute input box.

2. The method according to claim 1, characterized in that The base class model configuration interface includes: a base class model attribute list, each data row in the base class model attribute list stores the attribute information of a base class model, and the attribute information includes: project title, project name, project description, data type, reference definition, length, decimal places and field name; the base class model configuration interface is provided with a new button, an insert button, a copy button, a delete button and a save button.

3. The method according to claim 1, characterized in that Each data row in the scene list corresponds to a scene interface. The attribute information of the scene interface includes: scene name, category, type ID, introduced model, version number and release status. The introduced model indicates the name of the introduced sub-model, and the category indicates the category of the introduced model.

4. The method according to claim 3, characterized in that Determines the specified model attributes in the data table based on the preset filter conditions.

5. The method according to claim 1, wherein Perform data verification on the entity data and fill the verified entity data into the model attribute input box.

6. A dynamic entity input device based on a low-code development platform, characterized in that: include: A configuration unit is configured to configure a base class model in a data modeling interface, wherein the base class model includes description information of the base class model, including model name, category, version number, and release status. Each data row in the base class model list corresponds to a base class model, and the data row is used to store the description information of the base class model. The data modeling interface also includes a add button, a modify button, a delete button, an open button, a deactivate button, and a restore button. A selection unit, configured to select a base class model in the data modeling interface, and configure attribute information for the selected base class model in the base class model configuration interface; The configuration unit is further configured to configure a sub-model on the data modeling interface, wherein the sub-model includes: attribute information of multiple sub-models, wherein the attribute information of the sub-model is inherited from the attribute information of the associated base class model; a sub-model list is displayed on the sub-model configuration interface, wherein each data row in the sub-model list corresponds to a sub-model, each sub-model is associated with an entity, and the fields stored in the data row are inherited from the associated base class model; the attribute information of the sub-model includes: model name, category, version number, and release status; and the sub-model configuration interface is provided with a add button, a modify button, and a delete button; The configuration unit is further configured to configure a scene of a sub-model on a scene configuration interface, wherein the scene includes format information of multiple scenes configured based on a format wizard, and to configure a scene of a base class model on a scene configuration interface, wherein the scene includes format information of the scene configured based on an operation template of the format wizard; A binding unit configured to configure an interface based on an operation template of a format wizard, wherein one or more sub-models that inherit a base class model are selected in the operation template, and a scene interface is bound to each selected sub-model based on a sub-model scene, wherein each sub-model corresponds to an entity; The binding unit is further used to set the element type and element layout for the bound scene interface, and to bind the entity input interface configuration with the specified model attribute; A detection unit, configured to detect a user triggering an action on a model attribute during application runtime and display an entity input interface according to an entity input interface configuration associated with the model attribute; the entity input interface includes an entity list and a list page; a rendering unit, configured to, after receiving a user's selection instruction for an entity in the entity list, render a corresponding element in the list page according to a pre-configured layout of the entity; The filling unit is used to enter entity data in the rendered list page and fill the entity data into the model attribute input box.

7. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, which are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 5.

8. A terminal device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps according to any one of claims 1 to 5.

Images