Siebel Developer's Reference > Siebel Web Engine Tags >

swe:nav-control

In version 7.7 and higher, in High Interactivity views this tag implements the screenbar used for first-level navigation, the picklist used for second-level navigation, and the detail view list used for third-level navigation.

Usage

• First-level navigation: <swe:nav-control type="Screen With Category" style="Tab" indentWidth="nn"/>
• Second-level navigation: <swe:nav-control type="Category View" style="Select"/>
• Third-level navigation: <swe:nav-control type="xxx" style="Tab" indentWidth="nn" anchorTab="Enabled|Disabled"/>

Attributes

type, style. Supported values and combinations of the type and style attributes for the tag are summarized in Table 25.

indentWidth. Number of pixels to indent the row of tabs. Used for screen and detail view tabs.

anchorTab. Used to enable or disable smart view anchoring.

In Oracle's Siebel Business Applications before version 7.5.3.6, when a user action or navigation causes the current view to refresh or a new view to appear, by default the result is anchored at the top of the page. This behavior might disorient users in some common scenarios, for example when clicking a view tab to navigate to a new view, expecting to see detail information (such as Attachments) in the bottom part of the target view. The problem is exacerbated when the user is working on the lower part of a view whose parent applet consumes more than a full window height. In these cases, the user must scroll to see the detail portion of the view.

Starting in version 7.5.3.6 High Interactivity (HI) applications, the smart view anchoring feature solves these types of problems by anchoring and adjusting the scroll position for views following common user actions that cause a view to change or refresh. In general, this behavior is as follows: when a user initiates an action (such as clicking a view tab or the More/Less button), the position of the control (tab or button) used to initiate that action does not change.

In version 7.5.3.6 and later, view anchoring is enabled by default. It is possible to disable the behavior for third- and fourth-level view navigation (those initiated by view tabs) if so desired for a view or set of views. This is done by setting the anchorTab property in the SWE template for the view or set of views to Disabled.

First-Level Navigation Example

The following example is used in the CCScreenbar_Tabs.swt template:

<swe:if condition="Web Engine State Properties, IsHighInteractive">

<swe:switch>

<swe:case condition="Web Engine State Properties, IsHtmlMarkup">

<swe:nav-control type="Screen With Category" style="Tab" indentWidth="8"/>

</swe:case>

...

</swe:switch>

</swe:if>

Second-Level Navigation Example

The following example is used in the CCFormButtonsTop.swt template:

<swe:if-var name="Parent">

<swe:if condition="Web Engine State Properties, IsHighInteractive">

<swe:switch>

<swe:case condition="Web Engine State Properties, IsViewPosition, 'Position:2'">

<td><img src="images/spacer.gif" width="1" height="1"></td>

<td class="AppletTitle" nowrap>

<swe:nav-control type="Category View" style="Select"/>

</td>

</swe:case>

...

</swe:switch>

</swe:if>

</swe:if-var>

Third-Level Navigation Example

The following example is used in the CCViewbar_Tabs_DropList.swt template:

<swe:if condition="Web Engine State Properties, IsHighInteractive">

<swe:switch>

<swe:case condition="Web Engine State Properties, IsHtmlMarkup">

<swe:switch>

<swe:case condition="Web Engine State Properties, IsViewPosition, 'Position:3'">

<table class="tier3Back" width="100%" align="center" cellpadding="0" cellspacing="0" border="0"><tr valign="top"><td><img src="images/spacer.gif" width="1" height="3"></td></tr></table>

<swe:nav-control type="Detail Category With View" style="Tab" indentWidth="30" anchorTab="Enabled"/>

</swe:case>

</swe:switch>

</swe:case>

</swe:switch>

...

</swe:if>