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

Breaking Changes

In Experience Designer, the sub-flows are not project-specific. 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.
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

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

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 param oeevent=HELP_EVENT (here, HELP_EVENT is the event in the help intent) with the chatbot URL.
For example, https://sandbox.orbita.cloud:8443/oeapi/bot/support?oeevent=HELP_EVENT
Refer, How to invoke an intent instead of Launch node on loading the chatbot

Previously, when saving data using a schema, the data was saved even after the validation failed (such as only numbers, max number of characters per field, and so on). This bug is now fixed.
Previously, when the enableArrayresponse was set to true in the Bot provider V2 node, the validation messages in the flow studio were not appended to the response payload. This bug is now fixed.
Previously, when you clicked on the Flow Details of an imported flow, a "User not found" error displayed. Now, on import, the “Updated by” field is set as the user that performs the import action.
To use the Delete API with an empty body, you have to pass the key Content-Length and the value 0 in the Headers.

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 sub-flows with the same name that already exists in the destination environment.