Version 1.74

Release Date: 19.12.2023

ENHANCEMENTS

• Now, the files recevied from the users can be sent to 3rd party services! With this new development, for instance, image recognition service could be used to extract knowledge from the image if necessary. In the HTTP node, "form-data" is added as content type. By choosing this content type and filling other requested fields, a request can be sent to a 3rd party service.
• OpenAI services can now be integrated through Microsoft Azure as well, and customers can choose between using OpenAI or Azure OpenAI. In addition selection of model-id, api-key and vendor is possible now.
• ChannelID standardization is implemented. If you are integrated with Knovvu VA with external APIs it is expected to use pre-defined channel-IDs. This will make easy to search, export and reflect the conversations. Please check here for the related list. If you are using other channel-id which is not in the list, you will still get service but it may effect the reporting.

IMPROVEMENTS

• OpenAI API Key and Vendor can be selected accordingly in the Administration/Settings/Add-on AI features section.
• Deletion of start node from the flow is prevented and the node no longer can be seen in the node palette.
• For IVR channel, TTS voices can be reached through MinIO without requiring an authentication.
• In the VB node, "Not Enrolled" output is added to clarify is the user has registered to Voice Biometric system or not. If the user is not registered, the node will exit from "Not Enrolled".
• Attunements for the UI colors has been made to have a more holistic view.
• The end node, which previously included the 'keep the conversation' checkbox, has been removed. Instead, new nodes have been introduced, each exhibiting distinct functionalities in different flows. Here is the details of 3 new nodes;

1. Return to Start Node:
   This node is exclusive to the main flow.
   It operates by utilizing flow turns, and it is named "Return to End" to emphasize these turns.
   It mimics the functionality of the existing end node with 'keep the conversation on.'

2. End Node:
   Specifically designed for use in subflows and action flows, it is only visible in their respective node palettes.
   It seamlessly continues the flow from where it entered or left off.
   Retains the visual representation of the current end node.

3. Exit Node:
   Applicable to all types of flows including main,subflows and action flows.
   Defines the functionality of the existing end node with 'keep the conversation off.'
   Terminates the session, and upon receiving a new message, initiates a new conversation with a new session ID.

FIXES

• Some of the connection lines of the nodes were not proparly visible.
• UI supported languages were shown wrong.
• System prebuilt VA's were permitted to delete, now they do not have delete icon and cannot be deleted.
• There was a delay problem when starting the testchat.
• HEIC file type was not successfully being added to "Ask attachment node".
• HEIC extension was not displayed in custom files.
• In the dashboard page, "Fallback messages" graph was loading slowly.