Categories:
Conversational dialog
Description of the conversational-dialog global use case available for Aiwi
Introduction
The conversational-dialog allows users to interact with an LLM with a predefined prompt.
This prompt should return a json formatted object to be mapped in a standard Aiwi response message.
Specific configuration
The conversational-dialog is designed to handle user’s requests using LLMs in ATRIA.
Currently, this dialog is available for Aura channelData V1 version and can only be used for the channel AIWI.
For this use case, the required specific configuration is set below:
{
"name": "conversational",
"dialogs": [
{
"id": "conversational-dialog",
"allowAnonymous": true,
"triggerConditions": [
{
"intent": "None"
}
],
"bypass": {
"duration": 30,
"payloadName": "conversational",
"initialData": {},
"recognizersEnabled": false,
"recognizersBreakIntents": {}
}
}
]
}
Specific values
| Key | Value | Description |
|---|---|---|
| bypass.duration | 30 (minutes) | This value overwrites the default aura-bot value for bypass lasting 10 minutes. |
| bypass.payloadName | conversational | Name of the interface that will be used as bypass payload for this dialog. |
| bypass.initialData | empty | It should contain any data needed by the dialog to be initialized. |
| bypass.recognizersEnabled | false | This value overwrites the default aura-bot way of working with recognizers when it is in bypass mode. If it is set to true, recognizers are executed, and their result is stored in the bypass payload to be used, if needed, afterwards. |
| bypass.recognizersBreakIntents | empty | Used to handle when the user requested any other use case during the execution of the dialog. To enable this config, bypass.recognizersEnabled should be enabled. |
Environment variables
| Property | Type | Description | Modifiable by OB? |
|---|---|---|---|
| AURA_GATEWAY_API_ENDPOINT | URI string | Endpoint to access the locally deployed ATRIA aura-gateway-api | NO |
| AURA_GATEWAY_API_ISSUER_URL | string | Aura issuer URL. It is automatically fulfilled by the installer. | NO |
| CONVERSATIONAL_COMMAND_KEY | string | Key of the command in the returned json from prompt. | YES |
| CONVERSATIONAL_MESSAGE_KEY | string | Key of the message in the returned json from prompt. | YES |
Configuration by channel
From Prince’s release onwards, the configuration of applicationId and presetId per channel and intent has been added to the channel model.
For this use case, the required specific configuration per channel is set below (added dialogs section under atria property at Main-Recognizer-Video-Triage-29855):
{
"atria": {
"dialogs":{
"None": {
"applicationId": "816bdab6-3ea3-4a77-bdea-12945d6d7053",
"presetId": "ef3d0603-3fef-4109-a577-0ab92f9060df"
}
}
}
}
Specific values by channel
| Intent | Key | Value | Description | Modifiable by OB? |
|---|---|---|---|---|
| intent.tv.custom_recommendation | applicationId | 1eb11727-14f2-447f-acc0-a2211ab55870 | ATRIA application identifier | NO |
| intent.tv.custom_recommendation | presetId | e0cdcae2-025d-4624-8096-d6bf4b5eaaff | ATRIA preset identifier to be used within the use case. | NO |