Categories:
Configuration of the generic dialog for TV move backwards use case
How the generic dialog must be configured for this use case
Specific configuration
The TV move backwards use case is triggered by the generic dialog v3. For this use case, the required specific configuration is set below:
- Configuration for Brazil OB in STB channel. In this configuration, no default value is defined, as the STB device will resolve it when receiving an empty value in the parameter
levels. A new entity is now recognized:ent.time_length_hour. Additional recognition was required by the aura-bot in order to obtain the total number of seconds to be returned in the parameterlevels. To obtain that convertion into seconds, a new function has been created in utiles called:getSecondsLevelsWithTimerRecognizer.
{
"id": "generic-dialog-v3",
"channelDataVersion": "v3",
"suggestions": false,
"triggerConditions": [
{
"intent": "intent.tv.move_backwards",
"settings": {
"locales": {
"success": [
"tv:tv.moveBackwards"
],
"error": [
"core:flc.answer.error"
]
},
"actions": [
{
"name": "SEND_KEY"
},
{
"name": "MAKE_SOUND"
}
],
"payloadType": "tv",
"functions": {
"params": [
"currentIntent",
"persistentData",
"genericUtils",
"configuration"
],
"algorithm": "return new Promise(async (resolve, reject) => { try { const params = { levels: await genericUtils.getSecondsLevelsWithTimerRecognizer(currentIntent, configuration) }; persistentData.dialogData.actionParams['SEND_KEY'] = params; resolve(); } catch (error) { reject(error); } });"
}
}
}
],
"onlyIn": [
"set-top-box"
]
}
Last modified April 10, 2025: feat: Redefine move_forwards and move_backwards #AURA-26924 [RTM] (cb875ea3)