Application-based multi-system page integration method and system
By uniformly saving the src directory of multiple systems and creating compatible login interfaces, the problem of low switching efficiency between multiple systems in the existing technology is solved, and the establishment of new applications and menu integration is realized, which improves work efficiency and user experience.
Patent Information
- Application Number
- CN202410964646.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-18
- Publication Date
- 2024-11-12
AI Technical Summary
The existing visual integration method between multiple systems requires switching back and forth within each system, which reduces work efficiency and lacks a unified login and menu management mechanism.
By obtaining the startup entrance file route from the server, saving the src directory of multiple systems uniformly, and modifying the front-end configuration file to select the startup project, creating a portal login interface compatible with multiple systems, realizing the establishment of new applications and menu integration.
It realizes efficient page integration and unified login between multiple business systems, improves work efficiency, allows users to form new applications and independently build integrated applications, improving user experience.
Smart Images

Figure CN118939158A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field, and in particular relates to an application-based multi-system page integration method and system. Background Art
[0002] In the prior art, for example, Chinese patent ZL202311182669.2 provides a visual integration method and system among multiple systems. The system integrates the pages of multiple subsystems of the enterprise information system into the integrated system. Users only need to operate on the integrated system to handle all business. However, the prior art only does single sign-on, that is, develops a portal homepage, and then puts the entrance of each subsystem on the homepage, and jumps to the corresponding system after clicking. Using the integration method provided by the prior art, it is necessary to switch back and forth between the systems, which reduces work efficiency. Summary of the invention
[0003] In view of the above technical problems, the present invention proposes an application-based multi-system page integration method and system, comprising the following steps:
[0004] S1 obtains its startup entry file route from the first front-end on the server side;
[0005] S2 obtains the src directories of multiple original systems and saves them uniformly as subdirectories under the src directory of the startup entry file;
[0006] S3 modifies the configuration file of the first front end and adds a parameter for selecting the project name to be started;
[0007] S4 modifies the startup mode of the first front end to start the server on the specified front end;
[0008] S5 creates a portal login interface to make it compatible with logins of multiple existing systems.
[0009] In the case of multiple existing business systems, the present invention can select existing function pages from each system as needed to form one or more new applications. All menus of the original system can be integrated to form a system application. On this basis, integrated applications can also be built separately and arbitrarily. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 : Network topology diagrams of some solutions;
[0011] Figure 2 : Flowcharts of some schemes;
[0012] Figure 3 : File structure diagrams of some solutions;
[0013] Figure 4 : Screenshots of the front-end pages of some solutions;
[0014] Figure 5 : Integrated system application of some solutions;
[0015] Figure 6 : Screenshots of the front-end pages of some solutions. DETAILED DESCRIPTION
[0016] The following examples further illustrate the content of the present invention, but should not be construed as limiting the present invention. Without departing from the spirit and substance of the present invention, modifications or substitutions made to the methods, steps or conditions of the present invention all fall within the scope of the present invention.
[0017] Some solutions, such as Figure 1 The network structure is implemented, including the following steps:
[0018] S1 obtains its startup entry file route from the first front-end on the server side;
[0019] S2 obtains the src directories of multiple original systems and saves them uniformly as subdirectories under the src directory of the startup entry file;
[0020] S3 modifies the configuration file of the first front end and adds a parameter for selecting the project name to be started;
[0021] S4 modifies the startup mode of the first front end to start the server on the specified front end;
[0022] S5 creates a portal login interface to make it compatible with the login of multiple existing systems. More specifically, 2, the S5 specifically includes the following steps: creating a new login interface in the first front end, the login interface receives the user name and account password fields and compares them with the user table in the database of the server, creates a login credential when the comparison is successful, returns the user information, and stores the user information in the server.
[0023] In some other solutions, when other interfaces receive the login credentials, they query the server side, and if found, continue with the subsequent logic, otherwise feedback is invalid login credentials.
[0024] Based on the above solution, a more specific solution is applied in the field of intelligent parking terminal technology. Figure 2 The steps shown will include: the subsystems of the intelligent parking business system including the parking management platform, charging management platform, access control management platform, and car wash management platform are integrated into a new system page. When the user logs in to the system page, he can request application configurations of different subsystems, request menu data, request form data, and request page data.
[0025] In some solutions based on the above solution, after the first front end receives the access application list instruction of the user of the portal login interface, its back end executes the access application list display step, and the application list display step specifically includes the following steps:
[0026] Data is read from the application table of the database of the first front end, and icons, application names, and modification operation buttons of applications from all different original systems are displayed on the page of the first front end.
[0027] Some solutions based on the above solutions also include application management steps, specifically including the following steps:
[0028] Query the system integration table in the first backend, query the data under all nodes whose parent menu ID is 0 and display it on the left side of the selector;
[0029] Select a system in the system integration table, query the system ID field in the system integration table to match all menu data in the table, and associate the menu ID with the parent menu ID to form tree data.
[0030] In some solutions based on the above solution, the application management step further includes the following steps:
[0031] When creating a new group, enter the group name and create a new group record in the menu table of the database;
[0032] Set the menu ID of the newly added menu as auto-increment, set the parent menu ID of the newly added menu to 0, set the application ID to the current application ID, set the menu name to the input value, and set other field values to empty;
[0033] A new record is added to the menu table, the parent menu ID of the record is the ID of the first-level menu, and the page path is the path of the original system.
[0034] Adding a new record in the menu table also includes the steps of menu editing and deletion, specifically including: modifying the corresponding menu name and menu icon fields in the menu table of the database to implement menu editing and deletion.
[0035] Adding a new record in the menu table also includes the step of moving the menu, specifically including:
[0036] Select the menu data to be moved and call the selector of the first-level group;
[0037] By querying the menu data, the record whose application ID is the current application ID and whose parent menu ID is 0 represents a first-level group;
[0038] After selecting a first-level group, change the parent menu ID of the menu to the currently selected record ID.
[0039] Some solutions, based on the above solutions, further include the step of displaying the application page on the first front end, specifically including: obtaining the page path value from the menu, and rendering the specific content of the application page.
[0040] An application-based multi-system page integration system according to some embodiments includes at least one processor; and a memory storing instructions, which, when executed by at least one processor, implement the steps according to the above embodiments.
[0041] The following is Figure 3-6 The illustrated embodiment is used to illustrate the steps in the above scheme.
[0042] The first step of front-end execution: the original front-end code structure of multiple systems is as follows Figure 4 , where the src directory contains the system source code, src / index.js is the startup entry file, and the other files are configurations or public libraries.
[0043] Create a new portal project with the following file structure: Figure 3 , put the src parts of multiple systems into the src directory of the new project, and use the original system name as the subdirectory name. For example, if the account system is moved into the portal project, its code location is src / account. Its startup file address is src / account / index.js.
[0044] Modify the project's configuration file and add a new parameter projectName to select the name of the project to be started.
[0045] The original system startup mode is yarn start.
[0046] The modified startup method is yarn start account.
[0047] When the portal project receives this parameter, it will load src / account / index.js as the project startup item, thus entering the project.
[0048] Steps performed by the first backend of the first frontend:
[0049] Unified login interface: Create a portal login interface to make it compatible with the login of the original systems. Specifically: create a new login interface, accept the userName and password fields, compare with the user table in the database, and when the comparison is successful: create a login credential token and return the user information, and store it on the server.
[0050] The steps for implementing the service in this embodiment are as follows:
[0051] Application list display steps: read data from the application table in the database and display all applications on the front-end page. As shown in the figure, the application icon is at the top of the application list and the application name is at the bottom. Click the More button to modify the name, color, and icon again.
[0052] Steps for creating a new application: Enter a new application name, such as "Operation Management", and select the application color and icon. Click Save to read the values of the application name, color, and icon and create a new application record in the application table of the database. The corresponding fields are appName, appColor, and appIcon. The appID will be used as the primary key and increment automatically.
[0053] To delete the app: Click Figure 4 Click the Delete App button in the dialog box, and a second confirmation prompt box will pop up. After clicking Confirm Delete, the delete interface is called to pass the appID to the server, and the server completes the deletion operation by deleting the corresponding record in the application table in the database.
[0054] Application Management - Add new menu grouping steps:
[0055] Click an application (such as "Operation Management") in the application list to jump to the application management interface. You can create, edit, and delete first-level groups in the application.
[0056] When creating a group, enter the group name (for example: Coupon Management). A new group record is created in the menu table of the database.
[0057] Add new steps to the subsystem page:
[0058] The rightID of the newly added menu is auto-incremented, parentRightID is the parent ID of 0, application ID is the current application ID, menu name rightName is the input value, and other field values are empty.
[0059] By querying the system integration table, query all the data in the table with parentRightID of 0 (0 represents the top-level node). And display it on the left side of the selector. After selecting one of the systems, such as the parking management platform, query the systemID field in the table to match all the menu data in the table, and associate rightID with parentRightID to form tree data. Display the original menu content of the system on the right side of the selector.
[0060] Figure 5 , select a menu, such as Parking Ticket Management, click Save, and the page save interface pops up. Enter the new page name, and the original system page name is filled in by default. Click Confirm.
[0061] Add a new record in the menu table. The parent ID of the record is the ID of the first-level menu, and the page path is the rightPath of the original system.
[0062] In showing Figure 6 When you open a page, you will first get the page path value from the menu and render the specific content of the page. The path value is the URL address of the specific page, and the page is displayed by opening the address in the content area.
[0063] Menu Editing and Deleting Steps: Click the More button next to the menu to edit or delete the menu item. When editing, you can modify the menu name or icon. Just modify the corresponding rightName and rightIcon fields in the menu table of the database.
[0064] Menu moving steps:
[0065] Select the submenu to be moved, and the selector for the first-level group will pop up. By querying the menu table, the record whose appID is the current application ID and parentRightID is 0 represents the first-level group.
[0066] After selecting the first level group, modify the parentRightID of the menu to the ID of the currently selected record. The menu is moved.
[0067] The database table structure of the above embodiment is as follows:
[0068] Table 1. Database table structure
[0069]
[0070] Embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on one or more tangible, non-transitory program carriers for execution by, or to control the operation of, a data processing device. Alternatively or in addition, the program instructions may be encoded on an artificially generated propagating signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated as encoded information for transmission to an appropriate receiver device for execution by a data processing device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of the foregoing.
[0071] A computer program (which may also be referred to or described as a program, software, software application, module, software module, script or code) may be written in any form of programming language, including compiled or interpreted languages or declarative or procedural languages, and the computer program may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program may be stored in a portion of a file that stores other programs or data, for example, one or more scripts stored in the following: in a markup language document; in a single file dedicated to a related program; or in multiple collaborative files, for example, files storing one or more modules, subroutines or code portions. A computer program may be deployed to execute on one or more computers, the computers being located in one place or distributed to multiple locations and interconnected by a communication network.
[0072] A computer suitable for executing a computer program includes and may be based, for example, on a general purpose microprocessor or a special purpose microprocessor or both, or a central processing unit of any other kind. Typically, the central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a central processing unit for running or executing instructions and one or more memory devices for storing instructions and data.
[0073] To transmit interactions with a user, embodiments of the subject matter described in this specification may be implemented on a computer having: a display device, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user; and a keyboard and a pointing device, such as a mouse or a trackball, with which the user can transmit input to the computer. Other kinds of devices may also be used to transmit interactions with a user; for example, feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic input, voice input, or tactile input. In addition, a computer may interact with a user by sending documents to a device used by the user and receiving documents from the device; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.
[0074] The embodiments of the subject matter described in this specification can be implemented in a computing system, which includes a back-end component such as a data server, or includes an intermediate component such as an application server, or includes a front-end component such as a client computer, and the client computer has a graphical user interface or a web browser, and a user can interact with the implementation of the subject matter described in this specification through a graphical user interface or a web browser, or the computer system includes any combination of one or more such back-end components, intermediate components, or front-end components. The components in the system can be interconnected by digital data communication of any form or medium such as a communication network. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), for example, the Internet.
[0075] Although the present invention has been described in detail above by general description, specific implementation methods and experiments, it is obvious to those skilled in the art that some modifications or improvements can be made to the present invention. Therefore, these modifications or improvements made without departing from the spirit of the present invention all belong to the scope of protection claimed by the present invention.
Claims
1. A multi-system page integration method based on application, characterized in that: The process includes the following steps performed by the first backend: S1 obtains its startup entry file route from the first front-end on the server side; S2 obtains the src directories of multiple original systems and saves them uniformly as subdirectories under the src directory of the startup entry file; S3 modifies the configuration file of the first front end and adds a parameter for selecting the project name to be started; S4 modifies the startup mode of the first front end to start the server on the specified front end; S5 creates a portal login interface to make it compatible with logins of multiple existing systems.
2. The method according to claim 1, characterized in that The S5 specifically includes the following steps: a new login interface is created on the first front end, and after the login interface receives the user name and account password fields, they are compared with the user table in the database of the server. When the comparison is successful, a login credential is created, the user information is returned, and the user information is stored in the server.
3. The method according to claim 2, characterized in that When the first front end receives the access application list instruction of the user of the portal login interface, the back end thereof executes the access application list display step, and the application list display step specifically includes the following steps: Data is read from the application table of the database of the first front end, and icons, application names, and modification operation buttons of applications from all different original systems are displayed on the page of the first front end.
4. The method according to claim 3, characterized in that It also includes application management steps, which specifically include the following steps: Query the system integration table in the first backend, query the data under all nodes whose parent menu ID is 0 and display it on the left side of the selector; Select a system in the system integration table, query the system ID field in the system integration table to match all menu data in the table, and associate the menu ID with the parent menu ID to form tree data.
5. The method according to claim 4, characterized in that The application management step also includes the following steps: When creating a new group, enter the group name and create a new group record in the menu table of the database; The menu ID of the newly added menu is a self-increasing number. The parent menu ID of the newly added menu is set to 0, the application ID is set to the current application ID, the menu name is set to the input value, and the other field values are set to empty; A new record is added to the menu table, the parent menu ID of the record is the ID of the first-level menu, and the page path is the path of the original system.
6. The method according to claim 5, characterized in that The method also includes the steps of menu editing and deletion, which specifically include: modifying the corresponding menu name and menu icon fields in the menu table of the database to implement menu editing and deletion.
7. The method according to claim 6, characterized in that It also includes steps for moving the menu, including: Select the menu data to be moved and call the selector of the first-level group; By querying the menu data, the record whose application ID is the current application ID and whose parent menu ID is 0 represents a first-level group; After selecting a first-level group, change the parent menu ID of the menu to the currently selected record ID.
8. The method according to claim 7, characterized in that The method also includes the step of displaying the application page on the first front end, which specifically includes: obtaining the page path value from the menu and rendering the specific content of the application page.
9. An application-based multi-system page integration system, characterized in that: The system comprises at least one processor; and a memory storing instructions, which, when executed by the at least one processor, implement the steps of the method according to any one of claims 1 to 8.
10. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: The computer program / instructions implement the steps of the method of claim 1 when executed by a processor.
