This document was generated from CDN thread
Created by: Christopher Nagel on 31-03-2010 04:08:16 PM
I come to CVP VXML from an OO (NeXT) background, and I'm used to focusing on reusability in infrastructural ways. It takes a while to get there, and I am by no means saying I'm there, but I wanted to talk about a few things I'm seeing and maybe generate some new ideas on it.
Here are a couple things that I think all IVRs should have:
- context-sensitive help
- * takes you back to previous menu / request-for-input
The only way I know to implement either of these is:
1. keep session variables updated (manually by the call flow designer) in the Data tab of appropriate elements.
2. send no-input, no-match, and PressZeroHotlink to the same Help page and use a decision element to choose the prompt
3. use another decision and page connectors to get back to the previous spot
4. for PressedStarHotlink, the mechanism is pretty much the same except no intervening prompts
It would be really nice if there were a way to "subclass" a vxml app and not have to do it all manually in each application. Even better if there were some server class I could write to track context and play standard files like no-input-help.wav, then redirect flow back to context.
To that end, I have a default app shell, but again, it's a lot of manual labor. I guess I'm trying to get to VXY 2.0... :-)
Any thoughts? What does your team do to promote quality and consistency? How do you raise the standards?
Thanks!
Chris
Subject: RE: Reusability in call flows?
Replied by: Tieying Xuan on 02-04-2010 09:15:11 AM
Append other 2 ways,
5. Local Hot Link prompt
6. Invoke another app by Sub Dialog
