Versions Compared

Old Version 3

changes.mady.by.user Rajkiran Alla

Saved on

compared with

New Version Current

changes.mady.by.user Rajkiran Alla

Saved on

Key

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

The list below represents the features, updates, and fixes included in the Orbita Voice GA Release for July 2021.

Table of Contents

Breaking Changes

...

  • In the Single Input control, you can now use the Phone number and Email options to validate the user input.

Core Platform

Chatbot

General Improvements

  • While Previously, when saving data using any a schema, the data gets was saved even after the validation failsfailed (such as only numbers, max number of characters per field, and so on). This bug is now fixed.

  • When the enableArrayresponse is set to true in the Bot provider V2 node, the validation messages in the flow studio are not appended to the response payload. This bug is now fixed.

  • To Previously, when you clicked on the Flow Details of an imported flow, a "User not found" error was displayed. Now, the “Updated by” field is set as the user that performs the import action.

  • Previously, when the Delete API is used with an empty body, the system throws a 504 bad gateway error. Now, if you want to use the Delete API with an empty body, you have to pass the key Content-Length and the value 0 in the Headers.

  • The bug that shows the "User not found" error when you click on the Flow Details of an imported flow is now fixed. On import, the “Updated by” field is set as the user that performs the import action.

  • Fixed the looping issue that occurs in the chatbot while using Flow Group intent in the Experience Manager.

  • The Previously, the chatbot utterance is triggered in a loop when the Flow Group intent is used in the Experience Designer. Now, when the Flow Group intent is used in the Experience Designer, the chatbot utterance is triggered only once per request.

  • Previously, the auto-generated slots are not getting generated when a flow studio is saved with the Autogenerated slots option enabled on the Flow details screen. Now, the auto-generated slots will now get created after saving the Flow Studio.

  • The bug that duplicates Custom Previously, custom hook content is duplicated in the chatbot when the custom control is connected with between only the start and end nodes controls in flow studio is now fixed. Importing the Flow studio. Now, the custom hook content will not be duplicated even if the custom control is connected between only the start and end controls in the Flow studio

  • Previously, importing the Experience Designer flows with restore API will no longer throw throws a 500 error when the flows contain subflows sub-flows with the same name that already exist in the destination environmentexists in the destination environment. Now, when a sub-flow with an existing name is imported via restore API, it will replace all the instances of the sub-flows with the same name in the destination environment.

Release 4.0.88

  • Build 1626221127

Patch fixes

  • Build 1627485026:

    • Previously, the re-indexing of documents failed when the schema contains es field property. Now, re-indexing of documents is working as expected.

  • Build 1629215153:

    • Previously, intents are duplicated while importing the modules from one project to another with the “delete and import” option is selected. Now, the duplicate intents will not be created while importing the modules from one project to another with the “delete and import” option selected.

    • Introduced a new setting for the Chatbot that allows the chatbot user control when to send the voice input for processing. Refer, https://orbita.atlassian.net/wiki/spaces/OCS/pages/1933901852/How+to+control+mic+input+in+the+chatbot
      The default setting is "autoPost": true,.
      If the setting is "autoPost": false,, then the chatbot user can click on the mic icon to continue the voice input and choose to send the input when he/she has completed the utterance/command.