Tenjin Icon

Release Notes - v2.44 - 5 January 2024

Version: v2.44
Release date: 4 January 2024

New Features and Enhancements

Automatic Generation of QnA Questions Using Answer

To help both new and advanced users alike improve their QnA knowledge base, Tenjin can now generate new alternative questions using the information in the answer as a guide. Having more than one question for each QnA can increase the chances of correct answers being found by making sure the questions are worded in a way that improves matching.

In addition, if you would like to modify the way the questions are generated including the information used, along with the number of questions supplied, there is the ability to modify the prompts, giving advanced users complete control over the generation of the questions. Just in case, there is also the ability to revert the prompts back to their default value.

This was a new feature that has had quite a bit of input from users already, and it'd be great to receive feedback on the impact it has with your knowledge base matching, so please get in touch with your thoughts on this new feature.

Project Flow and Assistant Flow History / Auditing

We already have the capability for users to view past executions of flows and their associated debug values, and we have now extended this further to provide more auditing information around who has changed project and assistant flows, and when; whilst also giving Administrators the ability to make a historic flow live and export the historic versions to a file.

By providing this update it has three major benefits:

  1. There is now a complete audit of all updates made, by who, and when, which makes it easy to identify changes.
  2. If a change has been made that generates an error, the flow can be reverted to a previously working state quickly whilst the issue is investigated elsewhere.
  3. If an administrator incorrectly deletes a project flow, it can now be recovered quickly and imported back to its previous state.

Deprecation of "Submit QnA Question Suggestion" Flow Action

After analyzing how the Submit QnA Question Suggestion flow action has been used and its impact on the QnA knowledge base, we have made the decision to remove it from future releases of Tenjin. This means that the QnA knowledge base will now only receive suggested alternative phrases using questions asked by customers. This update has been triggered by a change made in the last release: Improve Display and Use of QnA Alternative Phrasing.

As part of this specific release, we are deprecating the flow action and removing its functionality, which means it will continue to appear in flows but will no longer perform any action. It is also no longer possible to add it to new flows from the add action panel. The flow action will be completely removed in a future release, but only after it has been removed from all customer flows; we will be in touch if this impacts you.

Minor Updates / Bug Fixes

  • Improve help documentation for persistent users in the new webchat, including updated code example that can be copied.
  • Improve layout, selection, and visibility of project flow input and return parameters, removing it from the main flow properties area and treating it the same as a flow action.
  • Enhance the visibility of search inputs by adding a default label so that their function is more obvious.
  • Allow QnA topics to be queried using an expression.
  • Improve performance of analytics generation to minimize the impact it has on other more critical services.
  • Improve the project and assistant flow help template to include more flow related help articles, which were not previously available from the left-hand navigation in the help pop-up.
  • When Expert Assist questions do not contain a user's name within the administration area, because they are raised anonymously, make sure the layout remains consistent and does not appear broken.
  • Improve the expression engine within flow to support more number types and remove errors where it incorrectly said a 'double' was not a number, causing errors in flow under specific circumstances.

Share this article

Comments

0 comments

Article is closed for comments.