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

Core Product Modules

Experience Manager

General

• Previously, while logging into the system, the auto-complete option was activated for the Username. Now, the auto-complete has been disabled on the Admin portal and Engage portal login screens as a security measure.

• We've disabled the display of all auto-generated slots in the Deployment page during publish activity. The warning notice will only apply to the custom Intents that have been created.

  Open

  

Answers v2

• The Labels now have a restriction of 30 characters. The user will not be able to input more than 30 characters when creating a new Label.

• We will be alerted if we are creating multiple Question variants. The duplicates will be highlighted.

  Open

  

  Duplicate Question variations warning message

• Users upgrading from v1 to v2 KB will only be able to move one KB at a time to ensure a smooth transition.

Chatbot v3

• Bot v3 now accepts microphone input. The feature works the same as in bot v2 by enabling the mic with the property micInput set to true. Please referhttps://orbita.atlassian.net/wiki/spaces/OCS/pages/1933901852 for more info.

• Contextual information about the page where the bot is embedded will be included in the Bot data. The x-orbi-headers property under msg.req.headers can be used to get these facts. This property stores information about the query string, IP, Cookie, Headers, User-Agent, Session, and so on. The content header object is accessible using msg.alexaRequest.getContextParams() as well.

• Similar to the v2 bot, the keyboardPlaceholderText property in the ChatBot settings may be used to control the placeholder for keyboard input.

   

• The thumbs up/down feedback method is now supported in Bot v3. More information is available here. https://orbita.atlassian.net/wiki/spaces/OCS/pages/1339654166

• The Bot v3 now has a redesigned user interface. This design adheres to the WCAG guidelines and uses semantic markup. The design is enabled by default in the default Chatbot settings, allowing us to automatically send upgrades to the default bot in future versions. To construct any bot, it's a good idea to make a duplicate of the default Chatbot settings.

Flow Studio

• Preview in Chat-Bot This button on the Flow Studio canvas may now be used to preview a chatbot flow under development. The Bot preview will open in a new tab using the Default Bot Settings in the project. In order for this functionality to perform properly, the Agent must be deployed.

  In the Experience Designer, the user must have the Flow Manager flow with Flow Group intent set up for existing projects. To support this functionality, a new Flow preview intent will be built. The Experience Designer flows will be configured automatically for new projects.

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