...

• 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.

...

• 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). This is also included in the v4.0.102 Patch.

  

• A new dropdown Dropdown display format is introduced for Choose One control Choices options. In the Choices tab, we may input the values as normal. Select the 'Show as Drop-down' option on the Directive tab. As a result, the Choices are now dropdown options. This option is unchecked by default. This is supported in Chatbot V3 only.

...

Image RemovedImage Added

Chatbot v3

• Peek View is a new feature for ChatBot V3. The virtual assistant appears to be partially open and some of the messages get displayed. The Peek view changes to the Dock view after the user interacts with the buttons/input elements, and the interaction continues. Peek view support is offered for monitors, tablets, and mobile devices.

"peekview":true property should be set in the ChatBot settings to enable this view. By default, it is set to false.

...

• 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 while transferring to a Live Agent. Sample code: . Please refer to How do I use directives? for more details.

  Code Snippet

  Code Block
  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 } }];

...

• 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-