Using the default value field for a form element then deleting it messes up automation

[DOUGLAS THOMPSON]

Here are the steps to reproduce.  Pretty sure this may be a bug:

1. Create a form/request for a portal
2. For one of the text fields, set the 'default value' to something.  Make sure the key is named so you can reference it in a rule (flow).
3. Create an automation that will process the form field with an 'if', something like {{if(exists(forms.last.my-field-name.trim))}}Field Name: {{forms.last.my-field-name.trim}}
4. Submit the form through the portal, and the default value should show up
5. From the form, for the field default value, delete the default value
6. Re-submit, and the automation thinks a value is there which causes the 'if' to pass, but nothing comes through
7. Go back to the form, delete the old element, create a new element with the same key but do NOT set the default value.
8. Submit the form again.  Now the 'if' statement is honored.