Documentation will get fixed.
As to the api: technically a prompt does not have tts. A prompt is a container for a bunch of language resources. So if you can have a greeting prompt, with a resource in en-us that says "hello", a 2nd resource in fr-ca that says "bonjour", etc. So when you look up the
/api/v2/architect/prompts endpoint you will see something like this
{
"entities": [{
"id": "myPromptId",
"name": "greeting",
"description": "how to say hi",
"resources": [{
"id": "en-us",
"promptId": "myPromptId",
"language": "en-us",
"mediaUri": "<someUriHere>",
"ttsString": "hello",
"text": "hi",
"uploadStatus": "transcoded",
"uploadUri": "<anotherUriHere>",
"languageDefault": true,
"durationSeconds": 1.053,
"selfUri": "/api/v2/architect/prompts/myPromptId/resources/en-us"
},
{
"id": "fr-ca",
"promptId": "myPromptId",
"language": "fr-ca",
"ttsString": "bonjour",
"text": "bonjour",
"uploadStatus": "created",
"uploadUri": "<anotherDifferentUriHere>",
"languageDefault": true,
"selfUri": "/api/v2/architect/prompts/myPromptId/resources/fr-ca"
}
],
"selfUri": "/api/v2/architect/prompts/myPromptId"
},
{
"id": "myPromptId2",
"name": "goodbye",
"description": "how we say bye",
"resources": [{
"id": "en-us",
"promptId": "myPromptId2",
"language": "en-us",
"ttsString": "goodbye",
"text": "bye-bye",
"uploadStatus": "created",
"uploadUri": "<yetAnotherUriHere>",
"languageDefault": true,
"selfUri": "/api/v2/architect/prompts/myPromptId2/resources/en-us"
},
{
"id": "fr-ca",
"promptId": "myPromptId2",
"language": "fr-ca",
"ttsString": "Au revoir",
"text": "Au revoir",
"uploadStatus": "created",
"uploadUri": "<oneMoreUri>",
"languageDefault": true,
"selfUri": "/api/v2/architect/prompts/myPromptId2/resources/fr-ca"
}
],
"selfUri": "/api/v2/architect/prompts/myPromptId2"
}
],
"pageSize": 25,
"pageNumber": 1,
"total": 2,
"firstUri": "/api/v2/architect/prompts?pageSize=25&pageNumber=1&sortBy=name",
"selfUri": "/api/v2/architect/prompts?pageSize=25&pageNumber=1&sortBy=name",
"lastUri": "/api/v2/architect/prompts?pageSize=25&pageNumber=1&sortBy=name",
"pageCount": 1
}
------------------------------
Melissa Bailey
Genesys - Employees
------------------------------
Original Message:
Sent: 07-27-2021 16:12
From: Vaun McCarthy
Subject: User Prompt data type textToSpeech Property
Hi Patrick
I took a very quick look at this yesterday and in my short testing I could only get back the id, name and type - not the textToSpeech property. Not sure then if the documentation is wrong, I'm looking at it wrong, or it's a defect.
Out of curiosity what are you looking to do with this data when you retrieve it?
------------------------------
Vaun McCarthy
NTT New Zealand Limited
Original Message:
Sent: 07-26-2021 10:34
From: Patrick Rohlf
Subject: User Prompt data type textToSpeech Property
There is an article (see below) In the Genesys Cloud help portal which shows that the 'textToSpeech' property is "available in a prompt data type". But, I cannot find a way to retrieve this value real-time in an Architect flow.
For example, I would like to provide the name of an existing User Prompt in the Find User Prompt action and have it return the value in the textToSpeech Property of that prompt. I've tried multiple different ways in the expression editor, but I can't find a way to make it work. Has anyone done this before and/or have a suggestion of how I might achieve this? I also did a cursory look through the Genesys Cloud data action documentation to see if there was a method to do it there, but I did not find anything obvious.
I appreciate the help!
Prompt data type - Genesys Cloud Resource Center| Genesys Cloud Resource Center | remove preview |
|
#ArchitectureandDesign
------------------------------
Patrick Rohlf
Summit Broadband
------------------------------