Hi,
I am working with a frontend application that is used via Scripts when the users are in interactions in Genesys Cloud. This application is used to wrap up interactions and the intent is for the user not to need to choose wrapup again from the menu in Genesys.
There is an issue that has happened, unsure when but when it uses the API calls to set the wrapup code and disconnect the users they are directed to the After Call Work menu where they again have to chose a wrapup code and press done.
The initial API call that was used was this one (different calls used for the different interaction media types):
https://developer.genesys.cloud/devapps/api-explorer#patch-api-v2-conversations-calls--conversationId--participants--participantId-
Where i am patching the conversation with a Wrapup object with a code and the state is set to disconnected.
This is no longer working, and i have also made some attempts to try different API calls that should do somewhat the same:
api-explorer#patch-api-v2-conversations-calls--conversationId--participants--participantId--communications--communicationId-
api-explorer#post-api-v2-conversations--conversationId--disconnect
All Requests have returned 200/202 status code when run in the API Explorer and locally.
I have found a temporary solution where the application is doing one PATCH request to api-explorer#patch-api-v2-conversations-calls--conversationId--participants--participantId-
and one post request to
api-explorer#post-api-v2-conversations-calls--conversationId--participants--participantId--communications--communicationId--wrapup
Has there been any changes to these so they don't skip past the After Call Work?
Is this intended functionality or is this a issue for others?