12-30-2015 07:07 AM - edited 03-14-2019 03:36 PM
Just curious if anyone has any (documented or otherwise) best practices for UCCX scripting. Specifically wondering if every step's output branch should be handled (not marking a contact as handled) for the purpose of error handling.
cheers,
will
Solved! Go to Solution.
01-15-2016 06:12 AM
Not really a question of requirements James. Let's just say that I've inherited a deployment with plenty of opportunities for improvement and I'm gathering intel to develop a more standard and maintainable way to manage it going forward. Specifically, I was thinking of 'hanging' the holiday checks 'behind' the 'date/time' check subflow check. Not looking to start a debate on whether that's a good idea, but I will go on record as saying that it's a bad idea to develop a solution without entertaining all possibilities. It's extremely frustrating getting halfway through something and then learning that there's a better way of doing it. Guess I'm trying to be more methodical in my old age by asking more questions before than during.
cheers,
will
12-30-2015 10:05 AM
This is a great document. Thank you for sharing.
Bill
01-05-2016 12:18 AM
Also, when talking about exceptions:
https://supportforums.cisco.com/document/112046/uccx-discovering-exceptions
and also
https://supportforums.cisco.com/document/113951/uccx-exceptions-step
G.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide