Outgoing Test Environment email

We have a script that is run post-copy to take every email address in the environment and replace the ‘@’ with an ‘~’ effectively destroying the email address, but leaving it intact.  Then no jobs have to change and no replacement has to happen.

This also allows flipping the email address back on easily if needed for testing through IT or super users.

We copy PROD to QA every two weeks on a schedule and this post-db copy script is ran automatically as part of the process before bringing QA back online so it doesn’t impersonate PROD.

I use post-copy script with updates on fndcn_config_param_tab, fnd_setting_tab and plsqlap_environment_tab. First one table is related to email account settings: username, pwd, host, etc,.

Do you really want the emailing off in your Test environment?  If off or addresses messed with, how do you tell if your events work before deploying to production?  How do users find out about background job issues?

We leave emailing on in Test.  We also add the database name in the subject of the emails.  Then we turn off most of the scheduled tasks only turning them back on for testing of that process.

Yes, we definitely want the emailing off in TEST or QA AND want the email addresses altered as well.  It only takes one time of a test environment spamming customers or suppliers with already sent invoices or already sent POs to create an absolute mess (been there, done that).

We turn the emails on in a controlled fashion and replace/update the email addresses when required for testing as part of the final process.

We have the database name in the subject line of emails too, but believe me customers and suppliers have no idea what that means.

@MWILSON - how do you get the database name? Would love to add this.