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 5 Next »

GA Release - 4.0.104 - April 2022

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

Core Product Modules

Experience Manager

General

  • Multiple emails were incorrectly triggered while editing a Recurrence Event on the Calendar.
    This is now handled.

Flow Studio

  • On the Flow Details page of Flow Studio, we can now bulk add Utterances. The Events can also be defined as part of these Utterances. After the intent has been created, all of the details may be viewed on the Intent page.

  • In the Choose One control, new choices for selecting options from a predefined range of possibilities will be available. This will reduce the effort to recreate frequently used options. Under the Choices tab, choose Select from List to go to this option.
    A pre-defined list of choices will be shown, with the ability to reverse their direction. These can only be utilised with the One output pin option by default.

Chatbot v3

  • Requests to the Bot will now include contextual information about the page where the Bot is embedded.
    The information is found in msg.req.headers["x-orbi-headers"]. IP addresses, hostnames, and other information can be obtained.The Function node in Experience Designer may be used to retrieve specific context header objects by calling the msg.alexaRequest.getContectParams() function.

  • Previously, when the user gave text inputs instead of selecting buttons on the chatbot, we allowed the user to reselect the buttons even after providing the text input. This is now under control. When text is entered instead of a button selection, the buttons are disabled. Similar behaviour can be seen in the date picker, rating control, and so on.

  • We have added the capability to add a Text Break as a directive. The Text Break can be used on the chatbot where we need to provide breaks between conversations, like transferring to a Live Agent. Sample code: 

    msg.payload.orbita.directive = [{
    type: 'textbreak',
    options: {
        primaryMessage: "Transferring you to a live agent.", //mandatory
        secondaryMessage: "12:45pm", //optional
        tertiaryMessage: "Sharron has entered the chat."  //optional
    }
}];

  • autoFocus is a new property added to the Default Chatbot Settings. This option is set to true by default. When true, the focus is automatically managed and the chatbot's focus goes to the next action item. If false, the attention remains on the action item unless manual input is made.

Calendar

  • Earlier, we were receiving an error displayed while deleting a monthly recurring meeting from the Calendar. This has now been resolved.

Experience Designer

Live Agent

With our new Live agent support we can connect with SalesForce Live Agent and AWS Connect. For implementing the support to the Live Agent services, please connect with support@orbita.ai

General

  • In the Experience Designer, we will now be able to obtain the revision ID of the deployed flow.
    To acquire the revision ID of the flow published, ORBI.utils.getRevisionId();

  • We will be able to acquire the current Flow or Tab name where the Experience Designer Node is present by sending the node as an argument to the method ORBI.utils.getFlowname(node);

  • The Send SMS node has got the ability to choose the type of encoding to happen. By default, Auto detect encoding type will be selected. There are GSM-7 and UCS-2 encoding types available now.

Release 4.0.104

Build number: 4.0.104-

###########################

Patch 4.0.102

Build number: 4.0.102-

  • The flows were malfunctioning when utilising Flow Studio Link node controls in conjunction with a Flow Manager node configured to not store data to Orbita. This has been taken care of.

  • Domains with '_' can now be entered as Allowed domains in Application Settings.

  • The phone numbers will be formatted in “+1 (XXX) XXX-XXX” US Canada format. This formatting will get applied only when the user has selected either Input Type as Phone number or selects Validator as Input Validator Type as Phone (US/CAN).

  • The mustache tags used in the End Node control of the Flow Studio is being printed as tags themselves, instead of the actual value. This has been taken care of.

  • No labels