There are multiple problems with handling workflow inputs in run workflow modal:
1. Objects and arrays
Similarly to when executing workflows on deployments there are not all possible types supported. Objects (dictionaries) and arrays (lists) shall also be supported. Are there any others? What is more - currently we distinguish strings, integers and booleans basing on default values types. If default value is not set, then we are assuming that workflow input shall be provided as a string.
2. Error handling
Checking if the value is not empty is not proper => integer 0 is treated as empty value and the error is shown to the user blocking executions submission.
3. Boolean parameters are shown in different way
Both - force and ignore_failure parameters are boolean. One is shown as dropdown list, second as toggle. We should use toggle for both.
1. Check if there are any other way to get input type other that checking default value's type.
2. Update way of checking inputs type (if any other possible). If not possible extend already implemented to handle new types (at least object and array) and provide type selector for inputs without type identified
3. Use new components (implemented within ) for handling workflow execution inputs