Druid v1.66

Deployment Dates

The table below lists the deployment date of Druid v1.66 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

May 12, 2022 June 09, 2022 June 09, 2022 June 09, 2022

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

  • Adaptive Cards. This release introduces support for repeaters and full support for Microsoft Adaptive Cards Template Language. For more information on how to create Adaptive, see Adaptive Cards Steps.
  • Virtual nodes for menus. Creating menus (Hero steps with Input mapping empty and marked as flow last step) automatically transforms the menu options in virtual nodes. For every button in the menu, the bot takes the button value and tries to find flows that contain in the training phrases the button’s value. If the bot finds any flow, it will group the referenced flow under the virtual node.
  • Authoring referenced flows. This release introduces a powerful Flow Diagram feature for authoring flows and referenced flows. You can author the referenced flows (edit/create one) directly inside the virtual nodes or trigger flow steps, as you would do with any other flow using the Flow Diagram options.
  • You can choose to author complex flows in a new browser window.

    For more information, see Authoring Referenced Flows.

  • The VoiceText Channel is now active in Druid by default, dedicated to voice integration in Contact Centers with the voice service and the voice bot being delivered by third parties.
  • For more information on this channel, see VoiceText Channel.

  • Flow steps. The Skip if known setting available on flow step configuration, General section will move the dialog forward when the entity/entity field or Druid local variable provided in Input mapping already has a value in the conversation context.
  • The Code Editor is now available in the Portal and allows bot authors to set variables and set conditions on steps using advanced coding. It provides you with a set of predefined code template to help you define your JavaScript code.
  • Set variable

    Setting Up Conditions on Steps

    For more information on how to use it, see Set Variables and Setting Up Conditions on Steps.

Improvements

  • The ChangeConversation internal action was extended to support both conversation change and snippet refresh, eliminating the need to use a backchannel step for refreshing the chat snippet. If the Welcome Flow is set on a flow step with input mapping and the user is inactive for 15 mins (triggering the InactivityCancelFlow), to avoid the bot from entering a loop, the following error message is logged into the Conversation History: "[ChangeConversation invocation was canceled, because it was triggered from a welcome flow, and that would generate infinite loops.]". The conversation will remain in idle mode until the user writes something.
  • The Connector Host version was added to the Connector Host installer.
  • Debugging information was added to ConnectToHelpdeskClientMultichat error to address situations when two helpdesk agents click connect to live chat at the same time. To provide information on the helpdesk agent who wasn’t able to connect to the conversation, in the conversation history, the following message will be logged: "Attempting to connect to client conversationId {ConversationId} failed; probably another agent picked up this conversation."
  • For bots using bot framework version 4, a new cookie parameter is available in the webchat editor > General > Cookies section, DruidCookiesExpirationInDays that allows setting up the cookie expiry in days or fractional in minutes.

Bug Fixes

  • When creating a bot with more than one language or add a new language on the bot, all special messages (bot details, section Special Flows) are reset, they become orange, requiring manual setup of special messages.
  • Query timeout error is raised even after Portal users navigate from the Dashboard page to other pages.