Cisco Bug: CSCum29066 - Wildcard collection returns unexpected results
Feb 06, 2017
- Cisco Unified Intelligence Center
Known Affected Releases
Symptom: Customer has created a Call Type Collection with Wildcard Collection Type. An example of one value is FSHO.9529248* We would expect a return of all Call Types that begin with FSHO.9529248 However, we are getting FSHO.9529245... Call Types as well. Conditions: Use Wildcard string for filtering collections in reporting.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases