- From: David Wright <David.Wright@OntarioSystems.com>
- Date: Wed, 21 May 2014 14:56:32 -0400
- To: "www-voice@w3.org" <www-voice@w3.org>
- Message-ID: <DB612857EA0A4A4798F20CAE2CA211491BFFE5AB7D@munexch.ontariosystems.com>
The <subdialog> feature of VXML 2.1 is a great improvement over just <goto> call flow. However, I have never found a benefit to having a fresh variable context when calling a form via <subdialog>. Other users may rely on this, so I recommend an alternate behavior based on a new attribute or a new tag. This alternate behavior would allow the form that is called via <subdialog> to execute in the same application context as the caller. In order to get around this, I currently pass all of my variables to forms that are called by <subdialog> as javascript objects with lots of properties. And I have to pass them with temporary names and assign them back to their real names immediately inside the form I'm calling. <var name="sessionArgs"> <subdialog name="sub_verifyIntro" src="#s102_Verification1"> <param name="tempSessionArgs" expr="sessionArgs"/> <filled> <!-- do something --> </filled> </subdialog> <form id="s102_Verification1"> <var name="tempSessionArgs"/> <block> <assign name="sessionArgs" expr="tempSessionArgs"/> </block> ... </form> David Wright, OFS Senior Software Engineer Ontario Systems, LLC 765-751-7233 Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.
Received on Friday, 23 May 2014 06:50:58 UTC