Defining the Maximum Number of Objects Displayed Per Folder 

Use

When users browse the Portal Catalog, a data request is sent to the PCD to collect the information. The higher the number of entries displayed per folder, the more processing the server needs to perform to query the database, and the longer the wait time for the user navigating the Portal Catalog.

This topic describes how you can customize the Portal Catalog to limit the number of items displayed per folder. This setting is designed to enhance portal performance, particularly in cases where Portal Catalog folders have a large number of entries (generally above 100). By reducing this value browsing times in the Portal Catalog can be improved since data is retrieved in limited packets.

If a folder contains more entries than the maximum number allowed per group, Previous and Next buttons are placed at the top and bottom of the displayed group in the selected folder. respectively. To view additional and previous entries in the selected folder, the user must click these buttons.

Unpredictable results may occur if a folder contains more items than the maximum defined display number and the items are displayed by object name (as opposed to object ID only). The portal always retrieves items in a chunk from the PCD according to the alphabetic sequence of their object ID, and not the object name. Thus, for example, in the first chunk the user may see items beginning with an a followed by items beginning with c, d, and then h; however, in the following chunk the user may see more items beginning with aand b. The user may have assumed in the first chunk that all items from a to g were displayed; this is not the case.

 

Procedure

...

       1.      Edit the appropriate iView (see Selecting the iViews to Configure) in the Property Editor (see Property Editor).

       2.      Display the properties in the Advanced category.

       3.      In the Maximum Number of Node Child Items property, enter a value (default is 150).

Do not set this value too high; otherwise, it may have a negative impact on system performance.

       4.      Save the changes you have made and close the editor.

       5.      If needed, perform these steps again in other iViews for other portal editors.