Portal management and authority allocation method, device and medium based on aPaaS

Abstract

The present application proposes a portal management and authority allocation method, device and medium based on aPaaS, which realizes flexible management of portal panel, dynamic maintenance of portal, real-time update of portal content and dynamic allocation of portal authority, including: dividing the management work of the portal management system based on aPaaS into panel maintenance management and portal content management; based on the demand of application system for portal panel, classifying panel maintenance management into resource attribute management, first authority attribute management, style attribute management and version attribute management, and dynamically managing the portal panel of each application system; based on the demand of application system for portal website, classifying portal content management into second authority attribute management and portal layout management; based on the second authority attribute management, dynamically allocating and managing the portal authority of each application system according to different dimensions, and based on portal layout management, dynamically updating and managing the portal content of each application system.

Description

Technical Field

[0001] The present application relates to the field of portal management technology, and in particular to a portal management and authority allocation method, device and medium based on aPaaS. Background Art

[0002] With the development of information technology, many enterprises have established their own application systems to assist in enterprise operation and management. However, as more and more application systems are used by enterprises, traditional portal management systems often face the following major problems:

[0003] (1) Inflexible portal panel management: The portal panel of the application system is usually fixed and cannot be dynamically combined and adjusted according to the needs of different application systems.

[0004] (2) Complex portal maintenance: Portals of different application systems need to be maintained separately, and there is a lack of a unified management platform, resulting in high maintenance costs and low efficiency.

[0005] (3) Delayed portal content updates: The portal content management of the application system is not updated in a timely manner and cannot support real-time content editing and dynamic insertion of multimedia elements.

[0006] (4) Imperfect portal permission management: The portal permission management mechanism of the application system is relatively simple and cannot dynamically adjust permissions based on user roles and behavior patterns, posing information security risks. Summary of the invention

[0007] The embodiment of the present application provides a portal management and authority allocation method, device and medium based on aPaaS to solve the problems existing in the related technologies. The technical solution is as follows:

[0008] In a first aspect, an embodiment of the present application provides a portal management and authority allocation method based on aPaaS, including:

[0009] Divide the management work of the portal management system based on aPaaS into panel maintenance management and portal content management;

[0010] Based on the requirements of the application system for the portal panel, the panel maintenance management is classified into resource attribute management, first authority attribute management, style attribute management and version attribute management;

[0011] Based on the resource attribute management, the first permission attribute management, the style attribute management and the version attribute management, the portal panel of each application system is dynamically managed; each application system is an application system that interacts with the aPaaS-based portal management system for data;

[0012] Based on the requirements of the application system for the portal website, the portal content management is classified into second authority attribute management and portal layout management;

[0013] Based on the second permission attribute management, the portal permission of each application system is dynamically allocated and managed according to different dimensions; and based on the portal layout management, the portal content of each application system is dynamically updated and managed.

[0014] In one embodiment, dynamically managing the portal panel of each application system based on the resource attribute management, the first permission attribute management, the style attribute management, and the version attribute management includes:

[0015] Based on the resource attribute management, the first authority attribute management, the style attribute management and the version attribute management, the resource attributes, the authority attributes, the style attributes and the version attributes of the portal panel of each application system are dynamically combined and adjusted.

[0016] In one embodiment, the resource attribute management includes panel resource storage management and panel resource acquisition management; wherein,

[0017] The panel resource storage management is used to: when the portal panel is a dynamic form panel, store the page code of the portal panel in the database in the form of JSON data; when the portal panel is a front-end resource panel, store the page code of the portal panel in the form of file data in the front-end project of its corresponding application system;

[0018] The panel resource acquisition management is used for: when the portal panel is a dynamic form panel, obtaining the page JSON data from the background according to the dynamic form primary key request, building the page code according to the page JSON data, and then rendering the content of the current portal panel according to the page code; when the portal panel is a front-end resource panel, obtaining the page code according to the file path, and then rendering the content of the current portal panel according to the page code.

[0019] In one embodiment, the first permission attribute management includes external permission management and internal permission management; wherein, the external permission management is used to manage whether the portal panel is visible to other tenants of each application system; and the internal permission management is used to manage whether the portal panel is available to each application system.

[0020] In one embodiment, the style attribute management is used to maintain and manage the necessary initial style and display of the portal panel;

[0021] The version attribute management is used to manage the resource attributes of the portal panel according to the version.

[0022] In one embodiment, dynamically allocating and managing the portal authority of each application system according to different dimensions based on the second authority attribute management includes: dynamically allocating and managing the portal authority of each application system according to the organizational dimension, the user dimension, and the role dimension based on the second authority attribute management;

[0023] Based on the portal layout management, the portal content of each application system is dynamically updated and managed, including: after the portal is created, based on the front-end configuration interface of each application system and the maintained portal panel, the default layout corresponding to each portal of each application system is configured; if the portal currently in use has not been configured with a portal layout, the default layout corresponding to the portal currently in use is displayed, otherwise, the portal with portal permissions is switched, and a secondary configuration is performed based on the default layout of the portal and the portal panel selected when configuring the default layout, so as to build and display the personalized layout of the portal.

[0024] In one embodiment, the front-end configuration interface is configured with a vue-grid-layout component library, and any component in the vue-grid-layout component library can be organized and arranged by dragging and dropping.

[0025] In one implementation, the second permission attribute management includes whether to disclose permission attribute management, whether to enable permission attribute management, and whether to default permission attribute management, wherein:

[0026] The public permission attribute management is used to manage whether each portal of each application system is visible to other tenants of each application system;

[0027] The whether to enable permission attribute is used to manage whether each portal of each application system is available to each application system;

[0028] The default permission attribute management is used to manage whether each portal of each application system can be authorized. When each portal is in a non-default state, each user is authorized according to different dimensions. When each portal is in a default state, each portal is available to all users under the current tenant of each application system.

[0029] In a second aspect, an embodiment of the present application further provides a computer device, comprising: a memory and a processor, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement a method in any one of the above-mentioned aspects, wherein the memory and the processor communicate with each other through an internal connection path.

[0030] In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the method in any one of the above-mentioned embodiments is implemented.

[0031] The advantages or beneficial effects of the above technical solution include at least:

[0032] (1) Improve the flexibility of portal panel management: dynamically combine and adjust portal panels according to the needs of different application systems to meet the diverse needs of portal panels;

[0033] (ii) Simplify portal maintenance: Maintaining the portal panel as portals of different application systems can efficiently maintain the portals of different application systems, reduce maintenance costs, and improve work efficiency;

[0034] (III) Realize real-time update of portal content: Administrators can update and edit portal content in real time through portal layout management in portal content management on the aPaaS-based portal management system, support dynamic insertion and layout adjustment of multimedia elements, and improve user experience.

[0035] (iv) Enhance the dynamism of portal permission management: Through permission attribute management in portal content management, portal permissions can be dynamically adjusted according to organization, user or role to improve the security and flexibility of portal information.

[0036] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present application will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed in the present application and should not be regarded as limiting the scope of the present application.

[0038] Figure 1 A flowchart of a portal management and authority allocation method based on aPaaS provided in an embodiment of the present application;

[0039] Figure 2 An example diagram of a corresponding interface for panel maintenance management provided in an embodiment of the present application;

[0040] Figure 3 An example diagram of a corresponding interface of portal content management provided in an embodiment of the present application;

[0041] Figure 4 An example diagram of a process for panel resource acquisition management provided in an embodiment of the present application;

[0042] Figure 5 An example diagram of the execution process of a portal panel rendering configuration terminal provided in an embodiment of the present application;

[0043] Figure 6 An example diagram of the execution process of a portal panel rendering display terminal provided in an embodiment of the present application;

[0044] Figure 7 A structural block diagram of an aPaaS-based portal management system provided in an embodiment of the present application;

[0045] Figure 8 A structural block diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.

[0047] Figure 1 FIG. 1 is a flow chart showing a portal management and authority allocation method based on aPaaS according to an embodiment of the present application. Figure 1 As shown, the method may include the following steps:

[0048] S110 , dividing the management work of the portal management system based on aPaaS into panel maintenance management and portal content management.

[0049] In specific implementation, aPaaS refers to application platform as a service. The aPaaS platform provides a more flexible development environment and operating platform, making portal management more dynamic and personalized.

[0050] In one implementation, in order to facilitate the management of the needs of different application systems for portal panels and portal content, the management work of the aPaaS-based portal management system can be divided into panel maintenance management and portal content management. It can also be understood as portal management and authority allocation for the application system from the two aspects of panel maintenance and portal content.

[0051] For example, the corresponding interface of the panel maintenance management can be as follows: Figure 2 As shown, the corresponding interface of portal content management can be as follows Figure 3 shown.

[0052] S120. Based on the requirements of the application system for the portal panel, the panel maintenance management is classified into resource attribute management, first authority attribute management, style attribute management and version attribute management.

[0053] In specific implementation, a panel is an independent display area used to place a certain type of content page. For example, a carousel panel is used to display a carousel page composed of some promotional pictures, and an application system panel is used to display a list page composed of available application systems. As the entry interface of the application system, the portal is usually divided into multiple panels when designing the portal. Panel maintenance management is responsible for maintaining these panels for easy reuse and updating.

[0054] In specific implementation, when adding a portal panel for each application system, in addition to configuring the necessary description information of the portal panel itself (such as the panel name), it is also necessary to configure the resource attributes, permission attributes, style attributes and version attributes of the portal panel.

[0055] Based on this, in an embodiment of the present application, in order to facilitate dynamic management of the portal panel, the panel maintenance management is classified into resource attribute management, first authority attribute management, style attribute management and version attribute management.

[0056] S130 , dynamically managing the portal panel of each application system based on resource attribute management, first authority attribute management, style attribute management, and version attribute management.

[0057] In specific implementation, each application system referred to in this article is an application system that interacts with the aPaaS-based portal management system for data.

[0058] In one implementation, step S130 may include: dynamically combining and adjusting resource attributes, permission attributes, style attributes and version attributes of the portal panel of each application system based on resource attribute management, first permission attribute management, style attribute management and version attribute management.

[0059] In specific implementation, portal panels are usually classified into front-end resource panels (panels whose content is front-end resource pages) and dynamic form panels (panels whose content is dynamic form pages). Based on this, in an embodiment of the present application, in terms of resource attribute management, the portal panel of each application system can be managed according to different panel types.

[0060] For example, resource attribute management may include panel resource storage management and panel resource acquisition management. Among them, panel resource storage management is used for: when the portal panel is a dynamic form panel, the page code of the portal panel is stored in the database as JSON data. In other words, the dynamic form page code is uniformly stored in the database as a JSON string; when the portal panel is a front-end resource panel, the page code of the portal panel is stored in the front-end project of its corresponding application system as file data. In other words, the front-end resource page code is uniformly stored in the front-end project of the application system as a file. Panel resource acquisition management is used for: when the portal panel is a dynamic form panel, the background is requested to obtain the page JSON data according to the dynamic form primary key, the page code is constructed according to the page JSON data, and then the content of the current portal panel is rendered according to the page code; when the portal panel is a front-end resource panel, the page code is obtained according to the file path, and then the content of the current portal panel is rendered according to the page code.

[0061] Among them, the dynamic forms mentioned above refer to form pages dynamically constructed through low-code platforms, which can greatly reduce the difficulty of page development and improve development efficiency. The front-end resources mentioned above, in contrast to dynamic forms, refer to form pages written in manual code in the front-end engineering of the application system, which can be freely combined with various front-end technologies to achieve, and are generally used to write pages with a high degree of complexity or sophistication.

[0062] As an example, the process of panel resource acquisition management can be as follows: Figure 4 As shown. It can be understood that, for the front-end resource panel, the path to obtain the content page is the relative file path of the code file, while for the dynamic form panel, the path to obtain the content page is the primary key of the page JSON data in the database. When needed, the JSON data can be obtained through the interface request and rendered into the portal panel.

[0063] In one implementation, in order to facilitate maintenance and management of the permissions of the portal panel, in the implementation of this application, the permissions of the portal panel of each application system are managed by dividing different permissions.

[0064] For example, the permissions of the portal panel can be classified into external permissions and internal permissions, that is, the first permission attribute management includes external permission management and internal permission management. Among them, the external permission management is used to manage whether the portal panel is publicly visible to other tenants of each application system, that is, the creator can see all portal panels of the same tenant and portal panels publicly disclosed by other tenants under each application system, and the publicly disclosed portal panels only have usage permissions but no modification permissions; the internal permission management is used to manage whether the portal panel is available for each application system, that is, to manage whether the portal panel is currently available for each application system.

[0065] In one embodiment, the style attribute management is used to maintain and manage the necessary initial style and display of the portal panel. It can also be understood that the style attribute management is mainly to maintain some necessary initial styles and display information of the portal panel, such as the width and height of the portal panel, the icon of the portal panel, the thumbnail of the portal panel, etc.

[0066] In one implementation, in order to facilitate displaying different page resources for portal panels of different versions, in the embodiment of the present application, each portal panel may be configured to be associated with a version attribute to control the resource attributes of the portal panel by version. That is, the version attribute management is used to manage the resource attributes of the portal panel according to the version.

[0067] For example, in the version attribute management, the newly added portal panel will be recorded as the default version, and after the portal panel is modified, you can choose to publish the modified portal panel as a new version or save it to the old version. At the same time, each portal panel can be online or offline multiple versions, and only the online version of the portal panel can be used for portal layout configuration.

[0068] In the embodiment of the present application, by executing step S120 and step S130, the flexibility of portal panel management can be improved and portal maintenance can be simplified. For example, the portal panel can be dynamically combined and adjusted according to the needs of different application systems to meet the diverse needs of the portal panel. In addition, the portal panel can be maintained as a portal of different application systems, which can efficiently maintain the portals of different application systems, reduce maintenance costs, and improve work efficiency.

[0069] S140: Based on the requirements of the application system for the portal website, the portal content management is classified into the second authority attribute management and the portal layout management.

[0070] In the specific implementation, during the implementation of step S140, as with the panel maintenance management, the portal content management can be divided and configured according to different application systems. For example, in the second permission attribute management, each application system can customize multiple portals, and in the portal layout management, each portal can use all enabled portal panels in the application system to configure its own default layout, so that the portal can be made dynamic by switching different portals.

[0071] S150. Based on the second permission attribute management, dynamically allocate and manage the portal permissions of each application system according to different dimensions, and based on the portal layout management, dynamically update and manage the portal content of each application system.

[0072] In one implementation, dynamically allocating and managing the portal permissions of each application system according to different dimensions based on the second permission attribute management may include: dynamically allocating and managing the portal permissions of each application system according to the organizational dimension, the user dimension, and the role dimension based on the second permission attribute management.

[0073] In one embodiment, the second permission attribute management includes whether to disclose permission attribute management, whether to enable permission attribute management, and whether to default permission attribute management, wherein whether to disclose permission attribute management is used to manage whether each portal of each application system is visible to other tenants of each application system; whether to enable permission attributes is used to manage whether each portal of each application system is available to each application system; whether to default permission attribute management is used to manage whether each portal of each application system can be authorized. When each portal is in a non-default state, each user is authorized according to different dimensions (such as different dimensions such as organization, user, role, etc.); when each portal is in a default state, each portal is available to all users under the current tenant of each application system.

[0074] It can be understood that whether to disclose the permission attribute management and whether to enable the permission attribute management are similar to the external permission management and internal permission management in the above panel maintenance management.

[0075] In one embodiment, based on the portal layout management, the portal content of each application system is dynamically updated and managed, including: after the portal is created, based on the front-end configuration interface of each application system and the maintained portal panel, the default layout corresponding to each portal of each application system is configured; if the portal currently used has not been configured with a portal layout, the default layout corresponding to the portal currently used is displayed; otherwise, the portal with portal authority is switched, and secondary configuration is performed based on the default layout of the portal and the portal panel data selected when configuring the default layout, and the personalized layout of the portal is built and displayed. After the personalized layout of each portal is built, the personalized layout can be saved as the layout data of each portal.

[0076] In one implementation, the front-end configuration interface may be configured with a vue-grid-layout component library, and any component in the vue-grid-layout component library may be organized and arranged by dragging and dropping.

[0077] For example, based on the vue-grid-layout component library, developers can dynamically organize and arrange the page elements of each portal, that is, quickly build a responsive grid layout interface by dragging and dropping, and each grid corresponds to a portal panel. In the portal interface of each application system, for the portal currently in use, if the user layout has not been configured, the default layout of the portal is displayed by default, otherwise the user layout is displayed. In the process of displaying the user layout, the vue-grid-layout component library is also used. For example, system users can freely switch portals with portal permissions, and perform secondary configuration based on the default layout of the portal and the portal panel selected when configuring the default layout, build a personalized layout and save it as their own data.

[0078] As an example, in step S150, by combining the upper and lower versions of the portal panel and the permission control, the portal content can be flexibly displayed and updated. Figure 5 The execution process of the portal panel rendering configuration end shown and Figure 6 The execution process of the portal panel rendering display end shown is used to realize flexible display and update of portal content.

[0079] In the embodiment of the present application, by executing step S140 and step S150, the real-time update of portal content and the enhancement of the dynamic nature of portal authority management can be achieved. For example, the administrator can update and edit portal content in real time through portal layout management in portal content management on the aPaaS-based portal management system, support dynamic insertion and layout adjustment of multimedia elements, improve user experience, and dynamically adjust portal authority according to organization, user or role through authority attribute management in portal content management, thereby improving the security and flexibility of portal information.

[0080] From the above description, it can be seen that the aPaaS-based portal management and authority allocation method provided in the embodiment of the present application can realize flexible management of portal panels, dynamic maintenance of portals, real-time updating of portal content, and dynamic allocation of portal authorities.

[0081] Figure 7 FIG. 1 shows a structural block diagram of a portal management system based on aPaaS according to an embodiment of the present application. Figure 7 As shown, the aPaaS-based portal management system may include: a panel maintenance management unit 210 and a portal content management unit 220 .

[0082] Among them, the panel maintenance management unit 210 includes a panel module and a panel authority control module. The panel module can be used to implement the corresponding processing procedures of resource attribute management, style attribute management and version attribute management in the above-mentioned panel maintenance management, and the panel authority control module is used to implement the corresponding processing procedures of authority attribute management in the above-mentioned panel maintenance management.

[0083] The portal content management unit 220 includes a portal module and a portal authority control module. The portal module is used to implement the corresponding processing of portal layout management in the above portal content management. The portal authority control module is used to implement the corresponding processing of authority attribute management in the above portal content management.

[0084] The functions of each unit in the aPaaS-based portal management system in the embodiment of the present application can be found in the corresponding description in the above method, and will not be repeated here.

[0085] Figure 8 FIG. 2 shows a block diagram of a computer device according to an embodiment of the present application. Figure 8 As shown, the computer device includes: a memory 310 and a processor 320. The memory 310 stores instructions, and the instructions are loaded and executed by the processor 320 to implement the portal management and authority allocation method based on aPaaS in the above embodiment. The number of the memory 310 and the processor 320 can be one or more.

[0086] The computer device also includes:

[0087] The communication interface 330 is used to communicate with external devices and perform data exchange transmission.

[0088] If the memory 310, the processor 320 and the communication interface 330 are implemented independently, the memory 310, the processor 320 and the communication interface 330 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0089] Optionally, in a specific implementation, if the memory 310, the processor 320 and the communication interface 330 are integrated on a chip, the memory 310, the processor 320 and the communication interface 330 can communicate with each other through an internal interface.

[0090] An embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the method provided in the embodiment of the present application is implemented.

[0091] An embodiment of the present application also provides a chip, which includes a processor for calling and executing instructions stored in a memory, so that a communication device equipped with the chip executes the method provided by the embodiment of the present application.

[0092] An embodiment of the present application also provides a chip, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the application.

[0093] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting the Advanced RISC Machines (ARM) architecture.

[0094] Further, optionally, the above-mentioned memory may include a read-only memory and a random access memory, and may also include a non-volatile random access memory. The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may include a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available. For example, static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).

[0095] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.

[0096] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.

[0097] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0098] Any process or method description in the flow chart or otherwise described herein can be understood to represent a module, fragment or portion of a code including one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.

[0099] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be embodied in any computer-readable medium for use by an instruction execution system, apparatus or device (such as a computer-based system, a system including a processor or other system that can fetch instructions from an instruction execution system, apparatus or device and execute instructions), or used in combination with these instruction execution systems, apparatuses or devices.

[0100] It should be understood that the various parts of the present application can be implemented with hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented with software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium, and when the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0101] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a disk or an optical disk, etc.

[0102] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A portal management and authority allocation method based on aPaaS, characterized in that: include: Divide the management work of the portal management system based on aPaaS into panel maintenance management and portal content management; Based on the requirements of the application system for the portal panel, the panel maintenance management is classified into resource attribute management, first authority attribute management, style attribute management and version attribute management; Based on the resource attribute management, the first permission attribute management, the style attribute management and the version attribute management, the portal panel of each application system is dynamically managed; each application system is an application system that interacts with the aPaaS-based portal management system for data; Based on the requirements of the application system for the portal website, the portal content management is classified into second authority attribute management and portal layout management; Based on the second permission attribute management, dynamically assigning and managing the portal permissions of each application system according to different dimensions, and based on the portal layout management, dynamically updating and managing the portal content of each application system; Wherein, the resource attribute management includes panel resource storage management and panel resource acquisition management, and the panel resource storage management is used to: when the portal panel is a dynamic form panel, store the page code of the portal panel in the database in the form of JSON data; when the portal panel is a front-end resource panel, store the page code of the portal panel in the form of file data in the front-end project of its corresponding application system; The panel resource acquisition management is used to: when the portal panel is a dynamic form panel, obtain the page JSON data from the background according to the dynamic form primary key request, build the page code according to the page JSON data, and then render the content of the current portal panel according to the page code; when the portal panel is a front-end resource panel, obtain the page code according to the file path, and then render the content of the current portal panel according to the page code; Among them, based on the portal layout management, the portal content of each application system is dynamically updated and managed, including: after the portal is created, based on the front-end configuration interface of each application system and the maintained portal panel, the default layout corresponding to each portal of each application system is configured; if the portal currently in use has not been configured with a portal layout, the default layout corresponding to the portal currently in use is displayed, otherwise, the portal with portal permissions is switched, and a secondary configuration is performed based on the default layout of the portal and the portal panel selected when configuring the default layout, so as to build and display the personalized layout of the portal.

2. The method according to claim 1, characterized in that Based on the resource attribute management, the first permission attribute management, the style attribute management and the version attribute management, dynamically managing the portal panel of each application system includes: Based on the resource attribute management, the first authority attribute management, the style attribute management and the version attribute management, the resource attributes, the authority attributes, the style attributes and the version attributes of the portal panel of each application system are dynamically combined and adjusted.

3. The method according to claim 1 or 2, characterized in that: The first permission attribute management includes external permission management and internal permission management; wherein the external permission management is used to manage whether the portal panel is visible to other tenants of each application system; and the internal permission management is used to manage whether the portal panel is available to each application system.

4. The method according to claim 1 or 2, characterized in that: The style attribute management is used to maintain and manage the necessary initial style and display of the portal panel; The version attribute management is used to manage the resource attributes of the portal panel according to the version.

5. The method according to claim 1, characterized in that Based on the second permission attribute management, dynamically allocating and managing the portal permissions of each application system according to different dimensions includes: based on the second permission attribute management, dynamically allocating and managing the portal permissions of each application system according to the organizational dimension, the user dimension and the role dimension.

6. The method according to claim 1, characterized in that The front-end configuration interface is configured with a vue-grid-layout component library, and any component in the vue-grid-layout component library can be organized and arranged by dragging.

7. The method according to claim 5, characterized in that The second permission attribute management includes whether to disclose permission attribute management, whether to enable permission attribute management, and whether to default permission attribute management, wherein: The public permission attribute management is used to manage whether each portal of each application system is visible to other tenants of each application system; The whether to enable permission attribute is used to manage whether each portal of each application system is available to each application system; The default permission attribute management is used to manage whether each portal of each application system can be authorized. When each portal is in a non-default state, each user is authorized according to different dimensions. When each portal is in a default state, each portal is available to all users under the current tenant of each application system.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement the method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the method according to any one of claims 1 to 7 is implemented.

Images