Plum DEV Documentation
voicexml:tags:exit

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

voicexml:tags:exit [2014/05/29 15:47]
jennifer added meta description
voicexml:tags:exit [2019/09/17 12:29]
Line 1: Line 1:
-{{description>​‹exit› VoiceXML tag details, attributes and VXML code example | exit returns control to the interpreter context that determines what to do next.}} 
-=====<​exit>​===== 
- 
-Returns control to the interpreter context that determines what to do next. 
-====Attributes==== 
-| expr | A return expression (e.g., "​0"​ or "'​oops!'"​). | 
-| namelist | Variable names to be returned to interpreter context. The default is to return no variables; this means the interpreter context will receive an empty ECMAScript object. | 
- 
-====Notes==== 
- 
-The interpreter context is the VoiceXML core. Plum DEV, upon reaching an <​exit>​ tag, will simply discard the variables returned to it and disconnect. Unlike the <​disconnect>​ tag, no event is thrown when an <​exit>​ tag is encountered and the call is immediately terminated. 
- 
-====Example==== 
-<​code>​ 
-<?xml version="​1.0"?>​ 
-<vxml version="​2.0">​ 
-  <​form>​ 
-    <​block>​ 
-      <​prompt>​ 
-        You will hear this text. 
-      </​prompt>​ 
-      <​exit/>​ 
-      <​prompt>​ 
-        You will never hear this text. 
-      </​prompt>​ 
-    </​block>​ 
-  </​form>​ 
-</​vxml>​ 
-</​code>​ 
-The output of the above script would be: 
- 
-Computer: You will hear this text. 
- 
- 
-====Child Tags==== 
- 
-None 
- 
- 
-====Parent Tags==== 
- 
-[[voicexml:​tags:​block|<​block>​]],​ [[voicexml:​tags:​catch|<​catch>​]],​ [[voicexml:​tags:​error|<​error>​]],​ [[voicexml:​tags:​foreach|<​foreach>​]],​ [[voicexml:​tags:​filled|<​filled>​]],​ [[voicexml:​tags:​help|<​help>​]],​ [[voicexml:​tags:​if|<​if>​]],​ [[voicexml:​tags:​noinput|<​noinput>​]],​ [[voicexml:​tags:​nomatch|<​nomatch>​]] 
-