Druid v1.40
Deployment Dates
The table below lists the deployment date of Druid v1.40 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 West-Europe (PROD) *.Druidplatform.com |
|---|---|---|
| May 13, 2021 |
May 13, 2021 |
June 10, 2021 |
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.
Improvements
- Druid Entity Designer is an all-in one place graphical tool that provides bot authors with the following major benefits:
- Better understanding the entity models coming with solution templates.
- Easier visual creation of new entity models.
- increased productivity as bot authors can copy the label of entities / entity fields and use the label in step messages and input mapping and for fields mapping.
- Solutions: The References mechanism now also brings the entities used on flow steps. This is particularly useful when exporting solutions which only contain flows and entities (no integration). For more information, see Exporting and Downloading.
- UiPath Flow Step: When adding a new UiPath flow step, it will now automatically create a connector action (called <your flow name>-<step name>) and a task (named "Start Job"), which you can configure to accommodate your UiPath integration.
- UiPath Connector App: When testing an UiPath Connector app, you will now see additional error information (instead of the general"Could not authenticate" message), to further help authors in debugging connectivity issues.
- Druid details for UiPath integration (for starting a job): The callback address and secret necessary to set up the Orchestrator webhook to allow Druid directly start a job based on a chat request, are now also available in the UiPath Connector app page.
- The [[MatchingFlow]] system entity now has an additional field: "FlowCategory", which you can use to filter multiple intents, if needed. On the Intent Not Recognized flow, the [[Intent]].OtherFlows field, of type entity list referencing the [[MatchingFlow]] entity, displays all the intents predicted by the NLP engine.
- Added Druid Endpoint BaseURL to Druid Services (Administration menu > Druid Services) with the possibility to copy the URL to clipboard.
For information on how to use it to understand existing entity models or to create new ones, see Entity Designer.
Bug fixes
-
When uploading a train set that contains intents which have a value specified in the Response column (in default language), but have no information for the additional one, the message content in default language is duplicated for the additional language.
