More Improvements to Studio's UI/UX

Share Feedback & Ideas
1

Suggestions

  1. [:white_check_mark: ADDED ]I liked the new “Advanced configuration” section in the Capture Information card, it really helps to declutter. One suggestion though: if I click on an item, it should show up expanded already, so we don’t have to click twice to get to the setting.

  2. — Now we have autocompletion for objects, which is amazing.

  3. I would like better logging for Infinite Loops. It would be nice to see the nodes and workflow names. Right now it looks like this, which is unreadable:
    An error occurred in the error handler. Abandoning. [Error, Infinite loop detected. (wf-7a646a9757 (nd-24b220c23e) --> wf-7a646a9757 (nd-5c7ff86985) --> wf-7a646a9757 (nd-01f808e9fb) --> wf-7a646a9757 (nd-714f75de65) --> wf-7a646a9757 (nd-4dd414610b) --> wf-7a646a9757 (nd-24b220c23e)). Flow: wf-7a646a9757 | Node: nd-24b220c23e]

  4. Botpress Studio sessions should be longer or reset on usage. I have to log in everyday, and sometimes i am logged out while working on the bot, which is annoying.

  5. [:white_check_mark: ADDED] I would like to select many nodes at once to drag them around the flow editor and organize them.

  6. I would like to move nodes (multiple if possible) to different flows.

  7. I want to be able to duplicate/copy nodes and cards, because a lot of times the logic is the same between nodes and cards and I am forced to created them from the start.

  8. When I want to regenerate custom code or a transition condition because the variable have changed, I have to modify the label, press enter to get an undesired code, and then change it back to the previous label to get the new code.

    • ezgif.com-crop
    • My condition checks if a parameter value is 8, but I had changed the variable name, so now I have to update the label, and then change it back to get the code with the correct name.
    • In short - codes and conditions should be regenerated by simply pressing enter. (Arguably this would reduce the workload of GPT, since I would need to generate the new code just once)

  9. The condition code box should be bigger by default and not just when you click on it, because sometimes conditions can be lengthy.

  10. Bigger variable names - 25 characters is too little, I like to have descriptive names and also words in Portuguese are bigger.

  11. Bigger node names with special characters allowed - 20 characters is not enough. Also, in Portuguese many words use symbols like ~ ^ ç á. So not having this greatly reduces the correctness and descriptiveness of the names.

  12. Go back/Undo button in the simulator. I mentioned this on another topic but I am asking for it again because I am really missing it when I make simple updates on cards and nodes and want to see the new behavior.

Thanks for the work you guys have been putting up in the new Studio, we can see it getting much better with each release! Cheers

1 Like
2

Hey @devguilherm!

Wow, thank you so much for the detailed feedback you provided :raised_hands:. That’s awesome!

I’m passing this on to the Product team.

We’re constantly looking to improve the Botpress building experience so please, if you have anything else to add, feel free to let us know. It can only be beneficial!

6. I would like to move nodes (multiple if possible) to different flows.
You can copy a single node by right-clicking on it. You’ll see the copy option. Copying multiple nodes at a time is not possible yet.

1 Like
3
  1. I liked the new “Advanced configuration” section in the Capture Information card, it really helps to declutter. One suggestion though: if I click on an item, it should show up expanded already, so we don’t have to click twice to get to the setting.

This is done :slight_smile:

1 Like
4

For this point, there is a description for the node, you can add all the details you want there. I don’t think it is a good UX when it comes - for example to sub workflows - accessing a variable from a sub workflow.

What do you think?

5

I have submitted the rest as Feature requests/enhancements.

Thanks for your continuously organized feedback.

1 Like
6

Hi @devguilherm ,

Issue number 5 is applied and deployed :wink:
use SHIFT and drag if you are using windows.

Thanks :slight_smile:

1 Like
7

That is true, but the description can only be seen when you open the node. The name should be descriptive enough that you don’t have to open it to know what it does. Bumping the limit to 30 characters would help already.

We can change the card name from which to access the sub workflow variables, it doesn’t have to be the same as the flow. The system could also automatically convert special characters to regular ones, ç becomes c, â/á becomes a, and symbols like ? become _.

1 Like