Hi guys, i’m a rookie when it comes to routing so please bear with me. I’m wondering if there’s a simple way to attach the config dbid of the agent I routed a call to as userdata in my strategy?
Eugene
Hi guys, i’m a rookie when it comes to routing so please bear with me. I’m wondering if there’s a simple way to attach the config dbid of the agent I routed a call to as userdata in my strategy?
Eugene
Hi Eugene,
as far as I know URS is not aware of that piece of info, so the first thing which comes across my mind is getting the agent employee id from your target selection step and run a query to the configuration database (the table you would be interested in is the cfg_person).
Francesco
Not sure why you need the DBID, but if you use the URS automatic attach – then there’s tons of good information there.
RTargetAgentSelected will contain the Agent User (or Employee - I forget and we have them set to the same)