Show TOC

Procedure documentationCreating and Editing a Framework Page Locate this document in the navigation structure

 

To create a framework page, use the same tools as you use to create a regular portal page.

Procedure

  1. To create or edit a framework page, use the Page Editor in the Portal Content Studio.

    For more information, see Page Editing

    Recommendation Recommendation

    To create your own framework page, we strongly recommend to use the Classic Framework Page (see Classic Framework Page) shipped with the portal as a delta link template. This ensures that the new framework page contains all necessary properties, and that future enhancements made to the Classic Framework Page by SAP are subsequently applied to your own framework page after upgrading.

    End of the recommendation.

  2. For the portal runtime to recognize and fully support framework pages, such as underlying navigation-related mechanisms, eventing, and optimal performance, you need to set the Element in Framework Page property in the framework page and in the structural pages that compose it.

    This property is necessary for page objects only. You do not need to set the property in iViews that compose or run in the framework page, such as iViews in the navigation panel and header area.

    You define the Element in Framework Page property described below in the Property Editor. For more information, see Property Editor.

'Element in Framework Page' Property

This property identifies the function of a particular page in relation to the entire framework page. Depending on the function of the page in the framework page, assign one of the following values:

  • Framework Page: Assign this value to the main page designated as the framework page. This is the page that holds the structural components constituting the framework page, and which you eventually combine with portal themes to create portal desktops (see Portal Desktops).

    For example, this value is assigned to the Classic Framework Page object (com.sap.portal.frameworkpage) that is shipped with the portal.

  • Dynamic: Assign this value to the page within the framework page that changes with each navigation event at runtime.

    For example, this value is assigned to the Desktop Innerpage object (com.sap.portal.innerpage) which is part of the Classic Framework Page shipped with the portal.

  • None: Assign this value to regular portal pages that display content in the portal runtime environment.

If instead of creating a framework page or inner page from a delta link template, you create them from scratch based on your own portal components, you must add the following code in the portal component descriptor file of the respective pages to provide the necessary property and values:

Syntax Syntax

  1. <property name="com.sap.portal.framework.phase" value="None">
  2. 	<property name="plainDescription" value="Element in Framework Page"/>
  3. 	<property name="validvalues" value="4/None9/Framework8/Navigate12/Personportal10/Personpage"/>
  4. 	<property name="validValueTitle0" value="None"/>
  5. 		<property name="validValueTitle1" value="Framework Page"/>
  6. 		<property name="validValueTitle2" value="Dynamic"/>
  7. 		<property name="validValueTitle3" value="Personalize Portal"/>
  8. 		<property name="validValueTitle4" value="Personalize Page"/>
  9. 		<property name="category" value="Navigation"/>
  10. 	</property>
End of the code.