It's useful to make sure that emails generated by a form go to an appropriate test account during the testing phase of building a form but go to the correct recipient(s) once the form is in production.
Example Scenario
For example, during the testing phase, you might want the emails to go to a test account, but once the form is live in production, the emails should go to the correct department (e.g., payroll).
You don't want the payroll department to receive test emails while you're still working on the form, and you also don't want to accidentally send test emails to real recipients once the form is live.
Managing Email Recipients
There are ways to automatically switch the email recipient based on the environment the form is being submitted from (testing vs. production). This helps prevent mistakes, like migrating a form to production that still references a test email, or needing to manually change the email address every time you move between testing and production
(Method 1) Emails Chosen by Form Submitter (Testing vs. Production):
- This method allows form testers to input their own email addresses for testing purposes. When the form is in the test environment, the user enters the test email(s), while the production environment uses pre-defined, hard-coded email addresses.
- Refer to Jadu Forms: Set Email Recipients by Environment Using Emails Chosen by Form Submitter
(Method 2) Emails Defined by Form Builder (Testing vs. Production):
- In this method, both test and production email addresses are pre-defined by the form builder. The environment logic automatically sends emails to the respective addresses, with no need for the form submitter to enter their email during testing.
- Refer to Jadu Forms: Set Email Recipients by Environment Using Emails Defined by Form Builder