Watson conversation API returns empty output for yes and no input
Date : March 29 2020, 07:55 AM
I wish this help you Based on the full JSON request/response, your issue is here (actually it's also in the previous call, but that works by concidence): {"input": {"text": "yes"}}
{
"input": {"text": "yes"},
"context": {
"conversation_id": "b53dff12-9252-4b7e-abe8-7b45f561d394",
"system": {
"dialog_stack": [{"dialog_node": "node_19_1480518011225"}],
"dialog_turn_counter": 1,
"dialog_request_counter": 1
}
}
|
Multiple output text value setting in watson conversation
Date : March 29 2020, 07:55 AM
help you fix your problem This is really complicated to answer because depends your Business role inside your Chatbot. But, if you wanna answer one message according to the Condition... if bot recognizes successScenario response "I want to get this with success scenario"
if bot recognizes errorScenario response "I want to get this with error scenario"
|
Watson Conversation Unity - Add third party API data to the Watson Conversation/Assistant dialog answer
Tag : chash , By : Alex Sadzawka
Date : March 29 2020, 07:55 AM
I wish this helpful for you I don't have knowledge on unity/C#, but independent from the language you are using, it's possible to manipulate the information that the Conversation/Assistent will have by changing the context object before sending it back, creating a new index, like "context.temperature", and then in the conversation, you can use something like "The current temperature in Berlin is $temperature". The Conversation/Assistent is stateless, so everything the system will know about your dialog is in the context object, thats why you aways need to send it back on a new requisition. So anytime you need to add a information to the flow from another source, all you need to do is create a new index in the context.
|
IBM Watson Assistant / Conversation : The output displays the last search
Date : March 29 2020, 07:55 AM
wish help you to fix your issue Found the answer. I put the output text in a child node instead of the parent node. No need to remove any context variable.
|
IBM Watson Conversation - Unable to connect node.js to watson conversation
Date : March 29 2020, 07:55 AM
|