Shape the future of FME with your ideas
Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.
I would love for the bookmarks to snap to the grid when they are created Would be a small change, but big QoL update !
I often find in some scenarios it would be helpful to have annotations point to multiple transformers.In the scenario below, the annotation applies to both the AttributeExposer and the AttributeRemover, but I can only connect it to one An alternative way is adding it to a bookmark and annotating like below. I think a bookmark is overkill in this situation and having the annotation attached to both would be helpful
Hi there, it could be a good idea to have a ‘zoom to’ button on a hidden connection, that takes you to the other end (start or end) of a hidden connection. Sometimes I instantly want to see where the other end of the hidden connection is without having to manually scroll and find it
Hi there, when using hidden connections, I still like to know the counts of features going through the outputs, however using hidden connections doesn’t show this. I can add a junction afterwards to show the count and then create a hidden connection, but it looks a bit messy to do that for things like test filters etc. So putting counts inside the transformers seems like a good idea. Can have the ability to turn this off if needed. Alternatively, can show the count at the start point and end point of a hidden connection
Hi there, I like the idea of being able to look at a workspace and seeing easily what transfomers change attributes, which change geometry, which filter etc. To do this, it would be nice to change the colours of transformers, so I could have say green transfromers are filter transfromers etc. I could add annotations to the top of these but it becomes a bit cumbersome. If you can rename transfomers, changing their colours should not cause any unintended issues.
It would be useful to allow a way to group related transformers together without having to use a bookmark. Bookmarks can take up too much space, or also the grouping might not be logical to put in a bookmark. Would be nice to just be able to select a group of transformers and make them ‘stick’ to each other, so if you need to move them again you don’t have to manually select the whole area they cover (and accidentally select other things you don’t want), all this can make working with FME more productive
Hi there, I like to create hidden connections for larger workspaces to keep things tidy. However, so many times when I select and grab a group of transformers I end up accidentally selecting the hidden connection and removing it. It doesn’t help also that the hidden connection colour is too light when you select a transformer that uses it.
Using FME as a mail merge tool to fill in form content to a word document with pre-defined fields would be great. Currently the data has to be written to excel then mail merged to the template document. It would be good to do this within FME.
PDF/Word documents have the ability to create form fields for users to fill in. Looking for the ability to auto-populate some or all of these fields from a database record. Ideally, the writer would accept a template .docx or .pdf and allow the field from the database to write to a field in the form.
The new DV functionality seems amazing, I haven’t tried it out yet, but I understand it as one has to provide workspaces for every api endpoint one is creating.Wouldn’t be great if one could easily, in the FME Flow interface, create CRUD (Create, Read, Update, Delete) functionality? This is all functionality that is available in reader/writers, one just have to specify required attributes, primary keys etc.
It would be great to have an 'undo' function for automations that are deleted.
As FME continues to grow in popularity and power, it would be incredibly valuable to have an official FME mobile app that connects users more closely with both the community and their FME workflows. ield teams can stay connected and monitor automation workflows. New users can learn anytime, anywhere. Community engagement will increase, especially for those using mobile devices. It enhances the overall reach and impact of the FME platform. I believe this app could significantly enhance the FME ecosystem and empower both professionals and learners in more flexible, modern ways.Looking forward to the community’s thoughts and Safe Software’s consideration!
The message parameter on the desktop side can be formatted (for color styling) using html tag. However, when the FME workspace published to the FME Flow, the message is not getting formatted and displaying the html tag as part of the message.
Hi there,In ArcGIS Online/Portal if you are writing to a feature service, and that feature service already exists, then almost always you want to write to an existing layer. However the current workflow is:Add writer Add bogus feature type Import Feature type from existing layers Delete bogus feature typeI feel like this could be optimised. When you add a Portal/Agol Writer, and you choose an existing feature service, you should be prompted to select from the existing layers from that feature service.This would be a great quality of life update for people that write to Esri Web Layers often.Thanks,Marc
Currently FME can’t guess a format, if the dataset is a zip file, and the user has to select the Format manually.
I’ve become a fan of AI assist, particularly for writing regex. However, I note that on returning to a workspace after a break, I can’t remember exactly what the prompt I gave it was.Might be useful to be able to expose that prompt as an annotation or as a comment within the transformer, as I see now with certain transformers.
When joining data sources with lots of attributes, it can be a little difficult to track what came from where. One potential solution would be to be able to add a coloured tag based upon the input. E.g.
It would be really helpful to have the ability to save a post as a draft before publishing it—whether it's a question, conversation starter, or idea. Sometimes I need a bit more time to refine things or come back to it later.
When publishing a workspace to Server, you have the option of pushing up your database connections. My idea is to be able to download these to be added to your Workbench database connections. This could be helpful to editors who do not have the connections settings, and would also help rebuild your desktop environment (i.e. if you have a new computer or your system crashes.)I suppose this could be a security issue, but my assumption is that if I gave you sufficient privileges to download/publish then you should also be granted access to the db connections. It may also help that the password characters are not displayed on the connection properties dialogs. I also assume these are not stored in plain text.
When bookmarks are closed, transformers inside the bookmark are not cached. While this is a great feature, I barely use it as closing and opening bookmark usually change the layout, and I really like to see the transformers and how many features go where. It would be nice to have a featurecaching enable / disable switch on bookmarks.
I usually don’t like hiding code behind custom transformers or keeping bookmarks collapsed, so I avoid that approach. At the same time, I often need to turn off feature caching for specific parts of my workbench. Right now the only way to do that is to collapse the bookmark, which messes up my layout.It would be great to have an option on each bookmark to toggle feature caching on or off without having to collapse it. That way you can see your code and layout exactly as you want, while still controlling caching behavior where you need it.
When accessing the FME Flow WebUI, the initial focus should be set to the username field again.This used to be the case.Currently, it takes four tabs to get there. This isn't particularly user-friendly.
It would be really helpful if the FME Flow RUN WORKSPACE UI could display the workspace start time directly during runtime.I think switching to the log for this is a possibility but unnecessary.
Currently, searching for a location in a workspace app’s geometry parameter window appends the search bar contents to Nominatim’s URL. Example 1:Nominatim URL: https://nominatim.openstreetmap.org/ Search entered in workspace app: “vancouver” Appended Content: “search.php?q=vancouver&format=jsonv2” Resulting GET request: https://nominatim.openstreetmap.org/search.php?q=vancouver&format=jsonv2 What gets appended does not allow users or workspace app authors to include additional parameters limiting users’ search results in the Nominatim URL. Adding parameters that are compatible with the q parameter such as countrycodes, limit, and layer to the Nominatim URL breaks the resulting GET request. Example 2:Nominatim URL with parameters added: https://nominatim.openstreetmap.org/search.php?countrycodes=ca&limit=1 Search entered in workspace app: “vancouver” Appended Content: “search.php?q=vancouver&format=jsonv2” Resulting GET request (invalid): https://nominatim.openstreetmap.org/search.php?countrycodes=ca&limit=1search.php?q=vancouver&format=jsonv2 FME Flow should check if the Nominatim URL already includes parameters designed to limit users’ search results before deciding what to append so the final result is always a valid GET request such as: https://nominatim.openstreetmap.org/search.php?countrycodes=ca&limit=1&q=vancouver&format=jsonv2 The current workaround is to add the additional parameters in the search bar. Example: “vancouver&countrycodes=ca&limit=1” This is cumbersome for users. Posted from:
Currently, when building a workspace app that includes a geometry parameter, the parameter is collapsed by default. This means users have to know to expand it before they can provide any input.It would be great to have the option to set the geometry parameter to display inline (expanded) by default. This would make the input more intuitive and improve the overall user experience.
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.
