we have an issue with "Configuring Custom Email Senders". When we firs

natasav over 10 years ago

we have an issue with "Configuring Custom Email Senders". When we first implemented that functionality,wWe followed the instruction on Appian 6.2 ,and migrate those conf files till now on Appian 7.0.
We have the same integration on all environments (DEV,UAT,PROD) the only difference is the mail address on each server.
For example on DEV it is bpmsdev@company.com and on PROD it is bpms prod@company.com.
And the issue is , when on some process instance "sent mail " is executing from PROD , actually it is like sending from DEV or UAT.
How it is possible and does anybody faced the same situation and how it was solved?
Thanks in advance,Natasa...

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 10 years ago

The problem is that your custom sender is not following the best practice of using expressions:

<address name="customUser">
<expression>=toemailaddress(user(cons!CUSTOM_USER, "email"))</expression>
</address>

if you do not use an expression and hard-code an email address then when the model gets published that address is hardcoded in the model meaning that if you export the model and import it then the hardcoded email address will be preserved, that's why you see that when your models on DEV get promoted to PROD they still send emails with the DEV's address.

Use constants and expressions instead as shown in the example above. There's a full example here too (at the bottom in the section called Expression Email Address) forum.appian.com/.../Configuring_Custom_Email_Senders
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 10 years ago

The problem is that your custom sender is not following the best practice of using expressions:

<address name="customUser">
<expression>=toemailaddress(user(cons!CUSTOM_USER, "email"))</expression>
</address>

if you do not use an expression and hard-code an email address then when the model gets published that address is hardcoded in the model meaning that if you export the model and import it then the hardcoded email address will be preserved, that's why you see that when your models on DEV get promoted to PROD they still send emails with the DEV's address.

Use constants and expressions instead as shown in the example above. There's a full example here too (at the bottom in the section called Expression Email Address) forum.appian.com/.../Configuring_Custom_Email_Senders
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data