This mApp provides a method of checking email monitoring activities from within your Cherwell environment, eliminating the need, in some cases, to have access to the log file for the Email and Event Monitoring service.

This should be especially useful for SaaS customers, who will not have direct access to the Server or its logs. It functions by tracking the Journal ? Mail History records created when the Email and Event Monitoring service receives an incoming email.

If the email monitor definition is configured to record a Journal for incoming emails, in most cases, even if an email/event monitor action fails with an error, the Journal record is still created.

Journal ? Mail History records allow you to view the full email (From the Trebuchet Mail table) when viewed from a Form Arrangement. When doing so, the end-user has access to an ?Executed Actions? dialog that will provide a list of Email/Event Monitoring actions performed on the email, including any relevant error messages.

As a result, this mApp provides a lookup table object, named ?B20 Mail History Tracking?, to allow the user to find the Journal records being created for failed inbound emails.

To use this object, the user simply needs to create one (1) record in this lookup table, and then save and refresh the record.

After doing this, any emails sent or received (that also created Journal records) will appear in the form arrangement tabs, and the user may view any error messages [?]


Beyond20 Contact and Location Information
Website: https://www.beyond20.com/cherwell-development
Washington, DC | 1325 G Street NW, Suite 1020, Washington, DC 20005
(202) 540-9601
Tempe, AZ | 60 E Rio Salado Pkwy, Suite 900, Tempe, AZ 85281
(480) 603-9292
San Diego, CA | 4445 Eastgate Mall, Suite 200, San Diego, CA 92121
(858) 324-1727

System Requirements

Platform Version Requirements: 9.1.1 - 9.6.2



IT Service Management