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

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 terminal equipment, and relates to the field of data processing. According to the application, the base class model and the attribute information thereof are constructed, and the sub-class model is created, so that the flexibility and the adaptability of the data model are enhanced, the change of the service scene requirement is effectively treated, the repeated configuration is reduced, and the modeling efficiency is improved. By means of the scene and the reference operation template configuration interface, the scene in which a plurality of sub-model operations are carried out on one interface can be easily created and managed, the sub-model is bound with a specific scene, and visual display and interaction of data are achieved. The entity input interface configuration and the model attribute are bound, so that the dynamic and intelligent operation period data input is realized, and a user can display the entity input interface, select and input data by triggering the attribute input box. After data is input, the data is automatically filled into the corresponding input frame, so that the working efficiency is improved, and the data accuracy is ensured.

Description

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

Technical Field

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

In the field of modern software development, a low-code development platform is a key tool for improving development efficiency and reducing technical thresholds by virtue of a graphical interface and simple configuration of the low-code development platform. These platforms enable developers to quickly create applications without deep coding, but in an intuitive configuration. However, while low code platforms perform well in simplifying development flows, significant challenges remain in dealing with complex and varied business requirements.

Conventional low-code platforms are designed primarily to support configuration of single entity pages, which is deficient in providing users with an intuitive and consistent data manipulation experience. Since the core goal of low code platforms is to simplify development and lower thresholds, their original design does not adequately take into account the requirements of dynamic interactions and complex layouts among multiple entities. Thus, when business requirements involve interactions and complex layouts of multiple entities, the graphical interfaces and configuration of low-code platforms tend to be frustrating.

This limitation results in the developer having to do additional programming work to make up for the shortfall in configuration of the low code platform when handling multi-entity dynamic interactions. This not only violates the original purpose of the low code platform to reduce the encoding work, but also increases the burden on the developer and reduces the development efficiency. Therefore, how to solve the limitation of processing complex service requirements while maintaining the usability of a low-code platform is a problem to be solved in the current low-code development field.

Disclosure of Invention

The embodiment of the application provides a dynamic entity input method, a device, a storage medium and terminal equipment based on a low-code development platform, which can solve the problem of low development efficiency of realizing entity input under the low-code platform in the prior art. The technical scheme is as follows:

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

configuring a base model on a data modeling interface, wherein the base model comprises description information of the base model;

Selecting a base model from the data modeling interface, and configuring attribute information for the selected base model at a base model configuration interface;

Configuring sub-models in the data modeling interface, wherein the sub-models comprise attribute information of a plurality of sub-models, and the attribute information of the sub-models is the attribute information inherited from an associated base class model;

Configuring scenes of the sub-model at a scene configuration interface, wherein the scenes comprise format information configured by a plurality of scenes based on format guidance, and configuring scenes of the base class model at the scene configuration interface, and the scenes comprise format information configured by the scenes based on an operation template of the format guidance;

An operation template configuration interface based on format guidance, wherein one or more sub-models of an inheritance base class model are selected in the operation template, a scene interface is respectively bound for each selected sub-model based on the sub-model scene, and each sub-model corresponds to an entity;

Setting element types and element layout modes for the bound scene interfaces, and binding the configuration of the entity input interface with the designated model attributes;

when detecting trigger action of a user on a certain model attribute in an application running period, configuring and displaying an entity input interface according to an entity input interface associated with the model attribute, wherein the entity input interface comprises an entity list and a list page;

after receiving a selection instruction of a user for a certain entity in the entity list, rendering a corresponding element in a list page according to a layout mode preset by the entity;

inputting entity data in the rendered list page, and filling the entity data into the model attribute input box.

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

the configuration unit is used for configuring a base model at the data modeling interface, wherein the base model comprises description information of the base model;

The selection unit is used for selecting a base model in the data modeling interface and configuring attribute information for the selected base model in the base model configuration interface;

The configuration unit is further used for configuring a sub-model on the data modeling interface, wherein the sub-model comprises attribute information of a plurality of sub-models, and the attribute information of the sub-model is the attribute information inherited from the associated base class model;

The configuration unit is further used for configuring scenes of the sub-model in the scene configuration interface, wherein the scenes comprise format information configured by a plurality of scenes based on format guidance, and the scenes of the base class model are configured in the scene configuration interface, and the scenes comprise format information configured by the scenes based on an operation template of the format guidance;

the binding unit is used for configuring an interface based on an operation template of the format guide, selecting one or more sub-models of the inheritance base class model in the operation template, and binding a scene interface for each selected sub-model based on the sub-model scene, wherein each sub-model corresponds to an entity;

the binding unit is further configured to set element types and element layout modes for the bound scene interfaces, and bind the configuration of the entity input interface with the designated model attribute;

The detection unit is used for configuring and displaying an entity input interface according to the entity input interface associated with a certain model attribute when the trigger action of a user on the model attribute is detected in the application running period;

the rendering unit is used for rendering corresponding elements in a list page according to a layout mode pre-configured by the entity after receiving a selection instruction of a user for a certain entity in the entity list;

And the filling unit is used for inputting entity data in the rendered list page and filling the entity data into the model attribute input box.

In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-described method steps.

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 adapted to be loaded by the processor and to perform the above-mentioned method steps.

The technical scheme provided by the embodiments of the application has the beneficial effects that at least:

by configuring the base class model list and the attribute information thereof and creating the sub-model based on the base class model, the design of the data model is more flexible, and the requirement change of different business scenes can be easily dealt with. The subclass model inherits the attribute information of the base class model, reduces the workload of repeated configuration, and improves the modeling efficiency.

Through the scene configuration interface, a plurality of scene interfaces can be conveniently created and managed, and the sub-models are bound with a specific scene interface, and each sub-model corresponds to one entity. The scene configuration mode ensures that the data display and interaction are more visual and meet the service requirement, and simultaneously realizes the dynamic and intelligent data input through the binding of the entity input interface configuration and the model attribute input box.

The user can display a corresponding entity input interface through triggering a model attribute input box, and the interface comprises an entity list and a list page, so that the user can conveniently select an entity and input data. Meanwhile, corresponding elements are rendered in the list page according to a layout mode pre-configured by the entity, so that the data input process is smoother and more efficient.

After the user inputs entity data in the rendered list page, the data can be automatically filled into the corresponding model attribute input box, so that errors and complexity of manual input are avoided. The automatic data input mode not only improves the working efficiency, but also ensures the accuracy and consistency of data.

According to the technical scheme, powerful support is provided for data management under complex service scenes through flexible data modeling, scene configuration, intelligent entity input interfaces and automatic data filling. Whether data is displayed, interacted or input, the business requirement can be met, and the efficiency and accuracy of data management are improved.

Drawings

In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present application;

FIG. 2 is a flow chart of a dynamic entity input method based on a low-code development platform according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a data modeling interface provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a base class model configuration interface provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a submodel configuration interface provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a scene configuration interface provided by an embodiment of the application;

FIGS. 7 and 8 are diagrams of format wizard interfaces provided by embodiments of the present application;

FIG. 9 is a schematic diagram of a physical input interface provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of a dynamic entity input device based on a low-code development platform according to the present application;

fig. 11 is a schematic structural diagram of a terminal device provided by the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings.

As shown in fig. 1, the system architecture may include a terminal device 101 and a server 102. The communication between the terminal device 101 and the server 102 may be performed through a network for the medium providing the communication link between the above-mentioned respective units. The network may include various types of wired or wireless communication links, such as wired communication links including fiber optic, twisted pair, or coaxial cables, etc., wireless communication links including Bluetooth communication links, wireless fidelity (WIreless-FIdelity, wi-Fi) communication links, or microwave communication links, etc.

The terminal device 101 and the server 102 may be hardware or software. When the terminal apparatus 101 and the server 102 are hardware, they may be realized as a distributed server cluster composed of a plurality of servers, or as a single server. When the terminal device 101 and the server 102 are software, they may be implemented as a plurality of software or software modules (for example, to provide distributed services), or may be implemented as a single software or software module, which is not particularly limited herein.

Various communication client applications, such as a video recording application, a video playing application, a voice interaction application, a search application, an instant messaging tool, a mailbox client, social platform software and the like, can be installed on the terminal equipment.

The terminal device may be hardware or software. When the terminal device is hardware, it may be various terminal devices with a display screen including, but not limited to, smartphones, tablet computers, laptop and desktop computers, and the like. When the terminal device is software, the terminal device may be installed in the above-listed terminal device. Which may be implemented as multiple software or software modules (e.g., to provide distributed services), or as a single software or software module, without limitation.

When the terminal device is hardware, a display device and a camera can be mounted on the terminal device, the display device can be various devices capable of realizing display functions, and the camera is used for collecting video streams, for example, the display device can be a cathode-ray tube display (cathode ray tube display, CR for short), a light-emitting diode display (light-emitting diode display, LED for short), an electronic ink screen, a liquid crystal display (liquid CRYSTAL DISPLAY, LCD for short), a plasma display panel (PLASMA DISPLAYPANEL, PDP for short) and the like. The user can view the displayed text, picture, video and other information by using the display device on the terminal device.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. Any number of terminal devices, networks, and servers may be used as desired for implementation.

The dynamic entity input method based on the low-code development platform provided by the embodiment of the application is described in detail below with reference to fig. 2. The dynamic entity input device based on the low-code development platform in the embodiment of the application may be the terminal device shown in fig. 1.

Referring to fig. 2, a flow chart of a dynamic entity input method based on a low-code development platform is provided for an embodiment of the present application. As shown in fig. 2, the method according to the embodiment of the present application may include the following steps:

s201, configuring a base class model at a data modeling interface.

The terminal equipment firstly loads a data modeling interface, and the interface provides a region for displaying a base class model list. The terminal device reads description information of the base class model from a local storage or a remote server, and the information includes model names, attribute structures and the like. The terminal equipment displays the description information in a specified area of the data modeling interface in a list form for a user to select and view.

In some embodiments of the present application, referring to the schematic diagram of the data modeling interface shown in fig. 3, the terminal device loads the data modeling interface that provides a region dedicated to exposing and managing the base class model list. Description information of base class model includes, but is not limited to, model name, name for uniquely identifying the base class model. And the classification indicates the classification or the field to which the base class model belongs, and is helpful for users to quickly search and screen the model according to the classification. Version number, recording version information of the base class model, which is used for distinguishing models of different versions and ensuring consistency and compatibility of data. The publishing status, which indicates whether the base class model has been published, may be "published", "unpublished", "deactivated", etc., for controlling the availability and visibility of the model.

The data rows correspond to base class models, and each data row corresponds to one base class model in the base class model list. The data line is used for storing and displaying description information of the base class model, including model names, categories, version numbers, release states and the like.

Interface control buttons the data modeling interface also provides a series of control buttons for the user to manage and operate the base class model, including a new button that allows the user to create a new base class model and enter its description information.

And modifying the button, namely allowing the user to select the existing base class model and modifying the description information of the base class model. Delete button-allow the user to delete base class models that are no longer needed. Opening button-allow the user to open and view detailed information or configuration of the published base class model. And a disable button, which allows the user to set the published base model to a disable state so that the published base model is not available any more. And a restore button for allowing the user to restore the deactivated base model to an available state. And displaying the base model list by the terminal equipment according to the information, and displaying the base model and the description information thereof in a list form in a designated area of a data modeling interface. The user can quickly find and locate the required base class model by means of scrolling, screening or searching.

S202, selecting a base model in the data modeling interface, and configuring attribute information for the selected base model in the base model configuration interface.

Wherein the user selects a base class model from the list of base class models. And the terminal equipment responds to the selection of the user and jumps to the base class model configuration interface. In the base class model configuration interface, the terminal device provides input fields and options that allow the user to configure attribute information, such as attribute names, data types, default values, etc., for the selected base class model. After the user completes configuration, the terminal device stores the configuration information to a local storage or a remote server.

In some embodiments of the present application, referring to the schematic diagram of the base class model configuration interface shown in fig. 4, in the base class model list, the user selects a specific base class model for attribute configuration. And the terminal equipment responds to the selection of the user and loads the base class model configuration interface. The interface is dedicated to configuring and managing attribute information of the selected base class model.

In the base class model configuration interface, there is a base class model attribute list for displaying and editing attribute information of a selected base class model. Each data line corresponds to an attribute in the list, and the attribute information stored in the data line comprises an item title, a short title or a label of the attribute, and the short title or the label is used for identifying the attribute on the interface. Item name-formal name of attribute, used to uniquely identify the attribute in a code or database. Item description, the detailed description of the attribute, the description of the purpose, constraint condition or business logic, etc. Data type, data type of attribute, such as integer, floating point number, character string, date, etc. Reference definition a referenced target model or entity is defined herein if the attribute is a reference to another model or entity. Length-for the attribute of the string type, its maximum length is specified. Decimal place for the attribute of the value type, the number of bits of its decimal part is specified. Field name-field name used to store the attribute in a database or code.

Interface control buttons-the base class model configuration interface also provides a series of control buttons for the user to manage and operate the attributes, including a new button to allow the user to add new attributes in the attribute list and to input their attribute information. Insert button-allow the user to insert a new attribute before the currently selected attribute. Copy button-allow the user to copy the currently selected attribute and generate a new attribute (some attribute information may need to be modified by the user to avoid duplication). Delete button-allow the user to delete the currently selected attribute. And a save button for allowing the user to save the change made to the attribute list and save the updated attribute information to a local storage or a remote server. Editing attribute information-a user may modify information of an attribute by clicking on a data line or related editing control in the attribute list. The terminal device will update the interface in real time to reflect the user's changes.

And verifying the attribute information, namely verifying the attribute information input by the user by the terminal equipment before storing the attribute information so as to ensure that the attribute information accords with constraint conditions such as data type, length, decimal place and the like. If the verification fails, the terminal device will display an error message and prompt the user for correction.

S203, configuring a sub-model in a data modeling interface.

The terminal equipment loads a submodel configuration interface, and the interface provides an area for displaying a submodel list. For each sub-model, the terminal device inherits the attribute information of the base class model selected by the user. The user may add additional properties or modify inherited properties for each sub-model at the sub-model configuration interface. The terminal device generates a unique identifier for each sub-model and associates it with an entity (e.g., a record or business object in a database). After the configuration is completed, the submodel list and its attribute information are saved to a local storage or remote server.

In some embodiments of the present application, referring to the submodel configuration interface shown in fig. 5, after the configuration of the base class model is completed, the user may enter the submodel configuration interface through a navigation or menu. The interface is dedicated to exposing and managing the list of submodels. In the submodel configuration interface, each data row corresponds to a submodel. These data lines not only show the attribute information of the sub-model, but also point to specific entities (e.g., database tables, business objects, etc.) through associations.

Each sub-model inherits from a base class model, so that the fields stored in its data lines are largely inherited from the associated base class model. These fields include all of the attributes of the base class model, but sub-models may also add or override specific attributes.

In addition to inheriting properties from the base class model, the sub-model also has its own property information including model name, a name for uniquely identifying the sub-model. The category indicates the category or the field to which the submodel belongs, and is helpful for a user to quickly search and screen the submodel according to the category. Version number, namely recording version information of the submodels, and is used for distinguishing submodels of different versions and ensuring consistency and compatibility of data. The release status, which indicates whether the sub-model has been released, may be "released", "not released", "deactivated", etc., for controlling the availability and visibility of the sub-model.

Interface control buttons the submodel configuration interface also provides a series of control buttons for the user to manage and operate the submodel, including a new button that allows the user to create a new submodel based on the selected base class model and to enter its specific attribute information. Modifying buttons, allowing the user to select existing sub-models and modify their attribute information, including adding or overriding the attributes inherited from the base class model. Delete button-allow the user to delete sub-models that are no longer needed.

In creating or modifying a sub-model, a user needs to specify an entity to associate with the sub-model. This entity may be a table in a database, a business object, or any other data structure that can be recognized and processed by the system. After modifying or adding the sub-model, the terminal device verifies the attribute information input by the user to ensure that the attribute information accords with the constraint conditions of data type, length and the like and keeps consistent with the associated base class model. After verification is passed, the user may save configuration information for the sub-model.

S204, configuring scenes of the sub-model on the scene configuration interface, wherein the scenes comprise format information configured by a plurality of scenes based on the format guide, configuring scenes of the base class model on the scene configuration interface, and configuring the scenes comprise format information configured by the scenes based on the operation template of the format guide.

The terminal equipment loads a scene configuration interface, and the interface provides an area for displaying a scene list. The user may create new scenes or edit existing scenes, each containing attribute information of multiple scene interfaces, such as interface layout, element types, etc. The terminal device stores the scene information configured by the user to a local storage or a remote server.

In some embodiments of the present application, referring to the schematic diagram of the scene configuration interface shown in fig. 6, a user enters the scene configuration interface through a navigation or menu, which is used to present and manage a list of scenes. In the scene configuration interface, each data line corresponds to one scene interface. The data line stores attribute information of the scene interface, and the attribute information is used for describing basic characteristics and configuration of the scene interface.

The attribute information of the scene interface comprises, but is not limited to, a scene name, namely a name for uniquely identifying the scene interface, so that the user can conveniently identify and manage the scene interface. The category indicates the category or domain to which the scene interface belongs, such as a "configuration center" or an "inputter". These categories help users to quickly find and screen scene interfaces based on business needs. Type ID-a unique identifier for distinguishing between different types of scene interfaces, possibly one for internal use. An import model, which represents the name of the sub-model imported in the scene interface. The sub-model provides data structure and business logic support for the scene interface. Version number, recording the version information of the scene interfaces, and distinguishing the scene interfaces with different versions to ensure the consistency and compatibility of the data. And the release state indicates whether the scene interface is released or not, and the release state can be released, unpublished, deactivated and the like and is used for controlling the usability and the visibility of the scene interface.

The scene configuration interface also provides a series of control buttons for the user to manage and operate the scene interface, which may include a new button that allows the user to create a new scene interface and enter its attribute information. Modifying buttons, allowing the user to select the existing scene interface and modifying the attribute information thereof, such as changing scene names, belonging categories, introducing models, and the like. Delete button-allow the user to delete scene interfaces that are no longer needed.

In creating or modifying a scenario interface, a user needs to specify one or more sub-models as data source or business logic support for the scenario interface. These sub-models interact with interface elements in a specific way (e.g., data binding, event handling, etc.) in the scene interface. After modifying or adding the scene interface, the terminal device verifies the attribute information input by the user to ensure that the attribute information accords with constraint conditions such as data type, length and the like and keeps consistent with the introduced sub-model. After the verification is passed, the user can save the configuration information of the scene interface. To facilitate the user's viewing and verifying the actual effect of the scene interface, the scene configuration interface may also provide preview functionality. The user can view the layout, style, and presentation effect of the sub-model data of the scene interface by clicking the preview button.

S205, configuring an interface based on an operation template of a format guide, selecting one or more sub-models of an inheritance base class model in the operation template, and binding a scene interface for each selected sub-model based on a sub-model scene, wherein each sub-model corresponds to an entity.

Wherein the terminal device loads a format wizard interface that allows a user to select a plurality of sub-models from a list of sub-models.

After the user selects the sub-models, the terminal device provides an option for the user to select a scene interface from the scene list to bind each sub-model. The binding process involves associating an identifier of the sub-model with an identifier of the scene interface for use in a subsequent step. The binding information is saved to a local store or to a remote server.

For example, referring to the schematic diagrams of the format wizard interface shown in fig. 7 and 8, the format wizard interface is provided with two tabs, namely a main body area tab and a modal window button tab, after the user clicks the tab of the main body area, the interface shown in fig. 7 is displayed, the user sets a plurality of sub-models on the page, and the binding scenes, namely the content and the display style of the configuration entity list, are respectively set for each sub-model. After clicking the modal window button tab, the user displays the interface of fig. 8, in which the user configures elements and display styles in the list page.

S206, setting element types and element layout modes for the bound scene interfaces, and binding the entity input interface configuration with the designated model attributes.

Wherein for each bound scene interface, the terminal device allows the user to set the element type (e.g., text box, drop-down menu, etc.) and the layout manner (e.g., grid layout, linear layout, etc.) of the element. The user may also bind the entity input interface configuration (e.g., field mappings, validation rules, etc.) to the specified model property input box. The terminal device saves the configuration information to a local storage or remote server for use in rendering the scene interface.

In some embodiments of the application, a data table containing data to be screened is loaded in a data modeling or data analysis tool. The data table should contain a number of columns (fields) and rows (records), where each column represents an attribute and each row represents a data entity. And setting a series of preset filtering conditions according to the service requirements or analysis targets. These conditions may be set based on any column (field) in the data table, including but not limited to a range of values, text matches, date intervals, and the like. The setting of the filtering conditions should ensure that the data rows meeting the specific requirements can be accurately screened out. And applying preset filtering conditions in the data table. This is typically accomplished by a screening function in the data modeling tool or data analysis software. The user only needs to input or select the corresponding filtering conditions according to the prompts, and the system can automatically screen out the data rows meeting the conditions. After screening out the eligible data lines, the user needs to further determine the specified model attribute input box. This typically involves the step of selecting a column (field) of interest from the screened data row. These columns may contain data that the user needs to analyze or manipulate in depth. A particular row of data is located in the selected column. This may be accomplished by scrolling the data table, using a search function, or based on specific attributes of the data line (e.g., date, ID, etc.). A specified model attribute input box is determined in the selected column and the located data row. The model attribute input box should contain data values that the user needs to extract, modify, or analyze.

S207, when the application running period detects the trigger action of a user on a certain model attribute, an entity input interface is configured and displayed according to the entity input interface associated with the model attribute, wherein the entity input interface comprises an entity list and a list page.

Wherein the terminal device detects this action when the user triggers a certain model property input box (e.g. a click or double click). And according to the entity input interface configuration associated with the model attribute input box, the terminal equipment loads the corresponding entity input interface from a local storage or a remote server. The entity input interface comprises an entity list and a list page, wherein the entity list displays available entities, and the list page is used for inputting entity data. The terminal device presents the entity input interface to the user.

For example, after the user clicks the model attribute input box, an entity input interface shown in fig. 9 is displayed, the left side of the entity input interface is an entity list, which includes 6 entities, each entity corresponds to one 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 determine elements, and different entities in the entity list are clicked to correspondingly switch different list pages.

S208, after receiving a selection instruction of a user for an entity in the entity list, rendering corresponding elements in the list page according to a layout mode preset by the entity.

Wherein, after the user selects an entity from the entity list, the terminal device receives the selection instruction. According to the layout mode and element type pre-configured by the entity, the terminal equipment loads corresponding elements from a local storage or a remote server. The terminal device renders these elements in a list page so that the user can input entity data.

S209, inputting entity data in the rendered list page, and filling the entity data into the model attribute input box.

Wherein, the user inputs entity data in the rendered list page. The terminal device monitors the input actions of the user and verifies the validity of the data (such as data type, format and the like) in real time. When the user finishes inputting and submitting the data, the terminal device fills the entity data into a model attribute input box of the trigger action.

The embodiment of the application specifically comprises the following beneficial effects:

by configuring the base class model list and the attribute information thereof and creating the sub-model based on the base class model, the design of the data model is more flexible, and the requirement change of different business scenes can be easily dealt with. The subclass model inherits the attribute information of the base class model, reduces the workload of repeated configuration, and improves the modeling efficiency.

Through the scene configuration interface, a plurality of scene interfaces can be conveniently created and managed, and the sub-models are bound with a specific scene interface, and each sub-model corresponds to one entity. The scene configuration mode ensures that the data display and interaction are more visual and meet the service requirement, and simultaneously realizes the dynamic and intelligent data input through the binding of the entity input interface configuration and the model attribute input box.

The user can display a corresponding entity input interface through triggering a model attribute input box, and the interface comprises an entity list and a list page, so that the user can conveniently select an entity and input data. Meanwhile, corresponding elements are rendered in the list page according to a layout mode pre-configured by the entity, so that the data input process is smoother and more efficient.

After the user inputs entity data in the rendered list page, the data can be automatically filled into the corresponding model attribute input box, so that errors and complexity of manual input are avoided. The automatic data input mode not only improves the working efficiency, but also ensures the accuracy and consistency of data.

According to the technical scheme, powerful support is provided for data management under complex service scenes through flexible data modeling, scene configuration, intelligent entity input interfaces and automatic data filling. Whether data is displayed, interacted or input, the business requirement can be met, and the efficiency and accuracy of data management are improved.

The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

Referring to fig. 10, a schematic structural diagram of a dynamic entity input device based on a low-code development platform according to an exemplary embodiment of the present application is shown, and the device 10 is hereinafter referred to as "device 10". The apparatus 10 may be implemented as all or part of a terminal device by software, hardware, or a combination of both. The apparatus 10 includes a configuration unit 1001, a selection unit 1002, a binding unit 1003, a detection unit 1004, a rendering unit 1005, and a padding unit 1006.

The configuration unit 1001 is configured to configure a base class model at the data modeling interface, where the base class model includes description information of the base class model;

a selecting unit 1002, configured to select a base model in the data modeling interface, and configure attribute information for the selected base model in a base model configuration interface;

The configuration unit 1001 is further configured to configure a sub-model at the data modeling interface, where the sub-model includes attribute information of a plurality of sub-models, and the attribute information of the sub-model is attribute information inherited from an associated base class model;

The configuration unit 1001 is further configured to configure a scene of the sub-model at a scene configuration interface, where the scene includes format information configured by a plurality of scenes based on a format guide, and the scene configures a scene of the base class model at the scene configuration interface, where the scene includes format information configured by a scene based on an operation template of the format guide;

A binding unit 1003, configured to configure an interface based on an operation template of a format wizard, select one or more sub-models of an inheritance base class model in the operation template, and bind a scene interface for each selected sub-model based on the sub-model scene, each sub-model corresponding to an entity;

the binding unit 1003 is further configured to set an element type and an element layout mode for the bound scene interface, and bind the entity input interface configuration with the specified model attribute;

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 the application running period detects a trigger action of a user on the model attribute;

a rendering unit 1005, configured to render corresponding elements in a list page according to a layout manner preconfigured by the entity after receiving a selection instruction of a user for a certain entity in the entity list;

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

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 line in the base class model list corresponds to one base class model, the data lines are used for storing the description information of the base class model, and the data modeling interface further comprises a new button, a modification button, a deletion button, an opening button, a deactivation button and a recovery button.

In one or more possible embodiments, the base class model configuration interface comprises a base class model attribute list, wherein each data row of the base class model attribute list stores attribute information of one base class model, the attribute information comprises an item title, an item name, an item description, a data type, a reference definition, a length, a decimal place and a field name, and 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.

In one or more possible embodiments, each data line of the sub-model list corresponds to a word model, each sub-model is associated with an entity, fields stored by the data line are inherited by the associated base class model, attribute information of the sub-model comprises a model name, a category to which the sub-model belongs, a version number and a release state, and the sub-model configuration interface is provided with a new button, a modification button and a deletion button.

In one or more possible embodiments, each data line of the scene list corresponds to a scene interface, and attribute information of the scene interface includes a scene name, a category, a type ID, an introduced model, a version number and a release state, the introduced model represents a name of an introduced sub-model, and the category includes a configuration center/inputter.

In one or more possible embodiments, the specified model attribute input box is determined in the data table according to preset filtering conditions.

In one or more possible embodiments, data verification is performed on entity data, and entity data after verification is filled into a model attribute input box.

It should be noted that, when the apparatus 10 provided in the foregoing embodiment executes the dynamic entity input method based on the low-code development platform, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional allocation may 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 foregoing functions. In addition, the dynamic entity input device based on the low-code development platform provided in the above embodiment belongs to the same concept as the dynamic entity input method embodiment based on the low-code development platform, and the implementation process is embodied in the method embodiment, which is not described herein again.

The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are adapted to be loaded by a processor and execute the steps of the method shown in the embodiment of fig. 2, and the specific execution process may refer to the specific description of the embodiment shown in fig. 2, which is not repeated herein.

The present application also provides a computer program product storing at least one instruction that is loaded and executed by the processor to implement the low code development platform based dynamic entity input method as described in various embodiments above.

Referring to fig. 11, a schematic structural diagram of a terminal device is provided in an embodiment of the present application. As shown in fig. 11, the terminal device 1100 may include at least one processor 1101, at least one network interface 1104, a user interface 1103, a memory 1105, at least one communication bus 1102.

Wherein communication bus 1102 is used to facilitate connection communications among the components.

The user interface 1103 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 1103 may further include a standard wired interface and a wireless interface.

Network interface 1104 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.

Wherein the processor 1101 may comprise one or more processing cores. The processor 1101 connects various parts within the overall terminal device 1100 using various interfaces and lines, performs various functions of the terminal device 1100 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 1105, and invoking data stored in the memory 1105. Alternatively, the processor 1101 may 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), programmable logic array (Programmable Logic Array, PLA). The processor 1101 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like, the GPU is used for rendering and drawing contents required to be displayed by the display screen, and the modem is used for processing wireless communication. It will be appreciated that the modem may not be integrated into the processor 1101 and may be implemented by a single chip.

The Memory 1105 may include a random access Memory (RandomAccess Memory, RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 1105 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). Memory 1105 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 1105 may include a stored program area that may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, etc., and a stored data area that may store data related to the various method embodiments described above, etc. The memory 1105 may also optionally be at least one storage device located remotely from the processor 1101. As shown in fig. 11, an operating system, a network communication module, a user interface module, and application programs may be included in the memory 1105 as one type of computer storage medium.

In the terminal device 1100 shown in fig. 11, the user interface 1103 is mainly used for providing an input interface for a user to obtain data input by the user, while the processor 1101 may be used for calling an application program stored in the memory 1105 and specifically executing the method shown in fig. 2, and the specific process may be shown in fig. 2, which is not repeated herein.

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory, a random access memory, or the like.

The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.

Claims (8)

1. A dynamic entity input method based on a low-code development platform, comprising the following steps:

Configuring a base model in a data modeling interface, wherein the base model comprises description information of the base model, and the description information of the base model comprises a model name, a belonging category, a version number and a release state, wherein each data row in a base model list corresponds to one base model, and the data rows are used for storing the description information of the base model;

Selecting a base model from the data modeling interface, and configuring attribute information for the selected base model at a base model configuration interface;

The method comprises the steps of configuring a sub model on a data modeling interface, wherein the sub model comprises attribute information of a plurality of sub models, a sub model configuration interface and a data line configuration interface, wherein the attribute information of the sub model is inherited to attribute information of an associated base model;

Configuring scenes of the sub-model at a scene configuration interface, wherein the scenes comprise format information configured by a plurality of scenes based on format guidance, and configuring scenes of the base class model at the scene configuration interface, and the scenes comprise format information configured by the scenes based on an operation template of the format guidance;

An operation template configuration interface based on format guidance, wherein in the operation template, one or more sub-models of an inheritance base class model are selected, a scene interface is respectively bound for each selected sub-model based on a sub-model scene, and each sub-model corresponds to an entity;

setting element types and element layout modes for the bound scene interfaces, and binding entity input interface configuration with specified model attributes;

when detecting trigger action of a user on a certain model attribute in an application running period, configuring and displaying an entity input interface according to an entity input interface associated with the model attribute, wherein the entity input interface comprises an entity list and a list page;

after receiving a selection instruction of a user for a certain entity in the entity list, rendering a corresponding element in a list page according to a layout mode preset by the entity;

inputting entity data in the rendered list page, and filling the entity data into the model attribute input box.

2. The method of claim 1, wherein the base model configuration interface comprises a base model attribute list, wherein each data line of the base model attribute list stores attribute information of one base model, wherein the attribute information comprises an item title, an item name, an item description, a data type, a reference definition, a length, a decimal place and a field name, and wherein the base model configuration interface is provided with an add button, an insert button, a copy button, a delete button and a save button.

3. The method of claim 1, wherein each data line of the scene list corresponds to a scene interface, and wherein the attribute information of the scene interface includes a scene name, a category, a type ID, an introduced model, a version number, and a release status, the introduced model represents a name of an introduced sub-model, and the category is a category to which the introduced model belongs.

4. A method according to claim 3, characterized in that the specified model properties are determined in the data table according to preset filtering conditions.

5. The method of claim 1, wherein the entity data is subjected to data verification, and the entity data after the verification is filled into the model attribute input box.

6. A dynamic physical input device based on a low-code development platform, comprising:

The configuration unit is used for configuring a base model in a data modeling interface, wherein the base model comprises description information of the base model, the description information of the base model comprises a model name, a category, a version number and a release state, each data row in a base model list corresponds to one base model, and the data rows are used for storing the description information of the base model;

The selection unit is used for selecting a base model in the data modeling interface and configuring attribute information for the selected base model in the base model configuration interface;

the configuration unit is further used for configuring a sub-model on the data modeling interface, wherein the sub-model comprises attribute information of a plurality of sub-models, and the attribute information of the sub-model is the attribute information inherited from the associated base class model; displaying a submodel list on a submodel configuration interface, wherein each data line of the submodel list corresponds to one submodel, each submodel is associated with one entity, and fields stored by the data line are inherited from an associated base class model;

The configuration unit is further used for configuring scenes of the sub-model in the scene configuration interface, wherein the scenes comprise format information configured by a plurality of scenes based on format guidance, and the scenes of the base class model are configured in the scene configuration interface, and the scenes comprise format information configured by the scenes based on an operation template of the format guidance;

the binding unit is used for configuring an interface based on an operation template of the format guide, selecting one or more sub-models of the inheritance base class model in the operation template, and binding a scene interface for each selected sub-model based on the sub-model scene respectively, wherein each sub-model corresponds to an entity;

the binding unit is further used for setting element types and element layout modes for the bound scene interfaces and binding entity input interface configuration with the designated model attributes;

The detection unit is used for configuring and displaying an entity input interface according to the entity input interface associated with a certain model attribute when the trigger action of a user on the model attribute is detected in the application running period;

the rendering unit is used for rendering corresponding elements in a list page according to a layout mode pre-configured by the entity after receiving a selection instruction of a user for a certain entity in the entity list;

And the filling unit is used for inputting entity data in the rendered list page and filling the entity data into the model attribute input box.

7. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the method steps of any one of claims 1 to 5.

8. A terminal device comprising a processor and a memory, wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1-5.