Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Tony Tillyer on January 01, 1970, 12:00:00 AM
-
Hi Guys and Girls!
I have a requirement to add various KVP's to one Filter in DMA. Although I can build the Filter and it parses correctly, it is not shown as a Filter in CCPulse, after synchronisation with the correct StatServer. More simplified versions (that is, one Filter per KVP) works fine but multiple KVP's per Filter seem to be an issue.
Here's some examples:
Filtername1 = ( ( PairExist("OR_Exit_ID", 803) ) | ( PairExist("OR_Exit_ID", 806) ) | ( PairExist("OR_Exit_ID", 705) ) | ( PairExist("OR_Exit_ID", 707) ) | ( PairExist("OR_Exit_ID", 716) ) | ( PairExist("OR_Exit_ID", 735) ) | ( PairExist("OR_Exit_ID", 603) ) ) | ( PairExist("OR_Exit_ID", 616) ) | ( PairExist("OR_Exit_ID", 635) )
This works:
Filtername2 = PairExist ("OR_Exit_ID", 707)
Are we getting the syntax correct?
Is it possible to allocate more than one KVP per Filter?
-
Hi,
I believe you filter is simply to long. There might be no limitation for the content of a filter stored in DM (there used to be one when I worked with long filter definitions), however, for StatServer there is one. ConfigServer allows a max of 255 chars for the definition (including spaces), your's is above 255.
This might be one reason for a non working filter.
I'm very sure that you can filter several KVPs (I did that with up to 5 KVPs attached to a call).
One more thing: You might also want to add " in you definition (almost every KVP is a string and should be handled as such).
You should define:
Filtername1 = ( ( PairExist("OR_Exit_ID", "803") ) | ( PairExist("OR_Exit_ID", "806") ) | ( PairExist("OR_Exit_ID", "705") )
rather then:
Filtername1 = ( ( PairExist("OR_Exit_ID", 803) ) | ( PairExist("OR_Exit_ID", 806) ) | ( PairExist("OR_Exit_ID", 705) )
Regards
cyber
-
I definetly agree with Cyber, check also here:
http://baga.genesyslab.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=Solution84070xml&sliceId=&dialogID=216454
Moreover, can you restart StatServer? If yes, in the startup log file you should check if the filter has been accepted.
Hope it helps
-
Thanks guys!
The quotation marks were the bug... All OK now...
Happy Holidays!
Tony