Front-end and back-end integrated development method, system and equipment and storage medium

Abstract

The invention provides a front-end and back-end integrated development method, system and device and a storage medium. The method comprises the following steps: configuring a business object and a business entity, configuring a data table structure of the business entity, and configuring field authority information and business logic interceptor information; establishing a relationship between the business object and the business entity; according to the business object, the business entity, the field authority information, the business logic interceptor information and the relation between the business object and the business entity, rule information of the form and the list is configured, and the rule information comprises fields, query conditions and button functions; rendering a user interface according to the rule information of the form and the list; analyzing the data submitted by the user to a business object bound by the user, and mapping the data submitted by the user to a corresponding business entity field; performing permission verification on the mapped business entity field, and executing business logic verification through an interceptor; and storing the data under the condition that the permission verification and the business logic verification are respectively passed.

Description

Technical Field

[0001] The present application relates to the field of computers, and more specifically, to a front-end and back-end integrated development method, system, device and storage medium. Background Art

[0002] When current Web applications use low-code technology to implement interface functions such as form lists, they are usually based on highly customized prefabricated interface components (UI components or controls) and designed through a graphical interface using drag-and-drop layout. The association between these interface elements and the backend data model is usually achieved through a field binding mechanism, so that user operations on the front-end interface can be automatically converted into CRUD operations on the backend data. However, existing low-code technologies may not provide sufficient flexibility for unique or highly customized business needs and cannot meet the changing needs of the business.

[0003] Therefore, the present application provides a front-end and back-end integrated development method, system, device and storage medium to solve one of the above technical problems. Summary of the invention

[0004] The purpose of this application is to provide a front-end and back-end integrated development method, system, device and storage medium, which can solve at least one of the technical problems mentioned above. The specific solution is as follows: According to the specific implementation of the present application, in the first aspect, the present application provides a front-end and back-end integrated development method, including: Configure business objects and business entities, configure the data table structure of the business entity, and configure field permission information and business logic interceptor information; establish the relationship between the business object and the business entity; configure form and list rule information according to the business object, the business entity, the field permission information and business logic interceptor information, and the relationship between the business object and the business entity, the rule information includes fields, query conditions and button functions; render the user interface according to the form and list rule information; parse the user submitted data into the business object bound to the user, and map the user submitted data to the corresponding business entity field; perform permission check on the mapped business entity field, and perform business logic verification through the interceptor; save the data if the permission check and the business logic verification are passed respectively.

[0005] In one embodiment, the configuration field permission information and business logic interceptor information include: setting operation permissions for each business entity field, and customizing the permission level according to the user role; wherein the operation permissions include read permissions, edit permissions, and / or delete permissions; setting a business logic interceptor to insert specified business logic during data processing; wherein the specified business logic includes logging and / or data validation.

[0006] In one embodiment, the rendering user interface includes: controlling the page engine to generate a corresponding access interface in the user interface according to the rule information of the form and the list; and refining and adapting the display content of the user interface according to preset style and layout requirements.

[0007] In one implementation, in the relationship between the business object and the business entity, the number of correspondences between the business object and the business entity is specified based on business requirements.

[0008] In one embodiment, the business logic interceptor is modularly designed, and different business logic interceptors are used to execute the same or different business logic tasks; wherein the business logic tasks include data format verification, logging, and / or complex business logic applications.

[0009] According to the specific implementation of the present application, in the second aspect, the present application provides a front-end and back-end integrated development system, including: The page rendering engine is used to generate the user interface based on the configured form and list information; the rule management engine is used to perform field permission verification and business logic interception; the object management engine is used to maintain the core business object model and business entities in the application, and supports custom rule configuration and permission allocation.

[0010] In one embodiment, the rule management engine is used to coordinate various business logic interceptors; wherein different business logic interceptors are used to perform the same or different business logic tasks, and the business logic tasks include data format verification, logging, and / or complex business logic application.

[0011] In one implementation, the system further includes: a database for storing business objects and business entities, field permission information and business logic interceptor information, and the relationship between the business objects and the business entities.

[0012] According to the specific implementation of the present application, in a third aspect, the present application provides an electronic device, comprising a memory, a processor, and a computer program stored on the memory, characterized in that the processor executes the computer program to implement any one of the methods described in the first aspect.

[0013] According to the specific implementation of the present application, in a fourth aspect, the present application provides a computer-readable storage medium having a computer program / instruction stored thereon, characterized in that when the computer program / instruction is executed by a processor, the method described in any one of the first aspects is implemented.

[0014] Compared with the prior art, the above-mentioned scheme of the embodiment of the present application has at least the following beneficial effects: by configuring business objects, business entities and their relationships, and combining field permission information and business logic interceptor information, the method can flexibly configure form and list rules to ensure consistency and efficient collaboration between the front and back ends, which not only improves development efficiency, but also enhances the flexibility and maintainability of the system, and can quickly respond to changing business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 A flow chart showing a front-end and back-end integrated development method is shown; Figure 2 A flow chart of a method for configuring field permission information and business logic interceptor information is shown; Figure 3 A flow chart of a method for rendering a user interface is shown; Figure 4 An overall flow chart for front-end and back-end integrated development is shown; Figure 5 A flow chart for defining business objects and entity information is shown; Figure 6 shows an entity relationship diagram related to a list; Figure 7 An entity relationship diagram of a business object is shown; Figure 8 A schematic diagram of a process for preparing form and list information is shown; Fig. 9 A form and list configuration sub-flow chart is shown; Fig.10 A schematic diagram of a calling method of an interceptor is shown; Fig.11 A unit block diagram of a front-end and back-end integrated development system according to an embodiment of the present application is shown; Fig.12 An architecture diagram consisting of a front-end and back-end integrated development system is shown; Fig.13 It is a block diagram of an electronic device for front-end and back-end integrated development according to an exemplary embodiment. DETAILED DESCRIPTION

[0016] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0017] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings, and "multiple" generally includes at least two.

[0018] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0019] It should be understood that, although the terms first, second, third, etc. may be used to describe in the embodiments of the present application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, without departing from the scope of the embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first.

[0020] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0021] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a product or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such a product or system. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the product or system including the elements.

[0022] It should be particularly noted that any symbols and / or numbers in the specification that are not marked in the accompanying drawings are not drawing marks.

[0023] The optional embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0024] The embodiment provided in this application is an embodiment of a front-end and back-end integrated development method.

[0025] Combine the following Figure 1 The embodiments of the present application are described in detail.

[0026] Figure 1 A flowchart of a front-end and back-end integrated development method is shown, such as Figure 1 As shown, the process includes the following steps S101 to S107.

[0027] Step S101, configure business objects and business entities, configure the data table structure of the business entity, and configure field permission information and business logic interceptor information.

[0028] Step S102: establishing a relationship between a business object and a business entity.

[0029] Step S103, according to the business object, business entity, field permission information and business logic interceptor information, and the relationship between the business object and the business entity, configure the rule information of the form and the list, the rule information includes fields, query conditions and button functions.

[0030] Step S104: Rendering a user interface according to the rule information of the form and the list.

[0031] Step S105: parsing the user submitted data into the business object bound to the user, and mapping the user submitted data into the corresponding business entity field.

[0032] Step S106, performing permission check on the mapped business entity fields, and executing business logic verification through the interceptor.

[0033] Step S107, when the authority verification and business logic verification are passed respectively, data is saved.

[0034] The method provided in this application can flexibly configure form and list rules by configuring business objects, business entities and their relationships, and combining field permission information and business logic interceptor information to ensure consistency and efficient collaboration between the front and back ends. This method not only improves development efficiency, but also enhances the flexibility and maintainability of the system, and can quickly respond to changing business needs.

[0035] Figure 2 A flow chart of a method for configuring field permission information and business logic interceptor information is shown, such as Figure 2 As shown, the process includes the following steps S201 and S202.

[0036] Step S201, setting operation permissions for each business entity field, and customizing permission levels according to user roles.

[0037] The operation permissions include read permission, edit permission, and / or delete permission.

[0038] Step S202, setting a business logic interceptor to insert specified business logic into the data processing process.

[0039] Wherein, the specified business logic includes logging and / or data validation.

[0040] In the embodiment of the present application, the operation permissions are set for each business entity field, and the permission level is customized according to the user role. At the same time, the business logic interceptor is set to perform tasks such as logging and data verification, which significantly enhances the security and data integrity of the system. This fine-grained permission control and business logic processing capabilities make the system more reliable and robust.

[0041] Figure 3 A flowchart of a method for rendering a user interface is shown. Figure 3 As shown, the process includes the following steps S301 and S302.

[0042] Step S301, controlling the page engine to generate a corresponding access interface in the user interface according to the rule information of the form and the list.

[0043] Step S302: According to the preset style and layout requirements, the display content of the user interface is refined and adapted.

[0044] In the embodiment of the present application, the page engine generates a user interface according to the form and list rule information, and refines the display content according to the preset style and layout requirements, thereby ensuring the aesthetics and user experience of the user interface. This method makes the user interface meet business requirements and have good visual effects, thereby improving user satisfaction.

[0045] Figure 4 An overall flow chart for front-end and back-end integrated development is shown.

[0046] For example, Figure 4 As shown in the figure, first configure the data table structure of business objects and business entities to ensure that data can be stored and retrieved correctly, configure field permission information and business rule interceptor information, and establish the relationship between business objects and business entities to adapt to the business domain model. Next, configure the relevant rule information of forms and lists, including fields, query conditions, and button functions. Then, based on these configuration data and rules, further refine the interface display content so that the page engine generates an access interface that meets the preset style and layout requirements for users to use. When the user completes the data filling and clicks Submit, the system sends the collected information to the background for processing. The background will parse the data submitted by the user and map it to the bound business object and the corresponding business entity field. Before saving the data, the system will first check whether each field meets its permission settings to prevent unauthorized operations. Finally, the necessary business logic verification is performed through the interceptor to ensure the integrity and consistency of the data.

[0047] As a feasible embodiment, in the relationship between the business object and the business entity, the corresponding quantity between the business object and the business entity is specified based on the business requirement.

[0048] In the embodiment of the present application, the corresponding number between business objects and business entities is allowed to be specified based on business needs, providing greater flexibility. This flexibility enables the system to better adapt to various complex business scenarios, and both simple single relationships and complex many-to-many relationships can be effectively supported.

[0049] As a feasible embodiment, the business logic interceptor is modularly designed, and different business logic interceptors are used to execute the same or different business logic tasks.

[0050] Among them, business logic tasks include data format verification, log recording, and / or complex business logic applications.

[0051] In the embodiment of the present application, a modularly designed business logic interceptor can perform a variety of business logic tasks, such as data format verification, log recording, and complex business logic applications. This modular design improves the scalability and maintainability of the system, allowing developers to easily add or modify business logic without affecting other parts of the system.

[0052] Figure 5 A flow chart for defining business objects and entity information is shown.

[0053] For example, Figure 5As shown in the figure, first of all, it is necessary to define business objects and clarify their role and scope in the system, including identifying and creating business entities (such as customers, orders, etc.) and recording the attributes of these entities in detail (such as name, address, order number, etc.). The relationship between business objects and business entities can be one-to-one or one-to-many, depending on business needs. For example, one customer may correspond to multiple orders. The configuration engine ensures that each business object can be accurately mapped to the corresponding business entity, laying the foundation for subsequent data processing and permission management. Next, set permission rules for each field of the business entity. This step is completed by the rule management engine. The main purpose is to ensure the security and privacy of the data. The permission rules include but are not limited to read, edit, delete and other operation permissions, and customize different permission levels according to user roles. For example, ordinary employees may only have the permission to view certain sensitive information, while senior managers may have more extensive access rights. Finally, the business object configuration information determined in the first two steps and the permission rules of each business entity field are uniformly stored in the database, which not only helps to maintain the consistency and integrity of the data, but also facilitates the maintenance and expansion of the system. The information stored in the database serves as the basis for the operation of the system and supports the execution of various business processes. In addition, regularly checking and updating these configuration information and permission rules to adapt to changes in business development is also one of the key measures to ensure efficient and stable operation of the system.

[0054] Figure 6 A list-related entity relationship diagram is shown.

[0055] For example, Figure 6 As shown in the figure, it includes four main parts: "Basic List Information", "List Buttons", "List Fields" and "List Query Conditions". Basic list information involves basic information about a specific subject, such as book titles, authors, and publication dates in a library management system; list buttons refer to operation options related to lists, such as the functions of adding new entries, deleting existing entries, and editing existing entries; list fields refer to specific items or data columns that make up a list, such as book titles; and list query conditions are the criteria used to filter or search lists to help users find the information they need. These four are interrelated. Basic list information provides basic data, list fields define how data is organized, list buttons allow users to operate on data, and list query conditions help users obtain the information they need more efficiently.

[0056] Figure 7 An entity relationship diagram of a business object is shown.

[0057] For example, Figure 7As shown in the figure, the business object is the core of the entire model, which consists of one or more business entities and represents a domain instance. Business entities correspond to specific physical database tables, representing the actual storage structure of data, while business entity fields are the specific attributes or characteristics of these entities, corresponding to actual data table fields. Field rule configuration involves setting specific rules for business entity fields, including basic rules such as data types and length restrictions, as well as extended rules for field permissions. Field control configuration is configured for business interceptor types (such as date formatting interceptors, address format interceptors, etc.) to facilitate users to operate and manage these fields in the system. Overall, this entity relationship diagram shows how to build a complete business management system architecture by defining business objects and their related fields, and combining corresponding rules and control configurations, thereby improving the flexibility and scalability of the system while ensuring data quality and security.

[0058] Figure 8 A schematic diagram of a process for preparing form and list information is shown.

[0059] For example, Figure 8 As shown, it is necessary to collect and organize the form and list information required on the user interface, which involves designing the layout of the form, field types (such as text input boxes, drop-down selection boxes, etc.) and the content structure of the list display. This information is submitted to the interface management engine for processing to ensure that they can be correctly displayed on the user interface and provide a good user experience. At the same time, relevant business objects are obtained from the object management engine to ensure that the form and list can accurately reflect the needs of the business logic. Once the form and list information are parsed by the interface management engine, the next step is to associate this information with the business objects obtained from the object management engine, establish a mapping relationship between the form and list information and the business objects, and ensure that the user's operations on the interface can directly affect the business data in the background. For example, when the user fills out the form and submits it, this data should be automatically updated to the corresponding business object. Finally, save this configuration information to the database, including the basic information of the form and list and the association rules between them and the business objects.

[0060] Fig. 9 A form and list configuration sub-flowchart is shown.

[0061] For example, Fig. 9As shown in the figure, when the front-end user submits a form or initiates a list query request, the interface management engine will first receive these requests and query the corresponding form and list configuration information from the configuration database, including field definitions, query conditions, buttons and other interactive elements, to ensure that the user interface can be dynamically generated according to the preset configuration. Subsequently, the interface management engine calls the object management engine to query the business object associated with the configuration information. The object management engine extracts specific business object instances from the database and obtains field permission information and business logic interceptor information from the rule management engine. The rule management engine performs permission verification on the data requested by the user based on the field permission information. If the user does not have sufficient permission to access a field, the data of the field will not be returned. At the same time, the rule management engine injects business logic interceptors into the data processing process. These interceptors execute specific business logic before and after data query, modification or deletion operations, such as logging and data validation. After receiving the processed data, the interface management engine combines the form and list configuration information to dynamically generate the user interface, ensure that all fields and buttons are displayed correctly according to the configuration, and present it to the user through the front-end framework or technology (such as HTML, CSS, JavaScript), so that the user can see and operate the data they requested.

[0062] Fig.10 A schematic diagram of a calling method of an interceptor is shown.

[0063] For example, Fig.10 As shown in the figure, the rule management engine coordinates and manages a series of interceptors, each of which is responsible for executing specific business logic. For example, interceptor A is the first interceptor to enter the process, and its task is to perform data format verification. Only after successful execution can it continue to the subsequent steps; followed by interceptor B, which is responsible for logging; and below is interceptor C, which performs deeper data processing or complex business rule application. The ellipsis in the figure indicates that there are more interceptors that are not listed one by one in the figure, which means that the rule management engine can accommodate any number of interceptors, each with its own responsibilities, together forming a highly modular and extensible business logic processing chain.

[0064] This application is based on data and rule-driven development of rendering pages, field permission rules, and interceptor insertion execution business. Compared with the ordinary low-code front-end and back-end form list implementation solution, this application solves the problem that ordinary low-code technology cannot flexibly respond to changes in demand through online configuration, automatic rendering interface, automatic verification of fields, and interceptor execution of business logic, thereby improving the flexibility and efficiency of the system. In terms of commercial value, this application not only improves the ability to respond quickly to changes in business needs and reduces R&D investment, but also has been successfully applied to multiple projects such as product products, technical middle-end management platform, capability operation center, science and technology innovation platform, smart park, rural revitalization, marketing management platform, and R&D cloud platform. At the same time, it also abstracts the front-end and back-end development methods that combine data-driven and rule-driven, and provides a front-end and back-end visual development platform, which helps R&D personnel to quickly build business applications and improve product delivery efficiency and quality. In actual project applications, after the business management project adopted the technology of this application, the demand response efficiency was significantly improved. By configuring forms and lists online, the effects can be seen in real time, which greatly improves the system's business response capabilities and makes the front-end and back-end integrated development more efficient.

[0065] The present application also provides a system embodiment that is based on the above embodiment, which is used to implement the method steps of the above embodiment. The explanation based on the same name meaning is the same as the above embodiment, and has the same technical effect as the above embodiment, which will not be repeated here.

[0066] like Fig.11 As shown, the present application provides a front-end and back-end integrated development system 1100, including: The page rendering engine 1101 is used to generate a user interface based on the configured form and list information. The rule management engine 1102 is used to perform field permission verification and business logic interception. The object management engine 1103 is used to maintain the core business object model and business entities in the application, and supports custom rule configuration and permission allocation.

[0067] In one implementation, the rule management engine 1102 is used to coordinate various business logic interceptors, wherein different business logic interceptors are used to execute the same or different business logic tasks, and the business logic tasks include data format verification, log recording, and / or complex business logic application.

[0068] In one implementation, the front-end and back-end integrated development system 1100 further includes: a database 1104 for storing business objects and business entities, field permission information and business logic interceptor information, and the relationship between business objects and business entities.

[0069] Fig.12 An architecture diagram consisting of a front-end and back-end integrated development system is shown.

[0070] For example, Fig.12 As shown in the figure, the architecture diagram shows three main components: page rendering engine, rule management engine and object management engine, which are closely related. The page rendering engine consists of two sub-modules: form and list. The form contains various types of input boxes (such as text boxes, drop-down menus) and operation buttons, while the list is used to display data sets and provide filtering conditions for users to find specific information. The rule management engine ensures that all interactive behaviors comply with the preset security policies or business process requirements, prevents unauthorized access to sensitive data through "field permission verification", and performs additional checks before performing key operations through "business logic interceptors", such as verifying user permissions and parameter validity. The object management engine is responsible for maintaining the core business object model and business entities (i.e., data tables) in the application. Business objects can be composed of one or more business entities. Each business entity has its own unique set of attributes and can be configured with permissions through custom rules (such as adding new calculation formulas). In addition, different business interceptor types (such as date formatting interceptors, address format interceptors, etc.) can be assigned to each field to provide a more flexible configuration path. These three engines together form a powerful and flexible application development framework, enabling developers to quickly build complex and diverse enterprise-level application software products.

[0071] Regarding the system in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0072] Fig.13 It is a block diagram of an electronic device 1300 for front-end and back-end integrated development according to an exemplary embodiment.

[0073] like Fig.13 As shown, one embodiment of the present application provides an electronic device 1300. Among them, the electronic device 1300 includes a memory 1301, a processor 1302, and an input / output (I / O) interface 1303. Among them, the memory 1301 is used to store instructions. The processor 1302 is used to call the instructions stored in the memory 1301 to execute the front-end and back-end integrated development method of the embodiment of the present application. Among them, the processor 1302 is connected to the memory 1301 and the I / O interface 1303 respectively, for example, it can be connected through a bus system and / or other forms of connection mechanisms (not shown). The memory 1301 can be used to store programs and data, including the programs of the front-end and back-end integrated development method involved in the embodiment of the present application, and the processor 1302 executes various functional applications and data processing of the electronic device 1300 by running the programs stored in the memory 1301.

[0074] In the embodiment of the present application, the processor 1302 can be implemented in at least one hardware form of a digital signal processor (Digital Signal Processing, DSP), a field programmable gate array (Field Programmable Gate Array, FPGA), and a programmable logic array (Programmable Logic Array, PLA). The processor 1302 can be a central processing unit (Central Processing Unit, CPU) or one or a combination of other forms of processing units with data processing capabilities and / or instruction execution capabilities.

[0075] The memory 1301 in the embodiment of the present application may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may include, for example, read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD), etc.

[0076] In the embodiment of the present application, the I / O interface 1303 may be used to receive input instructions (such as digital or character information, and key signal input related to user settings and function control of the electronic device 1300), and may also output various information to the outside (such as images or sounds). In the embodiment of the present application, the I / O interface 1303 may include one or more of a physical keyboard, a function key (such as a volume control key, a switch key, etc.), a mouse, a joystick, a trackball, a microphone, a speaker, and a touch panel.

[0077] In some embodiments, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, any of the methods described above is performed.

[0078] In some embodiments, the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, any of the methods described above is performed.

[0079] Although operations are described in a particular order in the drawings, this should not be understood as requiring that the operations be performed in the particular order shown or in serial order, or that all shown operations be performed to achieve desired results. In certain circumstances, multitasking and parallel processing may be advantageous.

[0080] The methods, systems, devices and storage media of the present application can be implemented using standard programming techniques, using rule-based logic or other logic to implement various method steps. It should also be noted that the terms "system" and "module" used herein and in the claims are intended to include implementations using one or more lines of software code and / or hardware implementations and / or devices for receiving input.

[0081] Any steps, operations or procedures described herein may be performed or implemented using one or more hardware or software modules, either alone or in combination with other devices. In one embodiment, the software module is implemented using a computer program product including a computer-readable medium containing computer program code, which can be executed by a computer processor to perform any or all of the described steps, operations or procedures.

[0082] The foregoing description of the implementation of the present application has been given for the purpose of illustration and description. The foregoing description is not exhaustive nor is it intended to limit the present application to the exact form disclosed, and various variations and modifications may exist according to the above teachings or may be obtained from the practice of the present application. These embodiments are selected and described in order to illustrate the principles of the present application and its practical application, so that those skilled in the art can utilize the present application in various embodiments and various modifications suitable for the specific purpose contemplated.

[0083] Regarding the system in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0084] It can be further understood that, unless otherwise specified, “connection” includes a direct connection without other components between the two, and also includes an indirect connection with other components between the two.

[0085] It is further understood that, although the operations are described in a specific order in the drawings in the embodiments of the present application, it should not be understood as requiring the operations to be performed in the specific order or serial order shown, or requiring the execution of all the operations shown to obtain the desired results. In certain environments, multitasking and parallel processing may be advantageous.

[0086] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to encompass any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the field of the present application that are not disclosed in the present application. The specification and embodiments are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following scope of rights.

[0087] It should be understood that the present application is not limited to the precise structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the scope of the appended claims.

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

Claims

1. A front-end and back-end integrated development method, characterized in that: The following steps are involved: Configure business objects and business entities, configure the data table structure of the business entity, and configure field permission information and business logic interceptor information; Establishing a relationship between the business object and the business entity; According to the business object, the business entity, field permission information and business logic interceptor information, and the relationship between the business object and the business entity, configure rule information of the form and the list, the rule information including fields, query conditions and button functions; Rendering a user interface according to the rule information of the form and the list; Parsing the user submitted data into the business object bound to the user, and mapping the user submitted data to the corresponding business entity field; Perform permission check on the mapped business entity fields and perform business logic verification through interceptors; When the authority verification and the business logic verification are passed respectively, data is saved.

2. The method according to claim 1, characterized in that The configuration field permission information and business logic interceptor information include: Set operation permissions for each business entity field and customize permission levels according to user roles; wherein the operation permissions include read permissions, edit permissions, and / or delete permissions; A business logic interceptor is set to insert specified business logic into the data processing process; wherein the specified business logic includes logging and / or data verification.

3. The method according to claim 1, characterized in that The rendering user interface includes: Controlling the page engine to generate a corresponding access interface in the user interface according to the rule information of the form and the list; According to the preset style and layout requirements, the display content of the user interface is refined and adapted.

4. The method according to any one of claims 1 to 3, characterized in that: In the relationship between the business object and the business entity, the number of correspondences between the business object and the business entity is specified based on business requirements.

5. The method according to any one of claims 1 to 3, characterized in that: The business logic interceptor is modularly designed, and different business logic interceptors are used to execute the same or different business logic tasks; The business logic tasks include data format verification, log recording, and / or complex business logic application.

6. A front-end and back-end integrated development system, characterized in that: include: Page rendering engine, used to generate user interface based on configured form and list information; Rule management engine, used to perform field permission verification and business logic interception; The object management engine is used to maintain the core business object model and business entities in the application, and supports custom rule configuration and permission allocation.

7. The system according to claim 6, characterized in that The rule management engine is used to coordinate various business logic interceptors; Among them, different business logic interceptors are used to execute the same or different business logic tasks, and the business logic tasks include data format verification, log recording, and / or complex business logic application.

8. The system according to claim 6 or 7, characterized in that: The system further comprises: The database is used to store business objects and business entities, field permission information and business logic interceptor information, and the relationship between the business objects and the business entities.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the method according to any one of claims 1 to 5.

10. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images