WDE: Subscribe to requests that WDE sends to other components?

[abudwill]

Hello,

In the past within WDE customization I have subscribed to TServer or UCS to receive raw messages that come from those components.  Doing this allows me to examine those messages in detail, or interpret custom messages that I might be sending from a custom 3rd party application.  The Genesys support site has some pretty good examples on how to do this as well.

Now I am running into a scenario where I find myself wanting to see all Requests that WDE is sending out to other components, examine those and possibly change or react to them before WDE sends them on to the intended component. 

Normally I would examine command chains.  But in my particular case, no command chain is fired within the action I am wanting to perform.

This being said, is anyone aware of a way to subscribe to requests that WDE is sending to other components?

My particular use case is around UCS, I want to examine RequestUpdateAttributes requests that WDE sends to UCS and possibly change some attributes in the request before passing it along.  But in a general sense, I am wondering if requests can be intercepted / examined at all.

Regards,
Andrew

[daniel_san]

Hello Abudwill,

Hope i´m wrong, but i´m afraid that you can not intercept the requests to another servers. As you can see on the log what chain of command are the WDE executing (reacting to something), you can also see what are the events that WDE is sending.

For example, when WDE executes MarkProcessedOutboundChain on outbound call, you can see on the log:

'RequestDistributeUserEvent' ('48')
message attributes:
AttributeCommunicationDN [str] = "71110"
UserEvent      = ComplexClass(CommonProperties):
Time            = ComplexClass(TimeStamp):
AttributeUserData [bstr] = KVList:
'GSW_APPLICATION_ID' [int] = 487
[...]
'GSW_AGENT_REQ_TYPE' [str] = "RecordProcessed"
AttributeReferenceID [int] = 7

I don´t know exactly what do you want to accomplish but maybe you can figure out what are the command the WDE is executing on this particular case and delete it from the chain of command. You will be able to send your own event instead of the command.

Anyway if someone comes to say that he accomplished to subscribe to events that the WDE i will eat my words  .

Regards