Skip to Content

Playing with Portal Roles

There are many properties of the portal object – Roles, where in most of the object properties are neither used nor noticed. This blog is an attempt to understand few properties of Portal Roles using which, some tricky requirements can be solved in a very simple way. By using few of these we can actually change the way the normal portal roles behave.


Scenario 1:  Multiple Roles to be displayed in a single tab.



Normally when many roles are assigned to the user, in the 1st level of Top Navigation a horizontal scroll bar appears so that the user can scroll for the roles that are not displayed initially. Hence, to get rid of this we can group roles inside a master role.


For example if Role M is the master role required to appear in 1st level navigation and Roles A, B & C are the one’s required to appear in the second level navigation, then


Maintain the Role properties as given:


Can be Merged = Yes

Entry Point = Yes

Merge ID = merge_roles (or some common IDs for all the roles)

Merge Priority = 1 to n for (Roles M & A, B, C)


By maintaining these properties in all the roles, we can achieve something like as shown below.




Scenario 2:  Using pictogram for Roles


On click of the master role in the 1st level navigation, we can have the child roles displayed in an overview page using the property pictogram.


In the Master Role M, add the standard service map I View (service Map I View is similar to a site map, displays pictograms, short texts and links representing the entries in a workset)


Change the I View properties as given:


Default Entry to Folder = Yes

Entry Point = Yes


In all the roles, change the role property Pictogram (and select an image from the drop down list). Save & refresh to see the result as shown below.



The same can be done for all the roles in case if roles consist of multiple objects.



Scenario 3: Navigation Zoom configuration


In case of multiple navigation levels, we can display subset of the navigation hierarchy by configuring a role, workset, or a folder in a role or workset, as a navigation zoom. Navigation zoom allows subdividing the portal into a main portal and several subportals. This enables portal users to view specific subject areas of the portal separately from the rest of the portal.


For achieving the same, maintain the Role properties as given:


Navigation Zoom Point = Yes

Navigation Zoom Point = PCD path of Portal Desktop (Optional property, can be given in case of branding requirements such as design, look and feel.)

Navigation Zoom Title = some custom value (Optional property, can be given so that the title appears in the masthead of the navigation zoom)


At runtime, clicking a navigation zoom point replaces the main portal screen with a subset of the navigation hierarchy. The navigation zoom point becomes the root node, and all of the navigation nodes below the navigation zoom point are now arranged in top-level navigation and detailed navigation.

For example on click of Role A, the screen display will be as shown below.



I have tried to outline only few of the properties in this blog. There are even more which can be explored and used to satisfy few tricky requirements and avoid developments as much as possible.

You must be Logged on to comment or reply to a post.
  • Hello Santtoah Raj,
    Nice Blog
    but dint turned usefull to me:-(
    I have four Role named RoleM/A/B/C.
    and have adjusted 4 properties as.
    Can be merged : Yes.
    Entry Point: Yes.
    Merg Id : vinit(all four).
    Merg Peority : 1(for RoleM)
                   2(for RoleA).
                   3(for RoleB).
                   4(for Rolec).
    Saved and Refreshed nothing happened.
    Output:RoleM is appred on Top level navigation beside Content Administration and ity is grayed out and after clicking on it nothing happens.
    please suggest:-(
    Vinit Soni
    • Hi Vinit,
      You need to have some contents in the roles.
      Also check the assigned properties again. Once done, clear the browser & server cache and check. It should work.


      • Hi Santhosh
        I think that merging the entry points will appear as Vinit describes. If you want a two level structure, then each of the top level entries of the roles (M, A, B and C) need to have a common entry point and then the second level folder of each role will appear on the second level of the menu.
        Role M <-entry point, mergeid xxx
        .. Role M level 2

        Role A <- entry point, mergeid xxx
        .. Role A level 2

        Role B <- entry point, mergeid xxx
        .. Role B level 2

  • Hi Santhosh,

    This is really nice blog on properties of the portal object – Roles.
    I was thinking same kind of feature as per my client requirement on role. We used same blog.

    thanks man… & Best of luck…for new-new things.

    Umesh Laxkar

  • Hi Micheal,
    Yes. You are right. Sorry, I have typed ‘not’ by mistake. We need to have the same merge id for all. The one extra thing I have got in my roles is sort priority which is common for all roles as I wanted these roles to be displayed in the last tab.


  • Yes, you are right. The only extra thing I had in my roles were common sort priority as I wanted this group of roles displayed in the last tab.
  • Santhosh,
    Nice Blog. We have a case where we need to switch the framework from Light to Default for some content areas, and are trying to use the Navigation Zoom to acheive that by having the entry point defined as a navigation zoom, and providing the pcd path of the default framework for the folder.

    This works perfectly fine and the Navigation Zoom opens the window with the folder at the top level and the switch to the default framework happenns.

    Now the problem. We have the “Back to portal” link that will take us back to where we came from, and we want to switch back to the light framework when the “Back to Portal” is clicked.

    Is there any means to do this?


  • Hi Santhosh,

    I have created three roles. I have set the following properties for roles. All roles have one page.

    Can be Merged = Yes
    Entry Point = Yes
    Merge ID = hema (common for all roles)
    Merge Priority = 1 for Roles M
                               2 for Roles A
                               3 for Roles B

    In First level it display the Roles M correctly. But I didn’t get the roles in second level. It displays the corresponding pages.

    What may be the problem?

    Hemalatha J

    • Hi Hema,
      Make Entry Points = Yes for the 2nd level roles & also if required u can also have sort priority 1..n. Clear the role cache & try again. It should work.