Here is a use case, which is purely a UX (transparency of automation) need:
Two issues:
- User needs to know what happens if the fields are left empty. Often an automation applies a default value, we need the user to see that before they hit Run.
- Either (simple) just a manual comment in the button form (‘defaultvalues when left empty are xx xx etc)
- or (which is better) to-one relations get a default value setting in their field configuration
which then should be shown in the button form.
- in this specific example below, numeric field gets assign ‘0’ instead of empty. This is a problem and assumption that should not be there. It leads to DATA LOSS
(the existing field values) because people think 0 means ‘not changing’ or they need to manuall remove the 0 to not overwite the existing values.
