Genesys Multicloud

 View Only
Discussion Thread View
Expand all | Collapse all

While requesting not ready, DnStateChanged emits data without reasons - nodejs api

  • 1.  While requesting not ready, DnStateChanged emits data without reasons - nodejs api

    Posted 01-13-2022 14:50
    Edited by Vinoth Ezhilan Manian 01-13-2022 14:53
    With workspace nodejs api, after sending agent not ready with reason code request. The "DnStateChanged" event received with  empty reasons array.
    //msg.mode = null & msg.code = 'Lunch'
    
    workspaceClient.voice.notReady(msg.mode, msg.code).then(()=>{return null;}).catch((error) => {
     this.logger.error('not ready failed as ', error);
     return error;
    });
    ​

    Json received as,

    {
    "dn":{
    "number":"xxxxx",
    "switchName":"xxxx",
    "agentId":"xxxxx",
    "capabilities":[
    "ready",
    "not-ready",
    "dnd-on",
    "set-forward",
    "start-monitoring"
    ],
    "agentState":"NotReady",
    "agentWorkMode":"Unknown",
    "reasons":[
    ]
    }

    but expected Json is,
    "reasons":[
    "key":"ReasonCode",
    "type":"str",
    "value":"Lunch"
    ]

    Why the reasons are empty for us? any clue.
    #Unsure/Other

    ------------------------------
    Vinoth Ezhilan Manian
    Pointel Inc
    ------------------------------


  • 2.  RE: While requesting not ready, DnStateChanged emits data without reasons - nodejs api

    Posted 02-01-2022 04:47
    This seems to be an issue with nodejs api. workspace client js issue 12

    ------------------------------
    Vinoth Ezhilan Manian
    Pointel (formerly Touch Point)
    ------------------------------



Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources