Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.

  • 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.

  • The bug that had the deleted taxonomy still accessible via the search node in Experience 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.

  • From this release, whenever the content data is deleted using the dynamic data manager node, the data will be removed from the Elasticsearch index as well. The same will be reflected in Insights.

You have to reindex the schema to remove the Elasticsearch indices of the data that is created and deleted prior to this release.

Release 4.0.84

  • Build 1623689085

Patch Fixes

  • Build 1620243240:

    Occasionally, there was an error displayed when the interaction model is published to google, "Orbita NLP: payload data is missing". This

    1624278404

    • There were multiple Token buttons in the Rich Text type filed in the content schema. This bug is now fixed.

    • Orbita chatbot now supports assistive technology for text responses and buttons.

    Build 1622154339:

    • Optimized the performance of Orbita NLP when the utterances include special symbolsIn the chatbot, when more than 3 buttons are added, it auto-scrolls to make the last button visible on the screen. This sometimes hides the first button from the screen. This bug is now fixed.

    • Even if the maxSuggestion property value is set in the autocomplete directive, the suggestion box contains all the suggestions available. This is fixed in this version.

    • The chatbot interruption due to the unavailability of the AppSettings node in the Experience Manager is now fixed.