Closed calexh-sar closed 2 years ago
We need a unique identifier for each email, separate from study_id. Maybe the Subject can serve as the identifier. Something like get_email_data(subject='My Email Subject') (Study_id is already sent with each script call)
It's possible that subjects could be dynamic, which is problematic using them as identifiers. We could use task id.
My current solution doesn't work for configurators. They won't know the workflow_id. Now looking at a combination of workflow_spec_id and study_id.
Bug in validation. We are looking for element documentation when it doesn't exist. Sentry error
For Approvals workflows and likely other Categories, we need to know when emails were sent. Some emails are only sent once, but many can be resent due to required updates. In the latter case, the configurator would need to know the date and time for each occurrence.
Work on this ticket includes providing a script that can be used to return the following information about each email sent: