indico
Improve registration email notifications
Is your feature request related to a problem? Please describe. When event managers fill the templates for notification emails, they expect the full markdown body they filled to be the sole content of the emails that will be delivered. However, turns out the system fills for them some content, and such action is not indicated elsewhere nor is intuitive and leads to confusion and many time incoherent content being sent.
Describe the solution you'd like We propose to create a "Preview email" button near the markdown content that, when clicked, displays a dialog that shows how would the email look like before being sent. This way the user can check not only the full email body, but also how the markdown written gets rendered. This will allow to edit the body accordingly.
Describe alternatives you've considered Other alternatives would be not to include default content in the email template, and instead pre-fill the default text area widget with the current text. This solution would require to handle the placeholders accordingly, which is not so easy to do since those placeholders are currently rendered inside the jinja template, and would likely require to perform naive text replacements.
Indeed, making the full email editable is a no-go because it contains lots of HTML formatting which we REALLY do not want to pass through the WYSIWYG editor.
Adding the ability to show a preview sounds like an excellent idea. The tricky part is what to use in the preview... some registrant? Dummy data (hard for custom fields)? Empty field data? Dummy data for known personal-data fields and empty for others?
PS: You may want to s/event/registration/ in the title of this issue since it seems to be just about registration emails.
Might be worth to see if we can reuse the "new" React email dialogs for this
I think this might be hard because those are not ad-hoc emails but configuring text snippets that are then included in the registration notification emails (which are highly dynamic and generated from Jinja templates)...
The tricky part is what to use in the preview... some registrant? Dummy data (hard for custom fields)? Empty field data? Dummy data for known personal-data fields and empty for others?
My initial approach was the latter. To fill as much information as possible, leaving placeholders (like {user_name}, for example) for what we can't.
PS: You may want to s/event/registration/ in the title of this issue since it seems to be just about registration emails.
Done 👍