SubDialog variables and properties

[agfa]

Hi

I am using some sub-dialogs to allow me to run the same code multiple times.

I noticed that document scope variables get reset when transitioning to a sub-dialog; these have to be passed as parameters to the sub-dialog. This I have done and they now contain the values I expect.

However, I have now noticed that Plum properties (such as voicename, timeout, interdigittimeout, etc.) don't seem to work properly in subdialogs. I have a global application page which runs at the start of each vxml page, this also sets some Plum properties. For some reason, they seem to get ignored or lose their values.

E.g.
Given this fragment of a subdialog:

<form id="select_patient">
<var name="index"/>
<var name="arrPatients"/>
<var name="answer"/>

<block>
<prompt bargein="false">
<audio src="patient_lastname.wav">
The patient's name is:
</audio>
<audio>
<say-as type="acronym">
<value expr="arrPatients[index]"/>
</say-as>
</audio>
</prompt>
</block>
etc.


The property 'voicename' is set to be 'mike'. However in this subdialog, the first audio sample plays in the female voice, the second plays as 'mike'. Timeout properties do not work.

I was wondering if anyone had any ideas on what is happening here, and what we can do to solve it.

Regards

Justin.

[support]

Hello,

Could you please provide a more complete and concise IVR example, it's possible that there is some problem with your IVR code. However, there are some IVR issues with how the IVR property "voicename" works and we are working to correct those. In the mean time it is best to continue to use the <voice> tag within the audio tag (as defined in the VoiceXML 2.0 specification) to guarantee TTS behavior. There is currently no time line for the resolution to this IVR issue.

Regards,
Plum Support

[agfa]

Thanks for the reply.

Actually I think we figured it out

The 'voicename' property does work, but only if 'all' <audio> tags are individually enclosed inside their own <prompt> tag.
The example given below works:

<prompt bargein="false">
<audio src="patient_lastname.wav">
The patient's name is:
</audio>
</prompt>

<prompt bargein="false">
<audio>
<value expr="arrPatients[index]"/>
</audio>
</prompt>

The earlier example did not because both audio tags were not enclosed in prompts.

We discovered that the timeout settings do work, we just had to understand how the timeout, noinputtimeout and property assignments worked.

Perhaps that helps somebody else too.