Show TOC

Understanding Framework PagesLocate this document in the navigation structure

Use

A framework page is a portal page object that contains user interface units, which together define the layout and structure of a portal desktop. A framework page contains the core iViews and pages that are required by a user to operate and navigate the portal.

Structure

A typical framework page includes the following components that comprise a portal desktop. For more information, see Understanding the Portal Interface ):

  • Header area

  • Navigation areas (for example, the top-level navigation area and the navigation panel)

  • Content area

The portal also provides:

  • A headerless framework page for the purpose of supporting headerless navigation (see Headerless Navigation ).

  • Framework pages for mobile devices, to support portal on device.

Organizations can generate multiple framework pages for their portal users, each one customized to suit a different user environment, browsing scenario, or role.

Framework pages are assigned to portal users via portal desktop objects (see Understanding Portal Desktops ). A portal desktop object combines any number of framework pages and portal themes. Portal desktops are assigned to users, groups, or roles via portal display rules (see Understanding Portal Display Rules ). A portal display rule determines which default portal desktop is allocated to users when they log on to the portal, and provides the user with the portal themes and framework pages assigned to that portal desktop.

SAP NetWeaver Portal supplies the following framework pages with the default portal installation:

Additional framework pages can be created by making copies of the out-of-the-box framework pages and then customizing them.

Although at design time more than one framework page may be assigned to a user, each user can use only one framework page instance at a time.

Example

The flexible design of framework pages and navigation layouts offers numerous adaptable options for various portal user experiences. For example, thin desktops can support slow dial-up connections. Varying framework pages in a company's portal may enable support of different navigational needs for its employee intranet as opposed to its customer- or guest-based extranet.