<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>RE: Time of Day Scripting</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=" />
  <subtitle>RE: Time of Day Scripting</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=</id>
  <updated>2013-06-20T06:30:03Z</updated>
  <dc:date>2013-06-20T06:30:03Z</dc:date>
  <entry>
    <title>RE: Going to the next node dynamically</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11141060" />
    <author>
      <name>Jonathan Adams</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11141060</id>
    <updated>2013-01-25T16:11:02Z</updated>
    <published>2013-01-25T16:09:23Z</published>
    <summary type="html">Honestly, don't waste your time making different versions of the script before you present it. Have your basic features for demonstration purposes if that's what they want. Present it while letting your customer know that you're flexible and can fit it to their needs/specifications. Don't want that menu option? Cool, I can do that. Want another one that does ____? Got it, I'll make sure to change the call flow diagram and program the script accordingly, etc. If you're so tied up on having a hard set version of the script that they can't have you change, they're probably not going to buy it. I know I wouldn't.

As for the default maximum number of steps, usually you don't want a script going over that, but it can be increased significantly.</summary>
    <dc:creator>Jonathan Adams</dc:creator>
    <dc:date>2013-01-25T16:09:23Z</dc:date>
  </entry>
  <entry>
    <title>RE: Going to the next node dynamically</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11137418" />
    <author>
      <name>Jonathan Adams</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11137418</id>
    <updated>2013-01-25T14:53:12Z</updated>
    <published>2013-01-25T14:53:12Z</published>
    <summary type="html">Sounds to me like you have a planning problem :)
What I would actually recommend doing before you go any further is sit down with your customer, get every last detail of what they'd like you to build, make a Visio drawing of the call flow including the verbiage of the prompts, and have them sign off on it. Then from there, any changes out of the scope of work are a minimum of 1 hour paid time (more if it takes you longer to change the script as requested) for you.</summary>
    <dc:creator>Jonathan Adams</dc:creator>
    <dc:date>2013-01-25T14:53:12Z</dc:date>
  </entry>
  <entry>
    <title>RE: Going to the next node dynamically</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11131855" />
    <author>
      <name>Jonathan Adams</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11131855</id>
    <updated>2013-01-25T12:44:58Z</updated>
    <published>2013-01-25T12:44:58Z</published>
    <summary type="html">Not sure why you'd have it do that, but if it's certain days it needs to go to the other part of the script, you could have a Day of Week switch in the menu with a different GoTo. Otherwise, if you need to manually change it and you want to do that without getting into the script, you could set a boolean variable as a Paramater. That way, you can just go to the application in UCCX and change it there instead of having to get into the script and make changes, save, and reload the app.</summary>
    <dc:creator>Jonathan Adams</dc:creator>
    <dc:date>2013-01-25T12:44:58Z</dc:date>
  </entry>
  <entry>
    <title>RE: Detect Answer Machine</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11114390" />
    <author>
      <name>Jonathan Adams</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11114390</id>
    <updated>2013-01-24T22:35:51Z</updated>
    <published>2013-01-24T22:35:51Z</published>
    <summary type="html">Assuming the people you're trying to reach actually want to speak with you/your company, you could have a menu with a prompt that asks them to press a number before continuing. Other than that, I'm not aware of a way it can be done, since most people have their own voice recorded on their answering machine.</summary>
    <dc:creator>Jonathan Adams</dc:creator>
    <dc:date>2013-01-24T22:35:51Z</dc:date>
  </entry>
  <entry>
    <title>RE: finalCalledPartyNumber CTI Route Point CDR</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8266491" />
    <author>
      <name>Jonathan Adams</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8266491</id>
    <updated>2012-11-02T17:01:55Z</updated>
    <published>2012-11-02T17:01:55Z</published>
    <summary type="html">Use HRC.... :)</summary>
    <dc:creator>Jonathan Adams</dc:creator>
    <dc:date>2012-11-02T17:01:55Z</dc:date>
  </entry>
  <entry>
    <title>RE: Time of Day Scripting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8266365" />
    <author>
      <name>Jonathan Adams</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8266365</id>
    <updated>2012-11-02T16:48:07Z</updated>
    <published>2012-11-02T16:48:07Z</published>
    <summary type="html">You could set it to open at 8am and then parse the time (T[now].hour, T[now].min) and on the day's it's open, run an if() statement for this 5 minute window, then GoTo open if it matches. Or you could do the reverse, in a way - have a specific switch case for 7am-8am, and only allow it to go to Open if it's 7:55~7:59; otherwise go to Closed. Doing it that way might be better so you don't have to mess around with am/pm recognition manually. Not really any other way around it if they don't let you enter specific times.</summary>
    <dc:creator>Jonathan Adams</dc:creator>
    <dc:date>2012-11-02T16:48:07Z</dc:date>
  </entry>
</feed>

