Imagine the scenario

1. DTMF/Speech element (can't have terminating character)
2. Caller presses zero/hash in stead
3. Global hotlnk activated
4. Write to log / update a variable
5. Return back ack to original DTMF/Speech Element
6. 60 possible DTMF/Speech entry elements
7. Achievable in VXML

So Audium

How can we route back to the correct DTMF/Speech Element from an activated hotlink. Usually reprompt would do this when in a VXML Link.

Hi Karl,

We have a Knowledge Base article that describes how to jump to a specific element at runtime. The article gives an example of how a user can return to the last element visited from a Hotlink element. The article is available at: How can I jump to a specific element at runtime (i.e. goto)?

With that said, we understand that this solution might be cumbersome for large applications. We have a enhancement request in our internal issue-tracking system with an ID of CSCzc10311 for adding a <goto>-type element that would let you jump to any element in the call flow by name. Please note that we have added a note to this enhancement request describing your specific needs. Please refer to that ID in the future to check the status of this request.

Hope this helps,
Harish

Hi Karl,

Since you have raised several different points, please see the reply to each inline below:

[quote:ad77436f1d]
audium.session.last_input_element
audium.session.last_prompt_element
audium.session.last_nomatch_noinput_event
audium.session.last_event_counter

Etc
[/quote:ad77436f1d]

It is possible to access the element history in Studio via substitution under the "Caller Activity" tab. Using substitution, it is possible to access the Nth-visited element. Please note that the Nth-visited element cannot currently retrieve the previous element's name.

It is also possible to access the list of previously visited elements by using the Audium Java API. Here is a link to a knowledge base article that describes how to achieve this:
How to access a list of previously visited elements

We understand that the Java API solution might not be suitable for everyone. Therefore, in order to have this data accessible from Studio, we have entered this enhancement request in our internal issue-tracking system with an ID of CSCsh84174. Please refer to this ID in the future to check the status of this request.

[quote:ad77436f1d]
1. Connectors should be parameterised
[/quote:ad77436f1d]

We have this enhancement request in our internal issue-tracking system with an ID of CSCsh78317. Please refer to this ID in the future to check the status of this request.

[quote:ad77436f1d]
2. Connectors should know the last page they came and have ability to return back to the next step after the call out.
[/quote:ad77436f1d]

This enhancement request also exists in our internal issue-tracking system with an ID of CSCsh71368. Please refer to this ID to check the status of this request.

Regards,
Harish

Hi Karl,

Thanks for your feedback! Constructive suggestions for improvements to our software are truly appreciated!

The ability to increase menu options within the same element is not currently supported in the XOptionMenu elements. However, it is possible to achieve the same functionality by using a Form element, followed by a Decision element. The Form element can be configured to listen for each of the options, and the Decision element can examine which option was chosen and exit accordingly. When this is done, new options can be added fairly easily by expanding the Form element grammar and adding new exit states to the Decision element.

As the Decision element has configurable exit states, the Form+Decision approach provides better call flow visibility than an approach using just an XOptionMenu element. So instead of exit states that are named 'option-1', 'option-2' and so on, you would get more meaningful exit state names such as 'news' and 'weather' in the call flow.

Hope this helps with what you are looking for.
Rachel

Hi Karl,

We sincerely appreciate the suggestions and feedbacks that you have provided. It is great that you are able to share your real-world experiences with us.

We have added the "XOptionMenu" enhancement request into our internal issue-tracking system. We have added your specific feedback to that request. Please refer to ID CSCsh98778 for status of this feature.

Regards,
Cheng