Thanks for going on this Date with me. If you have any comments after reading this..PLEASE send them my way..I really want to open up discussions on things we do in the field as IP IVR, Call Center Designers/Developers/Engineers..
This particular post won’t cover everything..especially considering its our first “Date”..I do have to String you along..hoping to leave you at the end of each post wanting more..The Date and Calendar Classes are part of the Standard Java Library in the java.utils package; if you look at the Date Class most of the Variables and Methods have become deprecated to mainly functions of the Calendar Class. In most of the CCX Scripts I’ve seen, most folks use the “Date” Class Cisco essentially “extends” from the Java Date Class; I will cover some of the syntax Cisco uses (you should know the syntax D[now]) but my sole focus won’t be on it..if you want to get fancy (I say that loosely because some business cases require you to perform fancy tasks on the Date period.) with Dates you won’t be using the Cisco Date Class (you can..but I’m not going to go there often; I want you to be able to do this as a Java developer).
I had to convince myself to pull the trigger on this post..I know it’s not that big of a deal..I’m just overly self-conscious; blogging has a way of potentially exposing weakness; letting others in on these types of things is extremely personal to me..but without further ado and hopefully not too many “tee-offs”..let’s get started..
What tools do you use to help you when developing applications for CCX? Just like the script editor tool helps the voice engineer create more useful and functional IVRs and Call Center functionality for their clientele; we can also use tools outside of the one Cisco provides to get a bigger bang for the buck. The CCX Script Editor has plenty of built-in “elements”/Java Beans within the application to perform most all useful functions within our applications:
This is a post that I will enjoy because we have to deal with the String data type so frequently in CCX Apps and this should be a very useful set of posts once it is all said(written) and done..I almost wish I could Sticky this post at the very top of the blog so it is always there to reference..it makes it that much more useful when you know how to precisely operate on Strings. A String is an interesting Java Data Type in that it is considered a Primitive as well as an Object.
Oh wait, I’ve never talked about Primitives! Primitivies are: int, byte, boolean, double, float, long, short, char, and String. These data types (by themselves) aren’t Java Objects (read Class..OOP), so they don’t have direct METHODS to use on them in order to get a more granular functionality out of them. (Just FYI, there is a Java Integer (capital I) Class (as well as the others) that has methods..we will use one for String Operations (that converts a String to an Integer or Float or Double or BigDecimal et al).)
Java Primitive data types (variables) are created like such:
int counter = 10;
boolean bool = true;
float flot = 3.1215;
String str = "My String";
For Object Creation you instantiate a new Object like such:
String str = new String("My String");
Posted in UCCX
Tagged DevOps, UCCX
Just wanted to write a quick post to go over some future posts that will be coming down the pipeline soon.
Variable Naming Best Practices: A guy at work recommended this one..I looked at it and was like..Why? Once I started using the practice he suggested I soon realized it was the way to go..
CCX Tools: I use many tools to help me develop applications; from audio recording apps to app that help you parse text, a developer can never have too many tools (perhaps). Tools help make our jobs easier by getting much more specific than the Cisco Script Editor can get when developing a test case for instance (or even experimenting with data sets).
Operating on the String: One of the most important Data Types we will be working with in CCX Applications is the String. I have brainstormed 10 “methods” to use to get the most out of the Strings we will be using..we’ll be “parsing” Strings within a String, replacing certain Strings with Strings we want (or getting rid of junk data that doesn’t make sense…some customer’s data can be quite messy), finding a certain point in a String and then changing the the Case of the following String, et al. This post should be fun and eye opening (hopefully), and it is possible that this post will contain numerous Parts…