The list below represents the features, updates, and fixes included in the Orbita GA Release for July 2021.
Table of Contents |
---|
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
...
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 totrue
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 was displayed. Now, on import, 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 value0
in the Headers.Previously, when the Flow Group intent is used in the Experience Designer, the chatbot utterance is triggered in a loop. 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 get created after saving the Flow Studio.
Previously, when the custom control is connected between only the start and end controls in the Flow studio, custom hook content is duplicated in the chatbot. 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 throws a 500 error when the flows contain sub-flows with the same name that already exists 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.
...