Skip to Content

Portal pages and iViews placed in the navigation can be indexed and appear in the search results with their full PCD URL (e.g. /irj/portal?NavigationTarget=ROLES://…). These URLs are not very user friendly.

If an object has a QuickLink property, why not use it in the navigation path shown for this object in the search results?

This feature has been developed as part of the Customer Connection Program and is available for NetWeaver Enterprise Portal 7.3 SP8 and NetWeaver Enterprise Portal 7.31 SP4.

Now when you search you’ll see nicer URLs as the navigation targets shown at the bottom of the page.

QuickLinkScreenShot.png

To enable the feature perform the following steps:

  1. In the NWA, under “Application Modules” locate the “com.sap.portal.index.provider”
  2. Choose SpiderIndexingService and set the property “enableQuickLinkInSearchResults” to “true”
  3. Save and restart the service
  4. Reindex the Portal (http://help.sap.com/saphelp_nw73/helpdata/en/fd/facb8487004a968da6a4b4f2ed9106/frameset.htm)
  5. To turn the feature off, if you’d like, set the “enableQuickLinkInSearchResults” to “false” and perform steps 3-4 again.

Related note: 1693141

Have a feature you’d like to add to Enterprise Portal? Place it in the ideas place.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Simon Kemp

    Hi Alexandra,

    Thanks for your post. I just had a couple of questions…

    Can you expand a little bit as to why the customer wanted to use the more friendly URLs? I know the long ones are not really human usable but I would have thought that most people would just click on the link from the search page anyway… and then maybe save to their favourites or something. I am just trying to understand the use case a bit better.

    Second… you mention 7.3 SP8… I know that SP7 was just recently released do you know when we should expect SP8?

    Thanks again,

    Simon

    (0) 
    1. Alexandra Shapilov Post author

      Hi Simon,

      I believe the need for using QuickLinks in the search results was more an aesthetic one. Although the URL itself is not actually used (typed in address bar) by users, it is still visible in the whole search environment and presented later on in the address bar once it is clicked on from the search results. Some inconsistency (purely UI-wise) occurred in the following case:

      When navigating to an object with QuickLink property configured on it, the url in the address bar is shown with the quicklink (something like <host>:<port>/irj/portal/quickLink).
      When navigating to the same object from the search results, the url (both on
      the bottom of the page and later on in the addres bar) is something less pretty, with the whole pcd path and parameters.

      Regarding your second question, I cannot guarantee SP releases since things might change, so I’ll carefully say that 7.3 SP8 should be released to customers around CW40-41, which is end of September 2012.

      Regards,

      Alex

      (0) 

Leave a Reply