You could add a htmlreportgenerator with this message in a custom html part, then publish the workspace including job submitter AND the Data Streaming service, where you specify the html writer/featurewriter.
some articles that may help
https://support.safe.com/hc/en-us/articles/25407401060365-Tutorial-Custom-Data-Delivery-using-FME-Flow The FME Flow Data Streaming Service can also be used to stream data such as an HTML page, PDF, or image directly in a user's browser so they do not have to download anything on their machine to view workspace outputs.
Thank you @j.botterill.
I have the html generated and published as job submitter and data streaming… For some reason the result was in .zip file..
I will look into the articles you suggested and see if I can have it to work..
Thanks.
You could add a htmlreportgenerator with this message in a custom html part, then publish the workspace including job submitter AND the Data Streaming service, where you specify the html writer/featurewriter.
some articles that may help
https://support.safe.com/hc/en-us/articles/25407401060365-Tutorial-Custom-Data-Delivery-using-FME-Flow The FME Flow Data Streaming Service can also be used to stream data such as an HTML page, PDF, or image directly in a user's browser so they do not have to download anything on their machine to view workspace outputs.
Yes. Figured it out!
Thank you @j.botterill for pointing me to the right direction!!
Thank you!!!
One thing you have to be prepared for, if it is a public facing app, is a horrendous amount of traffic, including fake and rubbish inputs. And I’m not even talking about a DDOS-attack, simply the amount of interested (or bored) people taking a look, and some of them will think it’s funny to enter completely rubbish stuff. And don’t forget the bots constantly scraping the interwebs for everything they can get their hands on, and will try to fill out any forms and submit them just to see what happens...
If it is just FME Flow handling this, make sure it has the capacity to deal with something like 60 requests per minute for example. And having to create an account won’t stop a lot of them either, I’m afraid. It’s one of the main reasons why I wouldn’t use a public-facing FME Flow webapp...
Great point! @s.jager
Yes. I am totally with you. I am concerned when I see the url as well..
May I ask what you usually use for public-facing survey? Will Survey123 work better?
Thank you!
I don’t use public-facing survey’s. So I have no idea what you could use that can handle everything that’s out there these days, but I’m sure there are options. No experience with Survey123, no idea what that can handle.
My FME Flow is behind our firewalls and only visible inside our own domain, but even there I see that frequent use can challenge both soft- and hardware. I’ve created a handful of FME Flow Webapps for my colleagues, around 200 - 300 users make use of them, some quite frequently when I look at the logs. And that does impact the server. If you open that up to the public….
3rd party tools like MuleSoft can be public internet middleware to your FME Flow behind the firewall.
