We should have a feature where each email sent is tracked by easyprocess and it records if it threw an exception.
each application we have that has emails runs into the same issue. We hear from the users that an email was not sent and then need to prove it was. Then we end up implementing a feature to note the emails.
The most robust we have done is tracking in the db when emails are sent and to who. Then when the inquires come in, we check the db and are able to say, no the email was sent.
The same is for exceptions. Each time we send an email, we check for failure and record it in somewhere like batch job history or db.
but building this is extra work and first needs to go through the step of looking for the proof and not having it, so we build out the feature to prevent the not knowing in the future.
Can EASYProcess do this instead?
Matt M has a need for this feature and wanted in previously in early 5.1
Email Exception Tracking by EASProcess
-
- Posts: 472
- Joined: November 16th, 2021, 11:15 am
- Contact:
Email Exception Tracking by EASProcess
Last edited by CathyC on October 7th, 2022, 2:25 pm, edited 1 time in total. word count: 184
Tags:
-
- Posts: 472
- Joined: November 16th, 2021, 11:15 am
- Contact:
Re: Email Exception Tracking by EASProcess
Is the current log feature enough to help with this? if the logs saved in PD were kept for 30 days, would that be enough to answer the support issues that come in that previously fueled these features
word count: 38
-
- Posts: 472
- Joined: November 16th, 2021, 11:15 am
- Contact:
Re: Email Exception Tracking by EASProcess
I talked to Matt M on this and we think the logs are good enough. so this is resolved now
word count: 20