The Try Out panel has been re-designed in Teneo 6 in order to provide a more intuitive way to show the processing path of each test input. While in Teneo 5 the UI has shown four panels for its Try Out (Inputs, Try Out, Response Info and Engine), the new Teneo 6 Try Out comes with a cleaner look which shows only the basic information on the standard view, while offering an Advanced Try Out in a separate window with more details than ever before. The below screenshot illustrates the “clean” view on the standard Try Out. As you see, it indicates the relevant information around the answer, and icons regarding the processing path.
You can also add input parameters by clicking Add Parameter about the text input box. It works in the same way as the Inputs panel in Teneo 5 or earlier versions.
Now, if you want to “deep dive” into the details such as parameter changes, input processing results or annotations, you can click the Advanced… button at the top right to open the Advanced Try Out window. Here is an example of the Advanced Try Out:
Input, Path, Output and State correspond to the information that had previously been shown in the Response Info panel of Teneo 5 or earlier versions. Input contains classification results, annotations and input processor results. You can click on Variable Change , Input Processor Results , Script or Global Listener to see detailed information.
Path contains information regarding the match, triggering and all the steps from raising to dropping a flow.
As you can see here, the match requirement to trigger the flow “User wants to order a coffee” has been a Class Match on the class CAN_I_ORDER_A_COFFEE .
Output contains output text and output parameters.
In this case here, there are two parameters being sent back within the response together with the answer text.
State contains all flow variable values and global variable values after the input is processed. As in previous Teneo versions, you can select the variables you are focusing on as Watched Variables to have them preselected in a separate view. In the following screenshot, we are focusing in the Watched Variables on the bot’s name which is stored in a global variable called Lib_sBotName .
Messages provide system outputs such as printlines in executed Groovy code and also warnings. These system outputs were shown in the Engine panel of Teneo 5 and earlier versions.
If you want to know more about Try Out in Teneo 6, please take a look at the documentation here and feel free to ask us here in the Forum any questions you might have!