Including an email address stored in a text field in an email notification
There's a workaround commonly referenced on the Community for including a calculated text field containing an email address in a notification that used to work like a charm:
1. Create the text field with Input Mask = Email Address
2. Apply/Save the field
3. Check "Calculated Field" and add a valid calculation
4. Apply/Save the field
5. Select the text field in the notification To, CC, or BCC field
All of a sudden this workaround is not working in our environment (SaaS v6.5.2). We are no longer able to select the text field in email notifications.
Anyone else experiencing this? Have you a found a workaround to the workaround (haha)?
Here are other threads where the workaround is referenced:
- Community Thread
- Email Notification
- Forum Thread
- Notification Issue
- RSA Archer
- RSA Archer Suite
- saas notification
- subscription notification
Yep, seems like the case even in 6.5 P4. Could be that workaround got fixed You can raise this to support, and if working as designed - open an enhancement idea.
There were couple of things "fixed" in 6.5 too, which used to work in lesser versions - could be on of those.
As for workaround to workaround, you can try ValueList instead, they are still visible for notifications.
Yep, appears a values-list field still works and is a good option if there's a small volume of known email address value options.
The bummer here is the calculated text field email address option was handy when needing to pull an email address from another non-calculated text field via a cross-reference. I'm not aware of another way to accomplish this except for Archer-to-Archer data feeds (which unfortunately SaaS customers cannot configure themselves like on-premise customers can). Ideas?
If you use the calculated text field email address workaround, keep an eye on corresponding notifications that reference these field. We've found that the text fields are being dropped from the notifications without warning if a change is made to the field and the field is saved even if the change has nothing to do with the email address input mask or calculation.
I would say maybe Custom Object might be one option to get value to the text field instead of the using calculation, but that is not always the possibility.
Other way is A2A DF like you said.
3rd option, enhancement idea
We are experiencing this issue as well. It used to work before we upgraded to version 6.6 P3 and now it no longer works for us. I see there is an idea on the Idea Exchange regarding this. I would recommend anyone experiencing this issue vote up the idea: https://community.rsa.com/ideas/3096