CN116820648A - Help document display method and device, electronic equipment and readable storage medium - Google Patents

Help document display method and device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN116820648A
CN116820648A CN202310777184.1A CN202310777184A CN116820648A CN 116820648 A CN116820648 A CN 116820648A CN 202310777184 A CN202310777184 A CN 202310777184A CN 116820648 A CN116820648 A CN 116820648A
Authority
CN
China
Prior art keywords
page
target
user
document
help document
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310777184.1A
Other languages
Chinese (zh)
Inventor
胡艳敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Dt Dream Technology Co Ltd
Original Assignee
Hangzhou Dt Dream Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Dt Dream Technology Co Ltd filed Critical Hangzhou Dt Dream Technology Co Ltd
Priority to CN202310777184.1A priority Critical patent/CN116820648A/en
Publication of CN116820648A publication Critical patent/CN116820648A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/453—Help systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/14—Details of searching files based on file metadata
    • G06F16/148—File search processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/14—Details of searching files based on file metadata
    • G06F16/156—Query results presentation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/164—File meta data generation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/168—Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • Library & Information Science (AREA)
  • Document Processing Apparatus (AREA)

Abstract

The application provides a help document display method, a device, an electronic device and a readable storage medium, wherein the method comprises the following steps: receiving an access request for a page element included in a target system; the target system comprises at least one hierarchy of page elements, the page elements corresponding to page unique identifications, the page unique identifications corresponding to document content in the help document; responding to the access request, and extracting target document content corresponding to the target page unique identifier from a pre-deployed help document according to the target page unique identifier corresponding to the target page element; and displaying to a user based on the target document content. After the system is deployed, help documents corresponding to the page elements selected by the user can be quickly acquired according to the page elements selected by the user, and displayed to the user, so that the user can better know the functions corresponding to the page elements, and the use experience of the user is improved.

Description

Help document display method and device, electronic equipment and readable storage medium
Technical Field
The present application relates to the field of big data technologies, and in particular, to a method and apparatus for displaying a help document, an electronic device, and a readable storage medium.
Background
With the development of internet technology, enterprises prefer paperless offices, and various information management systems may be used for flow processing, business docking, and the like.
Information management systems often may include multiple levels of page elements. For different page elements, a developer usually writes corresponding help documents during development to help users quickly understand specific functions implemented by each page element.
Currently, locally deployed systems are not capable of providing help documents online, which are typically offline data that is delivered offline, and even if online help documents are provided, only the address at which the help document is downloaded is provided, through which the help document is downloaded by the user. Therefore, only the user is supported to search for the content required by the user after downloading the help document, and the content of the help document corresponding to the user operation is not supported to be automatically displayed to the user according to the user operation.
Disclosure of Invention
The application provides a help document display method, which comprises the following steps:
receiving an access request for a page element included in a target system; the target system comprises at least one hierarchy of page elements, the page elements corresponding to page unique identifications, the page unique identifications corresponding to document content in the help document;
Responding to the access request, and extracting target document content corresponding to the target page unique identifier from a pre-deployed help document according to the target page unique identifier corresponding to the target page element;
and displaying to a user based on the target document content.
Optionally, the method further comprises:
determining page elements of at least one hierarchy of usage rights of a user in the target system;
based on the unique page identifier corresponding to the page element of at least one level of the user with the use authority in the target system, respectively extracting document contents corresponding to the unique page identifier of the page element of at least one level from a pre-deployed help document;
generating a help document directory tree based on the page unique identification of the page element of the at least one hierarchy and the document content corresponding to the page unique identification; the help document directory tree includes at least one help document directory, the hierarchical relationships between the help document directories corresponding to the hierarchical relationships between the page elements; the help document catalog contains document content corresponding to the page unique identification.
Optionally, the extracting, according to the unique target page identifier corresponding to the target page element, target document content corresponding to the unique target page identifier in the pre-deployed help document includes:
traversing the help document directory tree according to the unique target page identifier corresponding to the target page element, and determining whether the help document directory tree comprises target document content corresponding to the unique target page identifier;
and if so, extracting target document content corresponding to the target menu unique identification from the help document catalog.
Optionally, the determining the page element of at least one hierarchy of the user having the usage right in the target system includes:
obtaining a login license corresponding to the user, wherein the login license comprises at least one level of page elements of which the user has use rights in the target system;
based on the login license, at least one level of page elements for which the user has usage rights in the target system is determined.
Optionally, the login license includes a permission code of at least one level of page elements corresponding to the user;
Based on the login license, determining page elements of at least one hierarchy of usage rights for a user in the target system, comprising:
and acquiring the authority code of the page element of at least one level corresponding to the user in the login license, and determining the page element of at least one level with the user's use authority in the target system based on the numerical value of the authority code.
Optionally, the presenting to the user based on the target document content includes:
and responding to the viewing operation of the user on the help document in the target system, and displaying the content of the target document to the user through an interface provided by the target system.
Optionally, the method further comprises:
responding to a change operation of a user for the name of any target page element in the target system, and acquiring a target page unique identifier of the target page element and the changed name of the target page element;
traversing the help document directory tree, and based on the unique target page identifier, updating the help document directory name corresponding to the unique target page identifier into the name of the target page element in the help document directory tree.
Optionally, the method further comprises:
traversing a pre-deployed help document, and updating the names of target page elements in document contents of the help document into the names of the target page elements after user modification.
Optionally, the method further comprises:
responding to the position replacement operation of a user on a first target page element and a second target page element in the target system, and acquiring a first page unique identifier of the first target page element and a second page unique identifier of the second target page element;
traversing the help document directory tree, and exchanging the positions of a first help document directory corresponding to the first page unique identifier and a second help document directory corresponding to the second page unique identifier in the help document directory tree based on the first page unique identifier and the second page unique identifier.
Optionally, the method further comprises:
traversing a pre-deployed help document, updating a first target page element in a description path associated with the first target page element in the document content of the help document into a second target page element, and updating a second target page element in the description path associated with the second target page element in the document content of the help document into the first target page element.
The present application provides a help document display apparatus, the apparatus comprising:
a request receiving unit, configured to receive an access request for a page element included in a target system; the target system comprises at least one hierarchy of page elements, the page elements corresponding to page unique identifications, the page unique identifications corresponding to document content in the help document;
the content extraction unit is used for responding to the access request, and extracting target document content corresponding to the target page unique identifier from a pre-deployed help document according to the target page unique identifier corresponding to the target page element;
and the content display unit is used for displaying the target document content to a user.
The application also provides electronic equipment, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus;
the memory stores machine readable instructions and the processor performs the method by invoking the machine readable instructions.
The present application also provides a computer readable storage medium storing machine readable instructions that when invoked and executed by a processor implement the above-described method.
In the scheme described in the above embodiment, by receiving an access request for a page element included in a target system and acquiring a page unique identifier corresponding to the page element, extracting target document content corresponding to the target page unique identifier from a pre-deployed help document, and further displaying the document content to a user. The target system can quickly acquire the help document corresponding to the page element selected by the user according to the operation of the user in real time and automatically display the help document to the user, so that the user can better know the function corresponding to the page element, and the use experience of the user is improved.
Drawings
FIG. 1 is a flow diagram illustrating a method of facilitating document presentation in accordance with an exemplary embodiment.
Fig. 2 is a schematic diagram of an information management system according to an exemplary embodiment.
FIG. 3 is a flow chart of a method for generating a help document directory tree according to an exemplary embodiment.
FIG. 4 is a schematic diagram of a help document directory tree, as shown in an exemplary embodiment.
Fig. 5 is a schematic diagram of an information management system according to an exemplary embodiment.
Fig. 6 is a schematic diagram of an information management system according to an exemplary embodiment.
FIG. 7 is a hardware block diagram of an electronic device in which a help document presentation apparatus is located, as shown in an exemplary embodiment.
FIG. 8 is a block diagram of a help document presentation device, as shown in an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.
Referring to fig. 1, fig. 1 is a flowchart of a method for presenting a help document according to an exemplary embodiment. The method may comprise the steps of:
step 102, receiving an access request for a page element included in a target system; the target system includes at least one hierarchy of page elements corresponding to a page unique identification corresponding to document content in a help document.
In this specification, the target system may be an information management system comprising at least one hierarchy of page elements, wherein different page elements may be used to expose different functions of the information management system.
Referring to fig. 2, fig. 2 is a schematic diagram of an information management system according to an exemplary embodiment. As shown in fig. 2, the page element shown in fig. 2 may be a menu. Wherein, the multilevel menu can not only form multilevel page elements.
The left side of fig. 2 is a menu provided by the information management system, for example, organization management, user management, tenant management, and system management is a first-level menu; for example, under the user management menu, there is system user management, and the user management is organized into a second-level menu, and forms a multi-level menu with the user management menu. The right side of fig. 2 is the content displayed by each menu and the functions corresponding to each menu, for example, in fig. 2, all user information of the current information management system can be displayed under the user management menu, and the user can select the user information therein to perform operations such as modification or deletion.
In this specification, the target system includes at least one hierarchy of page elements corresponding to a page unique identifier for uniquely determining the page element and managed by the page unique identifier. The page unique identification may be generally represented by a page id, which may be a string of characters consisting of symbols, numbers or letters.
For example, in the information Management system as shown in fig. 2, the page unique identifier of "Organization Management" may be organization_management, the page unique identifier of "User Management" may be user_ma Management, or the like.
When the help document corresponding to the information management system is developed, the document content in the help document corresponding to the page element is marked with the page unique identifier corresponding to the page element, and the document content in the help document corresponding to the page element can be quickly searched through the page unique identifier by the page unique identifier.
The specific manner in which the page unique identifier corresponds to the document content in the help document is not specifically limited in this specification. For example, it may be stored in the form of key-value pairs, with the page unique identifier being a key, and the document content itself of the help document being stored as a value. For another example, the page unique identifier may be included as part of the help document file name. As another example, the page unique identification may also be written into the help document content, or the help document may also be at the end of the header page, or the like.
For example, in the information Management system shown in fig. 2, when the document content of the Help document corresponding to "Organization Management" is developed, the name thereof may be "organization_management_help", so as to implement that the Help document is marked with a page unique identifier corresponding to its page element.
In this specification, the page element may specifically include a multi-level menu in a page, menu options in the multi-level menu, and different function buttons in the page, etc., and is not specifically limited in this specification. Different page elements may have different page unique identifications and correspond to different document content in the help document.
In this specification, a user may select a page element in a target system and initiate an access request for the page element in the target system. For example, the user may select a page element of the target system through a mouse, and further initiate an access request for the page element by means of double clicking, right clicking, or the like.
And step 104, responding to the access request, and extracting target document content corresponding to the target page unique identifier from the pre-deployed help document according to the target page unique identifier corresponding to the target page element.
In this specification, when the target system is deployed, a help document corresponding to the target system may be deployed with a software package of the target system.
The target system can respond to the access request of the user for the target page element and acquire the unique target page identifier corresponding to the target page element. And extracting target document content corresponding to the target page unique identification from the pre-deployed help document.
For example, the help document may be stored in key value pairs, the page unique identifier is used as a key, and the document content of the help document is stored as a value. Therefore, the target document content corresponding to the target page unique identifier can be extracted directly through the page unique identifier.
And step 106, displaying to a user based on the target document content.
And the target system extracts target document content corresponding to the page unique identifier based on the page unique identifier, and then can display the target document content to a user.
The specific implementation manner of displaying the target document content to the user is not specifically limited in the present specification. For example, when a user accesses a page element, the target system may suspend the target document content in the target system by means of text suspension after extracting the target document content. For another example, the user may further display the target document content on an interface provided by the target system by selecting a help document viewing option provided by the target system, and so on.
In one embodiment, the target system may determine page elements of at least one hierarchy of usage rights of a user in the target system, and generate a help document directory tree according to the page elements and help document content corresponding to the page elements.
FIG. 3 is a flow chart of a method for generating a help document directory tree according to an exemplary embodiment. The method may comprise the steps of:
step 302, determining at least one hierarchical page element of which the user has a right to use in the target system.
The specific manner in which the target system determines the usage rights of the user for each level of menu in the information management system is not specifically limited in this specification.
For example, the target system may be divided into different system versions, and the usage rights of at least one hierarchical page element owned by the user are determined by the different system version numbers purchased by the user. For another example, the target system may determine the usage rights of at least one level of page elements owned by the user based on matching the user's username with the rights management system. For another example, a background administrator may configure usage rights for at least one hierarchy of page elements for a user based on a target system purchased by the user.
Step 304, based on the page unique identification corresponding to the page element of at least one level of the user with the use authority in the target system, respectively extracting the document content corresponding to the page unique identification of the page element of at least one level from the pre-deployed help document.
The content of the document corresponding to the page unique identifier is extracted from the pre-deployed help document through the page unique identifier and is consistent with the above, and details are not repeated here.
Step 306, generating a help document directory tree based on the page unique identifier of the page element of the at least one hierarchy and the document content corresponding to the page unique identifier; the help document directory tree includes at least one help document directory, the hierarchical relationships between the help document directories corresponding to the hierarchical relationships between the page elements; the help document catalog contains document content corresponding to the page unique identification.
In this specification, the page elements in the target system are formed by multiple levels of page elements, such as the information management system shown in fig. 2, "user management-system user management" is that page elements forming two levels.
In order to improve the retrieval efficiency of the help document, the information management system can construct a help document directory tree, and the structure of the help document directory tree is consistent with the hierarchical relationship of various levels of menus with use rights of users in the information management system.
For example, referring to FIG. 4, FIG. 4 is a schematic diagram of a help document directory tree provided by an exemplary embodiment.
As shown in fig. 4, the structure of the help document directory tree shown in fig. 4 is identical to the actual structure of the menus of the respective levels in the information management system shown in fig. 2. In the information management system shown in fig. 2, organization management, user management, tenant management, and system management are first-level menus; user management-system user management, user management-organization user management respectively form a secondary menu. The help document directory tree, organization management, user management, tenant management, system management shown in fig. 3 is a primary directory, and the user management-system user management-organization user management respectively forms a secondary directory.
In one embodiment, the target system may further traverse the help document directory tree according to the target page unique identifier corresponding to the target page element, and determine whether the help document directory tree includes target document content corresponding to the target page unique identifier;
And if so, extracting target document content corresponding to the target menu unique identification from the help document catalog.
Because the help document directory tree only contains at least one level of page elements with the use permission of the user, the user can be authenticated by the help document directory tree before the help document directory tree is displayed to the user, and the corresponding help document is displayed according to the levels of page elements with the use permission of the user. The user cannot view the help document corresponding to the page element without the use permission, and the business data can be better protected for the developer of the information management system.
In one embodiment, a login license corresponding to the user may be obtained, the login license including at least one level of page elements for which the user has usage rights in the target system;
based on the login license, at least one level of page elements for which the user has usage rights in the target system is determined.
In this specification, the login license may be a license that a background administrator typically configures for versions of the target system purchased by different users. The login license includes at least one hierarchy of page elements for which the user has usage rights in the target system.
For example, as in the information management system shown in fig. 2, a background administrator sets a use authority for a user that the user has user management, tenant management, and a login license may be generated based on a page element for which the user has use authority. The login license can comprise user management and tenant management use permission.
The login license can store the unique page identification of the page elements of at least the hierarchy of the user with the use permission in the form of a list, a linked list, a Map or the like. After the target system acquires the login license, the unique page identifier of the page element with the use permission of the user can be directly read from the login license, so that the page element with the use permission of the user in the target system is determined.
The login license, as well as the page unique identification of the page element for which the user has usage rights, may be stored in the database of the target system in the form of key-value pairs. The target system can acquire the login license, and reads the page unique identifier corresponding to the page element with the use permission of the user corresponding to the login license from the database.
When the same user logs in the information management system again, the login license can be directly obtained through the user name of the user, and further obtaining the login license comprises the use authority of the user for at least one level of page elements in the information management system.
In order to improve the security of the information management system, a login license may be generated at each login, and the login license may be automatically destroyed when the user exits. The present specification is not particularly limited.
In one embodiment, the login license includes a rights code of at least one hierarchy of page elements corresponding to the user; the target system can acquire the authority codes of all levels of menus corresponding to the user, and determine the page elements of at least one level of the user with the use authority in the information management system based on the numerical value of the authority codes corresponding to the page elements of at least one level.
In practical application, the permission code may be represented by 0 and 1, where 0 indicates that the user does not have the use permission of the level of page element, and 1 indicates that the user has the use permission of the page element.
The target system can acquire the permission codes corresponding to different system versions according to the different system versions purchased by the user, so that the page elements with the use permission of the user in the target system are further determined. The target system can also query a database of the authority management system according to the user name used when the user logs in, and determine the authority code of at least one level of page elements corresponding to the user name, so as to further determine each level of page elements with the use authority of the user in the information management system.
The page elements of at least one hierarchy of which the user has the selection authority are stored in the login license in the form of the authority code, so that the target system can quickly determine the page elements of at least one hierarchy of which the user has the use authority in the information management system through the authority code.
In one embodiment, the target system presents the target document content to a user through an interface provided by the target system in response to a user's viewing operation of the help document in the target system.
Referring to fig. 5, fig. 5 is a schematic diagram of an information management system according to an exemplary embodiment.
As shown in FIG. 5, when a user selects a user management menu and needs to view a help document, a corresponding button or icon provided by a target system may be clicked, which may provide a help document presentation interface and output a presentation to the user. As shown on the right side of FIG. 5, the target system may provide a window hovering over the system interface for presenting help documents corresponding to the user management menu.
The target system may provide global buttons or icons for presenting help documents, such as in the form of question mark icons, presented on an interface provided by the information management system. When the user selects the target page element, clicking a global button or icon for displaying the help document, so that the help document corresponding to the target page element can be displayed.
The target system can also provide corresponding buttons or icons for displaying the help documents for each menu respectively, and when a user selects a button or icon for displaying the help documents corresponding to a target page element, the help documents corresponding to the target page element can be displayed.
Referring to fig. 6, a schematic diagram of an information management system according to an exemplary embodiment of fig. 6 is provided. As shown in fig. 6, on the left side of the organization management menu, there is a question mark icon, and the user can display a help document corresponding to organization management by clicking on the icon. Similarly, clicking on the icon on the left side of the user management can also directly display the help document corresponding to the user management. When the user selects the user management interface, the function interface on the right side is also provided with a question mark icon, the icon is a global icon, and when the user selects the user management menu, the user can click the icon again to display the help document corresponding to the user management.
In one embodiment, the target system may update the help document directory tree in reverse based on a user's name modification operation for the information management system.
The user can change the name of any target page element in the target system, and the corresponding target system can reversely update the name of the help stabilizing directory corresponding to the page element in the help document directory tree.
The target system responds to the changing operation of a user for the name of any target page element in the target system, and obtains the unique target page identification of the target page element and the changed name of the target page element;
traversing the help document directory tree, and based on the unique target page identifier, updating the help document directory name corresponding to the unique target page identifier into the name of the target page element in the help document directory tree.
For example, as shown in the information management system of fig. 2, a user modifies a menu name of tenant management into authorization management, and the information management system may acquire a menu unique identifier corresponding to tenant management, and the modified menu name "authorization management", further traverse a help document directory tree, determine a specific location of a help document directory through the menu unique identifier, and further update the help document directory name of tenant management in the help document directory tree into "authorization management".
After the user changes the name of any target page element, the target system can traverse the pre-deployed help document, and update the name of the target page element in the document content of the help document to the name of the target page element after the user changes.
For example, as shown in fig. 2, the information management system may include "a specific implementation of tenant management is XXX" in the help document content corresponding to the information management system, and since the user has changed tenant management to "authority management", the "tenant management" in the help document content needs to be changed to "authority management", and the target system may traverse the pre-deployed help document and update the help document content to "a specific implementation of authority management is XXX".
In one embodiment, the user may also change the position between two page elements, and the corresponding target system may update the help document directory tree in a reverse direction according to the user's position replacement operation for the page elements in the target system.
The target system can respond to the position replacement operation of a user on a first target page element and a second target page element in the target system, and acquire a first page unique identifier of the first target page element and a second page unique identifier of the second target page element;
traversing the help document directory tree, and exchanging the positions of a first help document directory corresponding to the first page unique identifier and a second help document directory corresponding to the second page unique identifier in the help document directory tree based on the first page unique identifier and the second page unique identifier.
For example, as in the information management system shown in fig. 2, the user exchanges the tenant management menu with the system management menu, and the information management may obtain a first menu unique identifier of the tenant management menu and a second menu unique identifier of the system management menu. And exchanging the positions of the help documents corresponding to the tenant management menu and the help documents corresponding to the system management menu based on the first menu unique identification and the second menu unique identification.
After the user changes the position between the first target page element and the second target page element, the description path associated with the first target page element and the description path associated with the second target page element in the document content of the help document need to be changed accordingly.
The description path specifically comprises a description path formed by multi-level page elements, and the specific content of the description path comprises a first-level page element, a second-level page element and a third-level page element in sequence from left to right. For example, in the information management system shown in fig. 2, "user management-system user management" is one of the description paths.
The target system may also traverse a pre-deployed help document and update a first target page element in a description path associated with the first target page element in the document content of the help document to a second target page element, and update a second target page element in a description path associated with the second target page element in the document content of the help document to a first target page element.
For example, as in the information management system shown in fig. 2, the user previously replaces the locations of "system user management" and "organization user management". The help document content corresponding to the information management system may include "xxx" which is a specific setting in the user management-system user management ", and because the user has changed" system user management "to" organization user management ", the" user management-system user management "in the help document content needs to be changed to" user management-organization user management ", and the target system may traverse the pre-deployed help document and update the system user management in the description path associated with the system user management in the help document content to organization user management.
By means of a mechanism for reversely refreshing the help document directory tree, even if a user modifies the name of a page element or the position of the page element at the front end, the help document corresponding to the modified page element can be accurately searched when the user inquires help. The user does not need to manually modify the help document directory tree, so that the time for searching the help document content is saved, and the use experience of the user is improved.
Referring to fig. 7, fig. 7 is a hardware configuration diagram of an electronic device in which the help document display apparatus is located in an exemplary embodiment. At the hardware level, the device includes a processor 702, an internal bus 704, a network interface 706, memory 708, and non-volatile storage 710, although other hardware required by the service is possible. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 702 reading a corresponding computer program from the non-volatile storage 710 into the memory 708 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
Referring to FIG. 8, FIG. 8 is a block diagram of a help document presentation device, as shown in an exemplary embodiment. The help document display device can be applied to the electronic equipment shown in fig. 7 to realize the technical scheme of the specification. Wherein, the help document display device may include:
a request receiving unit 802, configured to receive an access request for a page element included in a target system; the target system comprises at least one hierarchy of page elements, the page elements corresponding to page unique identifications, the page unique identifications corresponding to document content in the help document;
a content extraction unit 804, configured to extract, in response to the access request, a target document content corresponding to the target page unique identifier according to the target page unique identifier corresponding to the target page element, from a pre-deployed help document;
and the content display unit 806 is configured to display the target document content to the user.
In this embodiment, the apparatus further includes:
a directory tree construction unit for determining page elements of at least one hierarchy level of a user having a use right in the target system;
based on the unique page identifier corresponding to the page element of at least one level of the user with the use authority in the target system, respectively extracting document contents corresponding to the unique page identifier of the page element of at least one level from a pre-deployed help document;
Generating a help document directory tree based on the page unique identification of the page element of the at least one hierarchy and the document content corresponding to the page unique identification; the help document directory tree includes at least one help document directory, the hierarchical relationships between the help document directories corresponding to the hierarchical relationships between the page elements; the help document catalog contains document content corresponding to the page unique identification.
In this embodiment, the directory tree construction unit further traverses the help document directory tree according to the unique target page identifier corresponding to the target page element, and determines whether the help document directory tree includes target document content corresponding to the unique target page identifier;
and if so, extracting target document content corresponding to the target menu unique identification from the help document catalog.
In this embodiment, the directory tree construction unit is further configured to obtain a login license corresponding to the user, where the login license includes at least one level of page elements of which the user has a use right in the target system;
based on the login license, at least one level of page elements for which the user has usage rights in the target system is determined.
In this embodiment, the login license includes a permission code of at least one level of page elements corresponding to the user;
the directory tree construction unit is further configured to obtain a permission code of the at least one level of page elements corresponding to the user in the login license, and determine, based on a value of the permission code, the at least one level of page elements of the user having a use permission in the target system.
In this embodiment, the content display unit is further configured to display, in response to a viewing operation of the user on the help document in the target system, the target document content to the user through an interface provided by the target system.
In this embodiment, the apparatus further includes:
the first reverse updating unit is used for responding to the changing operation of a user for the name of any target page element in the target system and acquiring the unique target page identification of the target page element and the changed name of the target page element;
traversing the help document directory tree, and based on the unique target page identifier, updating the help document directory name corresponding to the unique target page identifier into the name of the target page element in the help document directory tree.
In this embodiment, the apparatus further includes:
and the first content updating unit is used for traversing the pre-deployed help document and updating the names of the target page elements in the document content of the help document into the names of the target page elements changed by the user.
In this embodiment, the apparatus further includes:
the second reverse updating unit is used for responding to the position replacement operation of a user on a first target page element and a second target page element in the target system and acquiring a first page unique identifier of the first target page element and a second page unique identifier of the second target page element;
traversing the help document directory tree, and exchanging the positions of a first help document directory corresponding to the first page unique identifier and a second help document directory corresponding to the second page unique identifier in the help document directory tree based on the first page unique identifier and the second page unique identifier.
In this embodiment, the apparatus further includes:
and the second content updating unit is used for traversing the pre-deployed help document, updating a first target page element in a description path associated with the first target page element in the document content of the help document into a second target page element, and updating a second target page element in the description path associated with the second target page element in the document content of the help document into the first target page element.
The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are illustrative only, in that the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The present specification also provides an embodiment of a computer-readable storage medium. The computer readable storage medium stores machine readable instructions that, when invoked and executed by a processor, implement the help document presentation method provided by any of the embodiments in the present specification.
The computer readable storage medium provided by the embodiments of the present specification may include, but is not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks, ROMs (Read-Only memories), RAMs (Random Access Memory, random access memories), EPROMs (Erasable Programmable Read-Only memories), EEPROMs (Electrically Erasable Programmable Read-Only memories), flash memories, magnetic cards, or optical fiber cards. That is, a readable storage medium includes a readable medium that can store or transfer information.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.

Claims (10)

1. A help document presentation method, the method comprising:
receiving an access request for a page element included in a target system; the target system comprises at least one hierarchy of page elements, the page elements corresponding to page unique identifications, the page unique identifications corresponding to document content in the help document;
responding to the access request, and extracting target document content corresponding to the target page unique identifier from a pre-deployed help document according to the target page unique identifier corresponding to the target page element;
and displaying to a user based on the target document content.
2. The method of claim 1, the method further comprising:
determining page elements of at least one hierarchy of usage rights of a user in the target system;
Based on the unique page identifier corresponding to the page element of at least one level of the user with the use authority in the target system, respectively extracting document contents corresponding to the unique page identifier of the page element of at least one level from a pre-deployed help document;
generating a help document directory tree based on the page unique identification of the page element of the at least one hierarchy and the document content corresponding to the page unique identification; the help document directory tree includes at least one help document directory, the hierarchical relationships between the help document directories corresponding to the hierarchical relationships between the page elements; the help document catalog contains document content corresponding to the page unique identification.
3. The method of claim 2, wherein the extracting, in the pre-deployed help document, the target document content corresponding to the target page unique identifier according to the target page unique identifier corresponding to the target page element includes:
traversing the help document directory tree according to the unique target page identifier corresponding to the target page element, and determining whether the help document directory tree comprises target document content corresponding to the unique target page identifier;
And if so, extracting target document content corresponding to the target menu unique identification from the help document catalog.
4. A method according to claim 3, said determining page elements of at least one hierarchy of user rights in the target system, comprising:
obtaining a login license corresponding to the user, wherein the login license comprises at least one level of page elements of which the user has use rights in the target system;
based on the login license, at least one level of page elements for which the user has usage rights in the target system is determined.
5. The method of claim 4, the login license comprising a permission code of at least one hierarchy of page elements corresponding to a user;
based on the login license, determining page elements of at least one hierarchy of usage rights for a user in the target system, comprising:
and acquiring the authority code of the page element of at least one level corresponding to the user in the login license, and determining the page element of at least one level with the user's use authority in the target system based on the numerical value of the authority code.
6. The method of claim 2, the method further comprising:
responding to a change operation of a user for the name of any target page element in the target system, and acquiring a target page unique identifier of the target page element and the changed name of the target page element;
traversing the help document directory tree, and based on the unique target page identifier, updating the help document directory name corresponding to the unique target page identifier into the name of the target page element in the help document directory tree.
7. The method of claim 2, the method further comprising:
responding to the position replacement operation of a user on a first target page element and a second target page element in the target system, and acquiring a first page unique identifier of the first target page element and a second page unique identifier of the second target page element;
traversing the help document directory tree, and exchanging the positions of a first help document directory corresponding to the first page unique identifier and a second help document directory corresponding to the second page unique identifier in the help document directory tree based on the first page unique identifier and the second page unique identifier.
8. A help document presentation apparatus, the apparatus comprising:
a request receiving unit, configured to receive an access request for a page element included in a target system; the target system comprises at least one hierarchy of page elements, the page elements corresponding to page unique identifications, the page unique identifications corresponding to document content in the help document;
the content extraction unit is used for responding to the access request, and extracting target document content corresponding to the target page unique identifier from a pre-deployed help document according to the target page unique identifier corresponding to the target page element;
and the content display unit is used for displaying the target document content to a user.
9. An electronic device comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
the memory stores machine readable instructions, and the processor performs the method of any of claims 1-7 by invoking the machine readable instructions.
10. A computer readable storage medium storing machine readable instructions which, when invoked and executed by a processor, implement the method of any one of claims 1-7.
CN202310777184.1A 2023-06-28 2023-06-28 Help document display method and device, electronic equipment and readable storage medium Pending CN116820648A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310777184.1A CN116820648A (en) 2023-06-28 2023-06-28 Help document display method and device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310777184.1A CN116820648A (en) 2023-06-28 2023-06-28 Help document display method and device, electronic equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN116820648A true CN116820648A (en) 2023-09-29

Family

ID=88123650

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310777184.1A Pending CN116820648A (en) 2023-06-28 2023-06-28 Help document display method and device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN116820648A (en)

Similar Documents

Publication Publication Date Title
JP6599906B2 (en) Login account prompt
CN109787946B (en) Access method and authority management method and device for shared space
WO2020023828A1 (en) Blockchain-based cross-chain data operation method and apparatus
US20120131470A1 (en) Integrated Application Feature Store
US20230177009A1 (en) Techniques for handling letter case in file systems
CN108268609A (en) A kind of foundation of file path, access method and device
US9971789B2 (en) Selective disk volume cloning for virtual disk creation
US11803621B1 (en) Permissions searching by scenario
CN112257005B (en) Form component generation method and device
CN109240678B (en) Code generation method and device
US11645279B2 (en) Index selection for database query
US9483535B1 (en) Systems and methods for expanding search results
US9430530B1 (en) Reusing database statistics for user aggregate queries
CN116414935A (en) Method for distributed Search space vector data based on Elastic Search
CN111381745B (en) Page switching method, device and equipment
US20140379762A1 (en) Content management system
CN116820648A (en) Help document display method and device, electronic equipment and readable storage medium
CN105354506A (en) File hiding method and apparatus
US11720554B2 (en) Iterative query expansion for document discovery
US11003721B2 (en) System, control method, and storage medium
US11080238B2 (en) System and method for interactive visual representation of metadata within a networked heterogeneous workflow environment
CN111722881A (en) Resource expansion method, system and device of container cloud platform
JP6307287B2 (en) File management system, file management method, and program for file management system
CN111125083B (en) Historical record screening method and device
JP2004280416A (en) Software parts management system, software parts management method, and software parts management program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination