Allow form field default values to have complex patterns based on user selection | Voters

Allow form field default values to have complex patterns based on user selection

Juan Roldan

In some cases, we may want to create a certain default value for a field based on previous selection made by the user. This can include literals and even multiple fields references.

The default value should be adjusted automatically until the field becomes visible.

June 16, 2024

Kevin Campbell

An example from my experience is to load the defaults for all dependent fields from the driving field selection, in this case it is a day-2 operation's entity. This shows the user the current settings for the entity as defaults. The users can choose to change any of the values from the defaults or leave them as they are currently set. This works the first time a selection is made, when all the dependent fields are empty, but if the user selected the wrong driving field value and switches it to another value the defaults don't update for the dependent fields. This risks the user not recognizing this fact and proceeding with the prior selection's default values changing the entity and negatively impacting the entity in Kubernetes.