Chatbot

• The FAQ widget is now available via messaging API
• The Checkpoint widget is also exposed via messaging API from now on

Robot

• Creation of an Exchange Connector which does not fetch e-mails from a shared mailbox works again.

Robot

• Add missing German translations

Chatbot

• Triggers can now be set to the following device options:
  • all, mobile-only, desktop-only
  • This allows for use cases, where clients want to use different triggers on desktop and mobile devices, i.e. trigger fullscreen on mobile and chatbot window on desktops

• The registration process for new workspaces has been removed because we don’t offer self-registration anymore
• Fixed an issue, where the use of variables would not work in the user-input widget content field

Chatbot

• The new FAQ widget can be configured by selecting a FAQ from the AI module, and an optional introductory text.
  • This FAQ widget allows end-users to ask questions in free-form text, which then get matched to the configured question&answer pairs. The most similar question (and answer) is shown to the end-user.
  • The end-user has the possibility to repeatedly ask questions, or continue with the conversation as defined in the story builder.
  • The webchat includes a new UI element showing the “answer card” as result for a user question.
  • End-users can optionally vote (thumps up/down) directly on the answer card. The reporting API can be used to analyze the votes.
• We can now set Triggers based on query parameters
  • This has to be set by Development for now, please contact us if needed

• Fixed an issue, where a long filename would not be shown correctly when uploading in webchat
• Upgraded some libraries, which also fixes the issue that throttling in Chrome does not work for the webchat

AI

• FAQ:
  • Customers can create FAQs and configure its questions and answers, which can be integrated into the chatbot with the new FAQ widget.
  • The import wizard enables the upload, and automatic import of questions and answers from CSV & Excel files.
  • The testing page lets customers evaluate the FAQ with different user input texts, showing the most similar questions including a similarity score.

• Classifier: Fix small visual UI bug in classifer list, and on classifier testing page.
• Classifier: Fix anonymization for classifier template predictions, use correct project ID.
• NER: Fix datetime format for certain input texts (no effect for end user)

Robot

• When using arrays in the body of an API endpoint, refer to the documentation to understand how to use it correctly: 3rd party APIs | JSON-in-the-request-body

Chatbot

• Reworked the communication between Webchat and Server for more stability
• The content type of files uploaded by users gets stored and is available for further processing (i.e. with Robot)

Chatbot

• Fixed a bug where # in the URL did not fire the trigger correctly
• Show triggers on the story listing page (you can also add / edit triggers directly on the story list page)

Robot

• Worksteps can have a warning result now. This means that the Workflow will continue but there did something go wrong while executing the Workstep
• If at least one Workstep ends in the warning state, the whole Workflow will end in the warning state too
• Files downloaded with the Download File Plugin are now scanned for viruses
• Fixed a bug where creating an Exchange Online connector was not possible because Microsoft changed the length of the client secret parameter

Chatbot

• Fix avatar upload

Robot

• The navigation between Workflow Builder and Workflow Protocol has been made easier. There are links on both pages that allow you to navigate to the opposite side.
• Bug fix where downloading Trigger data caused an error if the data was already anonymized.

Authorization and Authentication

• API keys can now have different roles assigned to it. This is to prevent having one API key for a project that could be used for all services. The following roles can be assigned to an API key:
  • api.automation
  • api.conversations
  • api.messaging
  • api.reporting
• All existing API keys got all four roles assigned, so they continue to work as before.

Chatbot

• Fix handling messaging api requests (added delay)

Platform

• Data Security: This Enterprise-only feature allows project owners to set the retention period for data stored by aiaibot.
  • Users have a range of different categories of data to choose for scheduled deletion, including User Data across the modules Chatbot, AI and Robot
  • Only project owners are allowed to view and change these settings, which are found in the new Data Security tab in Project Settings
• Reporting API: Improved response time of Reporting API queries

Chatbot

• Improved file uploads and anti-virus scanning of uploaded files

Robot

• Added a modal dialogue which notifies the user of any unsaved changes, whenever leaving a Connector
• For Automation APIs we now allow multiple headers with the same name
• New Plugin: Convert Text To Date Objects
  • This plugin converts texts which contain a date and/or time to a standardised format and stores it in a date or datetime variable