Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

GA Release - 4.0.100 - February 2022

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

Core Product Modules

Experience Manager

Answers v2

  • The design for locking a question is updated to show the user details.

  • The Answers v2 KB can now export Labels along with the KB data. The Questions Sheet in the Excel file will have the KB data and its relevant Labels. The Labels Sheet in the Excel file will have all the Labels in the project. Going forward, the data export/import actions will use the .xlsx format only.

  • The .xlsx file structure is explained here.

    • When we import a KB using a new custom schema, rather than its original type, we will only import the data for the properties that are common. Other new properties will be ignored in the target location during import action.

    • When we create a KB using the custom schema, the user-defined properties will be exported in customData.propertyName column. For example, If we have the property firstName in the custom schema, the exported Excel header will be customData.firstName

    • Excel file header reference-

Primary Question

Question Variation

Voice Answer

Text/Chat Answer

Answer Screen

Labels

Guid

customData. propertyName

  • The search functionality is extended to search using the Labels, the data in Voice/ Text/ Screen/ Buttons, Question variations, Intent ID and the Content ID.

Flow Studio

  • Hide Message Bubble-This option is introduced to allow for accepting input utilizing a single input control with NO output rendered to prompt the user. This is present in the Single Input control. This is useful in scenarios where the expectation is an indicator is presented via another mechanism. For example when using a hook that rendered HTML5 directives or Adaptive Cards. In these scenarios, instructions for input are generally provided with the mechanism itself, making the additional bubble redundant.

    In previous versions of the platform, when you had a hook & single input combination, both controls would be rendered, presenting an additional message bubble with every hook render. More info in https://orbita.atlassian.net/wiki/spaces/OCS/pages/1659830303/3.3.9+Flow+Studio+Controls#Single-Input

  • The Bot formats the date and the phone number input type in a better way now. For example, the user input 9876543210 will be formatted as +1 (987) 654-3210. For dates, when the user input is February 9 2022, the bot displays in the format 02/09/2022.

  • In the Link Flow control, a new option called “Enable continuation of flow after completion“ is introduced. This allows the users to jump between the flows. More information in https://orbita.atlassian.net/wiki/spaces/OCS/pages/1659830303/3.3.9+Flow+Studio+Controls#Link-flow

  • One Output pin- This new option is available in the Choose One and Yes/No controls under the Choice tab. A new section to choose the number of output pins to display for the control is added. The new option, One Output pin will render only one output pin from the control in the Flow Studio canvas. This option lets the user connect the out pin of Choose One or Yes/No to the next control easily. This helps in places where the flow is the same regardless of the chosen option.

By default, One output pin per option will be selected which has been the default behaviour till now. This will give us output pins equal to the number of choices in the control.

Chatbot Settings

  • We have updated the Default Bot settings in v4.0.100. While upgrading the platform to v4.0.100, other existing copies of the ‘Default’ Bot settings of v4.0.98 if present, will be renamed as ‘Default legacy'. The reference made in the Bot provider OE node will not be changed by the system.

  • All Chatbot Settings (Settings, Custom CSS, Custom JS and Header) are editable except the Template. To update the Template settings, we should make a copy of the Default Chatbot settings file.

  • Previously when copying the Default chatbot settings, the Header content was not copied. This is handled now.

  • For Chatbot Settings, there are a few changes done as part of v4.0.98 Patch updates. Please refer to them here https://orbita.atlassian.net/wiki/spaces/OCS/pages/2143092942/GA+Release+-+4.0.98#Chatbot-Settings The changes are available in v4.0.100 as well.

Package Solutions

  • Auto indexing of content will happen when installing the Solution packages. Earlier this indexing process was done manually post the installation.

Experience Designer

Chatbot v3

  • For chatbot v3, there are a few changes done as v4.0.98 patch updates. The changes are available in v4.0.100 as well. Please refer to them. https://orbita.atlassian.net/wiki/spaces/OCS/pages/2143092942/GA+Release+-+4.0.98#Chatbot-V3

  • Now by using the property send_advance_message, we can pass different Value and Text data in the hook function. A simple use case will be in a Button action where the display text and the value passed to the backend can be different. This is similar to the submitQuery property in the v2 bot.

Sample code snippet

self.parent.OrbitaChatBotV3.hook('send_advance_message', `You chose an appointment for ${WEEKDAYS[formattedDate.getDay()]} ${MONTHS[formattedDate.getMonth()]} ${formattedDate.getDate()}, ${formattedDate.getFullYear()} at ${selectedTime}`, null, {
        date: selectedDate,
        time: selectedTime,
        timezone: timezone
    });

Release 4.0.100

  • Build number: 4.0.100-1645641079

  • No labels