Something like that.... but you have to add the reasoncode Key Value Pairs into your StatServer and also associate them within your Routing...
OK <deep breath...>
To populate (any) Key Value Pair you must first apply it, through either a Routing Strategy - or allow it to be attached, as data, from something like a Softphone or CTI Toolbar. In the case of reasoncodedata, the intention is to provide the means to allocate a "Reason Code" for an Interaction. There are some Values associated by default - but you can add your own Values, too - the same as any pre-defined Key Value Pair.
In most cases, a Reason Code will be applied [i]after [/i]the call or interaction is complete - usually during After Call Work (ACW). This is achieved through the Agent selecting an appropriate Reason Code and applying it, through their Softphone, Desktop or CTI Toolbar, during a period of ACW. Once applied, it will become attached to the Call UData, through the Agents (Softphone or CTI Toolbar), which is connected to a TServer. The TServer associates the Reason Code Key Value Pair to the ConnID of the Interaction.
...THEN the StatServer can pick up the Reason Code Key Value Pair and you can use it, for Reporting purposes.
So, your Filter is quite accurate - but it will have nothing to report on, if you don't first update your Routing to allow it to associate the Key Value Pairs for reasoncodedata.
.... <breathes out...>
[url=http://docs.genesys.com/Documentation/RTME/latest/User/Filters]http://docs.genesys.com/Documentation/RTME/latest/User/Filters[/url]
