Smart Action, unpredicted behaviour (?) field value about forest-rails HOT 2 OPEN

Hi @daniel-costa, thanks for the report. I think the expected behaviour is to always have the "not present" case in both usecases.

from forest-rails.

I get it from the "rails" perspective. My concern is more in the UX logic. When does the user chooses it has to be sent and has to be blank? And if he is aware of it, how could he revert blank to nil.

For example, if it is established the rule "If you focus the field, then the value becomes it's content. Therefore an empty field will result in a blank field." . What about the user going to a field and using tab to go to the next ones. He might go in a field and set it to blank while he was trying to move trough the form.

Anyway, I thought you should be aware of the behaviour and maybe reference it somewhere in the documentation.

from forest-rails.