Skip to main content
Archived

HTMLReportGenerator improvement suggestions

Related products:Transformers
  • November 3, 2016
  • 6 replies
  • 97 views

lifalin2016
Influencer
Forum|alt.badge.img+40

Hi,

I've just used the HTMLReportGenerator, and the result is not exactly how I want it to be

Here are some suggestion to enhance the transformer's output:

  1. A choice to generate only a part of a HTML document, i.e. something that can easily be embedded in the body part. This way one could assemble multiple parts into a single document with ease.
  2. A choice to avoid having the textual content html encoded, so HTML tags can be used freely.
  3. Add the possibilty of embedding some CSS styling into the HTML document, especially the possibility to specify text fonts and font size.
  4. Alternatively, adding a CSS file/url reference would be great.

Cheers
Lars I

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

Forum|alt.badge.img+6
Agreed, having control over column widths when creating a table would be good to have as well

 

 

Another thing I'm noticing is that incoming attributes are dropped and you have to play some tricks to get those attributes to pass through, such as grouping by them (even though you might not want/care to group). Or you end up having to use a FeatureMerger to get those attributes back. A case scenario is when you are assigning a recipient email to the incoming features, pass everything through the HTMLRepoertGenerator and then to the Emailer: you lose the email attribute unless you group by it.

 

 


jneujens
Forum|alt.badge.img
  • October 17, 2017
I am using version FME Workbench 2017.1 (build 17539) and I seem to have to same problems.

 

 


jneujens
Forum|alt.badge.img
  • October 17, 2017

It would useful to adapt the graphs: widths of the bars, sizes of the frames and most of all the legend.

 

 

Underneath is a screenshot showing the problem for the legend. The textbox for the legend is so small it puts the text on several lines. For more elaborate legends, the texts starts to overlap other elements of the legend making it less readable.

'


jneujens
Forum|alt.badge.img
  • October 17, 2017

It is also not possible (in build 17539) to use the parameter editor. Changing parameters is only possible when double clicking the transformer, and making edits in the new window.


revesz
Supporter
Forum|alt.badge.img+21
  • Supporter
  • October 17, 2017
Absolutely. XMLTemplater is unsuitable to write HTML emails, I ended up the manual way (chains of AttributeManagers and Aggregators)

 

I would also be really happy with a HTML5FragmentTemplater or something similar.

 

 


j.botterill
Influencer
Forum|alt.badge.img+60
  • Influencer
  • November 29, 2023

For those following ideas, there are other HTMLreportgenerator improvements being requested by the community

AC Idea: HTMLReportGenerator Table Styling (safe.com)

AC Idea: htmlreportgenerator - allow for layer colour to be linked to attributes (safe.com)

Symbolise Layers in HTML Report Generator / HTML Layouter (safe.com)

Ideally the htmlreportgenerator content settings would allow the "Color Layer" to make use of conditional values so you can style different fme_feature_types/fme_color for exampletransformers_with_color_conditional