Posts: 5
Joined: Thu Apr 28, 2016 11:45 pm


Wed May 04, 2016 4:12 am

After chasing down a problem for longer that I care to share (conflict between splitter and regexp), I think it would be helpful if there was some visibility into the internal mechanics, at least at a high level.

For example, a way to show:
* Output of Filter processing
* Output of Splitter
* Output of Normalizations
* Output after Pattern Reductions
* Matching REGEXP
* Matching Model

You get the idea. This would greatly simplify tracking down SIML code that is disconnected from expectations. :) It could output to the "Studio Console Debug" window or whatever.

And, since I'm dreaming, a 'trace' attribute on "significant" elements (ala RegExp and Models) with the intention that you are testing a certain model or Regexp, so when the Bot is traversing these marked elements additional trace is output.

In the long run I expect this would significantly reduce support questions.


User avatar
Help & Support
Posts: 320
Joined: Fri Oct 25, 2013 9:20 pm

Re: Tracing

Wed May 04, 2016 7:37 am

Thank you for the valuable Suggestion. I will surely consider these features for the next iteration of Chatbot Studio update. 8-)

Return to “Feature Request and Suggestions”

Who is online

Users browsing this forum: No registered users and 3 guests