Framework Page Properties 
For the portal to provide full support for framework pages in the runtime environment, such as underlying navigation-related mechanisms, eventing, and optimal performance, you need to set certain properties in the framework page and in its structural pages.
These properties are necessary for page objects only. You do not need to set them in iViews that compose or run in the framework page, such as iViews in the navigation panel and header area.
You define the properties described below in the Property Editor. For more information, see Property Editor.
Property Name |
Description |
Element in Framework Page |
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 Default Framework Page object (com.sap.portals.frameworkpage) that is shipped with the portal. See Default Framework Page. · Dynamic: Assign this value to the page within the framework page which 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 default framework page shipped with the portal. · None: Assign this value to regular portal pages that display content in the portal runtime environment.
If you create a new framework page or inner page, it is strongly recommended to use the default framework page or inner page, shipped with the portal’s initial content, as delta link templates. This will ensure that all necessary properties are available and that future enhancements made to the default framework page or inner page by SAP are also applied to your framework page or inner page (through delta link inheritance) after you upgrade the portal’s initial content. If you do however create a framework page or inner page from scratch based on your own portal components, you must add the following code in the portal component descriptor file of the respective pages in order to provide the necessary property and values: <property name="com.sap.portal.framework.phase" value="None"> <property name="plainDescription" value="Element in Framework Page"/> <property name="validvalues" value="4/None9/Framework8/Navigate12/Personportal10/Personpage"/> <property name="validValueTitle0" value="None"/> <property name="validValueTitle1" value="Framework Page"/> <property name="validValueTitle2" value="Dynamic"/> <property name="validValueTitle3" value="Personalize Portal"/> <property name="validValueTitle4" value="Personalize Page"/> <property name="category" value="Navigation"/> </property> |
