cancel
Showing results for 
Search instead for 
Did you mean: 
CHJESSON
Staff
Staff
Status: Reviewed

We are currently storing a lot of detail around the emails ingested by Capture in the Chorus database (AWD061/62/63) but there is no current mechanism to display this information holistically within the Chorus Portal.
This means that the data are currently only available by SQL query (the GetCapturedEmail operation oh the AWD Email Service returns info from those audit tables, but only for a single email at a time).
The main use case here would be an indicator of "failed" emails so that remedial action could be taken.
I think the view would just need to be a filterable, pageable tabular list of ingested emails.

1 Comment
Karen_Hunter
Staff
Staff
Comments welcome.  Please provide clarity for your audit expectations for the Capture results:
1. successful ingestion of an email resulting in a new work item in Chorus where the mailbox then files that email in a Completed Folder on the email Server.  What available criteria would you expect to use to "filter" on audit table data?
2. failed ingestion of the email where no work item is created and the mailbox files that email in an Error Folder on the email Server.  Same question here.  Is this just visibility to those logs so you can monitor and act effectively.

This audit interface would allow an administrator to check the email Server and take appropriate action to reprocess that email.  Is there an expectation that the administrator would "clear" the messages in any way or will it always show as having failed on that date?  Is this really admin or is more of a "monitor or dashboard" for this ingestion channel