Hi.

I am wondering if anyone has come across this when integrating Genesys Cloud with Verint WFM?  When we initially tested this, the file names provided were the Genesys queue name, but when I have been setting this up today for a client, the format of the queue name is the unique Genesys identifier. I appreciate I can check which queue is which, but in the interest of making this easier for both myself and the customer going forward, it would be great to map in a more readable format.

I will post on the WEM community too.

#WFM, #ConfiguringWFM, #Mapping

Thanks, Heather 

Yes, check with the WEM community.  What integration are you using?  I know this one Genesys AppFoundry - WFM Adapter (mypurecloud.com) works well and requires very little in the way of mapping and other issues with API.

Hi.

I am wondering if anyone has come across this when integrating Genesys Cloud with Verint WFM?  When we initially tested this, the file names provided were the Genesys queue name, but when I have been setting this up today for a client, the format of the queue name is the unique Genesys identifier. I appreciate I can check which queue is which, but in the interest of making this easier for both myself and the customer going forward, it would be great to map in a more readable format.

I will post on the WEM community too.

#WFM, #ConfiguringWFM, #Mapping

Thanks, Heather 

Thanks so much for your reply. I posted on the WEM community at the same time as here. It is Verint's own adaptors we are using. Thanks for this.

Yes, check with the WEM community.  What integration are you using?  I know this one Genesys AppFoundry - WFM Adapter (mypurecloud.com) works well and requires very little in the way of mapping and other issues with API.

Hi.

I am wondering if anyone has come across this when integrating Genesys Cloud with Verint WFM?  When we initially tested this, the file names provided were the Genesys queue name, but when I have been setting this up today for a client, the format of the queue name is the unique Genesys identifier. I appreciate I can check which queue is which, but in the interest of making this easier for both myself and the customer going forward, it would be great to map in a more readable format.

I will post on the WEM community too.

#WFM, #ConfiguringWFM, #Mapping

Thanks, Heather 

I would cross check the permissions associated with the integration to ensure it is correct and failing that confirm if the behaviour exist on multiple Verint instances via Genesys Cloud when using the Genesys CSI & STCI for Cloud connections (if possible) 

From looking at the documentation it doesn't appear that Genesys Queue Name is a valid part of the response that Verint receives back, Queue ID is though. I agree with you that the Queue Name makes sense to receive back and I too have seen it however as it's Verint making the request to Genesys I would suggest raising a support case with Verint in the first instance to ensure nothing has changed, in tandem a Genesys case won't hurt however may not be as fruitful. 

Thanks so much for your reply. I posted on the WEM community at the same time as here. It is Verint's own adaptors we are using. Thanks for this.

Yes, check with the WEM community.  What integration are you using?  I know this one Genesys AppFoundry - WFM Adapter (mypurecloud.com) works well and requires very little in the way of mapping and other issues with API.

Hi.

I am wondering if anyone has come across this when integrating Genesys Cloud with Verint WFM?  When we initially tested this, the file names provided were the Genesys queue name, but when I have been setting this up today for a client, the format of the queue name is the unique Genesys identifier. I appreciate I can check which queue is which, but in the interest of making this easier for both myself and the customer going forward, it would be great to map in a more readable format.

I will post on the WEM community too.

#WFM, #ConfiguringWFM, #Mapping

Thanks, Heather