Stand-Alone Buttons

In a WTE application, a stand-alone button is useful for presenting a Boolean-type menu that the caller can either click or skip. You create a stand-alone button either by using the BUTTON element, or by using the INPUT TYPE=button element outside a FORM element.

To introduce a stand-alone button to the caller, precede the BUTTON or INPUT element with text or a voice file, include a voice file or cues on the BUTTON or INPUT element itself, or use the LABEL element.

The following example shows a stand-alone button that is introduced by the cue-before and cue-after style properties on the BUTTON element:

<BUTTON STYLE = "cue-before: 'For'; cue-after: 'Press 5, To Skip press 7'" OnClick="Function1()">Books</BUTTON> 

The WTE renders a stand-alone button similarly to the way it renders other menus. If the BUTTON or INPUT element has a voice file or any cues associated with it, the WTE plays the voice file and cues and then waits for the caller to respond.

The WTEApplication object has two pairs of properties that specify the ways that the caller can click or skip a stand-alone button. The ClickButtonKey property specifies the DTMF key that the caller must press to click a button, and the SkipButtonKey property specifies the DTMF key for skipping a button.

When SR is enabled, the ClickButtonPhrases property specifies a set of words and phrases that the caller can speak in order to click a button. Similarly, the SkipButtonPhrases property specifies the words and phrases for skipping a button.

You can use the %1 and %2 notation in the VOICEFILE attribute and cue properties of a button to refer to the click and skip keys. For more information, see Using the %1 and %2 Notation.