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 for widget chatbot messages that display options (e.g., screenshots) that the user should select.
When the user says no to a bye confirmation of the chatbot, right after a widget message is displayed, the chatbot will display the same widget message (i.e., the new message); however, the past widget would not be disabled, which means the user can still select options from it, and this can cause errors in the conversation flow.
We can reproduce this by saying bye after the list of apps are shown for selection, then, we can see that both widget messages (listing the apps) are enabled, so I can use any and the other one will remain enabled (it shouldn't, it should be disabled).
One possible solution is to disable the past widget message in the react front end. However, I am not sure how to do this in react.
The text was updated successfully, but these errors were encountered:
Another potential solution is to have a token that is generated by the server for each widget message.
The server will keep a "current" token, which is the next expected token by the server.
If the token of a widget matches the one from the server, checked in the chatbot GUI (by sending a token verification request to the server), then it will process the message (i.e., send the msg to the server, etc).
Otherwise, the GUI will ignore the event for this widget and potentially display an alert for the user telling her that this widget cannot be used anymore.
This is for widget chatbot messages that display options (e.g., screenshots) that the user should select.
When the user says no to a bye confirmation of the chatbot, right after a widget message is displayed, the chatbot will display the same widget message (i.e., the new message); however, the past widget would not be disabled, which means the user can still select options from it, and this can cause errors in the conversation flow.
We can reproduce this by saying bye after the list of apps are shown for selection, then, we can see that both widget messages (listing the apps) are enabled, so I can use any and the other one will remain enabled (it shouldn't, it should be disabled).
One possible solution is to disable the past widget message in the react front end. However, I am not sure how to do this in react.
The text was updated successfully, but these errors were encountered: