Route using List oblects table with ListGetDataCfg

[kapusta1152]

Hello,

I am trying to route call base on 800/(dnis) numbers with List objects tables (see Fig.4 attachment).

My goal is to route all DNIS equal “true” from List Object “riute2ivr” see Fig .4 to top branch of strategy (simple fork).

I am using “ListGetDatacfg” function but all my calls going only in one direction?

v_800dnis=ListGetDataCfg[route2ivr,ivr800_dnis,'']  Fig.2

I am wondering how I can modify list objects or use another function to accomplish my task (just simple “fork”).

Thanks for your help

[kowari]

Hey dude,
I suspect you have fallen prey to one of the WORST genesys issues in the world.  The leading space.

Run the routing strategy and look in your URS logs - it will say "no key" or something like that in them.  Based on what I can see in your screenshots, it LOOKS like the section in route2ivr called "ivr800_dnis" is ACTUALLY " ivr800_dnis"

Oh yeah and you need to do this: v_800dnis=ListGetDataCfg['route2ivr','ivr800_dnis',v_dnis] to access the table properly.  Go read the help on how this function works

But ALWAYS ALWAYS ALWAYS look in your URS logs and trace a call through to see what happens
Hope that helps,
Gail

[kapusta1152]

Now I  can control destination from my list objects table ("route2ivr") by changing  status of each dnis/800 from true to false.

Thanks  for your help!

[kowari]

Good stuff 

[victor]

[quote author=kowari link=topic=3303.msg13733#msg13733 date=1221013724]
Good stuff 
[/quote]

Kowari,

what leading space? I don't recall anything like this...

v_800dnis=ListGetDataCfg[route2ivr,ivr800_dnis,''] -> was the problem that route2ivr needed to be ' route2ivr'??
Or do you always have a leading space in front of the object that Genesys adds? Can you please explain a little bit more?

Thanks,
Vic

[Dionysis]

If you look closely at the keys mentioned above, you have:

[code]"ivr800_dnis" is ACTUALLY " ivr800_dnis"[/code]

URS is looking for a key called "ivr800_dnis", however no such key exists, only this one " ivr800_dnis".

Notice the space before 'ivr' in the second key.  URS is not particularly smart when it comes to strings, each character could be a number, a space or a letter (among other things) and if the EXACT match is not found it will not find the value you are looking for and will cause an error in the logs stating "no key".

Does that help at all?

[kowari]

A leading space is when you type something and you accidentally put a ' ' in front of it.  The problem is, when you look at the thing you typed, it looks fine because you dont really see the space.

So the in the list object called 'route2ivr' the section was called ' ivr800_dnis' but he was typing 'ivr800_dnis' in the strategy which is not the same, and the routing strategy would have not worked.

ALWAYS run a test call and look in the URS logs - it will show you error messages that make this much clearer.