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
Create a Form with a Text field, Date field, Date and Time field and Time field. Add a valid email address to the Form Email
Add form to a Frontend page.
For Date and Date and Time fields, you can add any value to it. For the Time field, set 4:00 PM as its value.
Submit the form.
Notes:
The date format is inconsistent for some fields, and this is mostly caused by Dojo and how it handles Date/DateTime/Time fields in the form. For Date and Time fields, Once a value is placed in this field type on a form, there are other two hidden fields created in background, and they separately save the date and time, although with a different format: yyyy-MM-dd and HH:mm, instead of yyyy/MM/dd hh:mm:ss a. Notification email sends the field's value with yyyy/MM/dd hh:mm:ss a as its date format, but the other two additional hidden fields are included in the notification email as well. This may cause confusion among email recipients.
The Time field's value is sent with 24hr (HH:mm:ss) instead of 12hr format (hh:mm:ss a).
The Date field format is slightly different than Date and Time: it's yyyy-MM-dd. We should replace it to yyyy/MM/dd so it matches with the Date format from a Date and Time field and it would be more easy to read and consistent for email recipients.
Depending on the Country/Region, dates and times could be read differently (see https://en.wikipedia.org/wiki/Date_format_by_country for more details), so we should allow users to customize the Date/Time format of these fields when a notification email is being built. A config property like
NOTIFICATION_EMAIL_DATE_TIME_FORMAT=yyyy/MM/dd hh:mm:ss a NOTIFICATION_EMAIL_DATE_FORMAT=yyyy/MM/dd NOTIFICATION_EMAIL_TIME_FORMAT=hh:mm:ss a
Could be added to the codebase and, upon fields verification when an email is built, we could send a default value in case the config is not set (again, using the suggested values from above).
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity within the past 90 days. It will be closed in 30 days no further activity occurs. Thank you.
Reproduced in 3.2.4. Steps:
Notes:
Depending on the Country/Region, dates and times could be read differently (see https://en.wikipedia.org/wiki/Date_format_by_country for more details), so we should allow users to customize the Date/Time format of these fields when a notification email is being built. A config property like
NOTIFICATION_EMAIL_DATE_TIME_FORMAT=yyyy/MM/dd hh:mm:ss a
NOTIFICATION_EMAIL_DATE_FORMAT=yyyy/MM/dd
NOTIFICATION_EMAIL_TIME_FORMAT=hh:mm:ss a
Could be added to the codebase and, upon fields verification when an email is built, we could send a default value in case the config is not set (again, using the suggested values from above).
The text was updated successfully, but these errors were encountered: