How to Use Teneo Suggestions to Improve your Conversational AI Solution
Teneo suggestions tab will give you an overview of different errors and other potentially problematic issues. They are automatically detected and prioritized in your solution for you so you can easily address them.
The suggestions tab is relevant throughout the entire development process of a solution. You can find the suggestions tab in the solution’s backstage under the optimization area:
Different categories of errors
The suggestions tab consist of four different kinds of categories to make it easier to identify which type of issue is being displayed in the suggestion list:
- Text – Text related issues such as: Flow trigger has no description, flow output answer is empty
- Robustness – Robustness related issues such as: Node has only Conditional transitions, Continue transitions and Library updates such as a newer TLR available
- Condition – Condition related issues such as: Invalid conditions, empty conditions
- Scripts – Script related issues such as: Integration script is empty, script node is empty
Which suggestions to address first
The suggestions tab comprises four different suggestions:
- Fatal errors
The suggestions are grouped and sorted based on their severity from most severe to least severe. This way, the most ‘acute’ problems are at the top of the suggestion list.
The listed issues are accessible for you to immediately access the location in the solution where the issue can be corrected by double-clicking the item in the list.
If you don’t want to address the issue right away, you can select the issue that does not require immediate action and press ‘Acknowledge’ at the top. However, issues listed as Fatal errors or errors cannot be acknowledged since they require your attention.
Issues that are listed under Fatal errors must be corrected, because they are causing an Engine load failure and this is preventing the solution from running at all. Fatal suggestions come from the Engine and are also displayed in Try out.
Issues that are listed under Errors should be addressed because they cause a certain part of the solution, for instance a flow, a script or an integration, not to run.
Issues listed under Warning can cause problems whose impact is limited. These potential problems do not prevent the solution from running. You should consider these issues a part of the “solution’s hygiene” which should be maintained.
Issues listed under Information suggestions are more ‘nice to have’, which cause no direct problems in the solution but are against shared conventions or best practices. For instance, missing descriptions or deviation form naming conventions.
In the top right of the suggestions tab you can find the filter tab. In the filter tab you can filter among the suggestion to find specific categories of a certain severity, look through acknowledged issues and perform text search.