Set Required Flag for Forms either static or dynamic | Voters

Set Required Flag for Forms either static or dynamic

Matthias Kellers

I would like to have a dynamic required flag for forms - then you don't need to duplicate the field if you want to have it dynamic. I would like options like they are for the conditional visibility

April 1, 2025

Michiel van der Veeken

Matthias Kellers Thank you for your feedback. The current configuration options are already quite extensive and at times rather complex to explain or apply. For that reason, we are cautious about further expanding these configuration options, in order to keep the use and setup of the forms accessible. This may indeed mean that some form elements need to be implemented in duplicate. Could you describe an example use case?

Matthias Kellers

Michiel van der Veeken So for example if we have a department dropdown and then a textfield below it. It should be visible for all departments but for a one department it should be required - for the others not. And yes it would get more complex. I could think of two ways to do it: Either we have a small script to determine the required state or we just do it like with the conditinal visibility

Michiel van der Veeken

Matthias Kellers Thank you for the example. Within the current capabilities of HelloID, you could approach it as follows: Make the text field required and link it to a data source that takes the dropdown as input. This data source returns a dummy value (which you can ignore) and an empty value for the required selection. This way, the user needs to enter a value themselves for the required option, while for the other options the data source returns a dummy value. Please let me know the outcome of this suggestion.