Created by: Christopher Nagel on 22-03-2010 07:35:25 PM I have a rather tiny app that is invoked via Subdialog Invoke - it does one thing well. If I add a Hotlink to my Help page and set its DTMF to Inline and value of '*' (no quotes), any input in the initial Form element causes error.semantic! If I set the Form element to "Disable Hotlinks: true", the error is deferred until the next request for input (a 2_Option_Menu). Thereupon, error.semantic is thrown. If I end up disabling hotlinks throughout, I may as well have saved myself the trouble of adding it in the first place. If I remove the hotlink, no errors occur. (NOTE: There is a succesful hotlink of '0'(zero) leading to the help page.) Based on another post here, I added to Root Doc the property "termchar=;". That had zero effect. Perhaps I needed to use 'A' as in the example, but doing so did not change anything. I'd like to include the star key navigation (takes you back to previous RFI), but I'm unwilling to do it manually throughout. I am using CVP 7: Call Studio 7.0(2) and CVP VXML Server 7.2.4. Is there any limitation on Hotlinks in a subdialog? Is there a different semantic construct required to make the star key valid Hotlink input? Thanks, Chris
Subject: Re: New Message from Christopher Nagel in Customer Voice Portal (CVP) - Gen Replied by: Janine Graves on 22-03-2010 07:58:40 PM Christopher, Are you using the DTMF-only gateway adapter? If so, try using \* (back-slash star) and see if the error.semantic goes away.
Cisco Developer Community Forums wrote: > Christopher Nagel has created a new message in the forum "General > Discussion - All Versions": > > -------------------------------------------------------------- > I have a rather tiny app that is invoked via Subdialog Invoke - it > does one thing well. If I add a Hotlink to my Help page and set its > DTMF to Inline and value of '*' (no quotes), any input in the initial > Form element causes error.semantic! >  > If I set the Form element to "Disable Hotlinks: true", the error is > deferred until the next request for input (a 2_Option_Menu). > Thereupon, error.semantic is thrown. If I end up disabling hotlinks > throughout, I may as well have saved myself the trouble of adding it > in the first place. >  > If I remove the hotlink, no errors occur. (NOTE: There is a > succesful hotlink of '0'(zero) leading to the help page.) >  > Based on another post here, I added to Root Doc the property > "termchar=;". That had zero effect. Perhaps I need to use 'A' as > in the example, but I'm not quite sure what else that'll break... >  > I'd like to include the star key navigation (takes you back to > previous RFI), but I'm unwilling to do it manually throughout. >  > I am using CVP 7: Call Studio 7.0(2) and CVP VXML Server 7.2.4. >  > Is there any limitation on Hotlinks in a subdialog? > Is there a different semantic construct required to make the star key > valid Hotlink input? >  > Thanks, > Chris > -- > To respond to this post, please click the following link: > > <http://developer.cisco.com/web/cvp/forums/-/message_boards/message/2060336> > > or simply reply to this email.
Subject: RE: Re: New Message from Christopher Nagel in Customer Voice Portal (CVP) - Replied by: Christopher Nagel on 23-03-2010 04:03:41 PM Sa-WEET!! That did the trick, perfectly. Thank you, Janine! And yes, I'm using the DTMF-only gateway.
Chris
Subject: RE: Re: New Message from Christopher Nagel in Customer Voice Portal (CVP) - Replied by: Janine Graves on 23-03-2010 05:07:22 PM Chris, Glad that the \* solved the problem with the HotLink grammar for DTMF-only gateway. The same would be true if you are trying to collect * using the Form element and the DTMF-only gateway, you'd have to use \*. But, and here's where it gets tricky, if you want to collect * using the N_Option_Menu elements, then you just use '*' and omit the back-slash! Go figure! Janine www.TrainingTheExperts.com
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
