Druid v1.60
Deployment Dates
The table below lists the deployment date of Druid v1.60 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 17, 2022 | March 17, 2022 | March 17, 2022 | March 17, 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.
- Execution timeout on all connectors at APPs level
What's New
- Sensitive data manipulation. For chatbots using bot framework version 4, you can capture user sensitive data and send it to third-party systems via connectors. In this regard, a new field is available for entity field, Holds Sensitive Data.
- A new special flow, InactivityCancelConversation is now available and allows bot authors to customize the way chatbots handle the cases when the inactivity threshold is reached out. For more information, see Inactivity Cancel Conversation Flow.
- Delay message functionality is now available on flow steps. You can now activate a delay of 1 to 10 seconds between pre-action and the step message and everything that comes after (post-actions). For more information, see Metadata.
- You can now provide clients with the possibility to choose the priority of their live chat and place them in the queue(s) based on that priority. In this regard, a new parameter, PriorityLevel is available on internal actions ConnectToHelpdeskAgent and TransferHelpdeskCall.
- Authenticate Conversations with SSO Teams. For chatbots operating in the back-office in applications that use Azure AD authentication (e.g., Office 365 applications), bot authors can set the chatbots to operate on behalf of the users by using a token generated by the user’s Azure AD client. For more information, see Authenticate Conversations with SSO Teams.
- Druid Vision. Druid API engine now performs OCR and data extraction from Romanian Passports.
- Druid Vision. Added support for OCR and data extraction from Romanian Identity Cards for Romanians born outside the country. This introduces two new fields in the response: “cnp.CountyOfBirth” and “cnp.CountyOfBirth.Id”.
If you’re using such a field in Input Mapping on prompt steps, the sensitive information will be encrypted using a Druid proprietary encryption method right from the moment the user inputs data in the chat and remains encrypted while being transmitted to the connector (the data is encrypted end-to-end while being transmitted through the Druid platform).
The connector will decrypt the data using a Druid proprietary decryption method and send the data to external systems.
For more information, see Live Chat With Multiple Queues or Internal Actions.
For Romanians born outside the country, “cnp.CountyOfBirth.Id” is “80”. For more information, see Romanian Identity Cards OCR.
Improvements
- Input mapping errors are now logged in Conversation history. In case an error occurs due to an input mapping assignment (e.g., the specified entity/entity field does not exist, or the data validation fails), then the issue is logged in conversation history, similar to errors occurred in SetVariables.
- Add execution timeout on all connectors at APP level. A new field is now available for connector APP configuration, Execution Timeout that allows you to set the maximum number of seconds a request that uses the specific APP (integration task) is allowed to execute. The default value is 60 seconds.