Show TOC

Procedure documentationCreating a Service Map iView Locate this document in the navigation structure

Procedure

  1. Create an iView based on the service map template:

    1. Launch the Portal Content Studio. In top-level navigation, choose   Content Administration   Portal Content  .

    2. In the Portal Catalog, right-click a folder and choose   New   iView  .

    3. In the iView Wizard Template Selection screen, select Service Map iView.

    For information about accessing and using the iView Wizard, see Launching the iView Wizard and General Information.

  2. In the iView's Property Editor, set the Relative Workset Location property to define the location of the parent folder of all the services, relative to the service map iView.

    There are two possible attributes to which you may need to assign a value:

    • levelsup=n

    • pathlist=ID1; ID2; and so on

    For example, the value levelsup=1 means that the service is one level up from the iView, or the parent of the service map.

    If a Service Map iView overviews a service that is not its parent, and is several nodes away, you need to give the complete path from the service to the Service Map iView by listing the ID of each node in the path.

  3. You can specify whether you want portal users to be able to navigate to service map items by clicking on service map pictograms. In the iView's Property Editor, in the Navigation property category, set the Pictogram is Clickable property.

  4. For each item in the service, configure the following properties in the Property Editor:

    • Pictogram: From the list, select the name of an image to represent the service entry. You will see only the pictograms that relate to items on level 1.

    • iView Name: This name was set when the object was created.

    • Description: If this value was not entered when the object was created, then write a description of the entry now, or if necessary, edit what was written. This value can be edited at any time.

  5. Add the Service Map iView to your navigation hierarchy. For information, see Adding Content Objects to Roles and Worksets.