Page acquisition method, related equipment and medium

Abstract

The embodiments of the present application disclose a page acquisition method, related equipment and medium, which can be applied to the field of cloud technology. The method includes: obtaining the work page configuration information corresponding to the characteristic information of the logged-in user, thereby determining the target work page corresponding to the logged-in user according to the work page configuration information, the target work page includes at least one navigation option of the web workbench, and returning the target work page corresponding to the work page configuration information to the client. Since at least one web workbench is introduced in the work page, the user's needs for the workbench can be met and the user experience can be improved. The embodiments of the present application can be applied to industry applications in the field of cloud technology, and can be specifically applied to government office applications, such as obtaining a government workbench page through this application. The embodiments of the present application can also be applied to the field of blockchain, such as storing the work page configuration information corresponding to each logged-in user in the embodiments of the present application in the node of the blockchain.

Description

Technical Field

[0001] The present application relates to the field of cloud technology, and in particular to a page acquisition method, related equipment and media. Background Art

[0002] With the rapid development of Internet technology, various Internet products for office use (such as office software, financial systems, etc.) have gradually developed. Among them, Internet products for office use usually have a native workbench, such as a government workbench of a government office application, so that each user in the group can perform work tasks through some applications in the native workbench.

[0003] However, the inventors have found in practice that the page display method of the current native workbench is relatively fixed and cannot meet the needs of different users, and the functions of the native applications in the native workbench are too limited. Summary of the invention

[0004] The embodiments of the present application provide a page acquisition method, related devices and media, which are helpful to expand the functions in the workbench to meet the needs of different users for the workbench.

[0005] On the one hand, an embodiment of the present application provides a page acquisition method, the method comprising:

[0006] Receiving a first acquisition instruction for a work page sent by a client, wherein the first acquisition instruction carries characteristic information of a logged-in user in the client;

[0007] Acquire work page configuration information corresponding to the characteristic information of the logged-in user, wherein the work page configuration information is used to indicate a target work page displayed corresponding to the logged-in user, wherein the target work page includes at least one navigation option of a web workbench;

[0008] The target work page corresponding to the work page configuration information is returned to the client.

[0009] On the other hand, an embodiment of the present application provides another page acquisition method, the method comprising:

[0010] Sending a first acquisition instruction for a work page to a server, wherein the first acquisition instruction carries characteristic information of a logged-in user, and the server is used to acquire a target work page corresponding to the characteristic information of the logged-in user;

[0011] Receive and display a target work page corresponding to the feature information returned by the server, wherein the target work page includes at least one navigation option of a web workbench.

[0012] In another aspect, an embodiment of the present application provides a page acquisition device, the device comprising:

[0013] A receiving module, configured to receive a first acquisition instruction for a work page sent by a client, wherein the first acquisition instruction carries characteristic information of a user logged in to the client;

[0014] A processing module, used for obtaining work page configuration information corresponding to the characteristic information of the logged-in user, wherein the work page configuration information is used for indicating a target work page displayed corresponding to the logged-in user, wherein the target work page includes at least one navigation option of a web workbench;

[0015] The sending module is used to return the target working page corresponding to the working page configuration information to the client.

[0016] In another aspect, an embodiment of the present application provides a page acquisition device, the device comprising:

[0017] A sending module, used for sending a first acquisition instruction for a work page to a server, wherein the first acquisition instruction carries characteristic information of a logged-in user, and the first acquisition instruction is used for requesting a target work page corresponding to the characteristic information of the logged-in user;

[0018] A receiving module, used for receiving a target work page corresponding to the feature information returned by the server;

[0019] The display module is used to display the target work page, and the target work page includes at least one navigation option of a web workbench.

[0020] In another aspect, an embodiment of the present application provides a server, the server comprising a processor and a memory, the processor and the memory being connected to each other, wherein the memory is used to store computer program instructions, and the processor is configured to perform the following steps:

[0021] Receiving a first acquisition instruction for a work page sent by a client, wherein the first acquisition instruction carries characteristic information of a logged-in user in the client;

[0022] Acquire work page configuration information corresponding to the characteristic information of the logged-in user, wherein the work page configuration information is used to indicate a target work page displayed corresponding to the logged-in user, wherein the target work page includes at least one navigation option of a web workbench;

[0023] The target work page corresponding to the work page configuration information is returned to the client.

[0024] In another aspect, an embodiment of the present application provides a client, the client comprising a processor and a memory, the processor and the memory are connected to each other, wherein the memory is used to store computer program instructions, and the processor is configured to perform the following steps:

[0025] Sending a first acquisition instruction for a work page to a server, wherein the first acquisition instruction carries characteristic information of a logged-in user, and the first acquisition instruction is used to request a target work page corresponding to the characteristic information of the logged-in user;

[0026] Receive and display a target work page corresponding to the feature information returned by the server, wherein the target work page includes at least one navigation option of a web workbench.

[0027] On the other hand, an embodiment of the present application provides a computer-readable storage medium, in which computer program instructions are stored. When the computer program instructions are executed by a processor, they are used to execute any one of the methods.

[0028] The embodiment of the present application receives a first acquisition instruction for a work page sent by a client, acquires work page configuration information corresponding to the characteristic information of a logged-in user, and thereby determines a target work page corresponding to the logged-in user according to the work page configuration information, wherein the target work page includes at least one navigation option of a web workbench, and returns the target work page corresponding to the work page configuration information to the client. Since at least one web workbench is introduced into the work page, it helps to expand the functions in the workbench, meet the user's needs for the workbench, and improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0030] Figure 1 It is a structural diagram of a page acquisition system provided in an embodiment of the present application;

[0031] Figure 2 It is a flow chart of a page acquisition method provided in an embodiment of the present application;

[0032] Figure 3 This is a schematic diagram of the effect of a work page provided in an embodiment of the present application;

[0033] Figure 4 This is a schematic diagram of the effect of a web page workbench provided in an embodiment of the present application;

[0034] Figure 5 This is a schematic diagram of the effect of obtaining a web page workbench provided in an embodiment of the present application;

[0035] Figure 6 This is a flowchart of a permission judgment provided by an embodiment of the present application;

[0036] Figure 7 It is a flowchart of a web application permission configuration provided by an embodiment of the present application;

[0037] Figure 8 It is a flowchart of another page acquisition method provided in an embodiment of the present application;

[0038] Fig. 9 This is a schematic diagram of the effect of a page in a target work provided by an embodiment of the present application;

[0039] Fig.10 This is a schematic diagram of the effect of a conference assistant interface provided by an embodiment of the present application;

[0040] Fig.11 This is a schematic diagram of the effect of a native workbench provided in an embodiment of the present application;

[0041] Fig.12 This is a schematic diagram of the effect of a native workbench configuration interface provided by an embodiment of the present application;

[0042] Fig.13 This is a schematic diagram of the effect of a native workbench page template provided in an embodiment of the present application;

[0043] Fig.14 This is a schematic diagram of the effect of a native workbench page provided in an embodiment of the present application;

[0044] Fig.15 It is a structural schematic diagram of a page acquisition device provided in an embodiment of the present application;

[0045] Fig.16 It is a structural schematic diagram of a page acquisition device provided in an embodiment of the present application;

[0046] Fig.17 It is a structural diagram of a server provided in an embodiment of the present application;

[0047] Fig.18 It is a structural diagram of a client provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0049] The embodiment of the present application proposes a page acquisition scheme, which can provide customized workbenches for different users through customized workbenches, thereby showing the effect of "thousands of faces for thousands of people". For example, it can be achieved by displaying customized data on the native workbench; as another example, it can be achieved by customizing the web workbench; as another example, it can be achieved by the coexistence of the native workbench and the web workbench. Optionally, the present application can determine the target work page corresponding to the logged-in user based on the characteristic information of different logged-in users, and the target work page may include information of at least one web workbench and a native workbench, and the native workbench page can customize data. Thereby, the corresponding web workbench can be obtained according to the characteristic information of the logged-in user, thereby meeting the user's needs for the workbench and improving the user experience.

[0050] In this application, a workbench can refer to a platform for performing office operations in an Internet product used for office work (such as office software, financial system, etc.), such as performing an approval process through an approval application in the workbench. The native workbench, web workbench such as HTML5 workbench, etc. in this application are all a type of workbench.

[0051] In a possible implementation, the present application solution can be applied to a page acquisition system, see Figure 1 , Figure 1 Schematic diagram of a page acquisition system provided by an embodiment of the present application. Figure 1 As shown, the page acquisition system may include a client and a server. The client may send an acquisition instruction for a work page to the server (assuming it is recorded as a first acquisition instruction), and the server may receive the first acquisition instruction for the work page sent by the client, and then obtain the work page configuration information corresponding to the characteristic information of the logged-in user, and return the target work page corresponding to the work page configuration information to the client, and the client may receive and display the target work page corresponding to the characteristic information returned by the server. The specific implementation process can be found in the following Figure 2 , Figure 8 The description in the corresponding embodiment is not repeated here. Optionally, the client can be a terminal, and the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc., but is not limited to this. The server can also be called a server or other names. Optionally, the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The client and the server can be directly or indirectly connected via wired or wireless communication, and this application is not limited here.

[0052] The technical solution of the present application can be applied to the field of blockchain, which is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, which is a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. For example, the work page configuration information, web application permission information and other information corresponding to each logged-in user in the embodiment of the present application can be stored in the node of the blockchain, so as to obtain the corresponding information according to the instructions sent by the client.

[0053] It is understood that the above scenarios are only examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of the present application. The technical solutions of the present application can also be applied to other scenarios. For example, it is known to those skilled in the art that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0054] Based on the above description, the present application embodiment proposes a page acquisition method. Figure 2 , Figure 2 1 is a flow chart of a page acquisition method provided in an embodiment of the present application. The method can be applied to the above server and executed by the above server. The method can include steps S201-S203.

[0055] S201: Receive a first acquisition instruction for a working page sent by a client.

[0056] Among them, the first acquisition instruction can be an instruction for instructing to obtain a work page, and the work page can be a page of an Internet product for office use (such as office software, financial system, etc.) in the client. In the following description, the Internet product for office use can be referred to as a target office application. For example, the target office application can be WeChat for Enterprise, WeChat for Government Affairs, and so on. The work page may include a navigation bar, and the navigation bar may include multiple navigation options. In some scenarios, the navigation bar may also be referred to as a tab bar, an option bar, a menu bar, etc., and the navigation options may also be referred to as tabs, options to be selected, and menu options. For example, see Figure 3 , Figure 3 It is a schematic diagram of the effect of a work page provided in an embodiment of the present application. In the work page, the navigation bar can refer to 301, and the navigation bar includes 4 navigation options (refer to 302).

[0057] Optionally, the first acquisition instruction may carry characteristic information of the logged-in user in the client, or the server may obtain the characteristic information of the logged-in user through other means. The logged-in user may be a user who logs in to the client by using an account password or scanning a code to log in, such as a user who logs in to the above-mentioned target office application. Optionally, the characteristic information of the logged-in user may include information such as the user's responsibilities, the organization to which the user belongs, the user's position, the user's tags, the user's preferences, etc., which are not limited here. Optionally, the logged-in user may belong to one or more groups, and the group may also be a group with multiple personnel such as a company, enterprise, unit, class, school, etc. Each person in the group may correspond to a user account, and each user account may be called a logged-in user after logging in to the client.

[0058] S202: Obtain work page configuration information corresponding to the characteristic information of the logged-in user.

[0059] The work page configuration information may be used to indicate the target work page displayed to the logged-in user, and the target work page may include at least one navigation option of a web workbench. Optionally, the work page configuration information may also include the number of navigation options of the web workbench in the target work page, the work page configuration information may also include the number and option names of navigation options in the navigation bar, the work page configuration information may also include the location information of the navigation options in the navigation bar, and so on, which are not limited here. The target work page may be the work page displayed to the logged-in user. For example, if the work page configuration information corresponding to the characteristic information of the logged-in user indicates that the target work page has 1 navigation option of a web workbench, then the target work page displayed to the logged-in user has 1 navigation option of a web workbench.

[0060] The web workbench can be a workbench composed of web pages, that is, an office operation platform that realizes the user's work needs in the form of web pages. For example, the web workbench can be an HTML5 workbench. HTML5 is a language description method for building Web content. The HTML5 workbench is a platform for building web pages through the HTML5 description language to perform office operations. For another example, the web workbench can also be a mini-program workbench. A mini-program is an application that can be used without downloading and installing. The mini-program work platform is a platform for jumping to the mini-program page to perform office operations. There is no limitation here. It can be understood that the page of the web workbench can define the display style, user interface (User Interface, UI for short), product logic, etc. of the web workbench according to user needs, so that the web workbench can better meet user needs. For example, please refer to Figure 4 , Figure 4This is a schematic diagram of the effect of a web workbench provided in an embodiment of the present application. The web workbench may include some web applications, as shown in 401 in the figure; the web workbench may also include a user information display area, which may display part of the user information of the logged-in user, as shown in 402 in the figure; the web workbench may also include a top bar, as shown in 403 in the figure.

[0061] In a possible implementation, the work page configuration information may be configuration information for the work page configured by an administrator (developer) in the target group. For example, the work page configuration instructions for each user account sent by the management client may be received, and the work page configuration information corresponding to each user account may be extracted according to the work page configuration instructions. Each user account is a user account in the target group, and the work page configuration instructions are used to indicate instructions for configuring the work page for each user account. For example, the number and option names of the navigation options in the navigation bar corresponding to each user account are configured, the location information of the navigation options in each navigation bar is configured, and so on, which are not limited here.

[0062] Optionally, the user accounts under the target collective can also be divided into multiple user groups, and the work page configuration instructions for each user group sent by the management client are received, and the work page configuration information corresponding to each user group is extracted according to the work page configuration instructions. Among them, the user accounts under the target collective can be divided into multiple user groups according to the responsibilities of each user account, the organization to which the user account belongs, the position corresponding to the user account, the label corresponding to the user account, the preferences corresponding to the user account, and other information. The work page configuration instructions for each user group are used to indicate the instructions for configuring each user group in the management client, so that the same work page information can be configured for the user accounts in each user group to reduce the workload of the management client. Optionally, the same work page configuration information can be configured for all user accounts in the target collective.

[0063] S203: Return the target work page corresponding to the work page configuration information to the client.

[0064] Among them, the target work page corresponding to the work page configuration information returned to the client can be the page data of the target work page returned to the client, such as the option name of the navigation option in the page navigation bar of the target work page, the location information of the navigation option in the navigation bar, the image information of the target work page and other data, so that when the client receives the page data of the target work page, the client displays the target work page.

[0065] It is understandable that in a group, the work configuration information corresponding to each person can be the same or different, and the target work page corresponding to the logged-in user can be determined by obtaining the web workstation configuration information corresponding to the characteristic information of the logged-in user. In some scenarios, one or more web workstations can also be fixedly configured for each user in a group, so that after receiving the first acquisition instruction for the work page sent by the client, the work page corresponding to the information of the fixedly configured web workstation can be directly fed back to the client.

[0066] In a possible implementation, at least one web workstation in the target work page may include a target web workstation. It can be understood that the target web workstation can be any one of the at least one web workstation. The server may further perform the following steps: receiving a second acquisition instruction for the target web workstation sent by the client, and obtaining the identity information of the logged-in user in the second acquisition instruction; when the identity information of the logged-in user is verified, obtaining the web workstation configuration information corresponding to the characteristic information of the logged-in user; and returning the target web workstation page corresponding to the web workstation configuration information to the client.

[0067] Among them, the second acquisition instruction can be an instruction for instructing to obtain the target web page workbench. The identity information of the logged-in user is the unique identifier of the logged-in user in a group, and the identity information can also be called UserID or other names. The web page workbench configuration information can be used to indicate the information for the web page workbench page corresponding to the characteristic information of the logged-in user. The web page workbench configuration information can include the information of the web application in the web page workbench, such as the name of the web application configured in the web page workbench, the display mode of the configured web application, the icon of the web application, etc. The web page workbench configuration information can also include the user interface (User Interface, referred to as UI) of the web page workbench. For example, the web page workbench can include an area for displaying the information of the logged-in user (such as the name of the logged-in user), and the color information of the interface of the logged-in user (such as the background color, the color of the target area, etc., which are not limited here). The target web page workbench page is used to indicate the page displayed corresponding to the navigation option of the target web page workbench in the target work page after it is selected. It can be understood that in a group, the web page workbench configuration information corresponding to each person can be the same or different, so it is necessary to obtain the web page workbench configuration information corresponding to the characteristic information of the logged-in user, so as to determine the target web page workbench page corresponding to the logged-in user.

[0068] Optionally, the identity information of the logged-in user in the second acquisition instruction can be obtained through the Open Authorization 2.0 (OAuth2.0) verification interface, so that the login process can be avoided in the process of obtaining the target web page workstation through the client. Optionally, the second acquisition instruction indicates that the uniform resource locator (URL) of the acquired target web page workstation should be consistent with a preset trusted domain name, and the trusted domain name is used to indicate the secure and trusted domain name set corresponding to the target collective to which the logged-in user belongs. If the callback link address (redirect_uri) of the post-authorization redirection in the second acquisition instruction has a port number, the port number should also be set when setting the trusted domain name. If the trusted domain name is inconsistent with the redirect_uri, after receiving the second acquisition instruction, a prompt message is sent to the client that sent the second acquisition instruction to prompt that the domain name verification failed (redirect_uri parameter error).

[0069] Optionally, verifying the identity information of the logged-in user may include receiving the legitimacy of the uniform resource identifier, device ID (Device ID) and other information of the target web page workstation from the client, and may also include verifying whether the identity information of the logged-in user belongs to the target group, and may also include verifying whether the logged-in user has the authority to obtain the target web page workstation, etc. Optionally, after receiving the second acquisition instruction, an authorization code CODE may be generated according to the URL of the target web page workstation in the second acquisition instruction, and returned to the client, so that the target web page workstation background can obtain the identity information (UserID) of the logged-in user according to the CODE, and the server returns the data returned by the target web page workstation background to the client. The target web page work background is a module or program that can manage, set, and modify data. The web page work background can be applied to the above-mentioned server or to a server different from the above-mentioned server, and there is no limitation here. For example, please refer to Figure 5 , Figure 5This is a schematic diagram of the effect of obtaining a web workstation provided by an embodiment of the present application. The acquisition process may include a client, a target office application background, an API interface, a target web workstation background, etc. The user initiates an acquisition instruction for the target web workstation through the client (i.e., step S501), and then the target office application background can verify the legitimacy of the URI, Deviceid and other information in the second acquisition instruction (i.e., step S502). When the verification is passed, the target office application background verifies the URI and generates an authorization code (CODE) (i.e., step S503), and then returns a redirection address to the client (i.e., step S504), for example, https:REDIRE CT_URI&code=CODE, the client jumps to the jump address (i.e., step S505) through a 302 jump method, thereby initiating an access request to the target web page workstation background, and the target web page workstation background requests verification of the CODE through an API interface (i.e., step S506). When the verification is successful, the identity information (userid) and device ID (deviceid) of the logged-in user are returned to the target web page workstation background (i.e., step S507), so that the target web page workstation background finally returns the data of the target web page workstation page to the client (i.e., step S508).

[0070] In a possible implementation, the acquisition of the login user's identity information through (OAuth2.0) will have a certain time overhead, so the login user's identity information can also be acquired through the following steps: detecting that the preset uniform resource identifier (URL) for the target web page work page is the page address corresponding to the target group; when receiving the second acquisition instruction for the target web page workbench page, verifying whether there is data (cookie) stored on the client that identifies the login user's identity information; if there is no matching cookie, redirecting to the OAuth2.0 verification link, after acquiring the login user's identity information, according to the cookie information that identifies the login user's identity information stored in the server, after acquiring the login user's identity information according to the cookie, the login user's identity information is verified, and when the verification is passed, the target web page workbench page corresponding to the login user is returned to the client. In this way, in the scenario where the login user's identity information is frequently acquired, the time consumption can be reduced.

[0071] In a possible implementation, the target web page workstation may include at least one web application. Before returning the target web page workstation page corresponding to the web page workstation configuration information to the client, the web application permission information for the logged-in user may also be obtained. The web application permission information is used to indicate the permissions that the logged-in user has for each web application. Returning the target web page workstation page corresponding to the web page workstation configuration information to the client may include: returning the target web page workstation page corresponding to the web application permission information and the web page workstation configuration information to the client.

[0072] Among them, the web application is used to indicate the application used to provide office functions to users in the web workbench, such as the web application can be linked to the web workbench through an API interface. Optionally, the web application can be a customized application of the group to which the logged-in user belongs. The web application permission information is used to indicate the permissions that the logged-in user has for each web application. The permissions may include access permissions, operation permissions, data permissions, etc. The access permissions are used to indicate whether the logged-in user can access the web application; the operation permissions are used to indicate which operations the logged-in user can perform in the web application, such as in the approval application, the logged-in user can submit an approval application, but cannot approve other people's applications; the data permissions are used to indicate which data the logged-in user can obtain in the web application, such as the logged-in user can obtain customer contact information data, but cannot obtain the account information of all people in the group. Then, the target webpage workbench page corresponding to the webpage application permission information and the webpage workbench configuration information is returned to the client. When the corresponding target webpage workbench page is determined according to the above webpage workbench configuration information, the display permission of each webpage application in the target webpage workbench can also be determined according to the webpage user permission information. If it is detected that the logged-in user does not have the access permission for the target webpage application (the target webpage application can be any webpage application in the target webpage workbench), the target webpage application can be hidden from the target webpage workbench so that it is not displayed. The icon or logo of the target webpage application can also be displayed in the target webpage workbench, but the logged-in user cannot access it, such as displaying the icon or logo of the target webpage application in gray or dark color, or using text to indicate that it is not accessible at the icon or logo of the target webpage application. The information of the target webpage workbench page is obtained based on the webpage workbench configuration information of the logged-in user, and the display method of each webpage application in the target webpage workbench is determined according to the webpage application permission information of the logged-in user, so as to determine the target webpage workbench, and return the target webpage workbench page to the client.

[0073] In a possible implementation, when receiving the third acquisition instruction for the target web application sent by the client, the web application permission information of the logged-in user for the target web application is obtained, and the corresponding target web application page is returned to the client according to the web application permission information for the target web application. The third acquisition instruction for the target web application may be an operation performed after entering the target web application. For example, the target web application is an application for querying information of user accounts in the target group (user information query). If the third acquisition instruction indicates to obtain information of all user accounts in the target group, the server may determine whether the logged-in user carried in the third acquisition instruction has the authority to obtain information of all user accounts in the target group according to the web application permission information of the user. If yes, the information of all user accounts is returned to the client. If no, a prompt message is returned to prompt the logged-in user that the logged-in user has no authority. If the logged-in user only has the authority to query information of some user accounts, the information of the some user accounts is returned to the client accordingly, and the logged-in user is prompted that the logged-in user only has the authority to query information of some user accounts.

[0074] Optionally, the authority of the logged-in user can be determined through the authority determination interface, such as the / rights / check interface. The authority determination process can refer to Figure 6 , Figure 6 is a flowchart of a permission judgment provided by an embodiment of the present application. Figure 6As shown, in the permission judgment process, the web application calls the permission judgment interface to perform permission check through the 3A access control system (ACS), where 3A refers to account, authority, and authentication. For example, the interface is called: ^ / rights / check, and the basic information for permission judgment in the third acquisition instruction is obtained (i.e., step S601), i.e., the user code (accountid), the specific object (resource) for which authorization is to be obtained, the action (action), and other information; then the 3A access control system screens the hit principle (Policy) according to the basic information for permission judgment (accountid, resource, action) (i.e., step S602), and thus obtains the permission judgment result according to the hit Policy (i.e., step S603). For example, if the hit Policy contains multiple conditions (conditions), the relationship between the conditions is an AND relationship, and the effect of deny takes precedence over allow (allow), then when one of the conditions is deny, the permission judgment result is no permission (fasle); for another example, if the hit Policy does not contain any conditions, if the effect of the Policy is all allow (allow), the result is permission (true); if the Policy contains the effect of deny, the result is no permission (fasle), and the permission judgment result is finally determined to be permission (true) or no permission (fasle). After obtaining the permission judgment result, the permission judgment result is returned to the server (i.e., step S604). Among them, the basic elements of the principle (Policy) are the basic combination layer part of the permission judgment process. For example, as shown in Table 1 below, the basic elements may include one or more of the following.

[0075] Table 1:

[0076] Element Name describe Effect There are two types of authorization effectiveness: Allow and Deny. Action Behavior refers to the operation on specific resources. Resource Resources refer to the specific objects that are authorized. Condition Restrictions are the conditions under which the authorization takes effect.

[0077] Optionally, the user accounts under the target group can be divided into multiple user groups, and the web application permission configuration instructions for each user group sent by the management client are received, and the web application permissions corresponding to each user group are extracted according to the web application permission configuration instructions. The user accounts under the target group can be divided into multiple user groups according to the responsibilities of each user account, the organization to which the user account belongs, the position corresponding to the user account, the label corresponding to the user account, the preferences corresponding to the user account, and other information. The web application permission information may include access permissions, operation permissions, or data permissions. For example, see Figure 7 , Figure 7This is a flow chart of a web application permission configuration provided in an embodiment of the present application. User accounts can be divided into multiple user groups based on the organization, position, label and other information of the user accounts. That is to say, user accounts belong to user groups, so that the same or different permissions can be assigned to each user group, so that the user group has permissions and permission management in the target group is realized.

[0078] In a possible implementation, the web workbench can also be regarded as an application in the target office application. In this case, when building the web workbench, developers (managers) are required to have application development capabilities, for example, HTML5 page development technology, the ability to customize web page display style, UI and product logic, etc.; for example, the ability to use OAuth2.0 web authorization to obtain the information of the logged-in user; for example, the ability to use the front-end page JSSDK provided by the target office application; for example, the ability to use the "Open Application" option in JSSDK to reuse the application management system in the target office application; for example, the ability to use the HTML page in <title> The label is used as the display name of the workbench page, and so on, and there is no restriction here. Thus, developers can design a web workbench that meets the needs of users according to the user needs of the target group and improve the user experience.< / title>

[0079] In a possible implementation, when a user logs in to a user account in a target office application, it can be determined whether the logged-in user has the visible permission for the web workbench. If the logged-in user has the visible permission for the web workbench, the target work interface with the web client is returned to the client. Optionally, in order to improve the efficiency of obtaining the web workbench on the client, when the user logs in to the target office application, the user account with the visible permission for the web workbench can be obtained, and the web workbench configuration information corresponding to the user account can be written into the cache area. When a second acquisition instruction for the target web workbench is sent by the client of the logged-in user with the web workbench permission, the cache area is read. If the web workbench configuration information corresponding to the user account exists in the cache area, the target web workbench page is directly returned. If the web workbench configuration information corresponding to the user account does not exist in the cache area, the loading interface is returned, so that the server consumes time to obtain the target web workbench page and returns the target web workbench page to the client.

[0080] The embodiment of the present application receives a first acquisition instruction for a work page sent by a client, acquires work page configuration information corresponding to the characteristic information of a logged-in user, and thereby determines a target work page corresponding to the logged-in user according to the work page configuration information, wherein the target work page includes at least one navigation option of a web workbench, and returns the target work page corresponding to the work page configuration information to the client. Since at least one web workbench is introduced into the work page, the user's needs for the workbench can be met, thereby improving the user experience.

[0081] See also Figure 8 , Figure 8 1 is a flow chart of another page acquisition method provided by an embodiment of the present application. The method can be applied to the above-mentioned client and executed by the above-mentioned terminal. The method can include steps S801-S802.

[0082] S801. Send a first acquisition instruction for a working page to a server.

[0083] The first acquisition instruction carries the characteristic information of the logged-in user. For a specific description, reference can be made to the relevant description of the first acquisition instruction in the above step S201, which will not be repeated here. The server may be the server for executing steps S201-S203, and the server may be used to obtain the target work page corresponding to the characteristic information of the logged-in user.

[0084] In a possible implementation, the timing of sending the first acquisition instruction to the server may be that after the user logs in to the target office application by using an account password or scanning a code, the target work page needs to be acquired from the server. Then, after detecting that the user has successfully logged in to the target office application, the client sends the first acquisition instruction for the work page to the server. The timing of sending the first acquisition instruction to the server may also be that after the user logs in to the target office application, if the user does not operate in the acquired target work page for more than a preset time, the target work page needs to be refreshed. Then, the client detects that there is no operation instruction for the target work page after the preset time has passed, and then sends the first acquisition instruction to the server. The timing of sending the first acquisition instruction to the server may also be that after the user logs in to the target office application, if the user reopens the target office application in the client, the first acquisition instruction is sent to the server.

[0085] S802: Receive and display the target work page corresponding to the feature information returned by the server.

[0086] The target work page includes at least one navigation option of a web work station. The target work page is the work page corresponding to the characteristic information of the logged-in user. The description of the characteristic information and the target work station can be found in Figure 2 The relevant description in will not be repeated here.

[0087] In a possible implementation, after receiving the page data of the target work page returned by the server, the client can render according to the page data of the target work page and display it in the client. Fig. 9 , Fig. 9 : is a schematic diagram of the effect of a target work page provided by an embodiment of the present application. In the target work page, a navigation bar may be included. The navigation bar includes multiple navigation options. The multiple navigation options include at least one navigation option of a web workbench, such as Fig. 9In the figure, 901 is a navigation option of a web workbench.

[0088] In a possible implementation, the navigation options of the at least one web workstation may include the navigation options of the target web workstation. It is understandable that the target web workstation may be any one of the at least one web workstation. Then, after step S802, the following steps may also be performed: when a selection operation for the navigation options of the target web workstation in the target work page is detected, a second acquisition instruction for the target web workstation is sent to the server; and the target web workstation page returned by the server is received and displayed. Among them, the selection operation for the navigation options of the target web workstation may be a user clicking on the navigation options of the target web workstation in the navigation bar, or may be a voice instruction to obtain the target web workstation page, which is not limited here. The target web workstation page is determined by the web application permission information and web workstation configuration information corresponding to the logged-in user, and the target web workstation includes at least one web application. The method for obtaining the target web workstation page may refer to the above step S203, which is not described here.

[0089] In a possible implementation, the target webpage workbench may be an HTML5 workbench, and the HTML5 workbench page may be adjusted according to the page operation instruction of the logged-in user, which may specifically include the following steps: receiving the page operation instruction of the user for the HTML5 workbench; adjusting the HTML5 workbench page according to the page setting operation indicated by the page operation instruction; wherein the page setting operation indicated by the page operation instruction includes one or more of the following: configuring the position of the navigation option of the HTML5 workbench, configuring the color of the target position in the HTML5 workbench, and configuring the option name of the navigation option of the HTML5 workbench. The page operation instruction may be a page operation instruction for the HTML5 workbench initiated by the logged-in user in the setting interface for the HTML5 workbench page, and the page operation instruction may indicate the page setting operation for the HTML5 workbench. The position of the navigation option of the HTML5 workbench is used to indicate the position of the navigation option of the HTML5 workbench in the navigation bar. The position of the navigation option in the navigation bar may be used to indicate the relative position relationship between multiple navigation options (such as left-right relationship, up-down relationship), and may also be used to indicate the interval distance between multiple navigation options, which is not limited here. For example, the four navigation options in the navigation bar are called navigation option 1, navigation option 2, navigation option 3, and navigation option 4 from left to right. If the position of the navigation option of the HTML5 workbench is navigation option 4 when the target work page is obtained, when the page operation instruction for the HTML5 workbench is received to indicate that the position of the navigation option of the HTML5 workbench is adjusted to navigation option 3, the client configures the position of the navigation option of the HTML5 workbench to navigation option 3 according to the page operation instruction, and the position of the navigation option of the HTML5 workbench is changed from navigation option 4 to the position of navigation option 3. Configuring the color of the target position in the HTML5 workbench is used to indicate the adjustment of the color of the target position in the HTML5 workbench. The target position can be any position in the HTML5 workbench, such as the top bar of the HTML5 workbench (i.e., the top position in the HTML workbench page), the user information display area, etc. The color can be a color in the WEB standard color, CMYK color, or RGB color, which is not limited here. If the color configured by the page operation instruction is not a color in the above standard color, it is displayed as a default color. For example, if the top bar of the HTML5 workbench is red when the target work page is obtained, when receiving a page operation instruction for the HTML5 workbench indicating that the top bar of the HTML5 workbench is adjusted to yellow, the client configures the top bar of the HTML5 workbench to be yellow according to the page operation instruction, and the color of the top bar of the HTML5 workbench changes from red to yellow. The option name for configuring the navigation option of the HTML5 workbench is used to indicate the name of the navigation option for adjusting the HTML5 workbench.For example, if when the target work page is obtained, the option name of the navigation option of the HTML5 workbench is "Workbench", then when a page operation instruction for the HTML5 workbench is received instructing to adjust the option name of the HTML5 workbench to "Common Workbench", the client configures the option name of the navigation option of the HTML5 workbench to "Common Workbench" according to the page operation instruction, then the option name of the navigation option of the HTML5 workbench changes from "Workbench" to "Common Workbench".

[0090] Optionally, the client can also detect an operation instruction for the target work page, which is used to instruct the configuration of the initial navigation option of the target work page, or to determine the initial access location of the target work page, that is, when the client accesses the target office application, the navigation option focused on the target work page and the page corresponding to the navigation option. The initial navigation option can be any navigation option in the navigation bar.

[0091] Optionally, the page setting operation for the page operation execution instructions for the target work page and HTML5 workbench can also be set by the management user terminal, that is, the page setting operation can be set by the administrator in the target group through the management client. For example, the administrator can customize whether to turn on the web workbench (the default is on or off) through the management client. If you want to turn on a web workbench, you can choose to add an application in the "Navigation Bar Application Management" in the management page, and the application is the above-mentioned target web workbench; the administrator can configure the initial navigation option of the target work page through the management client, which defaults to navigation option 1 and can be changed to other locations (such as navigation option 2, navigation option 3, etc.); the administrator can configure the location of the navigation option of the target web workbench through the management client, which defaults to navigation option 4 and can be changed to other locations; the administrator can configure the color of the target location in the web workbench through the management client. If the color is not adjusted, it will be displayed as the default color, which can be any color.

[0092] Optionally, the configuration information for the HTML5 workbench can be saved to the working page configuration information and the web workbench configuration information corresponding to the characteristic information of the logged-in user, so that when the target work page and the target web workbench page are obtained next time, the target work page and the target web workbench page corresponding to the page setting operation configuration indicated by the above-mentioned surface operation instruction can be obtained.

[0093] In a possible implementation, the web application in the web workbench can replace the message notification, address book and other interfaces of the target office application to achieve deep integration of the web application with the target office application. Taking the conference assistant as an example, in the web workbench, the user can click on the conference assistant to enter the corresponding interface of the conference assistant, and then obtain the meeting information in the conference assistant interface. Please refer to Fig.10 , Fig.10 It is a schematic diagram of the effect of a conference assistant interface provided in an embodiment of the present application.

[0094] In a possible implementation, the target work page returned from the server may also include a navigation option of a native workbench, and the native workbench includes multiple native applications. Then, after executing step S802, the following steps may also be performed: when a selection operation for the navigation option of the native workbench in the target work page is detected, multiple native applications in the native workbench are displayed in a target form; wherein the target form may include any one or more of the following: key data type, image type, list type, and web page view type. The native workbench may be a workbench originally existing in the target office application, wherein the multiple native applications included therein are some basic office applications, and when obtaining the native web workbench page, no web page jump is required. The selection operation for the navigation option of the native web workbench may be for the user to click on the navigation option of the native web workbench in the navigation bar, or may be for obtaining the native web workbench page through a voice command, which is not limited here. When the selection operation for the navigation option of the native workbench is detected, the native workbench page may be displayed, and the multiple native applications in the native workbench page may be displayed in a target form, such as key data type, image type, list type, and web page view type, see Fig.11 , Fig.11 This is a schematic diagram of the effect of a native workbench provided by an embodiment of the present application. The key data type can be in the form of key data in the native application that displays the native workbench page, and is suitable for native applications that need to disclose key data in a timely manner, such as Fig.11 As shown in (1), the native workbench page can display the data of Example 1 as 2, such as the number of people currently waiting for approval (pending approval) is 2, the data of Example 2 as 4, such as the number of homeworks currently waiting for review (pending review homework) is 4, the data of Example 3 as 45, such as the number of people who have entered grades (grade entry) is 45, and the data of Example 4 as 98, such as the comprehensive evaluation of the logged-in user (comprehensive evaluation) is 98. The image type can be an image in the native application that displays the native workbench page, which is suitable for native applications for notification or promotional display, such as Fig.11As shown in (2), for example, the native application may be an information push application, and the image of the information pushed in the information push application or the accompanying image of the article is displayed first, so that the logged-in user can quickly obtain the latest information pushed by the application from the image. The list type can be a list display of data in the native application of the native workbench page, such as Fig.11 As shown in (3), the information or data in the multiple native applications (such as Example 1, Example 2, and Example 3) are displayed in a list format, which is suitable for native applications with multiple parallel contents. The web page view type can be a web page view to display the data of the native application in the native workbench, which is suitable for displaying native applications with complex content; Fig.11 As shown in (4), for example, the native application may be an information push application, and the title of the information in the information push application is displayed first, so that the logged-in user can quickly obtain the latest message pushed by the application from the title.

[0095] In a possible implementation, the target form displayed on the native workbench page can be set through the management client. For example, the administrator can configure the target form displayed on the native workbench through the native workbench configuration interface in the management client. Fig.12 , Fig.12 It is a schematic diagram of the effect of a native workbench configuration interface provided in an embodiment of the present application. In this interface, the target form of the current native workbench can be included, options for the target form can be included, examples of display according to different target forms, and so on.

[0096] Optionally, the management client can also set one or more page templates for the native workbench page in response to the administrator's template setting operation for the native workbench. For example, the administrator can set the page template of the native workbench page in the target office application through the template interface provided by the target office application, and the template interface can be: an interface for setting the display template of the native application in the native workbench (interface 1), an interface for obtaining the display template of the native application in the native workbench (interface 2), and an interface for setting the display template of the data of the native application in the native workbench (interface 3). The display template of the native application in the native workbench can be set through interface 1, such as setting the native application in the native workbench to display according to the above target form, and the default template of a target group can also be set through the interface 1, so that when a page template is not set for a user account (such as when a new person is added to the target group), the native workbench page corresponding to the user account is displayed as the native workbench page corresponding to the default template. The display template of the native application in the native workbench can also be obtained through the interface 2. The display template of the data of the native application in the native workbench can also be determined through the interface 3. Optionally, when calling the above template interface through the management client, you can make a request through POST or GET. In this way, you can configure the display page of the native workbench according to user needs, so that the native workbench can better meet user needs. See Fig.13 , Fig.13 It is a schematic diagram of the effect of a native workbench page template provided in an embodiment of the present application.

[0097] Optionally, the native work applications in the native workbench can also display native applications in the form of icons. When displaying native applications in the form of icons, they can be displayed in the form of a nine-square grid, a sixteen-square grid, or a list, etc., and there is no limitation here. The applications in the native workbench can also be displayed in accordance with multiple groups, such as displaying commonly used native applications under the commonly used group, displaying native applications for management under the management application, and so on. Optionally, the native workbench can also have a banner advertising page (banner page) for advertising display, or to improve the aesthetics of the workbench, or to display important notifications of the target group, etc. Please refer to Fig.14 , Fig.14 It is a schematic diagram of the effect of a native workbench page provided in an embodiment of the present application.

[0098] In a possible implementation, after detecting a selection instruction for a target web page workstation, a second acquisition instruction is sent to the server. If the server fails to return the target web page workstation page, the native workstation is displayed. Optionally, the server fails to return the target web page workstation page may be that the server does not return the target web page workstation page within a preset time. The server fails to return the target web page workstation page may also be that after the client sends the first second acquisition instruction, the target web page workstation page is not returned within a preset time, and the second acquisition instruction is sent again. The second acquisition instruction sent again does not require the user to perform a selection operation. When the client detects that the target web page workstation page is not returned within the preset time, the second acquisition instruction is sent to the server again. By analogy, if the second acquisition instruction sent is greater than a preset number and the target web page workstation page is still not obtained, the native workstation is displayed.

[0099] It can be understood from the above description that the navigation bar of the target work page may include the following situations: only including at least one web workbench, including at least one web workbench and a native workbench, or only including a native workbench. The display of the specific web workbench page or the native workbench page can refer to the above description and will not be repeated here.

[0100] The embodiment of the present application sends a first acquisition instruction for a work page to the server, the first acquisition instruction carries the characteristic information of the logged-in user, receives and displays a target work page corresponding to the characteristic information returned by the server, and the target work page includes at least one navigation option of a web workbench. Since at least one web workbench is introduced into the work page, the user's needs for the workbench can be met, thereby improving the user experience.

[0101] See also Fig.15 , Fig.15 is a schematic diagram of the structure of a page acquisition device provided in an embodiment of the present application. Optionally, the page acquisition device may be set in a server. Fig.15 As shown, the page acquisition device described in this embodiment may include:

[0102] The receiving module 1501 is used to receive a first acquisition instruction for a work page sent by a client, where the first acquisition instruction carries characteristic information of a user logged in in the client;

[0103] Processing module 1502, used to obtain work page configuration information corresponding to the characteristic information of the logged-in user, the work page configuration information is used to indicate the target work page displayed corresponding to the logged-in user, and the target work page includes at least one navigation option of a web workbench;

[0104] The sending module 1503 is used to return the target work page corresponding to the work page configuration information to the client.

[0105] In one implementation, the at least one webpage workstation includes a target webpage workstation, and the receiving module 1501 is further configured to receive a second acquisition instruction sent by the client for the target webpage workstation, and acquire the identity information of the login user in the second acquisition instruction;

[0106] The processing module 1502 is further configured to obtain webpage workstation configuration information corresponding to the feature information of the logged-in user when the identity information of the logged-in user is verified;

[0107] The sending module 1503 is further configured to return a target web workstation page corresponding to the web workstation configuration information to the client.

[0108] In one implementation, the target webpage workstation includes at least one webpage application, and the processing module 1502 is further used to: obtain webpage application permission information for the logged-in user; the webpage application permission information is used to indicate the permission that the logged-in user has for each webpage application;

[0109] The sending module 1503 returns the target webpage workstation page corresponding to the webpage workstation configuration information to the client, and is specifically used for:

[0110] A target webpage workbench page corresponding to the webpage application permission information and the webpage workbench configuration information is returned to the client.

[0111] See also Fig.16 , Fig.16 is a schematic diagram of the structure of another page acquisition device provided in an embodiment of the present application. Optionally, the page acquisition device may be a client. Fig.16 As shown, the page acquisition device described in this embodiment includes:

[0112] A sending module 1601 is used to send a first acquisition instruction for a work page to a server, wherein the first acquisition instruction carries characteristic information of a logged-in user, and the first acquisition instruction is used to request a target work page corresponding to the characteristic information of the logged-in user;

[0113] A receiving module 1602 is used to receive a target work page corresponding to the feature information returned by the server;

[0114] The display module 1603 is used to display the target work page, which includes at least one navigation option of a web workbench.

[0115] In one implementation, the at least one webpage workstation includes a target webpage workstation, and the sending module 1601 is further configured to send a second acquisition instruction for the target webpage workstation to the server when a selection operation for a navigation option for the target webpage workstation in the target work page is detected;

[0116] The receiving module 1602 is further configured to receive a target webpage workstation page returned by the server, wherein the target webpage workstation page is determined by the webpage application permission information corresponding to the logged-in user and the webpage workstation configuration information, and the target webpage workstation includes at least one webpage application;

[0117] The display module 1603 is further used to display the target web page workstation page returned by the server, wherein the target web page workstation page is determined by the web application permission information corresponding to the logged-in user and the web page workstation configuration information, and the target web page workstation includes at least one web application.

[0118] In one implementation, the target work page further includes a navigation option of a native workbench, the native workbench includes a plurality of native applications, and the display module 1603 is further configured to display the plurality of native applications in the native workbench in a target form when a selection operation for the navigation option of the native workbench is detected in the target work page;

[0119] The target form may include any one or more of the following: key data type, picture type, list type, and web page view type.

[0120] In one implementation, the target webpage workbench is an HTML5 workbench, and the receiving module 1602 is further used to:

[0121] Receiving a page operation instruction from the logged-in user for the HTML5 workbench; adjusting the HTML5 workbench page according to the page setting operation indicated by the page operation instruction;

[0122] The page setting operation indicated by the page operation instruction includes one or more of the following: configuring the position of the navigation option of the HTML5 workbench, configuring the color of the target position in the HTML5 workbench, and configuring the option name of the navigation option of the HTML5 workbench.

[0123] It is understood that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The functional units in the embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware or in the form of software functional units.

[0124] See also Fig.17 , Fig.17 1701 is a schematic diagram of a server structure provided in an embodiment of the present application. The client described in this embodiment includes: a processor 1701, a memory 1702, and a network interface 1703. The processor 1701, the memory 1702, and the network interface 1703 can exchange data.

[0125] The processor 1701 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.

[0126] The memory 1702 may include a read-only memory and a random access memory, and provide program instructions and data to the processor 1701. A portion of the memory 1702 may also include a non-volatile random access memory. When the processor 1701 calls the program instructions, it is used to execute:

[0127] Receiving a first acquisition instruction for a work page sent by a client, wherein the first acquisition instruction carries characteristic information of a logged-in user in the client;

[0128] Acquire work page configuration information corresponding to the characteristic information of the logged-in user, wherein the work page configuration information is used to indicate a target work page displayed corresponding to the logged-in user, wherein the target work page includes at least one navigation option of a web workbench;

[0129] The target work page corresponding to the work page configuration information is returned to the client.

[0130] In one implementation, the at least one webpage workstation includes a target webpage workstation, and the processor 1701 is further configured to:

[0131] receiving a second acquisition instruction for the target webpage workstation sent by the client, and acquiring the identity information of the login user in the second acquisition instruction;

[0132] When the identity information of the logged-in user is verified, obtaining webpage workstation configuration information corresponding to the feature information of the logged-in user;

[0133] Returning a target web page workbench page corresponding to the web page workbench configuration information to the client.

[0134] In one implementation, the target webpage workstation includes at least one webpage application, and the processor 1701 is further configured to:

[0135] Acquire web application permission information for the logged-in user; the web application permission information is used to indicate the permission that the logged-in user has for each web application;

[0136] The returning a target webpage workstation page corresponding to the webpage workstation configuration information to the client includes:

[0137] A target webpage workbench page corresponding to the webpage application permission information and the webpage workbench configuration information is returned to the client.

[0138] See also Fig.18 , Fig.18 1801, a memory 1802, and a network interface 1803. The processor 1801, the memory 1802, and the network interface 1803 can exchange data.

[0139] The processor 1801 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 the processor may be any conventional processor, etc.

[0140] The memory 1802 may include a read-only memory and a random access memory, and provide program instructions and data to the processor 1801. A portion of the memory 1802 may also include a non-volatile random access memory. When the processor 1801 calls the program instructions, it is used to execute:

[0141] Sending a first acquisition instruction for a work page to a server, wherein the first acquisition instruction carries characteristic information of a logged-in user, and the first acquisition instruction is used to request a target work page corresponding to the characteristic information of the logged-in user;

[0142] Receive and display a target work page corresponding to the feature information returned by the server, wherein the target work page includes at least one navigation option of a web workbench.

[0143] In one implementation, the at least one webpage workstation includes a target webpage workstation, and the processor 1801 may further be configured to:

[0144] When a selection operation of a navigation option for the target web page workstation is detected in the target work page, a second acquisition instruction for the target web page workstation is sent to the server;

[0145] A target webpage workstation page returned by the server is received and displayed, wherein the target webpage workstation page is determined by the webpage application permission information corresponding to the logged-in user and the webpage workstation configuration information, and the target webpage workstation includes at least one webpage application.

[0146] In one implementation, the target work page further includes a navigation option of a native workbench, the native workbench includes a plurality of native applications, and the processor 1801 may further be used to:

[0147] When a selection operation for a navigation option of the native workbench in the target work page is detected, displaying the plurality of native applications in the native workbench in a target form;

[0148] The target form may include any one or more of the following: key data type, picture type, list type, and web page view type.

[0149] In one implementation, the target webpage workbench is an HTML5 workbench, and the processor 1801 may also be used to:

[0150] Receiving a page operation instruction from the logged-in user for the HTML5 workbench; adjusting the HTML5 workbench page according to the page setting operation indicated by the page operation instruction;

[0151] The page setting operation indicated by the page operation instruction includes one or more of the following: configuring the position of the navigation option of the HTML5 workbench, configuring the color of the target position in the HTML5 workbench, and configuring the option name of the navigation option of the HTML5 workbench.

[0152] The embodiment of the present application further provides a computer storage medium, in which program instructions are stored. When the program is executed, some or all steps of the page acquisition method in the above method embodiment can be implemented, which will not be repeated here.

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

[0154] A person skilled in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0155] The embodiment of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. The processor of the server reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the server executes the steps performed in the embodiments of the above methods.

[0156] The above is a detailed introduction to a traffic scheduling method, device, equipment and storage medium provided in the embodiments of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A page acquisition method, characterized in that: include: Receiving a first acquisition instruction for a work page sent by a client, the first acquisition instruction carrying characteristic information of a logged-in user of a target office application in the client, the work page being a work page of the target office application, and the work page including a navigation bar having at least one navigation option; Acquire work page configuration information corresponding to the characteristic information of the logged-in user, wherein the work page configuration information is used to indicate a target work page displayed corresponding to the logged-in user, wherein a navigation bar of the target work page includes at least one navigation option of a web workbench, and the web workbench is a workbench composed of web pages; Returning the target work page corresponding to the work page configuration information to the client; Receiving a second acquisition instruction for a target webpage workstation sent by a client, and acquiring the identity information of the login user in the second acquisition instruction, wherein the target webpage workstation is any one of the at least one webpage workstation; When the identity information of the logged-in user is verified, obtaining webpage workstation configuration information corresponding to the feature information of the logged-in user; Returning a target web page workbench page corresponding to the web page workbench configuration information to the client.

2. The method according to claim 1, characterized in that: The target webpage workbench includes at least one webpage application, and the method further includes: Acquire web application permission information for the logged-in user; the web application permission information is used to indicate the permission that the logged-in user has for each web application; The returning a target webpage workstation page corresponding to the webpage workstation configuration information to the client includes: A target webpage workbench page corresponding to the webpage application permission information and the webpage workbench configuration information is returned to the client.

3. A page acquisition method, characterized in that: include: Sending a first acquisition instruction for a work page to a server, the first acquisition instruction carrying characteristic information of a login user of a target office application, the work page being a work page of the target office application, the work page including a navigation bar having at least one navigation option, and the first acquisition instruction being used to request a target work page corresponding to the characteristic information of the login user; Receiving and displaying a target work page corresponding to the characteristic information returned by the server, wherein the navigation bar of the target work page includes at least one navigation option of a webpage workbench, wherein the webpage workbench is a workbench composed of web pages; When a selection operation of a navigation option for a target web page workstation in the target work page is detected, a second acquisition instruction for the target web page workstation is sent to the server, the target web page workstation being any one of the at least one web page workstation; Receive and display a target web workstation page corresponding to the web workstation configuration information returned by the server based on the second acquisition instruction, wherein the web workstation configuration information corresponds to the feature information of the logged-in user.

4. The method according to claim 3, characterized in that: The target webpage workstation page is determined by the webpage application permission information corresponding to the logged-in user and the webpage workstation configuration information, and the target webpage workstation includes at least one webpage application.

5. The method according to claim 3, characterized in that: The target work page also includes a navigation option of a native workbench, the native workbench includes a plurality of native applications, and the method further includes: When a selection operation for a navigation option of the native workbench in the target work page is detected, displaying the plurality of native applications in the native workbench in a target form; The target form may include any one or more of the following: key data type, picture type, list type, and web page view type.

6. The method according to claim 4, characterized in that: The target webpage workbench is an HTML5 workbench, and the method further includes: Receiving a page operation instruction from the logged-in user for the HTML5 workbench; adjusting the HTML5 workbench page according to the page setting operation indicated by the page operation instruction; The page setting operation indicated by the page operation instruction includes one or more of the following: configuring the position of the navigation option of the HTML5 workbench, configuring the color of the target position in the HTML5 workbench, and configuring the option name of the navigation option of the HTML5 workbench.

7. A page acquisition device, characterized in that: include: A receiving module, configured to receive a first acquisition instruction for a work page sent by a client, wherein the first acquisition instruction carries characteristic information of a logged-in user of a target office application in the client, the work page is a work page of the target office application, and the work page includes a navigation bar having at least one navigation option; a processing module, configured to obtain work page configuration information corresponding to the characteristic information of the logged-in user, wherein the work page configuration information is used to indicate a target work page displayed corresponding to the logged-in user, wherein a navigation bar of the target work page includes at least one navigation option of a web workbench, and the web workbench is a workbench composed of web pages; A sending module, used for returning the target working page corresponding to the working page configuration information to the client; The receiving module is further configured to receive a second acquisition instruction for a target webpage workstation sent by a client, and acquire the identity information of the login user in the second acquisition instruction, wherein the target webpage workstation is any one of the at least one webpage workstation; The processing module is further configured to obtain webpage workstation configuration information corresponding to the feature information of the logged-in user when the identity information of the logged-in user is verified; The sending module is further used to return a target web page workstation page corresponding to the web page workstation configuration information to the client.

8. A page acquisition device, characterized in that: include: a sending module, configured to send a first acquisition instruction for a work page to a server, wherein the first acquisition instruction carries characteristic information of a login user of a target office application, the work page is a work page of the target office application, the work page includes a navigation bar having at least one navigation option, and the first acquisition instruction is used to request a target work page corresponding to the characteristic information of the login user; A receiving module, used for receiving a target work page corresponding to the feature information returned by the server; A display module, used for displaying the target work page, wherein the navigation bar of the target work page includes at least one navigation option of a webpage workbench, wherein the webpage workbench is a workbench composed of web pages; The sending module is further configured to send a second acquisition instruction for the target web page workstation to the server when a selection operation for a navigation option for a target web page workstation in the target work page is detected, wherein the target web page workstation is any one of the at least one web page workstation; The receiving module is further used to receive and display a target web workstation page corresponding to the web workstation configuration information returned by the server based on the second acquisition instruction, wherein the web workstation configuration information corresponds to the feature information of the logged-in user.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, they are used to execute the method according to any one of claims 1 to 6.

Images