Subsystem display method and related equipment
By uniformly displaying the items of the authorization subsystem in the portal system and supporting one-click jump to the approval form, the problem of scattered display of items in the approval system is solved, improving user experience and work efficiency, while also enhancing system security.
Patent Information
- Application Number
- CN202511408346.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-29
- Publication Date
- 2026-02-17
AI Technical Summary
In the approval system, items from different systems are displayed separately, requiring users to manually switch between systems to process each item, which affects work efficiency and user experience.
A method for displaying subsystems is provided. By obtaining all items of the authorized subsystem, the method displays the items to be done, important items to be read, ordinary items to be read, completed items, and read items uniformly on the portal system page. It supports users to approve subsystem forms in the portal system or to jump to the subsystem page to display the approval form through a token, realizing one-click jump.
It improves user efficiency and user experience, reduces user operations, and enhances system security.
Smart Images
Figure CN121544196A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a subsystem display method and related equipment. Background Technology
[0002] In the approval system for related technologies, items from different systems are usually displayed and approved separately. Items to be handled, items to be reviewed, and items that have been completed are also scattered. It is necessary to manually switch between systems, manually process and select specific approval items one by one. The management and processing process is relatively complicated, which affects work efficiency and user experience.
[0003] In summary, the technical problems existing in the relevant technologies need to be improved. Summary of the Invention
[0004] The main objective of this application is to propose a subsystem display method and related devices, which aim to improve user work efficiency and user experience.
[0005] To achieve the above objectives, one aspect of this application provides a subsystem display method, the method comprising: Obtain all items from the authorization subsystem, including items to be done on behalf of others, important documents to be read, ordinary documents to be read, completed items, and read items; In response to the first instruction, the authorized subsystem's to-do items, important document reading items, ordinary document reading items, completed items, and read items are displayed on the portal system page. The to-do items include general items and subsystem-specific items. In response to the second instruction, determine the current matter requiring approval from the list of matters to be handled; If the current matter is a general matter, then in response to the third instruction, the approval form corresponding to the current matter is displayed on the portal system page; If the current matter is a matter specific to the subsystem, then in response to the fourth instruction, the login token of the portal system is obtained, and the corresponding subsystem is navigated to using the login token, and the approval form corresponding to the current matter is displayed on the subsystem page.
[0006] In some embodiments, the method further includes: In response to the fifth directive, the authorization subsystem is displayed on the portal system page.
[0007] In some embodiments, the method further includes: Obtain the number of tasks to be performed by the authorization subsystem; Calculate the total number of tasks in the portal system based on the number of tasks in the authorization subsystem. In response to the sixth instruction, the number of tasks assigned to the authorized subsystem and the total number of tasks assigned to the portal system are displayed on the portal system page.
[0008] In some embodiments, the method further includes: In response to the selection instruction of the current important reading item, the login token of the portal system is obtained, and the corresponding subsystem is jumped through the login token and the important reading content corresponding to the current item is displayed on the subsystem page. The current important reading item is selected from the important reading items. In response to the selection command of the current ordinary reading item, the ordinary content to be read corresponding to the current ordinary reading item is displayed on the portal system page, and the current ordinary reading item is selected from the ordinary reading items.
[0009] In some embodiments, the method further includes: In response to the seventh instruction, the width and height of the current component are defined on the custom page. The current component includes the approval center component, the meeting component, the personal center component, and the internal message component. In response to the eighth instruction, the component properties of the current component are displayed on the custom page, and the component properties are associated with the current component; In response to the ninth instruction, display the current component on the custom page.
[0010] In some embodiments, the method further includes: In response to the tenth instruction, the page component mode is displayed and set on the custom page, the page component mode including single-column mode and multi-column mode; If the page component mode is a multi-column mode, in response to the eleventh instruction, the column width is displayed and set on the custom page, and the width of the corresponding component is adjusted by the column width, wherein the component corresponds to the column.
[0011] To achieve the above objectives, another aspect of this application provides a subsystem display device, the device comprising: The item acquisition module is used to acquire all items from the authorization subsystem. All items include items to be done, important items to be read, ordinary items to be read, completed items, and read items. The item display module is used to respond to the first instruction and display the items to be done, the important items to be read, the ordinary items to be read, the completed items and the read items of the authorized subsystem on the portal system page. The items to be done include general items and subsystem-specific items. The item determination module is used to determine the current item that needs approval from the items to be handled in response to the second instruction; The current display module is used to, in response to a third instruction, display the approval form corresponding to the current item on the portal system page if the current item is the general item; The jump display module is used to, in response to the fourth instruction, obtain the login token of the portal system if the current item is a subsystem-specific item, jump to the corresponding subsystem through the login token, and display the approval form corresponding to the current item on the subsystem page.
[0012] To achieve the above objectives, another aspect of this application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the method described above.
[0013] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods described above.
[0014] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer program product, including a computer program that, when executed by a processor, implements the aforementioned method.
[0015] The embodiments of this application include at least the following beneficial effects: This application provides a subsystem display method, device, electronic device, storage medium, and program product. This solution obtains all items of the authorized subsystem, including items to be done, important reading items, ordinary reading items, completed items, and read items; in response to a first instruction, it displays the items to be done, important reading items, ordinary reading items, completed items, and read items of the authorized subsystem on the portal system page. Items to be done include general items and subsystem-specific items, which is beneficial for users to intuitively view all items of the authorized subsystem, facilitates user management of items, and improves user experience. The system performs several steps: First, upon receiving the first instruction, it determines the current task requiring approval from the list of tasks. If the current task is a general task, it responds to the third instruction by displaying the corresponding approval form on the portal system page, allowing users to approve subsystem forms within the portal system, reducing user operations and improving user experience. Second, if the current task is a subsystem-specific task, it responds to the fourth instruction by obtaining the portal system's login token, using the token to navigate to the corresponding subsystem and displaying the approval form for the current task on the subsystem page. This enables one-click navigation, improving user efficiency and user experience, while also enhancing system security through token authentication. Attached Figure Description
[0016] Figure 1 This is a flowchart of the subsystem display method provided in the embodiments of this application; Figure 2 A flowchart of the steps for displaying the number of display items in the subsystem display method provided in this application embodiment; Figure 3 A flowchart of the document display steps of the subsystem display method provided in this application embodiment; Figure 4 A flowchart of the custom component steps of the subsystem display method provided in this application embodiment; Figure 5 This is a flowchart illustrating a specific implementation of the subsystem display method provided in this application when applied to a portal system; Figure 6 This is a schematic diagram of the portal system page subsystem provided in an embodiment of this application; Figure 7 This is a schematic diagram of the portal system page for tasks provided in this application embodiment; Figure 8 This is a schematic diagram of the portal system jumper system provided in the embodiments of this application; Figure 9 This is a schematic diagram of the portal system custom settings provided in the embodiments of this application; Figure 10 This is a schematic diagram of a custom page provided in an embodiment of this application; Figure 11 This is another custom page illustration provided in the embodiments of this application; Figure 12 This is a schematic diagram of the portal system email and meeting controls provided in an embodiment of this application; Figure 13 This is a schematic diagram of the portal system email message and notification controls provided in the embodiments of this application; Figure 14 This is a schematic diagram of the subsystem display device provided in the embodiments of this application; Figure 15 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0017] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.
[0018] It is understood that the terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words “if,” “when,” or “in response to a determination” as used herein may be interpreted as “when…” or “when…” or “in response to a determination.”
[0019] As used in this application, the terms "at least one", "multiple", "each", "any", etc., "at least one" includes one, two or more, "multiple" includes two or more, "each" refers to each of the corresponding multiples, and "any" refers to any one of the multiples.
[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.
[0021] Before providing a detailed description of the embodiments of this application, some of the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.
[0022] 1) A token is a mechanism used for authentication, authorization, and security control. Tokens ensure that communication between users or systems is legitimate and prevent unauthorized access. Tokens can be used to verify user identity, manage sessions, or transmit authorization information.
[0023] In the approval system for related technologies, items from different systems are usually displayed and approved separately. Items to be handled, items to be reviewed, and items that have been completed are also scattered. It is necessary to manually switch between systems, manually process and select specific approval items one by one. The management and processing process is relatively complicated, which affects work efficiency and user experience.
[0024] In summary, the technical problems existing in the relevant technologies need to be improved.
[0025] In view of this, this application provides a subsystem display method and related equipment. This solution obtains all items from the authorized subsystem, including items to be done, important reading items, ordinary reading items, completed items, and read items. In response to a first instruction, it displays these items on the portal system page. Items to be done include general items and subsystem-specific items, allowing users to intuitively view all items from the authorized subsystems, facilitating item management and improving user experience. In response to a second instruction, it determines the current item requiring approval from the items to be done. If the current item is a general item, in response to a third instruction, it displays the corresponding approval form on the portal system page, supporting user approval of subsystem forms within the portal system, reducing user operations and improving user experience. If the current item is a subsystem-specific item, in response to a fourth instruction, it obtains a login token from the portal system, jumps to the corresponding subsystem using the login token, and displays the corresponding approval form on the subsystem page, achieving one-click jump, improving user work efficiency and user experience, while also enhancing system security through token authentication.
[0026] The subsystem display method provided in this application relates to the field of computer technology. The subsystem display method provided in this application can be applied to a terminal, a server, or software running on a terminal or server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, or in-vehicle terminal, but is not limited to these. The server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The server can also be a node server in a blockchain network. The software can be an application implementing the subsystem display method, but is not limited to the above forms.
[0027] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.
[0028] It should be noted that in all specific embodiments of this application, when processing data related to user identity or characteristics, such as user information, user behavior data, user historical data, and user location information, user permission or consent is obtained first. Furthermore, the collection, use, and processing of this data comply with relevant laws, regulations, and standards. In addition, when embodiments of this application require access to sensitive personal information of users, separate permission or consent from the user is obtained through pop-ups or redirection to confirmation pages. Only after obtaining the user's separate permission or consent is the necessary user-related data required for the proper functioning of these embodiments acquired.
[0029] Figure 1 This is an optional flowchart of the subsystem display method provided in the embodiments of this application. Figure 1 The method may include, but is not limited to, steps S101 to S105.
[0030] Step S101: Obtain all matters related to the authorization subsystem.
[0031] Specifically, all items include items to be handled on behalf of others, important items to be read, ordinary items to be read, items that have been completed, and items that have been read.
[0032] Optionally, in response to the fifth instruction, the authorization subsystem is displayed on the portal system page. The fifth instruction is triggered when the portal system navigation page is opened.
[0033] In some embodiments, the portal system calls the API interface of the authorization subsystem to obtain the subsystem's list of tasks. The list of tasks includes tasks to be done, important tasks to be read, ordinary tasks to be read, completed tasks, and read tasks.
[0034] Optionally, when retrieving items, the portal system uses a user login token for authentication.
[0035] In some embodiments, if there are many items in a subsystem, incremental loading can be used to retrieve only the newly updated items instead of retrieving all of them each time.
[0036] In this embodiment, all matters of the authorization subsystem are obtained, enabling users to view all matters on a unified platform without having to manually log in to multiple systems, thus reducing the user's operational burden.
[0037] Step S102: In response to the first instruction, the authorized subsystem's to-do items, important reading items, ordinary reading items, completed items, and read items are displayed on the portal system page.
[0038] Specifically, the tasks to be handled include general tasks and subsystem-specific tasks. The first instruction is triggered when the portal system page is opened and the portal system page includes the approval center component.
[0039] In some embodiments, the approval center component area of the portal system page displays the to-do items, important reading items, ordinary reading items, completed items, and read items of each authorized subsystem.
[0040] It is understandable that the tasks to be completed, important documents to be read, ordinary documents to be read, completed items and read items to be displayed separately for each authorized subsystem.
[0041] Optionally, items to be handled, important items to be read, ordinary items to be read, completed items, and read items can be sorted according to priority, date, category, etc.
[0042] In some embodiments, the number of tasks in the authorized subsystem is obtained; the total number of tasks in the portal system is calculated based on the number of tasks in the authorized subsystem; and in response to the sixth instruction, the number of tasks in each authorized subsystem and the total number of tasks in the portal system are displayed on the portal system page.
[0043] Optionally, the number of tasks can be highlighted, either by color, background, or position.
[0044] In this embodiment, in response to the first instruction, the portal system page displays the to-do items, important reading items, ordinary reading items, completed items, and read items of the authorized subsystems. This allows users to intuitively view all items of the authorized subsystems, facilitates the management of items, and improves the user experience.
[0045] Step S103, in response to the second instruction, determine the current item requiring approval from the to-do list.
[0046] Specifically, the second instruction is the selection instruction for the current item, which is triggered when the current item is clicked, checked, or selected from the drop-down list.
[0047] In some embodiments, items requiring approval are selected from the list of to-do items.
[0048] Optionally, in response to the selection command for the currently important document, a login token for the portal system is obtained. The login token is used to navigate to the corresponding subsystem, and the important content to be read for the current document is displayed on the subsystem page. The currently important document is selected from the list of important documents. In some embodiments, in response to the selection instruction of the current ordinary reading item, the ordinary content to be read corresponding to the current ordinary reading item is displayed on the portal system page. The current ordinary reading item is selected from the ordinary reading items.
[0049] In step S104, if the current item is a general item, then in response to the third instruction, the approval form corresponding to the current item is displayed on the portal system page.
[0050] Specifically, the third instruction is triggered when the current item is selected and the current item is a general item.
[0051] In some embodiments, if the current matter is a general matter, the portal system will dynamically load the corresponding approval form based on the current matter.
[0052] Understandably, after the approval form is displayed, users can fill out the form and submit it.
[0053] In this embodiment, if the current matter is a general matter, in response to the third instruction, the approval form corresponding to the current matter is displayed on the portal system page, which supports users to approve subsystem forms in the portal system, reducing user operations and improving user experience.
[0054] In step S105, if the current matter is a subsystem-specific matter, then in response to the fourth instruction, obtain the login token of the portal system, jump to the corresponding subsystem through the login token, and display the approval form corresponding to the current matter on the subsystem page.
[0055] Specifically, the fourth instruction is triggered when the current item is selected and the current item is a subsystem-specific item. In some embodiments, if the current matter is a subsystem-specific matter, the user's login token is obtained through the portal system.
[0056] Furthermore, the portal system redirects to the corresponding subsystem page via a URL containing the token. After verifying the token, the subsystem displays the approval form for the current item.
[0057] Optionally, if there are many subsystems, SSO technology can be used to eliminate the need for repeated logins after a single login.
[0058] In this embodiment, if the current matter is a subsystem-specific matter, then in response to the fourth instruction, the login token of the portal system is obtained, and the corresponding subsystem is navigated to using the login token. The approval form corresponding to the current matter is then displayed on the subsystem page, achieving one-click navigation, improving the user experience, and enhancing system security through token authentication.
[0059] Steps S101 to S105 as illustrated in this embodiment involve obtaining all items from the authorized subsystem, including items to be done, important reading items, ordinary reading items, completed items, and read items. In response to a first instruction, the authorized subsystem's items to be done, important reading items, ordinary reading items, completed items, and read items are displayed on the portal system page. Items to be done include general items and subsystem-specific items, allowing users to intuitively view all items from the authorized subsystems, facilitating item management and improving user experience. In response to a second instruction, the current item requiring approval is determined from the items to be done. If the current item is a general item, in response to a third instruction, the corresponding approval form is displayed on the portal system page, supporting user approval of subsystem forms within the portal system, reducing user operations and improving user experience. If the current item is a subsystem-specific item, in response to a fourth instruction, a login token for the portal system is obtained. The user is then redirected to the corresponding subsystem using the login token, and the corresponding approval form is displayed on the subsystem page, achieving one-click redirection, improving user work efficiency and user experience, while token authentication enhances system security.
[0060] Please see Figure 2 In some embodiments, the subsystem display method provided in this application further includes a step of displaying the number of items, which may include, but is not limited to, steps S201 to S203: Step S201: Obtain the number of items to be done in the authorized subsystem.
[0061] In step S201 of some embodiments, the number of to-do items for each authorized subsystem is obtained.
[0062] Optionally, the number of tasks can be obtained from the authorization subsystem or calculated.
[0063] Step S202: Calculate the total number of tasks in the portal system based on the number of tasks in the authorized subsystem.
[0064] In step S202 of some embodiments, the number of to-do items for each authorized subsystem is added together to calculate the total number of to-do items for the portal system.
[0065] Step S203, in response to the sixth instruction, displays the number of tasks assigned to the authorized subsystems and the total number of tasks assigned to the portal system on the portal system page.
[0066] Specifically, the sixth instruction is triggered when the portal system page is opened, and the portal system page includes the approval center.
[0067] In step S203 of some embodiments, the number of to-do items for each authorized subsystem and the total number of to-do items for the portal system are displayed on the portal system page.
[0068] Please see Figure 3 In some embodiments, the subsystem display method provided in this application further includes a document display step, which may include, but is not limited to, steps S301 to S302: Step S301: In response to the selection instruction of the current important reading item, obtain the login token of the portal system, jump to the corresponding subsystem through the login token, and display the important reading content corresponding to the current item on the subsystem page.
[0069] Specifically, the currently important document is selected from the list of important documents. The selection command for the currently important document is triggered by clicking, double-clicking, checking the box, or selecting important documents from the drop-down list.
[0070] In step S301 of some embodiments, a login token of the portal system is obtained, and the corresponding subsystem is navigated to using the login token, and important content to be read corresponding to the current matter is displayed on the subsystem page.
[0071] Optionally, important documents include a document code, which allows you to retrieve the important content to be read. Similarly, all documents include a document code, which allows you to retrieve the detailed content of the document.
[0072] Step S302: In response to the selection command of the current ordinary reading item, display the ordinary content to be read corresponding to the current ordinary reading item on the portal system page.
[0073] Specifically, the current ordinary document to be read is selected from the ordinary document to be read. The selection command for the current ordinary document to be read is triggered by clicking, double-clicking, checking the box, or selecting an ordinary document to be read from the drop-down list.
[0074] In step S302 of some embodiments, the ordinary pending content corresponding to the current ordinary reading item is displayed on the portal system page.
[0075] Optionally, the general reading items include an item code, through which the general reading content is obtained.
[0076] Please see Figure 4 In some embodiments, the subsystem display method provided in this application further includes a custom component step, which may include, but is not limited to, steps S401 to S403: Step S401, in response to the seventh instruction, defines the width and height of the current component on the custom page.
[0077] Specifically, the current components include the approval center component, the meeting component, the personal center component, and the internal message component. The seventh instruction is triggered when the width or height of the current component is modified by opening a custom page.
[0078] In step S401 of some embodiments, in response to the tenth instruction, the page component mode is displayed and set on the custom page; if the page component mode is a multi-column mode, in response to the eleventh instruction, the column width is displayed and set on the custom page, and the width of the corresponding component is adjusted by the column width. The page component mode includes single-column mode and multi-column mode, with components corresponding to columns. The tenth instruction is triggered when the custom page is opened and the page component mode is modified, and the eleventh instruction is triggered when the custom page is opened and the column width is modified.
[0079] It should be noted that the number of columns in multi-column mode can be customized by the user, and the default column width in multi-column mode is automatically determined based on the number of columns.
[0080] In the multi-column mode, a corresponding column is determined for each component, and the component width is the same as the column width.
[0081] In step S402, in response to the eighth instruction, the component properties of the current component are displayed on the custom page.
[0082] Specifically, the component properties are associated with the current component, and the eighth instruction is triggered when the component properties are set in the custom page.
[0083] In step S402 of some embodiments, the component properties of the current component are displayed and set on a custom page.
[0084] It should be noted that different components correspond to different component properties.
[0085] Step S403, in response to the ninth instruction, displays the current component on the custom page.
[0086] Specifically, the ninth instruction is triggered when a custom page is opened.
[0087] In step S403 of some embodiments, the current component is displayed on a custom page according to the width and height of the current component and the component attributes.
[0088] Figure 5This is a flowchart illustrating a specific implementation of the subsystem display method provided in this application when applied to a portal system. Figure 5 The methods may include, but are not limited to, the following steps: Step 1: The portal system displays the subsystems that the user has permission to access.
[0089] In some embodiments, a portal system displays subsystems to which the user has permissions.
[0090] For example, a schematic diagram of the portal system page subsystem is shown below. Figure 6 As shown, all subsystems are displayed. Unauthorized subsystems are marked with an "No Permission" sign, while subsystems that are not yet online are marked with an "Under Construction" sign. Subsystems without any such sign are authorized subsystems.
[0091] Step 2: The portal system displays the to-do items of users in the subsystem.
[0092] In some embodiments, the approval center control of the portal system displays the to-do items of users in the subsystem.
[0093] For example, a diagram of the to-do items on the portal system page is shown below. Figure 7 As shown in the image. The number of tasks is highlighted in red with white text, and each task includes the creator and creation time.
[0094] Step 3: Click on the errand to be done. If the errand to be done is a general errand, the approval details will be displayed on the portal system page.
[0095] In some embodiments, general matters display the approval content of the matter on the portal system page.
[0096] Step 4: If the task is a subsystem-specific task, then the user will be redirected to the subsystem using the unified authentication center token obtained when logging into the portal system, and the task approval content will be displayed on the subsystem page.
[0097] In some embodiments, the user is redirected to a login subsystem based on the unified authentication center token obtained when logging into the portal system, and the approval details are displayed on the subsystem page.
[0098] For example, a schematic diagram of a portal system jumper system is shown below. Figure 8 As shown in the diagram. Clicking the item control will navigate to the corresponding subsystem. For example, the item control is as follows: Figure 8 The items highlighted in red correspond to the subsystems shown on the pages indicated by the arrows.
[0099] Step 5: Customize the display controls of the portal system.
[0100] In some embodiments, controls are used in a custom portal system.
[0101] For example, a diagram illustrating the custom settings of a portal system is shown below. Figure 9 As shown in the diagram, the custom page is illustrated below. Figure 10 and Figure 11 As shown. Among them, the controls in the custom page support drag-and-drop sorting up and down, left and right, and multi-column format display. The vertical and horizontal sorting and multi-column format display can be achieved by dragging the controls, and the width and height can be controlled by dragging the edges of the controls.
[0102] It is understandable that if the control changes from 1 column to 2 columns, the width of the control in both columns will be automatically adjusted. Similarly, if the control changes from n columns to n+1 columns, the width will also be automatically adjusted.
[0103] In this embodiment, customizing controls on the page helps improve user experience, meet users' customization needs, and help users intuitively and clearly customize the page.
[0104] Step 6: The portal system displays the user's emails and meetings.
[0105] For example, a diagram illustrating the portal system's email and meeting controls is shown below. Figure 12 As shown in the diagram, the portal system's email messages and notification controls are illustrated below. Figure 13 As shown.
[0106] Please see Figure 14 This application also provides a subsystem display device that can implement the above-described method. The device includes: The item acquisition module 1401 is used to acquire all items in the authorization subsystem. All items include items to be done, important items to be read, ordinary items to be read, completed items, and read items. The item display module 1402 is used to respond to the first instruction and display the authorized subsystem's pending items, important reading items, ordinary reading items, completed items and read items on the portal system page. Pending items include general items and subsystem-specific items. The item determination module 1403 is used to determine the current item that needs approval from the items to be done in response to the second instruction; The current display module 1404 is used to respond to a third instruction and display the approval form corresponding to the current item on the portal system page if the current item is a general item. The jump display module 1405 is used to respond to the fourth instruction if the current item is a subsystem-specific item, obtain the login token of the portal system, jump to the corresponding subsystem through the login token, and display the approval form corresponding to the current item on the subsystem page.
[0107] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The specific functions implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0108] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.
[0109] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0110] Please see Figure 15 , Figure 15 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes: The processor 1501 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. The memory 1502 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1502 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1502 and is called and executed by the processor 1501 using the methods described in the embodiments of this application. The input / output interface 1503 is used to implement information input and output; The communication interface 1504 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 1505 transmits information between various components of the device (e.g., processor 1501, memory 1502, input / output interface 1503, and communication interface 1504); The processor 1501, memory 1502, input / output interface 1503 and communication interface 1504 are connected to each other within the device via bus 1505.
[0111] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.
[0112] It is understood that the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.
[0113] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.
[0114] It is understood that the content of the above method embodiments is applicable to the embodiments of this program product. The specific functions implemented by the embodiments of this program product are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0115] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
[0116] The subsystem display method, apparatus, electronic device, storage medium, and program product provided in this application embodiment obtain all items of the authorized subsystem, including items to be done, important reading items, ordinary reading items, completed items, and read items; in response to a first instruction, display the items to be done, important reading items, ordinary reading items, completed items, and read items of the authorized subsystem on the portal system page. Items to be done include general items and subsystem-specific items, which helps users to intuitively view all items of the authorized subsystem, facilitates user management, and improves user experience; in response to a second instruction, determine the current item that needs approval from the items to be done; if the current item is a general item, in response to a third instruction, display the approval form corresponding to the current item on the portal system page, supporting users to approve subsystem forms in the portal system, reducing user operations and improving user experience; if the current item is a subsystem-specific item, in response to a fourth instruction, obtain the login token of the portal system, jump to the corresponding subsystem through the login token, and display the approval form corresponding to the current item on the subsystem page, realizing one-click jump, improving user work efficiency and user experience, and improving system security through token authentication.
[0117] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
[0118] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.
[0119] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0120] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.
[0121] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0122] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0123] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0124] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0125] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0126] If the integrated unit is implemented as 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 this application, 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. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0127] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.
Claims
1. A method of displaying a subsystem, characterized by, The method comprises the following steps: acquiring all the matters of the authorized subsystem, the all the matters comprising pending matters, important reading matters, ordinary reading matters, completed matters and read matters; in response to a first instruction, displaying the pending matters, the important reading matters, the ordinary reading matters, the completed matters and the read matters of the authorized subsystem on a portal system page, the pending matters comprising general matters and subsystem-specific matters; in response to a second instruction, determining a current matter requiring approval from the pending matters; if the current matter is the general matter, in response to a third instruction, displaying an approval form corresponding to the current matter on the portal system page; if the current matter is the subsystem-specific matter, in response to a fourth instruction, acquiring a login token of the portal system, jumping to the corresponding subsystem through the login token and displaying the approval form corresponding to the current matter on the subsystem page.
2. The method of claim 1, wherein, The method further comprises: in response to a fifth instruction, displaying the authorized subsystem on a portal system page.
3. The method of claim 1, wherein, The method further comprises: acquiring the number of pending matters of the authorized subsystem; calculating the total number of pending matters of the portal system according to the number of pending matters of the authorized subsystem; in response to a sixth instruction, displaying the number of pending matters of the authorized subsystem and the total number of pending matters of the portal system on a portal system page.
4. The method of claim 1, wherein, The method further comprises: in response to a selection instruction of a current important reading matter selected from the important reading matters, acquiring a login token of the portal system, jumping to the corresponding subsystem through the login token and displaying important reading content corresponding to the current matter on the subsystem page; in response to a selection instruction of a current ordinary reading matter selected from the ordinary reading matters, displaying ordinary reading content corresponding to the current ordinary reading matter on the portal system page.
5. The method of claim 1, wherein, The method further comprises: in response to a seventh instruction, defining the width and height of a current component on a custom page, the current component comprising an approval center component, a meeting component, a personal center component and an internal message component; in response to an eighth instruction, displaying component attributes of the current component on the custom page, the component attributes being associated with the current component; in response to a ninth instruction, displaying a current component on a custom page.
6. The method of claim 1, wherein, The method further comprises: in response to a tenth instruction, displaying and setting a page component mode on a custom page, the page component mode comprising a single-column mode and a multi-column mode; if the page component mode is the multi-column mode, in response to an eleventh instruction, displaying and setting a column width on a custom page, adjusting the width of a corresponding component through the column width, the component corresponding to the column.
7. A subsystem display device, characterized by The device comprises: a matter acquisition module, configured to acquire all the matters of the authorized subsystem, the all the matters comprising pending matters, important reading matters, ordinary reading matters, completed matters and read matters; The event display module is configured to display the to-be-handled events, the to-be-read events, the important to-be-read events, the common to-be-read events, the handled events and the read events of the authorized subsystem on the portal system page in response to a first instruction, wherein the to-be-handled events include general events and subsystem-specific events. The event determination module is configured to determine a current event that needs to be approved from the to-be-handled events in response to a second instruction. The current display module is configured to display an approval form corresponding to the current event on the portal system page in response to a third instruction if the current event is the general event. The jump display module is configured to acquire a login token of the portal system, jump to a corresponding subsystem through the login token, and display the approval form corresponding to the current event on a page of the subsystem in response to a fourth instruction if the current event is the subsystem-specific event.
8. An electronic device, comprising: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the method in any one of claims 1-6 when executing the computer program.
9. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 8. The computer program is executed by the processor to implement the method in any one of claims 1-6.
10. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the method in any one of claims 1-6.