Siebel Tools Reference > Physical User Interface Layer > Navigational Constructs >

Fourth Navigational Level: Subcategory Views

The fourth navigational level is the Subcategory View picklist inside the detail applet, just beneath the row of third-level view tabs. It allows the user to choose a View from the category represented by the selected detail View bar tab, when the View bar tab is for a category rather than an individual View. This is shown in Figure 225.

NOTE:  The Applet Toggle picklist, which, if present, is inside the applet just beneath the Subcategory View picklist, is not the same as the Subcategory View picklist. The Subcategory View picklist is for View navigation; the Applet Toggle picklist is for selection of an applet within the detail portion of the view. For more information on applet toggles, refer to Toggle Applets.

Categories are groupings of Views within a Screen. If Views are grouped into categories within a Screen, the category names for these Views are rendered in the detail View bar instead of the individual Views, requiring the user to drill down through the subcategory picklist to access the categorized Views. Uncategorized Views appear directly in the detail View bar. For example, in the Accounts screen there is a set of views under the Charts category (including Account Analysis By Rep, State Analysis and Territory Analysis). A detail tab (third navigational level) would be defined for Charts, and when the user clicked on this tab, the Current View picklist (fourth navigational level) would be populated with the names of these three views.

The hierarchy of screens, categories, and categorized views (first level, third level, and fourth level, in this case) is illustrated in Figure 225.

Figure 225. Hierarchy of Levels

Click for full size image

Any of the non-context Views in a Screen can be categorized (categories are ignored if specified for context Views). Specification of a category involves the use of the Category property in the Screen View object definition for each View to be included in a category. For example, the Account Analysis By Rep, State Analysis, and Territory Analysis views in the Accounts screen are given a Category value of "Charts." The Category value needs to be identical in spelling and capitalization among the Views being categorized together in the Screen, or multiple (slightly different) categories will result.

Screen View object definitions with a non-blank Category property result in their corresponding View names being accessible only from the subcategory picklist. A View bar tab is rendered for the category name instead of the names of the individual Views.

A subcategory View picklist is implemented using a <swe:subviewbar> tag. The <swe:subviewbar> tag can alternately be configured to display a second horizontal tab bar beneath the detail View bar, but the picklist is the preferable approach. It can either be a dropdown picklist or a set of tabs, depending on attribute settings in the tag. The actual placement of it depends where the <swe:subviewbar> tag is placed in the template.

The default behavior of the <swe:viewbar> tag, if the <swe:subviewbar> tag is not present, is to display the default View for that category when the user selects the category name in the detail View bar. The default View is the View with the lowest sequence number in that category that is visible to the user.

By including the <swe:subviewbar> tag, this behavior is augmented with a picklist or subcategory tab bar that conditionally appears when the currently active View belongs to a category. This tag expands to list all the Views that belong to the selected category. If the currently active View does not belong to a category, then this tag does not render anything on the page. Thus, if the user chooses a category name from the detail View bar (which means the default View within that category is now the active View), the subcategory picklist or tab bar is rendered in that default View if this tag is present. If the user chooses a non-category View from the detail View bar, the subview bar tag does not render anything on the resulting page.

The <swe:subviewbar> tag usage is described as follows:

When the Type attribute is not set to Select, <swe:viewlink> and <swe:viewname> tags are used within the body of the <swe:subviewbar> tag. The behavior of these tags is similar to their use inside of a <swe:viewbar> tag.

Examples of Use:


 Siebel Tools Reference, Version 7.5, Rev. A 
 Published: 18 April 2003