Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
hi there,In Automations you can select multiple items and edit their tags together. This is not possible with Schedules.I would like Schedules to have the same tag management options as automations.Thanks,Marc
Being able to store the HTML, JasvaScript, CSS, or other static content in FME Flow Resources folders and serve them via Data Virtualisation Manual Endpoints directly (without a workspace that feed the Data Virtualisation Writer attributes) would be more straightforward and engine saving way to provide HTML pages, so the Workspace Endpoints could deal with the dynamic contents.OK, it needs the ability to set the content_type header as well.
Hi,Wouldn’t it be great if FME could automatically generate a link to your API docs, just like the FME Flow API does? This would make the APIs you create almost self-documenting and ensure compliance with the Dutch national API guidelines.
Hi Safe team!I think it would be handy to create some separation of job logs, between Data Virtualization and ‘standard’ FME jobs.Depending on what you create with Data Virtualization, the volume of jobs which trigger could be substantial - and I think users will have very different needs for those two categories.As an administrator, it will be very challenging to find particular ‘standard’ job(s) amongst all the DV job logs.You may also want to configure the settings quite differently for the age of logs to keep. It’s much more likely you’ll want to keep logs which trigger as a batch job weekly/monthly for a longer period of time (i.e 3 cycles so you have a comparison between jobs). Whereas with the DV job logs, they’re probably a bit more disposable, and not something you’re likely to be looking back on a few weeks/months ago for a single API request.
It would be great if the email of the user running an app could be delivered as an automation app parameter so that the person who pushed the button could easily be emailed without additional workflow or having to enter via a parameter which is open to error.
In certain cases, a model has been revised or changed, while you have the FME AR app open. It would be great to be able to refresh/reload the file (same filename etc but with the latest changes), without having to send/download/upload. E.g. produce files directly to the cloud, and prompt the user that a newer version of your file has been detected (if you always get the files from e.g. Google Drive or similar).
Currently, selected transformers can be positioned by right-clicking and selecting either Align or Spread. Align provides the following options: Left, Middle, Right, Top, Center, or Bottom. Spread provides the following options: Horizontal or Vertical.I’d like to allow the user to align transformers by ports. I often find myself trying (and failing) to align transformers so that the output of one transformer directly aligns with the input of another transformer.
From this Q&A: Style Excel cell valuesIt would be great if the @CurrentAttribute() function could be applicable in a conditional value setting in order to set style individual cells conditionally. For example, allow this setting to set background color to A, B, C, D, and E columns separately according to each value (currently this setting is invalid).Expected Result:
It would be great to able to disable certain automations in FME Server when a restore from backup is completed. For example Publications, Subscriptions and Schedules. This would ensure that FME Server Workspaces that receive and send emails will not cause conflicts when moving from one install of server to the next.
It would be great to have an azure service bus connector so it is possible to write directly to an Azure Service Bus Queue within FME. Use case: I have records in my fme workbench that I want to write to an azure service bus queue. This would enhance fme's capabilities in the enterprise integration area especially when it comes to working with data and systems in the cloud.
Migration Note: Idea originally posted on 2015-10-29
We heavily use Automation Tagging to "describe" contents of the automation (e.g. which day of the week it runs, whan during day - in the evening, during night, early morning etc). With current UI it is possible to add/delete tags only, they remain in the order when they have been added. In some cases it would be useful to change the order of the tags, as in most cases currently the best idea is to delete all of them and add from scratch.
Slice solids with surfaces
When you use Zoom to Selected Feature in the Data Inspector, it seems to zoom in or out to some per-determined zoom level (some factor of the dataset extents?) However it would be much more useful to keep your current zoom level, ArcGIS Pro works like this and it works better IMHO.
Now AttributeExposer can only add each attribute name manually.but in many cases,There are some rules for the attributes name that needs to be exposed.Therefore I suggest that add wildcards and regular expression support to AttributeExposer.
E.g. dynamically exposing attributes to the workflow like this:
See this discussion. It would be useful if the url of FME Flow is available in an Automation as an attribute, just like it is available as a parameter in Workspace
A bit of a pipe dream, probably not possible to implement and for the most part there are workarounds, however, having some kind of compatibility mode would really help as a consultant / solution provider.When working with a large number of customers all of which have a different version of FME you need to make sure you have a lot of versions of FME installed to cater to all of them.This is mostly fine, however, with each release of FME the Installation grows in size, and, depending on the size of your disk it puts a cap on the number of different Installations you can have. If, however, I could always work with the latest version of FME (and take advantage of all the nice UI upgrades and things like workspace compare and merge like in FME 2023+) then it would really streamline the development process. Expected behaviour:When opening an old workspace in a newer version of FME a prompt asks if you'd like to open in compatibility mode.Compatibility mode would essentially be a restricted version of FME - formats and transformers would be limited to the appropriate versions etc.Saving a workspace in while in compatibility mode would enable a workspace to be opened up in that version. An option with new workspace to set the compatibility version. It should be noted that there would likely be sometimes differences in behaviour when actually running the workspace so warnings need to be put in place and the authors need to know the limitations. This perhaps would likely end up being a showstopper for some.Another benefit would be when the FME Server version is older than then your FME Desktop version. This means the feature would not only benefit solution providers but also users who work with an FME server in a rigid IT infrastructure with slow upgrade cycles. It would be acceptable if this functionality only supported a limited number of previous versions.Being able to reduce the number of FME installations and being able to use some new UI features would be a real benefit.
It would be great if FME 2022 supports read/writer CityGML 3.0https://docs.ogc.org/guides/20-066.html
Pdf page formatter in 2015.0 Is a good start. The fields need to receive params and atttibutes please. And the frames should be allowed to have overlap and different page_units extents. For the time being can pipe the layout and marginalia through one and the map frame and scale bars and insets through others and it should work. But would like to use attributes in the PDF transformer instead of values.
Writing data to IFC at the moment in FME is a little bit of guesswork because the target schema is so focused as to what is "allowed in". With formats like GPX, when you add the Writer it lays down for you the permissable FeatureType names and attributes, giving you at least a starting point and an indication that calling a layer "Bob" or "Test1" isn't going to get you too far.In the short term it strikes me that perhaps a template that helps to show how to set Names, Traits and Geometry Names might be a good starting point.
It would be convenient when moving FME Desktop installation from an old machine to a new one if there was a functionality to backup/restore FME Options configuration, especially regarding Database/Web Connections.
I'm frequently asked if it's possible to setup FME Desktop with some default configuration e.g. Proxies, Shared folders, database connection file locations, window layout, transformer versions turned on, number of recent workspaces set to 10 etc... and then save that off as a config file that can be deployed to other installations of FME Desktop in an organisation. Currently the closest option to this is a silent install, or packaging FME, but that's much more of an admin overhead.It feels like with 2019's ability to save presets in Transformers we're going in the right direction, so here's a suggestion along the same theme that will help organisations with more than a couple of installations of FME Desktop.
I'd like other users to see schedules and connections but not to change.Now there is "None" or "Full Access" (edit/delete) options only (unlike Read, Write, Remove for Topics, Subscriptions, etc.) per schedule/connection. A "Visible" or similar option would be really helpful.There are shared connections that I would promote to use but not to changed (same as in Desktop). Similarly schedules are OK to be visible for reference but shouldn't be editable to anyone.
I think it would be beneficial if there was a fourth option for Severity Level in the Logger, perhaps called LOGGER, and to go along with this a filter button in the Translation Log window. That way we would have the option to view all logs just from the loggers that have this option set.Thoughts?
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.
