Webpage interface loading method, electronic equipment and storage medium

Abstract

The invention discloses a webpage interface loading method, electronic equipment and a storage medium, and the method comprises the steps: obtaining at least one user contained in a target item, and configuring a binding relationship between each user and at least one corresponding role, configuring a binding relationship between each role and at least one corresponding workbench in the workbench warehouse; a plurality of workbenches stored in the workbench warehouse are obtained by arranging a plurality of service widgets in advance according to preset service requirements, and each workbench is configured to be bound with part of roles; in response to a login request of a target user in the target project, determining a target workbench of the target user by using the binding relationship, and further completing loading of the webpage interface by using the target workbench; according to the method and the device, the many-to-many relationship between the user and the workbench is realized, the differentiated requirements of massive business scenes on webpage interfaces are met, the quick delivery of projects is effectively realized, the development cost is reduced, and the working efficiency is improved.

Description

Technical Field

[0001] The present application relates to the technical field of differentiated working interfaces, and in particular to a web page interface loading method, an electronic device and a storage medium. Background Art

[0002] With the explosive growth of computer applications, the Internet of Things has entered a stage of rapid development of full-scenario IoT. More and more multi-dimensional sensing devices and rich services are loaded into the IoT management platform, such as video, access control, parking, portrait, attendance, fire protection, alarm host, etc.

[0003] However, in the specific process of implementing the baseline IoT management platform in various industries, there are great differences in the scenarios and concerns used by different industries, different positions, different users, and different projects. First, different industries will have differences due to different perception methods and different business scenarios. Secondly, different users will have differences due to different concerns and different display style requirements. In addition, different projects will have differences due to different management specifications and different business scopes under user jurisdiction. In addition, IoT platform manufacturers usually adopt project customization development to solve the deviation between the project and the baseline. On the one hand, it is time-consuming, labor-intensive and costly, and at the same time, it does not solve the pain point of different users in different industries who want to use the core work interface that better matches their own scenarios. That is, how to meet the differentiated needs of massive business scenarios for the core work interface, achieve rapid project delivery, reduce development costs, and thus improve work efficiency is a technical problem that needs to be solved at present. Summary of the invention

[0004] The present application mainly solves the current technical problems through the following technical solutions, and provides a web page interface loading method, an electronic device and a storage medium. By binding each user in the target project to at least one role, and each role is configured to be bound to at least one workbench, a many-to-many relationship between users and workbenches is realized, which meets the differentiated requirements of massive business scenarios for web pages. The interface is effectively delivered quickly, development costs are reduced, and work efficiency is improved.

[0005] To solve the above technical problems, a technical solution adopted in the present application is: providing a web page interface loading method, comprising: obtaining at least one user included in the target project, and configuring a binding relationship between each user and at least one corresponding role, and then configuring a binding relationship between each role and at least one corresponding workbench in the workbench warehouse; wherein, the several workbenches stored in the workbench warehouse are obtained by pre-arranging multiple business widgets according to preset business requirements, and each of the workbenches is configured to be bound to some roles; the role is used to represent an identity or function of a group of related permissions; in response to a login request of a target user in the target project, the target workbench of the target user is determined by using the binding relationship, and then the loading of the web page interface is completed by using the target workbench.

[0006] In some embodiments, the step of obtaining at least one user included in the target project and configuring a binding relationship between each user and at least one corresponding role, and then configuring a binding relationship between each role and at least one corresponding workbench in the workbench warehouse, includes: obtaining at least one user included in the target project; configuring a first binding relationship between each of the users and at least one corresponding role; using the role, selecting at least one bindable workbench from the workbench warehouse, and then configuring a second binding relationship between each of the roles and at least one workbench; using the first binding relationship and the second binding relationship, determining a binding relationship between each of the users and at least one workbench through each of the roles, and setting it as a first type of binding relationship.

[0007] In some embodiments, it also includes: utilizing preset business requirements, pre-selecting a plurality of corresponding business widgets from a business widget library for orchestration, generating a workbench matching the preset business requirements, and then obtaining a plurality of workbenches stored in the workbench warehouse, wherein the orchestrated workbench includes at least: workbench basic information, workbench layout information, and business widget list information.

[0008] In some embodiments, the binding relationship is determined by a first binding relationship and a second binding relationship, and the binding relationship is a first type of binding relationship, wherein the first binding relationship represents the binding between the user and the role, and the second binding relationship represents the binding between the role and at least one workbench in the workbench warehouse; the response to the login request of the target user in the target project, using the binding relationship to determine the target workbench of the target user, includes: responding to the login request, determining the target user in the target project corresponding to the login request; determining the target role corresponding to the target user by using the first binding relationship; determining the target workbench corresponding to the target role by using the second binding relationship, and then using the target workbench corresponding to the target role as the target workbench of the target user.

[0009] In some embodiments, before using the first binding relationship to determine the target role corresponding to the target user, it also includes: in response to the existence of a third binding relationship with the user, using the third binding relationship to select at least one workbench from the workbench warehouse as the target workbench of the user, and setting it as a second type of binding relationship, wherein the third binding relationship represents the binding of the user to at least one workbench in the workbench warehouse; in response to a login request, using the target workbench to complete the loading of the web page interface.

[0010] In some embodiments, it also includes: the workstation includes a first type of workstation and a second type of workstation, and the priority of the first type of workstation is greater than the priority of the second type of workstation; the use of the first binding relationship to determine the target role corresponding to the target user includes: in response to the target user not having the second type of binding relationship, using the first binding relationship to determine the target role corresponding to the target user; the use of the second binding relationship to determine the target workstation corresponding to the target role includes: in response to the target role corresponding to multiple workstations, using the loading priority and the second binding relationship to determine the target workstation corresponding to the target role, wherein the loading priority represents the current business focus of the target user; or in response to the target role corresponding to only one workstation, the target role is associated with the workstation, and the associated workstation is loaded as the target workstation, wherein the workstation bound to the target role is the second type of workstation, and the target workstation of the user determined by the second type of binding relationship is the first type of workstation.

[0011] In some embodiments, the workbench is customized for a target user or a target role and directly bound, and the workbench customized for the target user is a first type of workbench.

[0012] In some embodiments, it also includes: the workbench also includes a third type of workbench, the third type of workbench is a basic workbench, wherein the priority of the second type of workbench is greater than the priority of the third type of workbench; the user can also use the business module entrance of the third type of workbench to enter the function menu to perform specific business operations.

[0013] In some embodiments, it also includes: obtaining the target user's operation information on the business widget during the work process of the target workstation, wherein the operation information at least includes click count information, dwell time information, and click sequence information; using the click count information, the dwell time information, and the click sequence information to determine the value score and association of each business widget; dividing different areas of the target workstation according to the value score to obtain different value score areas; using the value score, the association, and the different value score areas to adjust the area of ​​the business widget of the target workstation, and in response to the user's confirmation of the adjusted target workstation, loading the adjusted target workstation.

[0014] To solve the above technical problems, another technical solution adopted in the present application is: to provide an electronic device, the electronic device comprising a memory and a processor coupled to the memory, the memory storing at least one computer program, and when the at least one computer program is loaded and executed by the processor, it is used to implement the web page interface loading method as mentioned above.

[0015] To solve the above technical problems, another technical solution adopted in the present application is: providing a computer-readable storage medium, wherein the computer-readable storage medium has at least one program, and when the at least one program is loaded and executed by the processor, it is used to implement the web page interface loading method as described above.

[0016] Different from the current technology, the web page interface loading method provided by the present application includes: obtaining at least one user included in the target project, and configuring the binding relationship between each user and the corresponding at least one role, and then configuring the binding relationship between each role and the corresponding at least one workbench in the workbench warehouse; wherein, the several workbenches stored in the workbench warehouse are obtained by pre-arranging multiple business widgets according to preset business requirements, and each workbench is configured to be bound to some users; in response to the login request of the target user in the target project, the target workbench of the target user is determined by using the binding relationship, and then the loading of the web page interface is completed by using the target workbench; that is, in the present application, each user in the target project is bound to at least one role, and each role is bound to at least one workbench, thereby realizing a many-to-many relationship between users and workbenches, meeting the differentiated needs of massive business scenarios for web pages The interface, for different projects, can effectively achieve rapid project delivery, reduce development costs, and improve work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. Among them: Figure 1 It is a flowchart of an embodiment of a web page interface loading method in the present application; Figure 2 It is a structural diagram of an embodiment of a physical management platform in this application; Figure 3 It is a structural diagram of an embodiment of an association model in this application; Figure 4 It is a schematic diagram of the process of loading an embodiment of the workbench in this application; Figure 5 It is a structural diagram of an embodiment of a web page interface loading system in the present application; Figure 6 It is a structural schematic diagram of an embodiment of an electronic device in the present application; Figure 7 It is a structural diagram of an embodiment of a computer-readable storage medium in the present application. DETAILED DESCRIPTION

[0018] The present invention will be further described in detail below in conjunction with the accompanying drawings and examples. It is particularly noted that the following examples are only used to illustrate the present invention, but are not intended to limit the scope of the present invention. Similarly, the following examples are only partial embodiments of the present invention rather than all embodiments, and all other embodiments obtained by those of ordinary skill in the art without creative work are within the scope of protection of the present invention.

[0019] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0020] IoT management platform vendors usually adopt a project-customized development approach to resolve the deviations between baseline products and specific projects. That is, they conduct customized development based on the differences in usage scenarios and focus points of different industries, different users, and different projects. This is time-consuming, labor-intensive, and costly, and it also does not resolve the pain points of different industries and different users in using a work interface that better matches their own scenarios.

[0021] Therefore, a web page interface loading method is provided, in which each user in the target project is bound to at least one role, and each role is bound to at least one workbench, thereby realizing a many-to-many relationship between users and workbenches, meeting the differentiated requirements of massive business scenarios for web pages interfaces, and effectively realizing rapid project delivery for different projects, reducing development costs, and improving work efficiency.

[0022] See also Figure 1 , Figure 1 is a flow chart of an embodiment of a web page interface loading method in the present application; it should be noted that if there is a substantial result, the method of the present application is not based on Figure 1 The process sequence shown is limited.

[0023] like Figure 1 As shown, the web page interface loading method may include the following steps.

[0024] S10. Obtain at least one user included in the target project, and configure a binding relationship between each user and at least one corresponding role, and then configure a binding relationship between each role and at least one corresponding workbench in the workbench warehouse; wherein, the several workbenches stored in the workbench warehouse are obtained by pre-arranging multiple business widgets according to preset business requirements; each workbench is configured to be bound to some roles; and the roles are used to represent the identity or function of a group of related permissions.

[0025] Among them, target projects refer to specific implementation projects, for example, baseline IoT management platform products can be implemented in projects in the park industry or in projects in the financial industry; users refer to users corresponding to different management scopes under specific projects, for example, park management platform projects can include administrative users, security users, operation and maintenance users, etc.; roles refer to abstract concepts with a set of related permissions in the platform, representing the identity or function of the user in a specific context, such as administrative roles have permissions for access control, attendance services and equipment, and security roles have permissions for monitoring, alarm services and equipment; workbench refers to the page that integrates the entrances to commonly used modules of the platform, that is, the core work interface after the user logs in, and the user can perform common business operations on the workbench.

[0026] Specifically, at least one user included in the target project is obtained, and a binding relationship between each user and at least one corresponding role is configured; then the workbenches stored in the workbench warehouse are traversed, and a binding relationship between each role in the target project and at least one workbench is configured.

[0027] In some embodiments, a number of workbenches are pre-stored in a workbench warehouse, and each workbench is determined by pre-orchestrating multiple business widgets based on preset business requirements. When binding is required, each workbench can be configured to be bound to at least one role, that is, the number of roles bound to each workbench is less than the total number of roles in the target project. Among them, a business widget refers to a functional module integrated to implement a certain function. Different business requirements correspond to different business widgets and orchestration layouts, thus forming several different workbenches.

[0028] The preset business requirement may be a business requirement in a specific scenario, and the relevant content of the business requirement is converted into the arrangement requirement of the business widget.

[0029] It can be understood that users can be bound to the workbench through roles, which is a first type of binding relationship, and users can also be directly bound to the workbench, which is a second type of binding relationship. That is, each project can have at least one user, and each user can be configured to bind at least one corresponding role. If the user is indirectly bound to the workbench through a role, there is an indirect first type of binding relationship, and if the user is directly bound to the workbench, there is a direct second type of binding relationship.

[0030] S20, in response to a login request of a target user in a target project, determining a target workstation of the target user by using the binding relationship, and then completing loading of the web page interface by using the target workstation.

[0031] Specifically, after determining the binding relationship between the role bound to each user in the target project and at least one corresponding workbench in the workbench warehouse, a login request is received, the target user in the target project is determined, and then in response to the login request, the binding relationship can be used to determine the target workbench corresponding to the target user, and then the target workbench is used to complete the loading of the current web page interface to provide the workbench matched by the user to perform related tasks.

[0032] In this application, each user in the target project is bound to at least one workbench through a bound role, thereby realizing a many-to-many relationship between users and workbenches, meeting the differentiated requirements of massive business scenarios for web interfaces, and effectively achieving rapid project delivery for different projects, reducing development costs, and improving work efficiency.

[0033] In some embodiments, the operation steps of loading the web page interface can be performed through the Internet of Things management platform. The Internet of Things management platform can include modules such as platform gateway, basic resource management, business subsystem and high-frequency analysis management.

[0034] See also Figure 2 , Figure 2 It is a structural diagram of an embodiment of a physical management platform in this application.

[0035] like Figure 2 As shown in the figure, the IoT management platform includes modules such as platform gateway, basic resource management, business subsystem, high-frequency analysis management and workbench engine; among them, platform gateway: the unified entrance of the platform, mainly responsible for the routing and distribution of business requests; basic resource management: the basic data management service of the IoT management platform, mainly responsible for the unified management of basic data such as equipment, organizations, departments, personnel, cards, vehicles, roles, permissions, etc. Business subsystem: a collection of services that implement functions in specific business fields, such as video subsystem, access control subsystem, and portrait subsystem. High-frequency analysis management: a service that aggregates and analyzes user clicks and stays and other operation information. Workbench engine: used for workbench management and orchestration services, with the capabilities of workbench orchestration, workbench rendering, user binding, business widget development, business widget management, authorization management, etc.

[0036] In addition, the workbench engine also includes a workbench warehouse, in which a plurality of workbenches are stored; and a widget warehouse, in which a plurality of business widgets are stored.

[0037] The IoT management platform can have the following operations: Workbench orchestration and application: Use the business widgets in the business widget warehouse in the workbench engine to complete the workbench orchestration, and then obtain the user list through the basic resource management service interface to complete the binding and associated data storage between the workbench and the user or role; High-frequency information reporting: User clicks and stays on the business subsystem are reported to the high-frequency analysis management service, which performs data statistics and association analysis; Workbench tuning: The workbench engine obtains high-frequency analysis results through the high-frequency analysis management service interface and completes the workbench tuning.

[0038] The workbench layout module is responsible for the workbench's new addition, import and export, deletion, copy, and viewing functions. A well-arranged workbench should contain the workbench basic information, workbench layout information, and business widget list information. This allows the workbench layout to be uniformly packaged and exported based on the referenced business widget information when exporting.

[0039] In some embodiments, step S10 obtains at least one user included in the target project, and configures a binding relationship between each user and at least one corresponding role, and then configures a binding relationship between each role and at least one corresponding workbench in the workbench warehouse; wherein, the several workbenches stored in the workbench warehouse are obtained by pre-arranging multiple business widgets according to preset business requirements, and each workbench is configured to be bound to some roles, which may include the following operations.

[0040] First, the users included in the target project are searched to determine the users included in the target project. In some embodiments, each project has one or more users, so at least one user included in the target project can be determined.

[0041] Next, bind at least one role to each user.

[0042] Among them, user refers to the account created on the platform for specific project personnel, and role refers to an abstract concept with a set of related permissions in the platform, which represents the identity or function of the user in a specific context. A user can be associated with multiple roles, and a role can also be associated with multiple users.

[0043] Then, bind the character to at least one workbench in the workbench warehouse.

[0044] The workbench may be obtained by pre-arranging multiple business widgets according to specific business requirements; each role may establish a binding relationship with one or more workbenches, and the binding relationship is stored in a database.

[0045] It can be understood that, if binding is required, each workbench can be bound to at least one role.

[0046] In this embodiment, a binding relationship is established between the role and the workbench, that is, the user forms an indirect binding relationship with the workbench through the role, that is, the first type of binding relationship, so that the first type of binding relationship can be directly used later to select the corresponding workbench for loading, thereby improving work efficiency.

[0047] Furthermore, the following operations may also be included.

[0048] First, a first binding relationship between each user and the role corresponding to the user is configured.

[0049] Among them, user refers to the account created on the platform for specific project personnel, and role refers to an abstract concept with a set of related permissions in the platform, which represents the identity or function of the user in a specific context. A user can be associated with multiple roles, and a role can also be associated with multiple users.

[0050] Specifically, for each user, a first binding relationship corresponding to each user and the role is configured.

[0051] Next, at least one bindable workbench is selected from the workbench warehouse, and a second binding relationship between the character and the at least one bindable workbench is configured.

[0052] Among them, each role can establish a binding relationship with at least one workbench.

[0053] Specifically, a workbench that can be bound to a role is selected from the workbench warehouse to configure the binding between the role and the workbench, that is, to establish a second binding relationship, wherein each role can establish a binding relationship with one or more workbenches.

[0054] Then, the binding relationship between each user and at least one workstation is determined by using the first binding relationship and the second binding relationship, and the indirect binding relationship between the user and the workstation through the role is set as a first type of binding relationship.

[0055] Specifically, because the first binding relationship represents the binding relationship between the user and the role, and the second binding relationship represents the binding relationship between the role and the workbench, the first binding relationship and the second binding relationship can be used to determine the binding relationship between each user and at least one workbench.

[0056] In some embodiments, users can also customize their own workstations. In this case, users can directly select at least one bindable workstation from the workstation warehouse, modify it according to user operating habits, and configure the corresponding binding relationship, that is, the third binding relationship. The third binding relationship can be used to determine the target workstation corresponding to the target user, and the direct binding relationship between the user and the workstation can be set to the second type of binding relationship; then, in response to the login request, the second type of binding relationship is used to determine the user's target workstation, and then the target workstation is used to complete the loading of the web page interface.

[0057] The following is an illustration of the association model of products, projects, users, roles, workbenches, and business widgets.

[0058] See also Figure 3 , Figure 3 It is a structural diagram of an embodiment of an association model in this application.

[0059] like Figure 3As shown, there can be multiple products, such as the first product, the second product, the third product, the Tth product, etc., and each product can have one or more projects; there can be multiple projects, such as the first project, the second project, the third project, the fourth project, and the Nth project; each project has one or more users, and each user can be associated with one or more roles; there can be multiple workbenches in the workbench warehouse, such as the first workbench, the second workbench, the third workbench, the fourth workbench, the fifth workbench, and the Mth workbench; there can be multiple business widgets in the business widget library, such as the first widget, the second widget, the third widget, the fourth widget, the fifth widget, the sixth widget, the seventh widget, and the Yth widget; then, the first The product includes the first project and the second project, the second product includes the third project, the third product includes the fourth project, and the Tth product includes the Nth project; the first project includes the first user and the second user, the first user is bound to the first role, the first role can be bound to the first workbench referenced by the first product, the second user is bound to the second role, the second role can be bound to the second workbench referenced by the first product; the second project includes the third user, the fourth user and the fifth user, the third user is bound to the third role, the fourth user and the fifth user can be bound to the fourth role, the third role can be bound to the second workbench referenced by the first product, and the third role can also be bound to the third workbench referenced by the first product, The fourth role can be bound to the sixth workbench newly created through the workbench engine in the project, that is, the sixth workbench is customized for the project and bound to the role; the third project contains the sixth user and the seventh user, the sixth user is bound to the fifth role and the sixth role, the fifth role can be bound to the third workbench referenced by the second product, the sixth role can be bound to the fourth workbench referenced by the second product, the seventh user is bound to the seventh role, the seventh role can bind to the fourth workbench and the fifth workbench referenced by the second product; the fourth project contains the eighth user and the ninth user, the eighth user is bound to the eighth role, the eighth role can bind to the fifth workbench referenced by the third product, the ninth user can bind to the eighth role, and make the ninth The user can bind to the fifth workbench referenced by the third product through the eighth role. The ninth user can also use a customized workbench, that is, the ninth user binds to the seventh workbench newly created by the workbench engine on the project, that is, the seventh workbench is customized for the project and bound to the user; the Nth project contains a user X, who is bound to a role Z, who is bound to the Mth workbench, that is, user X in the Nth project can be indirectly bound to the Mth workbench referenced by the baseline product of the project through role Z, which is a first type of binding relationship. User X can also be directly bound to the Mth workbench, which is a second type of binding relationship; each workbench is composed of one or more business widgets.

[0060] Among them, users can associate multiple workstations and switch between them, such as a third user binding the second workstation and the third workstation through a third role, and can switch between the second workstation and the third workstation; cross-industry workstations can also be included, and the aforementioned third workstation and fifth workstation are cross-industry general workstations, such as parking fees, visitor management and other general workstations; users can bind to workstations directly on the basis of binding roles to workstations, such as the ninth user associating the fifth workstation and the seventh workstation at the same time.

[0061] During baseline development, the workbench can reuse widgets from the business widget warehouse as needed to avoid repeated development of the same atomic business functions or integrated business function components; when releasing products, different industry platform product releases can reference workbenches in the workbench warehouse as needed; when industry platform products are implemented in projects, the workbench introduced by the product can be associated with the created platform role in the project, and users can associate available workbenches through associated roles; at the same time, users can also customize workbenches for their own use, so as to achieve the purpose of using differentiated workbenches for different industries, different projects, and different users. Through the optimization of the associated data model, the IoT management platform has derived a flexible and changeable baseline product and project implementation mechanism, which greatly improves the matching degree of the platform user's core work interface to massive business scenarios.

[0062] In this embodiment, after a first binding relationship is established between each user and a role, and a second binding relationship is established between each role and a workbench, each user has a binding relationship with at least one corresponding workbench, the business concern corresponding to each user is clarified, and the first type of binding relationship of indirect binding between the user and the workbench is further clarified, thereby improving the adaptability of the workbench to the user; if the user needs to customize the workbench corresponding to the user himself, a third binding relationship can be established between the user and the workbench, thereby clarifying the second type of binding relationship of direct binding between the user and the workbench, thereby improving the breadth of application.

[0063] Furthermore, the following operations may also be included: By using preset business requirements, multiple corresponding business widgets are selected in advance from the business widget library for arrangement, and a workbench matching the preset business requirements is generated, thereby obtaining a plurality of workbenches stored in the workbench warehouse.

[0064] First, multiple business widgets are developed and stored in a widget warehouse, wherein the business widgets can be reused in different workbenches.

[0065] Among them, the business widget refers to the integrated functional module used to realize a certain function, which can be reused in different workbenches. The reuse here means copying a business widget to the corresponding workbench without affecting other workbenches; for example, the visitor information business widget is used for the management of visitor information; the vehicle charging business widget is used for the management of vehicle charging information.

[0066] Specifically, a business widget development tool may be used to complete business widget development to obtain multiple business widgets, and then the multiple business widgets are stored in a widget warehouse.

[0067] Next, the web page interface is laid out according to professional experience for different business requirements, and the obtained multiple pre-selected business widgets are arranged to complete the workbench corresponding to each type of business requirement, thereby obtaining a number of workbenches stored in the workbench warehouse.

[0068] Specifically, according to the characteristics of each type of business, the location where the pre-selected business widget is to be placed is determined, and then multiple pre-selected business widgets are arranged to obtain a workbench that meets the type of business, and then the workbench is stored in a workbench warehouse to obtain several workbenches in the workbench warehouse.

[0069] In some embodiments, when a suitable workbench matching a special scenario of the project cannot be found in the existing workbench warehouse of the project, a corresponding workbench can be formulated according to the user's specific scheduling requirements to meet the user's specific needs for the workbench.

[0070] In this embodiment, by developing business widgets in advance and then completing the arrangement of multiple workbenches according to specific business requirements, a number of workbenches are prepared in advance for the workbench warehouse, so that the appropriate workbench can be directly selected from the workbench warehouse for loading later, thereby improving work efficiency.

[0071] In some embodiments, step S20 responds to a login request of a target user in a target project, determines a target workstation of the target user using a binding relationship, and then uses the target workstation to complete loading of a web page interface, which may include the following operations.

[0072] First, in response to a login request, a target user in a target item corresponding to the login request is determined.

[0073] The login request refers to a request for logging into the current web page interface, and may point to a specific user in a specific project. The target user refers to the user that the login request requires to log in.

[0074] Specifically, when the current web page interface receives a login request, in response to the login request, the target user corresponding to the login request is parsed, and then the target user corresponding to the login request is determined.

[0075] Next, the role corresponding to the target user is determined using the first binding relationship.

[0076] Specifically, because each user has a corresponding first binding relationship, the role of each user with the first binding relationship can be obtained.

[0077] Further, in response to the target user not having the second type of binding relationship, the first binding relationship is used to determine the target role corresponding to the target user.

[0078] Then, the second binding relationship is used to determine the target workbench corresponding to the role.

[0079] Specifically, because each character has a corresponding second binding relationship, the target workbench with which each character has a second binding relationship can be determined.

[0080] In some embodiments, each role can be bound to multiple workbenches. When a user logs in, one of the workbenches can be selected as the target workbench to load. Each workbench can also be bound to multiple roles, realizing a many-to-many relationship between roles and workbenches.

[0081] Furthermore, the following operations may also be included: Before using the first binding relationship to determine the role corresponding to the target user, you can also first determine whether the target user has a second type of binding relationship, that is, whether there is a third binding relationship, and then use the third binding relationship to determine that the workstation to which the target user is bound is the target workstation, and set it to the second type of binding relationship, where the workstation to which the target user is bound is the first type of workstation.

[0082] Specifically, first determine whether the target user has a third binding relationship, and if the target user does not have the third binding relationship, then determine whether the target user has a first binding relationship; if the third binding relationship exists, then use the third binding relationship to determine the workstation to which the target user is bound as the target workstation; if the target user does not have the third binding relationship, then determine the first binding relationship of the target user, use the first binding relationship to determine the role to which the target user is bound, and use the workstation corresponding to the second binding relationship as the target workstation.

[0083] In some embodiments, the workbench can be divided into a first type of workbench, a second type of workbench and a third type of workbench, wherein the loading priority of the first type of workbench is greater than the loading priority of the second type of workbench, and the loading priority of the second type of workbench is greater than the loading priority of the third type of workbench; for example, the third type of workbench is a basic workbench, which can be used in different projects; the second type of workbench is a role workbench, which is set for the role; the first type of workbench is a personal workbench, which is set for the user, and the customized personal workbench is the first type of workbench. In some embodiments, the second type of workbench can also be customized and set for the role, that is, the customized workbench can be the first type of workbench or the second type of workbench, and the specific division is based on whether it is customized for the user or customized for the role.

[0084] Among them, the first type of workbench is the personal workbench: a workbench associated with platform users, focusing on customization based on user operating habits, and has the highest loading priority. The second type of workbench is the role workbench: a workbench associated with a role in the platform's RBAC (Role-Based Access Control) model, focusing on professional experience, and can guide the corresponding identity roles to perform standardized and quick operations, with a medium loading priority. If a user is associated with multiple role workbenches, he or she can also switch role workbenches by himself or herself. The third type of workbench is the basic workbench: equivalent to the original unified work homepage, focusing on the full catalog of capabilities, users can enter the function menu through the business module entrance of the basic workbench to perform a specific business operation, and has a low loading priority.

[0085] Furthermore, the following operations may also be included: When there are multiple workstations bound to the target role, the target workstation corresponding to the target user is determined using the loading priority and the second binding relationship.

[0086] The target role refers to the role to which the user to be logged in by the login request is bound.

[0087] Specifically, each character can have one or more bound workbenches. Therefore, when logging in, the second binding relationship can be used to determine which bound workbenches there are, and then the loading priority of the workbenches can be used to determine the workbench with the highest priority as the target workbench. In some embodiments, the user can also select one of the workbenches as the target workbench, and when the user logs in again subsequently, the workbench selected by the user will be loaded by default.

[0088] Or when there is only one workbench corresponding to the character binding, this workbench is directly used as the target workbench for loading, wherein the workbench at this time is used as the second type of workbench.

[0089] The loading priority represents the current business focus of the user. For example, when there are multiple businesses, the current business focus of the user may be one of the businesses, and the corresponding business has the highest loading priority.

[0090] In some embodiments, the focus of the workbench may also be included. The first type of workbench focuses on the user's personal operating habits, the second type of workbench focuses on professional experience, and the third type of workbench focuses on full catalog coverage.

[0091] In some embodiments, the first type of workstation and the second type of workstation can be converted. For example, after user-defined arrangement, the second type of workstation can be converted to the first type of workstation corresponding to the user, and the first type of workstation can also be restored to the second type of workstation.

[0092] In some embodiments, a fourth type of workbench may also be included, which is a specialized workbench built into the product release, or a workbench customized by customers with industry experience in the project according to their own business characteristics. It can serve as a specialized workbench resource pool built into the product release, or a new workbench created by industry experts of project customers, without loading priority.

[0093] In some embodiments, a workbench may be created for a target user and directly bound, and in this case the workbench is a first type of workbench.

[0094] See also Figure 4 , Figure 4 It is a flow chart of an embodiment of workbench loading in this application.

[0095] like Figure 4 As shown, after logging into the platform and passing the authentication, you will enter the workbench page, and the workbench engine will obtain the user's workbench. Get the user's workbench and determine whether the user has a configured workbench. If the user has a configured workbench, open the configured workbench directly; if there is no configured workbench, determine whether the user's role has a bound workbench. If so, determine whether the number of workbenches bound to the role is greater than 1. If it is greater than 1, a pop-up window will be displayed to remind the role to make a selection, and then load the selected workbench. If it is not greater than 1, directly load the corresponding workbench; if there is no bound workbench, load the basic workbench. After loading, complete the instantiation of the business widget.

[0096] In some embodiments, the target workbench may also be adjusted, including the following operations.

[0097] First, the operation information of the target workstation on the business widget during the working process is obtained, wherein the operation information at least includes the number of clicks, the stay time, and the click sequence information.

[0098] Specifically, when the user works through the target workbench, the number of clicks, the stay time, and the click sequence information of each business widget during the work process are obtained as the click information.

[0099] Next, the value score and relevance of each business widget are determined using the click count information, the dwell time information, and the click sequence information.

[0100] The value score refers to the evaluation of the business widget under the click information in the current target workbench, and the correlation refers to the operational correlation between the business widgets.

[0101] Specifically, by using the number of clicks, dwell time and click sequence information in the acquired operation information, the value score corresponding to each business widget in the target workbench can be determined, and then the value score ranking of the business widgets in the target workbench can be obtained, as well as the correlation between the business widgets.

[0102] Then, different areas of the target workbench are divided according to the value scores to obtain different value score areas.

[0103] Specifically, different areas of the target workbench are divided into value scores according to different regional focus points, and then different value score areas of the target workbench are determined.

[0104] Furthermore, the business widgets of the target workstation are regionally adjusted using the value score, relevance, and different value score regions, and are loaded on the adjusted target workstation.

[0105] Specifically, the business widgets existing in the target workbench are adjusted by utilizing the value score ranking of the business widgets, the correlation of the business widgets, and the different value score areas of the target workbench, so that the adjusted target workbench is more suitable for the user, that is, easier to operate, and in response to the user's confirmation of the adjusted target workbench, the optimization message is pushed to the user. After the user confirms, the adjusted target workbench is loaded to obtain the final target workbench, that is, the web page interface that the user can finally operate.

[0106] The adjustment principle is as follows: the click events, stay time and other information of the business widgets in the workbench used by project users will be reported to the high-frequency analysis management service of the project platform; the high-frequency analysis management service will first clean the data, then count the total number of times the business widgets in each workbench are used, the total stay time, etc., and analyze the order of operations to calculate the relevance of the business widgets; the workbench engine regularly pulls the user's usage statistics and related analysis data from the high-frequency analysis management service, and automatically adjusts the layout of the workbench. The overall principle is: according to the weight coefficients of different times and durations, the value scores of all business widgets are calculated. The value score of the top of the layout is higher than that of the bottom, and the value score of the left of the layout is higher than that of the right; the ones with high relevance will be closer. For important business widgets that mainly display data, such as notifications, fixed values ​​are set; after the workbench is optimized, it is pushed to the user, and after the user confirms, the update of the workbench takes effect.

[0107] In this embodiment, each user in the target project is bound to at least one role, and each role is configured to be bound to at least one workbench, thereby realizing a many-to-many relationship between users and workbenches, meeting the differentiated requirements of massive business scenarios for web interfaces, effectively achieving rapid project delivery, reducing development costs, and improving work efficiency.

[0108] In some embodiments, a web page interface loading system is also provided.

[0109] See also Figure 5 , Figure 5 It is a structural diagram of an embodiment of a web page interface loading system in the present application.

[0110] like Figure 5 As shown, the web page interface loading system 400 includes a configuration module 410 and a determination module 420; wherein the configuration module 410 is used to obtain at least one user included in the target project, and configure the binding relationship between each user and the corresponding at least one role, and then configure the binding relationship between each role and the corresponding at least one workbench in the workbench warehouse; wherein the several workbenches stored in the workbench warehouse are obtained by pre-arranging multiple business widgets according to preset business requirements, and each workbench is configured to be bound to some roles; the determination module 420 responds to the login request of the target user in the target project, determines the target workbench of the target user by using the binding relationship, and then completes the loading of the web page interface by using the target workbench.

[0111] In some embodiments, an electronic device is also provided.

[0112] See also Figure 6 , Figure 61 is a schematic diagram of the structure of an electronic device in an embodiment of the present application. The electronic device can execute the step of loading the web page interface in the above method.

[0113] The electronic device 500 includes a memory 520, a processor 510 coupled to the memory, and at least one computer program stored in the memory 520 and executable on the processor 510; when the processor 510 loads and executes the at least one computer program, it is used to implement the step of loading the web page interface in the above method. For related contents, please refer to the detailed description in the above method, which will not be repeated here.

[0114] In some embodiments, a computer-readable storage medium is also included.

[0115] See also Figure 7 , Figure 7 It is a structural diagram of an embodiment of a computer-readable storage medium in the present application.

[0116] The computer readable storage medium 600 stores at least one program 610, which is used to implement the step of loading the web page interface in the above method when loaded and executed by the processor. For related contents, please refer to the detailed description of the above method, which will not be repeated here.

[0117] In the above scheme, each user in the target project is bound to at least one workbench through an associated role, or the user is directly bound to a workbench, thereby realizing a many-to-many relationship between users and workbenches, meeting the differentiated requirements of massive business scenarios for web interfaces, effectively achieving rapid project delivery, reducing development costs, and improving work efficiency.

[0118] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0119] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0120] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0121] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0122] The above description is only an implementation mode of the present invention, and does not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A web page interface loading method, characterized in that: include: Acquire at least one user included in the target project, and configure a binding relationship between each user and at least one corresponding role, and then configure a binding relationship between each role and at least one corresponding workbench in the workbench warehouse; wherein the workbenches stored in the workbench warehouse are obtained by pre-arranging multiple business widgets according to preset business requirements, and each of the workbenches is configured to be bound to some of the roles; the roles are used to represent the identity or function of a group of related permissions; In response to a login request of a target user in a target project, the target workstation of the target user is determined using the binding relationship, and then the target workstation is used to complete the loading of the web page interface.

2. The method according to claim 1, characterized in that The obtaining of at least one user included in the target project, configuring a binding relationship between each user and at least one corresponding role, and further configuring a binding relationship between each role and at least one corresponding workbench in the workbench warehouse, includes: Obtain at least one user included in the target project; Configuring a first binding relationship between each of the users and at least one corresponding role; Using the role, selecting at least one workbench that can be bound from the workbench warehouse, and then configuring a second binding relationship between each of the roles and at least one workbench; The first binding relationship and the second binding relationship are used to determine the binding relationship between each of the users and at least one workstation through each of the roles, and the binding relationship is set as a first type of binding relationship.

3. The method according to claim 1, characterized in that: Also includes: By using preset business requirements, a plurality of corresponding business widgets are selected from the business widget library in advance for arrangement, and a workbench matching the preset business requirements is generated, thereby obtaining a plurality of workbenches stored in the workbench warehouse, wherein the arranged workbench includes at least: basic workbench information, workbench layout information, and business widget list information.

4. The method according to claim 1, characterized in that The binding relationship is determined by a first binding relationship and a second binding relationship, and the binding relationship is a first type binding relationship, wherein the first binding relationship represents the binding between the user and the role, and the second binding relationship represents the binding between the role and at least one workbench in the workbench warehouse; The step of responding to a login request of a target user in a target project and determining a target workstation of the target user by using the binding relationship comprises: In response to the login request, determining a target user in the target project corresponding to the login request; Determining a target role corresponding to the target user by using the first binding relationship; The target workstation corresponding to the target role is determined by using the second binding relationship, and then the target workstation corresponding to the target role is used as the target workstation of the target user.

5. The method according to claim 4, characterized in that Before determining the target role corresponding to the target user by using the first binding relationship, the method further includes: In response to the existence of a third binding relationship for the user, at least one workbench is selected from the workbench warehouse as a target workbench for the user using the third binding relationship, and is set as a second type of binding relationship, wherein the third binding relationship represents a binding between the user and at least one workbench in the workbench warehouse; In response to the login request, the target workstation is used to complete loading of the web page interface.

6. The method according to claim 5, characterized in that Also includes: The workstations include a first type of workstation and a second type of workstation, the priority of the first type of workstation is greater than the priority of the second type of workstation; The determining the target role corresponding to the target user by using the first binding relationship includes: In response to the target user not having the second type of binding relationship, determining the target role corresponding to the target user by using the first binding relationship; The determining the target workstation corresponding to the target role by using the second binding relationship includes: In response to the target role corresponding to a plurality of workstations being bound, determining the target workstation corresponding to the target role by using the loading priority and the second binding relationship, wherein the loading priority represents the current business focus of the target user; Or in response to the target role corresponding to only one workbench being bound, the target role is associated with the workbench, and the associated workbench is loaded as the target workbench, wherein the workbench bound to the target role is a second-type workbench, and the target workbench of the user determined by the second-type binding relationship is a first-type workbench.

7. The method according to claim 6, characterized in that Also includes, The workbench is customized for the target user or target role and directly bound, and the workbench customized for the target user is the first type of workbench.

8. The method according to claim 6, characterized in that Also includes: The workbench further comprises a third type of workbench, the third type of workbench is a basic workbench, wherein the priority of the second type of workbench is greater than the priority of the third type of workbench; The user can also use the business module entrance of the third type of workstation to enter the function menu and perform specific business operations.

9. The method according to claim 4, characterized in that Also includes: Acquire the operation information of the target workstation on the business widget during the work process, wherein the operation information at least includes click count information, stay time information, and click sequence information; Determine the value score and relevance of each business widget by using the click count information, the dwell time information and the click sequence information; Dividing different areas of the target workbench according to value scores to obtain different value score areas; The business widget of the target workstation is regionally adjusted by using the value score, the degree of association and the different value score regions, and in response to the user's confirmation of the adjusted target workstation, the adjusted target workstation is loaded.

10. An electronic device, characterized in that: The electronic device includes a memory and a processor coupled to the memory, the memory stores at least one computer program, and when the at least one computer program is loaded and executed by the processor, it is used to implement the web page interface loading method according to any one of claims 1-9.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium has at least one program, and when the at least one program is loaded and executed by the processor, it is used to implement the web page interface loading method according to any one of claims 1 to 9.

Images