Framework Pages 

Definition

A portal page object containing 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, which comprise a portal desktop (for details, see 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). This page does not contain a header area.

An organization may generate more than one framework page for their portal users, each one customized to suit a different user environment, browsing scenario, or role (see Creating a Framework Page).

Framework pages are assigned to portal users through portal desktop objects (see Portal Desktops). A portal desktop object combines any number of framework pages and portal themes. The assignment of a portal desktop to users, groups, or roles is enabled by means of a portal display rule (see Portal Display Rules). A portal display rule determines which default portal desktop is allocated to a user when he or she logs on to the portal, and hence provides the user with the portal themes and framework pages assigned to that portal desktop.

§         SAP NetWeaver Portal supplies a single framework page and a headerless framework page with the default portal installation (see Default Framework Page). Additional framework pages can be created by making copies of the default framework and then customizing them. The headerless default framework page cannot be copied. 

§         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 support different navigational needs for its employee intranet as opposed to its customer- or guest-based extranet.

Customized desktops offer flexible user experiences