Blocked on #216313
Summary
When the scheduled reporting task is available, we want to have to ability to send email notifications when a scheduled report is complete, along with an attachment containing the generated report. Similar to the notification service, we can have a config specifying which preconfigured email connector to use for this notification.
We propose a custom reporting email action that can be scheduled at the end of the scheduled report task that reads the base64 encoded generated PDF/PNG from the report document and adds it as an attachment to the email, subject to any max size limitations from nodemailer.
For this first iteration, we suggest a pre-populated email message. In the future, we can allow users to customize their email message.
There is some discussion of whether we should only email the person scheduling the report, pulling that email address directly from the user profile. The outcome of this discussion may change the definition of done below.
Definition of done
Blocked on #216313
Summary
When the scheduled reporting task is available, we want to have to ability to send email notifications when a scheduled report is complete, along with an attachment containing the generated report. Similar to the notification service, we can have a config specifying which preconfigured email connector to use for this notification.
We propose a custom reporting email action that can be scheduled at the end of the scheduled report task that reads the base64 encoded generated PDF/PNG from the report document and adds it as an attachment to the email, subject to any max size limitations from nodemailer.
For this first iteration, we suggest a pre-populated email message. In the future, we can allow users to customize their email message.
There is some discussion of whether we should only email the person scheduling the report, pulling that email address directly from the user profile. The outcome of this discussion may change the definition of done below.
Definition of done