User Community Feedback
Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.
NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.
Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.
NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.
To add to this, you can specify the queue id as a variable but not the skill requirements. This is a feature gap. We are looking up the queue ID based in the DNIS, but then we have to use a case statement with multiple "Queue Contact" nodes just to be able to set the skill! Also when using the "Advanced Queue Info" node, again there the queue can be selected from a variable but not the skill. So within the queue loop we are having to use case statements and multiple nodes to achieve something that would be much more concise if the skill could be assigned by a variable. Right now the flow looks very confusing!
Attachments Open full size