Target page display method and page creation display method

Abstract

The embodiment of the invention provides a target page display method and a page creation display method.The target page display method comprises the steps that page instance configuration information is obtained according to a page instance identifier and user information carried in a target page access request, the page instance configuration information comprises module configuration information and field configuration information; determining a target component and a target application interface according to the module configuration information; the target application interface is called, target data corresponding to the field configuration information is obtained from a target database, and the target database is a database determined according to the module configuration information; according to the target component and the target data, rendering and displaying a target page; according to the page instance configuration information corresponding to different users, the target page configured by the user is dynamically rendered, flexible configuration and efficient rendering of the page in a multi-tenant environment are realized, and waste of storage resources is reduced.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer technology, and in particular to a target page display method. One or more embodiments of this specification also relate to a target page display device, a page creation and display method, a computing device, a computer-readable storage medium, and a computer program product. Background Art

[0002] When a SaaS (Software as a Service) service provider provides software services to users based on product capabilities, different tenants use pages with the same project functions on the basic application capabilities provided by the SaaS service provider, and the data between different tenants is completely isolated. Security and performance indicators are guaranteed by the service provider.

[0003] However, in multi-tenant scenarios, service providers need to enable different tenants to customize pages with the same functionality and adjust component fields within the pages. In multi-tenant scenarios, when providing personalized page configuration for multiple tenants and dynamically rendering pages based on tenant information at runtime, service providers face challenges such as duplicated module information across multiple tenants, resulting in wasted storage resources and inefficient page rendering. Summary of the Invention

[0004] In view of this, embodiments of this specification provide a method for displaying a target page. One or more embodiments of this specification also relate to a target page display device, a page creation and display method, a computing device, a computer-readable storage medium, and a computer program product to address technical deficiencies in the prior art.

[0005] According to a first aspect of an embodiment of this specification, a target page display method is provided, including: Obtaining page instance configuration information according to the page instance identifier and user information carried in the target page access request, wherein the page instance configuration information includes module configuration information and field configuration information; Determine the target component and target application interface according to the module configuration information; Calling the target application interface to obtain target data corresponding to the field configuration information from a target database, wherein the target database is a database determined according to the module configuration information; Render and display the target page according to the target component and the target data.

[0006] According to a second aspect of the embodiments of this specification, a target page display device is provided, including: An information determination module is configured to obtain page instance configuration information according to the page instance identifier and user information carried in the target page access request, wherein the page instance configuration information includes module configuration information and field configuration information; a target determination module, configured to determine a target component and a target application interface according to the module configuration information; a data acquisition module configured to call the target application interface to obtain target data corresponding to the field configuration information from a target database, wherein the target database is a database determined according to the module configuration information; The rendering and display module is configured to render and display the target page according to the target component and the target data.

[0007] According to a third aspect of the embodiments of this specification, a page creation and display method is provided, including: Creating a page prototype according to the user information carried in the page instance creation request, wherein the page prototype includes page information and user information; Determining a target module from a plurality of preset common modules corresponding to the page prototype, and obtaining module configuration information of the target module; Select a target field from the full field pool corresponding to the target module, and obtain field configuration information of the target field; Obtaining a target page instance according to the page prototype, the module configuration information, and the field configuration information, wherein a page instance identifier of the page instance is determined according to the page information, and page instance configuration information corresponding to the page instance is determined according to the module configuration information and the field configuration information; When a target page access request carrying a page instance identifier and user information is received, the target page display method described above is applied to render and display the target page.

[0008] According to a fourth aspect of the embodiments of this specification, a computing device is provided, including: memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps of the above-mentioned target page display method and page creation and display method are implemented.

[0009] According to the fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores a computer program / instruction, which, when executed by a processor, implements the steps of the above-mentioned target page display method and page creation and display method.

[0010] According to the sixth aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instruction, which, when executed by a processor, implements the steps of the above-mentioned target page display method and page creation and display method.

[0011] An embodiment of the present specification provides a target page display method, which obtains page instance configuration information based on the page instance identifier and user information carried in the received target page access request. When the page instance configuration information includes module configuration information and field configuration information, the target component and target application interface are determined based on the module configuration information. That is, by providing modular configuration capabilities, each user can obtain corresponding page instance configuration information based on user information and page instance identifiers, so that in multi-tenant similar project scenarios, different users can quickly launch pages according to their personalized functional requirements. By calling the target application interface, the target data corresponding to the field configuration information is obtained from the target database. When the target page is rendered and displayed according to the target component and target data, the user-configured target page is dynamically rendered according to the page instance configuration information corresponding to different users. The modules have specific capabilities and can be freely combined and configured, so that flexible configuration and efficient rendering of pages in a multi-tenant environment can be achieved, reducing storage resource waste and improving page rendering speed. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 This is a scenario diagram of a target page display method provided by an embodiment of this specification; Figure 2 This is a flowchart of a target page display method provided by an embodiment of this specification; Figure 3a This is a flowchart of a module configuration provided by an embodiment of this specification; Figure 3b This is a general module structure diagram provided by an embodiment of this specification; Figure 3c This is a schematic diagram of a process for creating and publishing a page instance provided by an embodiment of this specification; Figure 3d This is a schematic diagram of a processing process of a target page display method provided by an embodiment of this specification; Figure 4 This is a schematic diagram of the structure of a target page display device provided by an embodiment of this specification; Figure 5 This is a structural block diagram of a computing device provided by one embodiment of this specification. DETAILED DESCRIPTION

[0013] The following description sets forth many specific details to facilitate a thorough understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the scope of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0014] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a," "the," and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0015] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0016] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0017] First, the terms involved in one or more embodiments of this specification are explained.

[0018] Module: A page consists of multiple modules. A module is the layout unit of a page container. It consists of front-end components, module code, application code, interface, and field configuration information. The module code is globally unique and can be reused and rewritten.

[0019] Page prototype: In the embodiments of this specification, it refers to a container composed of multiple modules with scalable capabilities. You can introduce all the modules involved in the page prototype's functions into the page prototype and configure the general capability settings of each module.

[0020] Page instance: In the embodiments of this specification, it refers to a page that is instantiated according to the personalized needs of different tenants based on the page prototype. It is used to provide the corresponding tenant with a front-end view with corresponding functions after it is released online. Users can access the page in a browser through the URL and user information; Tenant: In the embodiments of this specification, refers to the user, who can personalize the page prototype and obtain the corresponding personalized page strength. That is, each tenant can have its own data, custom settings and configured page instances, but share the same page prototype and application code.

[0021] Field: A data input or display location within a module's corresponding front-end component. Fields are used to accept user input or display data retrieved from the back-end. For example, in a form structure, fields can be presented in various forms, such as labels, input boxes, drop-down menus, and checkboxes.

[0022] Application: In the embodiments of this specification, there are two types of applications. One type refers to the front-end application that provides interface requests and processes page instance view rendering functions, and the other type refers to the back-end application that processes project execution logic.

[0023] SaaS service providers provide the same basic application capabilities and page rendering capabilities in the same project scenarios, but need to isolate data and develop customized functional requirements for different tenants. In order to avoid repeated development and improve development efficiency, they also improve the efficiency of page view rendering and project data rendering, and avoid the waste of storage resources and slow page response speed caused by the expansion of front-end page resources in multi-tenant situations.

[0024] The embodiments of this specification provide a target page display method, which aims to use the design concept of dynamic pages and the idea of modular page rendering to enable each module to have specific capabilities. Tenants only need to introduce modules and corresponding fields into the page to achieve personalized customization and efficient development of multiple tenants, which significantly enhances the service provider's product iteration capabilities and customization capabilities in multi-tenant scenarios.

[0025] In this specification, a target page display method is provided. This specification also involves a target page display device, a page creation and display method, a computing device, a computer-readable storage medium, and a computer program product, which are described in detail one by one in the following embodiments.

[0026] See also Figure 1 , Figure 1 A schematic diagram of a scenario of a target page display method provided according to an embodiment of this specification is shown.

[0027] The end-side device is used to receive a user's target page access request, which carries a page instance identifier and user information; obtain page instance configuration information based on the page instance identifier and user information carried in the target page access request, wherein the page instance configuration information includes module configuration information and field configuration information; determine the target component and target application interface based on the module configuration information; call the target application interface to obtain target data corresponding to the field configuration information from the target database, wherein the target database is a database determined based on the module configuration information; render and display the target page based on the target component and the target data.

[0028] End-side devices can include browsers, apps (applications), web applications such as H5 (HyperText Markup Language 5), lightweight apps (also known as mini-programs, a type of lightweight application), or cloud applications. End-side devices can be developed based on the software development kit (SDK) of the corresponding service provided by the server, such as the real-time communication (RTC) SDK. End-side devices can be deployed in electronic devices and rely on the device or certain apps within the device to function. Electronic devices can have displays and support information browsing, such as personal mobile terminals such as mobile phones, tablets, and personal computers. Electronic devices can also typically host various other applications, such as human-computer interaction applications, model training applications, text processing applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, and social platform software.

[0029] The target page display method provided in the embodiment of this specification obtains page instance configuration information based on the page instance identifier and user information carried in the received target page access request. When the page instance configuration information includes module configuration information and field configuration information, the target component and target application interface are determined according to the module configuration information. That is, by providing modular configuration capabilities, each user can obtain corresponding page instance configuration information according to user information and page instance identifier, so that in similar multi-tenant project scenarios, different users can quickly launch pages according to their personalized functional requirements. By calling the target application interface, the target data corresponding to the field configuration information is obtained from the target database. When the target page is rendered and displayed according to the target component and target data, the user-configured target page is dynamically rendered according to the page instance configuration information corresponding to different users. The modules have specific capabilities and can be freely combined and configured, so that flexible configuration and efficient rendering of pages in a multi-tenant environment can be achieved, reducing storage resource waste and improving page rendering speed.

[0030] See also Figure 2 , Figure 2 A flowchart of a target page display method provided by an embodiment of this specification is shown, which specifically includes the following steps.

[0031] Step 202: Obtaining page instance configuration information based on the page instance identifier and user information carried in the target page access request, wherein the page instance configuration information includes module configuration information and field configuration information; Specifically, when a user requests access to a page, the page's configuration information is retrieved based on the page instance identifier (i.e., the page's unique identifier) and user information (such as user identity and permissions) provided in the request. This configuration information includes module configuration information and field configuration information. Module configuration information can be understood as the modules that make up the page and the specific settings of each module (such as the module's display method and function). Field configuration information can be understood as the specific settings of the fields (such as input boxes and drop-down menus) contained in each module (such as the display order of the fields and whether they are editable).

[0032] In fact, the personalized configuration of the page is dynamically obtained and generated through the information in the user request, ensuring that the page can be displayed correctly according to the user's needs and permissions.

[0033] In one or more embodiments of this specification, before a user requests to access a page, a page instance needs to be created and configured. The specific implementation is as follows: Before obtaining the page instance configuration information according to the page instance identifier and user information carried in the target page access request, the method further includes: Creating a page prototype according to the user information carried in the page instance creation request, wherein the page prototype includes page information and user information; Determining a target module from a plurality of preset common modules corresponding to the page prototype, and obtaining module configuration information of the target module; Select a target field from the full field pool corresponding to the target module, and obtain field configuration information of the target field; A target page instance is obtained based on the page prototype, the module configuration information and the field configuration information, wherein the page instance identifier of the page instance is determined based on the page information, and the page instance configuration information corresponding to the page instance is determined based on the module configuration information and the field configuration information.

[0034] Specifically, when a user initiates a request to create a page instance, the system will create a page prototype based on the user information carried in the request (such as user identity, permissions, etc.). The page prototype includes page information (such as page name, page code, etc.) and user information, which is used to define the page's infrastructure and user-related configurations.

[0035] From the multiple preset common modules corresponding to the page prototype, the user selects the required module, which is called the target module. Each module has its own module configuration information, including the module's function and display mode. From the full field pool corresponding to the target module, the user selects the field required by the user, which is called the target field. Each field has its own field configuration information, including the display order of the field and whether it is editable.

[0036] A target page instance is generated based on the page prototype, module configuration information and field configuration information. The page instance has a unique page instance identifier to identify the page instance. The page instance configuration information of the page instance is jointly determined by the module configuration information and the field configuration information to ensure that the page can be dynamically rendered according to user needs and permissions.

[0037] The target page display method provided in the embodiments of this specification, through page prototype, module configuration and field configuration, the system can dynamically generate personalized page instances according to user needs to meet the customization needs of different users, and through preset common modules and full field pools, the system can flexibly combine and configure pages, reduce repeated development, and improve development efficiency.

[0038] In one or more embodiments of this specification, before a user initiates a request to create a page instance, the module should first be developed and configured so that the user can conveniently use the module to create a page instance. The specific implementation is as follows: Before creating the page prototype according to the user information carried in the page instance creation request, the method further includes: Obtaining a general module and module information of the general module; Determine the front-end components and application interfaces corresponding to the general module, and set a corresponding full field pool for the general module.

[0039] Specifically, first obtain the common modules. These modules are pre-defined and have specific functions. Each common module has its module information, including the module name, code, function description, etc., which are used to identify and describe the module; each common module is associated with a front-end component, which is used to render the module view on the page. At the same time, each common module is also associated with an application interface, which is used to process the module's project logic, such as data query, addition, update, deletion and other operations; set a full field pool for each common module. The field pool contains all available fields of the module. These fields are the basic units for data input or display in the module. Users can select the required fields from the field pool for configuration according to their needs.

[0040] In fact, the developers of the SaaS platform develop general modules, application processing interfaces, and create data models, etc. That is, the SaaS platform developers implement the basic application capability development and general data model development of SaaS services in a type of project scenario.

[0041] The target page display method provided in the embodiment of this specification predefines common modules and their module information, so that the system can realize module reuse, reduce repeated development, and significantly improve development efficiency. The front-end components and application interfaces associated with the common modules enable the modules to be flexibly configured in different pages to meet the personalized needs of different users. By separating the front-end components from the application interfaces, the system realizes the separation of project logic and view, so that modifications to the project logic will not affect the front-end view, thereby improving the maintainability and scalability of the system.

[0042] In one or more embodiments of this specification, creating a data model corresponding to a common module and determining the application interface corresponding to the common module by exposing the operation interface of the data model is a key step in achieving multi-tenant data isolation and modular configuration. The specific implementation is as follows: The determining of the application interface corresponding to the universal module includes: A data model and a common module corresponding to the data model are created, and an application interface corresponding to the common module is determined by exposing the operation interface of the data model; wherein the data model isolates the user data through a user information field.

[0043] Among them, the data model is the underlying structure used to store and process module-related data. Each common module has a corresponding data model for persisting module-related data.

[0044] In fact, when creating a data model, the system will use DDL (Data Definition Language) statements to define the database table structure. The data model contains the fields required by the module and supports data addition, deletion, modification and query operations; and the data model contains a user information field (such as user ID) to distinguish the data of different users and ensure data isolation in a multi-user environment.

[0045] The data model is the basis for creating common modules. The data model defines the structure of the data being processed. For example, taking the order data model as an example, the order data model may include fields such as order number, order amount, and user number. The steps to create an order display module based on the order data model can be as follows: Determine the module code of the order display module to identify the module; and based on the fields in the order data model, the front-end component corresponding to the order display module can be designed as an order number display component, and this component is a tabular component; and the field configuration information corresponding to each field in the order display module can be designed. The field configuration information defines the display rules and behaviors of each field in the module, such as the rules for allowing reading and not allowing writing of a certain field.

[0046] Specifically, after the data model is created, the system will expose the operation interface of the data model for the front-end or other services to call. For example, these interfaces include query interface (used to obtain module data), add interface (used to add new data to the module), update interface (used to modify data in the module), delete interface (used to delete data in the module), etc.; these interfaces are the application interfaces of the general module, which are used to process the project logic of the module.

[0047] In a multi-tenant environment, data from different tenants must be strictly isolated. This is achieved in the data model through user information fields (such as the tenant ID). When a tenant accesses data, the system filters the data based on the user information fields to ensure that each tenant can only access their own data. For example, when querying data, the system automatically adds the tenant ID as a query condition to ensure that the returned data belongs only to the current tenant.

[0048] The application interface of the common module is implemented through the operation interface of the data model. These interfaces associate the view actions of the front-end module (such as user interaction) with the project logic of the back-end data model. For example, when the user clicks the "Query" button on the front-end page, the front-end will call the back-end query interface, and the back-end will filter the data according to the tenant ID and return the results.

[0049] The target page display method provided in the embodiment of this specification realizes data isolation through user information fields, ensures that the data of different tenants do not interfere with each other, and enhances the security and compliance of the system; through user information fields and unified data model design, the system can efficiently support multi-tenant scenarios and meet the personalized needs of different tenants.

[0050] In one or more embodiments of the present specification, the generated target page instance is published so as to be accessible to users. The specific implementation is as follows: After obtaining the target page instance according to the page prototype, the module configuration information, and the field configuration information, the method further includes: The target page instance is published, and the target page instance is stored in a page instance resource and cached in a page instance cache according to page dimensions.

[0051] The publishing operation usually includes saving the relevant configuration information of the page instance (such as module configuration, field configuration, etc.) into the database and generating the corresponding access URL.

[0052] Specifically, the target page instance after publication will be stored in the page instance resource. The page instance resource can be understood as a persistent storage system (such as a database or file system) used to store the configuration information and related data of the page instance for a long time. The stored content includes the page instance identifier, module configuration information, field configuration information, user information, etc.

[0053] To improve page access efficiency, the system caches page instance configuration information in a page instance cache based on page dimensions. Page dimension caching refers to caching per page instance, rather than per module or field. The cached content includes page instance configuration information, module configuration information, field configuration information, and more. When a user accesses a page, the system can quickly retrieve this information from the cache, eliminating the need to read it from persistent storage each time, thereby improving page rendering speed.

[0054] The target page display method provided in the embodiments of this specification caches page instances in a page instance cache, so that the system can quickly respond to users' page access requests, significantly improve page rendering speed, and improve user experience. In addition, the configuration information of the page instance will be cached after the first access, and subsequent accesses will be directly read from the cache, reducing frequent queries to the database and reducing the pressure on the database.

[0055] In one or more embodiments of this specification, when a user initiates a request to access a target page, the system retrieves the configuration information of the page instance from the page instance cache based on the page instance identifier (i.e., the unique identifier of the page) and user information (such as user identity, permissions, etc.) carried in the request. Specific implementations are as follows: The step of obtaining the page instance configuration information according to the page instance identifier and user information carried in the target page access request includes: According to the page instance identifier and user information carried in the target page access request, the target page instance is obtained from the page instance cache, and the page instance configuration information corresponding to the target page instance is determined.

[0056] Specifically, obtaining the target page instance from the page instance cache according to the page instance identifier and user information carried in the target page access request includes: According to the page instance identifier and user information carried in the target page access request, it is determined whether the target page instance is cached in the page instance cache. If so, obtaining the target page instance from the page instance cache; If not, the target page instance and the page instance configuration information of the target page instance are acquired from the page instance resource according to the page instance identifier and stored in the page instance cache, and the target page instance is obtained from the page instance cache.

[0057] In specific implementation, the target page instance is first searched from the page instance cache based on the page instance identifier and user information. The page instance cache is a high-speed cache system (such as Redis) used to store the configuration information of the page instance to improve the efficiency of page access. If the configuration information of the target page instance exists in the cache (i.e., cache hit), the system will directly obtain the configuration information of the page instance from it. If the configuration information of the target page instance does not exist in the cache (i.e., cache miss), the configuration information of the page instance is obtained from the page instance resource (such as a database), and the obtained configuration information is cached in the page instance cache according to the page dimension so that it can be quickly obtained during subsequent access.

[0058] The target page display method provided in the embodiments of this specification retrieves the configuration information of the target page instance from the page instance cache, enabling the system to efficiently respond to user page access requests, significantly improving page rendering speed and user experience. This caching mechanism not only reduces database pressure but also supports dynamic updates and multi-tenant data isolation, ensuring system flexibility, scalability, and security.

[0059] Step 204: Determine the target component and target application interface according to the module configuration information.

[0060] The target component can be understood as the front-end component that needs to be rendered on the page. These components are associated with the modules defined in the module configuration information. Each general module has its own corresponding front-end component, which is used to display the module's content and functions on the page. The target application interface can be understood as the back-end interface associated with the module defined in the module configuration information, which is used to process the module's project logic (such as querying, adding, updating, and deleting data). Each module has its own corresponding application interface, which is determined by the application code or interface identifier in the module configuration information.

[0061] Specifically, according to the module code or module name in the module configuration information, the system searches and loads the corresponding front-end component from the front-end component resource library, and according to the interface identifier in the module configuration information, the system searches and calls the corresponding interface from the application interface library.

[0062] In fact, the module code or module name is extracted from the module configuration information, and the corresponding front-end component is found from the front-end component resource library based on the module code or name. The front-end component is loaded and rendered to ensure that the page can correctly display the content of the module; the application code or interface identifier is extracted from the module configuration information, and the corresponding back-end interface is found from the application interface library based on the application code or interface identifier, so as to realize the calling of the interface to process the processing logic of the general module (such as querying data, submitting forms, etc.).

[0063] The target page display method provided in the embodiment of this specification can efficiently render the page by quickly determining the target component and target application interface from the module configuration information, thereby improving the page loading speed and user experience. The target component is responsible for rendering the page view, and the target application interface is responsible for processing the project logic, thereby realizing the separation of processing logic and view, and improving the maintainability and scalability of the system.

[0064] In one or more embodiments of this specification, in the process of determining the target component according to the module configuration information, the target component is efficiently loaded through the front-end resource cache and the front-end resource library. The specific implementation is as follows: The determining of the target component according to the module configuration information includes: According to the module configuration information, it is determined whether the target component is cached in the front-end resource cache, wherein the target component is determined by the target module corresponding to the module configuration information, If so, obtaining the target component from the front-end resource cache; If not, the target component's resources are obtained from the front-end resource library to the front-end resource cache, and the target component is obtained from the front-end resource cache.

[0065] Specifically, first determine the target component based on the module code or module name in the module configuration information, and check whether the target component has been cached in the front-end resource cache, which is used to store commonly used front-end component resources to improve page loading speed.

[0066] If the target component has been cached in the front-end resource cache (i.e., cache hit), the system will directly obtain the component's resources from the cache. This method avoids repeated loading of component resources and significantly improves page rendering efficiency. If the target component is not cached in the front-end resource cache (i.e., cache miss), the following steps will be performed: obtain the target component's resources from the front-end resource library. The front-end resource library is a persistent storage system (such as CDN or server file system) used to store the resources of all front-end components. The obtained target component resources are stored in the front-end resource cache so that they can be quickly obtained during subsequent access; load the target component resources from the cache for page rendering.

[0067] In fact, the front-end resource cache only needs to cache the component resources brought in by fixed common modules, and there is no need to load resources due to changes in user page configuration information.

[0068] The target page display method provided in the embodiment of this specification uses front-end resource caching to enable the system to quickly load target component resources, significantly improve page rendering speed, and improve user experience. In fact, the target component resources will be cached after the first loading, and subsequent accesses will be read directly from the cache, reducing the time for loading resources from the remote resource library and reducing network latency; and the caching mechanism of the target component supports modular design, so that component resources can be reused in different pages, reducing repeated loading and improving development efficiency.

[0069] In one or more embodiments of this specification, determining the target application interface according to the module configuration information includes: The target module is determined according to the module configuration information, and the target application interface corresponding to the target module is determined.

[0070] Specifically, the module code or module name is extracted from the module configuration information to determine the target module; the target module is a functional unit in the page with specific capabilities (such as data display, form submission, etc.), and each target module is associated with one or more application interfaces, which are used to process the module's project logic (such as data query, addition, update, deletion, and other operations); the system determines the target application interface corresponding to the target module based on the application code or interface identifier in the module configuration information.

[0071] For details, please refer to the above embodiments and will not be described in detail here.

[0072] Step 206: calling the target application interface to obtain target data corresponding to the field configuration information from a target database, wherein the target database is a database determined according to the module configuration information; Among them, the target application interface can be understood as the service interface provided by the back-end application, which is used to process the project logic of the module (such as data query, addition, update, deletion and other operations); the target database can be understood as the database determined according to the module configuration information, which is used to store project data related to the module.

[0073] Specifically, in a multi-tenant environment, the target database may be a shared database or an independent database allocated to a specific tenant. The system will determine the specific database instance based on user information (such as tenant ID).

[0074] For example, in existing approaches, SaaS service providers provide database-level tenant data isolation by assigning each tenant a database. The platform provides a basic model for project functionality and Data Definition Language (DDL) operations for the database model. The platform stores user-saved page configuration information in the tenant's database. Different tenants can define and modify their own data definitions for page rendering within their own databases. When a user accesses a page, the platform routes the user to the corresponding tenant's database based on the user's access path and parameters, enabling page rendering across different tenants.

[0075] In this scenario, the SaaS service provider platform needs to provide each tenant with a database. This, combined with the need to accelerate front-end resources through methods like CDN, results in a waste of storage resources. Furthermore, storing data in multiple databases can reduce query efficiency and impact page rendering speed. Tenants have DDL permissions, allowing them to customize the database physical model. This can make customized data models uncontrollable and lead to conflicts during subsequent platform model definition upgrades.

[0076] Alternatively, in the existing method, the SaaS service provider platform defines the common metadata of the project by defining metadata. The platform stores the standard objects and standard field definitions of the application system, and defines and describes the structure of the underlying data. The fields required by each tenant can be defined and used in specific pages from the common metadata, and tenant-specific metadata is provided on the basis of the common metadata, which stores the definitions of tenant-automatic objects and customized fields, and is used to define and describe the structure of the underlying data. The platform provides PAAS layer platform services, provides the creation of application object models, creates permission models, and creates layout pages for corresponding metadata for different tenants. The platform renders pages based on the metadata definitions and the model objects and page layouts created by the tenants.

[0077] However, in this case, because different tenants share the same metadata model, when different tenants perform operations such as field updates on the metadata model, they need to update the query views of all metadata related to the model. This results in slow data synchronization efficiency for the query views and also affects page rendering efficiency. Therefore, a more powerful query optimization tool is needed to avoid this situation.

[0078] Therefore, in the embodiments of this specification, the SaaS service provider creates a module based on a specific project model, and creates a data model of a corresponding module on the back end for data persistence. The SaaS service provider can implement the definition of a database model through DDL statements, and expose the operation interface corresponding to the data model for the module to call. The fields required for the same general module are different between different tenants, and the module styles are different. Processing and data isolation are performed through a unified interface and data model. Specifically, in addition to the basic fields required between all tenants, the back-end data model will provide a tenant attribute to isolate tenant data. The fields in the module field pool provide tenants with the ability to select on demand. Specifically, its fields are stored in a Map type attribute of the back-end model, and the corresponding database is a JSON format field. The interface can dynamically process the project logic interface according to the fields configured by the tenant through the unique key feature of the Map, thereby providing SaaS service developers with a lightweight and efficient interface hook method for dynamic project processing.

[0079] In fact, the target application interface will initiate a query request to the target database based on the field configuration information to obtain the target data corresponding to the field configuration information. The field configuration information defines the fields to be obtained (such as field name, field type, etc.). The target application interface will generate a query statement based on this information and extract the required data from the database. The query results will be returned to the front end for page rendering or further processing.

[0080] The target page display method provided in the embodiments of this specification determines the target database based on user information (such as tenant ID), ensuring that data from different tenants are isolated from each other, enhancing the security and compliance of the system. Field configuration information supports dynamic configuration, and users can select the fields to be displayed according to their needs. The system will dynamically generate query statements based on this configuration information to meet personalized needs.

[0081] In one or more embodiments of this specification, when calling a target application interface and obtaining target data corresponding to field configuration information from a target database, the target data is obtained from a target data set corresponding to user information in the target database. Specific implementations are as follows: The calling of the target application interface to obtain target data corresponding to the field configuration information from the target database includes: Calling the target application interface according to the module identifier of the target module; Determining, based on the target application interface and the user information, a target data model corresponding to the target module, and determining a target data set in a target database corresponding to the target data model and corresponding to the user information; Target data corresponding to the field configuration information is obtained from the target data set.

[0082] Specifically, according to the module identifier of the target module (such as module code or module name), the target application interface associated with the module is called. The target application interface determines the target data model corresponding to the target module based on user information (such as tenant ID). The target data model contains a user information field (such as tenant ID) to distinguish data of different users and ensure data isolation in a multi-tenant environment.

[0083] The target database is a database determined according to the target data model and is used to store module-related data. Based on user information fields (such as tenant ID), data related to the current user is filtered out from the target database to form a target dataset. That is, the target dataset is a subset of data related to the current user in the target database, ensuring data isolation and security.

[0084] The system extracts the required target data from the target dataset based on the field configuration information. The field configuration information defines the fields that need to be obtained (such as field name, field type, etc.). The system generates a query statement based on this information to extract the required data from the target dataset. The extracted target data will be returned to the front end for page rendering or further processing.

[0085] The target page display method provided in the embodiments of this specification determines the target data set through user information fields (such as tenant ID) to ensure that data of different users are isolated from each other. The design of the target data model and application interface supports modularization. Different modules can reuse the same data model and interface, reducing duplication of development and improving development efficiency. In addition, the design of the target database and data model supports multi-tenant scenarios. The system can dynamically switch data sets based on user information to ensure that data of different users are isolated and processed independently.

[0086] Step 208: Render and display the target page according to the target component and the target data.

[0087] Specifically, the target component is a front-end component determined according to the module configuration information, which is used to display the content and functions of the module on the page. The system loads the resources of the target component (such as HTML, CSS, JavaScript, etc.) from the front-end resource cache or front-end resource library and renders them on the page; the target data is obtained from the target database and corresponds to the field configuration information. The target data is bound to the corresponding field of the target component to ensure that the component can display the data correctly.

[0088] For example, if the target component is a table component, the system will fill the target data into the rows and columns of the table; if the target component is a form component, the system will fill the target data into the input boxes of the form.

[0089] In fact, according to the configuration information of the page instance (such as module configuration information, field configuration information, etc.), the target component and target data are combined to render a complete target page; after the rendering is completed, the system displays the target page to the user, and the user can access the URL corresponding to the page through the browser to view and interact with the target page.

[0090] The target page display method provided in the embodiments of this specification is designed to avoid the SaaS service provider platform needing to provide each tenant with a database, resulting in storage resource waste and repeated development problems in the same project scenario. In this specification, a common module and a unified data model are used to achieve that different tenants share the underlying model and infrastructure in the same project scenario, and support data isolation between different tenants and personalized customization of modules for project needs.

[0091] In order to avoid the problem of low page rendering efficiency of SaaS services and the need to cache a large number of front-end resources for different tenants, this manual designs a dynamic page rendering method to achieve the sharing of front-end resource cache among different tenants. By dynamically obtaining the configuration information of different tenants' pages and caching the configuration information according to the page dimension, the page rendering speed is greatly increased and the cost of resource storage is reduced.

[0092] To avoid uncontrollable model issues caused by the SaaS service providing tenants with DDL permissions and defining the data model, this specification introduces a modular development approach by designing two intermediate states for pages: page instances and page prototypes. This allows tenants to dynamically configure page views and provides permission control to isolate permissions at the user level. This ensures model availability while preventing tenants from directly interacting with the underlying application, making it more tenant-friendly and easier to use.

[0093] To avoid the problem of requiring updates to all metadata query views related to a piece of data when an update is performed on a metadata model, this specification defines a unified data model and uses modules to allow tenants to import required fields for storage and unified processing. This allows efficient project logic processing for fields imported by different tenants under a single application interface processing logic, avoiding updates to all related views caused by updates.

[0094] The embodiment of this specification also provides a page creation and display method, including: Creating a page prototype according to the user information carried in the page instance creation request, wherein the page prototype includes page information and user information; Determining a target module from a plurality of preset common modules corresponding to the page prototype, and obtaining module configuration information of the target module; Select a target field from the full field pool corresponding to the target module, and obtain field configuration information of the target field; Obtaining a target page instance according to the page prototype, the module configuration information, and the field configuration information, wherein a page instance identifier of the page instance is determined according to the page information, and page instance configuration information corresponding to the page instance is determined according to the module configuration information and the field configuration information; When a target page access request carrying a page instance identifier and user information is received, the target page display method described above is applied to render and display the target page.

[0095] The specific implementation method can be found in the above embodiments, which will not be described in detail here.

[0096] See also Figure 3a , Figure 3a A flowchart of a module configuration provided by an embodiment of this specification is shown, which specifically includes the following steps.

[0097] The SaaS service provider creates a data model and develops common modules corresponding to the data model.

[0098] The SaaS service provider creates a common module based on the data model of the specific project; a database model definition is created through DDL statements. The back-end data model is used for data persistence, and tenant data can be isolated by setting tenant properties of the data model.

[0099] Based on the specific project functions, the SaaS service provider can configure general modules such as query, details, list, and edit corresponding to the project functions, set the title, name, and code of the general module, bind the corresponding front-end component resources in the general module, and store and cache the front-end component resources. That is, the front-end component resources can be stored in the front-end component resource library and cached in the front-end component resource cache so that the front-end view component rendering can be efficiently obtained when the page is dynamically rendered. Set the application processing interface associated with the general module (i.e., the application interface in the above embodiment) and the data model corresponding to the application processing interface; set a full field pool for users to configure on demand.

[0100] For example, for a user management function, you can configure multiple related modules, including querying users (searching users based on conditions), viewing user details (viewing detailed information about a certain user), user list (displaying a list of all users), editing user information (modifying a user's basic information), and other general modules.

[0101] SaaS service providers develop application processing interfaces.

[0102] The SaaS service provider develops an application processing interface for the data model, including operations such as query, add, update, and delete; the application processing interface is associated with the database corresponding to the backend data model.

[0103] See also Figure 3b , Figure 3b A general module structure diagram provided in an embodiment of this specification is shown.

[0104] The general module structure is as follows Figure 3b As shown, the module title is used to display the module title when the page is rendered; the module name and module code are both globally unique identifiers to distinguish different modules; when the front-end component is used to dynamically obtain page configuration information, the corresponding view is rendered according to the front-end component of the module in the page; the associated application and interface are used to provide page dynamic rendering services. Specifically, the associated application is used for dynamic acquisition of specific pages, such as obtaining the corresponding page instance from the page instance cache through the associated application, and the interface is a bridge for the interaction between the module and the back-end data model, which can dynamically obtain the required data, such as determining the query interface based on the interactive operation of clicking the query button on the front end, thereby querying the corresponding data from the database); the persistence model (i.e., the data model in the above embodiment) is used to support the persistence of module field data and the isolation of tenant data. Different tenants use the same persistence model and support dynamic rendering of page fields according to the page instance information of different tenants. The front-end component information associated with the common module is saved in the front-end component resource library and the front-end component resource cache.

[0105] Specifically, the process of configuring the module includes: Before creating modules based on specific project requirements, SaaS service providers can create a unified data model to define the data structure handled by the module. This data model can also be used for data persistence. In this specification, SaaS service providers can use DDL statements to define a database model and expose the corresponding data model operation interface for module calls.

[0106] Develop an application processing interface, whose functions include associating the view actions of the front-end general module and the project processing logic of the back-end persistence model through the interface, including query, add, update, delete and other actions. The fields required for the same general module are different between different tenants and the module styles are different. This manual uses a unified interface and model for processing and data isolation. Specifically, in addition to the basic fields required between all tenants, the back-end persistence model will provide a tenant attribute to isolate tenant data. The fields in the module field pool provide tenants with the ability to select on demand. Specifically, its fields are stored in a Map type attribute of the back-end model, corresponding to the fields in the JSON format of the database. Through the unique key feature of the Map, the interface can dynamically process the project logic interface according to the fields configured by the tenant, thereby providing SaaS service developers with a lightweight and efficient interface hook method for dynamic project processing.

[0107] SaaS service providers publish front-end resources and back-end application processing interfaces.

[0108] Publish the front-end resources involved in the developed modules, reduce the time users spend acquiring front-end resources through CDN caching and other means, and publish the back-end application processing interface to realize the interaction of module interfaces.

[0109] When the service provider publishes the front-end resources of the common module, tenants can use the published front-end resources to instantiate and render pages. Specifically, Before tenants access the page, see Figure 3c , Figure 3c A schematic diagram of a process for creating and publishing a page instance provided in an embodiment of this specification is shown. The specific execution steps are as follows: Tenant creation page prototype.

[0110] Tenants who subscribe to SaaS services can create page prototypes. A page prototype includes page code, page name, and tenant information. By associating multiple modules in the page prototype, the project functions involved in the page are implemented.

[0111] Tenants select common modules as needed.

[0112] Specifically, according to the tenant's subscription level, the tenant's module usage rights can be set. For example, the higher the tenant's subscription level, the more modules the tenant can use, or the higher the tenant's subscription level, the higher the tenant's configuration rights for the modules that can be used. There is no limitation here.

[0113] Each tenant adds corresponding common modules to the page prototype according to the capabilities of the functions they subscribe to and the project functions they require. Modules cannot be added repeatedly to each page. Tenants can add modules only if they have the right to use the module, thus realizing module customization capabilities.

[0114] Tenant adds module configuration information.

[0115] After adding the required modules, tenants can add configuration information for each tenant's personalized part, including the module's addable, editable, and deletable functions, configurable cascading relationships between fields, and configurable module permission information, that is, the permissions of different users when rendering the page.

[0116] Required field for the tenant selection module.

[0117] The field pool of a general module contains all display fields that tenants can select on demand. Selected fields are dynamically rendered on the page, and field processing and field data rendering are performed according to the configured field supply application interface, thus enabling hot reloading of tenant-specific field configurations. In addition, based on the added fields, you can set field configuration information such as whether to display, read-only, and display order.

[0118] Tenant publishing page instance.

[0119] Publish the page instance, store it in the page instance resource after publishing, cache it according to the page dimension, and cache the page instance in the page instance cache.

[0120] See also Figure 3d , Figure 3d A schematic diagram of the processing process of a target page display method provided in an embodiment of this specification is shown.

[0121] When a user accesses a page, page rendering involves both module component rendering and target data rendering. Specifically, module component rendering retrieves the page instance configuration information based on the page request, obtains the page instance cache, and then retrieves front-end component resources from the front-end component resource cache based on the module information configured for the instance. Target data rendering retrieves the persistent data model from the application interface layer and invokes specific model project processing logic to render the target data for the module fields rendered on the page.

[0122] Tenant access page. Figure 3dAs shown in process 1.1, after the page instance is published, the tenant accesses the page through the URL corresponding to the page. The page sends a request to the server to obtain the page instance. In fact, the page passes the obtained tenant information and the code of the current page instance as parameters to the server.

[0123] The server obtains the page instance cache. Figure 3d As shown in process 1.2, the server obtains the page code and tenant information in the page instance, and obtains the cache information from the page instance cache according to the page instance dimension. If the cache hits, the configuration information of the page instance is obtained. If the cache does not hit, the configuration information of the page instance is obtained. Figure 3d As shown in processes 1.3 and 1.4, the page instance and associated module configuration information are obtained from the page instance resource according to the page code, and the page instance and module configuration information are loaded into the cache according to the page dimension.

[0124] Get the front-end component resource cache. Figure 3d As shown in process 1.5, the page rendering device filters the field information and module information according to the permissions of different user roles based on the user's access information, and then returns the page instance configuration information that the user can obtain. Through the dynamically returned page instance configuration information, the front-end component resource cache is requested and the front-end component is rendered on the page, realizing hot update and hot deployment of page rendering according to the tenant dimension. The front-end component resource cache only needs to cache the component resources brought in by the fixed common module, and there is no need to generate resource loading events due to changes in the user's page configuration information. Call the application interface. When a user interacts with a page module, the module's configured application interface takes user information and module code as parameters, and calls the corresponding application interface at the application interface layer to perform data interaction.

[0125] The application model processing layer handles specific project logic. Figure 3d As shown in processes 2.3.1 and 2.3.2, the model processing layer determines the data model corresponding to the module and obtains the corresponding data based on the called application interface. By combining the common module and the field information configured by the tenant, it implements multi-tenant project processing logic under the same data model and data isolation between different tenants. The project processing results are returned to the application interface according to the field data configured by the module.

[0126] Target data rendering. The application interface aggregates the return field values of the processing logic of each common module involved in this call to form the target data, and responds to the request to render the target data to the page.

[0127] The target page display method provided in the embodiments of this specification realizes dynamic rendering and hot update and hot deployment of pages according to page instances configured for different tenants, reuses page cache resources, and realizes efficient project logic processing for fields introduced by different tenants under a set of application interface processing logic by defining a unified data model. By defining modules, page prototypes, and page instances, the common attribute functions and personalized attributes and functions between different tenants are controlled in different dimensions, so that the personalized needs of different tenants can be accurately controlled under the same underlying application. The modules have specific capabilities and can be freely combined and configured to ensure efficient interaction between the front end and the server, and realize flexible configuration and efficient rendering of pages in a multi-tenant environment.

[0128] Corresponding to the above method embodiment, this specification also provides a target page display device embodiment, Figure 4 FIG. 1 shows a schematic diagram of a target page display device provided by an embodiment of this specification. Figure 4 As shown, the device includes: The information determination module 402 is configured to obtain page instance configuration information according to the page instance identifier and user information carried in the target page access request, wherein the page instance configuration information includes module configuration information and field configuration information; A target determination module 404 is configured to determine a target component and a target application interface according to the module configuration information; The data acquisition module 406 is configured to call the target application interface to obtain target data corresponding to the field configuration information from a target database, wherein the target database is a database determined according to the module configuration information; The rendering and display module 408 is configured to render and display the target page according to the target component and the target data.

[0129] Optionally, the information determination module 402 is further configured to: According to the page instance identifier and user information carried in the target page access request, the target page instance is obtained from the page instance cache, and the page instance configuration information corresponding to the target page instance is determined.

[0130] Optionally, the information determination module 402 is further configured to: According to the page instance identifier and user information carried in the target page access request, it is determined whether the target page instance is cached in the page instance cache. If so, obtaining the target page instance from the page instance cache; If not, the target page instance and the page instance configuration information of the target page instance are acquired from the page instance resource according to the page instance identifier and stored in the page instance cache, and the target page instance is obtained from the page instance cache.

[0131] Optionally, the target determination module 404 is further configured to: According to the module configuration information, it is determined whether the target component is cached in the front-end resource cache, wherein the target component is determined by the target module corresponding to the module configuration information, If so, obtaining the target component from the front-end resource cache; If not, the target component's resources are obtained from the front-end resource library to the front-end resource cache, and the target component is obtained from the front-end resource cache.

[0132] Optionally, the target determination module 404 is further configured to: The target module is determined according to the module configuration information, and the target application interface corresponding to the target module is determined.

[0133] Optionally, the data acquisition module 406 is further configured to: Calling the target application interface according to the module identifier of the target module; Determining, based on the target application interface and the user information, a target data model corresponding to the target module, and determining a target data set in a target database corresponding to the target data model and corresponding to the user information; Target data corresponding to the field configuration information is obtained from the target data set.

[0134] The device further comprises: The page creation module is configured to create a page prototype based on the user information carried in the page instance creation request, wherein the page prototype includes page information and user information; determine the target module from multiple preset common modules corresponding to the page prototype, and obtain the module configuration information of the target module; select the target field from the full field pool corresponding to the target module, and obtain the field configuration information of the target field; obtain the target page instance based on the page prototype, the module configuration information and the field configuration information, wherein the page instance identifier of the page instance is determined based on the page information, and the page instance configuration information corresponding to the page instance is determined based on the module configuration information and the field configuration information.

[0135] The device further comprises: The page publishing module is configured to publish the target page instance, store the target page instance in a page instance resource, and cache the target page instance in a page instance cache according to page dimensions.

[0136] The device further comprises: The module configuration module is configured to obtain a general module and module information of the general module; determine the front-end component and application interface corresponding to the general module, and set a corresponding full field pool for the general module.

[0137] Optionally, the module configuration module is further configured to: A data model and a common module corresponding to the data model are created, and an application interface corresponding to the common module is determined by exposing the operation interface of the data model; wherein the data model isolates the user data through a user information field.

[0138] A target page display device provided by an embodiment of the present specification obtains page instance configuration information based on the page instance identifier and user information carried in the received target page access request. When the page instance configuration information includes module configuration information and field configuration information, the target component and target application interface are determined based on the module configuration information. That is, by providing modular configuration capabilities, each user can obtain corresponding page instance configuration information based on user information and page instance identifiers, so that in multi-tenant similar project scenarios, different users can quickly launch pages according to their personalized functional requirements. By calling the target application interface, the target data corresponding to the field configuration information is obtained from the target database. When the target page is rendered and displayed according to the target component and target data, the user-configured target page is dynamically rendered according to the page instance configuration information corresponding to different users. The modules have specific capabilities and can be freely combined and configured, so that flexible configuration and efficient rendering of pages in a multi-tenant environment can be achieved, reducing waste of storage resources and improving page rendering speed.

[0139] The above is a schematic diagram of a target page display device according to this embodiment. It should be noted that the technical solution of the target page display device and the technical solution of the target page display method described above are based on the same concept. For details not described in detail in the technical solution of the target page display device, please refer to the description of the technical solution of the target page display method described above.

[0140] Figure 5The block diagram of a computing device 500 according to one embodiment of the present disclosure is shown. Components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and a database 550 is used to store data.

[0141] The computing device 500 also includes an access device 540 that enables the computing device 500 to communicate via one or more networks 560. Examples of such networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 540 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, or near field communication (NFC).

[0142] In one embodiment of the present specification, the above components of the computing device 500 and Figure 5 Other components not shown in the figure may also be connected to each other, for example, via a bus. Figure 5 The computing device structure block diagram shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art may add or replace other components as needed.

[0143] Computing device 500 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, personal digital assistant, laptop computer, notebook computer, netbook computer, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smartwatch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or personal computer (PC). Computing device 500 can also be a mobile or stationary server.

[0144] The processor 520 is configured to execute the following computer program / instructions, which, when executed by the processor, implement the steps of the target page display method and the page creation and display method.

[0145] Each embodiment in this specification is described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences from other embodiments. In particular, the computing device embodiment is generally similar to the target page display method and page creation display method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the target page display method and page creation display method embodiments.

[0146] An embodiment of the present specification further provides a computer-readable storage medium storing a computer program / instruction, which, when executed by a processor, implements the steps of the above-mentioned target page display method and page creation and display method.

[0147] Each embodiment in this specification is described in a progressive manner. Similar or identical parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences from other embodiments. In particular, the computer-readable storage medium embodiment is generally similar to the target page display method and page creation display method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the target page display method and page creation display method embodiments.

[0148] An embodiment of the present specification further provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of the above-mentioned target page display method and page creation and display method.

[0149] The above is a schematic diagram of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product shares the same concept as the technical solutions of the target page display method and the page creation display method described above. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solutions of the target page display method and the page creation display method described above.

[0150] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0151] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium may include any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium. It should be noted that the content of the computer-readable medium may be appropriately increased or decreased based on the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media does not include electric carrier signals and telecommunication signals.

[0152] It should be noted that for the aforementioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0153] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0154] The preferred embodiments disclosed above are intended only to help illustrate this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made based on the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that those skilled in the art can better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A target page display method, comprising: Obtaining page instance configuration information according to the page instance identifier and user information carried in the target page access request, wherein the page instance configuration information includes module configuration information and field configuration information; Determine the target component and target application interface according to the module configuration information; Calling the target application interface to obtain target data corresponding to the field configuration information from a target database, wherein the target database is a database determined according to the module configuration information; Render and display the target page according to the target component and the target data.

2. The target page display method according to claim 1, wherein obtaining the page instance configuration information based on the page instance identifier and user information carried in the target page access request comprises: According to the page instance identifier and user information carried in the target page access request, the target page instance is obtained from the page instance cache, and the page instance configuration information corresponding to the target page instance is determined.

3. The target page display method according to claim 2, wherein obtaining the target page instance from the page instance cache based on the page instance identifier and user information carried in the target page access request comprises: According to the page instance identifier and user information carried in the target page access request, it is determined whether the target page instance is cached in the page instance cache. If so, obtaining the target page instance from the page instance cache; If not, the target page instance and the page instance configuration information of the target page instance are acquired from the page instance resource according to the page instance identifier and stored in the page instance cache, and the target page instance is obtained from the page instance cache.

4. The target page display method according to any one of claims 1 to 3, wherein determining the target component according to the module configuration information comprises: According to the module configuration information, it is determined whether the target component is cached in the front-end resource cache, wherein the target component is determined by the target module corresponding to the module configuration information, If so, obtaining the target component from the front-end resource cache; If not, the target component's resources are obtained from the front-end resource library to the front-end resource cache, and the target component is obtained from the front-end resource cache.

5. The target page display method according to claims 1-3, wherein determining the target application interface according to the module configuration information comprises: Determine the target application interface corresponding to the target module according to the target module determined by the module configuration information; The calling of the target application interface to obtain target data corresponding to the field configuration information from the target database includes: Calling the target application interface according to the module identifier of the target module; Determining, based on the target application interface and the user information, a target data model corresponding to the target module, and determining a target data set in a target database corresponding to the target data model and corresponding to the user information; Target data corresponding to the field configuration information is obtained from the target data set.

6. The target page display method according to claim 1, before obtaining the page instance configuration information based on the page instance identifier and user information carried in the target page access request, further comprising: Creating a page prototype according to the user information carried in the page instance creation request, wherein the page prototype includes page information and user information; Determining a target module from a plurality of preset common modules corresponding to the page prototype, and obtaining module configuration information of the target module; Select a target field from the full field pool corresponding to the target module, and obtain field configuration information of the target field; A target page instance is obtained based on the page prototype, the module configuration information and the field configuration information, wherein the page instance identifier of the page instance is determined based on the page information, and the page instance configuration information corresponding to the page instance is determined based on the module configuration information and the field configuration information.

7. The target page display method according to claim 6, before creating the page prototype according to the user information carried in the page instance creation request, further comprising: Obtaining a general module and module information of the general module; Determine the front-end components and application interfaces corresponding to the general module, and set a corresponding full field pool for the general module.

8. The target page display method according to claim 7, wherein determining the application interface corresponding to the universal module comprises: Create a data model and a common module corresponding to the data model, and determine the application interface corresponding to the common module by exposing the operation interface of the data model, wherein the data model isolates user data through user information fields.

9. A method for creating and displaying a page, comprising: Creating a page prototype according to the user information carried in the page instance creation request, wherein the page prototype includes page information and user information; Determining a target module from a plurality of preset common modules corresponding to the page prototype, and obtaining module configuration information of the target module; Select a target field from the full field pool corresponding to the target module, and obtain field configuration information of the target field; Obtaining a target page instance according to the page prototype, the module configuration information, and the field configuration information, wherein a page instance identifier of the page instance is determined according to the page information, and page instance configuration information corresponding to the page instance is determined according to the module configuration information and the field configuration information; When a target page access request carrying a page instance identifier and user information is received, the target page display method according to any one of claims 1 to 8 is applied to render and display the target page.

10. A computing device comprising: memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer program / instructions are executed by the processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images