Skip to main content

In an automation, we are utilising an automation writer to pass a dynamically created json syntax for sending an email to a relevant FME Server topic.

 

e.g. { "email_to" : "<to email>", "email_cc" : "", "email_bcc" : "", "email_from" : "<source email>", "email_replyto" : "", "email_subject" : "Hi", "subscriber_content" : "its me again" }

 

The topic is however sending this as "content" rather than breaking it down into relevant parts when it is passed in as a variable from the automation writer (in this case {route.Output.text_line_data})

 

However, if I past that same hardcoded text value into the notification, rather than have it come from the automation value, then it works.

 

We utilise a email subscriber to send all emails, rather than setting up individual email sending for each automation, so we don't want to change how we achieve this. And I also know a workaround is to use a FMEServerNotifier inside the first workspace, but I would love to know what is causing this.

Be the first to reply!

Reply