An industrial management platform runtime configuration page generation method and system

Abstract

The application provides an industrial management platform runtime configuration page generation method and system. The method comprises: storing entity metadata, menu configuration and business operation configuration of a server into a front-end runtime container when a front-end application starts; generating a page entrance carrying a page type and a page parameter according to the menu configuration, and determining a page state according to the page entrance; generating a general entity page instance using the entity metadata pointed by the page parameter according to the page type, or generating a complex business dedicated page instance using a corresponding component construction function; associating the page instance to the page state, and storing the page state into a page state set; and rendering the page state set into a personal computer end multi-tab page or a mobile end page stack according to a terminal type and the business operation configuration. The application can reduce standard page repeated development, make the two types of pages share the page entrance and the page state management, and realize multi-terminal adaptation of the page state set.

Description

Technical Field

[0001] This application relates to the field of industrial management platform page generation technology, and more specifically, to a method and system for generating runtime configurable pages for an industrial management platform. Background Technology

[0002] In industrial management platforms such as smart warehousing and robotic fleet management, the system typically includes both a large number of standard business objects and complex business interfaces. Standard business object interfaces usually feature list queries, detailed viewing, editing and saving, batch operations, access control, and menu entry points, while complex business interfaces offer robust business interactions such as maps, real-time status displays, workflow orchestration, control panels, and alarm linkage. In field delivery, different customers, projects, and versions may also have varying business fields, menu structures, permission ranges, mobile interaction methods, and field expansion requirements.

[0003] In existing solutions, list pages, detail pages, and edit pages are typically developed separately for each standard business object. While common low-code or dynamic form solutions rely on metadata to generate standard forms, existing solutions may still employ independent development methods for complex industrial pages such as map scheduling, robot status monitoring, path planning, task flow orchestration, and equipment control.

[0004] In existing solutions, when the fields, permissions, validation, display rules, or menu entries of standard business objects change, developing separate pages requires simultaneous modifications to multiple front-end components and interface adaptation logic, which is prone to omissions and interaction differences. Ordinary low-code or dynamic form solutions are insufficient for complex industrial pages, while developing complex pages independently creates a disconnect between them and standard business pages in terms of navigation, permissions, mobile adaptation, internationalization, and page lifecycle. Furthermore, when on-site configuration changes require a re-release of the front-end version, it is difficult to meet the requirements of rapid deployment, rapid configuration, and continuous operation and maintenance, and there is also the problem of separation between navigation status on PCs and mobile devices.

[0005] Therefore, this application provides a method and system for generating runtime configuration pages for an industrial management platform to solve one of the aforementioned technical problems. Summary of the Invention

[0006] The purpose of this application is to provide a method and system for generating runtime configuration pages for an industrial management platform, which can solve at least one of the technical problems mentioned above. The specific solution is as follows: According to a specific embodiment of this application, in a first aspect, this application provides a method for generating a runtime configurable page for an industrial management platform, executed by a front-end application. The front-end application includes a front-end runtime container, a menu generation module, a page state management module, a page builder, and a multi-terminal adaptation module. The method includes: In response to the startup of the front-end application, entity metadata, menu configuration, and business operation configuration are obtained from the server and stored in the front-end runtime container. The menu generation module generates a page entry carrying page type and page parameters according to the menu configuration in the front-end runtime container. In response to the page entry being triggered, the page state management module determines the page state according to the page entry and sends it to the page builder and the page state. In response to the page type corresponding to a general entity page, the page builder generates the page instance according to the entity metadata pointed to by the page parameters. In response to the page type corresponding to a complex business-specific page, the page builder determines the corresponding component construction function according to the page type and uses the component construction function to generate the page instance. The page state management module associates the page instance with the page state and stores the page state in a page state set. The multi-terminal adaptation module renders the page state set into a PC multi-tab page or a mobile page stack according to the terminal type and the business operation configuration.

[0007] According to a specific implementation of this application, in a second aspect, this application provides an industrial management platform runtime configurable page generation system, including a front-end runtime container set in the front-end application, a menu generation module, a page state management module, a page builder, and a multi-terminal adaptation module. The front-end runtime container is used to retrieve and store entity metadata, menu configuration, and business operation configuration from the server in response to the startup of the front-end application. The menu generation module is used to read the menu configuration in the front-end runtime container and generate a page entry carrying page type and page parameters. The page state management module is used to determine the page state based on the page entry when the page entry is triggered, send the page entry and the page state to the page builder, associate the page instance returned by the page builder with the page state, and store the page state in a page state set. The page builder is used to send a page instance to the page state management module: in response to a general entity page corresponding to the page type, it generates the page instance based on the entity metadata pointed to by the page parameters; in response to a complex business-specific page corresponding to the page type, it determines the corresponding component construction function based on the page type and uses the component construction function to generate the page instance. The multi-terminal adaptation module is used to render the page state set into a PC multi-tab page or a mobile page stack based on the terminal type and the business operation configuration.

[0008] Compared with the prior art, the above-described solutions of this application have at least the following beneficial effects: This application provides a runtime configurable page generation method for an industrial management platform. When the front-end application starts, the front-end runtime container receives and stores the entity metadata, menu configuration, and business operation configuration from the storage server. The menu generation module generates a page entry carrying the page type and page parameters accordingly, and the page state management module determines the page state based on this. Furthermore, the page builder generates general entity page instances and complex business-specific page instances based on the page type, utilizing entity metadata and component construction functions respectively. This approach reduces redundant development of standard pages and allows for shared page entry and page state management. In addition, after associating page instances with page states, the page states are stored in a page state set. Then, the multi-terminal adaptation module renders the page state set as a multi-tab page for PCs or a page stack for mobile devices based on the terminal type and business operation configuration, thus unifying the semantics of page states across multiple terminals. Attached Figure Description

[0009] Figure 1 An exemplary flowchart illustrates a method for generating runtime configuration pages for an industrial management platform; Figure 2 An exemplary flowchart illustrates a method for menu permission filtering and terminal menu generation; Figure 3 An example diagram illustrating the relationship between an entity metadata structure and page construction rules is provided. Figure 4 An exemplary flowchart illustrates a method for generating a general entity list page instance; Figure 5 An exemplary flowchart illustrates a method for generating a general entity details page instance; Figure 6 An exemplary flowchart illustrates a method for generating a general entity editing page instance; Figure 7 An exemplary flowchart illustrates a method for generating complex business-specific page instances; Figure 8 An example flowchart illustrates a method for determining page status; Figure 9 An exemplary flowchart illustrates a method for page replacement, return, and closing; Figure 10 An exemplary flowchart illustrates a method for rendering a multi-terminal page state collection; Figure 11 An example is shown in a user permission control relationship diagram; Figure 12 The diagram illustrates the structure and data interaction of a runtime configurable page generation system for an industrial management platform. Detailed Implementation

[0010] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0011] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, and “multiple” generally includes at least two unless the context clearly indicates otherwise.

[0012] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

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

[0014] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0015] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a product or system. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the product or system that includes said element.

[0016] It should be noted that any symbols and / or numbers present in the specification that are not marked in the accompanying drawings are not reference numerals.

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

[0018] The embodiments provided in this application are embodiments of a method for generating runtime configuration pages for an industrial management platform.

[0019] The following is combined Figure 1 The embodiments of this application will be described in detail.

[0020] Figure 1 An exemplary flowchart illustrates a method for generating runtime configuration pages for an industrial management platform.

[0021] Reference Figure 1 The method is executed by the front-end application, which includes a front-end runtime container, a menu generation module, a page state management module, a page builder, and a multi-terminal adaptation module. The method includes the following steps: S101. In response to the startup of the front-end application, retrieve entity metadata, menu configuration and business operation configuration from the server and store them in the front-end runtime container. S102. The menu generation module generates a page entry carrying page type and page parameters based on the menu configuration in the front-end runtime container. S103. In response to the page entry being triggered, the page state management module determines the page state based on the page entry and sends the page entry and page state to the page builder. S104a. In response to the general entity page corresponding to the page type, the page builder generates a page instance based on the entity metadata pointed to by the page parameters. S104b: In response to a complex business-specific page corresponding to a page type, the page builder determines the corresponding component construction function based on the page type and uses the component construction function to generate a page instance. S105. The page state management module associates the page instance with the page state and stores the page state in the page state collection; S106. The multi-terminal adaptation module renders the page state set into a multi-tab page on a personal computer or a page stack on a mobile device, based on the terminal type and business operation configuration.

[0022] In this embodiment, the front-end application calls the server-side initialization interface after startup. The server issues entity metadata, menu configuration, and business operation configuration through the initialization interface, and the front-end application writes these three types of configurations into the front-end runtime container.

[0023] In one specific implementation, the front-end runtime container includes an entity metadata container, a menu container, and a runtime configuration container. Entity metadata is written to the entity metadata container, menu configuration is written to the menu container, and business operation configuration is written to the runtime configuration container.

[0024] For example, entity metadata, menu configuration, and business operation configuration can use structured configuration objects. These three types of configurations are associated through entity identifiers, menu identifiers, page types, and page parameters. Specifically, menu configuration determines the page type and page parameters corresponding to the page entry point, the entity identifier in the page parameters points to the corresponding entity metadata, and business operation configuration is used to determine the interaction form between the page container and the mobile terminal during the terminal adaptation process.

[0025] For example, the menu generation module reads the menu configuration from the front-end runtime container and generates a page entry based on the menu configuration. After the user triggers the page entry, the page state management module reads the page type and page parameters from the page entry and creates a new page state or activates an existing page state based on the page type and page parameters.

[0026] In some embodiments, the page state management module sends the page entry and the determined page state to the page builder, enabling the page builder to obtain the page type, page parameters, and the page state corresponding to this page opening process.

[0027] In this embodiment, the page builder selects the generation branch of the page instance based on the page type.

[0028] For example, when the page type corresponds to a generic entity page, the page parameter points to the entity metadata to be used, and the page builder generates a generic entity page instance based on the entity metadata.

[0029] For example, when the page type corresponds to a complex business-specific page, the page builder determines the component construction function based on the page type and uses the component construction function to generate a complex business-specific page instance.

[0030] In this embodiment, the page state management module receives a page instance, associates the page instance with the page state corresponding to the current page opening process, and stores the associated page state into a page state set. Based on this, the multi-terminal adaptation module reads the page state set and, in conjunction with the terminal type and business operation configuration, renders the page state set as a multi-tab page for a personal computer or a page stack for a mobile device.

[0031] In this embodiment, since entity metadata, menu configuration, and business operation configuration are issued by the server when the front-end application starts, driving subsequent menu generation, page construction, and terminal adaptation, adjustments to standard business objects, menu entries, and terminal display methods can enter the same processing chain through corresponding configurations, which helps reduce simultaneous modifications in multiple places on the front end. Furthermore, since general entity pages are generated based on entity metadata, and complex business-specific pages are generated through component construction functions corresponding to page types, and both types of page instances are included in the page state set by the page state management module, redundant development of standard business pages can be reduced. This allows general entity pages and complex business-specific pages to share page entries and page state management mechanisms. Furthermore, by rendering the same page state set as a multi-tab page on a PC and a page stack on a mobile device, both terminals can use consistent page state semantics.

[0032] Figure 2 An exemplary flowchart illustrates a method for menu permission filtering and terminal menu generation.

[0033] Reference Figure 2 This includes the following steps: S201. Obtain user permission information, filter menu items in menu configuration based on menu permissions in user permission information, and obtain retained menu items; S202a. In response to the terminal type being a personal computer, generate a personal computer menu based on the reserved menu items, and read the page type and page parameters from the personal computer menu to obtain the page entry. S202b: In response to the terminal type being mobile and the mobile menu tiling switch in the service operation configuration being turned on, a mobile tiled menu is generated based on the reserved menu items, and the page type and page parameters are read from the mobile tiled menu to obtain the page entry. S202c: In response to the terminal type being mobile and the mobile menu tiling switch in the service operation configuration being off, a mobile folded menu is generated based on the reserved menu items. The page type and page parameters are read from the mobile folded menu to obtain the page entry.

[0034] In this embodiment of the application, the menu configuration may record the menu identifier, menu name, parent menu identifier, menu icon, page type, page parameters, and permission identifier.

[0035] For example, user permission information can be distributed by the server through initialization data, menu data, or user information.

[0036] In some embodiments, the menu generation module matches the menu permissions in the user permission information with the permission identifiers corresponding to the menu items, and filters the menu items based on the matching results to obtain the retained menu items.

[0037] In this embodiment of the application, after the menu permission filtering is completed, the menu generation module selects the menu generation branch according to the terminal type.

[0038] For example, when the terminal type is PC, the menu generation module generates a PC menu based on the reserved menu items.

[0039] For example, when the terminal type is mobile, the menu generation module reads the mobile menu tiling switch in the business operation configuration. When the switch is on, a mobile tiled menu is generated; when it is off, a mobile collapsed menu is generated.

[0040] In the above embodiments, the PC-side menu, the mobile-side tiled menu, and the mobile-side collapsed menu all carry page types and page parameters. When a corresponding menu item is triggered, the menu generation module reads the page type and page parameters corresponding to that menu item to obtain the page entry point for use by the page state management module.

[0041] This application filters menu items through menu permissions, enabling page entry points to be generated according to user permissions. Furthermore, this application allows selection of menu format via terminal type and mobile menu tiling switch, allowing the same menu configuration to generate PC-side menus, mobile tiled menus, or mobile collapsed menus, improving flexibility and selectivity.

[0042] Figure 3 An example diagram illustrating the relationship between entity metadata structure and page construction rules is provided.

[0043] Reference Figure 3 Entity metadata is used to record the page construction rules for general entity pages. Entity metadata can include entity identifier, entity name, entity size type, field set, field type, field display rules, field validation rules, query rules, list column rules, detail layout rules, editing rules, button actions, and component mapping information.

[0044] For example, field metadata in a field collection can record field names, field types, default values, referenced entities, enumeration items, or inline options. Furthermore, field metadata can also record the display or editing rules for fields in the query area, list, details page, and edit page.

[0045] In some embodiments, the page builder locates the corresponding entity metadata based on the entity identifier in the page parameters, and selects the build branch for a list page, details page, or edit page based on the page type.

[0046] In one specific implementation, the server maintains the entity metadata of the robot entity. Specifically, the robot entity is recorded by an entity identifier field (name), the robot is recorded by a display name field (label), the entity is recorded as a multi-instance object by a scale type field (scale), and the field set (fields) is used to record the field configuration of the robot entity.

[0047] For example, the set of fields for a robot entity can be configured as robot identifier, robot name, status, area identifier, battery level, enabled status, and last online time.

[0048] In some specific embodiments, the status field can be configured as an enumerated field and mapped to status labels, the region identifier field can be configured as a field referencing a region entity, the battery level field can be configured as a numeric field, the enabled status field can be configured as a boolean field, and the online time field can be configured as a date and time field. Furthermore, each field can be configured for display in the query area, list display, details page display, edit status, required field status, default value, width, sorting, validation conditions, and mobile display method.

[0049] Figure 4 An exemplary flowchart illustrates a method for generating a general entity list page instance.

[0050] Reference Figure 4 This includes the following steps: S401. Responding to the general entity list page corresponding to the page type, generate query conditions according to the query rules in the entity metadata, generate a list according to the list column rules and field display rules in the entity metadata, generate field components according to the field types and component mapping information in the entity metadata, and generate page operation entry points according to the button actions in the entity metadata. S402. Construct a page instance based on the query conditions, list, field components, and page operation entry points.

[0051] For example, in the robot entity example, the page builder can generate query conditions based on query indexes or inline filters, generate list columns according to field list display rules, and select text components, number components, date components, enumeration label components, reference selection components, switch components, or custom components based on field type. The button actions in the entity metadata are converted into page operation entry points on the list page.

[0052] Figure 5 An exemplary flowchart illustrates a method for generating a general entity details page instance.

[0053] Reference Figure 5 This includes the following steps: S501. Responding to the general entity details page corresponding to the page type, generate details page content according to the details layout rules and field display rules in the entity metadata; responding to the general entity details page corresponding to the page type, generate field components according to the field types and component mapping information in the entity metadata; responding to the general entity details page corresponding to the page type, generate page operation entry points according to the button actions in the entity metadata. S502. Construct a page instance based on the details page content, field components, and page operation entry points.

[0054] For example, in the robot entity example, the page builder can organize field groups and buttons according to the detail layout configuration or mobile layout rules, determine the fields to be displayed on the detail page according to the field display rules, generate corresponding field components according to the field type and component mapping information, and generate page operation entry points according to button actions.

[0055] Figure 6 An exemplary flowchart illustrates a method for generating a general entity editing page instance.

[0056] Reference Figure 6 This includes the following steps: S601. In response to the general entity editing page corresponding to the page type, generate the editing page content and field components according to the editing rules, field types, field validation rules and component mapping information in the entity metadata. In response to the general entity editing page corresponding to the page type, generate the page operation entry according to the button action in the entity metadata. S602. Construct a page instance based on the edit page content, field components, and page operation entry points.

[0057] For example, in the robot entity example, the page builder can generate form controls based on editable configurations, required configurations, enumerated options, referenced entities, and field validation rules, and perform validation according to the field validation rules before saving.

[0058] For example, when a field configuration has a custom display script or field component mapping, the page builder calls the corresponding custom component.

[0059] For example, when field configuration uses field type mapping, the page builder calls the field component corresponding to the field type.

[0060] In this embodiment, query rules, page layout rules, field rules, component mapping information, and button actions are used to jointly drive the generation of general entity page instances, enabling list pages, detail pages, and edit pages to be generated based on entity metadata. This approach can reduce the need for developing separate pages for various standard business objects and for multiple simultaneous modifications when configurations change.

[0061] Figure 7 An exemplary flowchart illustrates a method for generating complex business-specific page instances.

[0062] Reference Figure 7 This includes the following steps: S701. Based on the page type, determine the component construction function from the registration mapping between the page type and the component construction function, and call the component construction function to load the dedicated page component; S702, Read page control storage from page state; S703. Pass the page state, page parameters, and page control storage to the dedicated page component to obtain a page instance.

[0063] In this embodiment, complex business-specific pages are accessed by the page builder through the registration relationship between page types and component construction functions. The registration mapping between page types and component construction functions can be recorded by a page builder map (pageBuilderMap), where each page type corresponds to one component construction function.

[0064] In one specific implementation, the registration mapping can record the FleetSceneRun page type, MapfDev page type, AI diagnostic page type, FalconTaskDefList page type, FalconTaskDefEditor page type, and programmable logic controller panel page type. Each page type corresponds to a specific component construction function.

[0065] For example, the component constructor can synchronously return a dedicated page component, or it can load a dedicated page component dynamically.

[0066] In some specific embodiments, after the page type and page parameters are provided in the menu event or business event, the page builder queries the registration mapping based on the page type to determine the corresponding component construction function.

[0067] As one specific implementation, the PageControlStore can be set in the page state. Specifically, the page builder passes the page state, page parameters, and PageControlStore to the dedicated page component. The dedicated page component obtains the page instance based on the received data and can set the page title, loading status, mobile display of page operation entry points, and return behavior through the PageControlStore.

[0068] For example, when a page type is not registered in the registration map or a dedicated page component fails to load, the page builder can display a page builder error message and isolate the component loading exception through error boundaries, thus isolating the loading exception of a single dedicated page from other pages in the front-end application.

[0069] In this example, the registration mapping between page types and component constructors allows complex business-specific pages to retain the implementation methods of their dedicated page components. Therefore, map scheduling, robot monitoring, and task orchestration pages can be generated through the corresponding component constructors. Furthermore, by passing page states, page parameters, and page control storage to the dedicated page components, complex business-specific pages can access a unified page entry point and page state management mechanism.

[0070] Figure 8 An example flowchart of a method for determining page status is shown.

[0071] Reference Figure 8 This includes the following steps: S801. Based on the page entry, compare the page type with the page types of existing pages in the page state set to obtain the page type comparison result; S802a: In response to the different results of the page type comparison, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set; S802b: In response to the consistent page type comparison results and the fact that both the page parameters and the page parameters of the existing page are simple values ​​that support item-by-item comparison, the two sets of page parameters are compared item by item to obtain the page parameter comparison results. For example, if S802b is executed, then S803a or S803b is executed further.

[0072] S803a: In response to the page parameter comparison result being consistent, update the opening order of existing pages and activate existing pages; S803b: In response to the difference in the comparison results of page parameters, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set. S802c: In response to the page type comparison results being consistent and at least one of the two sets of page parameters containing a complex value corresponding to the business context, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set.

[0073] In this embodiment, the page state management module maintains page type, page parameters, page identifier, page title, and page operation entry point.

[0074] For example, a new page identifier can be incrementally generated by the page state management module when creating a page state, and together with the page type, page parameters, opening order, and page control storage, constitutes the page state.

[0075] In this embodiment of the application, the page state determination first compares the page types.

[0076] For example, when the page type comparison results are different, the page state management module assigns a new page identifier to the page to be opened, creates a new page state, and adds the new page state to the page state set.

[0077] For example, when the page type comparison results are consistent, the page state management module determines whether both sets of page parameters are simple values ​​that support item-by-item comparison. These simple values ​​can be strings, numbers, booleans, or null values.

[0078] For example, when both sets of page parameters are simple values, the page state management module compares the two sets of page parameters item by item.

[0079] In one implementation, when the page parameter comparison results are consistent, the page state management module identifies the page to be opened as an existing page, updates the opening order of the existing pages, and activates the existing pages.

[0080] In one implementation, when the page parameter comparison results are different, the page state management module assigns a new page identifier, creates a new page state, and adds it to the page state set.

[0081] For example, in contrast to the handling of simple values, when the page type comparison results are consistent and at least one set of page parameters contains complex values ​​in the form of objects, arrays, or functions, the page state management module assigns a new page identifier to the page to be opened, creates a new page state, and adds it to the page state set, so that the corresponding business context is carried by the new page state.

[0082] In this embodiment, by comparing page types and simple page parameters, the page state management module can reuse existing page states when the page types and page parameters are consistent, reducing duplicate pages in the page state set. Furthermore, for page parameters containing complex values, creating new page states to carry the corresponding business context can reduce the possibility of dissimilar business contexts being merged into the same page state.

[0083] Figure 9 An example flowchart is shown for a method of page replacement, return, and closing.

[0084] Reference Figure 9 This includes the following steps: S901a. In response to the page replacement request, the page status management module finds the existing page corresponding to the page to be replaced. For example, if S901a is executed, then S902a or S902b is executed further.

[0085] S902a: In response to finding an existing page, activate the existing page; S902b: In response to the absence of an existing page, remove the current top page of the stack and insert the page state corresponding to the page to be replaced; S901b: In response to a page return request, the page state management module removes the top page from the stack and sets the previous page as the current page; S901c: In response to a page close request, the specified page is removed by the page state management module; For example, if S901c is executed, then S902c is executed further.

[0086] S902c: In response to the specified page being the current page, select the page with the closest opening order from the remaining pages and set it as the current page.

[0087] For example, after a page replacement request is triggered, the page state management module first searches the page state set for an existing page corresponding to the page to be replaced. Further, if an existing page is found, it is activated; if the search result is empty, the current top page of the stack is removed, and the page state corresponding to the page to be replaced is inserted into the page state set.

[0088] For example, when a page return request is triggered, the page state management module removes the top page from the stack and sets the page preceding the top page as the current page. If a page close request is triggered, the page state management module removes the specified page. Furthermore, if the specified page is already the current page, the page state management module selects the page with the closest opening order among the remaining pages and sets that page as the current page.

[0089] In one specific implementation, the page state management module can perform page opening and deduplication checks through the page push method, update the opening order of existing pages and activate existing pages through the reopen method, perform page replacement through the page replace method, remove the top page of the stack through the page back method, and remove the specified page through the page close method.

[0090] In this embodiment, the page state management module uniformly executes page replacement, page return, and page closing, so that the existing page activation, top page removal, and current page selection in the page state set adopt a consistent state processing relationship, and provides a unified page navigation state for personal computers and mobile devices.

[0091] Figure 10 An exemplary flowchart illustrates a method for rendering a collection of page states on multiple terminals.

[0092] Reference Figure 10 This includes the following steps: S1001. Read the page array, current page, and page operation entry point from the page state set; S1002a: In response to the terminal type being a personal computer, the page array is rendered as a multi-tab page, and the current page is rendered as the currently active tab; S1002b: In response to the fact that the terminal type is mobile and the mobile entity operation button tiling switch in the service operation configuration is in the on state, the page array is rendered as a page stack, the current page is rendered as the top page of the stack, and the page operation entry is rendered as a tiling entity operation button. S1002c: In response to the fact that the terminal type is mobile and the mobile entity operation button tile switch in the service operation configuration is in the off state, the page array is rendered as a page stack, the current page is rendered as the top page of the stack, and the page operation entry is rendered as the stored entity operation button.

[0093] For example, the page state set can include an array of pages, and the current page can be indicated by the current page pointer (top).

[0094] In this embodiment, the page state management module maintains page operation entry points, thus enabling the multi-terminal adaptation module to read the corresponding page operation entry points from the page state set. Furthermore, both the PC and mobile terminals read the same page array and the current page, selecting the page container type based on the terminal type, eliminating the need to maintain independent page state data for each terminal.

[0095] For example, when the terminal type is a personal computer, the multi-terminal adaptation module generates multiple tabs according to the page arrangement in the page array and renders the current page as the currently active tab.

[0096] For example, when the terminal type is mobile, the multi-terminal adaptation module renders the page array as a page stack and renders the current page as the top page of the stack. The multi-terminal adaptation module also reads the mobile physical operation button tiling switch in the business operation configuration. When the switch is on, the page operation entry is rendered as a tiled physical operation button; when it is off, the page operation entry is rendered as a collapsed physical operation button.

[0097] In one example, a PC user opens the robot list page twice consecutively. The second page opening activates an existing robot list tab. When a robot details page is opened, the corresponding details page is added to or activated in the page state set, and the current page is rendered as the currently active tab.

[0098] In another example, a mobile user enters the robot list page from the homepage, then enters the robot details page. The page array sequentially holds the list page and the details page, with the robot details page being rendered as the current page at the top of the stack. Upon receiving a page return request, the page state management module removes the robot details page from the top of the stack, and the robot list page becomes the current page, which is then rendered as the new top page by the multi-terminal adaptation module.

[0099] In this embodiment, since both the PC and mobile devices read the same set of page states, page state management is separated from the terminal container form, enabling consistent page state semantics for multitasking on the PC and step-by-step return on the mobile device. Furthermore, the mobile device entity operation button tile switch in the business operation configuration allows page operation entry points to switch between tiled and collapsed forms, improving flexibility and selectivity.

[0100] Figure 11 An example of a user permission control relationship diagram is shown.

[0101] Reference Figure 11 User permission information includes page access permissions, field visibility permissions, field editing permissions, and operation permissions. These four types of permissions respectively apply to page opening requests, field display on general entity pages, field editing on general entity pages, and page operation entry points.

[0102] For example, user permission information can be distributed by the server through initialization data, menu data, or user information. When a page entry is triggered, the front-end application verifies the page opening request based on page access permissions. Page access permissions can be verified before the page opens or during the page construction process.

[0103] For example, for a generic entity page, the page builder controls field display based on field visibility permissions and field editing based on field edit permissions. Field visibility permissions determine whether a corresponding field is displayed on the generic entity page, while field edit permissions determine whether a corresponding field is editable.

[0104] For example, operation permissions are used to control the entry points for page operations. When a general entity page generates page operation entry points, the operation permissions can be used to determine whether the entry points corresponding to add, modify, delete, import, export, or batch operations are displayed.

[0105] In a supplementary implementation, for page opening processes triggered by direct address input or business scripts, the front-end page status entry can still perform verification based on page type, page access permissions, and entity metadata. For example, the server-side interfaces corresponding to save, query, delete, and export can also perform permission verification and return the corresponding status and required permission identifier when permissions are insufficient.

[0106] This application applies page access permissions, field visibility permissions, field editing permissions, and operation permissions to page opening, field display, field editing, and page operation entry points respectively, so that permission control can cover the corresponding processing links in the page generation and page usage process.

[0107] Figure 12 The diagram illustrates the structure and data interaction of a runtime configurable page generation system for an industrial management platform.

[0108] Reference Figure 12 The industrial management platform runtime configuration page generation system includes a front-end runtime container 1201 set in the front-end application 1200, a menu generation module 1202, a page state management module 1203, a page builder 1204, and a multi-terminal adaptation module 1205. The front-end runtime container 1201 includes an entity metadata container 1206, a menu container 1207, and a runtime configuration container 1208. The server 1209 is located outside the front-end application 1200.

[0109] The front-end runtime container 1201 is used to retrieve and store entity metadata, menu configuration, and business operation configuration from the server 1209 in response to the startup of the front-end application 1200. Specifically, the entity metadata is stored in the entity metadata container 1206, the menu configuration is stored in the menu container 1207, and the business operation configuration is stored in the runtime configuration container 1208.

[0110] The menu generation module 1202 is used to read the menu configuration in the menu container 1207, generate a page entry carrying page type and page parameters, and provide the page entry to the page state management module 1203.

[0111] The page state management module 1203 is used to respond to the page entry being triggered, determine the page state based on the page entry, send the page entry and page state to the page builder 1204, receive the page instance returned by the page builder 1204, associate the page instance with the page state, and store the page state in the page state set.

[0112] Page builder 1204 is used to receive page entry points and page states sent by page state management module 1203, and to send the generated page instances to page state management module 1203. In response to a general entity page corresponding to a page type, page builder 1204 generates a page instance based on the entity metadata pointed to by the page parameters; in response to a complex business-specific page corresponding to a page type, page builder 1204 determines the corresponding component construction function based on the page type and uses the component construction function to generate a page instance.

[0113] The multi-terminal adaptation module 1205 is used to read the page state set and business operation configuration, and render the page state set into a PC-side multi-tab page or a mobile-side page stack according to the terminal type and business operation configuration.

[0114] For example, server 1209 provides three types of configurations to front-end runtime container 1201; front-end runtime container 1201 provides corresponding configurations to menu generation module 1202, page builder 1204 and multi-terminal adaptation module 1205; menu generation module 1202 provides page entry to page state management module 1203; page state management module 1203 interacts with page builder 1204 on page entry, page state and page instance; multi-terminal adaptation module 1205 generates terminal interface with page state set as input.

[0115] In this embodiment, since the components of the front-end application 1200 establish continuous data interaction relationships around entity metadata, menu configuration, business operation configuration, page entry, page status, page instance, and page status set, the same front-end application 1200 can collaboratively carry general entity pages and complex business-specific pages. Then, through the page status management module 1203 and the multi-terminal adaptation module 1205, the personal computer interface or mobile interface is output, reducing the disconnect between general entity pages and complex business-specific pages in terms of page entry, page status management, and terminal adaptation.

[0116] In one implementation, entity metadata can be generated by the server 1209's database, configuration files, low-code designer, or a third-party system. Even when the source of the entity metadata changes, the front-end application 1200 still receives entity metadata that can be pointed to by page parameters and read by the page builder 1204.

[0117] For example, the page engine can be implemented using React, Vue, Web Components, native mobile components, or other user interface frameworks. The corresponding implementation method is used to host general entity page components and complex business-specific page components, without changing the page type, page parameters, page state, and data relationships between page instances.

[0118] For example, page state management can manifest as tabs, route stacks, browser routes, micro-frontend routes, or other navigation mechanisms. When using the corresponding navigation mechanism, the page state management module 1203 still maintains the storage of page type, page parameters, page identifier, opening order, and page control, and provides the corresponding page display format according to the terminal type.

[0119] For example, permission filtering can be performed by the front-end application 1200, or by the server 1209 before issuing menu configurations and entity metadata. The configuration for mobile menu tiling, entity operation button tiling, and detail layout can be recorded in the business operation configuration or in the entity metadata.

[0120] In one supplementary implementation, server 1209 can distribute extended scripts and extended styles for registering custom pages, extended field components, or supplementing on-site specialized interactions. The extended scripts or remote components can be provided by server 1209 in the form of a distribution list through an initialization interface or a basic configuration interface. The extended script list can record the extension name, version, resource address, resource type, dependency list, loading order, scope, registration entry point, and permission range.

[0121] For example, when an extension name or page type conflicts with a built-in registered item, strategies such as rejecting overriding, isolating by namespace, or whitelisting can be used. When dependencies are missing, versions mismatched, or loading fails, the front-end application logs the error (1200) and skips the corresponding extension, while already loaded built-in pages and other extensions continue to be used. The extension registration interface provides page registration, field component registration, style registration, and configuration reading capabilities. The server (1209) can combine signature, version, source whitelist, permission scope, and project-level switches to control whether an extension is active.

[0122] For example, runtime extensions can be implemented using JavaScript, plugin packages, remote components, script templates, or web components. Internationalized text can be stored in a local dictionary, a server-side dictionary, or metadata fields.

[0123] For example, the page state management module 1203 determines the page state based on the page entry point as follows: Based on the page entry point, the page type is compared with the page types of existing pages in the page state set to obtain the page type comparison result; In response to a difference in the page type comparison result, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set; In response to a match in the page type comparison result and both the page parameters and the page parameters of the existing pages are simple values ​​that support item-by-item comparison, the two sets of page parameters are compared item-by-item to obtain the page parameter comparison result; In response to a match in the page parameter comparison result, the opening order of existing pages is updated and existing pages are activated; In response to a difference in the page parameter comparison result, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set; In response to a match in the page type comparison result and at least one set of page parameters contains a complex value corresponding to the business context, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set.

[0124] In one specific implementation, after the front-end application 1200 has loaded the basic framework, entity metadata, menu configuration, and internationalization dictionary, it can load the extension scripts and extension styles according to the loading order recorded in the extension script manifest. Specifically, the extension scripts register new page types with the page builder 1204 through a predefined registration interface, or register new field display components, input components, and button actions with the field component registry.

[0125] For example, the registered custom pages and field components are still managed uniformly by the page builder 1204 and the page state management module 1203.

[0126] Regarding the system in the above embodiments, the specific ways in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0127] Although the operations are described in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all of the operations shown to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.

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

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

[0130] The foregoing description of implementations of this application has been provided for illustrative and descriptive purposes. The foregoing description is not exhaustive and is not intended to limit this application to the exact forms disclosed. Various modifications and variations may exist in accordance with the foregoing teachings, or may arise from practice of this application. These embodiments were chosen and described to illustrate the principles of this application and its practical application, enabling those skilled in the art to utilize this application in various implementations and modifications to suit the specific purpose of the concept.

[0131] Regarding the system in the above embodiments, the specific ways in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0132] It can be further understood that, unless otherwise specified, "connection" includes both direct connections where no other components exist between the two parties and indirect connections where other components exist between them.

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

[0134] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the field of this application that are not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0135] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

[0136] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for generating runtime configuration pages for an industrial management platform, characterized in that, Executed by a front-end application, the front-end application including a front-end runtime container, a menu generation module, a page state management module, a page builder, and a multi-terminal adaptation module, the method includes: In response to the startup of the front-end application, entity metadata, menu configuration, and business operation configuration are obtained from the server and stored in the front-end runtime container; The menu generation module generates a page entry carrying page type and page parameters based on the menu configuration in the front-end runtime container; In response to the page entry being triggered, the page state management module determines the page state based on the page entry and sends the information to the page builder and the page state. In response to the general entity page corresponding to the page type, the page builder generates the page instance based on the entity metadata pointed to by the page parameters; In response to the page type corresponding to a complex business-specific page, the page builder determines the corresponding component construction function based on the page type and uses the component construction function to generate the page instance; The page state management module associates the page instance with the page state and stores the page state in the page state set; The multi-terminal adaptation module renders the set of page states into a multi-tab page for PCs or a page stack for mobile devices, based on the terminal type and the service operation configuration.

2. The method for generating a runtime configuration page for an industrial management platform according to claim 1, characterized in that, The step of generating a page entry carrying page type and page parameters based on the menu configuration in the front-end runtime container includes: Obtain user permission information, and filter menu items in the menu configuration based on the menu permissions in the user permission information to obtain the retained menu items; In response to the terminal type being a personal computer, a personal computer menu is generated based on the reserved menu items, and the page type and page parameters are read from the personal computer menu to obtain the page entry. In response to the terminal type being a mobile device and the mobile menu tiling switch in the service operation configuration being turned on, a mobile tiled menu is generated based on the reserved menu items, and the page type and page parameters are read from the mobile tiled menu to obtain the page entry. In response to the terminal type being a mobile device and the mobile menu tiling switch in the service operation configuration being off, a mobile folded menu is generated based on the reserved menu items, and the page type and page parameters are read from the mobile folded menu to obtain the page entry.

3. The method for generating a runtime configuration page for an industrial management platform according to claim 1, characterized in that, The step of generating the page instance based on the entity metadata pointed to by the page parameters includes: In response to the general entity list page corresponding to the page type, query conditions are generated according to the query rules in the entity metadata, a list is generated according to the list column rules and field display rules in the entity metadata, field components are generated according to the field types and component mapping information in the entity metadata, a page operation entry is generated according to the button actions in the entity metadata, and the page instance is constructed according to the query conditions, the list, the field components and the page operation entry. In response to the general entity details page corresponding to the page type, the details page content is generated according to the details layout rules and field display rules in the entity metadata, the field components are generated according to the field types and component mapping information in the entity metadata, the page operation entry is generated according to the button actions in the entity metadata, and the page instance is constructed according to the details page content, the field components and the page operation entry. In response to the general entity editing page corresponding to the page type, the editing page content and field components are generated according to the editing rules, field types, field validation rules and component mapping information in the entity metadata. The page operation entry is generated according to the button actions in the entity metadata. The page instance is constructed according to the editing page content, the field components and the page operation entry.

4. The method for generating a runtime configuration page for an industrial management platform according to claim 1, characterized in that, The step of determining the corresponding component construction function based on the page type and generating the page instance using the component construction function includes: Based on the page type, the component construction function is determined from the registration mapping between page type and component construction function; The component construction function is invoked to load the dedicated page component; Read page control storage from the page state; The page instance is obtained by passing the page state, the page parameters, and the page control storage to the dedicated page component.

5. The method for generating a runtime configuration page for an industrial management platform according to claim 1, characterized in that, Determining the page state based on the page entry includes: Based on the page entry point, the page type is compared with the page types of existing pages in the page state set to obtain the page type comparison result; In response to a discrepancy in the page type comparison results, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set. If the page type comparison results are consistent and the page parameters and the page parameters of the existing page are both simple values ​​that support item-by-item comparison, the two sets of page parameters are compared item by item to obtain the page parameter comparison result; if the page parameter comparison results are consistent, the opening order of the existing pages is updated and the existing pages are activated; if the page parameter comparison results are different, a new page identifier is assigned, a new page state is created and the new page state is added to the page state set. In response to the page type comparison results being consistent and at least one of the two sets of page parameters containing a complex value corresponding to the business context, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set.

6. The method for generating a runtime configuration page for an industrial management platform according to claim 1, characterized in that, The method further includes: In response to a page replacement request, the page state management module searches for an existing page corresponding to the page to be replaced; if the existing page is found, the existing page is activated; if the existing page is not found, the current top page of the stack is removed and the page state corresponding to the page to be replaced is inserted. In response to a page return request, the page state management module removes the top page from the stack and sets the previous page as the current page; In response to a page close request, the page state management module removes the specified page; in response to the specified page being the current page, the page with the closest opening order from the remaining pages is selected and set as the current page.

7. The method for generating a runtime configuration page for an industrial management platform according to claim 1, characterized in that, The step of rendering the page state set into a PC multi-tab page or a mobile page stack based on the terminal type and the service operation configuration includes: Read the page array, the current page, and the page operation entry point from the page state set; In response to the terminal type being a personal computer, the page array is rendered as a multi-tab page, and the current page is rendered as the currently active tab; In response to the terminal type being a mobile terminal and the mobile terminal physical operation button tiling switch in the service operation configuration being turned on, the page array is rendered as a page stack, the current page is rendered as the top page of the stack, and the page operation entry is rendered as a tiling physical operation button. In response to the terminal type being a mobile device and the mobile device physical operation button tiling switch in the service operation configuration being in the off state, the page array is rendered as a page stack, the current page is rendered as the top page of the stack, and the page operation entry is rendered as a stored physical operation button.

8. The method for generating a runtime configuration page for an industrial management platform according to claim 1, characterized in that, The method further includes: Obtain user permission information; wherein, the user permission information includes page access permissions, field visibility permissions, field editing permissions, and operation permissions; Verify the page opening request based on the page access permissions; The display of fields on the general entity page is controlled based on the field visibility permissions. The field editing permissions are used to control the field editing of the general entity page; Control page access points based on user permissions.

9. A runtime configuration page generation system for an industrial management platform, characterized in that, This includes a front-end runtime container set up in the front-end application, a menu generation module, a page state management module, a page builder, and a multi-terminal adaptation module; The front-end runtime container is used to retrieve and store entity metadata, menu configuration, and business operation configuration from the server in response to the startup of the front-end application. The menu generation module is used to read the menu configuration in the front-end runtime container and generate a page entry carrying page type and page parameters. The page state management module is used to respond to the page entry being triggered, determine the page state according to the page entry, send the page entry and the page state to the page builder, associate the page instance returned by the page builder with the page state, and store the page state in the page state set. The page builder is used to send a page instance to the page state management module: in response to a general entity page corresponding to the page type, it generates the page instance based on the entity metadata pointed to by the page parameters; in response to a complex business-specific page corresponding to the page type, it determines the corresponding component construction function based on the page type and uses the component construction function to generate the page instance. The multi-terminal adaptation module is used to render the page state set into a PC-side multi-tab page or a mobile-side page stack according to the terminal type and the business operation configuration.

10. The industrial management platform runtime configuration page generation system according to claim 9, characterized in that, The page status management module determines the page status based on the page entry point in the following manner: Based on the page entry point, the page type is compared with the page types of existing pages in the page state set to obtain the page type comparison result; In response to a discrepancy in the page type comparison results, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set. If the page type comparison results are consistent and the page parameters and the page parameters of the existing page are both simple values ​​that support item-by-item comparison, the two sets of page parameters are compared item by item to obtain the page parameter comparison result; if the page parameter comparison results are consistent, the opening order of the existing pages is updated and the existing pages are activated; if the page parameter comparison results are different, a new page identifier is assigned, a new page state is created and the new page state is added to the page state set. In response to the page type comparison results being consistent and at least one of the two sets of page parameters containing a complex value corresponding to the business context, a new page identifier is assigned, a new page state is created, and the new page state is added to the page state set.

Images