Skip to Content
author's profile photo Former Member
Former Member

EP5: How to determine the top level navigation menu entry

Hi all,

I'm wondering if it's possible to get information (e.g. Name) about the menu entry (EntryPoint) that the user

has clicked in the top level navigation.

We need this to display role-specific derived content for the user.

Any hints are welcome.

Best regards,

Rüdiger

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Aug 05, 2004 at 07:10 PM

    Hi Rüdiger,

    Were you able to resolve your problem on how to determine the top level navigation menu entry?

    Because I'm facing the same problem. I have role based iViews and one user can be assigned to more than one roles. Those roles sometimes have conflicting accesses, so being able to get the entry point from the top level navigation would solve my issue!

    Thanks and regards

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 06, 2004 at 01:20 AM

    Guys,

    Here is the documentation on Navigation API Available in EP6 SP2.

    Just use the right Interface to get to the Navigation structure. As your question is about Navigation I thought this might help you define it.

    Also available at in EP at

    Java Development->Documentation.

    *********************************************************

    Example

    Navigation Service

    The navigation service provides a generic platform for creation of navigation models and support for navigation data retrieval that origins from different navigation sources. The navigation service is the central point to register the navigation data sources (called "navigation connectors") and to pass the navigation data to the navigation presentation level (typically a navigation Portal application).

    Introduction

    The Portal navigation has following navigation parts:

    Top Level Navigation (TLN)

    Displays the first two levels of the navigation hierarchy. In the Portal (default settings), the TLN is horizontally aligned and on top of the work area.

    Detailed Navigation (DTN)

    Displays the hierarchical structure of the selected top navigation level. The DTN starts from the third level of the navigation model. In the Portal (default settings), the DTN is vertically aligned on the left hand side of the work area, below the TLN.

    Target

    Drag and Relate targets that are relevant to the content displayed in the work area. The content developer can use the “Target Editor” in the Application Designer (Portal application / Page Editor) to configure the targets.

    SeeAlso

    Links that are relevant to the content displayed in the work area. The content developer can use the “SeeAlso Editor” in the Application Designer (Portal application / Page Editor) to configure the "SeeAlso".

    Work Area

    Displays the content of the launched navigation node.

    Navigation Model

    The navigation model has three levels:

    Data level

    The navigation connectors that provide the navigation data for the navigation clients.

    Integration level

    The navigation service integrating between the data sources for creating a consistent navigation hierarchy.

    Presentation level

    Presenting the navigation hierarchies retrieved from the navigation service.

    The retrieval of the navigation data takes place as follows:

    The initialization of the Portal initializes the navigation service. In this process the navigation connectors become registered.

    The navigation Portal application calls the navigation service API to retrieve the navigation initial nodes or finds a node specified by its name. The navigation service retrieves the navigation information from the registered navigation connectors and returns the navigation units (called "navigation nodes") to the navigation Portal application. The navigation service does some preprocessing steps such as sorting and merging of navigation nodes.

    The navigation Portal application uses the retrieved navigation node(s) to display the navigation hierarchy. The navigation API supplies several methods to get additional information about the navigation node.

    Interfaces

    The navigation API provides methods for the navigation connector (the data level) and the navigation Portal applications (the presentation level). The navigation API has following interfaces:

    INavigationConnectorRegistration

    Used by the navigation connectors to call the navigation service methods. This interface covers the registering and unregistering of navigation connectors to the navigation service.

    INavigationConnector

    The interface every navigation connector has to implement in order to register to the navigation service as a valid navigation connector. This interface includes retrieval of navigation nodes from the navigation connectors.

    INavigationConnectorNode

    Defines the behavior of a single navigation unit retrieved from the navigation connector. Only objects that implement this interface can be retrieved by the navigation service therefore provided to the navigation Portal applications.

    INavigationService

    Covers the navigation hierarchy to the navigation Portal applications.

    INavigationGenerator

    Generating navigation names for launching navigation nodes.

    INavigationNode

    Defines a single navigation unit that is used by the navigation Portal applications. These objects are wrappers of the nodes retrieved from the navigation connectors INavigationConnectorNode.

    INavigationConstants

    Constants used by the navigation service.

    Navigation Connectors

    Implementing a Navigation Connector

    To implementing a navigation connector, the following interfaces have to be implemented:

    INavigationConnector

    Represents the main interface of the navigation connector to implement.

    INavigationConnectorNode

    Has to be implemented by the navigation units (which are returned by the navigation connector). The INavigationConnectorNode interface has three levels of implementation. The basic level is mandatory to implement while the other levels are optional. Implementing all levels allows the navigation Portal application to use the behavior of the navigation units.

    Registration

    A navigation connector registers to be navigation data provider using the method:

    INavigationConnectorRegistration registerConnector(String connectorKey, INavigationConnector connector);

    The registerConnector() method must be called in the afterInit() method of the navigation connector service. This guarantees that the navigation service has already created the registration environment.

    Unregistration

    A navigation connector unregisters being a navigation data provider using the method:

    INavigationConnectorRegistration unregisterConnector(String connectorKey);

    Navigation Presentation

    Initial Nodes Retrieval

    The initial nodes are found by using the method:

    INavigationService getInitialNodes(Hashtable environment);

    method. The environment argument must contain the user name and any other environment variable. The retrieved nodes are returned as NavigationNodes which is a list (of type java.util.List) of INavigationNode objects.

    Specific Node Retrieval

    A specific node is found by using the method:

    INavigationService public INavigationNode getNode(Hashtable environment, String nodeName);

    The environment argument must contain the user name and any other environment variable. The nodeName specifies the name of the node to be retrieved.

    *********************************************************

    Good Luck !

    GO.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 09, 2005 at 11:34 AM
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.