DRUID 5.7

Deployment Dates

The table below lists the deployment date of DRUID v5.7 across Druid Clouds. To view the Druid Releases Calendar, see Druid ChatBot Releases.

Druid Cloud Community *.community.Druidplatform.com	Druid Cloud US *.us.Druidplatform.com	Druid Cloud Australia *au.Druidplatform.com	Druid Cloud West-Europe (PROD) *.Druidplatform.com
February 02, 2023	February 16, 2023	February 16, 2023	February 16, 2023

These release notes give you a brief, high-level description of the improvements implemented to existing features.

If you have questions about your Druid tenant, please contact support@Druidai.com or your local Druid partner for more information.

What's New

• Custom Code. This release introduces the business operations layer and enables you to implement business rules that always apply either to the flow engine, web views, forms, or external applications. Using the Custom Code integration task, you can perform data validations and raise errors when validation fails or do extensive calculations (e.g., forecast calculations).
Note:   If you have a hybrid or on premise DRUID deployment and you want to use the business operations layer you should install DRUID Connector Host version 5.7.

Defining the business rules requires medium to extensive JavaScript knowledge. To streamline the authoring experience, DRUID provides you with a set of predefined code templates.

…

For more information, see Custom Code.

• Voice AudioCodes channel. The Voice channel through VoiceAI Connect from AudioCodes enables you to deliver a seamless voice experience to the users talking to your DRUID virtual assistants.



Important!  This channel is in technology preview as a tenant feature.

This channel provides you with powerful benefits and extensive options to have full control over the conversations authoring. To mention a few:

• Capture a collection of Dual Tone Multi Frequency (DTMF) Digits.
• Provide users with a flawless conversation and avoid interrupting the conversation due to language change.
• Extensive configuration for handling bot delays.
• Configure what happens on conversation disconnect.
• Let VoiceAI Connect know why the bot disconnected a call.

With this new channel, DRUID introduces new features:

• A new system entity field, [[ChatUser]].CalleePhoneNumber that stores the bot’s phone number.
• Two new conversation context entity fields: [[ChatUser]].VoiceConversationTerminatedReason and [[ChatUser]].VoiceConversationTerminatedReasonCode that store the reason for which the call is disconnected and its associated code.
• Three backchannel steps: SetVoiceActivityParams, SetVoiceSessionParams and hangup.
• New data is logged into the Conversation History which is useful for debugging purposes: all voice conversations begin with “[Voice start event]”. that helps you to measure the time from the moment when the call was initiated (bot picks up the call) until the bot says the first message, and Speech-to-Text Confidence Score shows the confidence level of the recognition received from the speech-to-text provider.

For more information, see Voice AudioCodes Channel.

• Kanban views. Kanban views allow you to work with the graphical visualization of your records. They are a good way to help you stay focused on finishing existing work before starting new work and ensuring that top priority work stays top priority, thus improving efficiency.



For more information, see Kanban Views

Improvements

• WhatsApp channel templates (for both Meta and Nexmo) have been extended to allow authors to add description to hero card buttons by for each button in the "buttons" array add the channelData object and set the "description" property.



For information on how to dd description for hero card buttons, see WhatsApp Meta Message Templates or WhatsApp Vonage Message Templates.

• Two new fields are now available in within the conversation context system entity [[ConversationInfo]]: [[ConversationInfo]].CurrentFlow and [[ConversationInfo]].PreviousFlow which store the FlowId, FlowName, FlowDescription and FlowCategory of the current and the previous flow. They provide you with a easy way to trigger back to the previous flow once a trigger flow step is executed.



For more information, see Trigger Flow Steps Configuration.

• The BF4 webchat widget has been adapted to Conversation time machine translation. When Conversation Time Translation is enabled on the bot, the language selector on the webchat snippet is replaced with a World icon (non-selectable) because user can use other languages than the bot languages. The webchat snippet automatically adapts to the new language code; therefore, if the user sends a voice message in a language different than the bot languages, the voice message will be sent to the STT service in that language.



For more information about Conversation Time Translation, see Conversation Time Translation and Building Multi-Language Bots Using SDL.

Bug Fixes

• Fixed NER issue where InvariantDate field type was not always extracted.