" /> Agent ACW status in WDE is changed but do we need to pass it to Tserver? - Genesys CTI User Forum

Author Topic: Agent ACW status in WDE is changed but do we need to pass it to Tserver?  (Read 1717 times)

Offline nandinir

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Advertisement
Greetings,

I am a newbie  in Genesys SDK development and am currently working with Genesys WDE wherein I have a query and request your help with below.

I could force the Agent Status in WDE to ACW(After Call Work) once after Event Released state. I could see that ACW status in WDE is changed but, request your help to  confirm "if WDE need to pass any data to Tserver so that Agent is put into ACW mode in Queue and no further calls lands on his extension until he goes ready".
[code]     
    IMyAgentState AState;
    Status sample = Status.NotReadyAfterCallWork;
    AState.State = sample;// changing status to ACW
[/code]


Or is this something automatically taken care by Agent once he goes into ACW mode , so we needn't worry about passing the status to TServer from our code.


Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
I am afraid to say you need to go back to Genesys Framework 101, as what you're asking is as fundamental as basic to understand how Genesys works, let alone developing an agent desktop application.

The Genesys logic is based on a request-event model, where client apps issue requests to T-Server - a message dispatcher, protocol translator and media component - via a proprietarty T-Library API. T-Server then packages up the response in a TEvent structure and issues an event back to the client(s).

An agent status is a key concept of the Genesys ecosystem and controlled by T-Server. So whenever you 'change' the agent status in WDE, is not set on the client on its own, but *requested* to and  granted by the T-Server instance your WDE is connected to.

Learn by heart T-Lib SDK guide :)

Fra