...
If the location access is blocked and in the chatbot and if the user clicks on “Yes” for location access, an error popup will be shown and on clicking “OK” the user will be redirected to the “No” flow.
If the location access is allowed in the chatbot and if the user clicks on “Yes” for location access, and if there is a timeout error, the user will be directed to the “No” flow.
...
The output from the Answers manager node wont won't have the
rawMultiagentproperty. However, the output payload of the following say node will have therawMultiagentproperty.
...
Fixed the autoscrolling issue in the mobile chatbot. If the user scrolls to the top for more than 300px, the auto-scroll will be turned OFF. If the user scrolls to the bottom of the bot or scrolls within the range of 0 - 300px, the auto-scroll will be turned ON.
Fixed a bug that doesn't allow deploying the interaction model of a new project to a new Google dialogflow agent.
In Schemas, while using the field with
type: "number", when you enter a number greater than 50, it throws a warning “<field name> should be the maximum of 50“. This bug is fixed.Deleting a taxonomy is The bug related to deleted taxonomy still accessible via the search node in the Experience Manager. This bug designer is now fixed.
In Flow studio > Options control, when the option "Say Number Before Option" is enabled, the response Say 1 as Option is not read. This bug is now fixed.Occasionally, there was an error displayed when the interaction model is published to google, "Orbita NLP: payload data is missing". This is now fixed.