Skip to main content
  • EN

Hello, I’m new to working with Flow automations and still fairly beginner level with FME. I appreciate any guidance you can provide.

The Workspace

I am working with ArcGIS Online and Field Maps. We have teams in the field everyday collecting data. At the end of the day I run a workspace that tidies up their tracklogs and calculates how many km they covered and hours spent.

I’m using 2024.2 build 24783 for both Form and Flow.

What I want to achieve

Having this data in the feature service isn’t enough. I also want an email summarising this information.

How can I do this with Flow Automations?

What I’ve tried

With the Email action I see options to send basic information like attaching the log, how much time it took to run, what time it ran, but I want more detailed information to show in the email. The information is an FME Feature Attribute created in the workspace pictured below.

One colleague said it wasn’t possible in Flow and is better to do in Form using the Emailer transformer. Is that correct? I have successfully set up in Form’s Emailer transformer. Another colleague has told me I can do it in Flow, but I haven’t been able to figure out how. I would prefer to do it in Flow.

I’ve also read through this article - https://support.safe.com/hc/en-us/articles/25407747313293-Send-Email-from-Automations.

Thanks in advance for any guidance. If you could provide a screenshot showing where I should go/what I should do that would be helpful.

Hi ​@epro_admin,

 

Absolutely, you can do this in FME Flow! The Automations Writer lets you extract parameters from a workspace running within an automation, which you can then pass to an Emailer. You have complete flexibility in formatting the email and embedding those parameters in the email body.

To complement the article you shared, I'd recommend taking a look at the documentation here: Routing Data From Workspaces. Additionally, there's a helpful tutorial in FME Academy—check out the Flow Authoring course under Connect Automations with Job Orchestration > Use the Automations Writer. You can access this course for free with your community account.

The Emailer will send an email as soon as a feature reaches the transformer, whereas the Email in Automations will only be triggered once the workspace translation has been completed. This provides additional control over which scenarios an email is actually sent out.

 

Please let me know if you need more information. 

 

-Dylan

Hi ​@dylan.at.safe ,

Is there a way to use attributes from a workspace in the fme flow email action without connecting the port?

I have an automation that runs a workspace and then a resource/directory watch that triggers an email once a new file is added.

If i connect the automations writer port to the emailer then it sends two emails, one when the attributes hit the email action and one when the directory watch fires. the first email contains the attributes, and the second contains the attachments which is of course not ideal.

Hi ​@bromp, 

 

Do you have a screenshot of your automation? It sounds like you may need to use a Merge Action. Unfortunately, there isn’t a straightforward way to include workspace attributes in the Email Action without connecting it to the workspace's Writer port in the automation.

 

-Dylan

Hi ​@dylan.at.safe ,

Is there a way to use attributes from a workspace in the fme flow email action without connecting the port?

I have an automation that runs a workspace and then a resource/directory watch that triggers an email once a new file is added.

If i connect the automations writer port to the emailer then it sends two emails, one when the attributes hit the email action and one when the directory watch fires. the first email contains the attributes, and the second contains the attachments which is of course not ideal.

 

You might want to write your data in a file/database, and retrieve them when your directory watch fire.

Reply


Community Stats

31,515
Posts
119,462
Replies
39,130
Members

Latest FME

Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.