Show TOC

Function documentationPage Editing Locate this document in the navigation structure

 

You edit pages that appear in the Portal Catalog to customize them for specific users and roles in the organization. The editing is done using the Page Editor, a tool that lets you populate pages with content and perform various operations relating to both the page and the content it contains.

Prerequisites

  • You have at least one page stored in the Portal Content Directory and displayed in the Portal Catalog.

  • The page you want to edit is not locked for editing by another user.

  • You have write permissions for the page that you want to edit.

  • You have write permissions for the content you want to add.

  • You are familiar with the Isolation Method of iViews.

  • You are familiar with iView caching.

Note Note

If a page is locked, you can open it in read-only mode. You can then keep testing whether the page is still locked by clicking the Edit Mode button.

  • For information about the locking feature, see Object Locking.

  • For information about the Edit Mode button in the Page Editor, see Editing an Object   Procedures   Editing Objects and Folders Listed in the Portal Catalog   Object Locking and Read-only/Edit Mode  .

End of the note.

Features

Page editing includes:

  • Setting page property values.

    Page properties are determined by the template on which you base the page and cannot be deleted. You can only edit the property values and attributes. Page properties that relate to specific issues are discussed within their respective topics.

    For more information, see Defining Property Values.

  • Adding Content to a Page

    • While creating Web Dynpro iViews, you are directed by the iView Wizard to the Web Dynpro Page Wizard to create a Web Dynpro page to which these iViews are automatically added.

      These same iViews are also displayed as separate delta link iViews in the Portal Catalog, allowing you to add them to other pages.

      Caution Caution

      Mixing Web Dynpro iViews and portal pages, and vice versa, generates a warning message concerning the isolation mode of the iViews. For more information, see Isolation Method of iViews.

      End of the caution.

    • Content that you add to a page is automatically displayed in the page content list. Each object displays its name, ID, and source type.

    • You can add content while working in either Page Content or Page Layout mode.

    • When you add an object, it is automatically assigned to the first available container on the page. The order of availability is dependent on the order of the containers as they are defined in the Property File list.

    • It is possible to add the same iView more than once to a page by repeating the Add iView to Page operation. The system generates a new ID, in ascending order, for each addition (<ID>, <ID_0>, <ID_1>, and so on). All other properties remain identical.

  • Editing Content and Layout

    • You can edit object properties in either Page Content or Page Layout mode.

    • You determine how much personalization an end user can perform on a given page and its content.

  • Working on Multiple Pages

    With each page that you open you create a tab in the editing area of the Portal Content Studio. You can toggle between the tabs, performing editing operations on each page.

After creating and editing a page and its properties, you can perform various related activities that enhance the usability of the page and its content.

  • Add iViews as Related Links

    You can create a list of links that represent subjects related to a given iView or page. The links can be other iViews and pages.

  • Assign iViews/pages as dynamic navigation iViews

    These are context-sensitive iViews that appear in the portal navigation panel and enable further data navigation into the content displayed in the content area.

  • Assign page permissions through the Permission Editor

    You can assign permissions to any entity that appears in the Portal Catalog, such as roles, worksets, folders, or pages. Child objects (iViews) inherit permissions from their page.

  • Assign dynamic role-based iViews deriving from business scenarios; see Object Based Navigation.

  • Adding Content Objects to Roles and Worksets

You perform all the above operations by using:

  • The function buttons associated with the Page Editor

  • The function buttons of the content area

  • The various related editors that you access from the drop-down Display list.