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

Abstract

The embodiment of the invention discloses a dynamic entity input method and device based on a low-code development platform, a storage medium and terminal equipment, and relates to the field of data processing. According to the method, the base class model and the attribute information of the base class model are constructed, and the subclass models are created, so that the flexibility and adaptability of the data model are enhanced, the business scene demand change is effectively dealt with, the repeated configuration is reduced, and the modeling efficiency is improved. By means of a scene and reference operation template configuration interface, a scene where a plurality of sub-class models are operated on one interface can be easily created and managed, the sub-models are bound with a specific scene, and visual display and interaction of data are achieved. By binding entity input interface configuration and model attributes, dynamic and intelligent data input in the operation period is realized, and a user can select and input data by triggering an attribute input box to display an entity input interface. And after being input, the data are automatically filled into the corresponding input box, so that the working 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, device, storage medium and terminal device based on a low-code development platform. Background Art

[0002] In the field of modern software development, low-code development platforms, with their graphical interface and simple configuration advantages, have become a key tool for improving development efficiency and lowering technical barriers. These platforms enable developers to quickly create applications through intuitive configuration without in-depth coding. However, although low-code platforms have performed well in simplifying the development process, they still face significant challenges when dealing with complex and changing business needs.

[0003] Traditional low-code platforms are mainly designed to support the configuration of single entity pages, which is insufficient in providing users with an intuitive and coherent data operation experience. Since the core goal of low-code platforms is to simplify development and lower barriers to entry, their original design did not fully consider the needs of dynamic interactions and complex layouts between multiple entities. Therefore, when business needs involve the interaction and complex layout of multiple entities, the graphical interface and configuration methods of low-code platforms often seem inadequate.

[0004] This limitation forces developers to perform additional programming work to compensate for the configuration deficiencies of low-code platforms when dealing with dynamic interactions among multiple entities. This not only goes against the original intention of low-code platforms to reduce coding work, but also increases the burden on developers and reduces development efficiency. Therefore, how to solve the limitations of low-code platforms in dealing with complex business needs while maintaining their ease of use has become an urgent problem to be solved in the current low-code development field. Summary of the invention

[0005] The embodiments of the present application provide a dynamic entity input method, device, storage medium and terminal device based on a low-code development platform, which can solve the problem of low development efficiency of entity input under a 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] Configure 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] Configuring a sub-model in the data modeling interface, the sub-model comprising: attribute information of a plurality of sub-models, the attribute information of the sub-model being inherited from the attribute information of the associated base class model;

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

[0011] An operation template configuration interface based on a format wizard, in which 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, and each sub-model corresponds to an entity;

[0012] Set the element type and layout mode for the bound scene interface, and bind the above entity input interface configuration to the specified model attribute;

[0013] When a user triggers a certain 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;

[0014] After receiving a user's 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;

[0015] Enter entity data in the rendered list page and fill the entity data into the model attribute input box.

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

[0017] A configuration unit, used to configure a base class model in a data modeling interface, wherein the base class model includes description information of the base class model;

[0018] A selection unit, used 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;

[0019] The configuration unit is further used to configure a sub-model in the data modeling interface, wherein the sub-model includes: attribute information of a plurality of sub-models, wherein the attribute information of the sub-model is attribute information inherited from an associated base class model;

[0020] The configuration unit is further used to configure a scene of a sub-model on a scene configuration interface, wherein the scene includes format information configured by a plurality of scenes 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 configured by an operation template of a format wizard;

[0021] A binding unit, configured to configure an operation template interface based on 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 respectively 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 the layout mode of the element 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 display an entity input interface according to an entity input interface configuration associated with the model attribute when detecting a user's triggering action on a model attribute during application runtime; the entity input interface includes an entity list and a list page;

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

[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 brought about by the technical solutions provided by some embodiments of the present application include at least:

[0029] By configuring the base class model list and its attribute information, and creating sub-models based on the base class model, the data model design is more flexible and can easily cope with the changing needs of different business scenarios. The sub-class model inherits the attribute information of the base class model, which reduces the workload of repeated configuration and improves modeling efficiency.

[0030] Through the scenario configuration interface, you can 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 method makes data display and interaction more intuitive and in line with business needs. At the same time, through the binding of the entity input interface configuration and the model attribute input box, data input is dynamic and intelligent.

[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, making it easy for users to select entities and enter data. At the same time, the corresponding elements are rendered in the list page according to the pre-configured layout of the entity, making the data input process smoother and more efficient.

[0032] After the user enters entity data in the rendered list page, the data can be automatically filled into the corresponding model attribute input box, avoiding the 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, scenario-based configuration, intelligent entity input interface and automatic data filling. Whether it is data display, interaction or input, it can meet business needs and improve the efficiency and accuracy of data management. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

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

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

[0037] Figure 3 is a schematic diagram of a data modeling interface provided in an embodiment of the present application;

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

[0039] Figure 5 is a schematic diagram of a sub-model configuration interface provided in an embodiment 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 a format wizard interface provided in an embodiment of the present application;

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

[0043] Fig.10 It is a structural diagram of a dynamic entity input device based on a low-code development platform provided by the present application;

[0044] Fig.11 It is a structural schematic 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 more clear, the embodiments of the present application will be further described in 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, and the network 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: a wired communication link includes an optical fiber, a twisted pair or a coaxial cable, etc., and a wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or a microwave communication link, etc.

[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, which is not specifically limited here.

[0048] Various communication client applications can be installed on the terminal device of the present 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 smart phones, tablet computers, laptops, and desktop computers. 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: used to provide distributed services), or it can be implemented 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 may be installed thereon. The display device may be any device capable of realizing a display function, and the camera is used to collect video streams; for example, the display device may 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), etc. The user may use the display device on the terminal device to view displayed text, pictures, videos and other information.

[0051] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be used as required.

[0052] The following will be combined with the attached Figure 2 , the dynamic entity input method based on the low-code development platform provided in the embodiment of the present application is described in detail. Among them, the dynamic entity input device based on the low-code development platform in the embodiment of the present application can be Figure 1 The terminal device shown.

[0053] See also Figure 2 , which is a flowchart of a dynamic entity input method based on a low-code development platform, provided in the embodiment of the present application. Figure 2 As shown, the method of the embodiment of the present application may include the following steps:

[0054] S201. Configure the base class model in the data modeling interface.

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

[0056] In some embodiments of the present 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 the model to 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 model name, category, version number, and release status.

[0058] Interface control buttons: The data modeling interface also provides a series of control buttons to enable 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. Deactivate button: allows users to set a published base class model to a deactivated state, making it no longer available. Restore button: allows users to restore a deactivated base class model to an available state. Display a list of base class models: based on the above information, the terminal device displays the base class models and their description information in a list in the specified 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 the base class model list. The terminal device responds to the user's selection and jumps to the base class model configuration interface. In the base class model configuration interface, the terminal device provides input fields and options to allow the user to configure attribute information for the selected base class model, such as attribute name, data type, default value, etc. 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 the present application, see Figure 4 The schematic diagram of the base class model configuration interface shown in FIG. 1 shows that in the base class model list, the user selects a specific base class model for attribute configuration. The terminal device responds to the user's selection and loads the base class model configuration interface. The interface is specifically used to configure and manage the attribute information 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 in the list corresponds to an attribute, and 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 target model or entity of the reference 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 field name 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 their 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 on the data row or related edit control in the property list. The terminal device will update the interface in real time to reflect the user's changes.

[0065] Verify attribute information: Before saving the attribute information, the terminal device will verify the attribute information entered by the user to ensure that it meets the constraints such as data type, length, decimal places, etc. If the verification 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] Among them, the terminal device loads the sub-model configuration interface, which provides an area for displaying the sub-model list. For each sub-model, the terminal device inherits its attribute information according to 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 or business object in a database). After the configuration is completed, the sub-model list and its attribute information are saved to local storage or a remote server.

[0068] In some embodiments of the present application, see Figure 5 The sub-model configuration interface shown in the figure, 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 used to display and manage the sub-model list. 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 model, so the fields stored in its data rows are mostly inherited from the associated base model. These fields include all the properties of the base model, but the sub-model can also add or override specific properties.

[0070] In addition to the properties inherited from the base model, the sub-model also has its own property information, including: Model name: a name used to uniquely identify the sub-model. Category: indicates the category 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, which is used to distinguish different versions of sub-models to ensure data consistency and compatibility. Release status: indicates whether the sub-model has been released. The release status can be "released", "unreleased", "disabled", etc., which is 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 for 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 enter its unique attribute information. Modify button: allows users to select an existing sub-model and modify its attribute information, including adding or overwriting 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 sub-model, the user needs to specify an entity to associate with the sub-model. This entity can be a table in the database, a business object, or any other data structure that can be recognized and processed by the system. After modifying or adding a sub-model, the terminal device will verify the attribute information entered by the user to ensure that it meets the constraints such as data type and length, and is consistent with the associated base class model. After verification, the user can save the configuration information of the sub-model.

[0073] S204. Configure the scene of the sub-model in the scene configuration interface, where the scene includes format information configured by the format wizard for multiple scenes. Configure the scene of the base class model in the scene configuration interface, where the scene includes format information configured by the operation template of the format wizard for the scene.

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

[0075] In some embodiments of the present application, see Figure 6 The schematic diagram of the scene configuration interface shown in the figure, the user enters the scene configuration interface through navigation or menu, and the 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 attribute information of the scene interface, which is used to describe the basic characteristics and configuration of the scene interface.

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

[0077] The scene configuration interface also provides a series of control buttons for users to manage and operate the scene interface. These buttons may include: Add button: allows users to create a new scene interface and enter its attribute information. Modify button: allows users to select an existing scene interface and modify its attribute information, such as changing the scene name, category, and model. Delete button: allows users 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 for the scene interface. These sub-models interact with interface elements in the scene interface through specific methods (such as data binding, event handling, etc.). After modifying or adding a scene interface, the terminal device will verify 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 introduced sub-model. After verification, the user can save the configuration information of the scene interface. In order to facilitate users to view and verify the actual effect of the scene interface, the scene configuration interface may also provide a preview function. Users can view the layout, style and display effect of sub-model data of the scene interface by clicking the preview button.

[0079] S205, configuring an operation template interface based on the format wizard, in which one or more sub-models that inherit the 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, and each sub-model corresponds to an entity.

[0080] The terminal device loads a format wizard interface, which allows the user to select multiple sub-models from a sub-model list.

[0081] After the user selects a sub-model, the terminal device provides the option 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 use in subsequent steps. The binding information is saved to local storage or a remote server.

[0082] For example, see Figure 7 and Figure 8 The schematic diagram of the format wizard interface shown in the figure has two tabs: the main area tab and the modal window button tab. After the user clicks the tab in the main area, the Figure 7 The interface shown in the figure shows that the user can set multiple sub-models on this page and bind scenes to each sub-model, that is, configure the content and display style of the entity list. After the user clicks the modal window button tab, the Figure 8 An interface in which users configure the elements and display styles in the list page.

[0083] S206: Setting element types and element layout methods for the bound scene interface, and binding the above entity input interface configuration with 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 layout of the element (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 in a data modeling or data analysis tool. The data table should contain multiple columns (fields) and rows (records), wherein each column represents an attribute and each row represents a data entity. A series of preset filtering conditions are set according to business needs or analysis objectives. These conditions can be set based on any column (field) in the data table, including but not limited to numerical range, text matching, date interval, etc. The setting of the filtering conditions should ensure that the data rows that meet specific requirements can be accurately filtered out. Preset filtering conditions are applied in the data table. This can usually be achieved through the filtering function in the data modeling tool or data analysis software. The user only needs to enter or select the corresponding filtering conditions according to the prompts, and the system can automatically filter out the data rows that meet the conditions. After filtering out the data rows that meet the conditions, the user needs to further determine the specified model attribute input box. This usually 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 analyze or operate in depth. Locate a specific data row in the selected column. This can be achieved by scrolling the data table, using the search function, or according to the 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 triggering 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 (such as clicking or double-clicking), the terminal device detects this action. According to the entity input interface configuration associated with the model attribute input box, the terminal device loads the corresponding entity input interface from the local storage or remote server. The entity input interface includes an entity list and a list page, wherein the entity list displays available entities and the list page is used to input 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, the Fig. 9 The entity input interface shown in the figure has an entity list on the left side, including 6 entities, each entity corresponds to a sub-model, and a list page on the right side of the entity input interface. 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's 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] After the user selects an entity from the entity list, the terminal device receives the selection instruction. According to the pre-configured layout mode and element type of the entity, the terminal device loads the corresponding element from the local storage or remote server. The terminal device renders these elements in 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 action and verifies the validity of the data (such as data type, format, etc.) 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 triggers the action.

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

[0094] By configuring the base class model list and its attribute information, and creating sub-models based on the base class model, the data model design is more flexible and can easily cope with the changing needs of different business scenarios. The sub-class model inherits the attribute information of the base class model, which reduces the workload of repeated configuration and improves modeling efficiency.

[0095] Through the scenario configuration interface, you can 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 method makes data display and interaction more intuitive and in line with business needs. At the same time, through the binding of the entity input interface configuration and the model attribute input box, data input is dynamic and intelligent.

[0096] Users can trigger the model attribute input box to display the corresponding entity input interface, which includes an entity list and a list page, making it easy for users to select entities and enter data. At the same time, the corresponding elements are rendered in the list page according to the pre-configured layout of the entity, making the data input process smoother and more efficient.

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

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

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

[0100] See also Fig.10 , which shows a schematic diagram of the structure of a dynamic entity input device based on a low-code development platform provided by an exemplary embodiment of the present application, hereinafter referred to as device 10. The device 10 can be implemented as all or part of a terminal device through software, hardware, or a combination of both. 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] A configuration unit 1001 is used 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] A selection unit 1002, 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;

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

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

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

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

[0107] The detection unit 1004 is used to detect the trigger action of the user on a certain model attribute during the application running period, and display the entity input interface according to the entity input interface configuration associated with the model attribute; the entity input interface includes an entity list and a list page;

[0108] The rendering unit 1005 is used to render corresponding elements in the list page according to the pre-configured layout mode of the entity after receiving a user's selection instruction for an entity in the entity list;

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

[0110] In one or more possible embodiments, the description information of the base class model includes: 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.

[0111] In one or more possible embodiments, the base class model configuration interface includes: a base class model attribute list, each data row in the base class model attribute list stores 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 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 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; the sub-model configuration interface is provided with a 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, category, type ID, import model, version number and release status. The import model represents the name of the introduced sub-model, and the categories include 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, data verification is performed on the entity data, and the entity data that passes the verification is filled into the model attribute input box.

[0116] It should be noted that when the device 10 provided in the above embodiment executes the dynamic entity input method based on the low-code development platform, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above-mentioned functions. In addition, the dynamic entity input device based on the low-code development platform provided in the above embodiment and the dynamic entity input method embodiment based on the low-code development platform belong to the same concept. The implementation process is detailed in the method embodiment, which will not be repeated here.

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

[0118] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 2 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 2 The specific description of the illustrated embodiment will not be repeated here.

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

[0120] See also Fig.11, which is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Fig.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 realize the connection and communication between these components.

[0122] The user interface 1103 may include a display screen (Display) and a camera (Camera), and the optional 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] Among them, the processor 1101 may include one or more processing cores. The processor 1101 uses various interfaces and lines to connect the various parts of the entire terminal device 1100, and executes various functions and processes data of the terminal device 1100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1105, and calling data stored in the memory 1105. Optionally, the processor 1101 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 1101 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1101, and it can be implemented separately through a 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 Fig.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 Fig.11 In the terminal device 1100 shown in FIG. 1 , 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 steps: Figure 2 The specific process can be referred to Figure 2 As shown, no further description is given here.

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

[0128] The above disclosure is only the preferred embodiment of the present application, which 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 in a data modeling interface, wherein the base class model includes description information of the base class model; 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; Configuring a sub-model in the data modeling interface, the sub-model comprising: attribute information of a plurality of sub-models, the attribute information of the sub-model being inherited from the attribute information of the associated base class model; Configure a scene of a sub-model in a scene configuration interface, wherein the scene includes format information configured by a plurality of scenes based on a format wizard, and configure a scene of a base class model in a scene configuration interface, wherein the scene includes format information configured by an operation template of a format wizard; An operation template configuration interface based on a format wizard, in which 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, and each sub-model corresponds to an entity; Set the element type and layout mode for the bound scene interface, and bind the above entity input interface configuration to the specified model attribute; When a user triggers a certain 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's 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 description information of the base class model includes: 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 new button, a modify button, a delete button, an open button, a disable button and a restore button.

3. The method according to claim 1 or 2, 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 add button, an insert button, a copy button, a delete button and a save button.

4. The method according to claim 3, characterized in that 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; the sub-model configuration interface is provided with a add button, a modify button, and a delete button.

5. The method according to claim 1, 2 or 4, 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 represents the name of the introduced sub-model, and the category represents the category of the introduced model.

6. The method according to claim 5, characterized in that Determine the specified model attributes in the data table based on the preset filter conditions.

7. The method according to claim 1 or 2 or 4 or 5, characterized in that: Perform data verification on the entity data and fill the verified entity data into the model attribute input box.

8. A dynamic entity input device based on a low-code development platform, characterized in that: include: A configuration unit, used to configure a base class model in a data modeling interface, wherein the base class model includes description information of the base class model; A selection unit, used 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 used to configure a sub-model in the data modeling interface, wherein the sub-model includes: attribute information of a plurality of sub-models, wherein the attribute information of the sub-model is attribute information inherited from an associated base class model; The configuration unit is further used to configure a scene of a sub-model on a scene configuration interface, wherein the scene includes format information configured by a plurality of scenes 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 configured by an operation template of a format wizard; A binding unit, configured to configure an operation template interface based on 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 respectively bound to each selected sub-model based on the sub-model scene, wherein each sub-model corresponds to an entity; The binding unit is further used to set the element type and the layout mode of the element for the bound scene interface, and to bind the above entity input interface configuration with the specified model attribute; A detection unit, configured to display an entity input interface according to an entity input interface configuration associated with the model attribute when detecting a user's triggering action on a model attribute during application runtime; the entity input interface includes an entity list and a list page; A rendering unit, configured to render corresponding elements in a list page according to a pre-configured layout of the entity after receiving a user's selection instruction for an entity in the entity list; 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.

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

10. 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 as claimed in any one of claims 1 to 7.

Images