Preview Tool

Cisco Bug: CSCsg33119 - Script editor does not need to load translation route labels.

Last Modified

Dec 29, 2016

Products (1)

  • Cisco Unified Contact Center Enterprise

Known Affected Releases

6.0(0) 7.0(0) 7.5(1)

Description (partial)

In a customer with a large configuration, there can be many labels. Currently, the script editor defers loading the labels until they are really needed. But when they are needed, and the label configuration is large, there can be a significant (minutes) delay.  

One reason for a large number of labels in a configuration is translation routes. But, there is no reason for the script editor to load translation route labels. It would be wrong for a customer to deliberately route a call directly to a translation route label, because it would just confuse the PG and cause the call to fail.  

The script editor could prevent this, and significantly improve performance by not loading these labels. 
Steps to reproduce:
1. Configure a translation route label in translation route config tool
2. Launch Script Editor and select the Label node in a script. Double click the label node to bring up the Label property dialog. 
3. In the Label property dialog, expand the label tree. The translation route label is listed in the tree.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.