GA Release - August 2020

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.mulitmodal will be removed in version v4.1. You will receive the below warning when using the multimodal property.
Please consider using msg.payload.multiagent property instead.
In Answers > Knowledgebase > Settings > Advanced tab, you can set a Primary Topic and 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).
Similarly, if the user’s utterance contains a relationship but no topic, the fact that corresponds to the Primary Topic and the relationship(user’s utterance) is rendered.
Please go through the below flow chart for more details on how it works.

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,
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.
The number in the clear (#) keys button denotes the count of cached keys by Redis and you can clear them by clicking on the button for the respective interface.

In the web chatbot, we have enabled users to navigate to all interactive interface components using a keyboard.

When a project is archived, the corresponding Experience designer flows will be disabled.
Removed the !important tag from the CSS block on the carousel control. As an admin user, you can now modify the carousel CSS block.
Admin users can now import sample flows that are stored in the repository.
In the Answers Manager node, we have introduced a toggle option, when enabled, will generate relationship buttons after the fact content is read.
When a fact is triggered, the fact content is accompanied by all the other relationships (as buttons) that are related to the invoked topic.
Sample screenshot of web chatbot with the Include related fact buttons enabled.
Cafeteria is the topic.
Availability, hours, and location are the relationships.
In this example, the topic(Cafeteria) and the relationship(Availability) is triggered. The corresponding fact is rendered along with the other relationships(Hours, Location) connected to that topic(Cafeteria).
The users can export the flows or selected nodes to the library using the Export > Library option from the hamburger menu.

Introduced a new feature that will generate an intent per fact provided that fact contains questions in the questions tab. Each question is treated as an utterance for that corresponding intent.
The toggle button is available in the Advanced tab > Generate intent per fact in KB.
You can also choose to publish these intents to either Google or Alexa or both.
By default, the Generate intent per fact in KB is toggled off.

Answers Group Intent - Introduced the Answers Group Intent node. This node groups all the intents that are generated by the toggle function described above.
- If this node is placed and connected to the Answers manager node in Experience Designer, it will be able to recognize the questions present in the questions tab of the facts screen as utterances and trigger the corresponding intent via this node.
The intents generated for Individual facts will be listed in the Settings page > Intents tab. Any changes made to the Questions inside a Fact are reflected in the intents tab.

Storage node (Beta)- Introduced a new node that will allow reading/writing files from a persistent storage from the Experience designer.
This node is currently is available only in the beta enabled environments. Please contact support to enable this feature.

As a flow studio user, you can end a session optionally via End control > directive tab > End session checkbox.
When a linked control (in link flow control) is deleted or when the flow manager node cannot find a valid control id, a new error message “Cannot find Control ID #“ is shown in the debug tab of the Experience Designer.
If the buttons are defined in the multimodal content editor’s button tab, the button type will be set to Default after the upgrade.

Added flow studio to the task types. Now the clinicians can assign flow studio flows in a task.
Then you can choose the flow studio. Please note that the dropdown contains all the flow studios present in the environment.

Added a menu item “Apply to population“ that will apply the care journey changes to all populations associated with it.
The tasks will be converted to the respective patient’s timezone before displaying them to the patient.

The text from Rating control in Flow studio will now be displayed in the chatbot.
Updated the default styles of cards in Engage.
Fixed an error that duplicates the say text in Survey and Flow studio.
Fixed the bug that duplicates the sub-flows when importing flows via API.
In Survey, on the choices page, fixed the misaligned dialog box that appears while adding the synonyms.
Simplified the error messages shown when the bot fails to load.
The text specified in the label field of SSML schema is reflected in the Multimodal content editor.
The chatbot will highlight the selected item and will keep the unselected items on the user response side.
Fixed bugs and alignment issues in the Clinician/Patient portal.
Fixed Chatbot loading issues when launched in Windows 10 IE11 browser.
Fixed a bug that doesn't allow to display the map icon in carousel’s full detailed view.
The Evaluate control and Rating control will now work as expected.
Fixed the bug that adds an empty bubble in the chatbot before the image is rendered from the Chat text field of the multimodal content editor in the flow studio.

Additional technical information can be found in the Engineering Notes for each of the builds included in the GA Release.