Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I have a requirement that my Webhook Automation can only be triggered by authorized applications, so it would be great if Automations Webhooks supported authentication through header specification. Eg. The request to the Webhook requires an Authorization header key with an FME Server token similar to the FME Server REST API.
Currently it's either all or nothing. A group by option would be helpful. Also better attribute handling, e.g. keep first attribute, concatenate, build list etc.
After scheduling a FME-Server job I want to try it out if everything runs as expectet. If I run it with "Immediately" checked, my previously set date and time settings are overwritten with the time at the given moment I run the scheduled task.An option to run the scheduled job once on demand without affecting any settings would therefore be nice. Similar to the windows task scheduler option to just run a task on demand.
Similar to this idea here: https://community.safe.com/s/idea/0874Q000000Tl36QAC/detailUnder Engine Assignment Rules (and even Job Routing Rules) have the ability to select a time window where jobs/engines get assigned to queues. EG during business hours have time critical jobs utilise the majority of you engines, then out of hours, allow for background task and less time dependant tasks to utilise those same engines
It would be nice to have options for the selection of the background map that is shown in the Geometry parameter. At the moment it is Leaflet | OpenStreetMap. Other web maps or a custom web map would be nice.
Migration Note: Idea originally posted on 2015-11-26
It would be nice to be able to Filter on Just messages from my Loggers. I think this would be a great addition to FME 2018's Log window filter. It would also same space in my log files and searching time (I could turn off INFORM).
PDF Tables are not detected in FME if not tagged as table by an appropriate software. However most of the PDF tables are not tagged correctly, and the PDF reader then does not read them. On the discussion here: https://knowledge.safe.com/questions/90534/reading-pdf-table.html?childToView=90894#comment-90894@jakemolnar and @krisvewsp had some ideas to improve this reader. Maybe something to look at? Would be very useful! Thanks,Claire
It would be great if there would be an option to stream result of one workspace in the automation. I presume max one workspace per automation would have that option.Alternatively, there could be new action in automation builder that would stream result.
Add QGIS support in Integration Console and/or create a QGIS plugin to integrate FME readers/writers inside QGIS ?
Allow GIT or Subversion to be used as a revision controlled repository for workspaces, and Workbench interacts directly with that system when saving workspaces.
Add more sensors ( compass, accelerometer...)
Migration Note: Idea originally posted on 2015-10-29
I was just playing with SQL Notebooks in Azure Data Studio, and I found this quite a fun and interesting concept. Then there are of course Jupyter/Python notebooks as well. (In case you are not familiar with the concept - you basically write a documentation document with notes and descriptions and inside it you embed data cells that perform operations. You can either run all cells, or run them one by one.) My next thought was - what if one could have an FME notebook? I think it would work very well for not-too-complicated one-off workspaces, or for tutorials. The documentation text is central and data cells one could perhaps be like bookmarks in a workspace. I am not sure how it would work and/or how one would implement this... But imagine uploading an FME notebook to a Flow instance to create a server app centered on the documentation and step by step execution of transformers/bookmarks/operations! Migration Note: Idea originally posted on 2024-02-01
***Note from Migration:***Original Title was: "Reject"port for writers \ changes to error log behavior with rejected features by writers Currently, when features are rejected when writing a file, there is no way to tell until you open the file.For example, if 51 features are passed by a transformer (and are visible in the inspector or other data formats), but 4 cannot be written to a specific writer (rejected), FME will still report"51 features written, Transformation successful"even though in actuality only 47 features are written.I propose that the FME logger and workspace will say"47 features written, 4 rejected by output file, Transformation successful"Alternatively, the addition of a "reject" port for writers can also be a solution.As there is no "reject" port for writers as there is with transformers, there is no way to tell without scrolling in the error log whether all features are written by a specific writer, until you open exported file in FME Data inspector.This behavior is discussed in this thread with an example. https://knowledge.safe.com/questions/69542/missing-points-when-exporting-to-shapefile.html?childToView=69550#comment-69550 Migration Note: Idea originally posted on 2018-05-03
When I got a humongous pile of parquet-files I had to find a way to read and filter the data in them. I found this and it works great, https://duckdb.org/docs/guides/import/parquet_import.html.Fast SQL-queries on all files without having to move the data into something else first!Using DBeaver and a DuckDB connection ":memory:" I can do queries like this:select count(distinct Id) FROM "D:\myfiles\**\*.parquet"where startingdate >= '2020-07-27 00:00:00' Perhaps this will be a bonus with the upcoming DuckDB-reader/writer...??? :) Migration Note: Idea originally posted on 2024-02-01
***Note from Migration:***Original Title was: Text size in the JSON \ XML transformers for the XQuery text editor too small on Mac When using any of the XML \ JSON - Templater, Flattener, etc. when entering the query in the text editor, the font is so small it's unreadable on a Mac. It will not allow you to change the text size and none of the zoom options work. Other text editors are ok on the Mac. Migration Note: Idea originally posted on 2019-04-18
I propose creating a file navigation window, akin to QGIS' "Browser," to FME Desktop. This window would enable me to swiftly browse files and decide whether to use them as readers or writers.Moreover, I envision the convenience ofmarking specific paths as favorites or bookmarks for my frequently used locations. This feature aims to enhance the user experience by simplifying the process of locating and incorporating files in FME Desktop. Migration Note: Idea originally posted on 2024-02-02
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
