The list below represents the features, updates, and fixes included in the Orbita Voice GA Release for August 2020.
Breaking Changes
The property
msg.payload.orbita.mulitmodalwill be removed in version v4.1. You will receive the below warning when using the multimodal property.
Please consider using
msg.payload.multiagentproperty instead.In Answers > Advanced tab, you can set a fallback relationship for the K-Graph.
If the user’s utterance contains a topic but doesn't have a relationship and if a default relationship is not set in the Answers Manager node, then the bot will check for the Fallback relationship (if any) and respond with the Fact content that corresponds to the topic(user’s utterance) and fallback relationship (if any).
...
Modified the chronology of events that happen while deploying the interaction model to the same agent.
1. The intents will be deleted,
2. The Entities will be deleted second, and
3. The new Interaction model is updated.The intent limit for amazon is 250 intents and for Google dialogue flow it is 2000. If you try to publish the skill with intents more than the specified limit, you will receive a warning on the deployment screen.
Error message for Google,
Error message for Alexa,
.png%26size=238193%26width=2404%26height=1116?version=1&modificationDate=1597315390985&cacheVersion=1&api=v2)
Added a new property in Global menu > Organization settings that will enable admin users to set default spell checker language in the multimodal content editor for that environment.
Five minutes before session expiry, a pop up will be displayed with the countdown from 4.59 mins. If the user takes no action, the session will expire and the user will be logged out of Experience Manager.
As an admin user, you can enable or disable Redis cache in the environment using the toggle in Organization settings. You can also set the Cache TTL (in seconds) for Experience Manager, Experience Designer, and user session.
.png%26size=80383%26width=1306%26height=534?version=1&modificationDate=1597314607544&cacheVersion=1&api=v2)
In the web chatbot, we have enabled users to navigate to all interactive interface components using a keyboard.
The auto-generated intents from answers will not be displayed in the intents listing screen.
...