GA Release - 4.0.106
GA Release - 4.0.106 - May 2022
The list below represents the features, updates, and fixes included in the Orbita Voice GA Release for May 2022.
Breaking Changes
The Template code of the Chatbot v3 using the Attributes has been fixed. Please make sure to add
<div id={elementId}
inside the<body>
tag. Refer Chatbot V3 | Template node for the updated sample code.
Â
Release v4.0.106
Build number: 4.0.106-1652817118
Core Product Modules
Chatbot V3
Previously, while loading the bot, the audio output of the first bubble did not always render correctly.
This has now been resolved.
Core Platform Capabilities
Orbita Chatbot Design System
Multi-SelectList - Users will be able to list down the Choose Many control options as a list of items in the Chatbot V3. In the Directive tab of the control, select the checkbox 'Show as a Multi-Select List' to render in List style.
The design of the Flow Studio Rating control has been updated for the Chatbot V3. We will be able to show the labels for minimum and maximum values in the new design.
The design of the Slider option for the Rating Control has been updated for the Chatbot V3. The Slider design can be enabled by going to the Flow Studio> Rating Control> Directive tab> Use Slider checkbox
Experience Designer
The platform now supports Twilio SMS and IVR communication status callback functionality.
The Twilio status callback property can be used to determine the delivery status of Twilio SMS or IVR calls made from the system. Please refer to Using Twilio node | Status call back for more information on this.
Â
Flow Group Intent is now available. This will merge the functionality of the Repeat Intent, Previous Intent, Orbita Flow Message Intent, FreeText Intent, No Intent, and Yes Intent nodes on the Experience Designer into a single Intent node.
The Experience Designer's Flow Manager Built-in flows have also been upgraded. Go to Experience Designer> Hamburger Menu> Import> Build-In> Orbita Flows> Flow Manager
General
Orbita NLP training takes place automatically now whenever an environment is deployed or restarted.
It will no longer be necessary to manually deploy the Google Agent to start this training.
The Orbita’s NLP is used for entity extraction primarily and not Intent detection like Google NLP. For more context behind this, please refer here 3.2.17 Orbita NLP Entity Extraction Pre Hook
Â
Insights: We have stopped capturing the Google Health Check requests made to Actions in the Insight logs. Google monitors deployed Actions to verify they're available and responding to user requests. The intention behind this is to not skew the data captured on user interactions.
Â
The Global Intents from the Intents listing page are removed. Now only the project-specific Intents will be visible.
Invalidating the CDN cache is now possible using the options provided in the Organization settings. Go to Global Settings and User profile menu > Settings > Organization> Invalidate CDN to set up the path of the CDN cache to be invalidated.
Once done, the Bot will take all assets from your CDN newly. Please input relative path only. More information in Experience Manager Settings
Skyhawk Portal
A few bugs in the Skyhawk Portal have been resolved.
Previously, we were unable to build a new Care Circle for the Patient Care Team, and the old Care Circle was not correctly shown. This has now been resolved.
The Patient did not previously display on the Message Center popup screen. As a result, speaking with any Patient or Care Team was impossible. It has been resolved.
Patch v4.0.106
Build number: 4.0.106-1654688661
UI issues with a few Flow Studio controls are fixed for the Chatbot v3 including the Slider Rating control, Choose Many control List view and the default Rating control.
When the Experience Designer had a lot of Flow Group Intent nodes, the system didn't always trigger the right Flow Manager node. This has been resolved. The Intent with the specified State will now be triggered first.
The blocker with the SalesForce Live Agent interaction has been fixed.
While using the mic, we were seeing a socket connection namespace issue with Google Speech to Text service. This is now handled.
SOAP Web services can be connected from the Orbita system now. Please refer to How to connect to SOAP Web Service? for more information.
Â