-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query - functionality of "notify" and link with CSV #289
Comments
Next to
Which is the same as the regular weekly emails - which also updates the "last check date". So CSV is updated in both cases. |
Ok, this is a problem. As we basically need to use the "notify" button to schedule an alert on a particular day, this is occurring before we add external users to the alert. As such, the CSV is recording data/alerts that were never sent to the external users, which is not what we want. I think this issue has arisen as we've used the notify function to both schedule an alert, and notify users with no way to actually schedule the day an alert sends right? Happy to talk though this more in our catch up tomorrow. |
I can confirm it definitely creates a new CSV file when it runs, mirroring what @kylie-m said. Yes, needs some thought, as there might be implications of doing it the other way - no update of DB and CSV files. It sounds like the |
Just adding another snippet of info on the notify function. It seems to ignore the "Check alert since" date picker (at least for existing alerts that have run via the schedule) and uses the last check date as the "previous" date. This makes sense as it is updating the database and will mean you will never double-up entries in the CSV file. |
When creating a new alert, when I click "notify" does this add the related alerts to the CSV?
Or will this only occur after the alert is scheduled?
The text was updated successfully, but these errors were encountered: