FEEDBACK
-
I liked the new dashboard interface, it’s a lot easier and pleasing to navigate -
The new chatbot settings modal is great, much more accessible -
The search feature is crazy useful! I like its zoom and focus behavior -
The new emulator logs are very detailed and they will make debugging much easier -
It’s nice that we now can snap nodes to the grid, and also select them with Shift
SUGGESTIONS
Emulator
-
Make the production bot available in the emulator as well, maybe with a switch or dropdown to select the environment. Because right now i can only access the production version through the dashboard -
The chat in the dashboard should use the same style as the bot sharing page or as the emulator, they’re cleaner and snappier. Maybe standardize all chat interfaces.` -
Have better markdown support in the emulator, so we have the actual view even on dev mode.
Dashboard
-
The button Create chatbot in the dashboard should open a modal with templates to choose from and basic setup like bot name and language instead of creating an bot directly, so we don’t need to edit those after.
-
Have the bot settings available in the dashboard, the same modal from the Studio would be nice!
Editor
-
We should be able to change the message type after having selected one and defined values. Right now the change message type disappears after having typed in stuff. The button should remain and if the user wants to change types he must confirm losing the current settings. -
Option to select how long is the conversation timeout, right now it’s just 5 minutes which is too short for some use cases. -
I would like to able able to select many nodes or cards at once using CTRL, it would help in situations where I want to delete or move several items at once. -
The search results should have a label to identify the result type - node / card (with type) / transition / custom code / workflow etc. -
Sometimes the AI generates custom code with uncommented free text, which leads to compilation errors.
BUGS
-
Values are being added as default to array variables when I run array.push() -
When I update the label of a choice, the transition is removed
-
If i define a default value to a number I can’t remove it anymore, I should be able to make it empty/undefined by default instead of 0
-
When a workflow ends because no transition is matched in a node the chat ends but it doesn’t transition to the conversation end flow. Maybe it should? Since it’s technically an end.
-
The location title and address is not shown in Telegram nor WhatsApp, the bot sharing page doesn’t show the map nor the address/title, only the GMaps link, and the emulator shows only the title and the address with a link to GMaps. Could we have the same behavior of a map and labels on all (or most) interfaces?
Let me know if you need clarification on any!
Cheers
It’s amazing that we now can restart conversations from a previous point and all data will be restored too, helps wonder with dev and debugging!
Highlight the right active nodes/cards. Right now, it’s very easy to mistake which one is selected, which can lead to accidental deletions. See example below.
The position in the flow editor should be saved so that when we open a workflow or switch tabs, we have the same view as when we left. It’s cumbersome to have to drag around every time you switch flows.
Better separation of transitions leaving a node. Take a look at the choices below, we can’t tell which one goes where.
When we select a transition card, only the transition of that card should be highlighted instead of all transitions, so that we can know at once where it goes.
The default value of boolean variables should be undefined, or at least allowed to be undefined. Default for number variables also should be null or undefined instead of 0, and we should be able to clear them after having set a value in the input, with a button like below.
Allow variables in the retry messages too and make the input big like the main prompt message.
When a capture card doesn’t store information in a variable, the “Skip if variable is filled” checkbox should be disabled (greyed out), since it doesn’t apply.
In the node settings, we could have a personality rewrite toggle to choose whether we want the rewrite to be enable on that node. It should be disabled/greyed out when the Bot Personality is disabled, and it should be enabled by default when the Bot Personality is on. Fan art below:
and would speed up development even more!
A button to go back to the previous turn. The Replay from node feature is very good already but it still requires us to find the desired node in the editor and click it, when sometimes we just need to go back a few turns.
Show the custom code execution status in the emulator logs.
Hide environment variables by default on the dashboard
Selection of current/production environment
One of the conversation tags for WhatsApp (and other channels) should be whatsapp:userName, for storing the user’s display name which the messenger already provides. That way we can know more of the user’s info by default.
The conversation updatedAt should be replaced every time there is a new message in a conversation, instead of just when it is actually updated. It would help when listing the conversations and ordering them by the most recent one.
Roadmap of features and releases so that we know exactly what’s being worked on and what are the time estimates (You could use a tool like ProductPlan, to avoid building a whole interface for that).
New release summaries, so we know exactly what was added/improved/fixed
Cancel), but the engine extracted another one (
but I ask that you give some special attention to these issues and possible improvements because I think Botpress is almost too unstable for production right now.
