You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue, rather something informative.
I could read from the ibm watson assistant v2 api documentation that there is a state property which provides information about the current conversation state. It also says that it is an encoded string. Is there any way i can decode this string and get the information on the current conversation state? If yes, please provide the steps to decode it.
Below is the format of the json object where state property is present,
Setting debug:true in the options object should return all the info you want. At this time you cannot pro-actively edit the state object you are seeing there to manipulate it, but you can get the same info via debug:true.
Editing the state in v2 api is on the roadmap.
If you absolutely need to edit the state then I'd suggest using v1 in the meantime.
Thanks @mitchmason@germanattanasio .
I already have debug set to true in the options object. But it isn't giving me the information related to digressions. Can you tell me the way to get information on digressions? Like v1 api has digressed:true in the system context variable. Getting atleast digressed:true would be of great help with v2 api.
This is not an issue, rather something informative.
I could read from the ibm watson assistant v2 api documentation that there is a state property which provides information about the current conversation state. It also says that it is an encoded string. Is there any way i can decode this string and get the information on the current conversation state? If yes, please provide the steps to decode it.
Below is the format of the json object where state property is present,
Also find the link to the documentation, https://cloud.ibm.com/apidocs/assistant/assistant-v2#send-user-input-to-assistant
Thanks in advance
The text was updated successfully, but these errors were encountered: