Bookshelf Home | Contents | Index | Search | PDF

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

Second and Third Navigational Level: Visibility Picklist and Detail Tab View Bar

---

Views are grouped into context Views (second level navigation: the Visibility picklist) and non-context Views (third level navigation: the detail View bar). You should choose an initial View that establishes business object and visibility context before drilling down into related Views. The visibility setting that has been established by choosing the context View in the Visibility picklist is maintained during subsequent navigation among the non-context Views available in the detail view bar.

Visibility (specifically in this case, record access visibility) refers to the user's access rights to see particular records of particular business components, as determined from the user's logon and other information maintained by an administrator. For more information on visibility, see Security Guide for Siebel eBusiness Applications.

The set of context Views for a selected Screen is established based on the following rules:

When all Views assigned to the Screen (through Screen View object definitions) belong to the same business object, the context Views are the set of Views in the Screen that have visibility rules (like "My Accounts", "All Contacts," and so on). The remaining Views that do not have visibility rules are grouped as non-context views (like "Account-Contacts", "Charts," and so on).
When some of the Views assigned to the Screen belong to different business objects, the entire set of Views in the Screen are grouped as context Views, and appear in the Visibility picklist. Such Screens do not have any non-context Views, and so the detail View bar is empty. An example is the Administration screen.

The segregation of Views into context and non-context views for the Accounts screen is illustrated in Figure 224.

Figure 224. Context and Non-Context Views

Notice that View categories appear with non-context Views in the detail View bar. View categories are described in Fourth Navigational Level: Subcategory Views.

Context views are automatically segregated from non-context views based on the Business Object and Visibility Applet/Visibility Applet Type properties in each View object definition. The only configuration in Tools required to implement second- and third- level View navigation in a Screen is the assignment of views to that screen using Screen View object definitions. You should avoid using views from different business objects in the same Screen.

The Visibility picklist appears in the "view bar" frame (see the CCPageContainer.swt and CCFrameViewbar.swt templates). The Visibility picklist is implemented as a <swe:viewbar> tag with a Type setting of Select and a Mode setting of Context:

<swe:form>

<td nowrap>

<swe:viewbar type="Select" mode="Context">

<swe:this property="FormattedHtml"/>

</swe:viewbar>

</td>

</swe:form>

The detail View bar is also implemented by means of a <swe:viewbar> tag, but with different attribute settings. Specifically, the Type attribute is omitted, and the Mode attribute has a value of NonContext instead of Context. This creates a horizontal View bar consisting of tabs populated with the display names of all the non-context Views instead of a picklist control populated with the display names of the context Views. The template logic for rendering the detail View bar is as follows (see CCViewbar_Tabs.swt):

<swe:viewbar mode="NonContext">

<swe:viewlink state="Active" property="FormattedHtml" >

<td><img src="images/nav/tabon_arrw.gif" align="absmiddle"
width="6" height="19" border="0" alt="alt=""/></td>

<td class='tier3OnLabel' background="images/nav/tabon_back.gif">
<nobr>&nbsp;<swe:viewname/>&nbsp;</nobr></td>

<td><img src="images/nav/tabon_rightcap.gif"
align="absmiddle"
width="6" height="19" border="0" alt="alt="" /></td>

</swe:viewlink>

<swe:viewlink state="Inactive" property="FormattedHtml" >

<td class='tier3Off'><nobr>&nbsp;<swe:viewname/>&nbsp;
<img src="images/nav/tab_rightcap.gif" align="absmiddle"
width="6" height="19" border="0" alt="alt=""/></nobr></td>

</swe:viewlink>

</swe:viewbar>

The detail View bar implementation of the <swe:viewbar> tag requires the use of the child tags <swe:viewlink> and <swe:viewname>. The Visibility picklist implementation omits these child tags.

The syntax of the <swe:viewbar> tag appears below:

<swe:viewbar>

Usage: <swe:viewbar type="xxx" mode="yyy" property="zzz">

Attributes:

Type. This can have one value which is "Select". If the type is set to "Select," the view bar is rendered as a HTML select control showing the set of available views (context, non-context or both, depending on the Mode setting). The user navigates to the selected view after making this choice of control.
Mode. The mode can have two values: Context and NonContext. If the value is Context only the context based views will be shown. If the value is NonContext, only the non-context views are shown.
Property. This attribute should be used only when the type is set to Select. This attribute can have a value of FormattedHtml, in which case the HTML select control is rendered.
<swe:viewlink>

Purpose:

Outputs a link to navigate to the view.

Attributes:

State. This is optional. Can have values "Active" or "Inactive." If state is "Active," this tag will be used only if the current view name being rendered is the currently active view. If state is "Inactive," this tag will be used only if the current view name being rendered is not the currently active view. If not specified, the tag will be shown for all views.
Property. This is optional. Can have only one value, "FormattedHtml," which will output the HTML for creating a link to navigate to the view. If this attribute is not specified, then no output will be generated.
htmlAttr. This is optional. Can be used to add additional HTML attributes to the generated HTML tag.

NOTE:  The swe:viewlink tag can be used without specifying the property attribute, but with a value for the state attribute to show conditionally different HTML for active and inactive views. When the property attribute is not specified, the property can be displayed within the body of the swe:viewlink tag using the swe:this tag.

<swe:viewname>

Purpose: Outputs the name of the view.

Bookshelf Home | Contents | Index | Search | PDF