I am automating a process of creating a Service Request on City works suing an Email (IMAP) topic and notification on FME Server. However, when email is received, my Workspace reads (JSON reader) it as an html instead of plain text and charset- utf=8; I have JSON extractors and HTTPO caller later in the Workspace and therefore due to this problem fails to create SR. I am attaching an image from the log file. Any feedback is much appreciated.
Question
Why JSON Reader reads the email as html instead of plain text ? Any transformer that I could add after JSON Reader to avoid this issue?
+35- Celebrity
So from the content type you can see that it's set to text/html - this means that the content of the email body itself is HTML. One thing you can do it to do a test on the content type and, if HTML, then you can use an HTMLExtractor.
You can see here that the JSON reader has worked correctly, it's parsed the JSON from the FME Server notification into fme attributes.
There is some more info here about it: https://docs.safe.com/fme/html/FME-Flow/ReferenceManual/IMAP_Publisher_Notification_Content.htm
+6- Contributor
virtualcitymatt wrote:
So from the content type you can see that it's set to text/html - this means that the content of the email body itself is HTML. One thing you can do it to do a test on the content type and, if HTML, then you can use an HTMLExtractor.
You can see here that the JSON reader has worked correctly, it's parsed the JSON from the FME Server notification into fme attributes.
There is some more info here about it: https://docs.safe.com/fme/html/FME-Flow/ReferenceManual/IMAP_Publisher_Notification_Content.htm
@virtualcitymatt Thats a good idea. I will try. Thank you so so much.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.