Chorus EQM - Ability to add system/environment level email overrides

[cpapendorf]

We have identified a potential risk in the EQM emailing capability which we’d like to mitigate by requesting an enhancement.

With regards to emails being sent out via Chorus in the Non-Prod environments during testing, if the user incorrectly provides actual production data (e.g. a client’s email address) there is no system level fail-safe to prevent test case emails from being sent out unintentionally to these parties.

We've been advised that it is possible at a process level, but we would prefer this to be configured at an environment level instead as a over-arching fail-safe.

We’d therefore like to request that a new field be introduced (possibly in the AWD Configuration Console where the mailboxes are captured).

This field would allow us to capture, at a system/environment level, an override email address(es) that will always be used when sending emails, instead of the ones provided in the Chorus work items.

Field: Override Email Address

Format: semi-colon delimited text values of the email addresses which should always be used when sending emails for that mailbox (e.g override1@email.com;override2@anotheremail.com).

in the Production environment, either the field would be left blank, or alternatively you could provide an explicit checkbox to indicate if it should be used or not.