But there are scenarios where that is not suffficient. A common example is a global enterprise portal where users of different subsidiaries access the same portal. Or a holding providing the infrastructure for several different companies on the same platform.
This adds another dimension to the navigation, because in the portal view of company A you shouldn’t see navigation entry points of company B, even if he has roles belonging to both companies.
Before Netweaver 7.0 SP14 you had to develop a navigation filter (you can find blogs to that topic as well), now it’s a piece of cake doing it with standard tools.
I show you how.
First of all, filtering the navigation must be globally enabled by setting the property FilterbyDesktopView to true in the Service Configuration (default=false).
This is described here:
Now, supply each desktop with a filter id like described in the help.
Finally, you have to add the filter id(s) to your navigation entry points.
That’s it. Easy, isn’t it?
Attention! If this feature doesn’t work after restart, the following workaround might help:
Somehow there might be a problem reading the dektop configuration from the persistence, at least found some log messages pointing to access problems.
As a workaround, open the desktop’s permission settings and add the group “Everyone” with read permissions.