Monthly Archives: February 2014

{uccx scripting tips & tricks: generating prompts}

Today we are going to do away with the Create Generated Prompt Step, because it really isn’t needed and in my opinion it obfuscates the development process..and toward the end of this post I will show you an example of a Prompt I had to create for a customer because the Speed of the Playback Message was too fast for them; in this real-world example it is required that you have, at a minimum, an Enhanced License for CCX.

What types of Prompts can you “Generate” without the Create Gen Prompt Step? Well ALL of them: Number Prompts (N[], such as in a year where the playback is like the following: Two-thousand and fourteen), Spellings (S[], this is typically how we playback a “number” from a Get Digit String Step), Dates (P[]+date), Currency ($[]), and it goes without saying (pun intended 🙂 a Delay Prompt (DP[]which produces silence).
Continue reading

{UCCX Practice Standards: Variable Naming Conventions}

Very quickly, we are going to discuss Variable Naming. For just a second, let’s consider ourselves Applications Developers/Software Engineers..and not just measily “script kiddies” as the name of our IDE (integrated development environment) suggests (CCX Script Editor); because in fact that is what we are when we start creating variables, condition statements, and any other type functions (such as Get Digit String, Play Prompt, et al) in the Development of our IVR, AA, and/or ACD Applications (ok scripts I suppose). We won’t open any {Curly Braces} today, but we will get in a DevOps state of mind…
Continue reading

{uccx scripting: what’s in a session variable}

Have you ever used a Session Variable? If you’ve gone to the CCX Advanced Scripting Course you probably did in the Scripts you used in the Lab. But did you get much utility out of them? I suppose we did in that class (depending on the instructor and my instructor, Elizabeth, was good at explaining these). Did you understand them? Hopefully I can clear the mud away and make these crystal clear. But first lets talk about Java and Memory really fast.

If you’ve worked with CCX long enough you might have seen Heap Errors either mentioned on the Cisco Support Forums (glad that didn’t happen to me!) and or in our own MIVR logs in which case we are sweating bullets in order to fix issues!.! There have been known bugs that affect the Heap where the Objects (variables), in our CCX Applications, aren’t set for garbage collection when they are null (and/or “terminated”). Garbage Collection? I take offense to data is not garbage! Nonetheless, the top end amount of memory our objects in memory can consume is 256mb and this is Heap Memory! Heap Memory comes from Java’s memory management methodology. So imagine if there is a Memory Leak in CCX surrounding the Heap..Applications crash and the Call Center turns to complete bedlam..
Continue reading