Janine Graves | Hi,
I'm going to teach at Nationwide in a few weeks and they are using Audium flagship on GVP (as you probably already know).
One of the things they'd like me to address in class is best practices for creating reusable code that includes collecting caller information (like credit card collection).
Can you please tell me what AUDIUM recommends as best practices for creating this sort of reusable code? For a credit card collection that might take a few separate Vxml pages plus some DB interaction on the back end, could one accomplish this best using Element Groups? Or by creating one voice element that invokes a couple of Audium voice elements (like the New Digit with Confirm example that I have), or would you recommend someone write a voice element from scratch?
I usually try to steer students away from creating their own voice elements, since most everything can be done with a FORM element plus a few other action or decision elements. Also, because I find voice elements very difficult to write, much less to explain to a beginner.
Customer would like to know best practices to follow to make future upgrades as painless as possible. Is there anything they should keep in mind regarding this?
Customer will be using the GVP Adapter, and I'm wondering if there are any special elements that the adapter provides that I need to know about before I get there for the training.
THANKS! Janine |