Helvia.ai Release 5.63.0
10 October 2024
Last updated
Was this helpful?
10 October 2024
Last updated
Was this helpful?
Our latest update introduces the use of LLM nodes to improve data extraction processes. By identifying and extracting specific parameters from user inputs, such as product names, customer locations, service requests, etc., your chatbots can better understand user intent and provide customized responses.
To take advantage of this new feature, you need to define within the prompt in the 'LLM node' the json schema. You also need to check the 'Response is in JSON' checkbox and define the JSON Property and the variable the extracted value will be stored as.
To use this feature, you need to have the LLM plugin activated.
In our previous release we updated our analytics to be split into tabs for easier access and improved readability. To reflect these changes in our export, we have made updates to the exported PDF report. The missed questions table has been removed from the Automated Answers section and a new section for missed questions has been created, showing the count, the top 50 missed questions for the selected period, as well as a histogram showing missed questions per day.
We have enhanced our testing process for automated answers within our console to now indicate when a question has been missed and the default fallback response is triggered. This provides better transparency and helps bot authors better understand when a question is missed during the testing process.
We have introduced a new 'Input Collection' node, which combines the 'Question' and the 'User Input' nodes, along with some added functionalities. This new node is currently in Beta.
To use this node, you need to add the question and define the question data type. You can select if you want to make this field required by checking the 'Required Field' checkbox in the advanced settings of the node, set a keyword to allow the user to skip the question and you can also set the question ID to use as a variable. Last, you can control the preferred rendering of the node. When preferred rendering is card, you can configure the maximum allowed characters and enable to display a multi-line.
The 'Input Collection' node has two outgoing edges to enable you to configure the exit path.
Bot authors can now configure additional settings for validations and error handling when using the file upload node. This includes specifying accepted file formats, setting file size limits, handling cases where the end-user types instead of uploading a file, and handling unhandled errors.
The structure of the current file-upload node has been updated to support these configurations. You can draw edges to continue the flow based on the validation results.
This improvement makes it easier to ensure that the right files are uploaded, leading to a more seamless user experience.
Bot authors can now easily access the variable of a file upload question and extract only the URL. The default variable value displays organized URL and file name information as {{file.url}} and {{file.name}}. Additionally, authors can take advantage of the base64 representation with {{file.base64}} to easily upload files to external systems using the 'HTTP Request' node.
We have expanded our date variable options beyond just {{today}} and {{currentDate}}. Now, you can access all date parts in numerical form with variables such as {{CurrentMonth}}, {{CurrentDay}}, {{CurrentHour}} and {{CurrentMinute}}. This added flexibility allows for greater customization and ease in constructing the specific dates you need.
These variables are in the bot's time zone.
With this update, organization admins can now track the number of times a 'Media' node has been triggered, as well as the appearances of other nodes such as 'LLM', 'File Upload', 'Analytics tags', 'HTTP Request', 'Channel Action' & 'Send email' nodes.
To view these metrics, within your organization's Analytics, select the Decision Trees section.
Find the flow (decision tree) you want to see additional metrics for, and click on the eye icon in the Actions column. You will then see the decision tree with metrics showing the views per node for the selected period.
