You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no indication of whether or not a field was hidden from the user, so it can be very difficult to discern if the user intended to accept the default for a field, or if the user simple never had the chance to change the default.
I am unable to think of any reason anyone might actually want conditionally hidden fields in the email. If the user was unable to modify the field, then its value will always be the default.
If it does end up needing to be optional, my suggestion is to add another checkbox to hide hidden fields in the "Email Content" section when editing a recipient (next to the existing "Hide form data from email?" and "Send email as plain text? (HTML will be stripped)" checkbox fields).
I would also suggest this apply to fields inside of a conditionally hidden form step.
The text was updated successfully, but these errors were encountered:
There is no indication of whether or not a field was hidden from the user, so it can be very difficult to discern if the user intended to accept the default for a field, or if the user simple never had the chance to change the default.
I am unable to think of any reason anyone might actually want conditionally hidden fields in the email. If the user was unable to modify the field, then its value will always be the default.
If it does end up needing to be optional, my suggestion is to add another checkbox to hide hidden fields in the "Email Content" section when editing a recipient (next to the existing "Hide form data from email?" and "Send email as plain text? (HTML will be stripped)" checkbox fields).
I would also suggest this apply to fields inside of a conditionally hidden form step.
The text was updated successfully, but these errors were encountered: