Skip to end of metadata
Go to start of metadata


A URL that navigates to a specific navigation node is made up of the base portal URL, plus a NavigationTargetparameter, whose value is a navigation target.
For example, the following URL :
navigates to the navigation node represented by the navigation target ROLES://portal_content/myFolder/myRole.
The navigation target is made up of the following parts:
●      Prefix: A string that represents the navigation connector that defines the requested navigation node. For the roles connector, the prefix is ROLES.
●      Separator: The character string ://
●      Internal URL or Path: A string that can be interpreted by the specified navigation connector.
In the example, the path is portal_content/myFolder/myRole.

You can merge a node from one role with a same-level node from another role. Both nodes then appear as one entry in the top-level or detailed navigation, with their respective subnodes appearing in a given sequence beneath the new merged node.
You can merge the following objects:

Entry points
Root nodes of roles and worksets
Folders in roles or worksets.

Both the merging of nodes and the setting of display priorities of the merged nodes are accomplished through various property settings :

●      Merge ID: A property of a node or entry within a role or workset. It consists of a given string that you must enter as a value. All nodes to be merged with the selected node must contain precisely this value. The navigation service checks the values of all navigation nodes, and all entries with identical values are merged.

●      Can be Merged: A property that defines an object as eligible for merging.

●      Merge Priority: A property that determines which node in a merged group is the dominant node, affecting the title, the display type (in a new window or in-place), the sort priority, and other properties of the node.

Navigation zoom allows you to subdivide the portal into a main portal and several subportals to enable the users to view specific subject areas of the portal separately from the rest of the portal.
At runtime, clicking a navigation zoom point replaces the main portal screen with a subset of the navigation hierarchy. The navigation zoom point becomes the root node, and all of the navigation nodes below the navigation zoom point are now arranged in top-level navigation and detailed navigation.
Only items that appear in detailed navigation can be configured as navigation zoom points. Top-level navigation items cannot be navigation zoom points.
In the navigation zoom, portal users can click Back to Main Portal to return to the main navigation hierarchy.
When portal users click the arrow beside the navigation zoom point, the item expands in the Detailed Navigation iView without replacing the portal screen.
Don’t use navigation zoom with the hovering effect.

Quick links are shortcuts to iViews and pages. Each quick link is a string that you add to the default portal URL in order to navigate to a specific iView or page
Quick links are created by setting the Quick Link property of a page or iView. They can be assigned to any page or iView navigation node to which navigation is possible
If you assign a quick link to an invisible node, the page is displayed but the top-level and detailed navigation iViews do not highlight the nodes in the selected path.
To view the page or iView, append a slash (/) to the default portal URL, followed by the quick link
For example : http://myServer:50000/irj/portal/myQuickLink
If you assign a quick link to an invisible node, the page is displayed but the top-level and detailed navigation iViews do not highlight the nodes in the selected path
Quick links should be unique within the portal. However, nothing prevents you from creating a duplicate quick link. If one quick link string is defined for two navigation nodes, the first node in the user’s navigation tree is displayed
Quick links must be composed of only URI unreserved characters, which are letters, digits, hyphen (‑), period (.), underscore (_) and tilde (~)


A Workset Map is the equivalent of a site map, providing users with explicit information about the functionality that is available in a given workset. It is based on an iView, and serves as a central point of entry and guided access to the contents of a workset.
The content developer creates the Workset Map iView using the portal worksetMap component, and adds it to the relevant workset.
Depending on the navigation hierarchy, the iView can appear as one of the following:
A tab in top-level navigation, with each item in the workset appearing as a subtab
A node in Detailed Navigation in the navigation panel
Links to pages and worksets are enriched by graphical and textual information. Each Workset Map iView contains:
        A short textual explanation of each item
         Identifying pictograms
         Direct links to the target pages


The Service Map iView is an ERP-specific variant of the portal Workset Map iView. It serves as a central point of entry and guided access to the services of SAP service modules such as the Manager Self Service (MSS) module, or the Employee Self Service (ESS) module.

A Service Map iView displays three levels of navigation hierarchy and contains:       
A short textual explanation of each service in the module    
Identifying pictograms of first-level item
Direct links from the third-level items to the target forms and pages

Creating a Service Map iView  has the same steps as workset map iview , the only difference is that In the iView Wizard Template Selection screen, we select Service Map iView.

For each item in the service, configure the following properties in the Property Editor:
Pictogram: From the list, select the name of an image to represent the service entry. You will see only the pictograms that relate to items on level 1.
       iView Name: This name was set when the object was created.
      Description: If this value was not entered when the object was created, then write a description of the entry now, or if necessary, edit what was written. This value can be edited at any time.


You can filter entry points so that only certain entry points are displayed in a given desktop. This is accomplished by specifying a Filter ID for roles, worksets, or folders that have been defined as entry points, and then adding the relevant Filter ID values to the desktop. At runtime, the desktop in use only displays the entry points with filter IDs that match the filter IDs specified in the desktop


  • No labels