Menu Block: Save menu/options selection(s) into a variable of JSON Array

  1. What problem does this feature request solve?
  2. What is the use case for this feature?

It would be nice to save the user selection(s) from a menu block into a variable for use in other parts of the workflow. (Labels, runtime data, conditional execution, etc.). I realize this var could just be a textchoice var in a User Input block, buy my menu options happen further down in the workflow sometimes.

Please describe the functionality of this feature request.

When a menu block is added to the workflow, add the method that allows for Save to Variable to the implementation. A JSON array would probably be most fitting as their might very well be multiple options selected.

Is there anything else we should know?

Also, sometimes the menu options are not required, and it would be helpful to know when that usecase exists. I suppose a choice might be “nothing selected” or “not needed”, that would accomplish the same concept etc.

:trophy: Thanks for your insights and considerations, team.

Hi @Avocet,

Thanks for the feature request!

As a workaround, you can add a User Input block with a Long Text input, then use the Custom Interface designer to make it appear as a menu to end users.

This way, users see multiple options to choose from, but instead of being immediately routed to a specific branch in the workflow, the selected value is simply saved to the user input variable.

Hmmm interesting …. I have, however, alreaded vibe coded a Menu Block (with several options) and the user may or may not already know which option to select at the initial user input location of the workflow …. I’ll do some more thinking on this … the timing of the selection might be an issue as the user can decide after choosing a file upload which option selection should be made … hmmm.