GA Release - 4.0.110

Owned by Bharathi Manohar (Deactivated)
Last updated: Oct 06, 2022 by Alexia.Sibony (Deactivated)
7 min read

GA Release - 4.0.110 - July 2022

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

Breaking Change

  • Reiterating the change that went in the v4.0.108 Patch update. Due to the introduction of the new bubble loading indicator design after the update to v4.0.108, customers who used custom CSS classes for the bubble loading indicator encountered issues.

    While using custom loading indicator classes, we need to add display: "none" for the typing-indicators class to avoid overriding by the Product Loading indicator.

Release v4.0.110

Build number: 4.0.110-

Core Product Modules

Chatbot V3

  • The dock float Bot was not rendering after the user interacted with the Peek View Bot while using the Carousel's Filter Option. It's now taken care of. The dock float Bot will render once the user interacts with the Peek View Bot.

  • For the Chatbot Settings, we have added support to have the Title, Description and Key be visible while working with them.

     

  • Reiterating the v4.0.108 patch update that was done. In the V3 Chatbot, when we specified "audio": false in the Chatbot Settings, the Speaker icon was retained in the Bot. Now it's fixed. Only when "audio" is set to true will the Speaker icon be visible.

New Feature: EDIT CONTENT FROM V3 CHATBOT

  • As a business user, upon clicking on the Pencil icon on the Bot bubble, you are now able to edit Flow Studio content directly from the chatbot conversation. You will be redirected to the Flow Studio Control of that content. See screenshot below

    Note: The user must be logged in to the Experience Manager as an Admin User to enable this feature of editing from the Bot directly.

    Click the Pencil icon to directly land on the Flow Studio content

     

  • The capability to edit Answers V2 content directly from a V3 Chatbot session has been added.
    By clicking the Pencil icon on the Bot bubble, we will be taken to the Answers V2 Fact page, just like with the aforementioned feature.

    To make this functionality of editing directly from the Bot available, the user must be logged in as an admin user to the Experience Manager.

 

  • The V3 Chatbot conversation's Adaptive Card content can also be edited. The same as with the aforementioned feature, we can access the Adaptive Card edit page by clicking the Pencil icon on the Bot bubble.
    To render the Adaptive Card, we had the option of using the Experience Designer technique or the Flow Studio Adaptive Card control. In either case, the user will be brought to that Adaptive Card's Edit screen.


    The user must be signed in as an admin user to the Experience Manager in order for this functionality of editing directly from the Bot to be available.

Flow Studio

Core Platform Capabilities

Orbita Virtual Assistant Design System

Experience Designer

  • We used to get an error message on our Experience Designer Debug message on refreshing the Host page of the Bot V3 saying that the "Input text not set." The problem is now addressed. Only if the socket connection is broken will the notification keep appearing.

Experience Manager

  • As a Bot developer, we can specify which Intent should be triggered for a particular input pattern given by the Bot User. This is made possible by using the Regexp Entity check box in the Slot Types> Lists. Please look at https://orbita.atlassian.net/wiki/spaces/OCS/pages/2320793601 for more information on the Regexp Entity option.

 

  • In the Kibana Insights, the Index pattern property express.voiceAnalytics.voiceAgent.device.name was not getting properly captured in the Voice Agent Dashboard Summary [Beta Release]. This is now handled and we can see the updates clearly.

 

  • For the Flow Studio content we create, instead of having one Slot per Flow, we will only have one Slot called OrbitaMessages which will include all the Slot values from all the flows. Every time we deploy, the system will rebuild the OrbitaMessages List from all the flows available.

    This removes clutter from the Lists > Slot Types page. The support is given for both Alexa and Google deployments. By this, we overcome the problem of having a limit on the Slot count specific to the Agents.

    Please refer here Nomenclature of auto generated Intents and Slots for more details on autogenerated Intents.





  • We have made the description for the chosen schema readily available visually on the Content listing page. Hovering your cursor over the schema or going to the description area on the page will bring up the description.

The description will also be available visually on the Schema listing page.

 

General

As a best practice, have separate content for Voice and Text tabs in the Content Editors. This will help deliver the content appropriately through Audio output (fetched from the Voice Tab) or through Chatbot conversations (fetched from the Text tab).

In the Voice Tab, use the Insert SayAs Tag icon to select the type of that content appropriately. Please refer to How to add content to the Voice tab? for detailed steps.

 

Patch v4.0.110.1

Build number: 4.0.110-1660655334

  • In Chatbot V3, the issue with maintaining the order of Flow Studio controls rendering on the Bot is fixed now.

  • The OrbitaMessages Slot created as part of the autogenerated Flow Studio Slot will not have the Numbers and Yes/ No values added to them. These will be excluded to avoid confusion between OrbitaMessages slot value and other common slots.

  • While making changes to the Flow Studio content, any change to the Autogenerated Slot will only happen after deploying to the Agent. This message is displayed in the OrbitaMessages Slot under the Lists menu.

 

  • While adding Button values in Flow Studio> Single Input control, the relevant values were not created in the OrbitaMessages Slot earlier. it's handled now.

  • The ability to obtain the revision ID of the deployed flow using the ORBI.utils.getRevisionId(); function has been restored in the Platform.

  • While using the CLI package Orbita CLI to export the project, the TLS configuration (if enabled) in the HTTP Request node of the Experience Designer, was not properly exported. This is now fixed.

  • In the Chatbot V3, with enableArrayResponse set to true the Flow Studio Custom Hook node was not triggering and the Adaptive card was not rendered in the expected conversation order. This is handled now.

  • The Chatbot V3 Bootstrap Carousel was not working out of the box. We have made the fix in the patch deployment.

  • The intents weren't appropriately matching the type of data the User chooses in the Bot when utilising the Flow Studio for various controls with the Bot. This matter has been resolved.

    Please keep in mind that while utilising the Submit action on an Adaptive Card, you must also add the
    'A-Submit' Event to the FreeTextIntent.

  • We encountered a problem earlier when attempting to save modifications to an Answers V1 Knowledge Base Fact. This has been fixed and the patch has been applied.

  • When selecting more than 15 options in the past using the Flow Studio Choose Many control, we were unable to get all of the selected values in the Experience Designer. The ability to manage 20 alternatives picked using the Choose Many control has now been introduced.

Â