The list below represents the features, updates, and fixes included in the Orbita Voice GA Release for July 2021.
Breaking Changes
In the Experience Designer, the subflows are not project-specific, When the subflow with an existing name is imported via restore API, it will replace all the instances of the subflows with the same name in the destination environment.
Please refer https://orbita.atlassian.net/wiki/spaces/OCS/pages/1747320855/How+to+export+and+import+Experience+Designer+flows+using+APIs#Import-Experience-Designer-flows
Core Product Modules
Experience Designer
Flow Studio
In the Single Input control, you can now use the Phone number and Email options to validate the user input.
Core Platform
Chatbot
In the chatbot URL, you can now dynamically pass query parameters to trigger an event (and the corresponding intent).
For example, You can invoke the help intent by using the query paramoeevent=HELP_EVENT
with the chatbot URL. https://sandbox.orbita.cloud:8443/oeapi/bot/support?oeevent=HELP_EVENT
General Improvements
While saving data using any schema, the data gets saved even after the validation fails(such as only numbers, max number of characters per field, and so on). This bug is now fixed.
When the
enableArrayresponse
is set totrue
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 use the Delete API with an empty body, you have to pass the key
Content-Length
and the value0
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 auto-generated slots will now get created after saving the Flow Studio.
The bug that duplicates Custom hook content in the chatbot when connected with only start and end nodes in flow studio is now fixed.
Importing the Experience Designer flows with restore API will no longer throw a 500 error when the flows contain subflows with the same name that already exist in the destination environment.