Users observe that a process model that uses a custom email sender retains the email address value of the original environment where it was created instead of using the sender’s email in the new environment when imported.
In addition, the process model continues to display the old email address even when the email address has changed in the configuration files.
The custom sender used in the process model is configured with a static email address instead of a dynamic one such as a constant. Therefore, it is internally mapped to the hard-coded email address value that gets stored in the XML of the process model. As a result, the sender cannot be automatically mapped to new values when the configurations are modified or the process model is exported and imported.
These issues can be resolved in two ways:
That being said, the best practice for custom email senders is to use a constant (see Expression Email Address for more information) to ensure that the value remains dynamic. The same constant can be imported on all environments once and each environment can then have the email address that belongs to that environment.
This article applies to all versions of Appian.
Last Reviewed: March 2017
© 2022 Appian. All rights reserved.