Skip to main content
Solved

Is there a way to use the Emailer Transformer where it gets the list of email addresses from a text file?


juliarozema
Contributor
Forum|alt.badge.img+7

Basically here is the need: right now workbenches run (Using FME Desktop 2020.2 and Task Scheduler) and the email addresses are typed out within the Emailer Addressing "To" parameter.

We would like things to be more easily updated. For example, if someone is no longer on the team, or if someone is new on the team, we would like to simply update a text file and ALL of our jobs will be updated.

 

I tried reading the text file in, aggregating the addresses into one long string separated with a comma, but I wasn't sure how to assign the value to a User Parameter.

(I tried a couple things and failed)

 

Thanks in advance for your help.

@danminneyatsaf​ 

Best answer by chrisatsafe

Hi @juliarozema​ ,

You can use a FeatureMerger for this. After aggregating to concatenate all of the email addresses into a single feature (comma separated), you can merge it onto the feature(s) that trigger the Emailer. In the FeautreMerger, set the requestor and supplier to the same character like "." or "x". This will merge the aggregated attribute onto the stream that is going into the Emailer.

imageIn your case, the Creator is the rest of your workspace (goes into the requestor port), and the aggregate feature from the Text file goes into the supplier port.

 

From here, you can set the email to from the attribute value containing the concatenated list of emails.

image

View original
Did this help you find an answer to your question?

3 replies

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • Best Answer
  • March 17, 2022

Hi @juliarozema​ ,

You can use a FeatureMerger for this. After aggregating to concatenate all of the email addresses into a single feature (comma separated), you can merge it onto the feature(s) that trigger the Emailer. In the FeautreMerger, set the requestor and supplier to the same character like "." or "x". This will merge the aggregated attribute onto the stream that is going into the Emailer.

imageIn your case, the Creator is the rest of your workspace (goes into the requestor port), and the aggregate feature from the Text file goes into the supplier port.

 

From here, you can set the email to from the attribute value containing the concatenated list of emails.

image


juliarozema
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • March 18, 2022
chrisatsafe wrote:

Hi @juliarozema​ ,

You can use a FeatureMerger for this. After aggregating to concatenate all of the email addresses into a single feature (comma separated), you can merge it onto the feature(s) that trigger the Emailer. In the FeautreMerger, set the requestor and supplier to the same character like "." or "x". This will merge the aggregated attribute onto the stream that is going into the Emailer.

imageIn your case, the Creator is the rest of your workspace (goes into the requestor port), and the aggregate feature from the Text file goes into the supplier port.

 

From here, you can set the email to from the attribute value containing the concatenated list of emails.

image

Woohoo!! Thank you @chrisatsafe​. Most excellent. This is exactly what I needed.

Have a great weekend,

Julia


juliarozema
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • November 26, 2024

Hello,
I have to activate this question again.  I have upgraded to FME 2024.1.3 and using the FeatureMerger (like shown in Chris’ screen capture use a “.” in the Requestor and Supplier) to add the email addresses from a text file is no longer working.

Is there a way to continue using the Feature Merger but with different settings?

Again, the question is:

an email address is within a text file.  How can this email address be added to every record?  Was using a FeatureMerger before upgrading to 2024.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings