Anthony, if you ever read this, is there a way to filter out a certain exception from being E-mailed to me when I have it setup to E-mail me on the WFExecutionException ? I like the way it functions now and it works great but if someone hangs up in the script it generates "Contact id: 248, Contact terminated remotely", which will get very annoying once this goes into production. I did talk to our E-Mail admin about having one of our e-mail filters just pick up on "Contact terminated remotely" in the body of the e-mail CCX sends me and delete it but he hasn't done anything for me yet.
If I ever read this? I live on these forums my man! :P
If you register more than one Exception handler, the more specific exception handler goes below or after the more generic handler and will be triggered instead of the more generic one.
Start On Exception (WFExecutionException) Goto Send Email On Exception (ContactInactiveException) Goto End of Script Accept... Play Prompt... Menu... Select Resource... Send Email: Create Email... Send Email... Goto End of Script End of Script: End
This was almost too simple Anthony. I must remember the sheer power of string functions (contains) in the if/then context.. Like the variable (WhatBroke) that holds the message its about to e-mail me: WhatBroke.contains("Contact terminated remotely") , then clear exception and end script. Works perfect!
I have learned there are 10 ways to kill that cat with anything Cisco. I re-read what you were saying about the more and less generic exception order and thought about it. I re-did my script. Your way is more short and precise as my way was perhaps entering what can become 'spaghetti code'? You know what I mean. Thanks!
Thanks for the tip, I'm always learning. Had to have somewhere to 'goto', so I sent them here..