According to this model, detailed navigation is part of a page and is assigned to a page as a Java iView. This is the delivered default model that can be used to define your detailed navigation.

Use the following two variants:

• Variant I: You create only one default page for detailed navigation. This has the advantage that you do not need a page with detailed navigation (variant II) for each folder of a role on the second level of top-level navigation. If a portal user clicks on a folder in a role in the second level of the top-level navigation and it does not have a page, this default page is automatically started in the content area. The disadvantage of this variant is that only this one page with the same iViews is displayed for every folder in a role.
• Variant II: You create different pages with detailed navigation and make sure that at least every role folder appearing as an entry on the second level of the top-level navigation in the portal has a page with detailed navigation. If this is not the case, no detailed navigation is displayed in the portal.

You can also use a combination of variants I and II. For example, you can design your roles and pages so that you create different pages, each having detailed navigation. You link these pages in your role in the folder for which you created your own special page. You also have a default page that is used when a folder in your role does not contain a special page with detailed navigation.