We have several process flows that send emails to employees to notify them of various things, especially registration for training. The employee email address is read from HR11. While these flows were in development and testing we have inadvertantly sent emails to employees that should not have gone out. We are looking for suggestions to keep these emails from going to employees and instead have them sent to a tester or pre-defined email address. Ideally, we'd like to have the UAT tester be able to control the email address they are sent to without having to contact a technical resource to change the email address. Also, we do not want to have to modify the process flow between test and prod.
We have considered changing the hr11 email address for everybody in test to a testing email address. This creates extra work for the sys admin after every refresh and mucks up the data some, but allows for user testing to change the email address on hr11 for test subjects without the risk of emails being sent to every employee.
We've also considered using a configuration file or other coding changes to tell the PF which product line it is in and where to send the email. This means that the PF is not executing exactly as it would in prod and also requires testers to contact IT to update the config file before each test. It may not allow emails to be sent to multiple testers of a single PF.
Are there other approaches that we haven't considered? Do you use one of these approaches? What problems or successes have you seen with it?
Thanks, Amy